Control data bandwidth allocation for fifth generation (5G) new radio communications

Abstract

Apparatus, systems, and techniques for transmitting control plane data over a radio network. In at least one embodiment, bursts of control plane data for future transmission slots are transmitted in a non-overlapping dedicated window at the end of the previous transmission slot.

Description

Technical Field

[0001] At least one embodiment relates to network communication. For example, at least one embodiment relates to a method for transmitting beamforming weights as control plane data via a wireless network. Background Technology

[0002] Computer networks typically implement multiple data channels, allowing for the separation of user data and control data. Control data can include routing information, client state, media access information, and so on. The amount of control data can vary, at least in part, based on network topology and other factors. For example, in wireless networks, control information can include parameters such as beamforming weights in multi-antenna systems. Often, control data competes with user data for bandwidth. Therefore, finding methods to accommodate control data without unduly impacting user data transmission is an important research area. Attached Figure Description

[0003] Figure 1 An example of an overlapping transmission window according to at least one embodiment is shown;

[0004] Figure 2 An example of a dedicated control plane transmission window according to at least one embodiment is shown;

[0005] Figure 3 An example timing distribution diagram of a non-overlapping control data plane window according to at least one embodiment is shown;

[0006] Figure 4 An example analysis for determining the size of a dedicated control plane data window is shown according to at least one embodiment;

[0007] Figure 5 An example analysis for determining the size of a dedicated control plane data window is shown according to at least one embodiment;

[0008] Figure 6 An example is shown of a process for transmitting data over a wireless network using a dedicated control plane window for beamforming weight parameters, as a result of execution by a control data thread, a user data thread, and a beamforming weight thread, according to at least one embodiment.

[0009] Figure 7 An example data center system according to at least one embodiment is shown;

[0010] Figure 8A An example of an autonomous vehicle according to at least one embodiment is shown;

[0011] Figure 8B The illustration shows an embodiment according to at least one of the embodiments. Figure 8AExamples of camera positions and field of view for autonomous vehicles;

[0012] Figure 8C This is an illustration based on at least one embodiment. Figure 8A A block diagram of an example system architecture for an autonomous vehicle;

[0013] Figure 8D The illustration, according to at least one embodiment, is for one or more cloud-based servers and Figure 8A A diagram of a system for communication between autonomous vehicles;

[0014] Figure 9 This is a block diagram illustrating a computer system according to at least one embodiment;

[0015] Figure 10 This is a block diagram illustrating a computer system according to at least one embodiment;

[0016] Figure 11 A computer system according to at least one embodiment is shown;

[0017] Figure 12 A computer system according to at least one embodiment is shown;

[0018] Figure 13A A computer system according to at least one embodiment is shown;

[0019] Figure 13B A computer system according to at least one embodiment is shown;

[0020] Figure 13C A computer system according to at least one embodiment is shown;

[0021] Figure 13D A computer system according to at least one embodiment is shown;

[0022] Figure 13E and Figure 13F A shared programming model according to at least one embodiment is shown;

[0023] Figure 14 An exemplary integrated circuit and a related graphics processor according to at least one embodiment are shown;

[0024] Figure 15A and Figure 15B An exemplary integrated circuit and an associated graphics processor according to at least one embodiment are shown;

[0025] Figure 16A and Figure 16B Additional exemplary graphics processor logic according to at least one embodiment is shown;

[0026] Figure 17 A computer system according to at least one embodiment is shown;

[0027] Figure 18A A parallel processor according to at least one embodiment is shown;

[0028] Figure 18B A partitioning unit according to at least one embodiment is shown;

[0029] Figure 18C A processing cluster according to at least one embodiment is shown;

[0030] Figure 18D A graphics multiprocessor according to at least one embodiment is shown;

[0031] Figure 19 A multi-graphics processing unit (GPU) system according to at least one embodiment is illustrated;

[0032] Figure 20 A graphics processor according to at least one embodiment is shown;

[0033] Figure 21 It is a block diagram illustrating a processor microarchitecture for a processor according to at least one embodiment;

[0034] Figure 22 At least a portion of a graphics processor according to one or more embodiments is shown;

[0035] Figure 23 At least a portion of a graphics processor according to one or more embodiments is shown;

[0036] Figure 24 At least a portion of a graphics processor according to one or more embodiments is shown;

[0037] Figure 25 It is a block diagram of a graphics processing engine of a graphics processor according to at least one embodiment;

[0038] Figure 26 It is a block diagram of at least a portion of a graphics processor core according to at least one embodiment;

[0039] Figure 27A and Figure 27B The diagram illustrates thread execution logic according to at least one embodiment, which includes an array of processing elements of a graphics processor core;

[0040] Figure 28 A parallel processing unit (“PPU”) according to at least one embodiment is shown.

[0041] Figure 29A general-purpose processing cluster (“GPC”) according to at least one embodiment is illustrated.

[0042] Figure 30 A memory partitioning unit of a parallel processing unit (“PPU”) according to at least one embodiment is shown;

[0043] Figure 31 A streaming multiprocessor according to at least one embodiment is illustrated;

[0044] Figure 32 A network for communicating data within a 5G wireless communication network, according to at least one embodiment, is shown;

[0045] Figure 33 A network architecture for a 5G LTE wireless network according to at least one embodiment is shown;

[0046] Figure 34 This is a diagram illustrating some basic functions of a mobile telecommunications network / system operating according to LTE and 5G principles according to at least one embodiment;

[0047] Figure 35 A radio access network, which may be part of a 5G network architecture according to at least one embodiment, is shown;

[0048] Figure 36 An example illustration of a 5G mobile communication system using multiple different types of devices according to at least one embodiment is provided;

[0049] Figure 37 An example advanced system according to at least one embodiment is shown;

[0050] Figure 38 The architecture of a network system according to at least one embodiment is shown;

[0051] Figure 39 Example components of a device according to at least one embodiment are shown;

[0052] Figure 40 An example interface of a baseband circuit according to at least one embodiment is shown;

[0053] Figure 41 An example of an uplink channel according to at least one embodiment is shown;

[0054] Figure 42 The architecture of a network system according to at least one embodiment is shown;

[0055] Figure 43 A control plane protocol stack according to at least one embodiment is shown;

[0056] Figure 44A user plane protocol stack according to at least one embodiment is shown;

[0057] Figure 45 The components of a core network according to at least one embodiment are shown; and

[0058] Figure 46 Components of a system supporting Network Function Virtualization (NFV) according to at least one embodiment are shown. Detailed Implementation

[0059] This document describes a system that, in at least one embodiment, provides for transmitting large bursts of control plane data over a wireless network. In at least one embodiment, the wireless network implements a multiple-input multiple-output (“MIMO”) network using multiple antennas to create signal path diversity. In at least one embodiment, this signal path diversity allows the network to acquire a set of distinct signals that are processed to reconstruct signals that would otherwise be lost in a single-antenna system. In at least one embodiment, some MIMO networks may have tens or even hundreds of antennas and are referred to as massive MIMO networks (“mMIMO”). In at least one embodiment, as the number of antennas increases, the MIMO network must generate and distribute a large number of beamforming weight (“BFW”) parameters as control plane data. In at least one embodiment, if a sufficient number of antennas are used in the MIMO network, the amount of data required to describe the correspondingly large number of beamforming weight parameters may exceed the amount of bandwidth allocated for the control plane data. In at least one embodiment, a dedicated bandwidth time slot is allocated at the end of the transmission window for the transmission of beamforming weights. In at least one embodiment, this allows the calculation of beamforming weights to be delayed to reduce the demand on network processing power and reduce the latency of updating beamforming weights.

[0060] In at least one embodiment, the wireless network is described by the Open Radio Access Network (“O-RAN”) standard. In at least one embodiment, the O-RAN Distributed Unit (“O-DU”) control plane (“C-plane”) transmission (“Tx”) window follows a concept similar to the user plane (“U-plane”) Tx window. In at least one embodiment, these windows have the same size. In at least one embodiment, in massive MIMO networks with numerous antenna arrays and data transmission layers, the amount of C-plane data to be transmitted to support beamforming weighted transmission (real-time) becomes significantly larger than the typical C-plane data rate, which does not include BFW. Therefore, in at least one embodiment, the same C-plane Tx window used for non-mMIMO use cases is generally not suitable for mMIMO use cases because the same C-plane Tx window for the large amount of data to be transmitted results in a sudden increase in fronthaul (“FH”) peak throughput. In at least one embodiment, to address this issue, different (unequal) relationships are defined between the C-plane and U-plane O-DU Tx windows to accommodate mMIMO use cases.

[0061] At least one embodiment addresses this issue by expanding the O-DU C-plane Tx window size to be larger than the U-plane Tx window size to avoid peak throughput in large-scale MIMO applications. In at least one embodiment, the C-plane Tx window (for slot #n, enhanced) overlays the U-plane Tx window for slot #n-1, causing the FH peak throughput to become an aggregation of the C-plane + U-plane data rates. In at least one embodiment, while the throughput due to the U-plane remains unchanged, the aggregated peak throughput is reduced by decreasing the average throughput of the C-plane (through the enhanced Tx window). One or more embodiments of this approach may have the following disadvantages:

[0062] 1. In some embodiments, relaxing the C-plane Tx window may require potentially large backoffs (up to one slot ahead), which would change the Media Access Control (“MAC”) scheduler to over-the-air (“OTA”) time.

[0063] 2. In some embodiments, earlier BFW transmissions may require the MAC scheduler to prepare C-plane messages. This significantly advances the timeline and necessitates more hardware processing power / CPU cores (thus increasing cost) to reduce BFW computation time.

[0064] In at least one embodiment, to avoid peak throughput in large-scale MIMO applications, the O-DUC-plane Tx window (for slot #n) with BFW is concatenated with the U-plane Tx window (for slot #n-1), rather than overlaying the U-plane Tx window (as in other solutions). In other words, the U-plane Tx window does not overlap with the C-plane Tx window carrying BFW. In at least one embodiment, the U-plane Tx window for slot (#n-1) is reduced by an amount of 𝑊𝑜𝑝𝑡, while the C-plane Tx window for slot (#n) is enhanced to 𝑊𝑜𝑝𝑡, such that the average FH data rate transmitted only by the U-plane is almost the same as the average FH data rate transmitted only by the C-plane. Various embodiments of this scheme may have at least one or more of the following advantages:

[0065] 1. In at least one embodiment, the C-plane Tx window does not require a large backoff. In at least one embodiment, peak FH throughput is reduced by cascading (non-overlapping) the C-plane and U-plane, so that the FH throughput is not an aggregation of C-plane + U-plane traffic, but mainly comes from the C-plane or U-plane. In at least one embodiment, there is no need to change the MAC scheduler to OTA timing relationship. Therefore, at least one embodiment does not impose a demand for more processing power on the MAC scheduler, which in turn may not lead to additional cost increases for large-scale MIMO applications.

[0066] 2. At least one embodiment reduces the average peak throughput at FH and can achieve a throughput reduction that is at least as good as other solutions without large C-plane timing window backoff.

[0067] At least one embodiment reduces FH throughput due to the C-plane (with BFW) by enhancing the C-plane Tx window, which has a potentially large backoff at start time. At least one embodiment addresses the peak throughput problem by adjusting the C-plane and U-plane Tx windows (overlapping with the C-plane) and by optimizing the C-plane Tx window length, thereby achieving an optimal balance between reducing C-plane throughput (with an enhanced window) and increasing U-plane throughput (with a scaled-down window) to reduce average FH peak throughput. At least one alternative embodiment requires a change in the MAC scheduler to OTA timing relationship (due to backoff from the large C-plane Tx window), while at least one embodiment described herein does not require a change in the MAC scheduler.

[0068] At least one alternative embodiment allows the C-plane (enhanced Tx window for time slot #n) and the U-plane (for time slot #n-1) to overlap, so the FH throughput is an aggregation of the C+U plane data rates, and because it does not change the U-plane data rate, the FH throughput reduction is achieved only by reducing the C-plane data rate through the enhanced Tx window, with a large time backoff of the C-plane Tx window enhancement. Instead, at least one embodiment addresses the high peak throughput problem by adjusting the C-plane and U-plane TX windows within the time slot and optimizing each to achieve the same average throughput for both the C and U planes. In at least one embodiment, by avoiding overlap between the C-plane and U-plane, the FH peak throughput is contributed by only the C-plane (carrying BFW) or the U-plane, rather than by both.

[0069] In at least one embodiment, the O-DU C-plane transmission window from O-DU to O-RU (O-RAN radio unit) follows the design of the U-plane Tx window. In at least one embodiment, these windows are typically the same size as, for example, an Orthogonal Frequency Division Multiplexing (“OFDM”) symbol. In at least one embodiment, to support large-scale multiple-input multiple-output with numerous antenna elements and data Tx layers, the C-plane data also includes significant beamforming weights. In at least one embodiment, the same Tx window will result in large data rate bursts in BFW transmissions. In at least one embodiment, designing the O-RAN C-plane Tx to manage the trade-off between BFW data bursts and the C-plane Tx window is an issue that may need to be redesigned and expanded. In at least one embodiment, a larger C-plane Tx window can flatten the data bursts, but it will also cause the MAC scheduler to advance its start time further, resulting in additional end-to-end application delays.

[0070] In at least one embodiment, a relationship is defined between the C-plane and the U-plane O-DU Tx window to support mMIMO with balanced data rates and improved latency. In at least one embodiment, the C-plane is cascaded with the U-plane on a separate Tx window to ensure that the BFW reaches the O-RU for application to OFDM symbols for beamforming, while still minimizing / removing data bursts.

[0071] Figure 1 An example of an overlapping transmission window according to at least one embodiment is shown. In at least one embodiment, non-BFW control plane data 102 is overlapped on user plane data within the transmission time slot. In at least one embodiment, BFW data 104 is overlapped on existing control plane data 102.

[0072] In at least one embodiment, to avoid peak throughput in large-scale MIMO applications, the O-DU C-plane Tx window is enhanced compared to the U-plane Tx window. In at least one embodiment, the C-plane Tx window with BFW is extended from x μs, the C-plane Tx window (without BFW), to n μs (n can be the duration of the time slot) to reduce peak FH throughput, since the coefficient of the C-plane is n / x.

[0073] In at least one embodiment, relaxing the C-plane Tx window requires potentially large backoff (earlier time slots), which changes the Media Access Control (“MAC”) scheduler to over-the-air (OTA) timing. In at least one embodiment, earlier BFW transmissions require the MAC scheduler to prepare C-plane messages. This significantly advances the time, necessitating more hardware processing power to reduce BFW computation time.

[0074] In at least one embodiment, Figure 1 An example implementation is shown where bandwidth (BW) = 100MHz, subcarrier spacing (SCS) = 30kHz, IQ compression = 9 bits, slot duration = 500μs, and slot configuration = DD.. (D → downlink slot only).

[0075] Figure 2 An example of a dedicated control plane transmission window according to at least one embodiment is shown. In at least one embodiment, a cascaded C / U plane Tx window is used, which provides a dedicated time window 202 for BFW data transmission. In at least one embodiment, the dedicated time window 202 appears at the end of the transmission time slot. In at least one embodiment, the dedicated time window 202 appears within the middle of the time slot. In at least one embodiment, to avoid peak throughput in massive MIMO applications, the O-DU C-plane Tx window with BFW (for time slot #n) is cascaded with the U-plane Tx window (for time slot #n-1), rather than superimposed on the U-plane Tx window. In at least one embodiment, the U-plane Tx window does not overlap with the C-plane Tx window carrying the BFW.

[0076] In at least one embodiment, the U-plane Tx window within the time slot is The size is reduced, while the C-plane Tx window in the time slot is enhanced. This makes the average FH data rate for U-plane transmission only roughly the same as the average FH data rate for C-plane transmission only.

[0077] In at least one embodiment, such as Figure 2As shown, the bandwidth (BW) = 100MHz, the subcarrier spacing (SCS) = 30KHz, the IQ compression = 9 bits, the time slot duration = 500μs, and the time slot configuration = DD.. (D → downlink time slot only).

[0078] Figure 3 An example timing distribution of a non-overlapping control data plane window according to at least one embodiment is shown. In at least one embodiment, U-plane data is preempted by transmission as beamforming weights for C-plane data. In at least one embodiment, for OTA slots, each slot contains 14 symbols, and the slot boundaries are relative to the physical antenna (at the radio unit).

[0079] In at least one embodiment, regarding the DU port reference time slot, the time slot boundary is the transmission of IQ data from the Ethernet port of the Distributed Unit (DU) to the Radio Unit via the Ethernet cable. In at least one embodiment, the DU port reference time slot timing is "earlier" than OTA time slot timing because data flows from the DU to the RU.

[0080] In at least one embodiment, Figure 3 In this context, Ux represents the U-plane symbol "x", and Cx represents the C-plane symbol "x". In at least one embodiment, in Figure 3 In this configuration, a series of rectangles labeled "Ux" represent the transmission duration of symbol "x" in the U-plane of time slot D(y) as the width of the rectangle. In at least one embodiment, each rectangle 306 and 308 represents the transmission duration of symbol "x" in the C-plane of time slot D(y) as the width of the rectangle, and the height of each rectangle approximately represents the amount of data carried by one symbol.

[0081] In at least one embodiment, C0 306, each time slot carrying BFW carries the first symbol of the C-plane. C1,...,C13 are the other C-plane symbols of the time slots that do not carry BFW (by...). Figure 3 (The relatively thin rectangle at the top of the U-plane rectangle is shown). In at least one embodiment, the C-plane Tx window of C0 of OTA time slot D(n) is shown as the width of rectangle 306.

[0082] In at least one embodiment, U0 is the first symbol carrying the U-plane message for each time slot. In at least one embodiment, the U-plane Tx window of U0 for OTA time slot D(n) is shown to begin just after BFW data is transmitted. In at least one embodiment, the C and U-plane Tx windows may overlap. In at least one embodiment, the C-plane of symbol x arrives earlier than the U-plane of symbol x. In at least one embodiment, since CO carrying BFW contains a large amount of data compared to other C / U-plane symbols, any U-plane Tx window “overlapping” with CO is preempted to maintain a lower FH data rate.

[0083] In at least one embodiment, the C-plane Tx window size = W opt In at least one embodiment, the U-plane Tx window size = W opt The minimum Tx window required for +U-plane data transmission. In at least one embodiment, in the case where the U-plane Tx window is partially preempted (W opt (Maximum), the U-plane Tx window is larger than the C-plane Tx window, which is sufficient for the amount of U-plane data transmission.

[0084] In at least one embodiment, the control plane data is divided into beamforming weights and other control plane data. In at least one embodiment, the beamforming weights are transmitted in bursts that preempt user plane data. In at least one embodiment, the remaining control plane data overlaps with the user data and is transmitted in parallel.

[0085] Figure 4 An example analysis for determining the size of a dedicated control plane data window is shown according to at least one embodiment. In at least one embodiment, for Figure 4 Option 2 shown, the O-DU C / U-plane data rate for the optimal O-DU C-plane Tx window size ( It becomes similar to the following:

[0086]

[0087] in, ( ) = length is The total number of bits in the C(U) plane within the time slot.

[0088] In at least one embodiment, when the C-plane Tx window (w / BFW) is extended to ~slot duration in Option 1, the optimized data rate of the C / U-plane in Option 2 is equivalent to the (C+U) plane data rate in Option 1.

[0089]

[0090] In at least one embodiment, for 100MHz BW, 30kHz SCS, 64T64R, and 16DL layers, Figure 4 The graph shown illustrates the determination of the C-plane window. Size.

[0091] Figure 5 An example analysis for determining the size of a dedicated control plane data window is shown according to at least one embodiment. In at least one embodiment, for 20MHz BW, 15kHz SCS, 16T16R, and 8DL layers, Figure 5 The graph shown illustrates the determination of the C-plane window. Size.

[0092] In at least one embodiment, as the C-plane Tx window increases, the FH data rate of the C-plane Tx (w / BFW) decreases faster than that of the U-plane Tx. Both solutions 1 and 2 can achieve similar FH data rate reductions. In at least one embodiment, solution 2 has the additional advantage of having no impact on the MAC scheduler-to-OTA timing relationship compared to solution 1.

[0093] Figure 6 An example of process 600 according to at least one embodiment is shown, in which data is transmitted over a wireless network using a dedicated control plane window for beamforming weight parameters as a result of execution by a control data thread, a user data thread, and a beamforming weight thread. In at least one embodiment, one or more computer systems implement multiple processing threads that control the transmission of control data, the transmission of user data, and the generation of beamforming weights for a MIMO wireless network. In at least one embodiment, each thread may be a single process, a lightweight process, or a thread of a process with its own storage space. In at least one embodiment, separate threads may be implemented on separate processors. In at least one embodiment, the processor may be a general-purpose processor, a multi-core processor, or a graphics processor. In at least one embodiment, each thread may be implemented on a separate core of a multi-core processor. In at least one embodiment, a system implements three processing threads, including a control data thread, a user data thread, and a beamforming weight calculation thread. In at least one embodiment, control data and user data are transmitted over a 5G wireless network; however, other embodiments may include other types of wireless networks, such as a MIMO Wi-Fi network, or a next-generation wireless network implementing MIMO technology. In at least one embodiment, the techniques described herein can be applied to 4G networks, Long Term Evolution (“LTE”) networks, or Wi-Fi networks.

[0094] In at least one embodiment, at block 602, the control data thread determines the control data to be transmitted on a time slot of the 5G wireless network. In at least one embodiment, the control data includes station updates, routing data, and other control data for managing the network itself. In at least one embodiment, the control data may be generated by a wireless station, or received by a wireless station and forwarded to another wireless station. In at least one embodiment, at block 604, the control data is transmitted over user data within the time slot.

[0095] In at least one embodiment, at block 606, the user data thread acquires user data transmitted on a time slot of the 5G wireless network. In at least one embodiment, the user data may include voice data from a wireless handheld device, data from a user equipment, or a combination of both. In at least one embodiment, at block 608, the user data thread transmits user data overlapping with the control data transmitted in block 604. In at least one embodiment, control data and user data are transmitted in parallel, and the proportion of available bandwidth of the wireless network is allocated to control data and user data, respectively. In at least one embodiment, the control data thread and user data thread operate in parallel, such as... Figure 6 As shown.

[0096] In at least one embodiment, at block 612, the beamforming weight thread is used to calculate the updated set of beamforming weights for the next time slot of the wireless network. In at least one embodiment, the calculation can occur in parallel, while control data is transmitted by the control data thread at block 604 and user data is transmitted by the user data thread at block 608. In at least one embodiment, at block 610, the user data thread is preempted and stops transmitting user data. In at least one embodiment, the transmission of user data is preempted and the bandwidth allocated to user data is redirected to the transmission of control data. In at least one embodiment, at block 614, the preemption of user data indicates the start of control data window 614 for exclusive beamforming weight transmission. In at least one embodiment, at block 616, the beamforming weight thread uses all available bandwidth of the wireless network to transmit beamforming weights. In at least one embodiment, by providing a dedicated window for transmitting beamforming weights within a time slot, beamforming weight calculation can be deferred, allowing more computation time and requiring less computational resources allocated to the beamforming weight thread.

[0097] Data Center

[0098] Figure 7 An example data center 700 that can be used with at least one embodiment is shown. In at least one embodiment, the data center 700 includes a data center infrastructure layer 710, a framework layer 720, a software layer 730, and an application layer 740.

[0099] In at least one embodiment, such as Figure 7 As shown, the data center infrastructure layer 710 may include a resource coordinator 712, grouped computing resources 714, and node computing resources (“nodes CR”) 716(1)-716(N), where “N” represents any integer, a positive integer. In at least one embodiment, the nodes CR 716(1)-716(N) may include, but are not limited to, any number of central processing units (“CPUs”) or other processors (including accelerators, field-programmable gate arrays (FPGAs), graphics processors, etc.), memory devices (e.g., dynamic read-only memory), storage devices (e.g., solid-state drives or disk drives), network input / output (“NW I / O”) devices, network switches, virtual machines (“VMs”), power modules, and cooling modules, etc. In at least one embodiment, one or more of the nodes CR 716(1)-716(N) may be servers having one or more of the aforementioned computing resources.

[0100] In at least one embodiment, the grouped computing resources 714 may include individual groups (not shown) of node CRs housed in one or more racks, or a plurality of racks (also not shown) housed in data centers in various geographic locations. In at least one embodiment, the individual groups of node CRs within the grouped computing resources 714 may include computing, networking, memory, or storage resources that can be configured or allocated to support groups of one or more workloads. In at least one embodiment, several node CRs, including CPUs or processors, may be grouped within one or more racks to provide computing resources to support one or more workloads. In at least one embodiment, the one or more racks may also include any number of power modules, cooling modules, and network switches, in any combination.

[0101] In at least one embodiment, resource coordinator 712 may be configured or otherwise control one or more nodes CR716(1)-716(N) and / or grouped computing resources 714. In at least one embodiment, resource coordinator 712 may include a Software Design Infrastructure (“SDI”) management entity for data center 700. In at least one embodiment, resource coordinator may include hardware, software, or some combination thereof.

[0102] In at least one embodiment, such as Figure 7As shown, framework layer 720 includes a job scheduler 732, a configuration manager 734, a resource manager 736, and a distributed file system 738. In at least one embodiment, framework layer 720 may include a framework of software 732 supporting software layer 730 and / or one or more applications 742 of application layer 740. In at least one embodiment, software 732 or application 742 may respectively include web-based service software or applications, such as services or applications provided by Amazon Web Services, Google Cloud, and Microsoft Azure. In at least one embodiment, framework layer 720 may be, but is not limited to, a free and open-source software web application framework, such as Apache Spark, which can utilize distributed file system 738 for large-scale data processing (e.g., "big data"). TM (Hereinafter referred to as "Spark"). In at least one embodiment, the job scheduler 732 may include a Spark driver to facilitate the scheduling of workloads supported by various layers of the data center 700. In at least one embodiment, the configuration manager 734 may be able to configure different layers, such as the software layer 730 and the framework layer 720, which includes Spark and a distributed file system 738 for supporting large-scale data processing. In at least one embodiment, the resource manager 736 is able to manage cluster or group computing resources mapped to or allocated to support the distributed file system 738 and the job scheduler 732. In at least one embodiment, the cluster or group computing resources may include group computing resources 714 on the data center infrastructure layer 710. In at least one embodiment, the resource manager 736 may coordinate with the resource coordinator 712 to manage these mapped or allocated computing resources.

[0103] In at least one embodiment, the software 732 included in the software layer 730 may include software used by at least a portion of the nodes CR 716(1)-716(N), the grouped computing resources 714, and / or the distributed file system 738 of the framework layer 720. In at least one embodiment, one or more types of software may include, but are not limited to, Internet web page search software, email virus scanning software, database software, and streaming video content software.

[0104] In at least one embodiment, one or more applications 742 included in application layer 740 may include one or more types of applications used by at least a portion of nodes CR 716(1)-716(N), grouped computing resources 714, and / or the distributed file system 738 of framework layer 720. In at least one embodiment, one or more types of applications may include, but are not limited to, any number of genomics applications, cognitive computing and machine learning applications, including training or inference software, machine learning framework software (e.g., PyTorch, TensorFlow, Caffe, etc.), or other machine learning applications used in conjunction with one or more embodiments.

[0105] In at least one embodiment, any of the configuration manager 734, resource manager 736, and resource coordinator 712 can perform any number and type of self-modification actions based on any amount and type of data acquired in any technically feasible manner. In at least one embodiment, self-modification actions can mitigate potentially poor configuration decisions by data center operators of data center 700 and can prevent underutilization and / or poor performance of the data center.

[0106] In at least one embodiment, data center 700 may include tools, services, software, or other resources to train one or more machine learning models or to use one or more machine learning models to predict or infer information according to one or more embodiments described herein. For example, in at least one embodiment, a machine learning model can be trained by calculating weight parameters based on a neural network architecture using the software and computing resources described above with respect to data center 700. In at least one embodiment, information can be inferred or predicted using trained machine learning models corresponding to one or more neural networks using the resources described above with respect to data center 700 by using weight parameters calculated through one or more training techniques described herein.

[0107] In at least one embodiment, the data center may use a CPU, application-specific integrated circuit (ASIC), GPU, FPGA, or other hardware to utilize the aforementioned resources to perform training and / or inference. Furthermore, one or more of the aforementioned software and / or hardware resources may be configured as a service to allow a user to train or perform information inference, such as image recognition, speech recognition, or other artificial intelligence services.

[0108] In at least one embodiment, data center 700 may include a wireless network, such as the MIMO network described above. In at least one embodiment, control data may be transmitted within a portion of a time window having an exclusive window with time slots.

[0109] Figure 8A An example of an autonomous vehicle 800 according to at least one embodiment is shown. In at least one embodiment, the autonomous vehicle 800 (which may alternatively be referred to herein as "vehicle 800") may be, but is not limited to, a passenger vehicle, such as a car, truck, bus, and / or another type of vehicle capable of accommodating one or more passengers. In at least one embodiment, vehicle 800 may be a semi-tractor-trailer for hauling goods. In at least one embodiment, vehicle 800 may be an aircraft, a robotic vehicle, or other type of vehicle.

[0110] Autonomous vehicles can be described according to the levels of automation defined by the National Highway Traffic Safety Administration (“NHTSA”) and the Society of Automotive Engineers (“SAE”) of the U.S. Department of Transportation in their “Taxonomy and Definitions for Terms Related to Driving Automation Systems for On-Road Motor Vehicles” (e.g., standard number J3016-201806, published June 15, 2018; standard number J3016-201609, published September 30, 2016; and previous and future versions of this standard). In one or more embodiments, vehicle 800 may be able to function according to one or more of the levels of autonomous driving from Level 1 to Level 5. For example, in at least one embodiment, vehicle 800 may be able to perform conditional automation (Level 3), high automation (Level 4), and / or full automation (Level 5).

[0111] In at least one embodiment, vehicle 800 may include, but is not limited to, components such as chassis, body, wheels (e.g., 2, 4, 6, 8, 18, etc.), tires, axles, and other vehicle components. In at least one embodiment, vehicle 800 may include, but is not limited to, propulsion system 850, such as an internal combustion engine, a hybrid powertrain, a fully electric motor, and / or another type of propulsion system. In at least one embodiment, propulsion system 850 may be connected to the drivetrain of vehicle 800, which may include, but is not limited to, a transmission, to enable propulsion of vehicle 800. In at least one embodiment, propulsion system 850 may be controlled in response to receiving a signal from throttle / accelerator 852.

[0112] In at least one embodiment, when the propulsion system 850 is operating (e.g., when the vehicle is in motion), the steering system 854 (which may include, but is not limited to, a steering wheel) is used to steer the vehicle 800 (e.g., along a desired path or route). In at least one embodiment, the steering system 854 may receive signals from the steering actuator 856. In at least one embodiment, the steering wheel may be optional for fully automated (Level 5) functionality. In at least one embodiment, the brake sensor system 846 may be used to operate the vehicle brakes in response to signals received from the brake actuator 848 and / or brake sensors.

[0113] In at least one embodiment, the controller 836 may include, but is not limited to, one or more system-on-chips (“SoCs”). Figure 8A A controller 836 (not shown) and / or a graphics processing unit (“GPU”) provides signals (e.g., representing commands) to one or more components and / or systems of vehicle 800. For example, in at least one embodiment, controller 836 may send signals to operate vehicle braking via brake actuator 848, to operate steering system 854 via one or more steering actuators 856, and to operate propulsion system 850 via one or more throttles / accelerators 852. In at least one embodiment, one or more controllers 836 may include one or more onboard (e.g., integrated) computing devices (e.g., supercomputers) that process sensor signals and output operating commands (e.g., signals representing commands) to enable autonomous driving and / or assist a driver in driving vehicle 800. In at least one embodiment, one or more controllers 836 may include a first controller 836 for autonomous driving functions, a second controller 836 for functional safety functions, a third controller 836 for artificial intelligence functions (e.g., computer vision), a fourth controller 836 for infotainment functions, a fifth controller 836 for redundancy in emergency situations, and / or other controllers. In at least one embodiment, a single controller 836 may handle two or more of the functions described above, and two or more controllers 836 may handle a single function and / or any combination thereof.

[0114] In at least one embodiment, one or more controllers 836 provide signals for controlling one or more components and / or systems of vehicle 800 in response to sensor data received from one or more sensors (e.g., sensor inputs). In at least one embodiment, the sensor data can be received from sensors, including but not limited to one or more Global Navigation Satellite System (“GNSS”) sensors 858 (e.g., one or more Global Positioning System sensors), one or more RADAR sensors 860, one or more ultrasonic sensors 862, one or more LIDAR sensors 864, one or more inertial measurement unit (IMU) sensors 866 (e.g., one or more accelerometers, one or more gyroscopes, one or more magnetic compasses, one or more magnetometers, etc.), one or more microphones 896, one or more stereo cameras 868, one or more wide-angle cameras 870 (e.g., fisheye cameras), one or more infrared cameras 872, one or more surround cameras 874 (e.g., 360-degree cameras), and remote cameras (…). Figure 8A (not shown in the image), medium-range camera ( Figure 8A (Not shown in the diagram) One or more speed sensors 844 (e.g., for measuring the speed of vehicle 800), one or more vibration sensors 842, one or more steering sensors 840, one or more brake sensors (e.g., as part of brake sensor system 846) and / or other sensor types are received.

[0115] In at least one embodiment, one or more controllers 836 may receive input (e.g., represented by input data) from the instrument panel 832 of the vehicle 800 and provide output (e.g., represented by output data, display data, etc.) via a human-machine interface (“HMI”) display 834, a voice signaler, a speaker, and / or other components of the vehicle 800. In at least one embodiment, the output may include information such as vehicle speed, velocity, time, map data (e.g., high-definition map). Figure 8A The HMI display 834 may display information such as (not shown in the image), location data (e.g., the location of vehicle 800, for example, on a map), direction, the location of other vehicles (e.g., occupancy raster), information about objects, and the state of objects perceived by one or more controllers 836. For example, in at least one embodiment, the HMI display 834 may display information about the presence of one or more objects (e.g., road signs, warning signs, traffic light changes, etc.) and / or information about driving operations that the vehicle has made, is making, or will make (e.g., changing lanes now, exiting exit 34B within two miles, etc.).

[0116] In at least one embodiment, the vehicle 800 further includes a network interface 824 that can communicate over one or more networks using one or more wireless antennas 826 and / or one or more modems. For example, in at least one embodiment, the network interface 824 may be able to communicate over Long Term Evolution (“LTE”), Wideband Code Division Multiple Access (“WCDMA”), Universal Mobile Telecommunications System (“UMTS”), Global System for Mobile Communications (“GSM”), IMT-CDMA Multicarrier (“CDMA2000”) networks, etc. In at least one embodiment, one or more wireless antennas 826 may also enable communication between objects in the environment (e.g., vehicles, mobile devices) using one or more local area networks (e.g., Bluetooth, Bluetooth Low Energy (LE), Z-Wave, ZigBee, etc.) and / or one or more low-power wide area networks (hereinafter “LPWAN”) (e.g., LoRaWAN, SigFox, etc. protocols).

[0117] In at least one embodiment, vehicle 800 may include a wireless network, such as the MIMO network described above. In at least one embodiment, control data may be transmitted within a portion of a time window having an exclusive window with time slots.

[0118] Figure 8B The illustration shows an embodiment according to at least one of the embodiments. Figure 8A Examples of camera positions and fields of view for an autonomous vehicle 800. In at least one embodiment, the camera and its respective field of view are an example embodiment and are not intended to be limiting. For example, in at least one embodiment, additional and / or alternative cameras may be included and / or the cameras may be located at different positions on the vehicle 800.

[0119] In at least one embodiment, the camera type used for the camera may include, but is not limited to, a digital camera suitable for use with components and / or systems of vehicle 800. In at least one embodiment, one or more cameras may operate at Automotive Safety Integrity Level (“ASIL”) B and / or other ASILs. In at least one embodiment, the camera type may have any image capture rate, such as 60 frames per second (fps), 120 fps, 240 fps, etc. In at least one embodiment, the camera may be able to use a rolling shutter, a global shutter, another type of shutter, or a combination thereof. In at least one embodiment, the color filter array may include a red transparent transparent (“RCCC”) color filter array, a red transparent transparent blue (“RCCB”) color filter array, a red blue green transparent (“RBGC”) color filter array, a Foveon X3 color filter array, a Bayer sensor (“RGGB”) color filter array, a monochrome sensor color filter array, and / or other types of color filter arrays. In at least one embodiment, a transparent pixel camera, such as a camera with RCCC, RCCB, and / or RBGC color filter arrays, may be used to improve photosensitivity.

[0120] In at least one embodiment, one or more cameras may be used to perform advanced driver assistance system (“ADAS”) functions (e.g., as part of a redundancy or fail-safe design). For example, in at least one embodiment, a multi-function mono camera may be installed to provide functions including lane departure warning, traffic sign assist, and intelligent headlight control. In at least one embodiment, one or more cameras (e.g., all cameras) may simultaneously record and provide image data (e.g., video).

[0121] In at least one embodiment, one or more cameras may be mounted in a mounting assembly, such as a custom-designed (three-dimensional (“3D”-printed) assembly, to cut out stray light and reflections from within the vehicle (e.g., dashboard reflections reflected in the windshield mirror), which may interfere with the camera’s image data capture capabilities. Regarding the rearview mirror mounting assembly, in at least one embodiment, the rearview mirror assembly may be 3D-printed custom-made such that the camera mounting plate matches the shape of the rearview mirror. In at least one embodiment, one or more cameras may be integrated into the rearview mirror. In at least one embodiment, for side-view cameras, one or more cameras may also be integrated within the four pillars at each corner of the vehicle.

[0122] In at least one embodiment, a camera (e.g., a forward-facing camera) having a field of view including a portion of the environment in front of the vehicle 800 can be used for surround view and, with the assistance of one or more controllers 836 and / or control SoCs, to help identify the forward path and obstacles, thereby providing information crucial for generating an occupancy grid and / or determining a preferred vehicle path. In at least one embodiment, the forward-facing camera can be used to perform many of the same ADAS functions as LIDAR, including but not limited to emergency braking, pedestrian detection, and collision avoidance. In at least one embodiment, the forward-facing camera can also be used for ADAS functions and systems, including but not limited to lane departure warning (“LDW”), adaptive cruise control (“ACC”), and / or other functions (e.g., traffic sign recognition).

[0123] In at least one embodiment, various cameras can be used in a forward-facing configuration, including, for example, a monocular camera platform including a CMOS (“complementary metal-oxide-semiconductor” color imager. In at least one embodiment, a wide-angle camera 870 can be used to sense objects entering from the periphery (e.g., pedestrians, people crossing the street, or bicycles). Although in Figure 8B Only one wide-angle camera 870 is shown; however, in other embodiments, the vehicle 800 may have any number (including zero) of wide-angle cameras. In at least one embodiment, any number of remote cameras 898 (e.g., a pair of remote stereo cameras) can be used for depth-based object detection, especially for objects for which a neural network has not yet been trained. In at least one embodiment, the remote camera 898 can also be used for object detection and classification, as well as basic object tracking.

[0124] In at least one embodiment, any number of stereo cameras 868 may also be included in a forward configuration. In at least one embodiment, one or more stereo cameras 868 may include an integrated control unit comprising a scalable processing unit that may provide programmable logic (“FPGA”) and a multi-core microprocessor with a controller area network (“CAN”) or Ethernet interface integrated on a single chip. In at least one embodiment, such a unit may be used to generate a 3D map of the environment of the vehicle 800, including distance estimates for all points in the image. In at least one embodiment, one or more stereo cameras 868 may include, but are not limited to, a compact stereo vision sensor, which may include, but is not limited to, two camera lenses (one on the left and one on the right) and an image processing chip that can measure the distance from the vehicle 800 to a target object and use the generated information (e.g., metadata) to activate autonomous emergency braking and lane departure warning functions. In at least one embodiment, other types of stereo cameras 868 may also be used in addition to those described herein.

[0125] In at least one embodiment, a camera (e.g., a side-view camera) having a field of view including a portion of the environment on the side of the vehicle 800 can be used for surround viewing, thereby providing information for creating and updating the occupied grid, and generating a side collision warning. For example, in at least one embodiment, a surround camera 874 (e.g., as...) Figure 8B The four surround cameras 874 shown can be positioned on the vehicle 800. In at least one embodiment, one or more surround cameras 874 can include, but are not limited to, any number and combination of wide-angle cameras 870, one or more fisheye lenses, one or more 360-degree cameras, and / or similar cameras. For example, in at least one embodiment, four fisheye lens cameras can be located at the front, rear, and sides of the vehicle 800. In at least one embodiment, the vehicle 800 can use three surround cameras 874 (e.g., left, right, and rear) and can utilize one or more other cameras (e.g., a forward-facing camera) as a fourth surround-view camera.

[0126] In at least one embodiment, a camera (e.g., a rear-view camera) having a field of view including a portion of the environment behind the vehicle 800 can be used for parking assistance, surround view, rear collision warning, and creating and updating occupancy raster. In at least one embodiment, a wide variety of cameras can be used, including but not limited to cameras that are also suitable as one or more forward-facing cameras (e.g., long-range camera 898 and / or one or more mid-range cameras 876, one or more stereo cameras 868, one or more infrared cameras 872, etc.), as described herein.

[0127] In at least one embodiment, vehicle 800 may include a wireless network, such as the MIMO network described above. In at least one embodiment, control data may be transmitted within a portion of a time window having an exclusive window with time slots.

[0128] Figure 8C The illustration shows an embodiment according to at least one of the embodiments. Figure 8A A block diagram of an example system architecture for an autonomous vehicle 800. In at least one embodiment, Figure 8CEach of one or more components, one or more features, and one or more systems of vehicle 800 is shown as connected via bus 802. In at least one embodiment, bus 802 may include, but is not limited to, a CAN data interface (which may alternatively be referred to herein as “CAN bus”). In at least one embodiment, CAN may be a network within vehicle 800 used to help control various features and functions of vehicle 800, such as brake actuation, acceleration, braking, steering, windshield wipers, etc. In one embodiment, bus 802 may be configured to have dozens or even hundreds of nodes, each node having its own unique identifier (e.g., CAN ID). In at least one embodiment, bus 802 can be read to find steering wheel angle, ground speed, engine rotation speed (“RPM”), button position, and / or other vehicle status indicators. In at least one embodiment, bus 802 may be an ASIL B compliant CAN bus.

[0129] In at least one embodiment, FlexRay and / or Ethernet may be used in addition to or from CAN. In at least one embodiment, there may be any number of buses 802, which may include, but are not limited to, zero or more CAN buses, zero or more FlexRay buses, zero or more Ethernet buses, and / or zero or more other types of buses using other protocols. In at least one embodiment, two or more buses 802 may be used to perform different functions and / or may be used for redundancy. For example, a first bus 802 may be used for a collision avoidance function, and a second bus 802 may be used for actuation control. In at least one embodiment, each bus 802 may communicate with any component of vehicle 800, and two or more buses 802 may communicate with the same component. In at least one embodiment, each of any number of system-on-chip (“SoC”) 804, each of one or more controllers 836, and / or each computer within the vehicle may access the same input data (e.g., input from sensors of vehicle 800) and may be connected to a common bus, such as a CAN bus.

[0130] In at least one embodiment, vehicle 800 may include one or more controllers 836, such as those described herein. Figure 8A As described above. In at least one embodiment, controller 836 can be used for a variety of functions. In at least one embodiment, controller 836 can be coupled to any of various other components and systems of vehicle 800, and can be used to control vehicle 800, artificial intelligence of vehicle 800, infotainment and / or other functions of vehicle 800.

[0131] In at least one embodiment, vehicle 800 may include any number of SoCs 804. Each of the SoCs 804 may include, but is not limited to, a central processing unit (“one or more CPUs”) 806, a graphics processing unit (“one or more GPUs”) 808, one or more processors 810, one or more caches 812, one or more accelerators 814, one or more data storage 816, and / or other components and features not shown. In at least one embodiment, one or more SoCs 804 may be used to control vehicle 800 on various platforms and systems. For example, in at least one embodiment, one or more SoCs 804 may be combined with a high-definition (“HD”) map 822 in a system (e.g., the system of vehicle 800), the HD map 822 being accessible from one or more servers via a network interface 824. Figure 8C (Not shown in the image) Get map refresh and / or update.

[0132] In at least one embodiment, one or more CPUs 806 may include CPU clusters or CPU complexes (which may alternatively be referred to herein as “CCPLEX”). In at least one embodiment, one or more CPUs 806 may include multiple cores and / or a secondary (“L2”) cache. For example, in at least one embodiment, one or more CPUs 806 may include eight cores in an intercoupled multiprocessor configuration. In at least one embodiment, one or more CPUs 806 may include four dual-core clusters, each with a dedicated L2 cache (e.g., 2MB L2 cache). In at least one embodiment, one or more CPUs 806 (e.g., CCPLEX) may be configured to support simultaneous cluster operation, such that any combination of clusters of one or more CPUs 806 can be active at any given time.

[0133] In at least one embodiment, one or more CPUs 806 may implement power management functions, including but not limited to one or more of the following features: automatic clock gating of individual hardware modules to conserve dynamic power when idle; clock gating of each core when the core is not actively executing instructions due to executing Wait for Interrupt (“WFI”) / Event Wait (“WFE”) instructions; independent power supply for each core; clock gating of each core cluster when all cores are clock-gated or power-gated; and / or power gating of each core cluster when all cores are power-gated. In at least one embodiment, one or more CPUs 806 may further implement an enhanced algorithm for managing power states, wherein allowed power states and expected wake-up times are specified, and the hardware / microcode determines the optimal power state for cores, clusters, and CCPLEX inputs. In at least one embodiment, the processing core may support a simplified power state input sequence in software, wherein the work is offloaded to the microcode.

[0134] In at least one embodiment, one or more GPUs 808 may include integrated GPUs (or “iGPUs” herein). In at least one embodiment, one or more GPUs 808 may be programmable and efficient for parallel workloads. In at least one embodiment, one or more GPUs 808 may use an enhanced tensor instruction set. In one embodiment, one or more GPUs 808 may include one or more streaming microprocessors, wherein each streaming microprocessor may include a Level 1 (“L1”) cache (e.g., an L1 cache with at least 96 KB of storage capacity), and two or more streaming microprocessors may share an L2 cache (e.g., an L2 cache with 512 KB of storage capacity). In at least one embodiment, one or more GPUs 808 may include at least eight streaming microprocessors. In at least one embodiment, one or more GPUs 808 may use a computation application programming interface (API). In at least one embodiment, one or more GPUs 808 may use one or more parallel computing platforms and / or programming models (e.g., NVIDIA’s CUDA).

[0135] In at least one embodiment, one or more GPU 808s may be power-optimized for optimal performance in automotive and embedded use cases. For example, in one embodiment, one or more GPU 808s may be fabricated on a FinFET (“FinFET”). In at least one embodiment, each streaming microprocessor may include multiple mixed-precision processing cores divided into multiple blocks. For example, but not limited to, 64 PF32 cores and 32 PF64 cores may be divided into four processing blocks. In at least one embodiment, each processing block may be allocated 16 FP32 cores, 8 FP64 cores, 16 INT32 cores, two mixed-precision NVIDIA Tensor cores for deep learning matrix arithmetic, a level-zero (“L0”) instruction cache, a thread bundle scheduler, a dispatch unit, and / or a 64 KB register file. In at least one embodiment, the streaming microprocessor may include independent parallel integer and floating-point data paths to provide efficient execution of workloads that mix computation and addressing operations. In at least one embodiment, the streaming microprocessor may include independent thread scheduling capabilities to enable finer-grained synchronization and cooperation between parallel threads. In at least one embodiment, the streaming microprocessor may include a combined L1 data cache and shared memory unit to improve performance while simplifying programming.

[0136] In at least one embodiment, one or more GPU 808s may include high-bandwidth memory (“HBM”) and / or a 16 GB HBM2 memory subsystem to provide a peak storage bandwidth of approximately 900 GB / s in some examples. In at least one embodiment, in addition to or instead of HBM memory, synchronous graphics random access memory (“SGRAM”), such as graphics double data rate type five synchronous random access memory (“GDDR5”), may be used.

[0137] In at least one embodiment, one or more GPUs 808 may include unified memory technology. In at least one embodiment, address translation service (“ATS”) support can be used to allow one or more GPUs 808 to directly access the page tables of one or more CPUs 806. In at least one embodiment, when one or more GPUs 808 memory management units (“MMUs”) experience a miss, an address translation request can be sent to one or more CPUs 806. In response, in at least one embodiment, one or more CPUs 806 can look up the virtual-physical mapping of the address in their page tables and transfer the translation back to one or more GPUs 808. In at least one embodiment, unified memory technology can allow a single unified virtual address space to be used for the memory of both one or more CPUs 806 and one or more GPUs 808, thereby simplifying the programming of one or more GPUs 808 and porting applications to one or more GPUs 808.

[0138] In at least one embodiment, one or more GPUs 808 may include any number of access counters that can track the frequency with which one or more GPUs 808 access the memory of other processors. In at least one embodiment, one or more access counters can help ensure that memory pages are moved to the physical memory of the processor that accesses the pages most frequently, thereby improving the efficiency of shared memory ranges between processors.

[0139] In at least one embodiment, one or more SoCs 804 may include any number of caches 812, including those described herein. For example, in at least one embodiment, one or more caches 812 may include a Level 3 (“L3”) cache available for one or more CPUs 806 and one or more GPUs 808 (e.g., connected to CPUs 806 and GPUs 808). In at least one embodiment, one or more caches 812 may include a write-back cache that can, for example, track the state of a line using a cache coherence protocol (e.g., MEI, MESI, MSI, etc.). In at least one embodiment, although a smaller cache size may be used, the L3 cache may include 4 MB or more, depending on the embodiment.

[0140] In at least one embodiment, one or more SoCs 804 may include one or more accelerators 814 (e.g., hardware accelerators, software accelerators, or a combination thereof). In at least one embodiment, one or more SoCs 804 may include a hardware acceleration cluster, which may include optimized hardware accelerators and / or large on-chip memory. In at least one embodiment, large on-chip memory (e.g., 4MB of SRAM) enables the hardware acceleration cluster to accelerate neural networks and other computations. In at least one embodiment, the hardware acceleration cluster may be used to supplement one or more GPUs 808 and offload some tasks from one or more GPUs 808 (e.g., freeing up more cycles from one or more GPUs 808 to perform other tasks). In at least one embodiment, one or more accelerators 814 may be used for a target workload (e.g., perceptual, convolutional neural network (“CNN”), recurrent neural network (“RNN”), etc.) that is sufficiently stable to withstand acceleration testing. In at least one embodiment, the CNN may include region-based or region convolutional neural networks (“RCNN”) and fast RCNN (e.g., for object detection) or other types of CNNs.

[0141] In at least one embodiment, one or more accelerators 814 (e.g., a hardware acceleration cluster) may include one or more deep learning accelerators (“DLAs”). One or more DLAs may include, but are not limited to, one or more Tensor Processing Units (“TPUs”) configured to provide an additional 10 trillion operations per second for deep learning applications and inference. In at least one embodiment, the TPU may be an accelerator configured and optimized for performing image processing functions (e.g., for CNNs, RCNNs, etc.). One or more DLAs may be further optimized for specific sets of neural network types and floating-point operations and inference. In at least one embodiment, one or more DLAs are designed to provide higher performance per millimeter than typical general-purpose GPUs and typically significantly outperform CPUs. In at least one embodiment, one or more TPUs may perform several functions, including single-instance convolution functions supporting, for example, INT8, INT16, and FP16 data types for features and weights, as well as post-processor functions. In at least one embodiment, one or more DLAs can execute neural networks, particularly CNNs, quickly and efficiently on processed or unprocessed data for any of the various functions, including, but not limited to: CNNs for object recognition and detection using data from camera sensors; CNNs for distance estimation using data from camera sensors; CNNs for emergency vehicle detection, recognition, and identification using data from microphone 896; CNNs for face recognition and vehicle owner recognition using data from camera sensors; and / or CNNs for safety and / or safety-related events.

[0142] In at least one embodiment, the DLA can perform any function of one or more GPUs 808, and by using an inference accelerator, for example, the designer can target one or more DLAs or one or more GPUs 808 for any function. For example, in at least one embodiment, the designer can concentrate the CNN processing and floating-point operations on one or more DLAs, leaving other functions to one or more GPUs 808 and / or one or more other accelerators 814.

[0143] In at least one embodiment, one or more accelerators 814 (e.g., a hardware acceleration cluster) may include programmable vision accelerators (“PVAs”), which may alternatively be referred to herein as computer vision accelerators. In at least one embodiment, one or more PVAs may be designed and configured to accelerate computer vision algorithms for advanced driver assistance systems (“ADAS”) 838, autonomous driving, augmented reality (“AR”) applications, and / or virtual reality (“VR”) applications. In at least one embodiment, one or more PVAs may strike a balance between performance and flexibility. For example, in at least one embodiment, each of one or more PVAs may include, for example, but not limited to, any number of reduced instruction set computer (“RISC”) cores, direct memory access (“DMA”), and / or any number of vector processors.

[0144] In at least one embodiment, the RISC core can interact with an image sensor (e.g., the image sensor of any camera described herein), an image signal processor, etc. In at least one embodiment, each RISC core may include any number of memories. In at least one embodiment, the RISC core may use any of a variety of protocols, depending on the embodiment. In at least one embodiment, the RISC core may execute a real-time operating system (“RTOS”). In at least one embodiment, the RISC core may be implemented using one or more integrated circuit devices, application-specific integrated circuits (“ASICs”), and / or storage devices. For example, in at least one embodiment, the RISC core may include an instruction cache and / or tightly coupled RAM.

[0145] In at least one embodiment, DMA enables components of the PVA to access system memory independently of one or more CPU 806s. In at least one embodiment, DMA can support any number of features for providing optimization to the PVA, including but not limited to, support for multidimensional addressing and / or circular addressing. In at least one embodiment, DMA can support up to six or more addressing dimensions, which may include, but are not limited to, block width, block height, block depth, horizontal block step, vertical block step, and / or depth step.

[0146] In at least one embodiment, the vector processor may be a programmable processor designed to efficiently and flexibly execute programming for computer vision algorithms and provide signal processing capabilities. In at least one embodiment, the PVA may include a PVA core and two vector processing subsystem partitions. In at least one embodiment, the PVA core may include a processor subsystem, a DMA engine (e.g., two DMA engines), and / or other peripherals. In at least one embodiment, the vector processing subsystem may serve as the main processing engine of the PVA and may include a vector processing unit (“VPU”), an instruction cache, and / or a vector memory (e.g., “VMEM”). In at least one embodiment, the VPU core may include a digital signal processor, such as a Single Instruction Multiple Data (“SIMD”) or Very Long Instruction Word (“VLIW”) digital signal processor. In at least one embodiment, the combination of SIMD and VLIW can improve throughput and speed.

[0147] In at least one embodiment, each vector processor may include an instruction cache and may be coupled to dedicated memory. As a result, in at least one embodiment, each vector processor may be configured to execute independently of other vector processors. In at least one embodiment, vector processors included in a particular PVA may be configured to employ data parallelism. For example, in at least one embodiment, multiple vector processors included in a single PVA may execute the same computer vision algorithm, except on different regions of an image. In at least one embodiment, vector processors included in a particular PVA may execute different computer vision algorithms simultaneously on the same image, or even execute different algorithms on a sequence of images or portions of images. In at least one embodiment, among others, any number of PVAs may be included in the hardware acceleration cluster, and any number of vector processors may be included in each PVA. In at least one embodiment, the PVA may include additional error correction code (“ECC”) memory to enhance overall system security.

[0148] In at least one embodiment, one or more accelerators 814 (e.g., a hardware acceleration cluster) may include an on-chip computer vision network and static random access memory (“SRAM”) for providing high-bandwidth, low-latency SRAM to one or more accelerators 814. In at least one embodiment, the on-chip memory may include at least 4 MB of SRAM, comprising, for example, but not limited to, eight field-configurable memory blocks accessible to both the PVA and DLA. In at least one embodiment, each pair of memory blocks may include an Advanced Peripheral Bus (“APB”) interface, configuration circuitry, a controller, and a multiplexer. In at least one embodiment, any type of memory may be used. In at least one embodiment, the PVA and DLA may access the memory via a backbone providing high-speed access to the memory for both the PVA and DLA. In at least one embodiment, the backbone may include an on-chip computer vision network that interconnects the PVA and DLA to the memory (e.g., using an APB).

[0149] In at least one embodiment, the on-chip computer vision network may include an interface that determines that both the PVA and DLA provide ready and valid signals before transmitting any control signals / addresses / data. In at least one embodiment, the interface may provide separate phases and separate channels for transmitting control signals / addresses / data, as well as bursty communication for continuous data transmission. In at least one embodiment, although other standards and protocols may be used, the interface may conform to the International Organization for Standardization (“ISO”) 26262 or the International Electrotechnical Commission (“IEC”) 61508 standard.

[0150] In at least one embodiment, one or more SoCs 804 may include a real-time eye-tracking hardware accelerator. In at least one embodiment, the real-time eye-tracking hardware accelerator may be used to quickly and efficiently determine the location and extent of an object (e.g., within a world model) to generate real-time visualization simulations for RADAR signal interpretation, for sound propagation synthesis and / or analysis, for simulation of SONAR systems, for general wave propagation simulation, for comparison with LIDAR data for localization and / or other functions, and / or for other purposes.

[0151] In at least one embodiment, one or more accelerators 814 (e.g., a hardware acceleration cluster) have broad applications for autonomous driving. In at least one embodiment, the PVA can be a programmable vision accelerator used in critical processing stages in ADAS and autonomous vehicles. In at least one embodiment, the capabilities of the PVA at low power and low latency are well-matched to algorithmic domains requiring predictable processing. In other words, the PVA performs well in semi-intensive or intensive conventional computations, even on small datasets that may require predictable runtimes with low latency and low power consumption. In at least one embodiment, in an autonomous vehicle, such as vehicle 800, the PVA may be designed to run classic computer vision algorithms, as they are efficient in object detection and integer mathematical operations.

[0152] For example, according to at least one embodiment of the technology, PVA is used to perform computer stereo vision. In at least one embodiment, a semi-global matching-based algorithm may be used in some examples, although this is not intended to be limiting. In at least one embodiment, applications for Level 3-5 autonomous driving use dynamic estimation / stereo matching (e.g., structure recovery from motion, pedestrian recognition, lane detection, etc.) during operation. In at least one embodiment, PVA can perform computer stereo vision functions on input from two monocular cameras.

[0153] In at least one embodiment, the PVA can be used to perform intensive optical flow. For example, in at least one embodiment, the PVA can process raw RADAR data (e.g., using 4D Fast Fourier Transform) to provide processed RADAR data. In at least one embodiment, the PVA is used for time-of-flight depth processing, for example, by processing raw time-of-flight data to provide processed time-of-flight data.

[0154] In at least one embodiment, the DLA can be used to run any type of network to enhance control and driving safety, including, but not limited to, neural networks whose output is used for a confidence score for each object detection. In at least one embodiment, the confidence score can be represented or interpreted as a probability, or as providing a relative “weight” for each detection relative to other detections. In at least one embodiment, the confidence score enables the system to make further decisions about which detections should be considered true positives rather than false positives. In at least one embodiment, the system can set a threshold for the confidence score and only consider detections exceeding the threshold as true positives. In embodiments using an Automatic Emergency Braking (“AEB”) system, false positives would cause the vehicle to automatically perform emergency braking, which is obviously undesirable. In at least one embodiment, a highly confident detection can be considered a trigger for AEB. In at least one embodiment, the DLA can run a neural network for regressing the confidence score value. In at least one embodiment, the neural network may take at least a subset of parameters as its input, such as bounding box size, obtained ground plane estimate (e.g., from another subsystem), and outputs of one or more IMU sensors 866 related to the vehicle orientation, distance, and 3D position estimate of the object obtained from the neural network and / or other sensors (e.g., one or more LiDAR sensors 864 or one or more RADAR sensors 860).

[0155] In at least one embodiment, one or more SoC 804s (e.g., a hardware acceleration cluster) may include one or more data storage devices 816 (e.g., memory). In at least one embodiment, one or more data storage devices 816 may be on-chip memory of one or more SoC 804s, which may store neural networks to be executed on one or more GPUs 808s and / or DLAs. In at least one embodiment, one or more data storage devices 816 may have a sufficiently large capacity to store multiple instances of the neural network for redundancy and security. In at least one embodiment, one or more data storage devices 812 may include L2 or L3 caches.

[0156] In at least one embodiment, one or more SoCs 804 may include any number of processors 810 (e.g., embedded processors). In at least one embodiment, one or more processors 810 may include a startup and power management processor, which may be a dedicated processor and subsystem for handling startup power and management functions, as well as associated security implementations. In at least one embodiment, the startup and power management processor may be part of a startup sequence of one or more SoCs 804s and may provide runtime power management services. In at least one embodiment, the startup power and management processor may provide clock and voltage programming, assist system low-power state transitions, thermal and temperature sensor management of one or more SoCs 804s, and / or power state management of one or more SoCs 804s. In at least one embodiment, each temperature sensor may be implemented with its output frequency proportional to temperature, and one or more SoCs 804s may use the ring oscillator to detect the temperature of one or more CPUs 806s, one or more GPUs 808s, and / or one or more accelerators 814s. In at least one embodiment, if it is determined that the temperature exceeds a threshold, the startup and power management processor may enter a temperature fault routine and place one or more SoCs 804s into a lower power state and / or place the vehicle 800 into a driver’s safe stopping pattern (e.g., bring the vehicle 800 to a safe stop).

[0157] In at least one embodiment, one or more processors 810 may further include a set of embedded processors that can be used as an audio processing engine. In at least one embodiment, the audio processing engine may be an audio subsystem capable of providing full hardware support for multi-channel audio through multiple interfaces and a wide and flexible range of audio I / O interfaces. In at least one embodiment, the audio processing engine is a dedicated processor core with a digital signal processor with dedicated RAM.

[0158] In at least one embodiment, one or more processors 810 may further include an always-on processor engine. In at least one embodiment, the automatic processing engine may provide the necessary hardware features to support low-power sensor management and wake-up use cases. In at least one embodiment, the processor on the always-on processor engine may include, but is not limited to, a processor core, tightly coupled RAM, support for peripherals (e.g., timers and interrupt controllers), various I / O controller peripherals, and routing logic.

[0159] In at least one embodiment, one or more processors 810 may further include a security cluster engine, which includes, but is not limited to, a dedicated processor subsystem for handling security management of automotive applications. In at least one embodiment, the security cluster engine may include, but is not limited to, two or more processor cores, tightly coupled RAM, supporting peripherals (e.g., timers, interrupt controllers, etc.) and / or routing logic. In a secure mode, in at least one embodiment, the two or more cores may operate in lockstep mode and may be used as a single core with comparison logic for detecting any differences between their operations. In at least one embodiment, one or more processors 810 may further include a real-time camera engine, which may include, but is not limited to, a dedicated processor subsystem for handling real-time camera management. In at least one embodiment, one or more processors 810 may further include a high dynamic range signal processor, which may include, but is not limited to, an image signal processor, which is a hardware engine as part of the camera processing pipeline.

[0160] In at least one embodiment, one or more processors 810 may include a video image synthesizer, which may be a processing block (e.g., implemented on a microprocessor) that implements video post-processing functions required by the video playback application to produce the final image for the player window. In at least one embodiment, the video image synthesizer may perform lens distortion correction on one or more wide-angle cameras 870, one or more surround cameras 874, and / or one or more cabin monitoring camera sensors. In at least one embodiment, preferably, the cabin monitoring camera sensors are monitored by a neural network running on another instance of the SoC 804, the neural network being configured to recognize cabin events and respond accordingly. In at least one embodiment, the cabin system may perform, but is not limited to, lip reading to activate cellular service and make phone calls, instruct emails, change the vehicle's destination, activate or change the vehicle's infotainment system and settings, or provide voice-activated web browsing. In at least one embodiment, certain functions are available to the driver when the vehicle is operating in autonomous mode, and are otherwise disabled.

[0161] In at least one embodiment, the video image synthesizer may include enhanced temporal denoising for simultaneous spatial and temporal denoising. For example, in at least one embodiment, when motion occurs in the video, denoising appropriately weights spatial information, thereby reducing the weight of information provided by adjacent frames. In at least one embodiment, when the image or a portion of the image does not contain motion, temporal denoising performed by the video image synthesizer may use information from previous images to reduce noise in the current image.

[0162] In at least one embodiment, the video image compositor can also be configured to perform stereoscopic correction on the input stereo lens frames. In at least one embodiment, when using an operating system desktop, the video image compositor can also be used for user interface compositing and does not require one or more GPUs 808 to continuously render new surfaces. In at least one embodiment, when one or more GPUs 808 are powered and actively performing 3D rendering, the video image compositor can be used to offload one or more GPUs 808 to improve performance and responsiveness.

[0163] In at least one embodiment, one or more SoCs of SoC 804 may further include a Mobile Industrial Processor Interface (“MIPI”) camera serial interface, a high-speed interface, and / or a video input block that can be used for receiving video and input from a camera and associated pixel input functions. In at least one embodiment, one or more SoCs of SoC 804 may further include an input / output controller that may be software-controlled and can be used to receive I / O signals not assigned to a specific role.

[0164] In at least one embodiment, one or more SoCs of SoC 804 may further include extensive peripheral interfaces to enable communication with peripheral devices, audio encoders / decoders (“codecs”), power management and / or other devices. One or more SoCs of SoC 804 may be used to process data from (e.g., via gigabit multimedia serial links and Ethernet connections) cameras, sensors (e.g., one or more LiDAR sensors 864, one or more RADAR sensors 860, etc., which may be connected via Ethernet), data from bus 802 (e.g., vehicle 800 speed, steering wheel position, etc.), data from one or more GNSS sensors 858 (e.g., via Ethernet bus or CAN bus connections), etc. In at least one embodiment, one or more SoCs of SoC 804 may further include a dedicated high-performance mass storage controller, which may include its own DMA engine and may be used to free one or more CPUs of SoC 806 from routine data management tasks.

[0165] In at least one embodiment, one or more SoCs 804 can be an end-to-end platform with a flexible architecture spanning automation levels 3-5, providing a comprehensive functional safety architecture that leverages and effectively utilizes computer vision and ADAS technologies to achieve diversity and redundancy. This provides a platform offering a flexible and reliable driving software stack as well as deep learning tools. In at least one embodiment, one or more SoCs 804 can be faster, more reliable, and even more energy and space efficient than conventional systems. For example, in at least one embodiment, one or more accelerators 814, when combined with one or more CPUs 806, one or more GPUs 808, and one or more data storage devices 816, can provide a fast and efficient platform for Level 3-5 autonomous vehicles.

[0166] In at least one embodiment, the computer vision algorithm can be executed on a CPU, which can be configured using a high-level programming language (such as C) to execute multiple processing algorithms on a variety of visual data. However, in at least one embodiment, the CPU typically cannot meet the performance requirements of many computer vision applications, such as performance requirements related to execution time and power consumption. In at least one embodiment, many CPUs cannot execute complex object detection algorithms in real time, which are used in automotive ADAS applications and practical Level 3-5 autonomous vehicles.

[0167] The embodiments described herein allow multiple neural networks to be executed simultaneously and / or sequentially, and allow the results to be combined to achieve Level 3-5 autonomous driving capabilities. For example, in at least one embodiment, a CNN executed on a DLA or discrete GPU (e.g., one or more GPU 820s) may include text and word recognition, thereby allowing a supercomputer to read and understand traffic signs, including signs for which the neural network has not yet been specifically trained. In at least one embodiment, the DLA may also include a neural network capable of recognizing, interpreting, and providing semantic understanding of symbols, and passing this semantic understanding to a path planning module running on a CPU Complex.

[0168] In at least one embodiment, for drives of levels 3, 4, or 5, multiple neural networks can run simultaneously. For example, in at least one embodiment, a warning sign consisting of a light bulb and the warning sign “Caution: flashing lights indicate icy conditions” can be interpreted independently or jointly by multiple neural networks. In at least one embodiment, the sign itself can be recognized as a traffic sign by a first deployed neural network (e.g., a trained neural network), and the text “flashing lights indicate icy conditions” can be interpreted by a second deployed neural network, which informs the vehicle’s path planning software (preferably executed on a CPU Complex) that icing conditions exist when flashing lights are detected. In at least one embodiment, flashing lights can be identified by operating a third deployed neural network across multiple frames, informing the vehicle’s path planning software of the presence (or absence) of flashing lights. In at least one embodiment, all three neural networks can run simultaneously, for example within a DLA and / or on one or more GPU 808s.

[0169] In at least one embodiment, the CNN for facial recognition and vehicle owner identification can use data from camera sensors to identify the presence of an authorized driver and / or the owner of vehicle 800. In at least one embodiment, a normally open sensor processor engine can be used to unlock the vehicle when the owner approaches the driver's door and turns on the lights, and, in security mode, can be used to disable the vehicle when the owner leaves it. In this way, one or more SoCs 804 provide protection against theft and / or carjacking.

[0170] In at least one embodiment, the CNN for emergency vehicle detection and identification can use data from microphone 896 to detect and identify emergency vehicle sirens. In at least one embodiment, one or more SoCs 804 use the CNN to classify environmental and urban sounds, as well as visual data. In at least one embodiment, the CNN running on DLA is trained to identify the relative approach speed of emergency vehicles (e.g., by using the Doppler effect). In at least one embodiment, the CNN can also be trained to identify emergency vehicles in the area where the vehicle is operating, as identified by one or more GNSS sensors 858. In at least one embodiment, when operating in Europe, the CNN will seek to detect European sirens, while when operating in the United States, the CNN will seek to identify only North American sirens. In at least one embodiment, once an emergency vehicle is detected, a control program can be used, with the assistance of one or more ultrasonic sensors 862, to execute emergency vehicle safety routines, slow the vehicle, pull the vehicle to the side of the road, stop, and / or leave the vehicle idle until the emergency vehicle passes.

[0171] In at least one embodiment, vehicle 800 may include one or more CPUs 818 (e.g., one or more discrete CPUs or one or more dCPUs) that may be coupled to one or more SoCs 804 via high-speed interconnects (e.g., PCIe). In at least one embodiment, one or more CPUs 818 may include x86 processors. For example, one or more CPUs 818 may be used to perform any of the various functions, such as arbitrating the results of potential inconsistencies between ADAS sensors and one or more SoCs 804, and / or monitoring the status and health of one or more monitoring controllers 836 and / or on-chip information systems (“information SoCs”) 830.

[0172] In at least one embodiment, vehicle 800 may include one or more GPUs 820 (e.g., one or more discrete GPUs or one or more dGPUs) that may be coupled to one or more SoCs 804 via a high-speed interconnect (e.g., NVIDIA's NVLINK). In at least one embodiment, one or more GPUs 820 may provide additional artificial intelligence capabilities, such as by executing redundant and / or different neural networks, and may be used to train and / or update the neural networks based at least in part on inputs from sensors of vehicle 800 (e.g., sensor data).

[0173] In at least one embodiment, vehicle 800 may further include a network interface 824, which may include, but is not limited to, one or more wireless antennas 826 (e.g., one or more wireless antennas 826 for different communication protocols, such as cellular antennas, Bluetooth antennas, etc.). In at least one embodiment, network interface 824 may be used to enable wireless connectivity with other vehicles and / or computing devices (e.g., passenger client devices) via the Internet with a cloud (e.g., employing servers and / or other network devices). In at least one embodiment, for communication with other vehicles, a direct link and / or an indirect link (e.g., via a network and the Internet) may be established between vehicle 800 and other vehicles. In at least one embodiment, a vehicle-to-vehicle communication link may be used to provide a direct link. In at least one embodiment, the vehicle-to-vehicle communication link may provide vehicle 800 with information about vehicles near vehicle 800 (e.g., vehicles in front, to the side, and / or behind vehicle 800). In at least one embodiment, the foregoing functionality may be part of a cooperative adaptive cruise control function of vehicle 800.

[0174] In at least one embodiment, network interface 824 may include a System-on-Chip (SoC) that provides modulation and demodulation functions and enables one or more controllers 836 to communicate over a wireless network. In at least one embodiment, network interface 824 may include a radio frequency (RF) front-end for up-conversion from baseband to RF and down-conversion from RF to baseband. In at least one embodiment, frequency conversion may be performed in any technically feasible manner. For example, frequency conversion may be performed using known processes and / or using a superheterodyne process. In at least one embodiment, the RF front-end functionality may be provided by a separate chip. In at least one embodiment, the network interface may include wireless functions for communication via LTE, WCDMA, UMTS, GSM, CDMA2000, Bluetooth, Bluetooth LE, Wi-Fi, Z-Wave, ZigBee, LoRaWAN, and / or other wireless protocols.

[0175] In at least one embodiment, vehicle 800 may further include one or more data storage units 828, which may include, but are not limited to, off-chip (e.g., one or more SoC 804) storage. In at least one embodiment, one or more data storage units 828 may include, but are not limited to, one or more storage elements, including RAM, SRAM, dynamic random access memory (“DRAM”), video random access memory (“VRAM”), flash memory, hard disk and / or other components and / or devices capable of storing at least one bit of data.

[0176] In at least one embodiment, the vehicle 800 may further include one or more GNSS sensors 858 (e.g., GPS and / or auxiliary GPS sensors) to assist in map creation, perception, occupancy raster generation, and / or path planning functions. In at least one embodiment, any number of GNSS sensors 858 may be used, including, for example but not limited to, GPS sensors connected to a serial interface (e.g., RS-232) bridge using a USB connector with Ethernet.

[0177] In at least one embodiment, vehicle 800 may further include one or more RADAR sensors 860. One or more RADAR sensors 860 can be used by vehicle 800 for remote vehicle detection, even in dark and / or inclement weather conditions. In at least one embodiment, the RADAR functional safety level may be ASIL B. One or more RADAR sensors 860 may use a CAN bus and / or bus 802 (e.g., to transmit data generated by one or more RADAR sensors 860) for control and access to object tracking data, and in some examples, may access an Ethernet channel to access raw data. In at least one embodiment, a wide variety of RADAR sensor types can be used. For example, but not limited to, one or more of the RADAR sensors 860 may be suitable for front, rear, and side RADAR use. In at least one embodiment, one or more RADAR sensors 860 are pulse Doppler RADAR sensors.

[0178] In at least one embodiment, one or more RADAR sensors 860 may include different configurations, such as long-range with a narrow field of view, short-range with a wide field of view, short-range side coverage, etc. In at least one embodiment, the long-range RADAR can be used for adaptive cruise control functions. In at least one embodiment, the long-range RADAR system can provide a wide field of view achieved through two or more independent scans (e.g., within a 250m range). In at least one embodiment, one or more RADAR sensors 860 can help distinguish between stationary and moving objects and can be used by the ADAS system 838 for emergency braking assistance and forward collision warning. In at least one embodiment, one or more sensors 860 included in the long-range RADAR system may include, but are not limited to, a monostatic multimode RADAR with multiple (e.g., six or more) fixed RADAR antennas and high-speed CAN and FlexRay interfaces. In at least one embodiment, having six antennas, with the four central antennas creating a focused beammap designed to record the environment around the vehicle 800 at a high speed while minimizing traffic interference from adjacent lanes. In at least one embodiment, the other two antennas can expand the field of view, thereby enabling rapid detection of lanes entering or leaving the vehicle 800.

[0179] In at least one embodiment, as an example, a mid-range RADAR system may include, for example, a range of up to 160m (front) or 80m (rear), and a field of view of up to 42 degrees (front) or 150 degrees (rear). In at least one embodiment, a short-range RADAR system may include, but is not limited to, any number of RADAR sensors 860 designed to be mounted at both ends of the rear bumper. When mounted at both ends of the rear bumper, in at least one embodiment, the RADAR sensor system may generate two beams that continuously monitor the blind spots at and near the rear of the vehicle. In at least one embodiment, the short-range RADAR system may be used in ADAS system 838 for blind spot detection and / or lane change assistance.

[0180] In at least one embodiment, the vehicle 800 may further include one or more ultrasonic sensors 862. In at least one embodiment, one or more ultrasonic sensors 862, which may be positioned at the front, rear, and / or sides of the vehicle 800, may be used for parking assistance and / or creating and updating occupancy detectors. In at least one embodiment, a wide variety of ultrasonic sensors 862 may be used, and different ultrasonic sensors 862 may be used for different detection ranges (e.g., 2.5m, 4m). In at least one embodiment, the ultrasonic sensors 862 may operate at the ASIL B functional safety level.

[0181] In at least one embodiment, vehicle 800 may include one or more LiDAR sensors 864. The one or more LiDAR sensors 864 may be used for object and pedestrian detection, emergency braking, collision avoidance, and / or other functions. In at least one embodiment, the one or more LiDAR sensors 864 may be of functional safety level ASIL B. In at least one embodiment, vehicle 800 may include multiple (e.g., two, four, six, etc.) LiDAR sensors 864 that can use Ethernet (e.g., providing data to a Gigabit Ethernet switch).

[0182] In at least one embodiment, one or more LiDAR sensors 864 may be able to provide a list of objects and their distances for a 360-degree field of view. In at least one embodiment, one or more commercially available LiDAR sensors 864 may, for example, have an advertising range of approximately 100m, an accuracy of 2cm-3cm, and support a 100Mbps Ethernet connection. In at least one embodiment, one or more non-protruding LiDAR sensors 864 may be used. In such embodiments, one or more LiDAR sensors 864 may be implemented as small devices embedded in the front, rear, sides, and / or corners of a vehicle 800. In at least one embodiment, one or more LiDAR sensors 864, in such embodiments, can provide a horizontal field of view of up to 120 degrees and a vertical field of view of 35 degrees, even for objects with low reflectivity, and have a range of 200m. In at least one embodiment, one or more forward-facing LiDAR sensors 864 may be configured for a horizontal field of view between 45 degrees and 135 degrees.

[0183] In at least one embodiment, LIDAR technology (such as 3D flash LIDAR) may also be used. 3D flash LIDAR uses a laser flash as a transmission source to illuminate approximately 200m around the vehicle 800. In at least one embodiment, the flash LIDAR unit includes, but is not limited to, a receiver that records the laser pulse propagation time and reflected light on each pixel, which in turn corresponds to the range from the vehicle 800 to the object. In at least one embodiment, flash LIDAR can allow the generation of highly accurate and distortion-free images of the surrounding environment using each laser flash. In at least one embodiment, four flash LIDAR sensors may be deployed, one on each side of the vehicle 800. In at least one embodiment, the 3D flash LIDAR system includes, but is not limited to, a solid-state 3D line-of-sight array LIDAR camera with no moving parts other than a fan (e.g., a non-scanning LIDAR device). In at least one embodiment, the flash LIDAR device can use a 5-nanosecond Class I (eye-safe) laser pulse per frame and can capture reflected laser light in the form of a 3D ranging point cloud and co-registered intensity data.

[0184] In at least one embodiment, vehicle 800 may further include one or more IMU sensors 866. In at least one embodiment, one or more IMU sensors 866 may be located at the center of the rear axle of vehicle 800. In at least one embodiment, one or more IMU sensors 866 may include, for example, but not limited to, one or more accelerometers, one or more magnetometers, one or more gyroscopes, one or more magnetic compasses, and / or other sensor types. In at least one embodiment, for example in a six-axis application, one or more IMU sensors 866 may include, but are not limited to, accelerometers and gyroscopes. In at least one embodiment, for example in a nine-axis application, one or more IMU sensors 866 may include, but are not limited to, accelerometers, gyroscopes, and magnetometers.

[0185] In at least one embodiment, one or more IMU sensors 866 may be implemented as a miniature, high-performance GPS-assisted inertial navigation system (“GPS / INS”) combining a microelectromechanical system (“MEMS”) inertial sensor, a high-sensitivity GPS receiver, and an advanced Kalman filtering algorithm to provide position, velocity, and attitude estimations; in at least one embodiment, one or more IMU sensors 866 may enable vehicle 800 to estimate heading without input from a magnetic sensor obtained by directly observing and correlating velocity changes from GPS to one or more IMU sensors 866. In at least one embodiment, one or more IMU sensors 866 and one or more GNSS sensors 858 may be combined in a single integrated unit.

[0186] In at least one embodiment, vehicle 800 may include one or more microphones 896 placed inside and / or around vehicle 800. In at least one embodiment, in addition, one or more microphones 896 may be used for emergency vehicle detection and identification.

[0187] In at least one embodiment, vehicle 800 may further include any number of camera types, including one or more stereo cameras 868, one or more wide-angle cameras 870, one or more infrared cameras 872, one or more surround cameras 874, one or more long-range cameras 898, one or more mid-range cameras 876, and / or other camera types. In at least one embodiment, the cameras can be used to capture image data around the entire perimeter of vehicle 800. In at least one embodiment, the type of camera used depends on vehicle 800. In at least one embodiment, any combination of camera types can be used to provide the necessary coverage around vehicle 800. In at least one embodiment, the number of cameras deployed may vary depending on the embodiment. For example, in at least one embodiment, vehicle 800 may include six cameras, seven cameras, ten cameras, twelve cameras, or other numbers of cameras. In at least one embodiment, the cameras may be, by way of example, but not limited to, supporting Gigabit Multimedia Serial Link (“GMSL”) and / or Gigabit Ethernet. In at least one embodiment, references previously made herein... Figure 8A and Figure 8B Each camera can be described in more detail.

[0188] In at least one embodiment, the vehicle 800 may further include one or more vibration sensors 842. In at least one embodiment, the one or more vibration sensors 842 may measure vibrations of components of the vehicle 800 (e.g., axles). For example, in at least one embodiment, changes in vibration may indicate changes in road surface conditions. In at least one embodiment, when two or more vibration sensors 842 are used, differences between vibrations may be used to determine road surface friction or slippage (e.g., when there is a vibration difference between a power drive axle and a free-rotating axle).

[0189] In at least one embodiment, vehicle 800 may include ADAS system 838. ADAS system 838 may include, but is not limited to, SoC. In at least one embodiment, ADAS system 838 may include, but is not limited to, any number of autonomous / adaptive / automatic cruise control (“ACC”) systems, cooperative adaptive cruise control (“CACC”) systems, forward collision warning (“FCW”) systems, automatic emergency braking (“AEB”) systems, lane departure warning (“LDW”) systems, lane keeping assist (“LKA”) systems, blind spot warning (“BSW”) systems, rear cross traffic warning (“RCTW”) systems, collision warning (“CW”) systems, lane centering (“LC”) systems, and / or other systems, features, and / or functions, and combinations thereof.

[0190] In at least one embodiment, the ACC system may use one or more RADAR sensors 860, one or more LIDAR sensors 864, and / or any number of cameras. In at least one embodiment, the ACC system may include a longitudinal ACC system and / or a lateral ACC system. In at least one embodiment, the longitudinal ACC system monitors and controls the distance to the vehicle immediately preceding the adjacent vehicle 800 and automatically adjusts the speed of the vehicle 800 to maintain a safe distance from the vehicle ahead. In at least one embodiment, the lateral ACC system performs distance holding and suggests that the vehicle 800 change lanes when necessary. In at least one embodiment, the lateral ACC is associated with other ADAS applications, such as LC and CW.

[0191] In at least one embodiment, the CACC system uses information from other vehicles, which may be received from other vehicles via network interface 824 and / or one or more wireless antennas 826 via a wireless link or indirectly via a network connection (e.g., via the Internet). In at least one embodiment, the direct link may be provided by a vehicle-to-vehicle (“V2V”) communication link, while the indirect link may be provided by an infrastructure-to-vehicle (“I2V”) communication link. Typically, the V2V communication concept provides information about the vehicle immediately preceding it (e.g., a vehicle immediately in front of vehicle 800 and in the same lane as it), while the I2V communication concept provides information about traffic further ahead. In at least one embodiment, the CACC system may include one or both of the I2V and V2V information sources. In at least one embodiment, given information about vehicles preceding vehicle 800, the CACC system can be more reliable and has the potential to improve traffic flow smoothness and reduce road congestion.

[0192] In at least one embodiment, the FCW system is designed to warn the driver of danger so that the driver can take corrective action. In at least one embodiment, the FCW system uses a forward-facing camera and / or one or more RADAR sensors 860, coupled to a dedicated processor, DSP, FPGA, and / or ASIC, electrically coupled to driver feedback, such as a display, speaker, and / or vibration components. In at least one embodiment, the FCW system can provide warnings, for example, in the form of audible, visual, haptic, and / or rapid braking pulses.

[0193] In at least one embodiment, the AEB system detects an impending forward collision with another vehicle or other object and can automatically apply brakes if the driver does not take corrective action within a specified time or distance parameter. In at least one embodiment, the AEB system may use one or more forward-facing cameras and / or one or more RADAR sensors 860 coupled to a dedicated processor, DSP, FPGA, and / or ASIC. In at least one embodiment, when the AEB system detects a hazard, it typically first warns the driver to take corrective action to avoid a collision, and if the driver does not take corrective action, the AEB system may automatically apply brakes to attempt to prevent or at least mitigate the effects of the predicted collision. In at least one embodiment, the AEB system may include techniques such as dynamic braking to support and / or brakes for impending collisions.

[0194] In at least one embodiment, when vehicle 800 crosses lane markings, the LDW system provides visual, auditory, and / or tactile warnings, such as steering wheel or seat vibrations, to alert the driver. In at least one embodiment, the LDW system is inactive when the driver indicates intentional lane departure, such as by activating turn signals. In at least one embodiment, the LDW system may use a front-facing camera coupled to a dedicated processor, DSP, FPGA, and / or ASIC, which is electrically coupled to driver feedback such as a display, speaker, and / or vibration components. In at least one embodiment, the LKA system is a variant of the LDW system. If vehicle 800 begins to leave the lane, the LKA system provides steering input or braking to correct vehicle 800.

[0195] In at least one embodiment, the BSW system detects and warns the driver of a vehicle in the blind spot. In at least one embodiment, the BSW system can provide visual, auditory, and / or tactile alerts to indicate that merging or changing lanes is unsafe. In at least one embodiment, the BSW system can provide additional warnings when the driver uses the turn signal. In at least one embodiment, the BSW system can use one or more rear-facing cameras and / or one or more RADAR sensors 860 coupled to a dedicated processor, DSP, FPGA, and / or ASIC, electrically coupled to driver feedback, such as a display, speaker, and / or vibration assembly.

[0196] In at least one embodiment, the RCTW system can provide visual, auditory, and / or tactile notifications when an object is detected outside the range of the rear camera while the vehicle 800 is reversing. In at least one embodiment, the RCTW system includes an AEB system to ensure the vehicle brakes to avoid a collision. In at least one embodiment, the RCTW system may use one or more rear-facing RADAR sensors 860 coupled to a dedicated processor, DSP, FPGA, and / or ASIC, which are electrically coupled to driver feedback such as a display, speaker, and / or vibration assembly.

[0197] In at least one embodiment, conventional ADAS systems may be prone to generating false alarms, which can be annoying and distracting to the driver, but are generally not catastrophic because conventional ADAS systems warn the driver and allow the driver to determine whether a safe situation truly exists and take appropriate action. In at least one embodiment, in the event of conflicting results, the vehicle 800 itself decides whether to follow the result of the primary computer or the secondary computer (e.g., the first controller 836 or the second controller 836). For example, in at least one embodiment, ADAS system 838 may be a backup and / or auxiliary computer for providing perception information to a backup computer rationality module. In at least one embodiment, the backup computer rationality monitor may run redundant software on hardware components to detect faults in perception and dynamic driving tasks. In at least one embodiment, the output from ADAS system 838 may be provided to a monitoring MCU. In at least one embodiment, if the outputs from the primary computer and the auxiliary computer conflict, the monitoring MCU decides how to reconcile the conflict to ensure safe operation.

[0198] In at least one embodiment, the master computer may be configured to provide a confidence score to the supervisory MCU to indicate the master computer's confidence in the selected result. In at least one embodiment, if the confidence score exceeds a threshold, the supervisory MCU may follow the master computer's instructions regardless of whether the auxiliary computer provides conflicting or inconsistent results. In at least one embodiment, if the confidence score does not meet the threshold, and if the master computer and the auxiliary computer indicate different results (e.g., conflict), the supervisory MCU may arbitrate between the computers to determine the appropriate result.

[0199] In at least one embodiment, the supervisory MCU may be configured to run a neural network trained and configured to determine, at least in part, the conditions under which the auxiliary computer provides a false alarm based on outputs from both the host computer and the auxiliary computer. In at least one embodiment, the neural network in the supervisory MCU may learn when the output of the auxiliary computer can be trusted and when it cannot. For example, in at least one embodiment, when the auxiliary computer is a RADAR-based FCW system, the neural network in the supervisory MCU may learn when the FCW system recognizes a metallic object that is not actually dangerous, such as a drain grating or manhole cover that would trigger an alarm. In at least one embodiment, when the auxiliary computer is a camera-based LDW system, the neural network in the supervisory MCU may learn to override the LDW when a cyclist or pedestrian is present and lane departure is actually the safest operation. In at least one embodiment, the supervisory MCU may include at least one of a DLA or GPU suitable for running a neural network with associated memory. In at least one embodiment, the supervisory MCU may include and / or be included as a component of one or more SoC 804s.

[0200] In at least one embodiment, the ADAS system 838 may include an auxiliary computer that performs ADAS functions using conventional computer vision rules. In at least one embodiment, the auxiliary computer may use classic computer vision rules (if-then), and the presence of a neural network in the supervisory MCU can improve reliability, security, and performance. For example, in at least one embodiment, diverse implementations and intentional non-identity make the entire system more fault-tolerant, especially for failures caused by software (or software-hardware interface) functionality. For example, in at least one embodiment, if a software vulnerability or bug exists in the software running on the host computer, and different software code running on the auxiliary computer provides the same overall result, the supervisory MCU can more confidently assume that the overall result is correct and that the vulnerability in the software or hardware on the host computer will not lead to a significant error.

[0201] In at least one embodiment, the output of the ADAS system 838 can be input to the perception module and / or the dynamic driving task module of the host computer. For example, in at least one embodiment, if the ADAS system 838 indicates a forward collision warning due to an object directly ahead, the perception block can use this information when identifying the object. In at least one embodiment, as described herein, the assistance computer can have its own neural network trained to reduce the risk of false alarms.

[0202] In at least one embodiment, vehicle 800 may further include an infotainment SoC 830 (e.g., an in-vehicle infotainment system (IVI)). Although shown and described as an SoC, in at least one embodiment, infotainment system 830 may not be an SoC and may include, but is not limited to, two or more discrete components. In at least one embodiment, infotainment SoC 830 may include, but is not limited to, a combination of hardware and software that can be used to provide audio (e.g., music, personal digital assistant, navigation instructions, news, radio, etc.), video (e.g., television, movies, streaming media, etc.), telephone (e.g., hands-free calling), network connectivity (e.g., LTE, WiFi, etc.) and / or information services (e.g., navigation system, rear parking assist, radio data system, vehicle-related information such as fuel level, total coverage distance, brake fuel level, fuel level, door opening / closing, air filter information, etc.) to vehicle 800. For example, the infotainment SoC 830 may include a radio, disk player, navigation system, video player, USB and Bluetooth connectivity, automobile, in-vehicle entertainment system, WiFi, steering wheel audio controls, hands-free voice control, head-up display (“HUD”), HMI display 834, telematics device, control panel (e.g., for controlling and / or interacting with various components, features and / or systems) and / or other components. In at least one embodiment, the infotainment SoC 830 may further be used to provide information (e.g., visual and / or auditory) to users of the vehicle, such as information from ADAS system 838, autonomous driving information (such as planned vehicle maneuvers), trajectory, surrounding environment information (e.g., intersection information, vehicle information, road information, etc.) and / or other information.

[0203] In at least one embodiment, the infotainment SoC 830 may include any number and type of GPU functionality. In at least one embodiment, the infotainment SoC 830 may communicate with other devices, systems, and / or components of the vehicle 800 via bus 802 (e.g., CAN bus, Ethernet, etc.). In at least one embodiment, the infotainment SoC 830 may be coupled to a monitoring MCU, enabling the GPU of the infotainment system to perform some autonomous driving functions in the event of a failure of the main controller 836 (e.g., the main computer and / or backup computer of the vehicle 800). In at least one embodiment, the infotainment SoC 830 may enable the vehicle 800 to enter a driver-to-safe-stop mode, as described herein.

[0204] In at least one embodiment, vehicle 800 may further include instrument panel 832 (e.g., digital instrument panel, electronic instrument panel, digital instrument control panel, etc.). In at least one embodiment, instrument panel 832 may include, but is not limited to, controllers and / or supercomputers (e.g., discrete controllers or supercomputers). In at least one embodiment, instrument panel 832 may include, but is not limited to, any number and combination of a set of instruments, such as speedometer, fuel level, oil pressure, tachometer, odometer, turn indicator, shift position indicator, one or more seatbelt warning lights, one or more parking brake warning lights, one or more engine malfunction lights, auxiliary restraint system (e.g., airbag) information, lighting controls, safety system controls, navigation information, etc. In some examples, information may be displayed and / or shared between infotainment SoC 830 and instrument panel 832. In at least one embodiment, instrument panel 832 may be included as part of infotainment SoC 830, or vice versa.

[0205] In at least one embodiment, vehicle 800 may include a wireless network, such as the MIMO network described above. In at least one embodiment, control data may be transmitted within a portion of a time window having an exclusive window with time slots.

[0206] Figure 8D It is based on at least one embodiment in a cloud-based server and Figure 8AA diagram of a system 876 for communication between autonomous vehicles 800. In at least one embodiment, system 876 may include, but is not limited to, one or more servers 878, one or more networks 890, and any number and type of vehicles, including vehicle 800. One or more servers 878 may include, but are not limited to, multiple GPUs 884(A)-884(H) (collectively referred to herein as GPU 884), PCIe switches 882(A)-882(D) (collectively referred to herein as PCIe switch 882), and / or CPUs 880(A)-880(B) (collectively referred to herein as CPU 880). GPU 884, CPU 880, and PCIe switch 882 may be interconnected with high-speed interconnects, such as, but not limited to, NVLink interface 888 developed by NVIDIA and / or PCIe connection 886. GPU 884 is connected via NVLink and / or NVSwitchSoC, and GPU 884 and PCIe switch 882 are connected via PCIe interconnect. In at least one embodiment, although eight GPUs 884, two CPUs 880, and four PCIe switches 882 are shown, this is not intended to be limiting. In at least one embodiment, each of one or more servers 878 may include, but is not limited to, any combination of any number of GPUs 884, CPUs 880, and / or PCIe switches 882. For example, in at least one embodiment, one or more servers 878 may each include eight, sixteen, thirty-two, and / or more GPUs 884.

[0207] In at least one embodiment, one or more servers 878 may receive image data representing an image from a vehicle via one or more networks 890, the image showing unexpected or changed road conditions, such as recently commenced roadworks. In at least one embodiment, one or more servers 878 may transmit a neural network 892, an updated neural network 892, and / or map information 894, including but not limited to information about traffic and road conditions, to the vehicle via one or more networks 890. In at least one embodiment, updates to the map information 894 may include, but are not limited to, updates to an HD map 822, such as information about construction sites, potholes, sidewalks, floods, and / or other obstacles. In at least one embodiment, the neural network 892, the updated neural network 892, and / or map information 894 may be generated from new training and / or experience represented by data received from any number of vehicles in the environment, and / or at least based on training performed in a data center (e.g., using one or more servers 878 and / or other servers).

[0208] In at least one embodiment, one or more servers 878 may be used to train a machine learning model (e.g., a neural network) at least in part based on training data. In at least one embodiment, the training data may be generated by the vehicle, and / or may be generated in a simulation (e.g., using a game engine). In at least one embodiment, any amount of training data is labeled (e.g., where the associated neural network benefits from supervised learning) and / or undergoes other preprocessing. In at least one embodiment, no amount of training data is labeled and / or preprocessed (e.g., where the associated neural network does not require supervised learning). In at least one embodiment, once the machine learning model is trained, the machine learning model may be used by the vehicle (e.g., transmitted to the vehicle via one or more networks 890), and / or the machine learning model may be used by one or more servers 878 to remotely monitor the vehicle.

[0209] In at least one embodiment, one or more servers 878 may receive data from a vehicle and apply the data to state-of-the-art real-time neural networks for real-time intelligent inference. In at least one embodiment, one or more servers 878 may include a deep learning supercomputer and / or a dedicated AI computer powered by one or more GPUs 884, such as the DGX and DGX Station machines developed by NVIDIA. However, in at least one embodiment, one or more servers 878 may include a deep learning infrastructure in a data center using CPU power.

[0210] In at least one embodiment, the deep learning infrastructure of one or more servers 878 may be capable of fast, real-time inference and can use this capability to assess and verify the health of the processor, software, and / or associated hardware in vehicle 800. For example, in at least one embodiment, the deep learning infrastructure may receive periodic updates from vehicle 800, such as image sequences and / or objects located by vehicle 800 in the image sequence (e.g., via computer vision and / or other machine learning object classification techniques). In at least one embodiment, the deep learning infrastructure may run its own neural network to identify objects and compare them with objects identified by vehicle 800, and if the results do not match and the deep learning infrastructure determines that the AI ​​in vehicle 800 is malfunctioning, one or more servers 878 may signal to vehicle 800 to instruct the fail-safe computer of vehicle 800 to take control, notify passengers, and complete a safe stopping operation.

[0211] In at least one embodiment, one or more servers 878 may include one or more GPUs 884 and one or more programmable inference accelerators (such as NVIDIA's TensorRT 3). In at least one embodiment, the combination of GPU-driven servers and inference acceleration can enable real-time response. In at least one embodiment, for example, where performance is less critical, servers driven by CPUs, FPGAs, and other processors can be used for inference.

[0212] Computer System

[0213] Figure 9 This is a block diagram illustrating an exemplary computer system according to at least one embodiment. The exemplary computer system may be a system of interconnected devices and components, a system-on-a-chip (SoC), or some combination thereof formed with a processor, which may include an execution unit to execute instructions. In at least one embodiment, according to this disclosure, such as the embodiments described herein, computer system 900 may include, but is not limited to, components such as processor 902, whose execution unit includes logic to execute algorithms for process data. In at least one embodiment, computer system 900 may include a processor, such as the PENTIUM® processor family or Xeon processor, available from Intel Corporation of Santa Clara, California. TM Itanium®, XScale TM and / or StrongARM TM The system may use an Intel® Core™ or Intel® Nervana™ microprocessor, although other systems (including PCs, engineering workstations, set-top boxes, etc.) may also be used. In at least one embodiment, the computer system 900 may execute a version of the Windows operating system available from Microsoft Corporation of Redmond, Wash., although other operating systems (such as UNIX and Linux), embedded software, and / or graphical user interfaces may also be used.

[0214] The embodiments can be used in other devices, such as handheld devices and embedded applications. Some examples of handheld devices include cellular phones, Internet Protocol (IP) devices, digital cameras, personal digital assistants (“PDAs”), and handheld PCs. In at least one embodiment, the embedded application may include a microcontroller, a digital signal processor (“DSP”), a system-on-a-chip (SoC), a network computer (“NetPC”), a set-top box, a network hub, a wide area network (“WAN”) switch, or any other system that can execute one or more instructions according to at least one embodiment.

[0215] In at least one embodiment, computer system 900 may include, but is not limited to, processor 902, which may include, but is not limited to, one or more execution units 908, to perform machine learning model training and / or inference according to the techniques described herein. In at least one embodiment, system 9 is a single-processor desktop or server system, but in another embodiment, system 9 may be a multiprocessor system. In at least one embodiment, processor 902 may include, but is not limited to, a Complex Instruction Set Computer (“CISC”) microprocessor, a Reduced Instruction Set Computing (“RISC”) microprocessor, a Very Long Instruction Word (“VLIW”) microprocessor, a processor implementing instruction set combination, or any other processor device, such as a digital signal processor. In at least one embodiment, processor 902 may be coupled to processor bus 910, which can transmit data signals between processor 902 and other components in computer system 900.

[0216] In at least one embodiment, processor 902 may include, but is not limited to, a Level 1 (“L1”) internal cache memory (“cache”) 904. In at least one embodiment, processor 902 may have a single internal cache or multiple levels of internal cache. In at least one embodiment, the cache memory may reside external to processor 902. Depending on specific implementation and requirements, other embodiments may also include a combination of internal and external caches. In at least one embodiment, register file 906 may store different types of data in various registers, including but not limited to integer registers, floating-point registers, status registers, and instruction pointer registers.

[0217] In at least one embodiment, an execution unit 908, including but not limited to logic for performing integer and floating-point operations, is also located within the processor 902. In at least one embodiment, the processor 902 may further include a microcode (“ucode”) read-only memory (“ROM”) for storing microcode of certain macro instructions. In at least one embodiment, the execution unit 908 may include logic for processing a packaged instruction set 909. In at least one embodiment, by including the packaged instruction set 909 in the instruction set of a general-purpose processor, along with the associated circuitry for executing the instructions, packaged data in the general-purpose processor 902 can be used to perform operations used by numerous multimedia applications. In one or more embodiments, many multimedia applications can be executed more quickly and efficiently by using the full width of the processor’s data bus to perform operations on the packaged data, which may eliminate the need to transfer smaller data units on the processor’s data bus to perform one or more operations on one data element at a time.

[0218] In at least one embodiment, execution unit 908 may also be used in a microcontroller, embedded processor, graphics device, DSP, and other types of logic circuitry. In at least one embodiment, computer system 900 may include, but is not limited to, memory 920. In at least one embodiment, memory 920 may be implemented as a dynamic random access memory (“DRAM”) device, a static random access memory (“SRAM”) device, a flash memory device, or other storage device. In at least one embodiment, memory 920 may store instructions 919 and / or data 921 represented by data signals that can be executed by processor 902.

[0219] In at least one embodiment, the system logic chip may be coupled to the processor bus 910 and the memory 920. In at least one embodiment, the system logic chip may include, but is not limited to, a memory controller hub (“MCH”) 916, and the processor 902 may communicate with the MCH 916 via the processor bus 910. In at least one embodiment, the MCH 916 may provide a high-bandwidth memory path 918 to the memory 920 for instruction and data storage, as well as for storage of graphics commands, data, and textures. In at least one embodiment, the MCH 916 may initiate data signals between the processor 902, the memory 920, and other components in the computer system 900, and bridge data signals between the processor bus 910, the memory 920, and the system I / O 922. In at least one embodiment, the system logic chip may provide a graphics port for coupling to a graphics controller. In at least one embodiment, the MCH 916 may be coupled to the memory 920 via the high-bandwidth memory path 918, and the graphics / video card 912 may be coupled to the MCH 916 via an Accelerated Graphics Port (“AGP”) interconnect 914.

[0220] In at least one embodiment, the autonomous vehicle 800 may include a wireless network, such as the MIMO network described above. In at least one embodiment, control data may be transmitted within a portion of a time window having an exclusive window with time slots.

[0221] Computer system 900 may use system I / O 922, which is a proprietary hub interface bus, to couple MCH 916 to I / O controller hub (“ICH”) 930. In at least one embodiment, ICH 930 may provide direct connectivity to certain I / O devices via a local I / O bus. In at least one embodiment, the local I / O bus may include, but is not limited to, a high-speed I / O bus for connecting peripheral devices to memory 920, chipset, and processor 902. Examples may include, but are not limited to, an audio controller 929, a firmware hub (“Flash BIOS”) 928, a wireless transceiver 926, a data storage 924, a conventional I / O controller 923 including a user input and keyboard interface, a serial expansion port 927 (e.g., Universal Serial Bus (USB)), and a network controller 934. In at least one embodiment, data storage 924 may include a hard disk drive, floppy disk drive, CD-ROM device, flash memory device, or other mass storage device.

[0222] In at least one embodiment, Figure 9 A system including interconnected hardware devices or "chips" is shown, while in other embodiments, Figure 9A system-on-a-chip (SoC) can be shown. In at least one embodiment, Figure 9 The devices shown can be interconnected with proprietary interconnects, standardized interconnects (e.g., PCIe), or some combination thereof. In at least one embodiment, one or more components of system 900 are interconnected using a compute fast link (CXL) interconnect.

[0223] In at least one embodiment, system 900 can be used to implement a wireless network, such as the MIMO network described above. In at least one embodiment, system 900 can implement, for example... Figure 6 The control data thread, user data thread, and beamforming weight calculation thread are shown.

[0224] Figure 10 This is a block diagram illustrating an electronic device 1000 for utilizing a processor 1010 according to at least one embodiment. In at least one embodiment, the electronic device 1000 may be, for example, but not limited to, a laptop computer, tower server, rack server, blade server, laptop computer, desktop computer, tablet computer, mobile device, telephone, embedded computer, or any other suitable electronic device.

[0225] In at least one embodiment, system 1000 may include, but is not limited to, processor 1010 communicatively coupled to any suitable number or type of components, peripherals, modules, or devices. In at least one embodiment, processor 1010 uses a bus or interface coupling, such as an I²C bus, system management bus (“SMBus”), low pin count (LPC) bus, serial peripheral interface (“SPI”), high-definition audio (“HDA”) bus, serial advanced technology accessory (“SATA”) bus, universal serial bus (“USB”) (versions 1, 2, 3, etc.), or universal asynchronous receiver / transmitter (“UART”) bus. In at least one embodiment, Figure 10 The system shown includes interconnected hardware devices or "chips," while in other embodiments, Figure 10 An exemplary system-on-a-chip (SoC) can be illustrated. In at least one embodiment, Figure 10 The device shown can be interconnected with proprietary interconnects, standardized interconnects (e.g., PCIe), or some combination thereof. In at least one embodiment, Figure 10 One or more components are interconnected using Computational Fast Link (CXL) interconnects.

[0226] In at least one embodiment, Figure 10This may include a display 1024, a touchscreen 1025, a touchpad 1030, a near-field communication unit (“NFC”) 1045, a sensor hub 1040, a thermal sensor 1046, a fast chipset (“EC”) 1035, a trusted platform module (“TPM”) 1038, a BIOS / firmware / flash memory (“BIOS, FW Flash”) 1022, a DSP 1060, a drive “SSD or HDD” 1020 (e.g., a solid-state drive (“SSD”) or a hard disk drive (“HDD”)), a wireless local area network unit (“WLAN”) 1050, a Bluetooth unit 1052, a wireless wide area network unit (“WWAN”) 1056, a global positioning system (GPS) 1055, a camera (“USB 3.0 camera”) 1054 (e.g., a USB 3.0 camera), or a low-power double data rate (“LPDDR”) memory unit (“LPDDR3”) 1015 implemented in, for example, the LPDDR3 standard. These components may each be implemented in any suitable manner.

[0227] In at least one embodiment, other components may be communicatively coupled to processor 1010 via the components described above. In at least one embodiment, accelerometer 1041, ambient light sensor (“ALS”) 1042, compass 1043, and gyroscope 1044 may be communicatively coupled to sensor hub 1040. In at least one embodiment, thermal sensor 1039, fan 1037, keyboard 1046, and touchpad 1030 may be communicatively coupled to EC 1035. In at least one embodiment, speaker 1063, earphone 1064, and microphone (“mic”) 1065 may be communicatively coupled to audio unit (“audio codec and Class D amplifier”) 1064, which in turn may be communicatively coupled to DSP 1060. In at least one embodiment, audio unit 1064 may include, for example, but not limited to, audio encoder / decoder (“codec”) and Class D amplifier. In at least one embodiment, SIM card (“SIM”) 1057 may be communicatively coupled to WWAN unit 1056. In at least one embodiment, components such as WLAN unit 1050, Bluetooth unit 1052, and WWAN unit 1056 can be implemented as next-generation form factor (NGFF).

[0228] In at least one embodiment, the processor 1010 can be used to implement a wireless network, such as the MIMO network described above. In at least one embodiment, the processor 1010 can implement, as... Figure 6 The control data thread, user data thread, and beamforming weight calculation thread are shown.

[0229] Figure 11A computer system 1100 according to at least one embodiment is shown. In at least one embodiment, the computer system 1100 is configured to implement various processes and methods described throughout this disclosure.

[0230] In at least one embodiment, the computer system 1100 includes, but is not limited to, at least one central processing unit (“CPU”) 1102 connected to a communication bus 1110 implemented using any suitable protocol, such as PCI (“Peripheral Device Interconnect”), Peripheral Component Interconnect Express (“PCI-Express”), AGP (“Accelerated Graphics Port”), HyperTransport, or any other bus or point-to-point communication protocol. In at least one embodiment, the computer system 1100 includes, but is not limited to, main memory 1104 and control logic (e.g., implemented in hardware, software, or a combination thereof), and data may be stored in main memory 1104 in the form of random access memory (“RAM”). In at least one embodiment, a network interface subsystem (“Network Interface”) 1122 provides an interface to other computing devices and networks for receiving data from the computer system 1100 and transferring data to other systems.

[0231] In at least one embodiment, the computer system 1100 includes, but is not limited to, an input device 1108, a parallel processing system 1112, and a display device 1106, which may be implemented using conventional cathode ray tube (“CRT”), liquid crystal display (“LCD”), light-emitting diode (“LED”), plasma display, or other suitable display technologies. In at least one embodiment, user input is received from the input device 1108 (such as a keyboard, mouse, touchpad, microphone, etc.). In at least one embodiment, each of the foregoing modules may reside on a single semiconductor platform to form the processing system.

[0232] At least one computer system 1100 can be used to implement a wireless network, such as the MIMO network described above. In at least one embodiment, the computer system 1100 can implement, as... Figure 6 The control data thread, user data thread, and beamforming weight calculation thread are shown.

[0233] Figure 12 A computer system 1200 according to at least one embodiment is illustrated. In at least one embodiment, the computer system 1200 includes, but is not limited to, a computer 1210 and a USB stick 1220. In at least one embodiment, the computer 1210 may include, but is not limited to, any number and type of processors (not shown) and memory (not shown). In at least one embodiment, the computer 1210 includes, but is not limited to, a server, a cloud instance, a laptop computer, and a desktop computer.

[0234] In at least one embodiment, the USB stick 1220 includes, but is not limited to, a processing unit 1230, a USB interface 1240, and USB interface logic 1250. In at least one embodiment, the processing unit 1230 can be any instruction execution system, apparatus, or device capable of executing instructions. In at least one embodiment, the processing unit 1230 can include, but is not limited to, any number and type of processing cores (not shown). In at least one embodiment, the processing core 1230 includes an application-specific integrated circuit (“ASIC”) optimized to perform any number and type of operations associated with machine learning. For example, in at least one embodiment, the processing core 1230 is a tensor processing unit (“TPC”) optimized to perform machine learning inference operations. In at least one embodiment, the processing core 1230 is a vision processing unit (“VPU”) optimized to perform machine vision and machine learning inference operations.

[0235] In at least one embodiment, the USB interface 1240 can be any type of USB connector or USB receptacle. For example, in at least one embodiment, the USB interface 1240 is a USB 3.0 Type-C receptacle for data and power. In at least one embodiment, the USB interface 1240 is a USB 3.0 Type-A connector. In at least one embodiment, the USB interface logic 1250 may include any amount and type of logic enabling the processing unit 1230 to connect to a device (e.g., computer 1210) via the USB connector 1240.

[0236] At least one computer system 1200 can be used to implement a wireless network, such as the MIMO network described above. In at least one embodiment, the computer system 1200 can implement, as... Figure 6 The control data thread, user data thread, and beamforming weight calculation thread are shown.

[0237] Figure 13A An exemplary architecture is illustrated, in which multiple GPUs 1310-1313 are communicatively coupled to multiple multi-core processors 1305-1306 via high-speed links 1340-1343 (e.g., bus / point-to-point interconnect, etc.). In one embodiment, the high-speed links 1340-1343 support communication throughput of 4GB / s, 30GB / s, 80GB / s, or higher. Various interconnect protocols can be used, including but not limited to PCIe 4.0 or 5.0 and NVLink 2.0.

[0238] Furthermore, in one embodiment, two or more GPUs 1310-1313 are interconnected via high-speed links 1329-1330, which may use the same or different protocols / links as those used for high-speed links 1340-1343. Similarly, two or more multi-core processors 1305-1306 may be connected via high-speed link 1328, which may be a symmetric multiprocessor (SMP) bus operating at speeds of 20GB / s, 30GB / s, 120GB / s, or higher. Alternatively, the same protocol / link may be used (e.g., via a common interconnect structure). Figure 13A This shows all communication between the various system components.

[0239] In one embodiment, each multi-core processor 1305-1306 is communicatively coupled to processor memories 1301-1302 via memory interconnects 1326-1327, and each GPU 1310-1313 is communicatively coupled to GPU memories 1320-1323 via GPU memory interconnects 1350-1353. Memory interconnects 1326-1327 and 1350-1353 may utilize the same or different memory access technologies. By way of example and not limitation, processor memories 1301-1302 and GPU memories 1320-1323 may be volatile memories, such as dynamic random access memory (DRAM) (including stacked DRAM), graphics DDR SDRAM (GDDR) (e.g., GDDR5, GDDR6), or high-bandwidth memory (HBM), and / or may be non-volatile memories, such as 3D XPoint or Nano-RAM. In one embodiment, some portions of the processor memories 1301-1302 may be volatile memory, while other portions may be non-volatile memory (e.g., using a two-level memory (2LM) hierarchy).

[0240] As described in this article, although the various processors 1305-1306 and GPUs 1310-1313 can be physically coupled to specific memories 1301-1302 and 1320-1323 respectively, a unified memory architecture can be implemented, in which the same virtual system address space (also known as the “effective address” space) is distributed among the various physical memories. For example, processor memories 1301-1302 can each contain 64 GB of system memory address space, and GPU memories 1320-1323 can each contain 32 GB of system memory address space (resulting in a total addressable memory size of 256 GB in this example).

[0241] Figure 13BAdditional details are shown regarding the interconnection between a multi-core processor 1307 and a graphics acceleration module 1346, according to an exemplary embodiment. The graphics acceleration module 1346 may include one or more GPU chips integrated on a line card coupled to the processor 1307 via a high-speed link 1340. Alternatively, the graphics acceleration module 1346 may be integrated on the same package or chip as the processor 1307.

[0242] In at least one embodiment, the processor 1307 shown includes a plurality of cores 1360A-1360D, each core having a translation back buffer 1361A-1361D and one or more caches 1362A-1362D. In at least one embodiment, cores 1360A-1360D may include various other components (not shown) for executing instructions and processing data. In at least one embodiment, caches 1362A-1362D may include level 1 (L1) and level 2 (L2) caches. Furthermore, one or more shared caches 1356 may be included in caches 1362A-1362D and shared by the respective groups of cores 1360A-1360D. For example, one embodiment of the processor 1307 includes 24 cores, each core having its own L1 cache, twelve shared L2 caches, and twelve shared L3 caches. In this embodiment, two adjacent cores share one or more L2 and L3 caches. Processor 1307 and graphics acceleration module 1346 are connected to system memory 1314, which may include Figure 13A The processor memory 1301-1302 in the memory.

[0243] Consistency of data and instructions stored in the various caches 1362A-1362D, 1356 and system memory 1314 is maintained via inter-core communication through the consistency bus 1364. For example, each cache may have associated cache consistency logic / circuit to communicate via the consistency bus 1364 in response to the detection of a read or write to a specific cache line. In one implementation, a cache snooping protocol is implemented via the consistency bus 1364 to snoop on cache accesses.

[0244] In one embodiment, proxy circuitry 1325 communicatively couples graphics acceleration module 1346 to coherence bus 1364, thereby allowing graphics acceleration module 1346 to participate in cache coherence protocols as a peer of cores 1360A-1360D. Specifically, in at least one embodiment, interface 1335 provides connectivity to proxy circuitry 1325 via high-speed link 1340 (e.g., PCIe bus, NVLink, etc.), and interface 1337 connects graphics acceleration module 1346 to link 1340.

[0245] In one implementation, the accelerator integrated circuit 1336 represents multiple graphics processing engines 1331, 1332, N of the graphics acceleration module, providing cache management, memory access, context management, and interrupt management services. The graphics processing engines 1331, 1332, N may each include a separate graphics processing unit (GPU). Optionally, the graphics processing engines 1331, 1332, N may selectively include different types of graphics processing engines within the GPU, such as graphics execution units, media processing engines (e.g., video encoders / decoders), samplers, and blit engines. In at least one embodiment, the graphics acceleration module 1346 may be a GPU having multiple graphics processing engines 1331-1332, N, or the graphics processing engines 1331-1332, N may be individual GPUs integrated on a general-purpose package, line card, or chip.

[0246] In one embodiment, the accelerator integrated circuit 1336 includes a memory management unit (MMU) 1339 for performing various memory management functions, such as virtual-to-physical memory translation (also known as effective-to-real memory translation), and a memory access protocol for accessing system memory 1314. The MMU 1339 may also include a translation back buffer (“TLB”) (not shown) for caching virtual / effective-to-physical / real address translations. In one implementation, cache 1338 may store commands and data for effective access by graphics processing engines 1331-1332,N. In at least one embodiment, data stored in cache 1338 and graphics memories 1333-1334,M is kept consistent with core caches 1362A-1362D, 1356 and system memory 1314. As previously mentioned, this task can be accomplished via proxy circuitry 1325 representing cache 1338 and graphics memory 1333-1334, M (e.g., sending updates related to the modification / access of cache lines on processor caches 1362A-1362D, 1356 to cache 1338 and receiving updates from cache 1338).

[0247] A set of registers 1345 stores the context data of the threads executed by graphics processing engines 1331, 1332, N, and context management circuitry 1348 manages the thread context. For example, context management circuitry 1348 can perform save and restore operations to save and restore the context of individual threads during context switching (e.g., saving the first thread and storing the second thread so that the second thread can be executed by the graphics processing engine). For example, during context switching, context management circuitry 1348 can store the current register value into a designated area in memory (e.g., identified by the context pointer). The register value can then be restored when returning to the context. In one embodiment, interrupt management circuitry 1347 receives and processes interrupts received from system devices.

[0248] In one implementation, MMU 1339 translates virtual / effective addresses from graphics processing engine 1331 into real / physical addresses in system memory 1314. One embodiment of accelerator integrated circuit 1336 supports multiple (e.g., 4, 8, 16) graphics accelerator modules 1346 and / or other accelerator devices. Graphics accelerator module 1346 may be dedicated to a single application executing on processor 1307, or may be shared among multiple applications. In one embodiment, a virtualized graphics execution environment is presented, where the resources of graphics processing engines 1331-1332, N are shared with multiple applications or virtual machines (VMs). In at least one embodiment, resources may be subdivided into “slices” based on processing requirements and priorities associated with VMs and / or applications, which are allocated to different VMs and / or applications.

[0249] In at least one embodiment, the accelerator integrated circuit 1336 acts as a system bridge for the graphics acceleration module 1346 and provides address translation and system memory caching services. Additionally, the accelerator integrated circuit 1336 can provide virtualization facilities for the host processor to manage the virtualization, interrupt, and memory management of the graphics processing engines 1331-1332.

[0250] Because of the graphics processing engines 1331-1332, N's hardware resources are explicitly mapped to the real address space seen by the host processor 1307, any host processor can directly address these resources using valid address values. In at least one embodiment, a function of the accelerator integrated circuit 1336 is to physically separate the graphics processing engines 1331-1332, N, so that they appear as independent units to the system.

[0251] In at least one embodiment, one or more graphics memories 1333-1334, M are coupled to each graphics processing engine 1331-1332, N, respectively. Graphics memories 1333-1334, M store instructions and data processed by each graphics processing engine 1331-1332, N. Graphics memories 1333-1334, M can be volatile memory, such as DRAM (including stacked DRAM), GDDR memory (e.g., GDDR5, GDDR6), or HBM, and / or can be non-volatile memory, such as 3D XPoint or Nano-RAM.

[0252] In one embodiment, to reduce data traffic on link 1340, a biasing technique can be used to ensure that the data stored in graphics memories 1333-1334, M is the data most frequently used by graphics processing engines 1331-1332, N, and preferably not used (or at least infrequently used) by cores 1360A-1360D. Similarly, in at least one embodiment, the biasing mechanism attempts to keep the data needed by the cores (and preferably not graphics processing engines 1331-1332, N) in the core caches 1362A-1362D, 1356 and system memory 1314.

[0253] Figure 13C Another exemplary embodiment is shown, in which the accelerator integrated circuit 1336 is integrated within the processor 1307. In this embodiment, graphics processing engines 1331-1332,N communicate directly with the accelerator integrated circuit 1336 via a high-speed link 1340 through interfaces 1337 and 1335 (which can also utilize any form of bus or interface protocol). The accelerator integrated circuit 1336 can perform operations related to... Figure 13B The operations described are the same. However, due to its close proximity to the coherence bus 1364 and caches 1362A-1362D, 1356, it may have higher throughput. One embodiment supports different programming models, including a dedicated process programming model (without graphics acceleration module virtualization) and a shared programming model (with virtualization), which may include a programming model controlled by accelerator integrated circuit 1336 and a programming model controlled by graphics acceleration module 1346.

[0254] In at least one embodiment, graphics processing engines 1331-1332,N are dedicated to a single application or process within a single operating system. In at least one embodiment, a single application can funnel requests from other applications to graphics processing engines 1331-1332,N, thereby providing virtualization within a VM / partition.

[0255] In at least one embodiment, graphics processing engines 1331-1332, N can be shared by multiple VM / application partitions. In at least one embodiment, the shared model can use a hypervisor to virtualize graphics processing engines 1331-1332, N to allow each operating system to access them. For a single-partition system without a hypervisor, the operating system owns graphics processing engines 1331-1332, N. In at least one embodiment, the operating system can virtualize graphics processing engines 1331-1332, N to provide access to each process or application.

[0256] In at least one embodiment, the graphics acceleration module 1346 or the individual graphics processing engines 1331-1332, N uses a process handle to select a process element. In one embodiment, the process element is stored in system memory 1314 and can be addressed using the effective address to physical address translation techniques described herein. In at least one embodiment, the process handle may be an implementation-specific value provided to the host process when registering its context with the graphics processing engines 1331-1332, N (i.e., invoking system software to add the process element to the process element linked list). In at least one embodiment, the lower 16 bits of the process handle may be the offset of the process element in the process element linked list.

[0257] Figure 13D An exemplary accelerator integration slice 1390 is shown. As used herein, a “slice” includes a designated portion of the processing resources of the accelerator integrated circuit 1336. The application is an effective address space 1382 in system memory 1314 that stores process element 1383. In one embodiment, process element 1383 is stored in response to a GPU call 1381 from an application 1380 executing on processor 1307. Process element 1383 contains the process state of the corresponding application 1380. A job descriptor (WD) 1384 contained in process element 1383 may be a single job requested by the application, or it may contain a pointer to a job queue. In at least one embodiment, WD 1384 is a pointer to a job request queue in the application’s address space 1382.

[0258] The graphics acceleration module 1346 and / or the various graphics processing engines 1331-1332, N, can be shared by all processes or a subset of processes in the system. In at least one embodiment, infrastructure may be included for setting process states and sending WD 1384 to the graphics acceleration module 1346 to begin operations in a virtualized environment.

[0259] In at least one embodiment, the dedicated process programming model is implementation-specific. In this model, a single process owns either the graphics acceleration module 1346 or an individual graphics processing engine 1331. When the graphics acceleration module 1346 is owned by a single process, the hypervisor initializes the accelerator integrated circuit for the owned partition; when the graphics acceleration module 1346 is assigned, the operating system initializes the accelerator integrated circuit 1336 for the owned process.

[0260] In operation, the WD fetch unit 1391 in the accelerator integrated slice 1390 fetches the next WD 1384, which includes instructions for the work to be performed by one or more graphics processing engines of the graphics acceleration module 1346. Data from the WD 1384 can be stored in register 1345 and used by the MMU 1339, interrupt management circuitry 1347, and / or context management circuitry 1348, as shown. For example, one embodiment of the MMU 1339 includes segment / page roaming circuitry for accessing segment / page tables 1386 within the OS virtual address space 1385. The interrupt management circuitry 1347 can handle interrupt events 1392 received from the graphics acceleration module 1346. When performing graphics operations, the effective address 1393 generated by the graphics processing engines 1331-1332,N is translated into a real address by the MMU 1339.

[0261] In one embodiment, for each graphics processing engine 1331-1332, N and / or graphics acceleration module 1346, the same set of registers 1345 is copied, and said registers 1345 can be initialized by a hypervisor or operating system. Each of these copied registers can be included in the accelerator integration slice 1390. Exemplary registers that can be initialized by a hypervisor are shown in Table 1.

[0262]

[0263] Table 2 shows exemplary registers that can be initialized by the operating system.

[0264]

[0265] In one embodiment, each WD 1384 is specific to a particular graphics acceleration module 1346 and / or graphics processing engine 1331-1332,N. It contains all the information required for the graphics processing engine 1331-1332,N to complete its work, or it may be a pointer to a memory location where the application has set up a command queue for the work to be done.

[0266] Figure 13EAdditional details of an exemplary embodiment of the shared model are shown. This embodiment includes a hypervisor real address space 1398, in which a list of process elements 1399 is stored. The hypervisor real address space 1398 can be accessed via a hypervisor 1396, which virtualizes the graphics acceleration module engine for operating system 1395.

[0267] In at least one embodiment, the shared programming model allows all processes or subsets of processes from all partitions or subsets of partitions in the system to use the graphics acceleration module 1346. Two programming models exist where the graphics acceleration module 1346 is shared by multiple processes and partitions: time-slice sharing and graphics-oriented sharing.

[0268] In this model, the hypervisor 1396 owns the graphics acceleration module 1346 and makes its functionality available to all operating systems 1395. For the graphics acceleration module 1346 to support virtualization through the hypervisor 1396, the graphics acceleration module 1346 may comply with the following: (1) the job requests of the application must be autonomous (i.e., no state needs to be maintained between jobs), or the graphics acceleration module 1346 must provide a context saving and restoration mechanism; (2) the graphics acceleration module 1346 guarantees that the job requests of the application are completed within a specified amount of time, including any conversion errors, or the graphics acceleration module 1346 provides the ability to preempt job processing; (3) when operating in a directed shared programming model, fairness between the processes of the graphics acceleration module 1346 must be ensured.

[0269] In at least one embodiment, application 1380 needs to make a system call to operating system 1395 using graphics acceleration module 1346 type, working descriptor (WD), authority mask register (AMR) value, and context save / restore region pointer (CSRP). In at least one embodiment, the graphics acceleration module 1346 type describes the target acceleration function for the system call. In at least one embodiment, the graphics acceleration module 1346 type can be a system-specific value. In at least one embodiment, the WD is specifically formatted for graphics acceleration module 1346 and can take the form of graphics acceleration module 1346 commands, valid address pointers to user-defined structures, valid address pointers to command queues, or any other data structure describing the work to be performed by graphics acceleration module 1346. In one embodiment, the AMR value is the AMR state for the current process. In at least one embodiment, the value passed to the operating system is similar to that of the application that sets the AMR. If the implementation of accelerator integrated circuit 1336 and graphics acceleration module 1346 does not support the User Authority Mask Overwrite Register (UAMOR), the operating system can apply the current UAMOR value to the AMR value before passing the AMR in the hypervisor call. Hypervisor 1396 may selectively apply the Current Privilege Mask Overwrite Register (AMOR) value before placing the AMR into process element 1383. In at least one embodiment, CSRP is one of registers 1345 containing the effective address of a region in the application's address space 1382 for the graphics acceleration module 1346 to save and restore context state. This pointer is optional if saving state between jobs is not required or when a job is preempted. In at least one embodiment, the context save / restore region may be fixed system memory.

[0270] Upon receiving a system call, the operating system 1395 can verify that the application 1380 has been registered and granted permission to use the graphics acceleration module 1346. Then, the operating system 1395 uses the information shown in Table 3 to invoke the hypervisor 1396.

[0271]

[0272] Upon receiving a hypervisor call, hypervisor 1396 verifies that operating system 1395 has been registered and granted permission to use graphics acceleration module 1346. Then, hypervisor 1396 adds process element 1383 to the linked list of process elements of the corresponding graphics acceleration module 1346 type. The process element may include the information shown in Table 4.

[0273]

[0274] In at least one embodiment, the hypervisor initializes multiple accelerator integration slice 1390 registers 1345.

[0275] like Figure 13F As shown, in at least one embodiment, a unified memory is used, which is addressable via a common virtual memory address space for accessing physical processor memories 1301-1302 and GPU memories 1320-1323. In this implementation, operations performed on GPUs 1310-1313 utilize the same virtual / effective memory address space to access processor memories 1301-1302 and vice versa, thereby simplifying programmability. In at least one embodiment, a first portion of the virtual / effective address space is allocated to processor memory 1301, a second portion to second processor memory 1302, a third portion to GPU memory 1320, and so on. In at least one embodiment, the entire virtual / effective memory space (sometimes referred to as the effective address space) is thus distributed across each of processor memories 1301-1302 and GPU memories 1320-1323, thereby allowing any processor or GPU to access that memory using a virtual address mapped to any physical memory.

[0276] In one embodiment, the bias / coherence management circuitry 1394A-1394E within one or more MMUs 1339A-1339E ensures cache coherence between the caches of one or more host processors (e.g., 1305) and the GPUs 1310-1313, and implements biasing techniques that indicate the physical memory in which certain types of data should be stored. While in Figure 13F Several instances of bias / coherence management circuits 1394A-1394E are shown, but bias / coherence circuits can be implemented within the MMU of one or more host processors 1305 and / or within the accelerator integrated circuit 1336.

[0277] One embodiment allows GPU-attached memories 1320-1323 to be mapped as part of system memory and accessed using shared virtual memory (SVM) technology without suffering the performance drawbacks associated with full system cache coherence. In at least one embodiment, the ability to access GPU-attached memories 1320-1323 as system memory without the heavy overhead of cache coherence provides a favorable operating environment for GPU offloading. This arrangement allows the host processor 1305 to software-set operands and access computation results without the overhead of conventional I / O DMA data copying. Such conventional copying includes driver calls, interrupts, and memory-mapped I / O (MMIO) accesses, all of which are less efficient than simple memory accesses. In at least one embodiment, the ability to access GPU-attached memories 1320-1323 without cache coherence overhead can be critical for the execution time of offloaded computations. For example, in cases with high streaming write traffic to memory, cache coherence overhead can significantly reduce the effective write bandwidth seen by GPUs 1310-1313. In at least one embodiment, the efficiency of operand setup, the efficiency of result access, and the efficiency of GPU computation may play a role in determining the effectiveness of GPU offloading.

[0278] In at least one embodiment, the selection of GPU bias and host processor bias is driven by a bias tracker data structure. For example, a bias table can be used, which may be a page-granular structure (e.g., controlled at the granularity of memory pages) comprising 1 or 2 bits of memory pages attached to each GPU. In at least one embodiment, with or without a bias cache (e.g., for caching frequently / recently used entries in the bias table) in GPUs 1310-1313, the bias table can be implemented over the stolen memory range of one or more GPU-attached memories 1320-1323. Alternatively, the entire bias table can be maintained within the GPU.

[0279] In at least one embodiment, prior to actual access to GPU memory, an access to the bias table entry associated with each access to GPU-attached memory 1320-1323 is performed, causing the following operations: First, a local request from GPUs 1310-1313 to locate its page in the GPU bias is directly forwarded to the corresponding GPU memory 1320-1323. A local request from the GPU to locate its page in the host bias is forwarded to processor 1305 (e.g., via the high-speed link described above). In one embodiment, a request from processor 1305 to locate the requested page in the host processor bias completes a request similar to a normal memory read. Alternatively, requests to GPU bias pages can be forwarded to GPUs 1310-1313. In at least one embodiment, if the GPU is not currently using the page, the GPU may subsequently migrate the page to the host processor bias. In at least one embodiment, the page bias state can be changed through a software-based mechanism, a hardware-assisted software mechanism, or, in limited cases, a purely hardware-based mechanism.

[0280] One mechanism for changing the bias state employs an API call (e.g., OpenCL), which subsequently invokes the GPU's device driver. The device driver then sends a message (or enqueues a command descriptor) to the GPU, instructing the GPU to change the bias state and, in some migrations, performs a cache refresh operation on the host. In at least one embodiment, the cache refresh operation is used for migrations from the host processor 1305 bias to the GPU bias, but not for the reverse migration.

[0281] In one embodiment, cache coherence is maintained by temporarily rendering GPU bias pages that the host processor 1305 cannot cache. To access these pages, the processor 1305 may request access from the GPU 1310, which may or may not grant access immediately. Therefore, to reduce communication between the processor 1305 and the GPU 1310, it is beneficial to ensure that the GPU bias pages are those required by the GPU, not those required by the host processor 1305, and vice versa.

[0282] Figure 14 Exemplary integrated circuits and associated graphics processors according to various embodiments described herein are illustrated, which may be manufactured using one or more IP cores. In addition to the illustrations, at least one embodiment may include other logic and circuitry, including additional graphics processors / cores, peripheral interface controllers, or general-purpose processor cores.

[0283] Figure 14This is a block diagram illustrating an exemplary system on a chip integrated circuit 1400 that may be fabricated using one or more IP cores according to at least one embodiment. In at least one embodiment, the integrated circuit 1400 includes one or more application processors 1405 (e.g., CPUs), at least one graphics processor 1410, and may additionally include an image processor 1415 and / or a video processor 1420, any of which may be a modular IP core. In at least one embodiment, the integrated circuit 1400 includes peripheral or bus logic including a USB controller 1425, a UART controller 1430, an SPI / SDIO controller 1435, and an I.sup.2S / I.sup.2C controller 1440. In at least one embodiment, the integrated circuit 1400 may include a display device 1445 coupled to one or more of a High Definition Multimedia Interface (HDMI) controller 1450 and a Mobile Industrial Processor Interface (MIPI) display interface 1455. In at least one embodiment, storage may be provided by a flash memory subsystem 1460, including flash memory and a flash memory controller. In at least one embodiment, a memory interface may be provided via a memory controller 1465 for accessing an SDRAM or SRAM memory device. In at least one embodiment, some integrated circuits also include an embedded security engine 1470.

[0284] At least one computer system 1100 can be used to implement a wireless network, such as the MIMO network described above. In at least one embodiment, the computer system 1100 can implement, as... Figure 6 The control data thread, user data thread, and beamforming weight calculation thread are shown.

[0285] Figures 15A-15B Exemplary integrated circuits and associated graphics processors according to various embodiments described herein are illustrated, which may be manufactured using one or more IP cores. In addition to the illustrations, at least one embodiment may include other logic and circuitry, including additional graphics processors / cores, peripheral interface controllers, or general-purpose processor cores.

[0286] Figures 15A-15B This is a block diagram illustrating an exemplary graphics processor used within a SoC according to embodiments described herein. Figure 15A An exemplary graphics processor 1510, which can be fabricated using one or more IP cores according to at least one embodiment, is shown. Figure 15B Further exemplary graphics processor 1540 of a system-on-a-chip integrated circuit according to at least one embodiment is shown, which can be manufactured using one or more IP cores. In at least one embodiment, Figure 15A The graphics processor 1510 is a low-power graphics processor core. In at least one embodiment, Figure 15B The graphics processor 1540 is a higher-performance graphics processor core. In at least one embodiment, each graphics processor 1510, 1540 may be... Figure 14 A variant of the 1410 graphics processor.

[0287] In at least one embodiment, the graphics processor 1510 includes a vertex processor 1505 and one or more fragment processors 1515A-1515N (e.g., 1515A, 1515B, 1515C, 1515D to 1515N-1 and 1515N). In at least one embodiment, the graphics processor 1510 may execute different shader programs via separate logic, such that the vertex processor 1505 is optimized to perform operations for the vertex shader program, while one or more fragment processors 1515A-1515N perform fragment (e.g., pixel) shading operations for fragments or pixels or shader programs. In at least one embodiment, the vertex processor 1505 performs the vertex processing stage of the 3D graphics pipeline and generates primitive and vertex data. In at least one embodiment, one or more fragment processors 1515A-1515N use the primitive and vertex data generated by the vertex processor 1505 to generate framebuffers for display on a display device. In at least one embodiment, one or more fragment processors 1515A-1515N are optimized to execute fragment shader programs as provided in the OpenGL API, which can be used to perform operations similar to those of pixel shader programs provided in the Direct 3D API.

[0288] In at least one embodiment, the graphics processor 1510 additionally includes one or more memory management units (MMUs) 1520A-1520B, one or more caches 1525A-1525B, and one or more circuit interconnects 1530A-1530B. In at least one embodiment, one or more MMUs 1520A-1520B provide a virtual-to-physical address mapping for the graphics processor 1510, including for the vertex processor 1505 and / or fragment processors 1515A-1515N, which can reference vertex or image / texture data stored in memory, in addition to vertex or image / texture data stored in one or more caches 1525A-1525B. In at least one embodiment, one or more MMUs 1520A-1520B can be synchronized with other MMUs within the system, including with... Figure 14One or more application processors 1405, graphics processors 1415, and / or video processors 1420 are associated with one or more MMUs, such that each processor 1405-1420 can participate in a shared or unified virtual memory system. In at least one embodiment, one or more circuit interconnects 1530A-1530B enable the graphics processor 1510 to be connected to other IP cores within the SoC via the SoC's internal bus or via a direct connection.

[0289] In at least one embodiment, the graphics processor 1540 includes Figure 15A The graphics processor 1510 includes one or more MMUs 1520A-1520B, caches 1525A-1525B, and circuit interconnects 1530A-1530B. In at least one embodiment, the graphics processor 1540 includes one or more shader cores 1555A-1555N (e.g., 1555A, 1555B, 1555C, 1555D, 1555E, 1555F to 1555N-1 and 1555N) that provide a unified shader core architecture, wherein a single core or type of core can execute all types of programmable shader code, including shader program code for implementing vertex shaders, fragment shaders, and / or compute shaders. In at least one embodiment, the number of shader cores may vary. In at least one embodiment, the graphics processor 1540 includes an inter-core task manager 1545 that acts as a thread dispatcher to assign execution threads to one or more shader cores 1555A-1555N and a tile unit 1558 to accelerate tile-based rendering operations, wherein rendering operations of a scene are subdivided in image space, for example, to take advantage of local spatial consistency within the scene or to optimize the use of internal caches.

[0290] In at least one embodiment, the graphics processor 1540 can be used to implement a wireless network, such as the MIMO network described above. In at least one embodiment, the graphics processor 1540 can implement, for example... Figure 6 The control data thread, user data thread, and beamforming weight calculation thread are shown.

[0291] Figures 16A-16B Additional exemplary graphics processor logic according to embodiments described herein is illustrated. In at least one embodiment, Figure 16A It shows that it can be included in Figure 14 The graphics core 1600 within the graphics processor 1410, and in at least one embodiment, may be as follows: Figure 15B The unified shader cores shown are 1555A-1555N. Figure 16BA highly parallel general-purpose graphics processing unit 1630 suitable for deployment on a multi-chip module is shown in at least one embodiment.

[0292] In at least one embodiment, the graphics core 1600 includes a shared instruction cache 1602, texture units 1618, and cache / shared memory 1620, which are common to the execution resources within the graphics core 1600. In at least one embodiment, the graphics core 1600 may include multiple slices 1601A-1601N or partitions of each core, and the graphics processor may include multiple instances of the graphics core 1600. Slices 1601A-1601N may include supporting logic, including local instruction caches 1604A-1604N, thread schedulers 1606A-1606N, thread dispatchers 1608A-1608N, and a set of registers 1610A-1610N. In at least one embodiment, slices 1601A-1601N may include a set of additional functional units (AFU1612A-1612N), floating-point units (FPU 1614A-1614N), integer arithmetic logic units (ALU 1616A-1616N), address calculation units (ACU 1613A-1613N), double-precision floating-point units (DPFPU 1615A-1615N), and matrix processing units (MPU1617A-1617N).

[0293] In at least one embodiment, the FPU 1614A-1614N can perform single-precision (32-bit) and half-precision (16-bit) floating-point operations, while the DPFPU 1615A-1615N performs double-precision (64-bit) floating-point operations. In at least one embodiment, the ALU 1616A-1616N can perform variable-precision integer operations with 8-bit, 16-bit, and 32-bit precision, and can be configured for mixed-precision operations. In at least one embodiment, the MPU 1617A-1617N can also be configured for mixed-precision matrix operations, including half-precision floating-point operations and 8-bit integer operations. In at least one embodiment, the MPU 1617-1617N can perform various matrix operations to accelerate machine learning application frameworks, including enabling support for accelerated generalized matrix-to-matrix multiplication (GEMM). In at least one embodiment, the AFU 1612A-1612N can perform additional logical operations not supported by floating-point or integer units, including trigonometric operations (e.g., sine, cosine, etc.).

[0294] In at least one embodiment, the graphics core 1600 can be used to implement a wireless network, such as the MIMO network described above. In at least one embodiment, the graphics core 1600 can implement, for example... Figure 6 The control data thread, user data thread, and beamforming weight calculation thread are shown.

[0295] Figure 16B A general-purpose processing unit (GPGPU) 1630 is illustrated in at least one embodiment, which can be configured to enable highly parallel computational operations to be performed by a set of graphics processing units. In at least one embodiment, the GPGPU 1630 can be directly linked to other instances of the GPGPU 1630 to create a multi-GPU cluster to improve the training speed for deep neural networks. In at least one embodiment, the GPGPU 1630 includes a host interface 1632 for connection to a host processor. In at least one embodiment, the host interface 1632 is a PCI Express interface. In at least one embodiment, the host interface 1632 may be a vendor-specific communication interface or communication structure. In at least one embodiment, the GPGPU 1630 receives commands from the host processor and uses a global scheduler 1634 to allocate execution threads associated with those commands to a set of compute clusters 1636A-1636H. In at least one embodiment, compute clusters 1636A-1636H share a cache memory 1638. In at least one embodiment, cache memory 1638 can be used as a higher-level cache within the cache memory of computing clusters 1636A-1636H.

[0296] In at least one embodiment, the GPGPU 1630 includes memories 1644A-1644B, which are coupled to the computing cluster 1636A-1636H via a set of memory controllers 1642A-1642B. In at least one embodiment, memories 1644A-1644B may include various types of memory devices, including dynamic random access memory (DRAM) or graphics random access memory, such as synchronous graphics random access memory (SGRAM), which includes graphics double data rate (GDDR) memory.

[0297] In at least one embodiment, each of the computing clusters 1636A-1636H includes a set of graphics cores, for example... Figure 16A The graphics core 1600 may include various types of integer and floating-point logic units that can perform computational operations across a range of precisions, including precisions suitable for machine learning computations. For example, in at least one embodiment, at least a subset of the floating-point units in each computing cluster 1636A-1636H may be configured to perform 16-bit or 32-bit floating-point operations, while different subsets of the floating-point units may be configured to perform 64-bit floating-point operations.

[0298] In at least one embodiment, multiple instances of the GPGPU 1630 can be configured as a computing cluster. In at least one embodiment, the communication used for synchronization and data exchange by the computing clusters 1636A-1636H varies between embodiments. In at least one embodiment, the multiple instances of the GPGPU 1630 communicate via a host interface 1632. In at least one embodiment, the GPGPU 1630 includes an I / O hub 1639 that couples the GPGPU 1630 to a GPU link 1640, enabling direct connection to other instances of the GPGPU 1630. In at least one embodiment, the GPU link 1640 is coupled to a dedicated GPU-to-GPU bridge, which enables communication and synchronization between the multiple instances of the GPGPU 1630. In at least one embodiment, the GPU link 1640 is coupled to a high-speed interconnect for sending and receiving data to and from other GPGPUs or parallel processors. In at least one embodiment, the multiple instances of the GPGPU 1630 reside in a separate data processing system and communicate via network devices accessible through the host interface 1632. In at least one embodiment, GPU link 1640 may be configured to enable connection to a host processor other than or as a replacement for host interface 1632.

[0299] In at least one embodiment, the GPGPU 1630 can be configured to train a neural network. In at least one embodiment, the GPGPU 1630 can be used within an inference platform. In at least one embodiment, when using the GPGPU 1630 for inference, the GPGPU may include fewer compute clusters 1636A-1636H compared to when using the GPGPU to train a neural network. In at least one embodiment, the memory technology associated with the memories 1644A-1644B can differ between inference and training configurations, with higher bandwidth memory technology dedicated to the training configuration. In at least one embodiment, the inference configuration of the GPGPU 1630 can support inference-specific instructions. For example, in at least one embodiment, the inference configuration can provide support for one or more 8-bit integer dot product instructions, which can be used during the inference operation of the deployed neural network.

[0300] In at least one embodiment, the GPGPU 1630 can be used to implement wireless networks, such as the MIMO network described above. In at least one embodiment, the GPGPU 1630 can implement, for example... Figure 6 The control data thread, user data thread, and beamforming weight calculation thread are shown.

[0301] Figure 17A block diagram of a computer system 1700 according to at least one embodiment is shown. In at least one embodiment, the computer system 1700 includes a processing subsystem 1701 having one or more processors 1702 and a system memory 1704 communicating via an interconnect path that may include a memory hub 1705. In at least one embodiment, the memory hub 1705 may be a separate component within a chipset component or may be integrated within one or more processors 1702. In at least one embodiment, the memory hub 1705 is coupled to an I / O subsystem 1711 via a communication link 1706. In one embodiment, the I / O subsystem 1711 includes an I / O hub 1707 that enables the computer system 1700 to receive input from one or more input devices 1708. In at least one embodiment, the I / O hub 1707 enables a display controller to provide output to one or more display devices 1710A, the display controller being included in one or more processors 1702. In at least one embodiment, one or more display devices 1710A coupled to the I / O hub 1707 may include local, internal, or embedded display devices.

[0302] In at least one embodiment, the processing subsystem 1701 includes one or more parallel processors 1712 coupled to the memory hub 1705 via a bus or other communication link 1713. In at least one embodiment, the communication link 1713 can be any of many standards-based communication link technologies or protocols, such as, but not limited to, PCI Express, or can be a vendor-specific communication interface or communication architecture. In at least one embodiment, the one or more parallel processors 1712 form a computationally concentrated parallel or vector processing system, which may include a large number of processing cores and / or processing clusters, such as a multi-core integrated (MIC) processor. In at least one embodiment, the one or more parallel processors 1712 form a graphics processing subsystem that can output pixels to one of one or more display devices 1710A coupled via an I / O hub 1707. In at least one embodiment, the one or more parallel processors 1712 may also include a display controller and a display interface (not shown) to enable direct connection to one or more display devices 1710B.

[0303] In at least one embodiment, system storage unit 1714 may be connected to I / O hub 1707 to provide a storage mechanism for computer system 1700. In at least one embodiment, I / O switch 1716 may be used to provide an interface mechanism to enable connectivity between I / O hub 1707 and other components, such as network adapter 1718 and / or wireless network adapter 1717 that may be integrated into the platform, and various other devices that may be added via one or more attachment devices 1720. In at least one embodiment, network adapter 1718 may be an Ethernet adapter or another wired network adapter. In at least one embodiment, wireless network adapter 1719 may include one or more of Wi-Fi, Bluetooth, Near Field Communication (NFC), or other network devices including one or more wireless devices.

[0304] In at least one embodiment, the computer system 1700 may include other components not explicitly shown, such as USB or other port connections, optical storage drives, video capture devices, etc., which may also be connected to the I / O hub 1707. In at least one embodiment, the interconnection may be implemented using any suitable protocol, such as a PCI (Peripheral Component Interconnect) based protocol (e.g., PCI-Express) or other bus or point-to-point communication interface and / or protocol. Figure 17 The communication paths of the various components, such as NV-Link high-speed interconnect or interconnect protocols.

[0305] In at least one embodiment, one or more parallel processors 1712 include circuitry optimized for graphics and video processing, including, for example, video output circuitry, and constituting a graphics processing unit (GPU). In at least one embodiment, one or more parallel processors 1712 include circuitry optimized for general-purpose processing. In at least one embodiment, components of the computer system 1700 may be integrated with one or more other system elements on a single integrated circuit. For example, in at least one embodiment, one or more parallel processors 1712, memory hub 1705, processor 1702, and I / O hub 1707 may be integrated into a system-on-a-chip (SoC) integrated circuit. In at least one embodiment, components of the computer system 1700 may be integrated into a single package to form a system-in-package (SIP) configuration. In at least one embodiment, at least a portion of the components of the computer system 1700 may be integrated into a multi-chip module (MCM) that can interconnect with other MCMs to a modular computer system.

[0306] In at least one embodiment, the parallel processor 1712 can be used to implement a wireless network, such as the MIMO network described above. In at least one embodiment, the parallel processor 1712 can implement, as... Figure 6 The control data thread, user data thread, and beamforming weight calculation thread are shown.

[0307] processor

[0308] Figure 18A A parallel processor 1800 according to at least one embodiment is illustrated. In at least one embodiment, various components of the parallel processor 1800 may be implemented using one or more integrated circuit devices, such as programmable processors, application-specific integrated circuits (ASICs), or field-programmable gate arrays (FPGAs). In at least one embodiment, the illustrated parallel processor 1800 is according to an exemplary embodiment. Figure 17 The variants shown are of one or more parallel processors 1712.

[0309] In at least one embodiment, the parallel processor 1800 includes a parallel processing unit 1802. In at least one embodiment, the parallel processing unit 1802 includes an I / O unit 1804 that enables communication with other devices, including other instances of the parallel processing unit 1802. In at least one embodiment, the I / O unit 1804 can be directly connected to other devices. In at least one embodiment, the I / O unit 1804 is connected to other devices using a hub or switch interface (e.g., a memory hub 1705). In at least one embodiment, the connection between the memory hub 1705 and the I / O unit 1804 forms a communication link 1713. In at least one embodiment, the I / O unit 1804 is connected to a host interface 1806 and a memory crossbar switch 1816, wherein the host interface 1806 receives commands for performing processing operations, and the memory crossbar switch 1816 receives commands for performing memory operations.

[0310] In at least one embodiment, when host interface 1806 receives a command buffer via I / O unit 1804, host interface 1806 can direct work operations to execute those commands to front end 1808. In at least one embodiment, front end 1808 is coupled to scheduler 1810, which is configured to assign commands or other work items to processing cluster array 1812. In at least one embodiment, scheduler 1810 ensures that processing cluster array 1812 is correctly configured and in an active state before assigning tasks to processing cluster array 1812. In at least one embodiment, scheduler 1810 is implemented via firmware logic executed on a microcontroller. In at least one embodiment, the microcontroller-implemented scheduler 1810 can be configured to perform complex scheduling and work assignment operations at both coarse and fine granular levels, thereby enabling fast preemption and context switching of threads executing on processing array 1812. In at least one embodiment, host software can demonstrate workloads scheduled on processing array 1812 via one of a plurality of graphics processing doorbells. In at least one embodiment, the workload can then be automatically distributed on the processing array 1812 by the scheduler 1810 logic within the microcontroller, which includes the scheduler 1810.

[0311] In at least one embodiment, the processing cluster array 1812 may include up to "N" processing clusters (e.g., clusters 1814A, 1814B to 1814N). In at least one embodiment, each cluster 1814A-1814N of the processing cluster array 1812 may execute a large number of concurrent threads. In at least one embodiment, the scheduler 1810 may use various scheduling and / or work allocation algorithms to allocate work to the clusters 1814A-1814N of the processing cluster array 1812, which may vary depending on the workload generated by each type of program or computation. In at least one embodiment, scheduling may be handled dynamically by the scheduler 1810, or may be partially assisted by compiler logic during the compilation of program logic configured to be executed by the processing cluster array 1812. In at least one embodiment, different clusters 1814A-1814N of the processing cluster array 1812 may be assigned to process different types of programs or to perform different types of computations.

[0312] In at least one embodiment, the processing cluster array 1812 can be configured to perform various types of parallel processing operations. In at least one embodiment, the processing cluster array 1812 is configured to perform general-purpose parallel computing operations. For example, in at least one embodiment, the processing cluster array 1812 may include logic for performing processing tasks, including filtering video and / or audio data, performing modeling operations, including physical operations, and performing data transformations.

[0313] In at least one embodiment, the processing cluster array 1812 is configured to perform parallel graphics processing operations. In at least one embodiment, the processing cluster array 1812 may include additional logic to support the execution of such graphics processing operations, including but not limited to texture sampling logic for performing texture operations, as well as tessellation logic and other vertex processing logic. In at least one embodiment, the processing cluster array 1812 may be configured to execute shader programs related to graphics processing, such as, but not limited to, vertex shaders, tessellation shaders, geometry shaders, and pixel shaders. In at least one embodiment, the parallel processing unit 1802 may transfer data from system memory via I / O unit 1804 for processing. In at least one embodiment, during processing, the transferred data may be stored in on-chip memory (e.g., parallel processor memory 1822) and then written back to system memory.

[0314] In at least one embodiment, when the parallel processing unit 1802 is used to perform graphics processing, the scheduler 1810 may be configured to divide the processing workload into tasks of approximately equal size to better distribute graphics processing operations among the multiple clusters 1814A-1814N of the processing cluster array 1812. In at least one embodiment, portions of the processing cluster array 1812 may be configured to perform different types of processing. For example, in at least one embodiment, a first portion may be configured to perform vertex shading and topology generation, a second portion may be configured to perform tessellation and geometry shading, and a third portion may be configured to perform pixel shading or other screen-space operations to generate a rendered image for display. In at least one embodiment, intermediate data generated by one or more of the clusters 1814A-1814N may be stored in a buffer to allow intermediate data to be transferred between the clusters 1814A-1814N for further processing.

[0315] In at least one embodiment, the processing cluster array 1812 may receive processing tasks to be executed via a scheduler 1810, which receives commands defining the processing tasks from a front end 1808. In at least one embodiment, the processing task may include an index of data to be processed, such as surface (patch) data, raw data, vertex data, and / or pixel data, as well as state parameters and commands defining how the data is processed (e.g., what program to execute). In at least one embodiment, the scheduler 1810 may be configured to acquire an index corresponding to a task, or may receive an index from the front end 1808. In at least one embodiment, the front end 1808 may be configured to ensure that the processing cluster array 1812 is configured to be active before initiating the workload specified by an incoming command buffer (e.g., a batch buffer, push buffer, etc.).

[0316] In at least one embodiment, each of one or more instances of the parallel processing unit 1802 may be coupled to the parallel processor memory 1822. In at least one embodiment, the parallel processor memory 1822 may be accessed via a memory crossbar switch 1816, which may receive memory requests from the processing cluster array 1812 and the I / O unit 1804. In at least one embodiment, the memory crossbar switch 1816 may be accessed via a memory interface 1818. In at least one embodiment, the memory interface 1818 may include a plurality of partition units (e.g., partition units 1820A, 1820B to 1820N), each of which may be coupled to a portion (e.g., a memory cell) of the parallel processor memory 1822. In at least one embodiment, the plurality of partition units 1820A-1820N are configured to be equal to the number of memory units, such that the first partition unit 1820A has a corresponding first memory unit 1824A, the second partition unit 1820B has a corresponding memory unit 1824B, and the Nth partition unit 1820N has a corresponding Nth memory unit 1824N. In at least one embodiment, the number of partition units 1820A-1820N may not be equal to the number of memory devices.

[0317] In at least one embodiment, memory cells 1824A-1824N may include various types of memory devices, including dynamic random access memory (DRAM) or graphics random access memory, such as synchronous graphics random access memory (SGRAM), including graphics double data rate (GDDR) memory. In at least one embodiment, memory cells 1824A-1824N may also include 3D stacked memory, including but not limited to high bandwidth memory (HBM). In at least one embodiment, rendering targets such as frame buffers or texture maps may be stored across memory cells 1824A-1824N, allowing partitioning cells 1820A-1820N to write portions of each rendering target in parallel, to efficiently utilize the available bandwidth of the parallel processor memory 1822. In at least one embodiment, local instances of the parallel processor memory 1822 may be excluded to facilitate a unified memory design that combines system memory with local cache memory.

[0318] In at least one embodiment, any of the clusters 1814A-1814N of the processing cluster array 1812 can process data to be written to any memory cell 1824A-1824N within the parallel processor memory 1822. In at least one embodiment, the memory crossbar switch 1816 can be configured to transfer the output of each cluster 1814A-1814N to any partition cell 1820A-1820N or another cluster 1814A-1814N, and the clusters 1814A-1814N can perform further processing operations on the output. In at least one embodiment, each cluster 1814A-1814N can communicate with the memory interface 1818 via the memory crossbar switch 1816 to read from or write to various external storage devices. In at least one embodiment, the memory crossbar switch 1816 has a connection to a memory interface 1818 for communication with I / O unit 1804, and a connection to a local instance of parallel processor memory 1822, thereby enabling processing units within different processing clusters 1814A-1814N to communicate with system memory or other memory not local to parallel processing unit 1802. In at least one embodiment, the memory crossbar switch 1816 may use virtual channels to separate traffic flows between clusters 1814A-1814N and partition units 1820A-1820N.

[0319] In at least one embodiment, multiple instances of the parallel processing unit 1802 may be provided on a single insert card, or multiple insert cards may be interconnected. In at least one embodiment, different instances of the parallel processing unit 1802 may be configured to interoperate, even if the different instances have different numbers of processing cores, different numbers of local parallel processor memories, and / or other configuration differences. For example, in at least one embodiment, some instances of the parallel processing unit 1802 may include higher-precision floating-point units relative to other instances. In at least one embodiment, a system combining one or more instances of the parallel processing unit 1802 or the parallel processor 1800 may be implemented in various configurations and form factors, including but not limited to desktop, laptop, or handheld personal computers, servers, workstations, game consoles, and / or embedded systems.

[0320] Figure 18B This is a block diagram of a partitioning unit 1820 according to at least one embodiment. In at least one embodiment, the partitioning unit 1820 is... Figure 18AThis is an example of one of the partitioning units 1820A-1820N. In at least one embodiment, the partitioning unit 1820 includes an L2 cache 1821, a frame buffer interface 1825, and a ROP 1826 (raster operation unit). The L2 cache 1821 is a read / write cache configured to perform load and store operations received from the memory crossbar switch 1816 and the ROP 1826. In at least one embodiment, the L2 cache 1821 outputs read misses and urgent write-back requests to the frame buffer interface 1825 for processing. In at least one embodiment, updates can also be sent to the frame buffer for processing via the frame buffer interface 1825. In at least one embodiment, the frame buffer interface 1825 communicates with memory cells in the parallel processor memory (such as...). Figure 18A It interacts with one of the memory cells 1824A-1824N (e.g., within the parallel processor memory 1822).

[0321] In at least one embodiment, ROP 1826 is a processing unit that performs raster operations such as stenciling, z-testing, blending, etc. In at least one embodiment, ROP 1826 then outputs processed graphics data stored in graphics memory. In at least one embodiment, ROP 1826 includes compression logic to compress depth or color data written to memory and decompress depth or color data read from memory. In at least one embodiment, the compression logic may be lossless compression logic utilizing one or more of a variety of compression algorithms. In at least one embodiment, the type of compression performed by ROP 1826 may vary based on the statistical characteristics of the data to be compressed. For example, in at least one embodiment, incremental color compression is performed based on depth and color data on a per-tile basis.

[0322] In at least one embodiment, ROP 1826 is included within each processing cluster (e.g., Figure 18A Clusters 1814A-1814N are used instead of partition units 1820. In at least one embodiment, read and write requests for pixel data are made via memory crossbar switch 1816 instead of pixel fragment data transfer. In at least one embodiment, the processed graphics data can be displayed on a display device (such as...). Figure 17 One or more display devices 1710) display, routed by processor 1702 for further processing, or by Figure 18A One of the processing entities within the parallel processor 1800 is routed for further processing.

[0323] Figure 18C This is a block diagram of a processing cluster 1814 within a parallel processing unit according to at least one embodiment. In at least one embodiment, the processing cluster is... Figure 18AAn instance of one of the processing clusters 1814A-1814N. In at least one embodiment, the processing cluster 1814 can be configured to execute a number of threads in parallel, wherein the term "thread" refers to an instance of a specific program executing on a particular set of input data. In at least one embodiment, a Single Instruction Multiple Data (SIMD) instruction issuing technique is used to support the parallel execution of a large number of threads without providing multiple independent instruction units. In at least one embodiment, a Single Instruction Multiple Threading (SIMT) technique is used to support the parallel execution of a large number of generally synchronous threads, which uses a common instruction unit configured to issue instructions to a set of processing engines within each processing cluster.

[0324] In at least one embodiment, the operation of the processing cluster 1814 can be controlled by a pipeline manager 1832 that assigns processing tasks to the SIMT parallel processors. In at least one embodiment, the pipeline manager 1832... Figure 18A The scheduler 1810 receives instructions and manages the execution of these instructions via the graphics multiprocessor 1834 and / or texture unit 1836. In at least one embodiment, the graphics multiprocessor 1834 is an exemplary instance of a SIMT parallel processor. However, in at least one embodiment, the processing cluster 1814 may include various types of SIMT parallel processors with different architectures. In at least one embodiment, the processing cluster 1814 may include one or more instances of the graphics multiprocessor 1834. In at least one embodiment, the graphics multiprocessor 1834 can process data, and the data cross switch 1840 can be used to distribute the processed data to one of a number of possible destinations, including other shader units. In at least one embodiment, the pipeline manager 1832 can facilitate the distribution of processed data by specifying the destination of the processed data to be distributed via the data cross switch 1840.

[0325] In at least one embodiment, each graphics multiprocessor 1834 within the processing cluster 1814 may include the same set of functional execution logic (e.g., arithmetic logic units, load-memory units, etc.). In at least one embodiment, the functional execution logic may be configured in a pipelined manner, wherein new instructions may be issued before previous instructions complete. In at least one embodiment, the functional execution logic supports a variety of operations, including integer and floating-point arithmetic, comparison operations, Boolean operations, shift operations, and computation of various algebraic functions. In at least one embodiment, the same functional unit hardware may be used to perform different operations, and any combination of functional units may exist.

[0326] In at least one embodiment, instructions sent to the processing cluster 1814 constitute threads. In at least one embodiment, a group of threads executed across a set of parallel processing engines is a thread group. In at least one embodiment, the thread group executes programs on different input data. In at least one embodiment, each thread within the thread group may be assigned to a different processing engine within the graphics multiprocessor 1834. In at least one embodiment, the thread group may include fewer threads than the number of processing engines within the graphics multiprocessor 1834. In at least one embodiment, when the number of threads included in the thread group is less than the number of processing engines, one or more processing engines may be idle during a loop that is processing the thread group. In at least one embodiment, the thread group may also include more threads than the number of processing engines within the graphics multiprocessor 1834. In at least one embodiment, when the thread group includes more threads than the number of processing engines within the graphics multiprocessor 1834, processing can be performed in consecutive clock cycles. In at least one embodiment, multiple thread groups can be executed simultaneously on the graphics multiprocessor 1834.

[0327] In at least one embodiment, the graphics multiprocessor 1834 includes an internal cache memory for performing load and store operations. In at least one embodiment, the graphics multiprocessor 1834 may forgo the internal cache and use a cache memory within the processing cluster 1814 (e.g., L1 cache 1848). In at least one embodiment, each graphics multiprocessor 1834 may also access partition units (e.g., Figure 18A The L2 cache is located within partition units 1820A-1820N, which are shared among all processing clusters 1814 and can be used to transfer data between threads. In at least one embodiment, the graphics multiprocessor 1834 can also access off-chip global memory, which may include one or more of local parallel processor memory and / or system memory. In at least one embodiment, any memory outside of the parallel processing unit 1802 can be used as global memory. In at least one embodiment, the processing cluster 1814 includes multiple instances of the graphics multiprocessor 1834, which can share common instructions and data that can be stored in the L1 cache 1848.

[0328] In at least one embodiment, each processing cluster 1814 may include a memory management unit (“MMU”) 1845 configured to map virtual addresses to physical addresses. In at least one embodiment, one or more instances of the MMU 1845 may reside in Figure 18AThe memory interface 1818 is located within the MMU 1845. In at least one embodiment, the MMU 1845 includes a set of page table entries (PTEs) for mapping virtual addresses to physical addresses of tiles (more specifically, tiling) and optionally to cache line indices. In at least one embodiment, the MMU 1845 may include an address translation lookahead buffer (TLB) or a cache that may reside within the graphics multiprocessor 1834 or the L1 cache or processing cluster 1814. In at least one embodiment, physical addresses are processed to allocate surface data access locality for efficient request interleaving between partition units. In at least one embodiment, cache line indices may be used to determine whether a request for a cache line is a hit or a miss.

[0329] In at least one embodiment, the processing cluster 1814 can be configured such that each graphics multiprocessor 1834 is coupled to a texture unit 1836 to perform texture mapping operations that determine texture sample locations, read texture data, and filter texture data. In at least one embodiment, texture data is read as needed from an internal texture L1 cache (not shown) or from an L1 cache within the graphics multiprocessor 1834, and texture data is also retrieved from an L2 cache, local parallel processor memory, or system memory. In at least one embodiment, each graphics multiprocessor 1834 outputs a processed task to a data crossbar switch 1840 to provide the processed task to another processing cluster 1814 for further processing or to store the processed task in an L2 cache, local parallel processor memory, or system memory via a memory crossbar switch 1816. In at least one embodiment, a PreROP 1842 (pre-raster operation unit) is configured to receive data from the graphics multiprocessor 1834 and direct the data to a ROP unit, which can be coupled with the partitioning unit described herein (e.g., Figure 18A The PreROP 1842 unit is located together with the partitioning units 1820A-1820N. In at least one embodiment, the PreROP 1842 unit can perform optimizations for color blending, organize pixel color data, and perform address translation.

[0330] In at least one embodiment, the processing cluster 1814 can be used to implement a wireless network, such as the MIMO network described above. In at least one embodiment, the processing cluster 1814 can implement... Figure 6 The control data thread, user data thread, and beamforming weight calculation thread are shown.

[0331] Figure 18DA graphics multiprocessor 1834 according to at least one embodiment is illustrated. In at least one embodiment, the graphics multiprocessor 1834 is coupled to a pipeline manager 1832 of a processing cluster 1814. In at least one embodiment, the graphics multiprocessor 1834 has an execution pipeline including, but not limited to, an instruction cache 1852, an instruction unit 1854, an address mapping unit 1856, a register file 1858, one or more general-purpose graphics processing unit (GPGPU) cores 1862, and one or more load / store units 1866. The GPGPU cores 1862 and the load / store units 1866 are coupled to a cache memory 1872 and a shared memory 1870 via a memory and cache interconnect 1868.

[0332] In at least one embodiment, instruction cache 1852 receives a stream of instructions to be executed from pipeline manager 1832. In at least one embodiment, instructions are cached in instruction cache 1852 and dispatched to instruction unit 1854 for execution. In one embodiment, instruction unit 1854 may dispatch instructions as thread groups (e.g., thread bundles), assigning each thread of the thread group to a different execution unit within GPGPU core 1862. In at least one embodiment, instructions can access any local, shared, or global address space by specifying an address within a unified address space. In at least one embodiment, address mapping unit 1856 may be used to translate addresses in the unified address space into different memory addresses that can be accessed by load / store unit 1866.

[0333] In at least one embodiment, register file 1858 provides a set of registers for functional units of graphics multiprocessor 1834. In at least one embodiment, register file 1858 provides temporary storage for operands of data paths connected to functional units of graphics multiprocessor 1834 (e.g., GPGPU core 1862, load / store unit 1866). In at least one embodiment, register file 1858 is partitioned among each functional unit, such that a dedicated portion of register file 1858 is allocated to each functional unit. In at least one embodiment, register file 1858 is partitioned among different thread bundles being executed by graphics multiprocessor 1834.

[0334] In at least one embodiment, the GPGPU core 1862 may each include a floating-point unit (FPU) and / or an integer arithmetic logic unit (ALU) for executing instructions of the graphics multiprocessor 1834. The GPGPU cores 1862 may be architecturally similar or may differ in architecture. In at least one embodiment, a first portion of the GPGPU core 1862 includes a single-precision FPU and an integer ALU, while a second portion of the GPGPU core includes a double-precision FPU. In at least one embodiment, the FPU may implement the IEEE 754-2008 standard for floating-point algorithms or enable variable-precision floating-point algorithms. In at least one embodiment, the graphics multiprocessor 1834 may additionally include one or more fixed-function or special-function units to perform specific functions, such as copying rectangles or pixel blending operations. In at least one embodiment, one or more of the GPGPU cores may also include fixed-function or special-function logic.

[0335] In at least one embodiment, the GPGPU core 1862 includes SIMD logic capable of executing a single instruction on multiple sets of data. In one embodiment, the GPGPU core 1862 can physically execute SIMD4, SIMD8, and SIMD16 instructions, and logically execute SIMD1, SIMD2, and SIMD32 instructions. In at least one embodiment, the SIMD instructions for the GPGPU core can be generated by a shader compiler at compile time, or automatically generated when executing a program written and compiled for a Single Program Multiple Data (SPMD) or SIMT architecture. In at least one embodiment, multiple threads of a program configured for a SIMT execution model can be executed using a single SIMD instruction. For example, in at least one embodiment, eight SIMD threads performing the same or similar operations can be executed in parallel using a single SIMD8 logic unit.

[0336] In at least one embodiment, the memory and cache interconnect 1868 is an interconnect network connecting each functional unit of the graphics multiprocessor 1834 to the register file 1858 and the shared memory 1870. In at least one embodiment, the memory and cache interconnect 1868 is a cross-switch interconnect that allows the load / store unit 1866 to perform load and store operations between the shared memory 1870 and the register file 1858. In at least one embodiment, the register file 1858 can operate at the same frequency as the GPGPU core 1862, resulting in very low latency for data transfer between the GPGPU core 1862 and the register file 1858. In at least one embodiment, the shared memory 1870 can be used to enable communication between threads executing on functional units within the graphics multiprocessor 1834. In at least one embodiment, the cache memory 1872 can be used, for example, as a data cache to cache texture data communicated between functional units and texture units 1836. In at least one embodiment, the shared memory 1870 can also be used as a program-managed cache. In at least one embodiment, in addition to the data automatically cached in cache memory 1872, the thread executing on GPGPU core 1862 can also programmatically store data in shared memory.

[0337] In at least one embodiment, a parallel processor or GPGPU, as described herein, is communicatively coupled to a host / processor core to accelerate graphics operations, machine learning operations, pattern analysis operations, and various general-purpose GPU (GPGPU) functions. In at least one embodiment, the GPU may be communicatively coupled to the host processor / core via a bus or other interconnect (e.g., high-speed interconnects such as PCIe or NVLink). In at least one embodiment, the GPU may be integrated with the core on the same package or chip and communicatively coupled to the core via an internal processor bus / interconnect (i.e., within the package or chip). In at least one embodiment, regardless of how the GPU is connected, the processor core may assign work to the GPU in the form of a sequence of commands / instructions contained in a job descriptor. In at least one embodiment, the GPU then uses dedicated circuitry / logic to efficiently process these commands / instructions.

[0338] In at least one embodiment, the GPGPU core 1862 can be used to implement wireless networks, such as the MIMO network described above. In at least one embodiment, the GPGPU core 1862 can implement, for example... Figure 6 The control data thread, user data thread, and beamforming weight calculation thread are shown.

[0339] Figure 19A multi-GPU computing system 1900 according to at least one embodiment is illustrated. In at least one embodiment, the multi-GPU computing system 1900 may include a processor 1902 coupled to a plurality of general-purpose graphics processing units (GPGPUs) 1906A-D via a host interface switch 1904. In at least one embodiment, the host interface switch 1904 is a PCI Express switch device that couples the processor 1902 to a PCI Express bus, through which the processor 1902 can communicate with the GPGPUs 1906A-D. The GPGPUs 1906A-D may be interconnected via a set of high-speed P2P GPU-to-GPU links 1916. In at least one embodiment, the GPU-to-GPU links 1916 are connected to each of the GPGPUs 1906A-D via dedicated GPU links. In at least one embodiment, the P2P GPU links 1916 enable direct communication between each of the GPGPUs 1906A-D without communication via the host interface bus 1904 to which the processor 1902 is connected. In at least one embodiment, when GPU-to-GPU traffic is directed to the P2P GPU link 1916, the host interface bus 1904 remains available for system memory access or, for example, communication with other instances of the multi-GPU computing system 1900 via one or more network devices. While in at least one embodiment, the GPGPUs 1906A-D are connected to the processor 1902 via the host interface switch 1904, in at least one embodiment, the processor 1902 includes direct support for the P2P GPU link 1916 and can be directly connected to the GPGPUs 1906A-D.

[0340] In at least one embodiment, the multi-GPU computing system 1900 can be used to implement a wireless network, such as the MIMO network described above. In at least one embodiment, the multi-GPU computing system 1900 can implement, as... Figure 6 The control data thread, user data thread, and beamforming weight calculation thread are shown.

[0341] Figure 20 This is a block diagram of a graphics processor 2000 according to at least one embodiment. In at least one embodiment, the graphics processor 2000 includes a ring interconnect 2002, a pipeline front end 2004, a media engine 2037, and graphics cores 2080A-2080N. In at least one embodiment, the ring interconnect 2002 couples the graphics processor 2000 to other processing units, said processing units including other graphics processors or one or more general-purpose processor cores. In at least one embodiment, the graphics processor 2000 is one of many processors integrated within a multi-core processing system.

[0342] In at least one embodiment, the graphics processor 2000 receives multiple batches of commands via a ring interconnect 2002. In at least one embodiment, the input commands are interpreted by a command streamer 2003 in a pipeline front-end 2004. In at least one embodiment, the graphics processor 2000 includes scalable execution logic for performing 3D geometry processing and media processing via graphics cores 2080A-2080N. In at least one embodiment, for 3D geometry processing commands, the command streamer 2003 provides the commands to the geometry pipeline 2036. In at least one embodiment, for at least some media processing commands, the command streamer 2003 provides the commands to a video front-end 2034, which is coupled to a media engine 2037. In at least one embodiment, the media engine 2037 includes a video quality engine (VQE) 2030 for video and image post-processing, and a multi-format encoding / decoding (MFX) engine 2033 for providing hardware-accelerated media data encoding and decoding. In at least one embodiment, the geometry pipeline 2036 and the media engine 2037 each generate an execution thread for thread execution resources provided by at least one graphics core 2080A.

[0343] In at least one embodiment, the graphics processor 2000 includes scalable thread execution resources featuring modular cores 2080A-2080N (sometimes referred to as core slices), each graphics core having multiple sub-cores 2050A-2050N, 2060A-2060N (sometimes referred to as core sub-slices). In at least one embodiment, the graphics processor 2000 may have any number of graphics cores 2080A to 2080N. In at least one embodiment, the graphics processor 2000 includes a graphics core 2080A having at least a first sub-core 2050A and a second sub-core 2060A. In at least one embodiment, the graphics processor 2000 is a low-power processor having a single sub-core (e.g., 2050A). In at least one embodiment, the graphics processor 2000 includes multiple graphics cores 2080A-2080N, each graphics core including a set of first sub-cores 2050A-2050N and a set of second sub-cores 2060A-2060N. In at least one embodiment, each of the first sub-cores 2050A-2050N includes at least a first set of execution units 2052A-2052N and media / texture samplers 2054A-2054N. In at least one embodiment, each of the second sub-cores 2060A-2060N includes at least a second set of execution units 2062A-2062N and samplers 2064A-2064N. In at least one embodiment, each of the sub-cores 2050A-2050N and 2060A-2060N shares a set of shared resources 2070A-2070N. In at least one embodiment, the shared resources include a shared cache memory and pixel operation logic.

[0344] In at least one embodiment, the graphics processor 2000 can be used to implement a wireless network, such as the MIMO network described above. In at least one embodiment, the graphics processor 2000 can implement, for example... Figure 6 The control data thread, user data thread, and beamforming weight calculation thread are shown.

[0345] Figure 21 This is a block diagram illustrating a microarchitecture for a processor 2100 according to at least one embodiment, the processor 2100 including logic circuitry for executing instructions. In at least one embodiment, the processor 2100 can execute instructions, including x86 instructions, ARM instructions, and special-purpose instructions for application-specific integrated circuits (ASICs). In at least one embodiment, the processor 2100 may include registers for storing packaged data, such as the 64-bit wide MMX registers used in Intel Corporation's Santa Clara, California-enabled MMX technology microprocessors. TMRegisters. In at least one embodiment, MMX registers available in integer and floating-point forms can operate with packaged data elements accompanying Single Instruction Multiple Data (“SIMD”) and Streaming SIMD Extensions (“SSE”) instructions. In at least one embodiment, a 128-bit wide XMM register associated with SSE2, SSE3, SSE4, AVX, or later (generally referred to as “SSEx”) technologies can hold such packaged data operands. In at least one embodiment, processor 2110 can execute instructions to accelerate machine learning or deep learning algorithms, training, or inference.

[0346] In at least one embodiment, processor 2100 includes an ordered front end (“front end”) 2101 to fetch instructions to be executed and prepare instructions for later use in the processor pipeline. In at least one embodiment, front end 2101 may include several units. In at least one embodiment, instruction prefetcher 2126 fetches instructions from memory and provides the instructions to instruction decoder 2128, which in turn decodes or interprets the instructions. For example, in at least one embodiment, instruction decoder 2128 decodes the received instructions into one or more machine-executable so-called “micro-instructions” or “micro-operations” (also referred to as “micro-operations” or “micro-instructions”). In at least one embodiment, instruction decoder 2128 parses the instructions into opcodes and corresponding data and control fields, which can be used by the microarchitecture to perform operations according to at least one embodiment. In at least one embodiment, trace cache 2130 may assemble the decoded micro-instructions into a program-ordered sequence or trace in micro-instruction queue 2134 for execution. In at least one embodiment, when trace cache 2130 encounters complex instructions, microcode ROM 2132 provides the micro-instructions required to complete the operation.

[0347] In at least one embodiment, some instructions may be converted into a single micro-operation, while others require several micro-operations to complete the entire operation. In at least one embodiment, if more than four micro-instructions are required to complete an instruction, the instruction decoder 2128 may access the microcode ROM 2132 to execute the instruction. In at least one embodiment, an instruction may be decoded into a small number of micro-instructions for processing at the instruction decoder 2128. In at least one embodiment, if multiple micro-instructions are required to complete the operation, the instructions may be stored in the microcode ROM 2132. In at least one embodiment, the trace cache 2130 references an entry point programmable logic array (“PLA”) to determine the correct micro-instruction pointer for reading a microcode sequence from the microcode ROM 2132 to complete one or more instructions, according to at least one embodiment. In at least one embodiment, after the microcode ROM 2132 has completed the micro-operation ordering of the instructions, the machine front end 2101 may resume fetching micro-operations from the trace cache 2130.

[0348] In at least one embodiment, the out-of-order execution engine (“out-of-order engine”) 2103 can prepare instructions for execution. In at least one embodiment, the out-of-order execution logic has multiple buffers to smooth and reorder the instruction flow to optimize performance as instructions descend the pipeline and are scheduled for execution. The out-of-order execution engine 2103 includes, but is not limited to, an allocator / register renamer 2140, a memory microinstruction queue 2142, an integer / floating-point microinstruction queue 2144, a memory scheduler 2146, a fast scheduler 2102, a slow / general-purpose floating-point scheduler (“slow / general-purpose FP scheduler”) 2104, and a simple floating-point scheduler (“simple FP scheduler”) 2106. In at least one embodiment, the fast scheduler 2102, the slow / general-purpose floating-point scheduler 2104, and the simple floating-point scheduler 2106 are also collectively referred to as “microinstruction schedulers 2102, 2104, 2106”. In at least one embodiment, the allocator / register renamer 2140 allocates the machine buffers and resources required for each microinstruction to be executed sequentially. In at least one embodiment, allocator / register renaming unit 2140 renames logical registers to entries in a register file. In at least one embodiment, allocator / register renaming unit 2140 also assigns entries for each microinstruction in one of two microinstruction queues, memory microinstruction queue 2142 for memory operations and integer / floating-point microinstruction queue 2144 for non-memory operations, preceding memory scheduler 2146 and microinstruction schedulers 2102, 2104, 2106. In at least one embodiment, microinstruction schedulers 2102, 2104, 2106 determine when they are ready to execute a microinstruction based on the readiness of their dependent input register operand sources and the availability of the execution resource microinstructions that need to be completed. In at least one embodiment, fast scheduler 2102 can schedule on each half of the master clock cycle, while slow / general-purpose floating-point scheduler 2104 and simple floating-point scheduler 2106 can schedule once per master processor clock cycle. In at least one embodiment, microinstruction schedulers 2102, 2104, and 2106 arbitrate the scheduling ports to schedule microinstructions for execution.

[0349] In at least one embodiment, execution block 2111 includes, but is not limited to, integer register file / branch network 2108, floating-point register file / branch network (“FP register file / branch network”) 2110, address generation units (“AGU”) 2112 and 2114, fast arithmetic logic units (“fast ALU”) 2116 and 2118, slow arithmetic logic unit (“slow ALU”) 2120, floating-point ALU (“FP”) 2122, and floating-point movement unit (“FP movement”) 2124. In at least one embodiment, integer register file / branch network 2108 and floating-point register file / bypass network 2110 are also referred to herein as “register files 2108, 2110”. In at least one embodiment, AGUs 2112 and 2114, fast ALUs 2116 and 2118, slow ALU 2120, floating-point ALU 2122, and floating-point movement unit 2124 are also referred to herein as "execution units 2112, 2114, 2116, 2118, 2120, 2122, and 2124". In at least one embodiment, execution block 2111 may include, but is not limited to, any number (including zero) and type of register files, branch networks, address generation units, and execution units (in any combination).

[0350] In at least one embodiment, register files 2108, 2110 may be arranged between microinstruction schedulers 2102, 2104, 2106 and execution units 2112, 2114, 2116, 2118, 2120, 2122, and 2124. In at least one embodiment, integer register file / tribute network 2108 performs integer operations. In at least one embodiment, floating-point register file / tribute network 2110 performs floating-point operations. In at least one embodiment, each of register files 2108, 2110 may include, but is not limited to, a tribute network that can bypass or forward recently completed results not yet written to the register file to a new dependent object. In at least one embodiment, register files 2108, 2110 may communicate data with each other. In at least one embodiment, integer register file / tribute network 2108 may include, but is not limited to, two separate register files, one register file for low-order 32-bit data and a second register file for high-order 32-bit data. In at least one embodiment, the floating-point register file / branch network 2110 may include, but is not limited to, entries with a width of 128 bits, since floating-point instructions typically have operands with a width of 64 to 128 bits.

[0351] In at least one embodiment, execution units 2112, 2114, 2116, 2118, 2120, 2122, and 2124 can execute instructions. In at least one embodiment, register files 2108 and 2110 store integer and floating-point data operation values ​​that the microinstructions need to execute. In at least one embodiment, processor 2100 may include, but is not limited to, any number of execution units 2112, 2114, 2116, 2118, 2120, 2122, and 2124, and combinations thereof. In at least one embodiment, floating-point ALU 2122 and floating-point move unit 2124 can perform floating-point, MMX, SIMD, AVX, and SSE or other operations, including specialized machine learning instructions. In at least one embodiment, floating-point ALU 2122 may include, but is not limited to, a 64-bit multiplication-64-bit floating-point divider to perform division, square root, and remainder micro-operations. In at least one embodiment, floating-point hardware can be used to process instructions involving floating-point values. In at least one embodiment, ALU operations can be passed to fast ALUs 2116 and 2118. In at least one embodiment, fast ALUs 2116 and 2118 can perform fast operations with an effective delay of half a clock cycle. In at least one embodiment, most complex integer operations are routed to slow ALU 2120, because slow ALU 2120 can include, but is not limited to, integer execution hardware for long-latency type operations, such as multipliers, shifters, flag logic, and branching. In at least one embodiment, memory load / store operations can be performed by AGUS 2112 and 2114. In at least one embodiment, fast ALU 2116, fast ALU 2118, and slow ALU 2120 can perform integer operations on 64-bit data operands. In at least one embodiment, fast ALU 2116, fast ALU 2118, and slow ALU 2120 can be implemented to support various data bit sizes, including sixteen, thirty-two, 128, 256, etc. In at least one embodiment, the floating-point ALU 2122 and the floating-point movement unit 2124 can be implemented to support a range of operands with various bit widths. In at least one embodiment, the floating-point ALU 2122 and the floating-point movement unit 2124 can operate on 128-bit wide packaged data operands in conjunction with SIMD and multimedia instructions.

[0352] In at least one embodiment, microinstruction schedulers 2102, 2104, and 2106 schedule dependent operations before the parent load completes execution. In at least one embodiment, since microinstructions can be speculatively scheduled and executed within processor 2100, processor 2100 may also include logic for handling memory misses. In at least one embodiment, if a data load miss occurs in the data cache, there may be a dependent operation running in the pipeline that temporarily deprives the scheduler of the correct data. In at least one embodiment, a replay mechanism tracks and re-executes instructions that use incorrect data. In at least one embodiment, it may be necessary to replay dependent operations and may allow independent operations to be completed. In at least one embodiment, the scheduler and replay mechanism of at least one embodiment of the processor may also be designed to capture instruction sequences for text string comparison operations.

[0353] In at least one embodiment, the term "register" may refer to an onboard processor storage location that can be used as part of an instruction that identifies an operand. In at least one embodiment, a register may be one that can be used from outside the processor (from a programmer's perspective). In at least one embodiment, a register may not be limited to a particular type of circuitry. Rather, in at least one embodiment, a register may store data, provide data, and perform the functions described herein. In at least one embodiment, the registers described herein may be implemented using a variety of different techniques via circuitry within the processor, such as dedicated physical registers, dynamically allocated physical registers renamed using register renaming, a combination of dedicated and dynamically allocated physical registers, etc. In at least one embodiment, an integer register stores 32-bit integer data. The register file of at least one embodiment also includes eight multimedia SIMD registers for encapsulating data.

[0354] In at least one embodiment, processor 2100 can be used to implement a wireless network, such as the MIMO network described above. In at least one embodiment, processor 2100 can implement, for example, Figure 6 The control data thread, user data thread, and beamforming weight calculation thread are shown.

[0355] Figure 22 A block diagram of a processing system according to at least one embodiment is shown. In at least one embodiment, system 2200 includes one or more processors 2202 and one or more graphics processors 2208, and may be a single-processor desktop system, a multi-processor workstation system, or a server system having a large number of processors 2202 or processor cores 2207. In at least one embodiment, system 2200 is a processing platform incorporated within a system-on-a-chip (SoC) integrated circuit for use in mobile, handheld, or embedded devices.

[0356] In at least one embodiment, system 2200 may include or be integrated into a server-based gaming platform, including a game console, mobile game console, handheld game console, or online game console, which are game and media consoles. In at least one embodiment, system 2200 is a mobile phone, smartphone, tablet computing device, or mobile internet device. In at least one embodiment, processing system 2200 may also include components coupled to or integrated into a wearable device, such as a smartwatch wearable device, smart glasses device, augmented reality device, or virtual reality device. In at least one embodiment, processing system 2200 is a television or set-top box device having one or more processors 2202 and a graphical interface generated by one or more graphics processors 2208.

[0357] In at least one embodiment, each of the one or more processors 2202 includes one or more processor cores 2207 to process instructions that, when executed, perform operations against the system and user software. In at least one embodiment, each of the one or more processor cores 2207 is configured to process a particular instruction set 2209. In at least one embodiment, the instruction set 2209 may facilitate Complex Instruction Set Computing (CISC), Reduced Instruction Set Computing (RISC), or computation via Very Long Instruction Word (VLIW). In at least one embodiment, each processor core 2207 may process a different instruction set 2209, which may include instructions that facilitate the emulation of other instruction sets. In at least one embodiment, the processor core 2207 may also include other processing devices, such as a digital signal processor (DSP).

[0358] In at least one embodiment, processor 2202 includes cache memory 2204. In at least one embodiment, processor 2202 may have a single internal cache or multiple levels of internal caches. In at least one embodiment, the cache memory is shared among various components of processor 2202. In at least one embodiment, processor 2202 also uses an external cache (e.g., a Level 3 (L3) cache or a last-level cache (LLC)) (not shown), which can be shared among processor cores 2207 using known cache coherence techniques. In at least one embodiment, processor 2202 further includes a register file 2206, which may include different types of registers for storing different types of data (e.g., integer registers, floating-point registers, status registers, and instruction pointer registers). In at least one embodiment, register file 2206 may include general-purpose registers or other registers.

[0359] In at least one embodiment, one or more processors 2202 are coupled to one or more interface buses 2210 to transmit communication signals, such as address, data, or control signals, between the processors 2202 and other components in the system 2200. In at least one embodiment, the interface bus 2210 may be a processor bus, such as a version of the Direct Media Interface (DMI) bus. In at least one embodiment, the interface 2210 is not limited to the DMI bus and may include one or more peripheral component interconnect buses (e.g., PCI, PCI Express), memory buses, or other types of interface buses. In at least one embodiment, the processor 2202 includes an integrated memory controller 2216 and a platform controller hub 2230. In at least one embodiment, the memory controller 2216 facilitates communication between memory devices and other components of the processing system 2200, while the platform controller hub (PCH) 2230 provides connectivity to input / output (I / O) devices via a local I / O bus.

[0360] In at least one embodiment, memory device 2220 may be a dynamic random access memory (DRAM) device, a static random access memory (SRAM) device, a flash memory device, a phase-change memory device, or a device with suitable performance for use as processor memory. In at least one embodiment, memory device 2220 may be used as system memory of processing system 2200 to store data 2222 and instructions 2221 for use when one or more processors 2202 execute an application or process. In at least one embodiment, memory controller 2216 is also coupled to an optional external graphics processor 2212, which may communicate with one or more graphics processors 2208 of processor 2202 to perform graphics and media operations. In at least one embodiment, display device 2211 may be connected to processor 2202. In at least one embodiment, display device 2211 may include one or more internal display devices, such as in mobile electronic devices or laptop devices, or external display devices connected via a display interface (e.g., DisplayPort). In at least one embodiment, the display device 2211 may include a head-mounted display (HMD), such as a stereoscopic display device for virtual reality (VR) or augmented reality (AR) applications.

[0361] In at least one embodiment, the platform controller hub 2230 enables peripheral devices to connect to the storage device 2220 and the processor 2202 via a high-speed I / O bus. In at least one embodiment, the I / O peripheral devices include, but are not limited to, an audio controller 2246, a network controller 2234, a firmware interface 2228, a wireless transceiver 2226, a touch sensor 2225, and a data storage device 2224 (e.g., a hard drive, flash memory, etc.). In at least one embodiment, the data storage device 2224 may be connected via a storage interface (e.g., SATA) or via a peripheral bus, such as a peripheral component interconnect bus (e.g., PCI, PCIe). In at least one embodiment, the touch sensor 2225 may include a touchscreen sensor, a pressure sensor, or a fingerprint sensor. In at least one embodiment, the wireless transceiver 2226 may be a Wi-Fi transceiver, a Bluetooth transceiver, or a mobile network transceiver, such as a 3G, 4G, or LTE transceiver. In at least one embodiment, the firmware interface 2228 enables communication with the system firmware and may be, for example, a Unified Extensible Firmware Interface (UEFI). In at least one embodiment, network controller 2234 may enable network connectivity to a wired network. In at least one embodiment, a high-performance network controller (not shown) is coupled to interface bus 2210. In at least one embodiment, audio controller 2246 is a multi-channel high-definition audio controller. In at least one embodiment, processing system 2200 includes an optional legacy I / O controller 2240 for coupling legacy (e.g., Personal System 2 (PS / 2)) devices to system 2200. In at least one embodiment, platform controller hub 2230 may also be connected to one or more Universal Serial Bus (USB) controllers 2242 that connect input devices, such as a keyboard and mouse combination 2243, a camera 2244, or other USB input devices.

[0362] In at least one embodiment, instances of the memory controller 2216 and platform controller hub 2230 may be integrated into a discrete external graphics processor, such as external graphics processor 2212. In at least one embodiment, the platform controller hub 2230 and / or the memory controller 2216 may be external to one or more processors 2202. For example, in at least one embodiment, system 2200 may include external memory controller 2216 and platform controller hub 2230, which may be configured as a memory controller hub and peripheral controller hub in a system chipset communicating with processor 2202.

[0363] In at least one embodiment, system 2200 can be used to implement a wireless network, such as the MIMO network described above. In at least one embodiment, system 2200 can implement... Figure 6The control data thread, user data thread, and beamforming weight calculation thread are shown.

[0364] Figure 23 This is a block diagram of a processor 2300 having one or more processor cores 2302A-2302N, an integrated memory controller 2314, and an integrated graphics processor 2308 according to at least one embodiment. In at least one embodiment, the processor 2300 may include additional cores, up to and including additional cores 2302N indicated by dashed boxes. In at least one embodiment, each processor core 2302A-2302N includes one or more internal cache units 2304A-2304N. In at least one embodiment, each processor core may also access one or more shared cache units 2306.

[0365] In at least one embodiment, internal cache units 2304A-2304N and shared cache unit 2306 represent a cache memory hierarchy within processor 2300. In at least one embodiment, cache memory units 2304A-2304N may include at least one level of instruction and data cache within each processor core and one or more levels of cache in a shared intermediate cache, such as Level 2 (L2), Level 3 (L3), Level 4 (L4), or other levels of cache, wherein the highest level of cache preceding external memory is classified as LLC. In at least one embodiment, cache coherence logic maintains coherence between the various cache units 2306 and 2304A-2304N.

[0366] In at least one embodiment, the processor 2300 may further include a set of one or more bus controller units 2316 and a system agent core 2310. In at least one embodiment, the one or more bus controller units 2316 manage a set of peripheral buses, such as one or more PCI or PCIe buses. In at least one embodiment, the system agent core 2310 provides management functions for various processor components. In at least one embodiment, the system agent core 2310 includes one or more integrated memory controllers 2314 to manage access to various external memory devices (not shown).

[0367] In at least one embodiment, one or more processor cores 2302A-2302N include support for concurrent multithreading. In at least one embodiment, system agent core 2310 includes components for coordinating and operating cores 2302A-2302N during multithreaded processing. In at least one embodiment, system agent core 2310 may additionally include a power control unit (PCU) including logic and components for regulating one or more power states of processor cores 2302A-2302N and graphics processor 2308.

[0368] In at least one embodiment, processor 2300 further includes a graphics processor 2308 for performing graph processing operations. In at least one embodiment, graphics processor 2308 is coupled to a shared cache unit 2306 and a system proxy core 2310 including one or more integrated memory controllers 2314. In at least one embodiment, system proxy core 2310 further includes a display controller 2311 for driving graphics processor outputs to one or more coupled displays. In at least one embodiment, display controller 2311 may also be a separate module coupled to graphics processor 2308 via at least one interconnect, or it may be integrated within graphics processor 2308.

[0369] In at least one embodiment, the ring-based interconnect unit 2312 is used to couple internal components of the processor 2300. In at least one embodiment, alternative interconnect units, such as point-to-point interconnects, switched interconnects, or other technologies, may be used. In at least one embodiment, the graphics processor 2308 is coupled to the ring interconnect 2312 via I / O link 2313.

[0370] In at least one embodiment, I / O link 2313 represents at least one of a variety of I / O interconnects, including packaged I / O interconnects that facilitate communication between various processor components and high-performance embedded memory module 2318 (e.g., eDRAM module). In at least one embodiment, each of processor cores 2302A-2302N and graphics processor 2308 uses embedded memory module 2318 as a shared last-level cache.

[0371] In at least one embodiment, processor cores 2302A-2302N are homogeneous cores executing a common instruction set architecture. In at least one embodiment, processor cores 2302A-2302N are heterogeneous in terms of instruction set architecture (ISA), with one or more processor cores 2302A-2302N executing a common instruction set, while one or more other processor cores 2302A-2302N execute a subset of the common instruction set or a different instruction set. In at least one embodiment, processor cores 2302A-2302N are heterogeneous in terms of microarchitecture, with one or more cores having relatively high power consumption coupled to one or more power cores having lower power consumption. In at least one embodiment, processor 2300 may be implemented on one or more chips or implemented as a SoC integrated circuit.

[0372] In at least one embodiment, the processor cores 2302A-2302N can be used to implement wireless networks, such as the MIMO network described above. In at least one embodiment, the processor cores 2302A-2302N can implement control data threads, user data threads, and beamforming weight calculation threads, such as... Figure 6 As shown.

[0373] Figure 24 This is a block diagram of a graphics processor 2400, which may be a discrete graphics processing unit or a graphics processor integrated with multiple processing cores. In at least one embodiment, the graphics processor 2400 communicates with registers on the graphics processor 2400 and commands placed in memory via a memory-mapped I / O interface. In at least one embodiment, the graphics processor 2400 includes a memory interface 2414 for accessing memory. In at least one embodiment, the memory interface 2414 is an interface to local memory, one or more internal caches, one or more shared external caches, and / or to system memory.

[0374] In at least one embodiment, the graphics processor 2400 further includes a display controller 2402 for driving display output data to the display device 2420. In at least one embodiment, the display controller 2402 includes a combination of hardware for one or more overlay planes of the display device 2420 and multi-layer video or user interface elements. In at least one embodiment, the display device 2420 may be an internal or external display device. In at least one embodiment, the display device 2420 is a head-mounted display device, such as a virtual reality (VR) display device or an augmented reality (AR) display device. In at least one embodiment, the graphics processor 2400 includes a video codec engine 2406 for encoding, decoding, or transcoding media into one or more media encoding formats, encoding, decoding, or transcoding from one or more media encoding formats, or encoding, decoding, or transcoding between one or more media encoding formats, including but not limited to Moving Picture Experts Group (MPEG) formats (e.g., MPEG-2), Advanced Video Coding (AVC) formats (e.g., H.264 / MPEG-4 AVC, and SMPTE 421M / VC-1), and Joint Picture Experts Group (JPEG) formats (e.g., JPEG) and MotionJPEG (MJPEG) formats.

[0375] In at least one embodiment, the graphics processor 2400 includes a block image transfer (BLIT) engine 2404 to perform two-dimensional (2D) rasterizer operations, including, for example, bit boundary block transfer. However, in at least one embodiment, one or more components of a graphics processing engine (GPE) 2410 are used to perform 2D graphics operations. In at least one embodiment, the GPE 2410 is a computational engine for performing graphics operations, including three-dimensional (3D) graphics operations and media operations.

[0376] In at least one embodiment, GPE 2410 includes a 3D pipeline 2412 for performing 3D operations, such as rendering 3D images and scenes using processing functions that manipulate 3D primitive shapes (e.g., rectangles, triangles, etc.). The 3D pipeline 2412 includes programmable and fixed function elements that perform various tasks and / or generate execution threads to the 3D / media subsystem 2415. While the 3D pipeline 2412 can be used to perform media operations, in at least one embodiment, GPE 2410 also includes a media pipeline 2416 for performing media operations such as video post-processing and image enhancement.

[0377] In at least one embodiment, the media pipeline 2416 includes fixed-function or programmable logic units for performing one or more specialized media operations, such as video decoding acceleration, video deinterlacing, and video encoding acceleration, replacing or representing the video codec engine 2406. In at least one embodiment, the media pipeline 2416 also includes a thread generation unit for generating threads to execute on the 3D / media subsystem 2415. In at least one embodiment, the generated threads perform computations of media operations on one or more graphics execution units included in the 3D / media subsystem 2415.

[0378] In at least one embodiment, the 3D / media subsystem 2415 includes logic for executing threads generated by the 3D pipeline 2412 and the media pipeline 2416. In at least one embodiment, the 3D pipeline 2412 and the media pipeline 2416 send thread execution requests to the 3D / media subsystem 2415, which includes thread dispatch logic for arbitrating various requests and dispatching them to available thread execution resources. In at least one embodiment, the execution resources include an array of graphics execution units for processing 3D and media threads. In at least one embodiment, the 3D / media subsystem 2415 includes one or more internal caches for thread instructions and data. In at least one embodiment, the subsystem 2415 also includes shared memory, which includes registers and addressable memory for sharing data between threads and storing output data.

[0379] In at least one embodiment, the 3D / media subsystem 2415 can be used to implement a wireless network, such as the MIMO network described above. In at least one embodiment, the 3D / media subsystem 2415 can implement a control data thread, a user data thread, and a beamforming weight calculation thread, such as... Figure 6 As shown.

[0380] Figure 25 This is a block diagram of a graphics processing engine 2510 of a graphics processor according to at least one embodiment. In at least one embodiment, the graphics processing engine (GPE) 2510 is... Figure 24 The version of GPE 2410 shown is illustrated. In at least one embodiment, the media pipeline 2516 is optional and may not be explicitly included in the GPE 2510. In at least one embodiment, a separate media and / or image processor is coupled to the GPE 2510.

[0381] In at least one embodiment, GPE 2510 is coupled to or includes command stream converter 2503, which provides command streams to 3D pipeline 2512 and / or media pipeline 2516. In at least one embodiment, command stream converter 2503 is coupled to memory, which may be system memory, or one or more of internal cache memory and shared cache memory. In at least one embodiment, command stream converter 2503 receives commands from memory and sends the commands to 3D pipeline 2512 and / or media pipeline 2516. In at least one embodiment, the commands are instructions, primitives, or micro-operations retrieved from a circular buffer that stores commands for 3D pipeline 2512 and media pipeline 2516. In at least one embodiment, the circular buffer may further include a batch command buffer storing multiple commands in batches. In at least one embodiment, commands for 3D pipeline 2512 may further include references to data stored in memory, such as, but not limited to, vertex and geometry data for 3D pipeline 2512 and / or image data and memory objects for media pipeline 2516. In at least one embodiment, the 3D pipeline 2512 and the media pipeline 2516 process commands and data by performing operations or by dispatching one or more execution threads to the graphics core array 2514. In at least one embodiment, the graphics core array 2514 includes one or more graphics core blocks (e.g., one or more graphics cores 2515A, one or more graphics cores 2515B), each block including one or more graphics cores. In at least one embodiment, each graphics core includes a set of graphics execution resources, which include general and graphics-specific execution logic for performing graphics and computation operations, as well as fixed-function texture processing and / or machine learning and artificial intelligence acceleration logic.

[0382] In at least one embodiment, the 3D pipeline 2512 includes fixed functions and programmable logic for processing one or more shader programs, such as vertex shaders, geometry shaders, pixel shaders, fragment shaders, compute shaders, or other shader programs, by processing instructions and dispatching execution threads to the graphics core array 2514. In at least one embodiment, the graphics core array 2514 provides a unified execution resource block for processing shader programs. In at least one embodiment, the multipurpose execution logic (e.g., execution units) within the graphics cores 2515A-2515B of the graphics core array 2514 includes support for various 3D API shader languages ​​and can execute multiple concurrently running threads associated with multiple shaders.

[0383] In at least one embodiment, the graphics core array 2514 further includes execution logic for performing media functions, such as video and / or image processing. In at least one embodiment, in addition to graphics processing operations, the execution unit also includes general-purpose logic programmable to perform parallel general-purpose computing operations.

[0384] In at least one embodiment, output data can be output to memory in a unified return buffer (URB) 2518, the output data being generated by a thread executing on the graphics core array 2514. In at least one embodiment, the URB 2518 can store data from multiple threads. In at least one embodiment, the URB 2518 can be used to send data between different threads executing on the graphics core array 2514. In at least one embodiment, the URB 2518 can also be used for synchronization between threads on the graphics core array 2514 and fixed-function logic within shared-function logic 2520.

[0385] In at least one embodiment, the graphics core array 2514 is scalable, such that it includes a variable number of graphics cores, each having a variable number of execution units based on the target power and performance level of the GPE 2510. In at least one embodiment, the execution resources are dynamically scalable, such that they can be enabled or disabled as needed.

[0386] In at least one embodiment, the graphics core array 2514 is coupled to shared function logic 2520, which includes multiple resources shared among the graphics cores in the graphics core array 2514. In at least one embodiment, the shared functions performed by the shared function logic 2520 are embodied in hardware logic units that provide dedicated supplementary functions to the graphics core array 2514. In at least one embodiment, the shared function logic 2520 includes, but is not limited to, a sampler 2521, math 2522, and inter-thread communication (ITC) logic 2523. In at least one embodiment, one or more caches 2525 are included in or coupled to the shared function logic 2520.

[0387] In at least one embodiment, shared functionality is used if the demand for dedicated functionality is insufficient to be contained within the graphics core array 2514. In at least one embodiment, a single instance of the dedicated functionality is used in shared functionality logic 2520 and shared among other execution resources within the graphics core array 2514. In at least one embodiment, a specific shared functionality may be included within shared functionality logic 2520 within the graphics core array 2514, said specific shared functionality being within shared functionality logic 2516 widely used within the graphics core array 2514. In at least one embodiment, shared functionality logic 2516 within the graphics core array 2514 may include some or all of the logic within shared functionality logic 2520. In at least one embodiment, all logic elements within shared functionality logic 2520 may be replicated within shared functionality logic 2516 of the graphics core array 2514. In at least one embodiment, shared functionality logic 2520 is excluded to support shared functionality logic 2516 within the graphics core array 2514.

[0388] In at least one embodiment, the graphics core array 2514 can be used to implement a wireless network, such as the MIMO network described above. In at least one embodiment, the graphics core array 2514 can implement a control data thread, a user data thread, and a beamforming weight calculation thread, such as... Figure 6 As shown.

[0389] Figure 26 This is a block diagram of the hardware logic of a graphics processor core 2600 according to at least one embodiment described herein. In at least one embodiment, the graphics processor core 2600 is included within a graphics core array. In at least one embodiment, the graphics processor core 2600 (sometimes referred to as a core slice) may be one or more graphics cores within a modular graphics processor. In at least one embodiment, the graphics processor core 2600 is an example of a graphics core slice, and the graphics processor described herein may include multiple graphics core slices based on target power and performance envelopes. In at least one embodiment, each graphics core 2600 may include a fixed-function block 2630, also referred to as a sub-slice, coupled to a plurality of sub-cores 2601A-2601F, which includes modular blocks of general-purpose and fixed-function logic.

[0390] In at least one embodiment, the fixed-function block 2630 includes a geometry and fixed-function pipeline 2636, which, for example, may be shared by all sub-cores of the graphics processor 2600 in a lower-performance and / or lower-power graphics processor implementation. In at least one embodiment, the geometry and fixed-function pipeline 2636 includes a 3D fixed-function pipeline, a video front-end unit, a thread generator and a thread dispatcher, and a unified return buffer manager that manages a unified return buffer.

[0391] In at least one fixed embodiment, fixed functional block 2630 further includes a graphics SoC interface 2637, a graphics microcontroller 2638, and a media pipeline 2639. The graphics SoC interface 2637 provides an interface between the graphics core 2600 and other processor cores in the on-chip integrated circuit system. In at least one embodiment, the graphics microcontroller 2638 is a programmable subprocessor configurable to manage various functions of the graphics processor 2600, including thread dispatch, scheduling, and preemption. In at least one embodiment, the media pipeline 2639 includes logic that facilitates decoding, encoding, preprocessing, and / or post-processing of multimedia data, including image and video data. In at least one embodiment, the media pipeline 2639 implements media operations via requests for computation or sampling logic within subcores 2601-2601F.

[0392] In at least one embodiment, the SoC interface 2637 enables the graphics core 2600 to communicate with a general-purpose application processor core (e.g., a CPU) and / or other components within the SoC, including memory hierarchy elements such as shared last-level cache, system RAM, and / or embedded on-chip or packaged DRAM. In at least one embodiment, the SoC interface 2637 also enables communication with fixed-function devices within the SoC (e.g., a camera imaging pipeline) and enables the use and / or implementation of global memory atoms that can be shared between the graphics core 2600 and the CPU within the SoC. In at least one embodiment, the SoC interface 2637 also implements power management control for the graphics core 2600 and enables interfacing between the clock domain of the graphics core 2600 and other clock domains within the SoC. In at least one embodiment, the SoC interface 2637 enables the receipt of command buffers from a command stream converter and a global thread dispatcher, configured to provide commands and instructions to each of one or more graphics cores within the graphics processor. In at least one embodiment, when a media operation is to be performed, commands and instructions may be dispatched to the media pipeline 2639, or when a graphics processing operation is to be performed, they may be assigned to the geometry and fixed-function pipeline (e.g., geometry and fixed-function pipeline 2636, and / or geometry and fixed-function pipeline 2614).

[0393] In at least one embodiment, the graphics microcontroller 2638 can be configured to perform various scheduling and management tasks on the graphics core 2600. In at least one embodiment, the graphics microcontroller 2638 can perform graphics and / or compute workload scheduling on various graphics parallel engines within the execution unit (EU) arrays 2602A-2602F, 2604A-2604F in the sub-cores 2601A-2601F. In at least one embodiment, host software executing on the CPU core of the SoC including the graphics core 2600 can submit a workload of one of a plurality of graphics processor doorbells, which invokes scheduling operations on the appropriate graphics engine. In at least one embodiment, the scheduling operation includes determining which workload should be run next, submitting the workload to the command stream converter, preempting existing workloads running on the engine, monitoring the progress of the workload, and notifying the host software when the workload is completed. In at least one embodiment, the graphics microcontroller 2638 may also facilitate a low-power or idle state of the graphics core 2600, thereby providing the graphics core 2600 with the ability to save and restore registers across low-power state transitions within the graphics core 2600, independent of the operating system and / or the graphics driver software on the system.

[0394] In at least one embodiment, the graphics core 2600 may have up to N more or fewer modular sub-cores than the illustrated sub-cores 2601A-2601F. For each group of N sub-cores, in at least one embodiment, the graphics core 2600 may further include shared functional logic 2610, shared and / or cache memory 2612, geometry / fixed-function pipeline 2614, and additional fixed-function logic 2616 to accelerate various graphics and computational processing operations. In at least one embodiment, the shared functional logic 2610 may include logic units (e.g., samplers, mathematical and / or inter-thread communication logic) that can be shared by each of the N sub-cores within the graphics core 2600. In at least one embodiment, the shared and / or cache memory 2612 may be the last-level cache of the N sub-cores 2601A-2601F within the graphics core 2600, and may also be used as shared memory accessible by multiple sub-cores. In at least one embodiment, a geometry / fixed function pipeline 2614 may be included to replace the geometry / fixed function pipeline 2636 within the fixed function block 2630, and may include the same or similar logic units.

[0395] In at least one embodiment, the graphics core 2600 includes additional fixed-function logic 2616, which may include various fixed-function acceleration logics for use by the graphics core 2600. In at least one embodiment, the additional fixed-function logic 2616 includes additional geometry pipelines for use in position-only shading. In position-only shading, there are at least two geometry pipelines, and in the full geometry pipeline and culling pipeline within the geometry and fixed-function pipelines 2614, 2636, it is an additional geometry pipeline that can be included in the additional fixed-function logic 2616. In at least one embodiment, the culling pipeline is a trimmed version of the full geometry pipeline. In at least one embodiment, the full pipeline and the culling pipeline can execute different instances of the application, each with a separate environment. In at least one embodiment, position-only shading can hide long culling runs of discarded triangles, thereby allowing shading to be completed earlier in some cases. For example, in at least one embodiment, the culling pipeline logic in the additional fixed-function logic 2616 can execute the position shader in parallel with the main application and typically generates critical results faster than the full pipeline because the culling pipeline acquires and occludes the positional attributes of vertices without performing rasterization and rendering pixels to the framebuffer. In at least one embodiment, the culling pipeline can use the generated critical results to compute visibility information for all triangles, regardless of whether those triangles were culled. In at least one embodiment, the full pipeline (which may be referred to as the replay pipeline in this case) can consume visibility information to skip culled triangles and only occlude the visible triangles that are ultimately passed to the rasterization stage.

[0396] In at least one embodiment, the additional fixed-function logic 2616 may also include machine learning acceleration logic, such as fixed-function matrix multiplication logic, for implementing optimizations for machine learning training or inference.

[0397] In at least one embodiment, each graphics subcore 2601A-2601F includes a set of execution resources that can be used to perform graphics, media, and compute operations in response to requests from the graphics pipeline, media pipeline, or shader program. In at least one embodiment, the graphics subcore 2601A-2601F includes multiple EU arrays 2602A-2602F, 2604A-2604F, thread dispatch and inter-thread communication (TD / IC) logic 2603A-2603F, 3D (e.g., texture) samplers 2605A-2605F, media samplers 2606A-2606F, shader processors 2607A-2607F, and shared local memory (SLM) 2608A-2608F. In at least one embodiment, each of the EU arrays 2602A-2602F and 2604A-2604F includes multiple execution units, which are general-purpose graphics processing units capable of servicing graphics, media, or computational operations, performing floating-point and integer / fixed-point logic operations, including graphics, media, or computational shader programs. In at least one embodiment, the TD / IC logic 2603A-2603F performs local thread dispatch and thread control operations for the execution units within the subcore and facilitates communication between threads executing on the execution units of the subcore. In at least one embodiment, the 3D samplers 2605A-2605F can read data associated with textures or other 3D graphics into memory. In at least one embodiment, the 3D samplers can read texture data differently based on the sampling state and texture format configured and associated with a given texture. In at least one embodiment, the media samplers 2606A-2606F can perform similar read operations based on the type and format associated with the media data. In at least one embodiment, each graphics subcore 2601A-2601F may alternatively include a unified 3D and media sampler. In at least one embodiment, threads executing on execution units within each subcore 2601A-2601F may utilize shared local memory 2608A-2608F within each subcore, enabling threads executing within a thread group to use a common pool of on-chip memory for execution.

[0398] In at least one embodiment, the graphics core array 2514 can be used to implement a wireless network, such as the MIMO network described above. In at least one embodiment, the graphics core array 2514 can implement a control data thread, a user data thread, and a beamforming weight calculation thread, such as... Figure 6 As shown.

[0399] Figures 27A-27B The diagram illustrates thread execution logic 2700 of an array of processing elements including a graphics processor core, according to at least one embodiment. Figure 27A At least one embodiment is shown in which thread execution logic 2700 is used. Figure 27B Exemplary internal details of an execution unit according to at least one embodiment are shown.

[0400] like Figure 27A As shown, in at least one embodiment, thread execution logic 2700 includes a shader processor 2702, a thread dispatcher 2704, an instruction cache 2706, a scalable execution unit array including multiple execution units 2708A-2708N, a sampler 2710, a data cache 2712, and a data port 2714. In at least one embodiment, the scalable execution unit array can be dynamically scaled, for example, based on the computational requirements of the workload, by enabling or disabling one or more execution units (e.g., any one of execution units 2708A, 2708B, 2708C, 2708D, through 2708N-1 and 2708N). In at least one embodiment, the scalable execution units are interconnected via an interconnect structure linking to each execution unit. In at least one embodiment, the thread execution logic 2700 includes one or more connections to memory (such as system memory or cache memory) via one or more of the instruction cache 2706, data port 2714, sampler 2710, and execution units 2708A-2708N. In at least one embodiment, each execution unit (e.g., 2708A) is an independent programmable general-purpose computing unit capable of executing multiple concurrent hardware threads, processing multiple data elements in parallel for each thread. In at least one embodiment, the array of execution units 2708A-2708N is scalable to include any number of individual execution units.

[0401] In at least one embodiment, execution units 2708A-2708N are primarily used to execute shader programs. In at least one embodiment, shader processor 2702 can process various shader programs and dispatch execution threads associated with the shader programs via thread dispatcher 2704. In at least one embodiment, thread dispatcher 2704 includes logic for arbitrating thread initialization celebrations from the graphics and media pipeline and for instantiating requested threads on one or more execution units 2708A-2708N. For example, in at least one embodiment, the geometry pipeline can dispatch vertex, tessellation, or geometry shaders to thread execution logic for processing. In at least one embodiment, thread dispatcher 2704 can also handle runtime thread generation requests from executing shader programs.

[0402] In at least one embodiment, execution units 2708A-2708N support an instruction set that includes native support for many standard 3D graphics shader instructions, enabling shader programs in graphics libraries (e.g., Direct3D and OpenGL) to execute with minimal conversion. In at least one embodiment, the execution unit supports vertex and geometry processing (e.g., vertex programs, geometry programs, vertex shaders), pixel processing (e.g., pixel shaders, fragment shaders), and general processing (e.g., computation and media shaders). In at least one embodiment, each execution unit 2708A-2708N includes one or more arithmetic logic units (ALUs) capable of performing multiple-issue single-instruction multiple-data (SIMD) operations, and multithreaded operation enables an efficient execution environment despite higher latency memory access. In at least one embodiment, each hardware thread within each execution unit has a dedicated high-bandwidth register file and associated independent thread states. In at least one embodiment, execution is multiple issues per clock cycle to a pipeline capable of integer, single-precision, and double-precision floating-point operations, SIMD branching functions, logical operations, a priori operations, and other operations. In at least one embodiment, while waiting for data from one of the memory or shared functions, dependency logic within execution units 2708A-2708N causes the waiting thread to sleep until the requested data is returned. In at least one embodiment, while the waiting thread is sleeping, hardware resources can be dedicated to processing other threads. For example, in at least one embodiment, during the latency associated with vertex shader operations, the execution unit can perform operations on the pixel shader, fragment shader, or another type of shader program (including different vertex shaders).

[0403] In at least one embodiment, each execution unit in the execution units 2708A-2708N operates on an array of data elements. In at least one embodiment, the plurality of data elements is an "execution size" or the number of instruction channels. In at least one embodiment, an execution channel is a logical unit for execution of data element access, masking, and flow control within an instruction. In at least one embodiment, the plurality of channels may be independent of the plurality of physical arithmetic logic units (ALUs) or floating-point units (FPUs) for a particular graphics processor. In at least one embodiment, the execution units 2708A-2708N support both integer and floating-point data types.

[0404] In at least one embodiment, the execution unit instruction set includes SIMD instructions. In at least one embodiment, various data elements can be stored in registers as encapsulated data types, and the execution unit will process various elements based on the data size of those elements. For example, in at least one embodiment, when operating on a 256-bit wide vector, 256 bits of the vector are stored in registers, and the execution unit operates on the vector as four separate 64-bit encapsulated data elements (quad-word (QW) size data elements), eight separate 32-bit encapsulated data elements (double-word (DW) size data elements), sixteen separate 16-bit encapsulated data elements (word (W) size data elements), or thirty-two separate 8-bit data elements (byte (B) size data elements). However, in at least one embodiment, different vector widths and register sizes are possible.

[0405] In at least one embodiment, one or more execution units may be combined into a fused execution unit 2709A-2709N having thread control logic (2707A-2707N) that typically fuses EUs. In at least one embodiment, multiple EUs may be fused into an EU group. In at least one embodiment, the number of EUs in the fused EU group may be configured to execute separate SIMD hardware threads. The number of EUs in the fused EU group may vary depending on the embodiment. In at least one embodiment, each EU may execute various SIMD widths, including but not limited to SIMD8, SIMD16, and SIMD32. In at least one embodiment, each fused graphics execution unit 2709A-2709N includes at least two execution units. For example, in at least one embodiment, the fused execution unit 2709A includes a first EU 2708A, a second EU 2708B, and thread control logic 2707A shared by the first EU 2708A and the second EU 2708B. In at least one embodiment, thread control logic 2707A controls the threads executing on the fused graphics execution unit 2709A, thereby allowing each EU within the fused execution units 2709A-2709N to execute using a common instruction pointer register.

[0406] In at least one embodiment, one or more internal instruction caches (e.g., 2706) are included in the thread execution logic 2700 to cache thread instructions for the execution unit. In at least one embodiment, one or more data caches (e.g., 2712) are included to cache thread data during thread execution. In at least one embodiment, a sampler 2710 is included to provide texture sampling for 3D operations and media sampling for media operations. In at least one embodiment, the sampler 2710 includes dedicated texture or media sampling functions to process texture or media data during the sampling process before providing sampled data to the execution unit.

[0407] During execution, in at least one embodiment, the graphics and media pipeline sends thread initiation requests to thread execution logic 2700 via thread creation and dispatch logic. In at least one embodiment, once a set of geometric objects has been processed and rasterized into pixel data, pixel processor logic (e.g., pixel shader logic, fragment shader logic, etc.) within shader processor 2702 is invoked to further compute output information and cause the results to be written to output surfaces (e.g., color buffer, depth buffer, stencil buffer, etc.). In at least one embodiment, the pixel shader or fragment shader computes values ​​of various vertex attributes to be interpolated on the rasterized objects. In at least one embodiment, the pixel processor logic within shader processor 2702 then executes a pixel or fragment shader program provided by an application programming interface (API). In at least one embodiment, to execute the shader program, shader processor 2702 dispatches threads to execution units (e.g., 2708A) via thread dispatcher 2704. In at least one embodiment, shader processor 2702 uses texture sampling logic in sampler 2710 to access texture data in a texture map stored in memory. In at least one embodiment, arithmetic operations on the texture data and the input geometry data are performed to calculate pixel color data for each geometric segment, or one or more pixels are discarded for further processing.

[0408] In at least one embodiment, data port 2714 provides a memory access mechanism for thread execution logic 2700 to output processed data to memory for further processing on the graphics processor output pipeline. In at least one embodiment, data port 2714 includes or is coupled to one or more cache memories (e.g., data cache 2712) to cache data for memory access via the data port.

[0409] like Figure 27BAs shown, in at least one embodiment, the graphics execution unit 2708 may include an instruction fetch unit 2737, a general-purpose register file array (GRF) 2724, an architecture register file array (ARF) 2726, a thread arbiter 2722, a send unit 2730, a branch unit 2732, a set of SIMD floating-point units (FPUs) 2734, and a set of dedicated integer SIMD ALUs 2735. In at least one embodiment, the GRF 2724 and ARF 2726 include a set of general-purpose register files and architecture register files associated with each concurrent hardware thread that may be active in the graphics execution unit 2708. In at least one embodiment, the architecture state of each thread is maintained in the ARF 2726, while data used during thread execution is stored in the GRF 2724. In at least one embodiment, the execution state of each thread, including the instruction pointer of each thread, may be stored in thread-specific registers in the ARF 2726.

[0410] In at least one embodiment, the graphics execution unit 2708 has an architecture that is a combination of simultaneous multithreading (SMT) and fine-grained interleaved multithreading (IMT). In at least one embodiment, the architecture has a modular configuration that can be fine-tuned at design time based on a target number of simultaneous threads and the number of registers per execution unit, wherein execution unit resources are logically allocated for executing multiple simultaneous threads.

[0411] In at least one embodiment, the graphics execution unit 2708 can jointly issue multiple instructions, each of which can be a different instruction. In at least one embodiment, the thread arbiter 2722 of the graphics execution unit thread 2708 can dispatch instructions to one of the sending unit 2730, the branching unit 2742, or the SIMD FPU 2734 for execution. In at least one embodiment, each execution thread can access 128 general-purpose registers in the GRF 2724, each register being able to store 32 bytes and being accessible as a SIMD 8-element vector of 32-bit data elements. In at least one embodiment, each execution unit thread can access 4 KB of the GRF 2724, although the embodiments are not limited thereto, and more or fewer register resources may be provided in other embodiments. In at least one embodiment, although the number of threads per execution unit may also vary depending on the embodiment, a maximum of seven threads can be executed simultaneously. In at least one embodiment where seven threads can access 4 KB, the GRF 2724 can store a total of 28 KB. In at least one embodiment, the flexible addressing mode can allow registers to be addressed together to efficiently build wider registers or rectangular block data structures representing strides.

[0412] In at least one embodiment, memory operations, sampler operations, and other longer-latency system communications are scheduled via a "send" instruction executed by message sending unit 2730. In at least one embodiment, branch instructions are dispatched to a dedicated branching unit 2732 to facilitate SIMD divergence and eventual convergence.

[0413] In at least one embodiment, the graphics execution unit 2708 includes one or more SIMD floating-point units (FPUs) 2734 to perform floating-point operations. In at least one embodiment, the one or more FPUs 2734 also support integer computation. In at least one embodiment, the one or more FPUs 2734 can perform up to M 32-bit floating-point (or integer) operations in SIMD, or up to 2M 16-bit integer or 16-bit floating-point operations in SIMD. In at least one embodiment, at least one FPU provides extended mathematical capabilities to support high-throughput a priori mathematical functions and double-precision 64-bit floating-point operations. In at least one embodiment, a set of 8-bit integer SIMD ALUs 2735 is also present and can be specifically optimized to perform operations related to machine learning computations.

[0414] In at least one embodiment, an array of multiple instances of the graphics execution unit 2708 may be instantiated in a graphics sub-core group (e.g., a sub-slice). In at least one embodiment, the execution unit 2708 may execute instructions across multiple execution channels. In at least one embodiment, each thread executed on the graphics execution unit 2708 executes on a different channel.

[0415] In at least one embodiment, the graphics execution unit 2708 can be used to implement a wireless network, such as the MIMO network described above. In at least one embodiment, the graphics execution unit 2708 can implement a control data thread, a user data thread, and a beamforming weight calculation thread, such as... Figure 6 As shown.

[0416] Figure 28A parallel processing unit (“PPU”) 2800 according to at least one embodiment is illustrated. In at least one embodiment, the PPU 2800 is configured with machine-readable code that, if executed by the PPU 2800, causes the PPU 2800 to perform some or all of the processes and techniques described herein. In at least one embodiment, the PPU 2800 is a multi-threaded processor implemented on one or more integrated circuit devices and utilizes multi-threading as a latency-hiding technique designed to process computer-readable instructions (also known as machine-readable instructions or simple instructions) that are executed in parallel on multiple threads. In at least one embodiment, a thread refers to an execution thread and is an instance of a set of instructions configured to be executed by the PPU 2800. In at least one embodiment, the PPU 2800 is a graphics processing unit (“GPU”) configured to implement a graphics rendering pipeline for processing three-dimensional (“3D”) graphics data to generate two-dimensional (“2D”) image data for display on a display device, such as a liquid crystal display (“LCD”) device. In at least one embodiment, the PPU 2800 is used to perform computations, such as linear algebra operations and machine learning operations. Figure 28 An example parallel processor is shown for illustrative purposes only and should be interpreted as a non-limiting example of a processor architecture contemplated within the scope of this disclosure, which may be supplemented and / or replaced by any suitable processor.

[0417] In at least one embodiment, one or more PPU 2800s are configured to accelerate high-performance computing (“HPC”), data center, and machine learning applications. In at least one embodiment, the PPU 2800 is configured to accelerate deep learning systems and applications, including, but not limited to, the following non-limiting examples: autonomous vehicle platforms, deep learning, high-precision speech, image, and text recognition systems, intelligent video analytics, molecular simulation, drug discovery, disease diagnosis, weather forecasting, big data analytics, astronomy, molecular dynamics simulation, financial modeling, robotics, factory automation, real-time language conversion, online search optimization, and personalized user recommendations, etc.

[0418] In at least one embodiment, the PPU 2800 includes, but is not limited to, an input / output (“I / O”) unit 2806, a front-end unit 2810, a scheduler unit 2812, a job allocation unit 2814, a hub 2816, a crossbar (“Xbar”) 2820, one or more general-purpose processing clusters (“GPCs”) 2818, and one or more partitioning units (“memory partitioning units”) 2822. In at least one embodiment, the PPU 2800 is connected to a host processor or other PPU 2800 via one or more high-speed GPU interconnects (“GPU interconnects”) 2808. In at least one embodiment, the PPU 2800 is connected to a host processor or other peripheral device via an interconnect 2802. In one embodiment, the PPU 2800 is connected to local memory including one or more memory devices (“memory”) 2804. In at least one embodiment, the memory device 2804 includes, but is not limited to, one or more dynamic random access memory (“DRAM”) devices. In at least one embodiment, one or more DRAM devices are configured and / or configurable as high-bandwidth memory (“HBM”) subsystems, and multiple DRAM dies are stacked within each device.

[0419] In at least one embodiment, the high-speed GPU interconnect 2808 may refer to a wire-based multi-channel communication link used by the system for scaling, and includes one or more PPUs 2800s (“CPUs”) combined with one or more central processing units, supporting cache coherency between the PPUs 2800s and the CPUs, as well as CPU master control. In at least one embodiment, the high-speed GPU interconnect 2808 transmits data and / or commands to other units of the PPU 2800, such as one or more copy engines, video encoders, video decoders, power management units, and / or other components, via a hub 2816. Figure 28 Other components that may not be explicitly shown.

[0420] In at least one embodiment, the I / O unit 2806 is configured to access the host processor via the system bus 2802. Figure 28(Not shown) Sending and receiving communications (e.g., commands, data). In at least one embodiment, I / O unit 2806 communicates directly with the host processor via system bus 2802 or via one or more intermediate devices (e.g., memory bridges). In at least one embodiment, I / O unit 2806 may communicate with one or more other processors (e.g., one or more PPUs 2800) via system bus 2802. In at least one embodiment, I / O unit 2806 implements a Peripheral Component Interconnect Express (“PCIe”) interface for communication via the PCIe bus. In at least one embodiment, I / O unit 2806 implements an interface for communicating with external devices.

[0421] In at least one embodiment, I / O unit 2806 decodes packets received via system bus 2802. In at least one embodiment, at least some packets represent commands configured to cause PPU 2800 to perform various operations. In at least one embodiment, I / O unit 2806 sends the decoded commands to various other units of PPU 2800 as specified by the commands. In at least one embodiment, the commands are sent to front-end unit 2810 and / or to hub 2816 or other units of PPU 2800, such as one or more copy engines, video encoders, video decoders, power management units, etc. Figure 28 (Not explicitly shown). In at least one embodiment, I / O unit 2806 is configured to route communication between various logical units of PPU 2800.

[0422] In at least one embodiment, a program executed by the host processor encodes a command stream in a buffer that provides a workload to the PPU 2800 for processing. In at least one embodiment, the workload includes instructions and data to be processed by those instructions. In at least one embodiment, the buffer is a region in memory accessible (e.g., read / write) by both the host processor and the PPU 2800—the host interface unit can be configured to access a buffer in system memory connected to the system bus 2802 via memory requests transmitted through the system bus 2802 via the I / O unit 2806. In at least one embodiment, the host processor writes a command stream to the buffer and then sends a pointer indicating the start of the command stream to the PPU 2800, causing the front-end unit 2810 to receive pointers to one or more command streams and manage one or more command streams, read commands from the command streams, and forward the commands to the respective units of the PPU 2800.

[0423] In at least one embodiment, front-end unit 2810 is coupled to scheduler unit 2812, which configures various GPCs 2818 to process tasks defined by one or more command streams. In at least one embodiment, scheduler unit 2812 is configured to track status information related to the various tasks managed by scheduler unit 2812, wherein the status information may indicate which GPC 2818 a task is assigned to, whether the task is active or inactive, the priority associated with the task, etc. In at least one embodiment, scheduler unit 2812 manages multiple tasks executed on one or more GPCs 2818.

[0424] In at least one embodiment, scheduler unit 2812 is coupled to job allocation unit 2814, which is configured to dispatch tasks for execution on GPC 2818. In at least one embodiment, job allocation unit 2814 tracks multiple scheduled tasks received from scheduler unit 2812 and manages a pool of pending tasks and an active task pool for each GPC 2818. In at least one embodiment, the pool of pending tasks includes multiple time slots (e.g., 32 time slots) containing tasks assigned to a particular GPC 2818 for processing; the active task pool may include multiple time slots (e.g., 4 time slots) for tasks actively processed by GPC 2818, such that as one of the GPCs 2818 completes its execution, that task is evicted from the active task pool of the GPC 2818, and another task is selected from the pool of pending tasks and scheduled for execution on the GPC 2818. In at least one embodiment, if the active task is idle on GPC 2818, for example while waiting for data dependency resolution, the active task is evicted from GPC 2818 and returned to the task pool, while another task in the task pool is selected and scheduled to be executed on GPC 2818.

[0425] In at least one embodiment, the work allocation unit 2814 communicates with one or more GPCs 2818 via XBar 2820. In at least one embodiment, XBar 2820 is an interconnect network that couples a plurality of units of PPU 2800 to other units of PPU 2800, and can be configured to couple the work allocation unit 2814 to a specific GPC 2818. In at least one embodiment, other units of one or more PPUs 2800 can also be connected to XBar 2820 via hub 2816.

[0426] In at least one embodiment, tasks are managed by scheduler unit 2812 and assigned to one of GPCs 2818 by job allocation unit 2814. In at least one embodiment, GPC 2818 is configured to process tasks and produce results. In at least one embodiment, results may be consumed by other tasks in GPC 2818, routed to different GPCs 2818 via XBar 2820, or stored in memory 2804. In at least one embodiment, results may be written to memory 2804 via partitioning unit 2822, which implements a memory interface for writing data to or reading data from memory 2804. In at least one embodiment, results may be transferred to another PPU 2804 or CPU via high-speed GPU interconnect 2808. In at least one embodiment, PPU 2800 includes, but is not limited to, U partitioning units 2822, which is equal to the number of separate and different memory devices 2804 coupled to PPU 2800. In at least one embodiment, partitioning units 2822 will combine Figure 30 To describe in more detail.

[0427] In at least one embodiment, the host processor executes a driver core that implements an application programming interface (API) that enables one or more applications executing on the host processor to schedule operations for execution on the PPU 2800. In one embodiment, multiple computing applications are executed concurrently by the PPU 2800, and the PPU 2800 provides isolation, Quality of Service (“QoS”), and independent address spaces for the multiple computing applications. In at least one embodiment, application-generating instructions (e.g., in the form of API calls) cause the driver core to generate one or more tasks for execution by the PPU 2800, and the driver core outputs the tasks to one or more streams processed by the PPU 2800. In at least one embodiment, each task includes one or more associated thread groups, which may be referred to as a warp. In at least one embodiment, a warp includes multiple associated threads (e.g., 28 threads) that can be executed in parallel. In at least one embodiment, a cooperating thread may refer to multiple threads, including instructions for performing tasks and exchanging data via shared memory, in combination with... Figure 30 Threads and cooperative threads are described in more detail according to at least one embodiment.

[0428] In at least one embodiment, the PPU 2800 can be used to implement a wireless network, such as the MIMO network described above. In at least one embodiment, the PPU 2800 can implement, as... Figure 6 The control data thread, user data thread, and beamforming weight calculation thread are shown.

[0429] Figure 29 A general-purpose processing cluster (“GPC”) 2900 is illustrated according to at least one embodiment. In at least one embodiment, the GPC 2900 is Figure 28 The GPC 2818. In at least one embodiment, each GPC 2900 includes, but is not limited to, a plurality of hardware units for processing tasks, and each GPC 2900 includes, but is not limited to, a pipeline manager 2902, a pre-raster operation unit (“PROP”) 2904, a raster engine 2908, a work assignment crossbar switch (“WDX”) 2916, a memory management unit (“MMU”) 2918, one or more data processing clusters (“DPC”) 2906, and any suitable combination of components.

[0430] In at least one embodiment, the operation of GPC 2900 is controlled by pipeline manager 2902. In at least one embodiment, pipeline manager 2902 manages the configuration of one or more DPCs 2906 to handle tasks assigned to GPC 2900. In at least one embodiment, pipeline manager 2902 configures at least one of one or more DPCs 2906 to implement at least a portion of the graphics rendering pipeline. In at least one embodiment, DPC 2906 is configured to execute vertex shader programs on a programmable streaming multiprocessor (“SM”) 2914. In at least one embodiment, pipeline manager 2902 is configured to route data packets received from the work allocation unit to appropriate logic units within GPC 2900, and in at least one embodiment, some data packets may be routed to fixed-function hardware units in PROP 2904 and / or raster engine 2908, while other data packets may be routed to DPC 2906 for processing by raw engine 2912 or SM 2914. In at least one embodiment, pipeline manager 2902 configures at least one of DPCs 2906 to implement a neural network model and / or computation pipeline.

[0431] In at least one embodiment, the PROP unit 2904 is configured to route data generated by the raster engine 2908 and DPC 2906 to the raster operation (“ROP”) unit in the partition unit 2822, in conjunction with the above. Figure 28More detailed description. In at least one embodiment, the PROP unit 2904 is configured to perform optimizations for color blending, organize pixel data, perform address translation, etc. In at l...

Claims

1. One or more processors comprising: One or more circuits to cause fifth generation new radio (5G-NR) signal control information to be simultaneously transmitted using multiple different frequency bands of a 5G-NR signal, wherein a first portion of the 5G-NR signal control information is concurrently transmitted with user data during a first window of a transmission time slot, and a second portion of the 5G-NR signal control information is transmitted during a second window of the transmission time slot, the second window dedicated for transmission of control data.

2. The one or more processors of claim 1, wherein the 5G-NR signal control information is transmitted using some of the 5G-NR signal allocated to control plane data.

3. The one or more processors of claim 1, wherein the 5G-NR signal control information is adjusted by pre-empting the user data and exclusively transmitting the 5G-NR signal control information.

4. The one or more processors of claim 1, wherein: the second portion of the 5G-NR signal control information is exclusively transmitted within the second window of the transmission time slot of a wireless network; and the second window is a portion of the transmission time slot.

5. The one or more processors of claim 4, wherein the portion of the transmission time slot is at an end of the transmission time slot.

6. The one or more processors of claim 1, wherein the 5G-NR signal control information comprises beamforming weights for multiple input multiple output (MIMO) stations on a wireless network.

7. The one or more processors of claim 1, wherein the second portion of the 5G-NR signal control information is transmitted using a portion of the 5G-NR signal allocated to control data by pre-empting transmission of the user data.

8. A system comprising: One or more processors and a computer-readable memory storing instructions that, as a result of execution by the one or more processors, cause fifth generation new radio (5G-NR) signal control information to be simultaneously transmitted using multiple different frequency bands of a 5G-NR signal, wherein a first portion of the 5G-NR signal control information is concurrently transmitted with user data during a first window of a transmission time slot, and a second portion of the 5G-NR signal control information is transmitted during a second window of the transmission time slot, the second window dedicated for transmission of control data.

9. The system of claim 8, wherein some of the 5G-NR signal control information is transmitted using a portion of the 5G-NR signal bandwidth allocated to control data within the first window and the second window of the transmission time slot.

10. The system of claim 8, wherein a second portion of the 5G-NR signal control information is transmitted using some of the 5G-NR signal by pre-empting transmission of user data and increasing a bandwidth allocation allocated to the 5G-NR signal control information.

11. The system of claim 8, wherein some of the 5G-NR signal control information is transmitted using some of the 5G-NR signal allocated through control information within the second window that preempts transmission of user data and dedicates the entire bandwidth to the transmission time slot.

12. The system of claim 8, wherein: the 5G-NR signal control information is transmitted as control data over a wireless network; and the control data is transmitted at least partially in parallel with the user data.

13. The system of claim 8, wherein the system is a cellular telephone.

14. The system of claim 8, wherein the 5G-NR signal control information includes beamforming weights of a station having multiple antennas.

15. The system of claim 8, wherein the system implements a massive multiple-input multiple-output, MIMO, station over a wireless network.

16. A non-transitory computer-readable medium storing executable instructions that, if executed by one or more processors of a computer system, cause the computer system to use fifth generation new radio, 5G-NR, signal control information to be simultaneously transmitted using multiple different frequency bands of a 5G-NR signal, wherein a first portion of the 5G-NR signal control information is transmitted in parallel with user data during a first window of a transmission time slot, and a second portion of the 5G-NR signal control information is transmitted during a second window of the transmission time slot, the second window dedicated to transmission of control data.

17. The non-transitory computer-readable medium of claim 16, wherein the 5G-NR signal control information is transmitted using a portion of a bandwidth of the 5G-NR signal allocated to control plane data within the portion of the transmission time slot.

18. The non-transitory computer-readable medium of claim 16, wherein: the user data is transmitted as user plane data; the control data is transmitted as control plane data; and the user plane data is not transmitted during the second window.

19. The non-transitory computer-readable medium of claim 16, wherein: the 5G-NR signal control information includes beamforming weights; and the beamforming weights are exclusively transmitted in a dedicated time window.

20. The non-transitory computer-readable medium of claim 16, wherein at least a portion of the 5G-NR signal control information is transmitted in a dedicated time window at an end of the transmission time slot.

21. The non-transitory computer-readable medium of claim 16, wherein the computer system is a wireless router having multiple antennas that receive the 5G-NR signal control information.

22. The non-transitory computer-readable medium of claim 16, wherein, in response to a burst of control data, the computer system allocates a dedicated time window within a transmission time slot for transmission of the burst of control data.

23. The non-transitory computer-readable medium of claim 16, wherein: the computer system is a multiple-input multiple-output, MIMO, station connected to a computer network; and the 5G-NR signal control information is transmitted to the MIMO station. The 5G-NR signal control information includes beamforming weights for the multiple-input multiple-output (MIMO) station.

Images