Sharing radio access network information
By storing and accessing information in the database of the O-RAN network, the delay problem caused by the lack of direct interface between components is solved, and the rapid data sharing and access between components is realized, improving the performance and response speed of the network.
Patent Information
- Application Number
- CN202410531391.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2023-05-01
- Filing Date
- 2024-04-29
- Publication Date
- 2024-11-01
AI Technical Summary
In an open radio access network (O-RAN), due to the lack of direct interfaces between components, the information exchange delay increases, which affects the performance of the neural network. In particular, near-real-time controllers need to quickly access data for beamforming operations. The delay problem is particularly prominent.
By storing and accessing the information of the O-RAN network in the database, all components are allowed to subscribe and query information, and directly access the database through hardware interfaces such as Ethernet, reducing data transmission of intermediate components and realizing direct data sharing and access between components.
It reduces the delay in data transmission between components, improves the performance and response speed of the O-RAN network, ensures that the neural network can quickly obtain the required data to generate decisions, and improves the real-time control capabilities of the network.
Smart Images

Figure CN118890600A_ABST
Abstract
Description
Technical Field
[0001] At least one embodiment is directed to processing resources for facilitating radio access technology.For example, at least one embodiment is directed to a processor or computing system for providing access to a database storing radio access network (RAN) information. Background Art
[0002] To support more users and provide access in diverse locations, RAN providers are installing more base stations, radio units, and other components of the RAN network at numerous locations. As the RAN infrastructure grows, the amount of information generated by the equipment supporting the RAN continues to increase. This information can be used to optimize RAN performance. For example, based on RAN bandwidth, latency, connectivity, and other performance data, RAN-supporting equipment can be modified to perform better and improve RAN quality. However, storing, accessing, and otherwise using this information requires significant computing and memory resources. BRIEF DESCRIPTION OF THE DRAWINGS
[0003] Figure 1 An example system for providing access to a database storing RAN information in accordance with at least one embodiment is shown;
[0004] Figure 2 An example system for providing access to a database storing RAN information in accordance with at least one embodiment is shown;
[0005] Figure 3 shows a call flow diagram in which resources are shared by a database according to at least one embodiment;
[0006] Figure 4 shows a call flow diagram in which resources are shared by a database according to at least one embodiment;
[0007] Figure 5 An example process for providing access to a database storing RAN information is shown in accordance with at least one embodiment;
[0008] Figure 6 An example process for providing access to a database storing RAN information is shown in accordance with at least one embodiment;
[0009] Figure 7 An example system for providing access to a database storing RAN information in accordance with at least one embodiment is shown;
[0010] Figure 8 An example data center system is shown in accordance with at least one embodiment;
[0011] Figure 9AAn example of an autonomous vehicle according to at least one embodiment is shown;
[0012] Figure 9B According to at least one embodiment, Figure 9A Examples of camera positions and fields of view for autonomous vehicles in [1].
[0013] Figure 9C is a diagram illustrating a method according to at least one embodiment Figure 9A A block diagram of an example system architecture for an autonomous vehicle in FIG.
[0014] Figure 9D is a diagram illustrating a method for performing a multi-processor communication between a cloud-based server and a Figure 9A Figure 1 shows a system for communication between autonomous vehicles.
[0015] Figure 10 is a block diagram illustrating a computer system according to at least one embodiment;
[0016] Figure 11 is a block diagram illustrating a computer system according to at least one embodiment;
[0017] Figure 12 A computer system according to at least one embodiment is shown;
[0018] Figure 13 A computer system according to at least one embodiment is shown;
[0019] Figure 14A A computer system according to at least one embodiment is shown;
[0020] Figure 14B A computer system according to at least one embodiment is shown;
[0021] Figure 14C A computer system according to at least one embodiment is shown;
[0022] Figure 14D A computer system according to at least one embodiment is shown;
[0023] Figure 14E and Figure 14F illustrates a shared programming model according to at least one embodiment;
[0024] Figure 15 An exemplary integrated circuit and associated graphics processor are shown in accordance with at least one embodiment;
[0025] Figure 16A and Figure 16B An exemplary integrated circuit and associated graphics processor are shown in accordance with at least one embodiment;
[0026] Figure 17A and Figure 17B Additional exemplary graphics processor logic is shown in accordance with at least one embodiment;
[0027] Figure 18 A computer system according to at least one embodiment is shown;
[0028] Figure 19A A parallel processor according to at least one embodiment is shown;
[0029] Figure 19B shows a partition unit according to at least one embodiment;
[0030] Figure 19C illustrates a processing cluster according to at least one embodiment;
[0031] Figure 19D A graphics multiprocessor is shown in accordance with at least one embodiment;
[0032] Figure 20 A multi-graphics processing unit (GPU) system is shown in accordance with at least one embodiment;
[0033] Figure 21 A graphics processor according to at least one embodiment is shown;
[0034] Figure 22 is a block diagram illustrating a processor microarchitecture for a processor according to at least one embodiment;
[0035] Figure 23 illustrates at least a portion of a graphics processor according to one or more embodiments;
[0036] Figure 24 illustrates at least a portion of a graphics processor according to one or more embodiments;
[0037] Figure 25 illustrates at least a portion of a graphics processor according to one or more embodiments;
[0038] Figure 26 is a block diagram of a graphics processing engine of a graphics processor according to at least one embodiment;
[0039] Figure 27 is a block diagram of at least a portion of a graphics processor core according to at least one embodiment;
[0040] Figure 28A and Figure 28B Thread execution logic is shown, which includes an array of processing elements of a graphics processor core;
[0041] Figure 29illustrates a parallel processing unit ("PPU") in accordance with at least one embodiment;
[0042] Figure 30 illustrates a general processing cluster ("GPC") in accordance with at least one embodiment;
[0043] Figure 31 illustrates a memory partitioning unit of a parallel processing unit ("PPU") according to at least one embodiment;
[0044] Figure 32 A streaming multiprocessor is shown in accordance with at least one embodiment;
[0045] Figure 33 A network for transmitting data within a 5G wireless communication network according to at least one embodiment is shown;
[0046] Figure 34 illustrates a network architecture for a 5G LTE wireless network according to at least one embodiment;
[0047] Figure 35 is a diagram illustrating some basic functionality of a mobile telecommunications network / system operating according to LTE and 5G principles, according to at least one embodiment;
[0048] Figure 36 illustrates a radio access network that may be part of a 5G network architecture in accordance with at least one embodiment;
[0049] Figure 37 An example illustration of a 5G mobile communication system in which multiple different types of devices are used is provided according to at least one embodiment;
[0050] Figure 38 An example high-level system according to at least one embodiment is shown;
[0051] Figure 39 shows the architecture of a network system according to at least one embodiment;
[0052] Figure 40 illustrates example components of a device according to at least one embodiment;
[0053] Figure 41 illustrates an example interface for a baseband circuit according to at least one embodiment;
[0054] Figure 42 An example of an uplink channel according to at least one embodiment is shown;
[0055] Figure 43 shows the architecture of a network system according to at least one embodiment;
[0056] Figure 44 illustrates a control plane protocol stack according to at least one embodiment;
[0057] Figure 45 illustrates a user plane protocol stack according to at least one embodiment;
[0058] Figure 46 illustrates components of a core network according to at least one embodiment; and
[0059] Figure 47 Components of a system supporting network functions virtualization (NFV) are shown in accordance with at least one embodiment. Specific embodiments
[0060] In at least one embodiment, in an open radio access network (O-RAN) architecture, different components of such a network store information locally. For example, a scheduler stores its scheduling data in a local database, and a controller stores its control information in a local database. In at least one embodiment, if different components of the O-RAN network require information from other components, they use interfaces (e.g., defined by the O-RAN specifications) to exchange information. In at least one embodiment, for components that do not have a direct interface with other components, these components send information through an intermediate component (also referred to as an "intermediary node") to exchange information. In at least one embodiment, components of an O-RAN network may be referred to as "nodes," and a node may include one or more layers (e.g., Layer 1 Open Distributed Unit (O-DU), Layer 2 of an O-DU). In at least one embodiment, O-RAN and O-RAN networks refer to radio access networks based on the Third Generation Partnership Project (3GPP) and Technical Specifications (TSs) (such as 38.401) of the Global System for Mobile Communications (GSMA). In at least one embodiment, O-RAN includes disaggregated components, nodes, or units, where disaggregation may include components, nodes, or units provided by different vendors, manufacturers, or software providers.
[0061] In at least one embodiment, the use of interfaces by some components or nodes and the lack of direct component-to-component or node-to-node interfaces can cause latency in the O-RAN network because the interfaces have limited bandwidth and data transfers through intermediate components take longer than direct component-to-component transfers. In at least one embodiment, this latency issue is exacerbated by the desire of some O-RAN providers to include neural networks in various components to enhance performance, but these neural networks do not perform well if there is too much latency in the network (e.g., it takes too long for the neural network to acquire relevant data to generate a decision). For example, a near real-time controller could use a neural network to improve beamforming operations, but the near real-time controller neural network requires almost immediate access to data so that there is little latency in receiving output from the neural network.
[0062] In at least one embodiment, to improve O-RAN performance, a database allows, enables, or otherwise facilitates devices in the O-RAN network to store and access information from other O-RAN devices. All components of the O-RAN network can subscribe to the database; for example, they can periodically send or receive data to or from the database. For example, when a scheduler begins providing fifth-generation (5G) service, it can send data related to how many operations it needs to schedule and which radios should transmit the results of those operations. In at least one embodiment, devices can also query the database for information related to other O-RAN devices, components, nodes, or layers. In at least one embodiment, the database receives this information and stores it for access by other components (for example, a controller can access scheduler data at any time and use the scheduler information as input to a neural network to learn how to perform better based on the scheduler information). In at least one embodiment, each component, node, and layer of the O-RAN network can access the database using a hardware interface (e.g., Ethernet). In at least one embodiment, a database includes a processor including circuitry for providing access to the database, the database storing information generated by a plurality of different devices of a fifth generation open new radio (5G-NR) radio access network. In at least one embodiment, the processor includes circuitry for receiving, at the database, information indicating information of a fifth generation new radio (5G-NR) signal of the open radio access network. In at least one embodiment, the processor includes circuitry for receiving, at the database, a request to send information of a plurality of open radio access network (O-RAN) components to a component of the O-RAN network.
[0063] Figure 1An example system 100 is shown for providing access to a database storing RAN information in accordance with at least one embodiment. In at least one embodiment, the system 100 is used to share information stored in the database with multiple components within a fifth generation new radio (5G-NR) radio access network.
[0064] In at least one embodiment, system 100 includes a wireless mobile network, such as a fourth generation (4G), fifth generation (5G), sixth generation (6G), seventh generation (7G), eighth generation (8G), or other network types defined by 3GPP. In at least one embodiment, system 100 is network 3300 as described herein. In at least one embodiment, system 100 is mobile telecommunications system 3400 as described herein. In at least one embodiment, system 100 is 5G mobile communications system 3600 as described herein. In at least one embodiment, system 100 is network 3700 as described herein. In at least one embodiment, system 100 is system 3900 as described herein. In at least one embodiment, system 100 includes control plane protocol stack 4400 as described herein.
[0065] In at least one embodiment, system 100 includes a core network 102 and a RAN 104. In at least one embodiment, core network 102 includes one or more processors, servers, or computing devices that perform, implement, or otherwise operate the backbone of a wireless mobile network by executing software that is responsible for managing and routing all data traffic between devices and services.
[0066] In at least one embodiment, the core network 102 includes multiple components that perform multiple functions, such as, but not limited to, network function virtualization, software-defined networking, and edge computing. In at least one embodiment, network function virtualization refers to a software-based networking approach that allows network operators to virtualize network functions (such as routing, firewalling, and load balancing). In at least one embodiment, software-defined networking refers to a network architecture that separates the control plane from the data plane, allowing for more centralized control and management of the network (e.g., system 100). In at least one embodiment, software-defined networking enables network operators to dynamically adjust the network to adapt to changing business models and optimize performance. In at least one embodiment, network slicing refers to dividing the network into multiple virtual networks, each with its own set of resources and performance characteristics. In at least one embodiment, network slicing enables operators to provide customized services to different types of customers, such as low-latency connections for autonomous vehicles, high-speed connections for video streaming, and high-reliability connections for mission-critical applications. In at least one embodiment, edge computing refers to a distributed computing model that brings computing resources closer to the edge of the network, reducing latency and improving the performance of applications that require real-time responsiveness. In at least one embodiment, using edge computing, the core network 102 enables applications such as augmented reality, virtual reality, and gaming.
[0067] In at least one embodiment, the components of the core network 102 may include a processor (e.g., a central processing unit (CPU), a graphics processing unit (GPU), a field programmable gate array (FPGA), an application-specific integrated circuit (ASIC), or a combination thereof) that performs the functions described. In at least one embodiment, the components include a GPU or a system on a chip (SoC) that includes a CPU and one or more GPUs to accelerate the performance of 5G-NR network operations. In at least one embodiment, the core network 102 communicates directly or indirectly within the RAN 104.
[0068] In at least one embodiment, the core network 102 comprises a mobile edge computing network because it is close (e.g., less than 5 miles) to end-user devices in the RAN 104, enabling it to execute applications related to processing tasks closer to the end user. In at least one embodiment, the core network 102 includes an internal controller, which is software executed by one or more processors to control, monitor, or otherwise operate the core network 102. In at least one embodiment, the core network 102 provides its node-specific analytics, such as a control plane function (CPF) and a user plane function (UPF), to other networks or devices through a network exposure function (NEF) and / or an internal analytics function (AF), where the functions are executed by one or more devices including one or more processors. In at least one embodiment, the core network 102 includes external applications (e.g., MEC) that can subscribe to the RAIE and / or NEF to obtain RAN and core network-specific network analytics and utilize the analytics to dynamically optimize their performance. In at least one embodiment, the core network 102 and the RAN 104 may perform analysis sharing operations in parallel or sequentially.
[0069] In at least one embodiment, the core network 102 is the core network 3502 described herein. In at least one embodiment, the core network 102 is the core network 3938 described herein. In at least one embodiment, the core network 102 is the core network 4310 described herein.
[0070] In at least one embodiment, the RAN 104 is responsible for sending and receiving wireless signals between the user equipment 106A, 106B and the core network 102. In at least one embodiment, the RAN 104 includes a network of small cells or base stations that are distributed throughout a geographic area to provide coverage. In at least one embodiment, these small cells are typically mounted on utility poles, buildings, or other structures and can provide a range of several hundred meters to several kilometers, depending on the frequency band and type of cell.
[0071] In at least one embodiment, the RAN 104 can perform various network operations, including signaling, network synchronization, radio resource management, and security. In at least one embodiment, signaling includes the user equipment 106A, 106B transmitting wireless signals to base stations and vice versa using encoding and decoding, for example, 5G-NR signals, and managing radio resource allocation. In at least one embodiment, network synchronization refers to ensuring that all base stations in the RAN 104 are synchronized with each other and with the core network 102. In at least one embodiment, radio resource management refers to managing, for example, bandwidth and power to ensure efficient use of available resources and optimal performance. In at least one embodiment, ensuring security refers to providing a secure communication channel between the user equipment 106A, 106B and the core network 102.
[0072] In at least one embodiment, the RAN 104 is the RAN 3500 described herein. In at least one embodiment, the RAN 104 is the RAN 3916 described herein. In at least one embodiment, the RAN 104 includes a Figure 42 In at least one embodiment, the RAN 104 is the RAN 4308 described herein. In at least one embodiment, the RAN 104 is an open RAN (O-RAN).
[0073] In at least one embodiment, RAN 104 includes component 112 and database node 114. In at least one embodiment, the components of RAN 104 refer to the different components that make up RAN 104. For example, in at least one embodiment, RAN 104 includes components comprising different nodes, such as, but not limited to, orchestration node 210, near real-time controller node 220, protocol node A 232, protocol node B 234, distribution unit node 240, and radio unit node 250, as described herein. In at least one embodiment, the components may also include different portions of a node, such as, but not limited to, layer 1 portion 242, layer 1 portion 244, and non-real-time controller 212, as described herein. In at least one embodiment, component 112 performs different network operations. In at least one embodiment, the portions may be executed by processors separate from the processors used to execute the nodes comprising the portions. In at least one embodiment, component 112 includes a non-real-time RAN intelligent controller (non-RT RIC) as defined by O-RAN. In at least one embodiment, component 112 includes a scheduler, such as a service manager and coordinator (SMO). For example, a scheduler (e.g., an SMO) in a radio access network executed by a processor can share its upcoming schedule and analysis information of such schedule with the database node 114, so that other components 112 can access the database node 114 to improve user service quality and network efficiency (e.g., other components 112 can use the SMO data as training data for a neural network, or as input to a trained neural network to reason about decisions or settings of components of the O-RAN network). In at least one embodiment, if an O-RAN node (e.g., an SMO) needs to collect data from multiple other nodes (e.g., O-DUs, O-CUs, O-RUs), it can directly query the database node 114. In at least one embodiment, direct querying includes node-to-node or component-to-component connections without intermediate nodes, such as a direct Ethernet connection between two network addresses.
[0074] In at least one embodiment, component 112 is part of an O-RAN network, and component 112 can directly access database node 114 using another interface or hardware interface (e.g., Ethernet) rather than using an O-RAN defined interface (e.g., O1, O2, E1, A1, E2). In at least one embodiment, an O-RAN defined interface (e.g., O1, O2, E1, A1, E2) can be used with or in conjunction with database node 114 to collect or access data for the component. In at least one embodiment, the interface between component 112 and database node 114 can be unified (e.g., a standard interface for each node), proprietary, or a combination thereof (e.g., defined by O-RAN if it is an O-RAN node, proprietary if connected to a non-O-RAN node).
[0075] In at least one embodiment, RAN 104 is based on the O-RAN architecture. In at least one embodiment, O-RAN is a network architecture for mobile communications that is based on open standards and interfaces, enabling network operators to mix and match equipment from different vendors rather than being locked into proprietary solutions from a single vendor. In at least one embodiment, O-RAN supports virtualization, which enables the creation of multiple virtual networks on a single physical infrastructure. In at least one embodiment, O-RAN supports cloud-based deployments.
[0076] In at least one embodiment, the component 112 includes components such as, but not limited to, an ORAN near real-time RAN intelligent controller, an ORAN near real-time RAN intelligent controller, a network management system, an O-RAN central unit (CU)-control plane, an O-RAN central unit (CU)-user plane, an O-RAN distributed unit (DU), and an O-RAN radio unit (RU). In at least one embodiment, the O-RAN architecture includes ORAN interfaces (e.g., O1, O2, A1, E1, E2) and third generation partnership project (3GPP) interfaces (e.g., X2-c, X2-u, NG-u, Xn-u, Xn, F1-u, F1-x).
[0077] In at least one embodiment, the RAN 104 includes a database node 114. In at least one embodiment, the database node is a node that directly connects to the component 112 without using an interface implemented using a RAN standard (e.g., an O-RAN standard). In at least one embodiment, the database node 114 connects to the component 112 using a hardware interface (e.g., Ethernet, Wi-Fi). In at least one embodiment, the database node 114 can receive data requests from any component 112 and send or forward such requests to different components within the component 112 to receive the corresponding data requested by the requester. In at least one embodiment, the database node can send such requests to different components in a one-shot manner, where a one-shot means sending the requests to the different components simultaneously or at least minimizing the delay between each request to the corresponding component. In at least one embodiment, a one-shot means receiving the requested data from the different components within a minimal delay or interval. In at least one embodiment, the delay or interval is in the near-real-time range, or at least less than the time it takes for each component to receive the requested data from the different components using an O-RAN interface. In at least one embodiment, database node 114 provides a subscription model or service by periodically or irregularly receiving data from the various components and sending such data when the requester desires such data.
[0078] In at least one embodiment, the database node utilizes stored request data received from a plurality of components, such as, for example, volatile memory, such as flash memory, read-only memory (ROM), programmable read-only memory (PROM), cache memory, erasable programmable read-only memory (EPROM) or electrically erasable programmable read-only memory (EEPROM), random-access memory (DRAM), static random access memory (SRAM), hard disk drive (HDD), solid-state drive (SSD), network attached storage, and / or other mass storage devices. In at least one embodiment, if the database node 114 receives a data request for data stored in the database node 114, the database node 114 can simply determine whether the data is stored and send the stored data to the requester without having to send or forward the request to different components of the component 112.
[0079] In at least one embodiment, database node 114 is part of a distributed database node and is connected to other database nodes in the distributed database node via a hardware interface (e.g., Ethernet, Wi-Fi). In at least one embodiment, database node 114 is connected to core network 102 to store data generated by core network 102. In at least one embodiment, the data generated by core network 102 can be shared with component 112.
[0080] In at least one embodiment, any of the components 112 or database nodes 114 perform data processing operations on such data from any of the components 112, such as, but not limited to, data cleansing, data compression, data augmentation (e.g., augmenting online data with simulated data), combining data, data pre-processing, and other data processing operations. In at least one embodiment, any of the components 112 or database nodes 114, individually or in combination, perform operations to perform the operations to meet the data requirements of different neural networks used by different applications (e.g., xApps, rApps). In at least one embodiment, any of the components 112 or database nodes 114, individually or in combination, can generate new data based on the received data. In at least one embodiment, the database node 114 can convert the format of the received data into a different format that is consistent with the requester of the data. For example, in at least one embodiment, assuming that the requester is a near-real-time controller node 220 and the requested data is from a radio unit node 250, the database node 114 can, upon receiving the data in a first format consistent with the radio unit node 250, convert the first format into a second format consistent with the near-real-time controller node.
[0081] In at least one embodiment, the (5G-NR) network operations include, but are not limited to, optimizing the transmit power of cellular towers; predicting radio frequency (RF) signals; predicting cell site utilization based at least in part on collected data; estimating actual quality of experience (QoE) (e.g., for cloud VR gaming) based at least in part on RF signals and actual cell utilization; if in a neighboring cell, estimating QoE based on actual RF signals and actual neighboring cell utilization relative to neighboring cells; if connected to a serving cell, estimating future QoE based on predicted signals and predicted cell utilization; predicting future user equipment (UE) locations and RF signal levels as the UE moves in a certain direction; performing traffic steering; performing beamforming optimization; in at least one embodiment, performing logical network partitioning; performing RAN slicing to ensure service level agreements; performing local indoor positioning in the RAN; optimizing RAN energy efficiency and RAN sharing; optimizing RF parameters; detecting network anomalies; performing load balancing of network flows; and / or performing multi-user scheduling. In at least one embodiment, the applications include rApps and xApps to optimize network performance in the RAN. In at least one embodiment, the applications train and / or use one or more neural networks to perform operations. In at least one embodiment, the application requires a specific type of data to use and train the one or more neural networks.
[0082] In at least one embodiment, some components 112 (e.g., non-real-time controller 212, near real-time controller node 220) use or train one or more neural networks to perform the 5G-NR network operations. In at least one embodiment, the rApps and xApps are configured to use or train the one or more neural networks. In at least one embodiment, the one or more neural networks include, but are not limited to, feedforward neural networks, convolutional neural networks (CNNs), recurrent neural networks (RNNs), long short-term memory (LSTM) networks, autoencoders, generative adversarial networks (GANs), restricted Boltzmann machines (RBMs), deep belief networks (DBNs), radial basis function networks (RBFNs), Hopfield networks, self-organizing maps, perceptrons with one or more layers, modular neural networks, spike neural networks, deep reinforcement learning networks, echo state networks, time-delay neural networks, support vector machines, attention-based neural networks, autoencoders, graph neural networks, and any neural network suitable for 5G-NR network operations. In at least one embodiment, a neural network may refer to a combination of the different types of neural networks described herein (e.g., a feedforward neural network combined with a CNN).
[0083] In at least one embodiment, the neural network training for training the one or more neural networks may include information or data including, but not limited to, identifiers of different nodes of the radio access network (e.g., orchestration node 210, near real-time controller node 220, protocol node A 232, protocol node B 234, distribution unit node 240, radio unit node 250, and database node 202 as described herein), identifiers of new radio cells, physical resource block usage, reference signal received power, reference signal received power, reference signal received quality, reference signal signal-to-noise ratio, GPS coordinates of different nodes and / or user equipment, timestamps of different measurements, messages from different interfaces (e.g., E1, E2, A1, FAPI, FH-CUS, proprietary, Ethernet), number of bytes processed by the Packet Data Convergence Protocol layer, radio frequency data, beamforming coefficients, data predicted by one or more neural networks, simulation data, raw radio data, number of antennas, power of antennas, and / or various combinations thereof achieved by performing various methods or techniques described herein. In at least one embodiment, the data is from different nodes of the RAN. In at least one embodiment, the data is outside the RAN. In at least one embodiment, the data is stored as JSON, XML, a log file, CSV, YAML, XLS, binary, or other machine-readable data formats. In at least one embodiment, the information or data may change over time, and the value of the information or data in a specific time frame may be stored as time series data. In at least one embodiment, the information or data may be stored in different formats to conform to specific components. For example, in at least one embodiment, first data may be stored in a first format that conforms to, for example, a distribution unit node 240, while second data may be stored in a second format that conforms to, for example, a radio unit node 250. In at least one embodiment, the information or data may be stored in a form suitable for use as neural network training data (e.g., a matrix, vector, tensor).
[0084] In at least one embodiment, an example of using the information or data to train / use the one or more neural networks is: (1) receiving information, such as past network traffic, weather conditions, time of day, where the information includes annotated ground truth data; (2) using the received information to train the one or more neural networks to perform 5G-NR network operations (e.g., predict future traffic demand patterns); and (3) using the neural networks to generate such predictions. In at least one embodiment, database node 114 processes such information using various methods described herein.
[0085] In at least one embodiment, the information includes 5G-NR signals of O-RAN and one or more second 5G-NR information outside of O-RAN, because some components of component 112 may be O-RAN compatible, while other components of component 112 may be outside of O-RAN (non-ORAN components). In at least one embodiment, such components outside of O-RAN refer to network elements that do not belong to the O-RAN architecture but can be used in conjunction with O-RAN compatible components to build a complete 5G-NR network. In at least one embodiment, the components outside of O-RAN include a management system, dedicated hardware and / or third-party applications. In at least one embodiment, the management system is used to manage network components and monitor network performance. In at least one embodiment, the dedicated hardware is used to accelerate certain functions in the 5G-NR network, such as encryption and decryption. In at least one embodiment, the third-party applications include Figure 7 In at least one embodiment, the components outside of O-RAN include components that are part of a closed RAN, which is a monolithic RAN where one vendor provides the entire integrated system.
[0086] In at least one embodiment, the RAN 104 includes user devices 106A and 106B. In at least one embodiment, user devices 106A and 106B refer to one or more devices used by end users to access a mobile network. In at least one embodiment, user devices 106A and 106B include, but are not limited to, smartphones, tablets, laptops, and other wireless-enabled devices. In at least one embodiment, each user device includes several hardware and software components, including a modem, antenna, and baseband processor, as well as an operating system, application processor, and other software components. In at least one embodiment, these components within user devices 106A and 106B work together to enable user devices 106A and 106B to communicate with system 100, establish and maintain connections, and transfer data.
[0087] In at least one embodiment, the user devices 106A, 106B are the user devices 3308 described herein. In at least one embodiment, the user devices 106A, 106B are the user devices 3408 described herein. In at least one embodiment, the user devices 106A, 106B are the user devices 3506, 3506a described herein. In at least one embodiment, the user devices 106A, 106B are user devices 3506, 3506a described herein. Figure 36 In at least one embodiment, the user equipment 106A, 106B refers to a combination of Figure 37In at least one embodiment, the user equipment 106A, 106B is the UE 3902, 3904 described herein. In at least one embodiment, the user equipment 106A, 106B is the UE 4302 described herein.
[0088] Figure 2 An example system 200 is shown for providing access to a database storing RAN information, according to at least one embodiment. In at least one embodiment, system 100 is configured to share information stored in the database with multiple components within a 5G-NR radio access network. In at least one embodiment, system 200 is a portion of system 100.
[0089] In at least one embodiment, the system 200 includes the radio access network 104. In at least one embodiment, the system 200 may include an open RAN (O-RAN) architecture using an O-RAN interface. In at least one embodiment, the system 200 may be a cloud RAN or a centralized RAN (CRAN). In at least one embodiment, the system 200 may be a virtual RAN (vRAN).
[0090] In at least one embodiment, system 200 deploys a mobile fronthaul and midhaul network built on hardware, cloud, or a combination of cloud and hardware. In at least one embodiment, any component comprising system 200 is manufactured or configured by different vendors (e.g., NVIDIA, Ericsson, Nokia). In at least one embodiment, some components may adhere to the O-RAN architecture, while others may not.
[0091] In at least one embodiment, system 200 includes components, but is not limited to, orchestration node 210, near real-time controller node 220, protocol node A 232, protocol node B 234, distribution unit node 240, radio unit node 250, and database node 202. In at least one embodiment, at least some of orchestration node 210, near real-time controller node 220, protocol node A 232, protocol node B 234, distribution unit node 240, radio unit node 250, and database node 202 are part of a cloud computing platform (e.g., O-cloud of O-RAN), which includes a collection of physical and logical infrastructure devices that host the nodes. In at least one embodiment, the components also refer to portions of such nodes (e.g., layer 2 portion 242, layer 1 portion 244).
[0092] In at least one embodiment, the components of system 200 can be any combination of software logic, firmware logic, hardware logic and / or circuitry configured to provide the functionality described herein. In at least one embodiment, the software is embodied as a software package, code, instruction set, instruction, procedure, function, object class, instance, related data application and / or program that, as a result of being executed by one or more processors, causes system 200 to perform network operations, the processor including a central processing unit (CPU) (e.g., x86, ARM), a graphics processing unit (GPU), a data processing unit (DPU) or other hardware, such as a field programmable gate array (FPGA) or an application-specific integrated circuit (ASIC), and "hardware," as used in any embodiment described herein, includes, for example, hard-wired circuits, programmable circuits, state machine circuits, fixed function circuits, execution unit circuits and / or firmware that stores instructions executed by programmable circuits to perform network operations, alone or in any combination. In at least one embodiment, the components are collectively or individually embodied as circuitry that forms part of a larger system, such as an integrated circuit (IC), a system on a chip (SoC), and the like.
[0093] In at least one embodiment, orchestration node 210 optimizes the network performance of system 200 based at least in part on data analysis and neural network-based solutions. In at least one embodiment, orchestration node 210 includes a non-real-time controller 212 and an interface 214. In at least one embodiment, non-real-time refers to operations that take longer than one second to execute. In at least one embodiment, orchestration node 210 is specific to the O-RAN Alliance. In at least one embodiment, orchestration node 210 may be provided by various vendors. In at least one embodiment, orchestration node 210 oversees the lifecycle management of network functions in system 200. In at least one embodiment, non-real-time controller 212 performs radio network analysis and training of neural networks and other artificial intelligence models. In at least one embodiment, non-real-time controller 212 receives data from various nodes in system 200 to train the neural networks. In at least one embodiment, the neural networks are used to perform, but are not limited to, runtime execution, network slicing, security operations, role-based access control, and RAN sharing. In at least one embodiment, non-real-time controller 212 sends the trained neural networks to near-real-time controller node 220 via an interface (e.g., an A1 interface) for online prediction and execution. In at least one embodiment, orchestration node 210 performs lifecycle management of cloud-native applications (such as rApps). In at least one embodiment, orchestration node 210 manages the security of system 200 or a network including system 200. In at least one embodiment, orchestration node comprises a service management and orchestration (SMO) framework in an O-RAN architecture. In at least one embodiment, non-real-time controller 212 comprises an O-RAN non-real-time intelligent controller in an O-RAN architecture.
[0094] In at least one embodiment, the rApp is executed in conjunction with Figure 1 One of the network applications for various network operations described. In at least one embodiment, different rApps are configured by different vendors.
[0095] In at least one embodiment, interface 214 enables orchestration node 210 to communicate with near-real-time controller node 220, protocol node A 232, protocol node B 234, and distribution unit node 240 via, for example, an O1 interface. In at least one embodiment, the O1 interface is a physical or logical connection. In at least one embodiment, the O1 interface utilizes standard protocols, such as, but not limited to, Secure Shell (SSH), Transport Layer Security (TLS), and Network Configuration Protocol (NETCONF). In at least one embodiment, the O1 interface utilizes the Yang data model. In at least one embodiment, the O1 interface supports various management services, including, but not limited to, provisioning management services, fault monitoring management services, performance assurance management services, tracking management services, file management services, communication monitoring, heartbeat management services, physical network function (PNF) startup and registration management services, and PNF software management services. In at least one embodiment, orchestration node 210 utilizes the O2 interface to communicate with other nodes within the core network described herein to provide platform resources (e.g., inventory, monitoring, provisioning), software management, lifecycle management, and workload management. In at least one embodiment, orchestration node 210 executes one or more application programming interfaces (APIs) to perform the techniques and methods described herein.
[0096] In at least one embodiment, the near real-time controller node 220 uses one or more trained neural networks to perform various operations to optimize network performance. In at least one embodiment, the near real-time controller node 220 receives the trained neural network from the orchestration node 210. In at least one embodiment, near real-time refers to a time frame between 10ms and 1s. In at least one embodiment, the near real-time controller node 220 stores configurations related to other nodes, cells, bearers, flows, user equipment, and mappings therebetween. In at least one embodiment, the near real-time controller node 220 supports data pipelining. In at least one embodiment, the near real-time controller node 220 performs security functions. In at least one embodiment, the near real-time controller node 220 includes a database dedicated to the near real-time controller node 220 and capable of reading and writing RAN or UE information. In at least one embodiment, the near real-time controller node 220 uses one or more neural networks to determine how to distribute data to different installed xApps (e.g., conflict mitigation). In at least one embodiment, the near real-time controller node 220 performs monitoring of transactions on different nodes of the system 200 and generates metrics for the different nodes and xApps. In at least one embodiment, the xApp is combined with Figure 1 One of the applications described performs various operations that take less than one second. In at least one embodiment, the near real-time controller is an O-RAN near real-time RAN intelligent controller of the O-RAN architecture.
[0097] In at least one embodiment, the near real-time controller node 220 is Open RAN Alliance-specific. In at least one embodiment, the near real-time controller node 220 can be provided by different vendors. In at least one embodiment, the near real-time controller node 220 is part of a base station. In at least one embodiment, the near real-time controller node 220 is part of a next-generation Node B (gNB) supporting 5G or 4G LTE protocols. In at least one embodiment, the near real-time controller node 220 communicates with protocol node A 232, protocol node B 234, and distribution unit node 240 using an E2 interface. In at least one embodiment, the E2 interface runs over the Stream Control Transmission Protocol (SCTP). In at least one embodiment, the E2 interface supports the E2 application protocol and the E2 service model. In at least one embodiment, the E2 application protocol handles E2 setup, E2 reset, and E2 indication. In at least one embodiment, the E2 service model handles E2 reporting, E2 insertion, E2 control, and E2 policy. In at least one embodiment, the near real-time controller node 220 communicates with the orchestration node 210 using an A1 interface or an O1 interface. In at least one embodiment, the near real-time controller node 220 executes one or more APIs to perform the techniques and methods described herein.
[0098] In at least one embodiment, protocol node A 232 processes one or more higher-layer protocols. In at least one embodiment, protocol node A 232 is Open RAN Alliance-specific. In at least one embodiment, protocol node A 232 can be provided by different vendors (e.g., NVIDIA, Ericsson). In at least one embodiment, protocol node A 232 is part of a base station. In at least one embodiment, protocol node A 232 is part of a next-generation Node B (gNB) that supports 5G protocols or 4G LTE protocols. In at least one embodiment, protocol node A 232 communicates with the near-real-time controller node 220 and the distribution unit node 240 using an E2 interface. In at least one embodiment, protocol node A 232 communicates with the orchestration node 210 using an O1 interface. In at least one embodiment, protocol node A 232 communicates with protocol node B 234 using an E1 interface. In at least one embodiment, protocol node A 232 or protocol node B 234 transmits configuration data and capacity information between protocol nodes 232 and 234. In at least one embodiment, protocol node A 232 hosts the control plane portions of the Packet Data Convergence Protocol (PDCP) and Radio Resource Control (RRC). In at least one embodiment, protocol node A 232 executes one or more APIs to perform the techniques and methods described herein. In at least one embodiment, protocol node A 232 can handle more than one distribution unit node 240. In at least one embodiment, protocol node A 232 can train or use one or more neural networks to reason about data. In at least one embodiment, protocol node A 232 is the O-RAN central unit—the control plane in the O-RAN architecture.
[0099] In at least one embodiment, the protocol node B 234 processes one or more higher-layer protocols. In at least one embodiment, the protocol node B 234 is Open RAN Alliance-specific. In at least one embodiment, the protocol node B 234 may be provided by different vendors. In at least one embodiment, the protocol node B 234 is part of a base station. In at least one embodiment, the protocol node B 234 is part of a next-generation Node B (gNB) that supports 5G protocols or 4G LTE protocols. In at least one embodiment, the protocol node B 234 communicates with the near-real-time controller node 220 and the distribution unit node 240 using an E2 interface. In at least one embodiment, the protocol node B 234 communicates with the orchestration node 210 using an O1 interface. In at least one embodiment, the protocol node B 234 communicates with the protocol node A 232 using an E1 interface. In at least one embodiment, the protocol node A 232 hosts the user plane portion of the PDCP and Service Data Adaptation Protocol (SDAP). In at least one embodiment, the protocol node B 234 executes one or more APIs to perform the techniques and methods described herein. In at least one embodiment, protocol node B 234 can handle more than one distribution unit node 240. In at least one embodiment, both protocol node A 232 and protocol node B 234 are responsible for higher-level Layer 2 and Layer 3 functions. In at least one embodiment, Layer 3 is the network layer of the network stack. In at least one embodiment, protocol node B 234 can train or use one or more neural networks to reason about data. In at least one embodiment, protocol node A 232 and protocol node B 234 are part of a larger protocol node. In at least one embodiment, protocol node B 234 is the O-RAN central unit—the user plane in the O-RAN architecture.
[0100] In at least one embodiment, the distribution unit node 240 functions as a baseband processing unit. In at least one embodiment, the distribution unit node 240 performs resource pooling for virtualized baseband functions. In at least one embodiment, the distribution unit node 240 bridges the midhaul interface and the fronthaul interface. In at least one embodiment, the distribution unit node 240 is specific to the O-RAN Alliance. In at least one embodiment, the distribution unit node 240 can be provided by different vendors. In at least one embodiment, the distribution unit node 240 is part of a base station. In at least one embodiment, the distribution unit node 240 is part of a next-generation Node B (gNB) supporting 5G or 4G LTE protocols. In at least one embodiment, the distribution unit node 240 is a logical node that hosts radio link control (RLC), medium access control (MAC), and layer 1 interfaces. In at least one embodiment, layer 1 is the physical layer (the lowest layer) of the network stack. In at least one embodiment, layer 2 is the data link layer of the network stack. In at least one embodiment, the distribution unit node 240 is an O-RAN distributed unit in the O-RAN architecture.
[0101] In at least one embodiment, distribution node 240 includes a layer 1 component 244 and a layer 2 component 242. In at least one embodiment, these two components are responsible for layer 1 and layer 2 scheduling functions. In at least one embodiment, layer 1 component 244 and layer 2 component 242 can be manufactured or configured by different vendors. In at least one embodiment, distribution unit node 240 executes one or more APIs to implement the techniques and methods described herein. In at least one embodiment, distribution unit node 240 can be connected to more than one radio unit node 250.
[0102] In at least one embodiment, Layer 2 component 242 communicates with Layer 1 component 244 via an F1AP interface. Alternatively, in at least one embodiment, Layer 2 component 242 communicates with Layer 1 component 244 using a vendor-specific interface. In at least one embodiment, Layer 2 component 242 communicates with near real-time controller node 220, protocol node A 232, and protocol node B 234 using an E2 interface. In at least one embodiment, Layer 2 component 242 communicates with orchestration node 210 using an O1 interface. In at least one embodiment, Layer 2 component 242 communicates with protocol node A 232 and protocol node B 234 using an F1 interface. In at least one embodiment, Layer 2 component 242 receives various requests (e.g., configuration, data, reconfiguration, or any other information) from orchestration node 210, near real-time controller node 220, protocol node A 232, and protocol node B 234 and sends the various requests to Layer 1 component 244. In at least one embodiment, layer 2 portion 242 receives responses (eg, acknowledgments, indications, data) from layer 1 portion 244 and radio node 250 .
[0103] In at least one embodiment, Layer 1 portion 244 communicates with Layer 2 portion via an F1AP interface. In at least one embodiment, Layer 1 portion 244 communicates with radio node 250 using an FH-CUS plane interface and / or an FH-M plane interface according to a fronthaul interface library. In at least one embodiment, in response to receiving the different requests from Layer 2 portion 242, Layer 1 portion 244 sends the different requests to radio node 250. In at least one embodiment, Layer 1 portion 244 receives the responses from radio node 250 and sends the responses to Layer 2 portion 242. In at least one embodiment, Layer 1 portion 244 receives requests (e.g., configuration, reconfiguration, setup) from radio node 250 and sends the requests to Layer 2 portion 242. In at least one embodiment, Layer 2 portion 242 sends the requests to the corresponding nodes (e.g., orchestration node 210, near real-time controller node 220, protocol node A 232, and protocol node B 234) using the different interfaces described herein. In at least one embodiment, layer 1 portion 242 implements the functionality of 3GPP TS 38.211, 212, 213, 214, and 215. In at least one embodiment, distribution node 240 may train or use one or more neural networks to reason about data.
[0104] In at least one embodiment, the radio node 250 processes (e.g., converts) the radio signals sent to and from the antenna into digital signals that can be transmitted to the distribution node 240 via fronthaul. In at least one embodiment, the radio node 250 includes GPS / PTP to synchronize the radio node 250 with a precise GPS clock and time. In at least one embodiment, the radio node 250 receives synchronization information (e.g., time, frequency) from the distribution node 240. In at least one embodiment, the radio node 250 includes a radio front end that includes an antenna element array, a bandpass filter, a power amplifier, a low noise amplifier, a digital-to-analog converter, and an analog-to-digital converter. In at least one embodiment, the radio node 250 includes a digital front end that includes a digital up-converter, a digital down-converter, digital pre-distortion, and crest factor reduction. In at least one embodiment, the radio node 250 performs fast Fourier transform / inverse fast Fourier transform, in-phase / quadrature modulation / demodulation, cyclic prefix addition and removal, and digital beamforming. In at least one embodiment, the radio unit node 250 is an O-RAN radio unit in an O-RAN architecture.
[0105] In at least one embodiment, the radio unit node 250 is Open RAN Alliance specific. In at least one embodiment, the radio unit node 250 can be provided by different vendors. In at least one embodiment, the radio unit node 250 uses one or more APIs to execute the techniques and methods described herein. In at least one embodiment, the radio unit node 250 can train or use one or more neural networks to reason about data.
[0106] In at least one embodiment, database node 202 is database node 114. In at least one embodiment, database node 202 directly connects to orchestration node 210, near real-time controller node 220, protocol node A 232, protocol node B 234, distribution unit node 240, and radio unit node 250 using a hardware interface (e.g., Ethernet, Wi-Fi). In at least one embodiment, each portion of database node 202 can be adjacent to orchestration node 210, near real-time controller node 220, protocol node A 232, protocol node B 234, distribution unit node 240, and radio unit node 250.
[0107] In at least one embodiment, the database node 202 receives data requests from one or more of the near real-time controller node 220, the protocol node A 232, the protocol node B 234, the distribution unit node and the radio unit node 250, and other components and subcomponents (e.g., the non-real-time component 212, the layer 2 component 242, the layer 1 component 244). In at least one embodiment, the data may be combined Figure 1 In at least one embodiment, the database node 202 determines whether the requested data is in the Figure 1 In at least one embodiment, if the requested data is in the storage, the database node 202 sends the stored data. In at least one embodiment, if the requested data is not in the system memory or at least a portion of the data is missing, the database node 202 sends a request to another node that contains the data.
[0108] In at least one embodiment, database node 202 may use a combination of Figure 1 For example, in at least one embodiment, database 202 receives the requested data from distribution unit 240 in response to a request from orchestration node 210 and converts the format of the requested data into another format consistent with orchestration node 210. In at least one embodiment, the converted format may depend on various factors, such as, but not limited to, the type of application (xApp, rApp) being used by the component, the type of component, and the instructions listed in the data request.
[0109] In at least one embodiment, the database node 202 sends or forwards requests to multiple components in one trigger. Alternatively, in at least one embodiment, the database node 202 sends or forwards requests to multiple components based on a trigger event. In at least one embodiment, the multiple components that receive the data request send the requested data to the database node 202. In at least one embodiment, the database node 202 receives data from other components that have requested data. In at least one embodiment, the database node 202 uses a combination of Figure 1The described methods and techniques perform operations on the received data. In at least one embodiment, the database node 202 stores the received data in the storage system. In at least one embodiment, the database node 202 sends the requested data to the requester, which can be any of the near real-time controller node 220, protocol node A 232, protocol node B 234, distribution unit node, and radio unit node 250, or portions of the node (e.g., non-real-time controller 212, layer 2 portion 242, layer 1 portion 244). In at least one embodiment, the database node can be a subscription model that receives data from different components periodically or aperiodically in response to data requests.
[0110] Figure 3 A call flow diagram 300 is shown in which resources are shared by a database according to at least one embodiment. In at least one embodiment, the call flow diagram 300 enables information stored in the database to be shared with multiple components within 5G-NR. In at least one embodiment, the call flow diagram 300 is executed by a system (which may be system 100, system 200, and / or system 700 described herein).
[0111] In at least one embodiment, different components operate to share information stored in a database with multiple components within 5G-NR. In at least one embodiment, the different components include, but are not limited to, orchestration node 311, database node 312, near real-time controller node 313, distribution unit node 316 including layer 2 portion 314 and layer 1 portion 315, and radio unit node 317. In at least one embodiment, orchestration node 311 is orchestration node 210. In at least one embodiment, database node 312 is database node 202. In at least one embodiment, near real-time controller node 313 is near real-time controller node 220. In at least one embodiment, distribution unit node 316 is distribution unit node 240. In at least one embodiment, radio unit node 317 is radio unit node 250.
[0112] In at least one embodiment, orchestration node 311 requests data from one or more components including near real-time controller node 313, layer 2 components 314 and layer 1 components 315 from distribution node 316, and / or radio unit node 317. In at least one embodiment, the data may be in combination with Figure 1In at least one embodiment, orchestration node 311 sends data request 321 to database node 312. In at least one embodiment, database node 312 sends or forwards one or more data requests to near real-time controller node 313, layer 2 components 314 and layer 1 components 315 from distribution node 316, and / or radio unit node 317 using a physical interface (e.g., Ethernet, Wi-Fi). In at least one embodiment, database node 312 collects data 322 from near real-time controller node 313. In at least one embodiment, database node 312 collects data 323 from layer 2 portion 314 of distribution node 316. In at least one embodiment, database node 312 collects data 324 from layer 1 portion 314 of distribution node 316. In at least one embodiment, database node 312 collects data 325 from radio unit node 317.
[0113] In at least one embodiment, database node 312 may use a Figure 2 、 Figure 5 、 Figure 6 Various techniques and methods are described for processing data received from near real-time controller node 313, layer 2 components 314 and layer 1 components 315 from distribution node 316, and / or radio node 317. In at least one embodiment, database node 312 sends data 326 collected from database node 312 to an orchestration node. In at least one embodiment, near real-time controller node 313 can be a requester, and other nodes send data to database node 312. In at least one embodiment, layer 2 component 314 of distribution node 316 can be a requester, and other nodes send data to database node 312. In at least one embodiment, layer 1 component 315 of distribution node 316 can be a requester, and other nodes send data to database node 312. In at least one embodiment, radio node 317 can be a requester, and other nodes send data to database node 312.
[0114] In at least one embodiment, rather than sending data collected from different components (e.g., real-time controller node 313, layer 2 components 314 and layer 1 components 315 from distribution node 316, and / or radio node 317), database node 312 may first send data received from a specific component and then send other data. For example, in at least one embodiment, database node 312 receives data collected from near real-time controller node 322 and sends that data to orchestration node 311 because the data from near real-time controller node 313 is more time-sensitive. In at least one embodiment, database node 312 may pre-process data received earlier than other data received from other nodes. For example, in at least one embodiment, database node 312 may pre-process data received from near real-time controller node 322 and pre-process that data at the same time as receiving other data from other nodes (e.g., layer 2 components 314 and layer 1 components 315 from distribution node 316, and / or radio node 317). In at least one embodiment, the earlier sent data may come from other nodes (eg, from layer 2 components 314 and layer 1 components 315 of distribution node 316, and / or radio unit node 317).
[0115] Figure 4 An example call flow diagram 400 is shown in which resources are shared by a database according to at least one embodiment. In at least one embodiment, the call flow diagram 400 enables information stored in the database to be shared with multiple components within 5G-NR. In at least one embodiment, the call flow diagram 400 is performed by a system / network, which may be system 100, system 200, and / or system 700 described herein.
[0116] In at least one embodiment, orchestration node 411 is orchestration node 311 as described herein. In at least one embodiment, database node 412 is database node 312 as described herein. In at least one embodiment, near real-time controller node 413 is near real-time controller node 313 as described herein. In at least one embodiment, distribution unit node 416 is distribution unit node 316 as described herein. In at least one embodiment, radio unit node 417 is radio unit node 317 as described herein.
[0117] In at least one embodiment, various components operate to share information stored in a database with multiple components within 5G-NR. In at least one embodiment, these various components include, but are not limited to, orchestration node 411, database node 412, near real-time controller node 413, distribution unit node 416 including layer 2 portion 414 and layer 1 portion 415, and radio unit node 417. In at least one embodiment, orchestration node 411 is orchestration node 311. In at least one embodiment, database node 412 is database node 312. In at least one embodiment, near real-time controller node 413 is near real-time controller node 313. In at least one embodiment, distribution unit node 416 is distribution unit node 316. In at least one embodiment, radio unit node 417 is radio unit node 317. In at least one embodiment, layer 2 portion 414 is layer 2 portion 314. In at least one embodiment, layer 1 portion 415 is layer 1 portion 315.
[0118] In at least one embodiment, orchestration node 411 requests data from one or more components including near real-time controller node 413, layer 2 components 414 and layer 1 components 415 from distribution node 416, and / or radio unit node 417. In at least one embodiment, the data may be in combination with Figure 1 Any type of data described.
[0119] In at least one embodiment, before sending or forwarding a data request to a different component, database node 412 determines whether the requested data from orchestration node 411 is stored within database node 412. In at least one embodiment, database node 412 determines whether the data is stored within database node 412. In at least one embodiment, database node 412 may use a combination of Figure 2 、 Figure 4 、 Figure 5The methods and techniques described herein are used to process stored data. In at least one embodiment, data is stored in database node 412 as a result of its subscription service, which allows database node 412 to periodically or aperiodically receive data from the various components described herein. Alternatively, in at least one embodiment, database node 412 receives data only when triggered by an event. In at least one embodiment, database node 412 transmits data 424 collected from database node 424. In at least one embodiment, near real-time controller node 413 may be a requester and receive data from database node 412. In at least one embodiment, layer 2 component 414 of distribution node 416 may be a requester and receive data from database node 412. In at least one embodiment, layer 1 component 415 of distribution node 416 may be a requester and receive data from database node 412. In at least one embodiment, radio unit node 417 may be a requester and receive data from database node 412. In at least one embodiment, call flow may be conserved by having database node 412 transmit the requested data without sending additional requests to other nodes.
[0120] Figure 5 An example process 500 for providing access to a database storing RAN information in accordance with at least one embodiment is shown. In at least one embodiment, the process 500 enables information stored in the database to be shared with multiple components within a 5G-NR radio access network.
[0121] Although the example process 500 is described as a series of steps or operations, it should be understood that at least one embodiment of the process 500 includes changing or reordering the steps or operations, or omitting certain steps or operations (unless explicitly stated or logically required, such as when the output of one step or operation is used as the input of another step). In at least one embodiment, a system can perform each block of the process 500 described herein, wherein the system can be the system 100, system 200, and / or system 700 described herein for performing the process 500. In at least one embodiment, the system can include the database node 116 and / or the database node 202.
[0122] Alternatively or in combination, in at least one embodiment, each block of process 500 is performed using any combination of hardware, firmware, and / or software. In at least one embodiment, various functions are implemented by a processor executing instructions stored in a memory. In at least one embodiment, the method may also be embodied as computer-usable instructions (e.g., macroinstructions, microinstructions) stored on a computer storage medium or provided by a standalone application, service, or hosted service (standalone or in combination with another hosted service). In at least one embodiment, the computer-usable instructions may include executing one or more programming models (e.g., CUDA, HIP, One API, and / or variants thereof).
[0123] In at least one embodiment, at 502, the system receives a data request from a component of the RAN. In at least one embodiment, the RAN is an O-RAN. In at least one embodiment, the system receives the data request using a hardware interface (e.g., Ethernet, Wi-Fi). In at least one embodiment, the component can be a node (e.g., orchestration node 311, 411, near real-time controller node 313, 413, distributed unit node 316, 416, radio unit node 317, 417) or a portion of a node (e.g., layer 1 portion 315, 415, layer 2 portion 414, 315). In at least one embodiment, the data request is to receive data from a component of the RAN. Alternatively, in at least one embodiment, the data request is to receive different types of data (e.g., 5G-NR signals) from multiple components of the RAN. In at least one embodiment, the components in the RAN use the requested data to perform one or more network operations. In at least one embodiment, in combination Figure 1 Describe different types of data. In at least one embodiment, the data request is to periodically receive data from other components of the RAN. In at least one embodiment, the data request is to aperiodically receive data from other components of the RAN, for example, by receiving data from other components of the RAN when the data is ready to be sent.
[0124] In at least one embodiment, at 504, the system collects data from one or more other components of the RAN. In at least one embodiment, the one or more other components may include O-RAN components, non-O-RAN components, or both. In at least one embodiment, the system sends or forwards a request to the one or more other components of the RAN. In at least one embodiment, the system sends or forwards the request to the one or more other components in a single trigger. In at least one embodiment, in response to the request, the system receives the requested data from the one or more other components of the RAN. In at least one embodiment, the system communicates with the one or more other components of the RAN using a hardware interface (e.g., Ethernet, Wi-Fi). In at least one embodiment, the system waits until all requested data has been received from the one or more other components. In at least one embodiment, the system may subscribe to the one or more other components by periodically or aperiodically receiving newer versions of the requested data. In at least one embodiment, the data received as a result of the subscription may be stored as time series data.
[0125] In at least one embodiment, at 506, the system stores the received data. In at least one embodiment, the system may use, for example, a hard drive, a solid-state drive, a network-attached storage, random access memory, read-only memory, flash memory, and / or cache memory to store the requested data. In at least one embodiment, the system indexes the requested data so that the requested data is searchable. In at least one embodiment, at 508, the system sends the data to the requesting component of the RAN. In at least one embodiment, the system sends the data using a physical interface (e.g., Ethernet, Wi-Fi).
[0126] Figure 6 An example process 600 for providing access to a database storing RAN information is shown in accordance with at least one embodiment. In at least one embodiment, the process 500 enables information stored in the database to be shared with multiple components within 5G-NR. In at least one embodiment, the process 600 is performed by a system or network, which may be system 100, system 200, and / or system 700 described herein.
[0127] Although the example process 600 is described as a series of steps or operations, it should be understood that at least one embodiment of the process 600 includes changing or reordering the steps or operations, or omitting certain steps or operations (unless explicitly stated or logically required, such as when the output of one step or operation is used as the input of another step). In at least one embodiment, a system can perform each block of the process 600 described herein, wherein the system can be the system 100, system 200, and / or system 700 described herein for performing the process 600. In at least one embodiment, the system can include the database node 116 and / or the database node 202.
[0128] Alternatively or in combination, in at least one embodiment, each block of process 600 is performed using any combination of hardware, firmware, and / or software. In at least one embodiment, various functions are implemented by a processor executing instructions stored in a memory. In at least one embodiment, the method may also be embodied as computer-usable instructions (e.g., macroinstructions, microinstructions) stored on a computer storage medium or provided by a standalone application, service, or hosted service (standalone or in combination with another hosted service). In at least one embodiment, the computer-usable instructions may include executing one or more programming models (e.g., CUDA, HIP, One API, and / or variants thereof).
[0129] In at least one embodiment, at 602, the system receives a data request from a component of the RAN. In at least one embodiment, the RAN is an O-RAN. In at least one embodiment, the system receives the data request using a hardware interface (e.g., Ethernet, Wi-Fi). In at least one embodiment, the component can be a node (e.g., orchestration node 311, 411, near real-time controller node 313, 413, distributed unit node 316, 416, radio unit node 317, 417) or a portion of a node (e.g., layer 1 portion 315, 415, layer 2 portion 314, 415). In at least one embodiment, the data request is to receive data from a component of the RAN. Alternatively, in at least one embodiment, the data request is to receive different types of data (e.g., 5G-NR signals) from multiple components of the RAN. In at least one embodiment, the components in the RAN use the requested data to perform one or more network operations. In at least one embodiment, in combination Figure 1 Describe different types of data. In at least one embodiment, the data request is to periodically receive data from other components of the RAN. In at least one embodiment, the data request is to aperiodically receive data from other components of the RAN, for example, by receiving data from other components of the RAN when the data is ready to be sent.
[0130] In at least one embodiment, at 604, the system determines whether the requested data is stored in memory of the network or system, and determines that the data is stored, for example, on a hard drive, solid-state drive, network-attached storage, random access memory, read-only memory, flash memory, and / or cache memory of the system. In at least one embodiment, the system performs the determination by using an index associated with the requested data. In at least one embodiment, the system performs a database operation (e.g., a query) to retrieve the requested data stored in the system. In at least one embodiment, the at least one processor within the network or system determines that the requested data is within the system. In at least one embodiment, the data stored in the system is stored as a result of a subscription to one or more other components of the RAN.
[0131] Alternatively, in at least one embodiment, if the system determines that the requested data is not stored in the database, the system performs a combined Figure 5 In at least one embodiment, the system sends the request data within the system to the requesting component of the RAN at 606. In at least one embodiment, the system sends the data using a physical interface (e.g., Ethernet, Wi-Fi).
[0132] Figure 7 An example system 700 is shown for providing access to a database storing RAN information according to at least one embodiment. In at least one embodiment, system 700 enables information stored in the database to be shared with multiple components within 5G-NR. In at least one embodiment, system 700 can be part of system 100 and / or system 200.
[0133] In at least one embodiment, system 700 includes processor 702. In at least one embodiment, processor 702 is part of data center 800 as described herein. In at least one embodiment, processor 702 is one of processor 910, CPUs 906, 908, 918, and 920 as described herein. In at least one embodiment, processor 702 is part of CPU 980 as described herein. In at least one embodiment, processor 702 is processor 1002 as described herein. In at least one embodiment, processor 702 is processor 1110 as described herein. In at least one embodiment, processor 702 is part of CPU 1202 as described herein. In at least one embodiment, processor 702 is part of processing unit 1330 as described herein. In at least one embodiment, processor 702 is part of multi-core processor and / or multi-core processor 1406 as described herein. In at least one embodiment, processor 702 is processor 1407 as described herein. In at least one embodiment, processor 702 is part of SoC integrated circuit 1500. In at least one embodiment, processor 702 is one of processors 1802 as described herein. In at least one embodiment, the processor 702 is the processor 2002 described herein. In at least one embodiment, the processor 702 is the processor 2200 described herein. In at least one embodiment, the processor 702 is one of the processors 2302 described herein. In at least one embodiment, the processor 702 is the processor 2400 described herein.
[0134] In at least one embodiment, processor 702 is part of network 3300 as described herein. In at least one embodiment, processor 702 is part of network 3400 as described herein. In at least one embodiment, processor 702 is part of network 3500 as described herein. In at least one embodiment, processor 702 is part of network 3600 as described herein. In at least one embodiment, processor 702 is part of network 3700 as described herein. In at least one embodiment, processor 702 is part of high-level system 3800 as described herein. In at least one embodiment, processor 702 is part of system 3900 as described herein. In at least one embodiment, processor 702 is part of CPU 4008E as described herein. In at least one embodiment, processor 702 is part of system 4200 as described herein. In at least one embodiment, processor 702 is associated with RAN 4380 as described herein. In at least one embodiment, processor 702 is associated with RAN 3916 as described herein. In at least one embodiment, processor 702 is connected to components of core network 4600 as described herein. In at least one embodiment, processor 702 is part of system 4700 as described herein.
[0135] In at least one embodiment, processor 702 is part of any GPU 9087 described herein. In at least one embodiment, processor 702 is part of any GPU 984(A)...(H) described herein. In at least one embodiment, processor 702 is part of graphics / video card 1012 described herein. In at least one embodiment, processor 702 is part of parallel processing unit 1214 described herein. In at least one embodiment, processor 702 is part of any GPU 1410, 1411, 1412, 1413 described herein. In at least one embodiment, processor 702 is part of graphics acceleration 1446 described herein. In at least one embodiment, processor 702 is any of application processor 1505, graphics processor 1510, image processor 1515, video processor 1520 described herein. In at least one embodiment, processor 702 is graphics processor 1640 described herein. In at least one embodiment, processor 702 is graphics processor 1700 described herein. In at least one embodiment, processor 702 is GPGPU 1730 described herein. In at least one embodiment, processor 702 is any of the parallel processors 1812 described herein. In at least one embodiment, processor 702 is parallel processor 1900 described herein. In at least one embodiment, processor 702 is graphics multiprocessor 1934 described herein. In at least one embodiment, processor 702 is any of the GPGPUs 2006A...2006D described herein. In at least one embodiment, processor 702 is graphics processor 2100 described herein. In at least one embodiment, processor 702 is graphics processor 2408 described herein. In at least one embodiment, processor 702 is graphics processor 2500 described herein. In at least one embodiment, processor 702 is part of graphics processing engine 2610 described herein. In at least one embodiment, processor 702 is part of system 2700. In at least one embodiment, processor 702 is part of graphics execution unit 2808 described herein. In at least one embodiment, processor 702 is part of parallel processing unit 2900 described herein. In at least one embodiment, processor 702 is part of general processing cluster 3000 described herein. In at least one embodiment, processor 702 is part of streaming multiprocessor 3200 .
[0136] In at least one embodiment, processor 702 includes a database module 712 , a radio access network module 714 , a core network module 716 , and an API module 718 .
[0137] In at least one embodiment, as used in any implementation described herein, unless the context clearly dictates otherwise or clearly contradicts, terms such as "module" and nominalized verbs (e.g., compiler and / or other terms) refer to any combination of software logic, firmware logic, hardware logic, and / or circuitry configured to provide the functionality described herein. In at least one embodiment, software may be embodied as a software package, code, and / or instruction set or instructions, and "hardware," as used in any embodiment described herein, may include, for example, hardwired circuitry, programmable circuitry, state machine circuitry, fixed function circuitry, execution unit circuitry, and / or firmware that stores instructions executed by programmable circuitry, alone or in any combination. In at least one embodiment, software includes a software package, code, a programming language, a driver, instructions, an instruction set, or some combination thereof. The modules may be collectively or individually embodied as circuits forming part of a larger system, such as an integrated circuit (IC), a system on a chip (SoC), a central processing unit (CPU), a graphics processing unit (GPU), a data processing unit (DPU), a digital signal processor (DSP), a tensor processing unit (TPU), an accelerated processing unit (APU), an application specific integrated circuit (ASIC), an intelligent processing unit (IPU), a neural processing unit (NPU), a smart network interface controller (SmartNIC), a vision processing unit (VPU), a field programmable gate array (FPGA), and the like.
[0138] In at least one embodiment, database module 712 is a module that performs functions to control a database node, such as database node 114, database node 202, database node 312, and / or database node 412. In at least one embodiment, database module 712 performs steps 322, 323, 324, 325, and 326. In at least one embodiment, database module 712 performs step 422. In at least one embodiment, database module 712 performs steps 502, 504, 506, and 508. In at least one embodiment, database module 712 performs steps 602, 604, and 606.
[0139] In at least one embodiment, the radio access network module 714 is a module for performing functions to control a RAN, such as the RAN 104 and / or the system 200. In at least one embodiment, the core network module 716 is a module for performing one or more functions to control a core network, such as the core network 102.
[0140] In at least one embodiment, the API module 718 is a module that executes one or more APIs, calls APIs, or otherwise uses APIs. In at least one embodiment, the APIs include network-related APIs, such as 5G core network APIs, 5G RAN APIs, multi-access edge computing (MEC) APIs, and IoT APIs. In at least one embodiment, the 5G core network APIs include interfaces such as network function virtualization infrastructure (NFVI), network slice subnet management (NSSM), network exposure function (NEF), and service-based interface (SBI). In at least one embodiment, the 5G RAN API allows external applications or systems to interact with 5G RAN functions, including base stations or gNodeBs, and includes interfaces such as gNodeB application protocol (NGAP), Xn application protocol (XnAP), and E1 interface. In at least one embodiment, the MEC API enables computing and storage capabilities to be closer to end users, thereby enabling low latency and high bandwidth applications such as augmented reality (AR) and virtual reality (VR). In at least one embodiment, the MEC API allows external applications or systems to interact with the MEC platform, thereby enabling access to computing and storage resources, and includes interfaces such as mobile edge computing (MEC), service capability exposure function (SCEF), mobile edge computing application programming interface (API-MEC), and network exposure function (NEF). In at least one embodiment, the IoT API is capable of connecting to a wide range of devices and sensors. In at least one embodiment, the IoT API allows external applications or systems to interact with the IoT platform, thereby enabling collection and analysis of IoT data, and includes interfaces such as OneM2M interface, lightweight machine-to-machine (LwM2M) interface, and constrained application protocol (CoAP).
[0141] In at least one embodiment, the API may be a neural network training and inference API for RAN components, such as orchestration node 210 and / or near real-time controller node 220. For example, in at least one embodiment, the API may include, but is not limited to, TensorFlow (e.g., TensorFlow Lite), PyTorch (e.g., PyTorch Lightning), Keras, Caffe, MXNET, Theano, NVIDIA CUDA, OpenCV, TensorRT, ONNX, Intel, and / or OpenVINO.
[0142] In at least one embodiment, the API module 718 may be used in conjunction with other modules (e.g., the database module 712, the radio access network module 714, the core network module 716) to perform various 5G-NR network operations.
[0143] In at least one embodiment, the techniques and methods described herein reduce the time and resource usage of nodes within a system, including a RAN. In at least one embodiment, the techniques and methods described herein enable nodes within a system to communicate efficiently without being constrained by the architecture of the RAN. For example, in at least one embodiment, the techniques and methods described herein do not require one or more data reformatting operations for different interfaces of the RAN. In at least one embodiment, the techniques and methods described herein enable efficient use of bandwidth across different interfaces of the RAN. In at least one embodiment, the techniques and methods described herein provide greater flexibility for a system to include different nodes from different entities that manufacture different equipment for the RAN.
[0144] Data Center
[0145] Figure 8 An example data center 800 is shown in which at least one embodiment may be used. In at least one embodiment, the data center 800 includes a data center infrastructure layer 810, a framework layer 820, a software layer 830, and an application layer 840.
[0146] In at least one embodiment, Figure 8 As shown, the data center infrastructure layer 810 may include a resource coordinator 812, grouped computing resources 814, and node computing resources ("node CRs") 816(1)-816(N), where "N" represents any integer, positive integer. In at least one embodiment, the node CRs 816(1)-816(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 memories), 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 node CRs 816(1)-816(N) may be servers having one or more of the above-mentioned computing resources.
[0147] In at least one embodiment, the grouped computing resources 814 may include separate groups of node CRs housed in one or more racks (not shown), or may include many racks (also not shown) housed in data centers at various geographic locations. In at least one embodiment, the separate groups of node CRs within the grouped computing resources 814 may include computing, networking, memory, or storage resources that may be configured or allocated to support groupings of one or more workloads. In at least one embodiment, several node CRs including CPUs or processors may be grouped in one or more racks to provide computing resources to support one or more workloads. In at least one embodiment, one or more racks may also include any number of power modules, cooling modules, and network switches, in any combination.
[0148] In at least one embodiment, a resource coordinator 812 may configure or otherwise control one or more node CRs 816(1)-816(N) and / or grouped computing resources 814. In at least one embodiment, the resource coordinator 812 may comprise a software design infrastructure ("SDI") management entity for the data center 800. In at least one embodiment, the resource coordinator may comprise hardware, software, or some combination thereof.
[0149] In at least one embodiment, Figure 8 As shown, the framework layer 820 includes a job scheduler 832, a configuration manager 834, a resource manager 836, and a distributed file system 838. In at least one embodiment, the framework layer 820 may include a framework that supports the software 832 of the software layer 830 and / or one or more applications 842 of the application layer 840. In at least one embodiment, the software 832 or the application 842 may include web-based service software or applications, such as those provided by Amazon Web Services, Google Cloud, and Microsoft Azure. In at least one embodiment, the framework layer 820 may be, but is not limited to, a free and open source software web application framework, such as Apache Spark, which can utilize the distributed file system 838 to perform large-scale data processing (e.g., "big data"). TM(hereinafter referred to as "Spark"). In at least one embodiment, the job scheduler 832 may include a Spark driver to facilitate scheduling of workloads supported by the various layers of the data center 800. In at least one embodiment, the configuration manager 834 may be capable of configuring the different layers, such as the software layer 830 and the framework layer 820 including Spark and a distributed file system 838 for supporting large-scale data processing. In at least one embodiment, the resource manager 836 may be capable of managing the cluster or group computing resources mapped to or allocated to support the distributed file system 838 and the job scheduler 832. In at least one embodiment, the cluster or group computing resources may include the group computing resources 814 on the data center infrastructure layer 810. In at least one embodiment, the resource manager 836 may coordinate with the resource coordinator 812 to manage these mapped or allocated computing resources.
[0150] In at least one embodiment, the software 832 included in the software layer 830 may include software used by at least a portion of the node CRs 816(1)-816(N), the grouped computing resources 814, and / or the distributed file system 838 of the framework layer 820. In at least one embodiment, the 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.
[0151] In at least one embodiment, the one or more applications 842 included in the application layer 840 may include one or more types of applications used by at least a portion of the node CRs 816(1)-816(N), the grouped computing resources 814, and / or the distributed file system 838 of the framework layer 820. In at least one embodiment, the 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.
[0152] In at least one embodiment, any of the configuration manager 834, the resource manager 836, and the resource coordinator 812 can implement any number and type of self-modification actions based on any number and type of data obtained in any technically feasible manner. In at least one embodiment, the self-modification actions can relieve the data center operator of the data center 800 from making potentially poor configuration decisions and can avoid underutilized and / or poorly performing portions of the data center.
[0153] In at least one embodiment, the data center 800 may include tools, services, software, or other resources to train one or more machine learning models or 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 according to a neural network architecture using the software and computing resources described above with respect to the data center 800. In at least one embodiment, using the weight parameters calculated using one or more training techniques described herein, a trained machine learning model corresponding to one or more neural networks can be used to infer or predict information using the resources described above with respect to the data center 800.
[0154] In at least one embodiment, the data center 800 can use a CPU, an application-specific integrated circuit (ASIC), a GPU, an FPGA, or other hardware to use the above resources to perform training and / or reasoning. In addition, one or more of the above software and / or hardware resources can be configured as a service to allow users to train or perform information reasoning, such as image recognition, speech recognition, or other artificial intelligence services.
[0155] Figure 1-8 The information stored in the database is shared with multiple components within the fifth generation new radio (5G-NR) radio access network. For example, according to at least one embodiment, the data center provides access to the database storing RAN information. In at least one embodiment, the data center 800 includes Figure 1-7 and performing processes 500 and 600.
[0156] Figure 9A An example of an autonomous vehicle 900 according to at least one embodiment is shown. In at least one embodiment, autonomous vehicle 900 (alternatively referred to herein as "vehicle 900") can be, but is not limited to, a passenger vehicle, such as a car, truck, bus, and / or another type of vehicle that can accommodate one or more passengers. In at least one embodiment, vehicle 900 can be a semi-tractor-trailer for hauling cargo. In at least one embodiment, vehicle 900 can be an aircraft, a robotic vehicle, or another type of vehicle.
[0157] An autonomous vehicle may be described according to the automation levels defined by the National Highway Traffic Safety Administration ("NHTSA") and the Society of Automotive Engineers ("SAE") under the U.S. Department of Transportation, "Taxonomy and Definitions for Terms Related to Driving Automation Systems for On-Road Motor Vehicles" (e.g., Standard No. J3016-201806, issued on June 15, 2018, Standard No. J3016-201609, issued on September 30, 2016, and previous and future versions of this standard). In one or more embodiments, the vehicle 900 may be capable of functioning according to one or more of the levels 1 to 5 of automated driving. For example, in at least one embodiment, the vehicle 900 may be capable of conditional automation (level 3), high automation (level 4), and / or full automation (level 5), depending on the embodiment.
[0158] In at least one embodiment, the vehicle 900 may include, but is not limited to, components such as a chassis, a body, wheels (e.g., 2, 4, 6, 8, 18, etc.), tires, axles, and other components of the vehicle. In at least one embodiment, the vehicle 900 may include, but is not limited to, a propulsion system 950, such as an internal combustion engine, a hybrid power plant, an all-electric engine, and / or another type of propulsion system. In at least one embodiment, the propulsion system 950 may be connected to a drive train of the vehicle 900, which may include, but is not limited to, a transmission, to enable propulsion of the vehicle 900. In at least one embodiment, the propulsion system 950 may be controlled in response to receiving a signal from a throttle / accelerator 952.
[0159] In at least one embodiment, when propulsion system 950 is operating (e.g., when vehicle 900 is traveling), a steering system 954 (which may include, but is not limited to, a steering wheel) is used to steer vehicle 900 (e.g., along a desired path or route). In at least one embodiment, steering system 954 may receive signals from steering actuator 956. In at least one embodiment, a steering wheel may be optional for fully automated (Level 5) functionality. In at least one embodiment, brake sensor system 946 may be used to operate vehicle brakes in response to signals received from brake actuator 948 and / or brake sensors.
[0160] In at least one embodiment, the controller 936 may include, but is not limited to, one or more system-on-chips ("SoCs") ( Figure 9A) and / or a graphics processing unit ("GPU") provides signals (e.g., representing commands) to one or more components and / or systems of the vehicle 900. For example, in at least one embodiment, the controller 936 can send signals to operate the vehicle brakes via the brake actuator 948, operate the steering system 954 via one or more steering actuators 956, and operate the propulsion system 950 via one or more throttles / accelerators 952. In at least one embodiment, the one or more controllers 936 may include one or more onboard (e.g., integrated) computing devices (e.g., supercomputers) that process sensor signals and output operational commands (e.g., signals representing commands) to implement autonomous driving and / or assist the driver in driving the vehicle 900. In at least one embodiment, the one or more controllers 936 may include a first controller 936 for autonomous driving functions, a second controller 936 for functional safety functions, a third controller 936 for artificial intelligence functions (e.g., computer vision), a fourth controller 936 for infotainment functions, a fifth controller 936 for redundancy in emergency situations, and / or other controllers. In at least one embodiment, a single controller 936 may handle two or more of the above functions, two or more controllers 936 may handle a single function, and / or any combination thereof.
[0161] In at least one embodiment, the one or more controllers 936 provide signals for controlling one or more components and / or systems of the vehicle 900 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 such as, but not limited to, one or more global navigation satellite system ("GNSS") sensors 958 (e.g., one or more global positioning system sensors), one or more RADAR sensors 960, one or more ultrasonic sensors 962, one or more LIDAR sensors 964, one or more inertial measurement unit (IMU) sensors 966 (e.g., one or more accelerometers, one or more gyroscopes, one or more magnetic compasses, one or more magnetometers, etc.), one or more microphones 996, one or more stereo cameras 968, one or more wide angle cameras 970 (e.g., fisheye cameras), one or more infrared cameras 972, one or more surround cameras 974 (e.g., 360 degree cameras), long range cameras (e.g., infrared cameras), and / or a combination of these. Figure 9A Not shown), mid-range camera ( Figure 9A), one or more speed sensors 944 (e.g., for measuring the speed of the vehicle 900), one or more vibration sensors 942, one or more steering sensors 940, one or more brake sensors (e.g., as part of a brake sensor system 946), and / or other sensor types are received.
[0162] In at least one embodiment, one or more controllers 936 may receive input (e.g., represented by input data) from the instrument panel 932 of the vehicle 900 and provide output (e.g., represented by output data, display data, etc.) via a human machine interface ("HMI") display 934, an audible annunciator, a speaker, and / or other components of the vehicle 900. In at least one embodiment, the output may include information such as vehicle speed, velocity, time, map data (e.g., high definition map ( Figure 9A ), location data (e.g., the location of the vehicle 900, such as on a map), directions, the locations of other vehicles (e.g., occupancy barriers), information about objects and the states of objects sensed by the one or more controllers 936, etc. For example, in at least one embodiment, the HMI display 934 can display information about the presence of one or more objects (e.g., road signs, warning signs, traffic light changes, etc.) and / or information about the driving maneuvers the vehicle has made, is making, or will make (e.g., changing lanes now, taking exit 34B in two miles, etc.).
[0163] In at least one embodiment, the vehicle 900 further includes a network interface 924 that can communicate over one or more networks using one or more wireless antennas 926 and / or one or more modems. For example, in at least one embodiment, the network interface 924 may be capable of communicating over Long Term Evolution ("LTE"), Wideband Code Division Multiple Access ("WCDMA"), Universal Mobile Telecommunications System ("UMTS"), Global System for Mobile Communications ("GSM"), IMT-CDMA Multi-Carrier ("CDMA2000") networks, etc. In at least one embodiment, the one or more wireless antennas 926 can also use 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 referred to as "LPWAN") (e.g., protocols such as LoRaWAN, SigFox, etc.) to enable communication between objects in the environment (e.g., vehicles, mobile devices).
[0164] Figure 1-9AThe information stored in the database is shared with various components within a fifth generation new radio (5G-NR) radio access network. For example, according to at least one embodiment, a data center provides access to a database storing RAN information. For example, according to at least one embodiment, vehicle 900 may be one of the user devices that is part of RAN 104.
[0165] Figure 9B According to at least one embodiment, Figure 9A Examples of camera locations and fields of view for autonomous vehicle 900 are shown. In at least one embodiment, the cameras and respective fields 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 in different locations on vehicle 900.
[0166] In at least one embodiment, the camera type used for the camera may include, but is not limited to, a digital camera that may be suitable for use with components and / or systems of the vehicle 900. 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), 1220fps, 240fps, etc., depending on the embodiment. In at least one embodiment, the camera may be capable of using 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-clear-clear ("RCCC") filter array, a red-clear-clear-blue ("RCCB") filter array, a red-blue-green-clear ("RBGC") filter array, a Foveon X3 filter array, a Bayer sensor ("RGGB") filter array, a monochrome sensor filter array, and / or other types of filter arrays. In at least one embodiment, a clear pixel camera, such as one having an RCCC, RCCB, and / or RBGC color filter array, may be used in an effort to increase photosensitivity.
[0167] In at least one embodiment, one or more cameras can be used to perform advanced driver assistance system ("ADAS") functions (e.g., as part of a redundant or fail-safe design). For example, in at least one embodiment, a multi-function mono camera can be installed to provide functions including lane departure warning, traffic sign assistance, and intelligent headlight control. In at least one embodiment, one or more cameras (e.g., all cameras) can simultaneously record and provide image data (e.g., video).
[0168] In at least one embodiment, one or more cameras can be mounted in a mounting assembly, such as a custom designed (three-dimensional ("3D") printed) assembly, so as to cut out stray light and reflections from within the vehicle (e.g., reflections of the dashboard reflecting in the windshield mirror) that may interfere with the camera's image data capture capabilities. With respect to the rearview mirror mounting assembly, in at least one embodiment, the rearview mirror assembly can be 3D printed custom so that the camera mounting plate matches the shape of the rearview mirror. In at least one embodiment, one or more cameras can be integrated into the rearview mirror. In at least one embodiment, for side-view cameras, one or more cameras can also be integrated into the four pillars at each corner of the cabin.
[0169] In at least one embodiment, a camera (e.g., a forward-facing camera) having a field of view that includes a portion of the environment in front of the vehicle 900 can be used for surround vision, as well as to help identify the forward path and obstacles with the assistance of one or more controllers 936 and / or control SoCs, thereby providing information that is critical 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 ADAS functions similar to 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"), automatic cruise control ("ACC"), and / or other functions (e.g., traffic sign recognition).
[0170] 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 970 can be used to sense objects entering from the periphery (e.g., pedestrians, people crossing the road, or bicycles). Although Figure 9B Only one wide-angle camera 970 is shown in FIG. 1 , however, in other embodiments, any number (including zero) of wide-angle cameras 970 may be present on the vehicle 900. In at least one embodiment, any number of remote cameras 998 (e.g., a remote stereo camera pair) may be used for depth-based object detection, particularly for objects for which a neural network has not yet been trained. In at least one embodiment, the remote cameras 998 may also be used for object detection and classification, as well as basic object tracking.
[0171] In at least one embodiment, any number of stereo cameras 968 may also be included in the forward configuration. In at least one embodiment, one or more stereo cameras 968 may include an integrated control unit including 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 900, including distance estimates for all points in the image. In at least one embodiment, one or more stereo cameras 968 may include, but are not limited to, a compact stereo vision sensor, which may include, but are not limited to, two camera lenses (one on each side) and an image processing chip that may measure the distance from the vehicle 900 to the 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 968 may be used in addition to those described herein.
[0172] In at least one embodiment, a camera having a field of view of a portion of the environment including the sides of the vehicle 900 (e.g., a side view camera) can be used for surround viewing to provide information for creating and updating occupancy grids and generating side collision warnings. For example, in at least one embodiment, the surround camera 974 (e.g., Figure 9B Four surround cameras 974 (shown) can be positioned on the vehicle 900. In at least one embodiment, the one or more surround cameras 974 can include, but are not limited to, any number and combination of wide-angle cameras 970, one or more fish-eye lenses, one or more 360-degree cameras, and / or the like. For example, in at least one embodiment, four fish-eye lens cameras can be located on the front, rear, and sides of the vehicle 900. In at least one embodiment, the vehicle 900 can use three surround cameras 974 (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.
[0173] In at least one embodiment, a camera having a field of view that includes a portion of the environment behind the vehicle 900 (e.g., a rearview camera) can be used for parking assistance, surround view, rear collision warning, and creating and updating occupancy grids. In at least one embodiment, a 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 998 and / or one or more mid-range cameras 976, one or more stereo cameras 968, one or more infrared cameras 972, etc.), as described herein.
[0174] Figure 1-9BThe information stored in the database will be shared with multiple components within the fifth generation new radio (5G-NR) radio access network. For example, according to at least one embodiment, the vehicle 900 can be one of the user devices that is part of the RAN 104.
[0175] Figure 9C According to at least one embodiment, Figure 9A A block diagram of an example system architecture for an autonomous vehicle 900 is provided. In at least one embodiment, Figure 9C Each of the one or more components, one or more features, and one or more systems of the vehicle 900 is shown as being connected via a bus 902. In at least one embodiment, the bus 902 may include, but is not limited to, a CAN data interface (alternatively referred to herein as a "CAN bus"). In at least one embodiment, the CAN may be a network internal to the vehicle 900 that helps control various features and functions of the vehicle 900, such as brake actuation, acceleration, braking, steering, wipers, etc. In one embodiment, the bus 902 may be configured to have dozens or even hundreds of nodes, each with its own unique identifier (e.g., a CAN ID). In at least one embodiment, the bus 902 may be read to find steering wheel angle, ground speed, engine revolutions per minute ("RPM"), button positions, and / or other vehicle status indicators. In at least one embodiment, the bus 902 may be an ASIL B compliant CAN bus.
[0176] In at least one embodiment, FlexRay and / or Ethernet may be used in addition to or in addition to CAN. In at least one embodiment, there may be any number of buses 902, 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 902 may be used to perform different functions and / or may be used for redundancy. For example, a first bus 902 may be used for collision avoidance functionality, and a second bus 902 may be used for actuation control. In at least one embodiment, each bus 902 may communicate with any component of the vehicle 900, and two or more buses 902 may communicate with the same component. In at least one embodiment, each of any number of system-on-chips ("SoCs") 904, each of one or more controllers 936, and / or each computer within the vehicle may have access to the same input data (e.g., input from sensors in the vehicle 900) and may be connected to a common bus, such as a CAN bus.
[0177] In at least one embodiment, the vehicle 900 may include one or more controllers 936, such as those described herein with respect to Figure 9A In at least one embodiment, one or more controllers 936 can be used for multiple functions. In at least one embodiment, controller 936 can be coupled to any of the various other components and systems of vehicle 900 and can be used to control vehicle 900, artificial intelligence of vehicle 900, infotainment and / or other functions of vehicle 900.
[0178] In at least one embodiment, the vehicle 900 may include any number of SoCs 904. In at least one embodiment, each of the SoCs 904 may include, but is not limited to, a central processing unit ("CPU(s)") 906, a graphics processing unit ("GPU(s")) 908, one or more processors 910, one or more caches 912, one or more accelerators 914, one or more data storage devices 916, and / or other components and features not shown. In at least one embodiment, the one or more SoCs 904 may be used to control the vehicle 900 in various platforms and systems. For example, in at least one embodiment, the one or more SoCs 904 may be combined in a system (e.g., a system of the vehicle 900) with a high-definition ("HD") map 922 that may be downloaded from one or more servers (e.g., a system of the vehicle 900) via a network interface 924. Figure 9C ) to obtain map refreshes and / or updates.
[0179] In at least one embodiment, one or more CPUs 906 may include a CPU cluster or CPU complex (alternatively referred to herein as a "CCPLEX"). In at least one embodiment, one or more CPUs 906 may include multiple cores and / or a second level ("L2") cache. For example, in at least one embodiment, one or more CPUs 906 may include eight cores in a mutually coupled multiprocessor configuration. In at least one embodiment, one or more CPUs 906 may include four dual-core clusters, each with a dedicated L2 cache (e.g., a 2MB L2 cache). In at least one embodiment, one or more CPUs 906 (e.g., CCPLEX) may be configured to support simultaneous cluster operations such that any combination of clusters of one or more CPUs 906 may be active at any given time.
[0180] In at least one embodiment, one or more CPUs 906 may implement power management functionality including, but not limited to, one or more of the following features: automatic clock gating of various hardware modules when idle to save dynamic power; clock gating of each core when the core is not actively executing instructions due to executing a wait for interrupt ("WFI") / wait for event ("WFE") instruction; each core may be independently powered; each core cluster may be independently clock gated when all cores are clock gated or power gated; and / or each core cluster may be independently power gated when all cores are power gated. In at least one embodiment, one or more CPUs 906 may further implement an enhanced algorithm for managing power states, wherein allowed power states and expected wakeup times are specified, and hardware / microcode determines the optimal power state for the core, cluster, and CCPLEX input. In at least one embodiment, the processing core may support a simplified power state entry sequence in software, where the work is offloaded to the microcode. In at least one embodiment, the processing core is referred to as a computational unit or an operational unit.
[0181] In at least one embodiment, one or more GPUs 908 may include an integrated GPU (or referred to herein as an "iGPU"). In at least one embodiment, one or more GPUs 908 may be programmable and may be efficient for parallel workloads. In at least one embodiment, one or more GPUs 908 may use an enhanced tensor instruction set. In one embodiment, one or more GPUs 908 may include one or more streaming microprocessors, each of which may include a level 1 ("L1") cache (e.g., an L1 cache with at least 96KB of storage capacity), and two or more streaming microprocessors may share an L2 cache (e.g., an L2 cache with 512KB of storage capacity). In at least one embodiment, one or more GPUs 908 may include at least eight streaming microprocessors. In at least one embodiment, one or more GPUs 908 may use a computing application programming interface (API). In at least one embodiment, one or more GPUs 908 may use one or more parallel computing platforms and / or programming models (e.g., NVIDIA's CUDA model).
[0182] In at least one embodiment, one or more GPUs 908 may be power-optimized for optimal performance in automotive and embedded use cases. For example, in one embodiment, one or more GPUs 908 may be fabricated on fin field-effect transistor (“FinFET”) circuits. 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 warp scheduler, a dispatch unit, and / or a 64KB 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 compute and addressing operations. In at least one embodiment, the streaming microprocessor may include independent thread scheduling capabilities to enable finer-grained synchronization and collaboration between parallel threads. In at least one embodiment, a streaming microprocessor may include a combined L1 data cache and shared memory unit to improve performance while simplifying programming.
[0183] In at least one embodiment, one or more GPUs 908 may include high bandwidth memory ("HBM") and / or a 16GB HBM2 memory subsystem to provide a peak memory bandwidth of approximately 900 GB / s in some examples. In at least one embodiment, synchronous graphics random access memory ("SGRAM"), such as graphics double data rate type five synchronous random access memory ("GDDR5"), may be used in addition to or in lieu of HBM memory.
[0184] In at least one embodiment, one or more GPUs 908 may include unified memory technology. In at least one embodiment, address translation service ("ATS") support may be used to allow one or more GPUs 908 to directly access one or more CPU 906 page tables. In at least one embodiment, when a memory management unit ("MMU") of a GPU in one or more GPUs 908 experiences a miss, an address translation request may be sent to one or more CPUs 906. In response, in at least one embodiment, one or more CPUs 906 may look up the virtual-to-physical mapping of the address in its page table and transmit the translation back to the one or more GPUs 908. In at least one embodiment, unified memory technology may allow a single unified virtual address space to be used for memory for both one or more CPUs 906 and one or more GPUs 908, thereby simplifying programming of one or more GPUs 908 and porting applications to one or more GPUs 908.
[0185] In at least one embodiment, one or more GPUs 908 may include any number of access counters that can track the frequency with which one or more GPUs 908 access the memory of other processors. In at least one embodiment, the one or more access counters can help ensure that memory pages are moved to the physical memory of the processor that accesses the page most frequently, thereby improving the efficiency of memory ranges shared between processors.
[0186] In at least one embodiment, one or more SoCs 904 may include any number of caches 912, including those described herein. For example, in at least one embodiment, one or more caches 912 may include a level 3 ("L3") cache available for one or more CPUs 906 and one or more GPUs 908 (e.g., connected to the CPUs 906 and GPUs 908). In at least one embodiment, one or more caches 912 may include a write-back cache that can track the state of a line, for example, by using a cache coherence protocol (e.g., MEI, MESI, MSI, etc.). In at least one embodiment, the L3 cache may include 4MB of memory or more, depending on the embodiment, although smaller cache sizes may be used.
[0187] In at least one embodiment, one or more SoCs 904 may include one or more accelerators 914 (e.g., hardware accelerators, software accelerators, or a combination thereof). In at least one embodiment, one or more SoCs 904 may include a hardware acceleration cluster that 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) may enable the hardware acceleration cluster to accelerate neural networks and other calculations. In at least one embodiment, the hardware acceleration cluster may be used to supplement one or more GPUs 908 and offload some tasks of one or more GPUs 908 (e.g., freeing up more cycles of one or more GPUs 908 to perform other tasks). In at least one embodiment, one or more accelerators 914 may be used for target workloads that are sufficiently stable to withstand acceleration testing (e.g., perception, convolutional neural networks ("CNN"), recurrent neural networks ("RNN"), etc.). In at least one embodiment, the CNN may include a region-based or region-based convolutional neural network ("RCNN") and a fast RCNN (e.g., as used for object detection) or other types of CNN.
[0188] In at least one embodiment, one or more accelerators 914 (e.g., a hardware acceleration cluster) may include one or more deep learning accelerators ("DLAs"). In at least one embodiment, one or more DLAs may include, but are not limited to, one or more tensor processing units ("TPUs") that may be configured to provide an additional 10 trillion operations per second for deep learning applications and inference. In at least one embodiment, a TPU may be an accelerator configured and optimized to perform image processing functions (e.g., for CNN, RCNN, etc.). In at least one embodiment, one or more DLAs may be further optimized for a specific set of neural network types and floating-point operations and inference. In at least one embodiment, the design of one or more DLAs may provide higher performance per millimeter than a typical general-purpose GPU, and generally significantly exceeds the performance of a CPU. In at least one embodiment, one or more TPUs may perform several functions, including single-instance convolution functions that support, for example, INT9, 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 quickly and efficiently execute neural networks, particularly CNNs, on processed or unprocessed data for any of a variety of functions, including, for example, but not limited to: a CNN for object recognition and detection using data from a camera sensor; a CNN for distance estimation using data from a camera sensor; a CNN for emergency vehicle detection and recognition and detection using data from microphone 996; a CNN for face recognition and vehicle owner recognition using data from a camera sensor; and / or a CNN for safety and / or security-related events.
[0189] In at least one embodiment, a DLA can perform any function of one or more GPUs 908, and by using an inference accelerator, for example, a designer can target any function to either one or more DLAs or one or more GPUs 908. For example, in at least one embodiment, a designer can focus CNN processing and floating-point operations on one or more DLAs and leave other functions to one or more GPUs 908 and / or one or more accelerators 914.
[0190] In at least one embodiment, one or more accelerators 914 (e.g., a hardware acceleration cluster) may include a programmable vision accelerator ("PVA"), which may be referred to herein alternatively as a computer vision accelerator. 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") 938, 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 the 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.
[0191] In at least one embodiment, the RISC core can interact with an image sensor (e.g., an image sensor of any camera described herein), an image signal processor, and the like. In at least one embodiment, each RISC core can include any amount of memory. In at least one embodiment, the RISC core can use any of a variety of protocols, depending on the embodiment. In at least one embodiment, the RISC core can execute a real-time operating system ("RTOS"). In at least one embodiment, the RISC core can be implemented using one or more integrated circuit devices, application specific integrated circuits ("ASICs"), and / or memory devices. For example, in at least one embodiment, the RISC core can include an instruction cache and / or tightly coupled RAM.
[0192] In at least one embodiment, the DMA can enable components of the PVA to access system memory independently of the one or more CPUs 906. In at least one embodiment, the DMA can support any number of features for providing optimizations to the PVA, including, but not limited to, support for multi-dimensional addressing and / or circular addressing. In at least one embodiment, the DMA can support up to six or more dimensions of addressing, which can include, but are not limited to, block width, block height, block depth, horizontal block stride, vertical block stride, and / or depth stride.
[0193] In at least one embodiment, the vector processor can be a programmable processor that can be designed to efficiently and flexibly execute programming for computer vision algorithms and provide signal processing capabilities. In at least one embodiment, the PVA can include a PVA core and two vector processing subsystem partitions. In at least one embodiment, the PVA core can 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 can serve as the main processing engine of the PVA and can 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 can include a digital signal processor, such as a single instruction multiple data ("SIMD"), a very long instruction word ("VLIW") digital signal processor. In at least one embodiment, the combination of SIMD and VLIW can increase throughput and speed.
[0194] 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 the other vector processors. In at least one embodiment, the vector processors included in a particular PVA may be configured to exploit data parallelism. For example, in at least one embodiment, multiple vector processors included in a single PVA may execute a common computer vision algorithm, except on different regions of an image. In at least one embodiment, the vector processors included in a particular PVA may execute different computer vision algorithms simultaneously on an image, or even different algorithms on sequenced images or portions of images. In at least one embodiment, any number of PVAs may be included in a hardware acceleration cluster, and any number of vector processors may be included in each PVA, among other things. In at least one embodiment, the PVAs may include additional error correction code ("ECC") memory to enhance overall system security.
[0195] In at least one embodiment, one or more accelerators 914 (e.g., a hardware acceleration cluster) may include an on-chip computer vision network and static random access memory ("SRAM") to provide high bandwidth, low latency SRAM to one or more accelerators 914. In at least one embodiment, the on-chip memory may include at least 4MB of SRAM, including, for example, but not limited to, eight field-configurable memory blocks that can be accessed by both the PVA and the 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 the DLA may access the memory via a backbone network that provides high-speed access to the memory to the PVA and the DLA. In at least one embodiment, the backbone network may include an on-chip computer vision network that interconnects the PVA and the DLA to the memory (e.g., using APB).
[0196] 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 sending control signals / addresses / data, as well as burst-type communication for continuous data transmission. In at least one embodiment, the interface may comply with the International Organization for Standardization ("ISO") 26262 or International Electrotechnical Commission ("IEC") 61508 standards, although other standards and protocols may be used.
[0197] In at least one embodiment, one or more SoCs 904 may include a real-time gaze tracking hardware accelerator. In at least one embodiment, the real-time gaze tracking hardware accelerator may be used to quickly and efficiently determine the position and range of objects (e.g., within a world model) to generate real-time visual simulations for use in RADAR signal interpretation, for sound propagation synthesis and / or analysis, for simulation of SONAR systems, for general wave propagation simulations, for comparison with LIDAR data for positioning and / or other functions, and / or for other uses.
[0198] In at least one embodiment, one or more accelerators 914 (e.g., a hardware acceleration cluster) have a wide range of uses for autonomous driving. In at least one embodiment, the PVA can be a programmable vision accelerator that is used in key 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 the algorithmic domain that requires predictable processing. In other words, the PVA performs well in semi-intensive or intensive conventional computations, even on small data sets, which may require predictable runtimes with low latency and low power. In at least one embodiment, an autonomous vehicle, such as in vehicle 900, may be designed to run classic computer vision algorithms because they can be efficient at object detection and integer math operations.
[0199] 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 can be used in some examples, although this is not meant to be limiting. In at least one embodiment, applications for Level 3-5 autonomous driving use dynamic estimation / stereo matching on the fly (e.g., structure from motion, pedestrian recognition, lane detection, etc.). In at least one embodiment, PVA can perform computer stereo vision functions on input from two monocular cameras.
[0200] In at least one embodiment, the PVA can be used to perform dense optical flow. For example, in at least one embodiment, the PVA can process raw RADAR data (e.g., using a 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.
[0201] In at least one embodiment, the DLA can be used to run any type of network to enhance control and driving safety, including, for example, but not limited to, a neural network that outputs a confidence score for each object detection. In at least one embodiment, the confidence score can be expressed or interpreted as a probability, or as providing a relative "weight" of 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 positive detections rather than false positive detections. In at least one embodiment, the system can set a threshold for the confidence score and only consider detections that exceed the threshold as true positive detections. In embodiments using an automatic emergency braking ("AEB") system, a false positive detection will 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. In at least one embodiment, the neural network may take as its input at least some subset of parameters, such as bounding box dimensions, a ground plane estimate obtained (e.g., from another subsystem), outputs of one or more IMU sensors 966 associated with vehicle 900 heading, distance, 3D position estimates of objects obtained from the neural network and / or other sensors (e.g., one or more LIDAR sensors 964 or one or more RADAR sensors 960), etc.
[0202] In at least one embodiment, one or more SoCs 904 (e.g., a hardware acceleration cluster) may include one or more data stores 916 (e.g., memory). In at least one embodiment, the one or more data stores 916 may be on-chip memory of the one or more SoCs 904 that may store neural networks to be executed on one or more GPUs 908 and / or DLAs. In at least one embodiment, the one or more data stores 916 may have a capacity large enough to store multiple instances of the neural network for redundancy and safety. In at least one embodiment, the one or more data stores 912 may include an L2 or L3 cache.
[0203] In at least one embodiment, one or more SoCs 904 may include any number of processors 910 (e.g., embedded processors). In at least one embodiment, one or more processors 910 may include a boot and power management processor, which may be a dedicated processor and subsystem to handle boot power and management functions and related security implementations. In at least one embodiment, the boot and power management processor may be part of the boot sequence of one or more SoCs 904 and may provide runtime power management services. In at least one embodiment, the boot power and management processor may provide clock and voltage programming, assist in system low power state transitions, one or more SoCs 904 thermal and temperature sensor management, and / or one or more SoCs 904 power state management. In at least one embodiment, each temperature sensor may be implemented as a ring oscillator whose output frequency is proportional to temperature, and one or more SoCs 904 may use the ring oscillator to detect the temperature of one or more CPUs 906, one or more GPUs 908, and / or one or more accelerators 914. In at least one embodiment, if the temperature is determined to exceed a threshold, the boot and power management processor may enter a temperature fault routine and place one or more SoCs 904 into a lower power consumption state and / or place the vehicle 900 into a driver's safe parking pattern (e.g., bringing the vehicle 900 to a safe stop).
[0204] In at least one embodiment, one or more processors 910 may further include a set of embedded processors that can be used as an audio processing engine, which can be an audio subsystem that can provide hardware with 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 that has a digital signal processor with dedicated RAM.
[0205] In at least one embodiment, one or more processors 910 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 processors on the always-on processor engine may include, but are not limited to, a processor core, tightly coupled RAM, supporting peripherals (e.g., timers and interrupt controllers), various I / O controller peripherals, and routing logic.
[0206] In at least one embodiment, one or more processors 910 may further include a safety cluster engine, which may include but is not limited to a dedicated processor subsystem for handling safety management of automotive applications. In at least one embodiment, the safety 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 safety mode, in at least one embodiment, the two or more cores may operate in lockstep mode and may function as a single core with comparison logic to detect any differences between their operations. In at least one embodiment, one or more processors 910 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 910 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 that is part of the camera processing pipeline.
[0207] In at least one embodiment, one or more processors 910 may include a video image synthesizer, which may be a processing block (e.g., implemented on a microprocessor) that implements the video post-processing functions required by a video playback application to generate the final video 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 970, one or more surround cameras 974, and / or one or more in-cabin monitoring camera sensors. In at least one embodiment, the in-cabin monitoring camera sensors are preferably monitored by a neural network running on another instance of SoC 904, the neural network being configured to identify cabin events and respond accordingly. In at least one embodiment, the in-cabin system may perform, but is not limited to, lip reading to activate cellular service and place calls, dictate emails, change the vehicle's destination, activate or change the vehicle's infotainment system and settings, or provide voice-activated web surfing. In at least one embodiment, certain features are available to the driver when the vehicle is operating in autonomous mode and are otherwise disabled.
[0208] In at least one embodiment, the video image compositor may include enhanced temporal noise reduction for simultaneous spatial and temporal noise reduction. For example, in at least one embodiment, where motion occurs in the video, the noise reduction appropriately weights the spatial information, thereby reducing the weight of information provided by adjacent frames. In at least one embodiment, where an image or portion of an image does not include motion, the temporal noise reduction performed by the video image compositor may use information from previous images to reduce noise in the current image.
[0209] In at least one embodiment, the video image compositor can also be configured to perform stereoscopic rectification on the input stereoscopic lens frames. In at least one embodiment, the video image compositor can also be used for user interface composition when using an operating system desktop, without requiring one or more GPUs 908 to continuously render new surfaces. In at least one embodiment, when one or more GPUs 908 are powered and actively performing 3D rendering, the video image compositor can be used to offload one or more GPUs 908 to improve performance and responsiveness.
[0210] In at least one embodiment, one or more of the SoCs 904 may further include a Mobile Industry Processor Interface ("MIPI") camera serial interface for receiving video and input from a camera, a high-speed interface, and / or a video input block that may be used for a camera and associated pixel input functionality. In at least one embodiment, one or more of the SoCs 904 may further include an input / output controller that may be controlled by software and may be used to receive I / O signals that are not assigned to a specific role.
[0211] In at least one embodiment, one or more of the SoCs 904 may further include a wide range of peripheral interfaces to enable communication with peripheral devices, audio encoders / decoders (“codecs”), power management, and / or other devices. In at least one embodiment, one or more of the SoCs 904 may be configured to process data from cameras (e.g., connected via Gigabit multimedia serial links and Ethernet channels), sensors (e.g., one or more LIDAR sensors 964, one or more RADAR sensors 960, etc., which may be connected via Ethernet channels), data from the bus 902 (e.g., vehicle 900 speed, steering wheel position, etc.), data from one or more GNSS sensors 958 (e.g., connected via an Ethernet bus or a CAN bus), and the like. In at least one embodiment, one or more of the SoCs 904 may further include dedicated high-performance mass storage controllers, which may include their own DMA engines and may be used to offload one or more of the CPUs 906 from routine data management tasks.
[0212] In at least one embodiment, one or more SoCs 904 can be an end-to-end platform with a flexible architecture that spans automation levels 3-5, thereby providing a comprehensive functional safety architecture that leverages and effectively uses computer vision and ADAS technologies to achieve diversity and redundancy, providing a platform that can provide a flexible and reliable driving software stack and deep learning tools. In at least one embodiment, one or more SoCs 904 can be faster and more reliable than conventional systems, and even more energy and space efficient. For example, in at least one embodiment, one or more accelerators 914, when combined with one or more CPUs 906, one or more GPUs 908, and one or more data storage devices 916, can provide a fast and efficient platform for level 3-5 autonomous vehicles.
[0213] In at least one embodiment, computer vision algorithms can be executed on a CPU, which can be configured using a high-level programming language (e.g., C) to execute a variety of processing algorithms on a variety of visual data. However, in at least one embodiment, CPUs generally cannot meet the performance requirements of many computer vision applications, such as those related to execution time and power consumption. In at least one embodiment, many CPUs are unable to execute complex object detection algorithms in real time, which are used in in-vehicle ADAS applications and actual Level 3-5 autonomous vehicles.
[0214] The embodiments described herein allow for the execution of multiple neural networks simultaneously and / or sequentially, and for the results to be combined together to achieve Level 3-5 autonomous driving functionality. For example, in at least one embodiment, a CNN executed on a DLA or a discrete GPU (e.g., one or more GPUs 920) may include text and word recognition, thereby allowing the supercomputer to read and understand traffic signs, including signs for which the neural network has not been specifically trained. In at least one embodiment, the DLA may also include a neural network that can recognize, interpret, and provide semantic understanding of the signs and pass this semantic understanding to a path planning module running on the CPU Complex.
[0215] In at least one embodiment, for Level 3, 4, or 5 driving, multiple neural networks can be run simultaneously. For example, in at least one embodiment, a warning sign consisting of "Caution: Flashing lights indicate icy conditions" along with connected lights can be interpreted independently or collectively by multiple neural networks. In at least one embodiment, the warning sign itself can be identified 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 notifies the vehicle's path planning software (preferably executing on a CPU Complex) that icy conditions exist when flashing lights are detected. In at least one embodiment, flashing lights can be identified by operating a third deployed neural network over multiple frames, notifying 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 the DLA and / or on one or more GPUs 908.
[0216] In at least one embodiment, a CNN for facial recognition and vehicle owner identification can use data from the camera sensor to identify the presence of an authorized driver and / or owner of the vehicle 900. In at least one embodiment, an always-on 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 the vehicle. In this way, one or more SoCs 904 provide protection against theft and / or carjacking.
[0217] In at least one embodiment, a CNN for emergency vehicle detection and identification can use data from microphone 996 to detect and identify emergency vehicle sirens. In at least one embodiment, one or more SoCs 904 use a CNN to classify environmental and urban sounds, as well as classify visual data. In at least one embodiment, the CNN running on the DLA is trained to identify the relative approaching speed of the emergency vehicle (e.g., by using the Doppler effect). In at least one embodiment, the CNN can also be trained to identify emergency vehicles for the area in which the vehicle is operating, as identified by one or more GNSS sensors 958. 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 962 to execute emergency vehicle safety routines, slow the vehicle, pull over, stop the vehicle, and / or idle the vehicle until the emergency vehicle passes.
[0218] In at least one embodiment, the vehicle 900 may include one or more CPUs 918 (e.g., one or more discrete CPUs or one or more dCPUs) that may be coupled to one or more SoCs 904 via a high-speed interconnect (e.g., PCIe). In at least one embodiment, for example, the one or more CPUs 918 may include an X86 processor. The one or more CPUs 918 may be used to perform any of a variety of functions, including, for example, arbitrating potentially inconsistent results between ADAS sensors and the one or more SoCs 904, and / or monitoring the status and health of the one or more controllers 936 and / or the infotainment system on chip ("infotainment SoC") 930.
[0219] In at least one embodiment, the vehicle 900 may include one or more GPUs 920 (e.g., one or more discrete GPUs or one or more dGPUs) that may be coupled to the one or more SoCs 904 via a high-speed interconnect (e.g., NVIDIA's NVLINK channel). In at least one embodiment, the one or more GPUs 920 may provide additional artificial intelligence functionality, 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 input (e.g., sensor data) from sensors of the vehicle 900.
[0220] In at least one embodiment, the vehicle 900 may further include a network interface 924, which may include, but is not limited to, one or more wireless antennas 926 (e.g., one or more wireless antennas 926 for different communication protocols, such as a cellular antenna, a Bluetooth antenna, etc.). In at least one embodiment, the network interface 924 may be used to enable wireless connectivity with other vehicles and / or computing devices (e.g., a passenger's client device) via an internet cloud service (e.g., using a server and / or other network devices). In at least one embodiment, to communicate with other vehicles, a direct link may be established between the vehicle 900 and the other vehicle, and / or an indirect link may be established (e.g., via a network and over the internet). In at least one embodiment, a vehicle-to-vehicle communication link may be used to provide the direct link. In at least one embodiment, the vehicle-to-vehicle communication link may provide the vehicle 900 with information about vehicles in its vicinity (e.g., vehicles in front of, to the sides of, and / or behind the vehicle 900). In at least one embodiment, this functionality may be part of the cooperative adaptive cruise control functionality of the vehicle 900.
[0221] In at least one embodiment, the network interface 924 may include a SoC that provides modulation and demodulation functionality and enables one or more controllers 936 to communicate over a wireless network. In at least one embodiment, the network interface 924 may include a radio frequency front end for up-conversion from baseband to radio frequency and down-conversion from radio frequency to baseband. In at least one embodiment, frequency conversion may be performed in any technically feasible manner. For example, frequency conversion may be performed by a well-known process and / or using a superheterodyne process. In at least one embodiment, the radio frequency front end functionality may be provided by a separate chip. In at least one embodiment, the network interface may include wireless functionality for communicating over LTE, WCDMA, UMTS, GSM, CDMA2000, Bluetooth, Bluetooth LE, Wi-Fi, Z-Wave, ZigBee, LoRaWAN, and / or other wireless protocols.
[0222] In at least one embodiment, the vehicle 900 may further include one or more data storage devices 928, which may include, but are not limited to, off-chip (e.g., one or more SoCs 904) storage. In at least one embodiment, the one or more data storage devices 928 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, a hard disk, and / or other components and / or devices that can store at least one bit of data.
[0223] In at least one embodiment, the vehicle 900 may further include one or more GNSS sensors 958 (e.g., GPS and / or assisted GPS sensors) to assist with mapping, perception, occupancy raster generation, and / or path planning functions. In at least one embodiment, any number of GNSS sensors 958 may be used, including, for example, but not limited to, GPS connected to a serial interface (e.g., RS-232) bridge using a USB connector with Ethernet.
[0224] In at least one embodiment, the vehicle 900 may further include one or more RADAR sensors 960. In at least one embodiment, the one or more RADAR sensors 960 may be used by the vehicle 900 for remote vehicle detection, even in darkness and / or in adverse weather conditions. In at least one embodiment, the RADAR functional safety level may be ASIL B. In at least one embodiment, the one or more RADAR sensors 960 may use the CAN bus and / or bus 902 (e.g., to transmit data generated by the one or more RADAR sensors 960) 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 variety of RADAR sensor types may be used. For example, but not limited to, one or more of the RADAR sensors 960 may be suitable for front, rear, and side RADAR use. In at least one embodiment, the one or more RADAR sensors 960 are pulse Doppler RADAR sensors.
[0225] In at least one embodiment, one or more RADAR sensors 960 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, long-range RADAR can be used for adaptive cruise control functionality. 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 range of 250 meters). In at least one embodiment, one or more RADAR sensors 960 can help distinguish between static and moving objects and can be used by the ADAS system 938 for emergency brake assistance and forward collision warning. In at least one embodiment, the one or more sensors 960 included in the long-range RADAR system may include, but are not limited to, a single-base multi-mode RADAR with multiple (e.g., six or more) fixed RADAR antennas and high-speed CAN and FlexRay interfaces. In at least one embodiment, with six antennas, the central four antennas can create a focused beam pattern designed to record the surroundings of the vehicle 900 at higher speeds with minimal interference from traffic in adjacent lanes. In at least one embodiment, the additional two antennas can expand the field of view, allowing for rapid detection of vehicles 900 entering or leaving the lane.
[0226] In at least one embodiment, as an example, the medium-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, the short-range RADAR system may include, but is not limited to, any number of RADAR sensors 960 designed to be mounted on both ends of the rear bumper. When mounted on both ends of the rear bumper, in at least one embodiment, the RADAR sensor system can generate two light beams that continuously monitor the rear direction of the vehicle and nearby blind spots. In at least one embodiment, the short-range RADAR system can be used in the ADAS system 938 for blind spot detection and / or lane change assistance.
[0227] In at least one embodiment, the vehicle 900 may further include one or more ultrasonic sensors 962. In at least one embodiment, one or more ultrasonic sensors 962, which may be positioned at the front, rear, and / or side of the vehicle 900, may be used for parking assistance and / or for creating and updating occupancy barriers. In at least one embodiment, a variety of ultrasonic sensors 962 may be used, and different ultrasonic sensors 962 may be used for different detection ranges (e.g., 2.5 m, 4 m). In at least one embodiment, the ultrasonic sensors 962 may operate at an ASIL B functional safety level.
[0228] In at least one embodiment, the vehicle 900 can include one or more LIDAR sensors 964. In at least one embodiment, the one or more LIDAR sensors 964 can 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 964 can operate at functional safety level ASIL B. In at least one embodiment, the vehicle 900 can include multiple (e.g., two, four, six, etc.) LIDAR sensors 964 that can use Ethernet (e.g., provide data to a Gigabit Ethernet switch).
[0229] In at least one embodiment, one or more LIDAR sensors 964 may be capable of providing a list of objects and their distances for a 360-degree field of view. In at least one embodiment, commercially available one or more LIDAR sensors 964 may, for example, have an advertised range of approximately 100 meters, an accuracy of 2-3 cm, and support a 100 Mbps Ethernet connection. In at least one embodiment, one or more non-obtrusive LIDAR sensors may be used. In such an embodiment, one or more LIDAR sensors 964 may comprise a small device that can be embedded in the front, rear, side, and / or corner locations of the vehicle 900. In at least one embodiment, one or more LIDAR sensors 964 may provide a horizontal field of view of up to 120 degrees and a vertical field of view of 35 degrees, even for low-reflectivity objects, and have a range of 200 meters. In at least one embodiment, the forward-facing one or more LIDAR sensors 964 may be configured for a horizontal field of view between 45 and 135 degrees.
[0230] In at least one embodiment, LIDAR technology (such as 3D flash LIDAR) may also be used. In at least one embodiment, 3D flash LIDAR uses a laser flash as a transmission source to illuminate approximately 200 meters around vehicle 900. 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 the reflected light at each pixel, which in turn corresponds to the range from vehicle 900 to the object. In at least one embodiment, flash LIDAR can allow for the generation of highly accurate and distortion-free images of the surrounding environment with each laser flash. In at least one embodiment, four flash LIDAR sensors can be deployed, one on each side of vehicle 900. 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 5 nanosecond Class I (eye-safe) laser pulses per frame and can capture the reflected laser light as a 3D range point cloud and co-registered intensity data.
[0231] In at least one embodiment, the vehicle 900 may also include one or more IMU sensors 966. In at least one embodiment, the one or more IMU sensors 966 may be located at the center of the rear axle of the vehicle 900. In at least one embodiment, the one or more IMU sensors 966 may include, for example, but not limited to, one or more accelerometers, one or more magnetometers, one or more gyroscopes, a magnetic compass, multiple magnetic compasses, and / or other sensor types. In at least one embodiment, for example, in a six-axis application, the one or more IMU sensors 966 may include, but not limited to, accelerometers and gyroscopes. In at least one embodiment, for example, in a nine-axis application, the one or more IMU sensors 966 may include, but not limited to, accelerometers, gyroscopes, and magnetometers.
[0232] In at least one embodiment, one or more IMU sensors 966 can be implemented as a miniature, high-performance GPS-aided inertial navigation system ("GPS / INS") that combines microelectromechanical system ("MEMS") inertial sensors, a high-sensitivity GPS receiver, and an advanced Kalman filter algorithm to provide estimates of position, velocity, and attitude; in at least one embodiment, one or more IMU sensors 966 can enable the vehicle 900 to estimate heading by directly observing and correlating velocity changes from GPS to one or more IMU sensors 966 without input from a magnetic sensor. In at least one embodiment, one or more IMU sensors 966 and one or more GNSS sensors 958 can be combined in a single integrated unit.
[0233] In at least one embodiment, the vehicle 900 can include one or more microphones 996 positioned within and / or around the vehicle 900. In at least one embodiment, the one or more microphones 996 can be used for emergency vehicle detection and identification, among other things.
[0234] In at least one embodiment, the vehicle 900 may further include any number of camera types, including one or more stereo cameras 968, one or more wide angle cameras 970, one or more infrared cameras 972, one or more surround cameras 974, one or more long range cameras 998, one or more mid range cameras 976, and / or other camera types. In at least one embodiment, the cameras may be used to capture image data around the entire periphery of the vehicle 900. In at least one embodiment, the type of camera used depends on the vehicle 900. In at least one embodiment, any combination of camera types may be used to provide the necessary coverage around the vehicle 900. In at least one embodiment, the number of cameras deployed may vary depending on the embodiment. For example, in at least one embodiment, the vehicle 900 may include six cameras, seven cameras, ten cameras, twelve cameras, or other number of cameras. In at least one embodiment, the cameras may, by way of example but not limitation, support Gigabit Multimedia Serial Link ("GMSL") and / or Gigabit Ethernet communications. In at least one embodiment, the present disclosure previously referred to herein may provide a plurality of cameras. Figure 9A and Figure 9B Each camera can be described in more detail.
[0235] In at least one embodiment, the vehicle 900 can further include one or more vibration sensors 942. In at least one embodiment, the one or more vibration sensors 942 can measure vibrations of a component (e.g., an axle) of the vehicle 900. For example, in at least one embodiment, changes in vibration can indicate changes in the road surface. In at least one embodiment, when two or more vibration sensors 942 are used, the difference between the vibrations can be used to determine friction or slippage in the road surface (e.g., when there is a vibration difference between a powered drive shaft and a freely rotating shaft).
[0236] In at least one embodiment, the vehicle 900 may include an ADAS system 938. In at least one embodiment, the ADAS system 938 may include, but is not limited to, an SoC. In at least one embodiment, the ADAS system 938 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 alert ("BSW") systems, rear cross traffic alert ("RCTW") systems, collision warning ("CW") systems, lane centering ("LC") systems, and / or other systems, features, and / or functions, and combinations thereof.
[0237] In at least one embodiment, the ACC system may utilize one or more RADAR sensors 960, one or more LIDAR sensors 964, 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 another vehicle in close proximity to the vehicle 900 and automatically adjusts the speed of the vehicle 900 to maintain a safe distance from the vehicle ahead. In at least one embodiment, the lateral ACC system performs distance keeping and suggests that the vehicle 900 change lanes when needed. In at least one embodiment, lateral ACC is associated with other ADAS applications, such as LC and CW.
[0238] In at least one embodiment, the CACC system uses information from other vehicles, which may be received from the other vehicles via a wireless link or indirectly via a network connection (e.g., via the Internet) via a network interface 924 and / or one or more wireless antennas 926. In at least one embodiment, a direct link may be provided by a vehicle-to-vehicle ("V2V") communication link, while an indirect link may be provided by an infrastructure-to-vehicle ("I2V") communication link. Typically, V2V communications provide information about the vehicle immediately ahead (e.g., the vehicle immediately ahead of vehicle 900 and in the same lane as it), while I2V communications provide 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 ahead of vehicle 900, the CACC system may be more reliable and have the potential to improve the smoothness of traffic flow and reduce road congestion.
[0239] In at least one embodiment, the FCW system is designed to warn the driver of hazards 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 960, which are coupled to a dedicated processor, DSP, FPGA, and / or ASIC, which is electrically coupled to provide driver feedback, such as a display, speaker, and / or vibration component. In at least one embodiment, the FCW system can provide warnings, such as in the form of audible, visual warnings, vibrations, and / or rapid brake pulses.
[0240] In at least one embodiment, an AEB system detects an impending forward collision with another vehicle or other object and can automatically apply the brakes if the driver does not take corrective action within specified time or distance parameters. In at least one embodiment, the AEB system can utilize one or more forward-facing cameras and / or one or more RADAR sensors 960 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 the collision, and, if the driver does not take corrective action, the AEB system can automatically apply the brakes to attempt to prevent or at least mitigate the effects of the predicted collision. In at least one embodiment, the AEB system can include technologies such as dynamic brake support and / or braking on impending collisions.
[0241] In at least one embodiment, the LDW system provides visual, audible, and / or tactile warnings, such as steering wheel or seat vibrations, to alert the driver when the vehicle 900 crosses a lane marking. In at least one embodiment, the LDW system is inactive when the driver indicates an intentional lane departure, such as by activating a turn signal. In at least one embodiment, the LDW system may utilize a front-facing camera coupled to a dedicated processor, DSP, FPGA, and / or ASIC, which is electrically coupled to provide driver feedback such as a display, speaker, and / or vibration component. In at least one embodiment, the LKA system is a variation of the LDW system. In at least one embodiment, if the vehicle 900 begins to leave the lane, the LKA system provides steering input or braking to correct the vehicle 900.
[0242] In at least one embodiment, the BSW system detects and warns the driver of vehicles in the car's blind spot. In at least one embodiment, the BSW system can provide visual, audible, 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 a 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 960 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 component.
[0243] In at least one embodiment, the RCTW system can provide visual, audible, and / or tactile notifications when an object is detected outside the rear camera range while the vehicle 900 is in reverse. In at least one embodiment, the RCTW system includes an AEB system to ensure application of vehicle brakes to avoid a collision. In at least one embodiment, the RCTW system can use one or more rear-facing RADAR sensors 960 coupled to a dedicated processor, DSP, FPGA, and / or ASIC that is electrically coupled to provide driver feedback such as a display, speaker, and / or vibration component.
[0244] In at least one embodiment, conventional ADAS systems can be prone to generating false positive results, which can be annoying and distracting to the driver, but are generally not catastrophic because conventional ADAS systems alert the driver and allow the driver to decide whether a safe condition truly exists and take appropriate action. In at least one embodiment, in the event of conflicting results, the vehicle 900 itself decides whether to follow the results of the primary computer or the secondary computer (e.g., the first controller 936 or the second controller 936). For example, in at least one embodiment, the ADAS system 938 can be a backup and / or auxiliary computer that provides perception information to a backup computer rationality module. In at least one embodiment, the backup computer rationality monitor can run redundant software on hardware components to detect failures in perception and dynamic driving tasks. In at least one embodiment, the output from the ADAS system 938 can be provided to a supervisory MCU. In at least one embodiment, if the output from the primary computer and the output from the secondary computer conflict, the supervisory MCU determines how to reconcile the conflict to ensure safe operation.
[0245] In at least one embodiment, the primary computer can be configured to provide a confidence score to the supervisory MCU to indicate the primary computer's confidence in the selected result. In at least one embodiment, if the confidence score exceeds a threshold, the supervisory MCU can follow the primary computer's instructions regardless of whether the secondary computer provides conflicting or inconsistent results. In at least one embodiment, if the confidence score does not meet the threshold, and if the primary and secondary computers indicate different results (e.g., a conflict), the supervisory MCU can arbitrate between the computers to determine the appropriate result.
[0246] In at least one embodiment, the supervisory MCU can be configured to run a neural network that is trained and configured to determine conditions under which the secondary computer provides a false alarm based, at least in part, on output from the primary computer and output from the secondary computer. In at least one embodiment, the neural network in the supervisory MCU can learn when the output of the secondary computer can be trusted and when it cannot be trusted. For example, in at least one embodiment, when the secondary computer is a RADAR-based FCW system, the neural network in the supervisory MCU can learn when the FCW system identifies a metal object that is not actually a danger, such as a drain grate or manhole cover, that would trigger an alarm. In at least one embodiment, when the secondary computer is a camera-based LDW system, the neural network in the supervisory MCU can learn to override the LDW when a cyclist or pedestrian is present and lane departure is actually the safest action. In at least one embodiment, the supervisory MCU can include at least one of a DLA or a GPU suitable for running a neural network with associated memory. In at least one embodiment, the supervisory MCU can include and / or be included as a component of one or more SoCs 904.
[0247] In at least one embodiment, the ADAS system 938 may include an auxiliary computer that performs ADAS functions using traditional computer vision rules. In at least one embodiment, the auxiliary computer may use classical computer vision rules (if-then), and the presence of a neural network in the supervisory MCU may improve reliability, safety, and performance. For example, in at least one embodiment, the diverse implementations and intentional non-identity make the entire system more fault-tolerant, especially for failures caused by software (or software-hardware interface) functions. For example, in at least one embodiment, if there is a software vulnerability or error in the software running on the main computer, and the different software code running on the auxiliary computer provides a consistent overall result, the supervisory MCU can be more confident that the overall result is correct and that the vulnerability in the software or hardware on the main computer will not cause a significant error.
[0248] In at least one embodiment, the output of the ADAS system 938 can be input into the primary computer's perception module and / or the primary computer's dynamic driving task module. For example, in at least one embodiment, if the ADAS system 938 indicates a forward collision warning due to an object directly ahead, the perception module can use this information when identifying the object. In at least one embodiment, as described herein, the secondary computer can have its own neural network that has been trained to reduce the risk of false positives.
[0249] In at least one embodiment, the vehicle 900 may further include an infotainment SoC 930 (e.g., an in-vehicle infotainment system (IVI)). Although shown and described as an SoC, in at least one embodiment, the infotainment system SoC 930 may not be an SoC and may include, but is not limited to, two or more discrete components. In at least one embodiment, the infotainment SoC 930 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., TV, movies, streaming, etc.), phone (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 distance covered, brake fuel level, oil level, door open / closed, air filter information, etc.) to the vehicle 900. For example, the infotainment SoC 930 may include a radio, a disk player, a navigation system, a video player, USB and Bluetooth connectivity, a car, an in-vehicle entertainment system, WiFi, steering wheel audio controls, hands-free voice control, a heads-up display ("HUD"), an HMI display 934, a telematics device, a 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 930 may be further configured to provide information (e.g., visual and / or auditory) to a vehicle user, such as information from an ADAS system 938, 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.
[0250] In at least one embodiment, the infotainment SoC 930 can include any number and type of GPU functionality. In at least one embodiment, the infotainment SoC 930 can communicate with other devices, systems, and / or components of the vehicle 900 via bus 902 (e.g., CAN bus, Ethernet, etc.). In at least one embodiment, the infotainment SoC 930 can be coupled to a supervisory MCU so that the GPU of the infotainment system can perform some autonomous driving functions in the event of a failure of the main controller 936 (e.g., the main computer and / or backup computer of the vehicle 900). In at least one embodiment, the infotainment SoC 930 can cause the vehicle 900 to enter a driver-to-safety stop mode, as described herein.
[0251] In at least one embodiment, the vehicle 900 may further include an instrument panel 932 (e.g., a digital instrument panel, an electronic instrument panel, a digital instrument panel, etc.). In at least one embodiment, the instrument panel 932 may include, but is not limited to, a controller and / or a supercomputer (e.g., a discrete controller or a supercomputer). The instrument panel 932 may include, but is not limited to, any number and combination of a set of instruments, such as a speedometer, a fuel level, an oil pressure, a tachometer, an odometer, a turn indicator, a shift position indicator, one or more seat belt warning lights, one or more parking brake warning lights, one or more engine fault lights, supplemental 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 the infotainment SoC 930 and the instrument panel 932. In at least one embodiment, the instrument panel 932 may be included as part of the infotainment SoC 930, and vice versa.
[0252] Figure 1-9C The information stored in the database is shared with multiple components within a fifth generation new radio (5G-NR) radio access network. For example, according to at least one embodiment, the vehicle 900 may be one of the user devices that is part of the RAN 104. In at least one embodiment, the server 978 may be part of the system 100 for executing the call flow diagrams 300, 400 and / or the processes 500, 600 to perform one or more 5G-NR network operations using the database.
[0253] Figure 9D In accordance with at least one embodiment, a cloud-based server and Figure 9A977 for communicating between autonomous vehicles 900. In at least one embodiment, system 977 may include, but is not limited to, one or more servers 978, one or more networks 990, and any number and type of vehicles, including vehicle 900. In at least one embodiment, one or more servers 978 may include, but are not limited to, multiple GPUs 984(A)-984(H) (collectively referred to herein as GPUs 984), PCIe switches 982(A)-982(D) (collectively referred to herein as PCIe switches 982), and / or CPUs 980(A)-980(B) (collectively referred to herein as CPUs 980). GPUs 984, CPUs 980, and PCIe switches 982 may be interconnected with high-speed connections, such as, but not limited to, NVLink interfaces 988 and / or PCIe connections 986 developed by NVIDIA. In at least one embodiment, GPUs 984 are connected via NVLink and / or NVSwitch SoCs, and GPUs 984 and PCIe switches 982 are connected via PCIe interconnects. In at least one embodiment, although eight GPUs 984, two CPUs 980, and four PCIe switches 982 are shown, this is not intended to be limiting. In at least one embodiment, each of the one or more servers 978 may include, but is not limited to, any combination of any number of GPUs 984, CPUs 980, and / or PCIe switches 982. For example, in at least one embodiment, one or more servers 978 may each include eight, sixteen, thirty-two, and / or more GPUs 984.
[0254] In at least one embodiment, one or more servers 978 may receive image data representing an image from a vehicle via one or more networks 990 that depicts unexpected or altered road conditions, such as recently begun road construction. In at least one embodiment, one or more servers 978 may transmit neural network 992, updated neural network 992, and / or map information 994, including, but not limited to, information regarding traffic and road conditions, to the vehicle via one or more networks 990. In at least one embodiment, updates to map information 994 may include, but not limited to, updates to HD map 922, such as information regarding construction sites, potholes, access roads, flooding, and / or other obstacles. In at least one embodiment, neural network 992, updated neural network 992, and / or map information 994 may be generated based on new training and / or experience derived from data received from any number of vehicles in the environment, and / or based at least on training performed at a data center (e.g., using one or more servers 978 and / or other servers).
[0255] In at least one embodiment, one or more servers 978 can be used to train a machine learning model (e.g., a neural network) based at least in part on the training data. In at least one embodiment, the training data can be generated by the vehicle and / or can be generated in simulation (e.g., using a game engine). In at least one embodiment, any amount of the training data is labeled (e.g., where the associated neural network benefits from supervised learning) and / or undergoes other pre-processing. In at least one embodiment, no amount of the training data is labeled and / or pre-processed (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 can be used by the vehicle (e.g., transmitted to the vehicle via one or more networks 990, and / or the machine learning model can be used by one or more servers 978 to remotely monitor the vehicle.
[0256] In at least one embodiment, one or more servers 978 can receive data from the vehicle and apply the data to the latest real-time neural networks for real-time intelligent reasoning. In at least one embodiment, one or more servers 978 can include a deep learning supercomputer and / or a dedicated AI computer powered by one or more GPUs 984, such as the DGX and DGX Station machines developed by NVIDIA. However, in at least one embodiment, one or more servers 978 can include the deep learning infrastructure of a data center using CPU power.
[0257] In at least one embodiment, the deep learning infrastructure of one or more servers 978 may be capable of fast, real-time reasoning and may use this capability to assess and verify the health of the processors, software, and / or related hardware in the vehicle 900. For example, in at least one embodiment, the deep learning infrastructure may receive periodic updates from the vehicle 900, such as an image sequence and / or objects that the vehicle 900 has located in that 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 to those identified by the vehicle 900, and if the results do not match and the deep learning infrastructure concludes that the AI in the vehicle 900 is malfunctioning, the one or more servers 978 may send a signal to the vehicle 900 to instruct the vehicle's 900 fail-safe computer to take control, notify passengers, and complete a safe parking maneuver.
[0258] In at least one embodiment, one or more servers 978 may include one or more GPUs 984 and one or more programmable inference accelerators (e.g., NVIDIA's TensorRT 3). In at least one embodiment, the combination of GPU-powered servers and inference acceleration can enable real-time responses. In at least one embodiment, for example, in situations where performance is less critical, servers powered by CPUs, FPGAs, and other processors can be used for inference.
[0259] Computer system
[0260] Figure 10 1 is a block diagram illustrating an exemplary computer system according to at least one embodiment, which may be a system of interconnected devices and components, a system on a chip (SOC), or some combination thereof, formed into a processor 1000, which may include execution units to execute instructions. In at least one embodiment, according to the present disclosure, such as the embodiments described herein, the computer system 1000 may include, but is not limited to, components such as a processor 1002, whose execution units include logic to execute algorithms for processing data. In at least one embodiment, the computer system 1000 may include a processor such as the Intel Corporation of Santa Clara, California. Processor family, XeonTM, XScaleTM and / or StrongARMTM, Core TM or Nervana TM microprocessor, although other systems (including PCs with other microprocessors, engineering workstations, set-top boxes, etc.) may also be used. In at least one embodiment, computer system 1000 may execute a version of the WINDOWS operating system available from Microsoft Corporation of Redmond, Wash., although other operating systems (e.g., UNIX and Linux), embedded software, and / or graphical user interfaces may also be used.
[0261] Embodiments may 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, 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.
[0262] In at least one embodiment, the computer system 1000 may include, but is not limited to, a processor 1002, which may include, but is not limited to, one or more execution units 1008 to perform machine learning model training and / or inference according to the techniques described herein. In at least one embodiment, the system 10 is a single-processor desktop or server system, but in another embodiment, the system 10 may be a multi-processor system. In at least one embodiment, the processor 1002 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 that implements a combination of instruction sets, or any other processor device, such as a digital signal processor. In at least one embodiment, the processor 1002 may be coupled to a processor bus 1010, which may transmit data signals between the processor 1002 and other components in the computer system 1000.
[0263] In at least one embodiment, processor 1002 may include, but is not limited to, a level 1 ("L1") internal cache memory ("cache") 1004. In at least one embodiment, processor 1002 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 1002. Other embodiments may include a combination of internal and external caches, depending on the specific implementation and requirements. In at least one embodiment, register file 1006 may store different types of data in various registers, including, but not limited to, integer registers, floating point registers, status registers, and an instruction pointer register.
[0264] In at least one embodiment, an execution unit 1008, including but not limited to logic for performing integer and floating point operations, is also located in the processor 1002. In at least one embodiment, the processor 1002 may also include a microcode ("ucode") read-only memory ("ROM") for storing microcode for certain macroinstructions. In at least one embodiment, the execution unit 1008 may include logic for processing a packed instruction set 1009. In at least one embodiment, by including the packed instruction set 1009 in the instruction set of the general-purpose processor 1002, and associated circuitry for executing the instructions, operations used by many multimedia applications may be performed using packed data in the general-purpose processor 1002. In one or more embodiments, many multimedia applications may be accelerated and executed more efficiently by using the full width of the processor's data bus to perform operations on the packed data, which may not require transferring smaller units of data across the processor's data bus to perform one or more operations one data element at a time.
[0265] In at least one embodiment, execution unit 1008 may also be used in a microcontroller, an embedded processor, a graphics device, a DSP, and other types of logic circuits. In at least one embodiment, computer system 1000 may include, but is not limited to, memory 1020. In at least one embodiment, memory 1020 may be implemented as a dynamic random access memory ("DRAM") device, a static random access memory ("SRAM") device, a flash memory device, or another storage device. In at least one embodiment, memory 1020 may store instructions 1019 and / or data 1021 represented by data signals that may be executed by processor 1002.
[0266] In at least one embodiment, a system logic chip can be coupled to the processor bus 1010 and the memory 1020. In at least one embodiment, the system logic chip can include, but is not limited to, a memory controller hub ("MCH") 1016, and the processor 1002 can communicate with the MCH 1016 via the processor bus 1010. In at least one embodiment, the MCH 1016 can provide a high-bandwidth memory path 1018 to the memory 1020 for instruction and data storage, as well as for storage of graphics commands, data, and textures. In at least one embodiment, the MCH 1016 can direct data signals between the processor 1002, the memory 1020, and other components in the computer system 1000, and bridge data signals between the processor bus 1010, the memory 1020, and the system I / O 1022. In at least one embodiment, the system logic chip can provide a graphics port for coupling to a graphics controller. In at least one embodiment, the MCH 1016 may be coupled to the memory 1020 via a high-bandwidth memory path 1018 , and the graphics / video card 1012 may be coupled to the MCH 1016 via an Accelerated Graphics Port (“AGP”) interconnect 1014 .
[0267] In at least one embodiment, the computer system 1000 may use system I / O 1022, which is a proprietary hub interface bus, to couple the MCH 1016 to an I / O controller hub ("ICH") 1030. In at least one embodiment, the ICH 1030 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 the memory 1020, chipset, and processor 1002. Examples may include, but are not limited to, an audio controller 1029, a firmware hub ("Flash BIOS") 1028, a wireless transceiver 1026, a data store 1024, a legacy I / O controller 1023 including a user input and keyboard interface, a serial expansion port 1027 (e.g., a universal serial bus (USB)), and a network controller 1034. In at least one embodiment, the data store 1024 may include a hard drive, a floppy disk drive, a CD-ROM device, a flash memory device, or other mass storage device.
[0268] In at least one embodiment, Figure 10 The system is shown as comprising interconnected hardware devices or "chips", while in other embodiments, Figure 10 A system on a chip (SoC) may be shown. In at least one embodiment, Figure 10The devices shown in can be interconnected with a proprietary interconnect, a standardized interconnect (eg, PCIe), or some combination thereof. In at least one embodiment, one or more components of system 1000 are interconnected using a Compute Express Link (CXL) interconnect.
[0269] Figure 1-10 The information stored in the database is shared with multiple components within a fifth generation new radio (5G-NR) radio access network. For example, in at least one embodiment, the system 1000 can be part of the systems 100, 200, 700 for executing the call flowcharts 300, 400 and / or the processes 500, 600 to perform one or more 5G-NR network operations using the database.
[0270] Figure 11 1 is a block diagram illustrating an electronic device 1100 for utilizing a processor 1110 in accordance with at least one embodiment. In at least one embodiment, the electronic device 1100 may be, for example, but not limited to, a notebook computer, a tower server, a rack server, a blade server, a laptop computer, a desktop computer, a tablet computer, a mobile device, a phone, an embedded computer, or any other suitable electronic device.
[0271] In at least one embodiment, the system 1100 may include, but is not limited to, a processor 1110 communicatively coupled to any suitable number or kind of components, peripherals, modules, or devices. In at least one embodiment, the processor 1110 is coupled using a bus or interface, such as an I2C bus, a system management bus ("SMBus"), a low pin count (LPC) bus, a serial peripheral interface ("SPI"), a high-definition audio ("HDA") bus, a serial advanced technology attachment ("SATA") bus, a universal serial bus ("USB") (versions 1, 2, 3, etc.), or a universal asynchronous receiver / transmitter ("UART") bus. In at least one embodiment, Figure 11 shows a system comprising interconnected hardware devices or "chips", while in other embodiments, Figure 11 An exemplary system on a chip (SoC) may be shown. In at least one embodiment, Figure 11 The devices shown in can be interconnected with proprietary interconnects, standardized interconnects (e.g., PCIe), or some combination thereof. In at least one embodiment, Figure 11 One or more components of the system are interconnected using Compute Express Link (CXL) interconnect lines.
[0272] In at least one embodiment, Figure 11It may include a display 1124, a touch screen 1125, a touchpad 1130, a near field communication unit (“NFC”) 1145, a sensor hub 1140, a thermal sensor 1139, a fast chipset (“EC”) 1135, a trusted platform module (“TPM”) 1138, a BIOS / firmware / flash memory (“BIOS, FW Flash”) 1122, a DSP 1160, a drive “SSD or HDD” 1120 (e.g., a solid state disk (“SSD”) or a hard disk drive (“HDD”)), a wireless local area network unit (“WLAN”) 1150, a Bluetooth unit 1152, a wireless wide area network unit (“WWAN”) 1156, a global positioning system (GPS) 1155, a camera (“USB 3.0 camera”) 1154 (e.g., a USB 3.0 camera), or a low-power double data rate (“LPDDR”) memory unit (“LPDDR3”) 1115 implemented with, for example, the LPDDR3 standard. These components may each be implemented in any suitable manner.
[0273] In at least one embodiment, other components may be communicatively coupled to processor 1110 via the components described above. In at least one embodiment, an accelerometer 1141, an ambient light sensor (“ALS”) 1142, a compass 1143, and a gyroscope 1144 may be communicatively coupled to sensor hub 1140. In at least one embodiment, a thermal sensor 1139, a fan 1137, a keyboard 1136, and a touchpad 1130 may be communicatively coupled to EC 1135. In at least one embodiment, a speaker 1163, an earpiece 1164, and a microphone (“mic”) 1165 may be communicatively coupled to an audio unit (“audio codec and class-D amplifier”) 1164, which in turn may be communicatively coupled to DSP 1160. In at least one embodiment, audio unit 1164 may include, for example, but not limited to, an audio codec / decoder (“codec”) and a class-D amplifier. In at least one embodiment, a SIM card (“SIM”) 1157 may be communicatively coupled to WWAN unit 1156. In at least one embodiment, components such as the WLAN unit 1150 and the Bluetooth unit 1152 and the WWAN unit 1156 may be implemented as a next generation form factor (NGFF).
[0274] Figure 1-11 The information stored in the database is shared with multiple components within a fifth generation new radio (5G-NR) radio access network. For example, in at least one embodiment, the processor 1100 can be part of the system 100, 200, 700 for executing the call flow diagrams 300, 400 and / or the processes 500, 600 to perform one or more 5G-NR network operations using the database.
[0275] Figure 12 A computer system 1200 is shown in accordance with at least one embodiment. In at least one embodiment, the computer system 1200 is configured to implement the various processes and methods described throughout this disclosure.
[0276] In at least one embodiment, computer system 1200 includes, but is not limited to, at least one central processing unit ("CPU") 1202 connected to a communication bus 1210 implemented using any suitable protocol, such as PCI ("Peripheral Component 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, computer system 1200 includes, but is not limited to, main memory 1204 and control logic (e.g., implemented as hardware, software, or a combination thereof), and data may be stored in main memory 1204 in the form of random access memory ("RAM"). In at least one embodiment, a network interface subsystem ("network interface") 1222 provides an interface to other computing devices and networks for receiving data from computer system 1200 and transmitting data to other systems.
[0277] In at least one embodiment, computer system 1200 includes, but is not limited to, input device 1208, parallel processing system 1212, and display device 1206, which can be implemented using conventional cathode ray tubes ("CRTs"), liquid crystal displays ("LCDs"), light emitting diodes ("LEDs"), plasma displays, or other suitable display technologies. In at least one embodiment, user input is received from input device 1208 (such as a keyboard, mouse, touchpad, microphone, etc.). In at least one embodiment, each of the aforementioned modules can be located on a single semiconductor platform to form a processing system.
[0278] Figure 1-12 The information stored in the database is shared with multiple components within a fifth generation new radio (5G-NR) radio access network. For example, in at least one embodiment, the computer system 1200 can be part of the systems 100 and 200 for executing the call flowcharts 300 and 400 and / or the processes 500 and 600 to perform one or more 5G-NR network operations using the database.
[0279] Figure 13A computer system 1300 is shown in accordance with at least one embodiment. In at least one embodiment, computer system 1300 includes, but is not limited to, a computer 1310 and a USB stick 1320. In at least one embodiment, computer 1310 may include, but is not limited to, any number and type of processors (not shown) and memory (not shown). In at least one embodiment, computer 1310 includes, but is not limited to, a server, a cloud instance, a laptop computer, and a desktop computer.
[0280] In at least one embodiment, the USB stick 1320 includes, but is not limited to, a processing unit 1330, a USB interface 1340, and USB interface logic 1350. In at least one embodiment, the processing unit 1330 can be any instruction execution system, apparatus, or device capable of executing instructions. In at least one embodiment, the processing unit 1330 can include, but is not limited to, any number and type of processing cores (not shown). In at least one embodiment, the processing core 1330 includes an application specific integrated circuit ("ASIC") that is optimized to perform any number and type of operations associated with machine learning. For example, in at least one embodiment, the processing core 1330 is a tensor processing unit ("TPC") that is optimized to perform machine learning inference operations. In at least one embodiment, the processing core 1330 is a vision processing unit ("VPU") that is optimized to perform machine vision and machine learning inference operations.
[0281] In at least one embodiment, USB interface 1340 can be any type of USB connector or USB receptacle. For example, in at least one embodiment, USB interface 1340 is a USB 3.0 Type-C receptacle for data and power. In at least one embodiment, USB interface 1340 is a USB 3.0 Type-A connector. In at least one embodiment, USB interface logic 1350 can include any number and type of logic that enables processing unit 1330 to connect to a device (e.g., computer 1310) via USB connector 1340.
[0282] Figure 1-13 The information stored in the database is shared with multiple components within a fifth generation new radio (5G-NR) radio access network. For example, in at least one embodiment, the computer system 1300 can be part of the systems 100 and 200 for executing the call flowcharts 300 and 400 and / or the processes 500 and 600 to perform one or more 5G-NR network operations using the database.
[0283] Figure 14AAn exemplary architecture is shown in which multiple GPUs 1410-1413 are communicatively coupled to multiple multi-core processors 1405-1406 via high-speed links 1440-1443 (e.g., buses / point-to-point interconnects, etc.). In one embodiment, high-speed links 1440-1443 support 4 GB / s, 30 GB / s, 80 GB / s, or higher communication throughput. Various interconnect protocols can be used, including but not limited to PCIe 4.0 or 5.0 and NVLink 2.0.
[0284] Furthermore, in one embodiment, two or more GPUs 1410-1413 are interconnected via high-speed links 1429-1430, which may be implemented using the same or different protocols / links as used for high-speed links 1440-1443. Similarly, two or more multi-core processors 1405-1406 may be connected via high-speed link 1428, which may be a symmetric multiprocessor (SMP) bus running at 20 GB / s, 30 GB / s, 120 GB / s, or higher. Alternatively, the same protocols / links may be used (e.g., via a common interconnect fabric) to accomplish this. Figure 14A All communications between the various system components shown in .
[0285] In one embodiment, each multi-core processor 1405-1406 is communicatively coupled to processor memory 1401-1402 via memory interconnects 1426-1427, respectively, and each GPU
[0286] 1410-1413 are communicatively coupled to GPU memories 1420-1423 via GPU memory interconnects 1450-1453, respectively. Memory interconnects 1426-1427 and 1450-1453 may utilize the same or different memory access technologies. By way of example and not limitation, processor memories 1401-1402 and GPU memories 1420-1423 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 processor memories 1401-1402 may be volatile memories, while other portions may be non-volatile memories (e.g., using a two-level memory (2LM) hierarchy).
[0287] As described herein, although the various processors 1405-1406 and GPUs 1410-1413 may be physically coupled to specific memories 1401-1402, 1420-1423, respectively, a unified memory architecture may be implemented in which the same virtual system address space (also referred to as an "effective address" space) is distributed across the various physical memories. For example, the processor memories 1401-1402 may each include 64GB of system memory address space, and the GPU memories 1420-1423 may each include 32GB of system memory address space (resulting in a total addressable memory size of 256GB in this example).
[0288] Figure 14B 1407 and a graphics acceleration module 1446. The graphics acceleration module 1446 may include one or more GPU chips integrated on a line card that is coupled to the processor 1407 via a high-speed link 1440. Alternatively, the graphics acceleration module 1446 may be integrated on the same package or chip as the processor 1407.
[0289] In at least one embodiment, the illustrated processor 1407 includes a plurality of cores 1460A-1460D, each having a translation lookaside buffer 1461A-1461D and one or more caches 1462A-1462D. In at least one embodiment, the cores 1460A-1460D may include various other components, not shown, for executing instructions and processing data. The caches 1462A-1462D may include level 1 (L1) and level 2 (L2) caches. In addition, one or more shared caches 1456 may be included in the caches 1462A-1462D and shared by each group of cores 1460A-1460D. For example, one embodiment of the processor 1407 includes 24 cores, each 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. In at least one embodiment, the processor 1407 and the graphics acceleration module 1446 are connected to a system memory 1418, which may include Figure 14A Processor memory 1401-1402 in.
[0290] Coherence is maintained for data and instructions stored in the various caches 1462A-1462D, 1456, and system memory 1418 via inter-core communication over the coherence bus 1464. For example, each cache may have cache coherence logic / circuitry associated therewith to communicate over the coherence bus 1464 in response to detecting a read or write to a particular cache line. In one implementation, a cache snooping protocol is implemented over the coherence bus 1464 to snoop cache accesses.
[0291] In one embodiment, proxy circuitry 1425 communicatively couples graphics acceleration module 1446 to coherence bus 1464, thereby allowing graphics acceleration module 1446 to participate in a cache coherence protocol as a peer of cores 1460A-1460D. Interface 1435 provides connectivity to proxy circuitry 1425 via high-speed link 1440 (e.g., PCIe bus, NVLink, etc.), and interface 1437 connects graphics acceleration module 1446 to link 1440.
[0292] In one implementation, the accelerator integrated circuit 1436 provides cache management, memory access, context management, and interrupt management services on behalf of the multiple graphics processing engines 1431, 1432, N of the graphics acceleration module 1446. The graphics processing engines 1431, 1432, N may each comprise a separate graphics processing unit (GPU). Alternatively, the graphics processing engines 1431, 1432, N may selectively comprise different types of graphics processing engines within the GPU, such as a graphics execution unit, a media processing engine (e.g., a video encoder / decoder), a sampler, and a blit engine. In at least one embodiment, the graphics acceleration module 1446 may be a GPU having multiple graphics processing engines 1431-1432, N, or the graphics processing engines 1431-1432, N may be individual GPUs integrated into a common package, line card, or chip.
[0293] In one embodiment, the accelerator integrated circuit 1436 includes a memory management unit (MMU) 1439 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 1414. The MMU 1439 may also include a translation lookaside buffer ("TLB") (not shown) for caching virtual / effective-to-physical / real address translations. In one implementation, cache 1438 may store commands and data for efficient access by the graphics processing engines 1431-1432, N. In one embodiment, data stored in cache 1438 and graphics memory 1433-1434, M is kept consistent with the core caches 1462A-1462D, 1456, and system memory 1414. As previously described, this task may be accomplished via proxy circuitry 1425 acting on behalf of cache 1438 and graphics memory 1433-1434, M (e.g., sending updates related to modifications / accesses of cache lines on processor caches 1462A-1462D, 1456 to cache 1438 and receiving updates from cache 1438).
[0294] A set of registers 1445 stores context data for threads executed by graphics processing engines 1431, 1432, N, and context management circuitry 1448 manages thread contexts. For example, context management circuitry 1448 can perform save and restore operations to save and restore the context of each thread during a context switch (e.g., where a first thread is saved and a second thread is stored so that the second thread can be executed by the graphics processing engine). For example, context management circuitry 1448 can store current register values to a designated area in memory (e.g., identified by a context pointer) upon a context switch. The register values can then be restored upon returning to the context. In one embodiment, interrupt management circuitry 1447 receives and processes interrupts received from system devices.
[0295] In one implementation, the MMU 1439 converts virtual / effective addresses from the graphics processing engine 1431 into real / physical addresses in the system memory 1414. One embodiment of the accelerator integrated circuit 1436 supports multiple (e.g., 4, 8, 16) graphics accelerator modules 1446 and / or other accelerator devices. The graphics accelerator module 1446 can be dedicated to a single application executing on the processor 1407, or can be shared among multiple applications. In one embodiment, a virtualized graphics execution environment is presented in which the resources of the graphics processing engines 1431, 1432, N are shared with multiple applications or virtual machines (VMs). In at least one embodiment, the resources can be subdivided into "slices" that are allocated to different VMs and / or applications based on processing requirements and priorities associated with the VMs and / or applications.
[0296] In at least one embodiment, the accelerator integrated circuit 1436 acts as a bridge to the system for the graphics acceleration module 1446 and provides address translation and system memory caching services. Additionally, in at least one embodiment, the accelerator integrated circuit 1436 can provide virtualization facilities for the host processor to manage virtualization, interrupts, and memory management for the graphics processing engines 1431-1432.
[0297] Because the hardware resources of the graphics processing engines 1431-1432, N are explicitly mapped into the real address space seen by the host processor 1407, any host processor can directly address these resources using effective address values. In one embodiment, one function of the accelerator integrated circuit 1436 is to physically separate the graphics processing engines 1431-1432, N so that they appear to the system as independent units.
[0298] In at least one embodiment, one or more graphics memories 1433-1434, M are respectively coupled to each graphics processing engine 1431-1432, N. The graphics memories 1433-1434, M store instructions and data, which are processed by each graphics processing engine 1431-1432, N. The graphics memories 1433-1434, M may be volatile memory, such as DRAM (including stacked DRAM), GDDR memory (e.g., GDDR5, GDDR6), or HBM, and / or may be non-volatile memory, such as 3D XPoint or Nano-Ram.
[0299] In one embodiment, to reduce data traffic on link 1440, biasing techniques can be used to ensure that the data stored in graphics memories 1433-1434, M is the data most frequently used by graphics processing engines 1431-1432, N, and preferably is not used (at least not frequently) by cores 1460A-1460D. Similarly, in at least one embodiment, the biasing mechanism attempts to keep data needed by the cores (and preferably not graphics processing engines 1431-1432, N) in the cores' caches 1462A-1462D, 1456 and system memory 1414.
[0300] Figure 14C Another exemplary embodiment is shown in which an accelerator integrated circuit 1436 is integrated into the processor 1407. In this embodiment, the graphics processing engines 1431-1432, N communicate directly with the accelerator integrated circuit 1436 via interfaces 1437 and 1435 (which may also utilize any form of bus or interface protocol) through a high-speed link 1440. The accelerator integrated circuit 1436 can perform operations related to Figure 14B The operations described above are identical to those described above. However, due to its close proximity to the coherence bus 1464 and caches 1462A-1462D, 1456, higher throughput is possible. 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 can include a programming model controlled by the accelerator integrated circuit 1436 and a programming model controlled by the graphics acceleration module 1446.
[0301] In at least one embodiment, graphics processing engines 1431-1432, N are dedicated to a single application or process under a single operating system. In at least one embodiment, a single application can funnel other application requests to graphics processing engines 1431-1432, N, thereby providing virtualization within a VM / partition.
[0302] In at least one embodiment, graphics processing engines 1431-1432, N can be shared by multiple VM / application partitions. In at least one embodiment, the sharing model can use a hypervisor to virtualize graphics processing engines 1431-1432, N to allow each operating system to access them. In at least one embodiment, for a single-partition system without a hypervisor, the operating system owns graphics processing engines 1431-1432, N. In at least one embodiment, the operating system can virtualize graphics processing engines 1431-1432, N to provide access to each process or application.
[0303] In at least one embodiment, the graphics acceleration module 1446 or each graphics processing engine 1431-1432, N uses a process handle to select a process element. In at least one embodiment, the process element is stored in the system memory 1414 and can be addressed using the effective address to real address translation techniques described herein. In at least one embodiment, the process handle can be an implementation-specific value that is provided to the host process when registering its context with the graphics processing engine 1431-1432, N (i.e., calling 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 can be the offset of the process element in the process element linked list.
[0304] Figure 14D An exemplary accelerator integrated slice 1490 is shown. As used herein, a "slice" comprises a designated portion of the processing resources of the accelerator integrated circuit 1436. The application effective address space 1482 in the system memory 1418 stores a process element 1483. In one embodiment, the process element 1483 is stored in response to a GPU call 1481 from an application 1480 executing on the processor 1407. The process element 1483 includes the process state of the corresponding application 1480. The work descriptor (WD) 1484 included in the process element 1483 can be a single job requested by the application, or can include a pointer to a job queue. In at least one embodiment, the WD 1484 is a pointer to a job request queue in the address space 1482 of the application.
[0305] The graphics acceleration module 1446 and / or the individual graphics processing engines 1431-1432, N can be shared by all processes or a subset of processes in the system. In at least one embodiment, an infrastructure for setting process state and sending WD 1484 to the graphics acceleration module 1446 to start a job in a virtualized environment can be included.
[0306] In at least one embodiment, the dedicated process programming model is implementation-specific. In at least one embodiment, in this model, a single process owns a graphics acceleration module 1446 or an individual graphics processing engine 1431. Since the hypervisor initializes the accelerator integrated circuit 1436 for the owned partition when the graphics acceleration module 1446 is owned by a single process, the operating system initializes the accelerator integrated circuit 1436 for the owned process when the graphics acceleration module 1446 is assigned.
[0307] In operation, the WD fetch unit 1491 in the accelerator integrated slice 1490 fetches the next WD 1484, which includes an indication of work to be completed by one or more graphics processing engines of the graphics acceleration module 1446. Data from the WD 1484 can be stored in registers 1445 and used by the MMU 1439, interrupt management circuitry 1447, and / or context management circuitry 1448, as shown. For example, one embodiment of the MMU 1439 includes segment / page roaming circuitry for accessing segment / page tables 1486 within the OS virtual address space 1485. The interrupt management circuitry 1447 can process interrupt events 1492 received from the graphics acceleration module 1446. When executing graphics operations, the effective addresses 1493 generated by the graphics processing engines 1431-1432, N are converted into real addresses by the MMU 1439.
[0308] In one embodiment, the same set of registers 1445 is replicated for each graphics processing engine 1431-1432, N, and / or graphics acceleration module 1446, and the registers 1445 can be initialized by the hypervisor or operating system. Each of these replicated registers can be included in the accelerator integration slice 1490. Example registers that can be initialized by the hypervisor are shown in Table 1.
[0309]
[0310] Example registers that may be initialized by the operating system are shown in Table 2.
[0311]
[0312] In one embodiment, each WD 1484 is specific to a particular graphics acceleration module 1446 and / or graphics processing engine 1431-1432, N. It includes all the information necessary for the graphics processing engine 1431-1432, N to complete the 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.
[0313] Figure 14E 1496 , which virtualizes the graphics acceleration module engine for the operating system 1495 .
[0314] In at least one embodiment, the shared programming model allows all processes or a subset of processes from all partitions or a subset of partitions in the system to use the graphics acceleration module 1446. In at least one embodiment, there are two programming models where the graphics acceleration module 1446 is shared by multiple processes and partitions: time-sliced sharing and graphics-directed sharing.
[0315] In this model, the hypervisor 1496 owns the graphics acceleration module 1446 and makes its functionality available to all operating systems 1495. For the graphics acceleration module 1446 to support virtualization through the hypervisor 1496, the graphics acceleration module 1446 may adhere to the following: (1) the application's job requests must be autonomous (i.e., no state needs to be maintained between jobs), or the graphics acceleration module 1446 must provide a context save and restore mechanism, (2) the graphics acceleration module 1446 guarantees that the application's job requests are completed within a specified amount of time, including any transition errors, or the graphics acceleration module 1446 provides the ability to preempt job processing, and (3) fairness between graphics acceleration module 1446 processes must be ensured when operating in a directed shared programming model.
[0316] In at least one embodiment, an application 1480 is required to make an operating system 1495 system call using a graphics acceleration module 1446 type, a work descriptor (WD), an authority mask register (AMR) value, and a context save / restore region pointer (CSRP). In at least one embodiment, the graphics acceleration module 1446 type describes the target acceleration function for the system call. In at least one embodiment, the graphics acceleration module 1446 type can be a system-specific value. In at least one embodiment, the WD is formatted specifically for the graphics acceleration module 1446 and can take the form of a graphics acceleration module 1446 command, an effective address pointer to a user-defined structure, an effective address pointer to a command queue, or any other data structure describing work to be performed by the graphics acceleration module 1446. 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 an application setting the AMR. In at least one embodiment, if the implementation of the accelerator integrated circuit 1436 and graphics acceleration module 1446 does not support the User Authority Mask Override Register (UAMOR), the operating system can apply the current UAMOR value to the AMR value before passing the AMR in the hypervisor call. In at least one embodiment, the hypervisor 1496 can optionally apply the current privilege mask overwrite register (AMOR) value before placing the AMR into the process element 1483. In at least one embodiment, the CSRP is one of the registers 1445 that contains the effective address of an area in the application's address space 1482 for the graphics acceleration module 1446 to save and restore context state. This pointer is optional if state does not need to be saved between jobs or when a job is preempted. In at least one embodiment, the context save / restore area can be fixed system memory.
[0317] Upon receiving the system call, the operating system 1495 may verify that the application 1480 has been registered and granted permission to use the graphics acceleration module 1446. The operating system 1495 then uses
[0318] The information shown in Table 3 is used to call the management program 1496.
[0319]
[0320] Upon receiving the hypervisor call, the hypervisor 1496 verifies that the operating system 1495 has registered and been granted permission to use the graphics acceleration module 1446. The hypervisor 1496 then places the process element 1483 into a linked list of process elements of the corresponding graphics acceleration module 1446 type. The process element may include the information shown in Table 4.
[0321]
[0322]
[0323] In at least one embodiment, the hypervisor initializes the plurality of accelerator integrated slice 1490 registers 1445 .
[0324] like Figure 14F As shown, in at least one embodiment, a unified memory is used that is addressable via a common virtual memory address space for accessing physical processor memories 1401-1402 and GPU memories 1420-1423. In this implementation, operations executed on GPUs 1410-1413 utilize the same virtual / effective memory address space to access processor memories 1401-1402, and vice versa, thereby simplifying programmability. In one embodiment, a first portion of the virtual / effective address space is allocated to processor memory 1401, a second portion is allocated to second processor memory 1402, a third portion is allocated to GPU memory 1420, 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 1401-1402 and GPU memories 1420-1423, thereby allowing any processor or GPU to access that memory using a virtual address mapped to any physical memory.
[0325] In one embodiment, bias / coherency management circuitry 1494A-1494E within one or more MMUs 1439A-1439E ensures cache coherency between the caches of one or more host processors (e.g., 1405) and GPUs 1410-1413 and implements biasing techniques that indicate the physical memory where certain types of data should be stored. In at least one embodiment, while Figure 14F Multiple instances of bias / coherence management circuits 1494A- 1494E are shown in , but bias / coherence circuits may be implemented within an MMU of one or more host processors 1405 and / or within an accelerator integrated circuit 1436 .
[0326] One embodiment allows GPU attached memory 1420-1423 to be mapped as part of system memory and accessed using shared virtual memory (SVM) technology, but without suffering the performance drawbacks associated with full system cache coherence. In at least one embodiment, the ability to access GPU attached memory 1420-1423 as system memory without heavy cache coherence overhead provides a favorable operating environment for GPU offloading. This arrangement allows software of the host processor 1405 to set operands and access computation results without the overhead of traditional I / O DMA data copies. Such traditional copies include driver calls, interrupts, and memory mapped I / O (MMIO) accesses, which are all less efficient than simple memory accesses. In at least one embodiment, the ability to access GPU attached memory 1420-1423 without cache coherence overhead may be critical to the execution time of the offloaded computation. For example, in situations with large amounts of streaming write memory traffic, cache coherence overhead can significantly reduce the effective write bandwidth seen by the GPUs 1410-1413. In at least one embodiment, efficiency of operand setup, efficiency of result access, and efficiency of GPU computation may play a role in determining the effectiveness of GPU offloading.
[0327] 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 can be a page-granular structure (e.g., controlled at the granularity of a memory page) that includes 1 or 2 bits per GPU-attached memory page. In at least one embodiment, the bias table can be implemented in the stolen memory range of one or more GPU-attached memories 1420-1423, with or without a bias cache in GPUs 1410-1413 (e.g., to cache frequently / recently used entries in the bias table). Alternatively, the entire bias table can be maintained within the GPU.
[0328] In at least one embodiment, before actually accessing the GPU memory, the bias table entry associated with each access to the GPU attached memory 1420-1423 is accessed, resulting in the following operations. First, local requests from GPUs 1410-1413 whose pages are found in the GPU bias are forwarded directly to the corresponding GPU memory 1420-1423. Local requests from the GPU whose pages are found in the host bias are forwarded to processor 1405 (e.g., via a high-speed link as described above). In one embodiment, a request from processor 1405 to find the requested page in the host processor bias completes a request similar to a normal memory read. Alternatively, a request to a GPU biased page can be forwarded to GPUs 1410-1413. In at least one embodiment, if the GPU is not currently using the page, the GPU can subsequently migrate the page to the host processor bias. In at least one embodiment, the bias state of a page can be changed by a software-based mechanism, a hardware-assisted software-based mechanism, or in limited cases by a purely hardware-based mechanism.
[0329] One mechanism for changing the bias state employs an API call (e.g., OpenCL), which in turn calls the GPU's device driver, which in turn sends a message (or queues a command descriptor) to the GPU, directing the GPU to change the bias state and, in some migrations, to perform a cache flush operation in the host. In at least one embodiment, the cache flush operation is used for migrations from host processor 1405 bias to GPU bias, but not for the reverse migration.
[0330] In one embodiment, cache coherence is maintained by temporarily rendering GPU-biased pages that cannot be cached by host processor 1405. To access these pages, processor 1405 may request access from GPU 1410, which may or may not immediately grant access. Therefore, to reduce communication between processor 1405 and GPU 1410, it is beneficial to ensure that GPU-biased pages are pages required by the GPU and not by host processor 1405, and vice versa.
[0331] Figure 15 An exemplary integrated circuit and associated graphics processor according to various embodiments described herein are shown, which can be manufactured using one or more IP cores. In addition to the illustrations, other logic and circuits may be included in at least one embodiment, including additional graphics processors / cores, peripheral interface controllers, or general-purpose processor cores.
[0332] Figure 1515 is a block diagram illustrating an exemplary system on a chip integrated circuit 1500 that can be manufactured using one or more IP cores according to at least one embodiment. In at least one embodiment, the integrated circuit 1500 includes one or more application processors 1505 (e.g., CPUs), at least one graphics processor 1510, and may additionally include an image processor 1515 and / or a video processor 1520, any of which may be modular IP cores. In at least one embodiment, the integrated circuit 1500 includes peripheral or bus logic that includes a USB controller 1525, a UART controller 1530, an SPI / SDIO controller 1535, and an I 2 S / I 2 IC controller 1540. In at least one embodiment, integrated circuit 1500 may include a display device 1545 coupled to one or more of a High Definition Multimedia Interface (HDMI) controller 1550 and a Mobile Industry Processor Interface (MIPI) display interface 1555. In at least one embodiment, storage may be provided by a flash memory subsystem 1560, including flash memory and a flash memory controller. In at least one embodiment, a memory interface may be provided via a memory controller 1565 for accessing SDRAM or SRAM memory devices. In at least one embodiment, some integrated circuits also include an embedded security engine 1570.
[0333] Figure 1-15 The information stored in the database will be shared with multiple components within a fifth generation new radio (5G-NR) radio access network. For example, in at least one embodiment, Figure 14A The different components or SoC integrated circuit 1500 described in -F can be part of the system 100, 200 for executing the call flow charts 300, 400 and / or the process 500, 600 to perform one or more 5G-NR network operations using the database.
[0334] Figures 16A-16B An exemplary integrated circuit and associated graphics processor according to various embodiments described herein are shown, which can be manufactured using one or more IP cores. In addition to the illustrations, other logic and circuits may be included in at least one embodiment, including additional graphics processors / cores, peripheral interface controllers, or general-purpose processor cores.
[0335] Figures 16A-16B is a block diagram illustrating an exemplary graphics processor for use within a SoC according to embodiments described herein. Figure 16A An exemplary graphics processor 1610 of a system-on-chip integrated circuit that can be fabricated using one or more IP cores in accordance with at least one embodiment is shown. Figure 16BAn additional exemplary graphics processor 1640 of a system-on-chip integrated circuit that can be fabricated using one or more IP cores according to at least one embodiment is shown. In at least one embodiment, Figure 16A The graphics processor 1610 is a low power graphics processor core. In at least one embodiment, Figure 16B The graphics processor 1640 is a higher performance graphics processor core. In at least one embodiment, each of the graphics processors 1610, 1640 can be Figure 15 A variant of the graphics processor 1510.
[0336] In at least one embodiment, the graphics processor 1610 includes a vertex processor 1605 and one or more fragment processors 1615A-1615N (e.g., 1615A, 1615B, 1615C, 1615D through 1615N-1 and 1615N). In at least one embodiment, the graphics processor 1610 can execute different shader programs via separate logic, such that the vertex processor 1605 is optimized to perform operations for the vertex shader program, while the one or more fragment processors 1615A-1615N perform fragment (e.g., pixel) shading operations for the fragment or pixel or shader program. In at least one embodiment, the vertex processor 1605 performs the vertex processing stage of the 3D graphics pipeline and generates primitives and vertex data. In at least one embodiment, the one or more fragment processors 1615A-1615N use the primitives and vertex data generated by the vertex processor 1605 to generate a frame buffer for display on a display device. In at least one embodiment, one or more fragment processors 1615A-1615N are optimized to execute fragment shader programs as provided in the OpenGL API, which can be used to perform similar operations as pixel shader programs provided in the Direct 3D API.
[0337] In at least one embodiment, graphics processor 1610 additionally includes one or more memory management units (MMUs) 1620A-1620B, one or more caches 1625A-1625B, and one or more circuit interconnects 1630A-1630B. In at least one embodiment, one or more MMUs 1620A-1620B provide a mapping of virtual to physical addresses for graphics processor 1610, including mapping of virtual to physical addresses for vertex processor 1605 and / or fragment processors 1615A-1615N, which may reference vertex or image / texture data stored in memory in addition to reference to vertex or image / texture data stored in one or more caches 1625A-1625B. In at least one embodiment, one or more MMUs 1620A-1620B may synchronize with other MMUs within the system, including with other MMUs. Figure 15 One or more MMUs associated with one or more application processors 1505, graphics processor 1515, and / or video processor 1520 enable each processor 1505-1520 to participate in a shared or unified virtual memory system. In at least one embodiment, one or more circuit interconnects 1630A-1630B enable graphics processor 1610 to connect to other IP cores within the SoC via an internal bus of the SoC or via a direct connection.
[0338] In at least one embodiment, graphics processor 1640 includes Figure 16A One or more MMUs 1620A-1620B, caches 1625A-1625B, and circuit interconnects 1630A-1630B of the graphics processor 1610. In at least one embodiment, the graphics processor 1640 includes one or more shader cores 1655A-1655N (e.g., 1655A, 1655B, 1655C, 1655D, 1655E, 1655F through 1655N-1 and 1655N) that provide a unified shader core architecture in which a single core or type or 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 can vary. In at least one embodiment, the graphics processor 1640 includes an inter-core task manager 1645 that acts as a thread dispatcher to dispatch execution threads to one or more shader cores 1655A-1655N and a tiling unit 1658 to accelerate tile-based rendering operations in which rendering operations of a scene are subdivided in image space, for example, to exploit local spatial coherence within a scene or to optimize use of internal caches.
[0339] Figure 1-16. The information stored in the database may be shared with multiple components within a fifth generation new radio (5G-NR) radio access network. For example, in at least one embodiment, the graphics processor 1610 may be part of the system 100, 200 for executing the call flow diagrams 300, 400 and / or the processes 500, 600 to perform one or more 5G-NR network operations using the database.
[0340] Figures 17A-17B Additional exemplary graphics processor logic according to embodiments described herein is shown. In at least one embodiment, Figure 17A Shows that can be included in Figure 15 Graphics core 1700 within graphics processor 1510 of FIG. 1 and, in at least one embodiment, may be such as Figure 16B Unified shader cores 1655A-1655N are shown. Figure 17B A highly parallel, general-purpose graphics processing unit 1730 suitable for deployment on a multi-chip module in at least one embodiment is shown.
[0341] In at least one embodiment, graphics core 1700 includes a shared instruction cache 1702, texture units 1718, and cache / shared memory 1720, which are common to execution resources within graphics core 1700. In at least one embodiment, graphics core 1700 may include multiple slices 1701A-1701N, or partitions of each core, and the graphics processor may include multiple instances of graphics core 1700. Slices 1701A-1701N may include support logic including local instruction caches 1704A-1704N, thread schedulers 1706A-1706N, thread dispatchers 1708A-1708N, and a set of registers 1710A-1710N. In at least one embodiment, slices 1701A-1701N may include a set of additional function units (AFUs 1712A-1712N), floating point units (FPUs 1714A-1714N), integer arithmetic logic units (ALUs 1716A-1716N), address calculation units (ACUs 1713A-1713N), double-precision floating point units (DPFPUs 1715A-1715N), and matrix processing units (MPUs 1717A-1717N).
[0342] In at least one embodiment, the FPUs 1714A-1714N can perform single-precision (32-bit) and half-precision (16-bit) floating-point operations, while the DPFPUs 1715A-1715N perform double-precision (64-bit) floating-point operations. In at least one embodiment, the ALUs 1716A-1716N 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 MPUs 1717A-1717N 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 MPUs 1717A-1717N can perform various matrix operations to accelerate machine learning application frameworks, including enabling support for accelerated general matrix-to-matrix multiplication (GEMM). In at least one embodiment, the AFUs 1712A-1712N can perform additional logical operations not supported by the floating-point or integer units, including trigonometric operations (e.g., sine, cosine, etc.).
[0343] Figure 1-17A The information stored in the database is shared with multiple components within a fifth generation new radio (5G-NR) radio access network. For example, in at least one embodiment, the graphics processor 1700 can be part of the system 100, 200 for executing the call flow charts 300, 400 and / or the processes 500, 600 to perform one or more 5G-NR network operations using the database.
[0344] Figure 17B A general purpose processing unit (GPGPU) 1730 is shown in at least one embodiment, which can be configured to enable highly parallel computing operations to be performed by a group of graphics processing units. In at least one embodiment, GPGPU 1730 can be directly linked to other instances of GPGPU 1730 to create a multi-GPU cluster to increase the training speed for deep neural networks. In at least one embodiment, GPGPU 1730 includes a host interface 1732 to enable connection to a host processor. In at least one embodiment, host interface 1732 is a PCI Express interface. In at least one embodiment, host interface 1732 can be a vendor-specific communication interface or communication structure. In at least one embodiment, GPGPU 1730 receives commands from the host processor and uses a global scheduler 1734 to assign execution threads associated with those commands to a group of compute clusters 1736A-1736H. In at least one embodiment, compute clusters 1736A-1736H share cache memory 1738. In at least one embodiment, cache memory 1738 may be used as a higher level cache for cache memory within compute clusters 1736A-1736H.
[0345] In at least one embodiment, GPGPU 1730 includes memory 1744A-1744B coupled to compute clusters 1736A-1736H via a set of memory controllers 1742A-1742B. In at least one embodiment, memory 1744A-1744B 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.
[0346] In at least one embodiment, computing clusters 1736A-1736H each include a set of graphics cores, e.g. Figure 17A The graphics core 1700 may include multiple types of integer and floating-point logic units that can perform computational operations at various precision ranges, including precision suitable for machine learning computations. For example, in at least one embodiment, at least a subset of the floating-point units in each of the compute clusters 1736A-1736H may be configured to perform 16-bit or 32-bit floating-point operations, while a different subset of the floating-point units may be configured to perform 64-bit floating-point operations.
[0347] In at least one embodiment, multiple instances of GPGPU 1730 can be configured to function as a compute cluster. In at least one embodiment, the communications used by compute clusters 1736A-1736H for synchronization and data exchange vary between embodiments. In at least one embodiment, multiple instances of GPGPU 1730 communicate via host interface 1732. In at least one embodiment, GPGPU 1730 includes an I / O hub 1739 that couples GPGPU 1730 to a GPU link 1740, enabling direct connections to other instances of GPGPU 1730. In at least one embodiment, GPU link 1740 is coupled to a dedicated GPU-to-GPU bridge that enables communication and synchronization between multiple instances of GPGPU 1730. In at least one embodiment, GPU link 1740 is coupled to a high-speed interconnect to send and receive data to other GPGPUs or parallel processors. In at least one embodiment, multiple instances of GPGPU 1730 reside in separate data processing systems and communicate via a network device accessible through host interface 1732. In at least one embodiment, GPU link 1740 may be configured to enable connection to a host processor in addition to or as an alternative to host interface 1732 .
[0348] In at least one embodiment, GPGPU 1730 can be configured to train neural networks. In at least one embodiment, GPGPU 1730 can be used within an inference platform. In at least one embodiment, where GPGPU 1730 is used for inference, the GPGPU can include fewer compute clusters 1736A-1736H than when the GPGPU is used to train a neural network. In at least one embodiment, the memory technology associated with memory 1744A-1744B can differ between the inference and training configurations, with higher-bandwidth memory technology being dedicated to the training configuration. In at least one embodiment, the inference configuration of GPGPU 1730 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 inference operations of a deployed neural network.
[0349] Figure 1-17B The information stored in the database is shared with multiple components within a fifth generation new radio (5G-NR) radio access network. For example, in at least one embodiment, the GPGPU 1730 can be part of the system 100, 200 for executing the call flow diagrams 300, 400 and / or the processes 500, 600 to perform one or more 5G-NR network operations using the database.
[0350] Figure 18 A block diagram of a computer system 1800 is shown, according to at least one embodiment. In at least one embodiment, computer system 1800 includes a processing subsystem 1801 having one or more processors 1802 and a system memory 1804, which communicates via an interconnect path that may include a memory hub 1805. In at least one embodiment, memory hub 1805 may be a separate component within a chipset assembly or may be integrated within one or more processors 1802. In at least one embodiment, memory hub 1805 is coupled to an I / O subsystem 1811 via a communication link 1806. In at least one embodiment, I / O subsystem 1811 includes an I / O hub 1807, which enables computer system 1800 to receive input from one or more input devices 1808. In at least one embodiment, I / O hub 1807 may enable a display controller, which may be included in one or more processors 1802, to provide output to one or more display devices 1810A. In at least one embodiment, the one or more display devices 1810A coupled to the I / O hub 1807 may include local, internal, or embedded display devices.
[0351] In at least one embodiment, the processing subsystem 1801 includes one or more parallel processors 1812 coupled to the memory hub 1805 via a bus or other communication link 1813. In at least one embodiment, the communication link 1813 can be any of a number of standard-based communication link technologies or protocols, such as, but not limited to, PCI Express, or can be a vendor-specific communication interface or communication structure. In at least one embodiment, the one or more parallel processors 1812 form a computationally focused parallel or vector processing system that can include a large number of processing cores and / or processing clusters, such as a multi-integrated core (MIC) processor. In at least one embodiment, the one or more parallel processors 1812 form a graphics processing subsystem that can output pixels to one of one or more display devices 1810A coupled via the I / O hub 1807. In at least one embodiment, the one or more parallel processors 1812 can also include a display controller and display interface (not shown) to enable direct connection to the one or more display devices 1810B.
[0352] In at least one embodiment, a system storage unit 1814 can be connected to the I / O hub 1807 to provide a storage mechanism for the computer system 1800. In at least one embodiment, an I / O switch 1816 can be used to provide an interface mechanism to enable connections between the I / O hub 1807 and other components, such as a network adapter 1818 and / or a wireless network adapter 1819 that can be integrated into the platform, as well as various other devices that can be added via one or more add-on devices 1820. In at least one embodiment, the network adapter 1818 can be an Ethernet adapter or another wired network adapter. In at least one embodiment, the wireless network adapter 1819 can include one or more of Wi-Fi, Bluetooth, near field communication (NFC), or other network devices including one or more radio devices.
[0353] In at least one embodiment, computer system 1800 may include other components not explicitly shown, including USB or other port connections, optical storage drives, video capture devices, etc., which may also be connected to I / O hub 1807. In at least one embodiment, interconnection may be achieved 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 18 Communication paths for various components in a chip, such as NV-Link high-speed interconnect or interconnect protocol.
[0354] In at least one embodiment, one or more parallel processors 1812 include circuits optimized for graphics and video processing, including, for example, video output circuitry, and constitute a graphics processing unit (GPU). In at least one embodiment, one or more parallel processors 1812 include circuits optimized for general-purpose processing. In at least one embodiment, the components of computer system 1800 can 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 1812, memory hub 1805, processor 1802, and I / O hub 1807 can be integrated into a system-on-chip (SoC) integrated circuit. In at least one embodiment, the components of computer system 1800 can 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 computer system 1800 can be integrated into a multi-chip module (MCM), which can be interconnected with other multi-chip modules to form a modular computer system.
[0355] Figure 1-18 The information stored in the database is shared with multiple components within a fifth generation new radio (5G-NR) radio access network. For example, in at least one embodiment, the computing system 1800 can be part of the systems 100 and 200 to execute the call flow diagrams 300 and 400 and / or the processes 500 and 600 to perform one or more 5G-NR network operations using the database.
[0356] processor
[0357] Figure 19A 1900 is shown in accordance with at least one embodiment. In at least one embodiment, the various components of the parallel processor 1900 may be implemented using one or more integrated circuit devices, such as a programmable processor, an application specific integrated circuit (ASIC), or a field programmable gate array (FPGA). In at least one embodiment, the parallel processor 1900 is shown in accordance with an exemplary embodiment. Figure 18 A variation of the one or more parallel processors 1812 shown.
[0358] In at least one embodiment, parallel processor 1900 includes parallel processing unit 1902. In at least one embodiment, parallel processing unit 1902 includes an I / O unit 1904 that enables communication with other devices, including other instances of parallel processing unit 1902. In at least one embodiment, I / O unit 1904 can be directly connected to other devices. In at least one embodiment, I / O unit 1904 connects to other devices using a hub or switch interface (e.g., memory hub 1905). In at least one embodiment, the connection between memory hub 1905 and I / O unit 1904 forms a communication link. In at least one embodiment, I / O unit 1904 is connected to a host interface 1906 and a memory crossbar switch 1916, where host interface 1906 receives commands for performing processing operations and memory crossbar switch 1916 receives commands for performing memory operations.
[0359] In at least one embodiment, when host interface 1906 receives command buffers via I / O unit 1904, host interface 1906 can direct work operations to execute those commands to front end 1908. In at least one embodiment, front end 1908 is coupled to scheduler 1910, which is configured to distribute commands or other work items to processing cluster array 1912. In at least one embodiment, scheduler 1910 ensures that processing cluster array 1912 is properly configured and in a valid state before distributing tasks to processing cluster array 1912. In at least one embodiment, scheduler 1910 is implemented by firmware logic executing on a microcontroller. In at least one embodiment, the microcontroller-implemented scheduler 1910 can be configured to perform complex scheduling and work distribution operations at both coarse and fine granularity, thereby enabling fast preemption and context switching of threads executing on processing array 1912. In at least one embodiment, host software can authenticate workloads for scheduling on processing array 1912 through one of multiple graphics processing doorbells. In at least one embodiment, the workload may then be automatically distributed across the processing array 1912 by scheduler 1910 logic within a microcontroller that includes scheduler 1910 .
[0360] In at least one embodiment, processing cluster array 1912 may include up to "N" processing clusters (e.g., cluster 1914A, cluster 1914B, through cluster 1914N). In at least one embodiment, each cluster 1914A-1914N of processing cluster array 1912 may execute a large number of concurrent threads. In at least one embodiment, scheduler 1910 may allocate work to clusters 1914A-1914N of processing cluster array 1912 using various scheduling and / or work distribution algorithms, which may vary depending on the workload generated by each program or computation type. In at least one embodiment, scheduling may be handled dynamically by scheduler 1910 or may be assisted in part by compiler logic during the compilation of program logic configured to be executed by processing cluster array 1912. In at least one embodiment, different clusters 1914A-1914N of processing cluster array 1912 may be assigned to process different types of programs or to perform different types of computations.
[0361] In at least one embodiment, processing cluster array 1912 can be configured to perform various types of parallel processing operations. In at least one embodiment, processing cluster array 1912 can be configured to perform general-purpose parallel computing operations. For example, in at least one embodiment, processing cluster array 1912 can include logic to perform processing tasks including filtering video and / or audio data, performing modeling operations including physics operations, and performing data transformations.
[0362] In at least one embodiment, processing cluster array 1912 is configured to perform parallel graphics processing operations. In at least one embodiment, processing cluster array 1912 may include additional logic to support the execution of such graphics processing operations, including but not limited to texture sampling logic to perform texture operations, as well as tessellation logic and other vertex processing logic. In at least one embodiment, processing cluster array 1912 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, parallel processing units 1902 may transfer data from system memory via I / O units 1904 for processing. In at least one embodiment, during processing, the transferred data may be stored in on-chip memory (e.g., parallel processor memory 1922) during processing and then written back to system memory.
[0363] In at least one embodiment, when parallel processing unit 1902 is used to perform graphics processing, scheduler 1910 can be configured to divide the processing workload into tasks of approximately equal size to better distribute graphics processing operations to multiple clusters 1914A-1914N of processing cluster array 1912. In at least one embodiment, portions of processing cluster array 1912 can be configured to perform different types of processing. For example, in at least one embodiment, a first portion can be configured to perform vertex shading and topology generation, a second portion can be configured to perform tessellation and geometry shading, and a third portion can 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 clusters 1914A-1914N can be stored in a buffer to allow the intermediate data to be transferred between clusters 1914A-1914N for further processing.
[0364] In at least one embodiment, processing cluster array 1912 can receive processing tasks to be executed via scheduler 1910, which receives commands defining the processing tasks from front end 1908. In at least one embodiment, a processing task can include an index of data to be processed, such as surface (patch) data, primitive data, vertex data, and / or pixel data, as well as state parameters and commands defining how to process the data (e.g., what program to execute). In at least one embodiment, scheduler 1910 can be configured to obtain an index corresponding to a task, or can receive the index from front end 1908. In at least one embodiment, front end 1908 can be configured to ensure that processing cluster array 1912 is configured in a valid state before starting a workload specified by an incoming command buffer (e.g., a batch buffer, a push buffer, etc.).
[0365] In at least one embodiment, each of one or more instances of parallel processing unit 1902 can be coupled to parallel processor memory 1922. In at least one embodiment, parallel processor memory 1922 can be accessed via memory crossbar 1916, which can receive memory requests from processing cluster array 1912 and I / O unit 1904. In at least one embodiment, memory crossbar 1916 can access parallel processor memory 1922 via memory interface 1918. In at least one embodiment, memory interface 1918 can include a plurality of partition units (e.g., partition unit 1920A, partition unit 1920B, through partition unit 1920N), which can each be coupled to a portion of parallel processor memory 1922 (e.g., a memory unit). In at least one embodiment, the plurality of partition units 1920A-1920N are configured to be equal to the number of memory cells, such that the first partition unit 1920A has a corresponding first memory cell 1924A, the second partition unit 1920B has a corresponding memory cell 1924B, and the Nth partition unit 1920N has a corresponding Nth memory cell 1924N. In at least one embodiment, the number of partition units 1920A-1920N may not be equal to the number of memory devices.
[0366] In at least one embodiment, memory units 1924A-1924N 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 units 1924A-1924N may also include 3D stacked memory, including but not limited to high bandwidth memory (HBM). In at least one embodiment, render targets such as frame buffers or texture maps may be stored across memory units 1924A-1924N, allowing partition units 1920A-1920N to write portions of each render target in parallel to efficiently use the available bandwidth of parallel processor memory 1922. In at least one embodiment, local instances of parallel processor memory 1922 may be eliminated in favor of a unified memory design that utilizes system memory in combination with local cache memory.
[0367] In at least one embodiment, any of the clusters 1914A-1914N in the processing cluster array 1912 can process data to be written to any memory unit 1924A-1924N within the parallel processor memory 1922. In at least one embodiment, the memory crossbar 1916 can be configured to transmit the output of each cluster 1914A-1914N to any partition unit 1920A-1920N or another cluster 1914A-1914N, which can perform other processing operations on the output. In at least one embodiment, each cluster 1914A-1914N can communicate with a memory interface 1918 via the memory crossbar 1916 to read from or write to various external storage devices. In at least one embodiment, memory crossbar 1916 has connections to memory interface 1918 for communicating with I / O unit 1904, and connections to local instances of parallel processor memory 1922, thereby enabling processing units within different processing clusters 1914A-1914N to communicate with system memory or other memory that is not local to parallel processing unit 1902. In at least one embodiment, memory crossbar 1916 may use virtual channels to separate traffic flows between clusters 1914A-1914N and partition units 1920A-1920N.
[0368] In at least one embodiment, multiple instances of parallel processing unit 1902 can be provided on a single plug-in card, or multiple plug-in cards can be interconnected. In at least one embodiment, different instances of parallel processing unit 1902 can be configured to interoperate with each other, even if the different instances have different numbers of processing cores, different amounts of local parallel processor memory, and / or other configuration differences. For example, in at least one embodiment, some instances of parallel processing unit 1902 can include higher precision floating point units relative to other instances. In at least one embodiment, a system incorporating one or more instances of parallel processing unit 1902 or parallel processor 1900 can be implemented in a variety of configurations and form factors, including but not limited to desktop, laptop, or handheld personal computers, servers, workstations, game consoles, and / or embedded systems.
[0369] Figure 19B is a block diagram of a partition unit 1920 according to at least one embodiment. In at least one embodiment, the partition unit 1920 is Figure 19A1920N). In at least one embodiment, partition unit 1920 includes an L2 cache 1921, a frame buffer interface 1925, and a ROP 1926 (raster operations unit). L2 cache 1921 is a read / write cache that is configured to execute load and store operations received from memory crossbar 1916 and ROP 1926. In at least one embodiment, L2 cache 1921 outputs read misses and urgent writeback requests to frame buffer interface 1925 for processing. In at least one embodiment, updates may also be sent to the frame buffer via frame buffer interface 1925 for processing. In at least one embodiment, frame buffer interface 1925 interacts with one of the memory units in the parallel processor memory, such as memory units 1924A-1924N of FIG. 19 (e.g., within parallel processor memory 1922).
[0370] In at least one embodiment, ROP 1926 is a processing unit that performs raster operations such as stenciling, z-testing, blending, etc. In at least one embodiment, ROP 1926 then outputs processed graphics data that is stored in graphics memory. In at least one embodiment, ROP 1926 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 can be lossless compression logic that utilizes one or more of a variety of compression algorithms. In at least one embodiment, the type of compression performed by ROP 1926 can 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.
[0371] In at least one embodiment, ROP 1926 is included within each processing cluster (e.g., clusters 1914A-1914N of FIG. 19 ), rather than within partition unit 1920. In at least one embodiment, read and write requests for pixel data are transmitted through memory crossbar 1916 rather than pixel fragment data. In at least one embodiment, processed graphics data may be displayed on a display device such as a Figure 18 1802 for further processing, or Figure 19A One of the processing entities within parallel processor 1900 is routed for further processing.
[0372] Figure 19C19. It is a block diagram of a processing cluster 1914 within a parallel processing unit according to at least one embodiment. In at least one embodiment, the processing cluster is an instance of one of the processing clusters 1914A-1914N of Figure 19. In at least one embodiment, the processing cluster 1914 can be configured to execute many threads in parallel, where the term "thread" refers to an instance of a specific program executed on a specific set of input data. In at least one embodiment, single instruction multiple data (SIMD) instruction issuance technology is used to support the parallel execution of a large number of threads without providing multiple independent instruction units. In at least one embodiment, single instruction multiple thread (SIMT) technology is used to support the parallel execution of a large number of generally synchronized threads, which uses a common instruction unit that is configured to issue instructions to a group of processing engines within each processing cluster.
[0373] In at least one embodiment, the operation of processing cluster 1914 can be controlled by a pipeline manager 1932 that distributes processing tasks to SIMT parallel processors. In at least one embodiment, pipeline manager 1932 receives instructions from scheduler 1910 of FIG. 19 and manages the execution of these instructions by graphics multiprocessor 1934 and / or texture unit 1936. In at least one embodiment, graphics multiprocessor 1934 is an exemplary instance of a SIMT parallel processor. However, in at least one embodiment, processing cluster 1914 may include various types of SIMT parallel processors with different architectures. In at least one embodiment, processing cluster 1914 may include one or more instances of graphics multiprocessor 1934. In at least one embodiment, graphics multiprocessor 1934 may process data, and data crossbar 1940 may be used to distribute the processed data to one of multiple possible destinations (including other shader units). In at least one embodiment, pipeline manager 1932 may facilitate the distribution of processed data by specifying the destination of the processed data to be distributed via data crossbar 1940.
[0374] In at least one embodiment, each graphics multiprocessor 1934 within a processing cluster 1914 may include the same set of function execution logic (e.g., arithmetic logic unit, load-store unit, etc.). In at least one embodiment, the function execution logic may be configured in a pipelined manner, where new instructions may be issued before previous instructions have completed. In at least one embodiment, the function execution logic supports a variety of operations, including integer and floating-point arithmetic, comparison operations, Boolean operations, shifts, and calculations of various algebraic functions. In at least one embodiment, the same functional unit hardware may be utilized to perform different operations, and any combination of functional units may be present.
[0375] In at least one embodiment, instructions transmitted to processing cluster 1914 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, a thread group executes a common program on different input data. In at least one embodiment, each thread within a thread group can be assigned to a different processing engine within graphics multiprocessor 1934. In at least one embodiment, a thread group can include fewer threads than the number of processing engines within graphics multiprocessor 1934. In at least one embodiment, when a thread group includes fewer threads than the number of processing engines, one or more processing engines may be idle during the processing of a loop within the thread group. In at least one embodiment, a thread group can also include more threads than the number of processing engines within graphics multiprocessor 1934. In at least one embodiment, when a thread group includes more threads than the number of processing engines within graphics multiprocessor 1934, processing can be performed within consecutive clock cycles. In at least one embodiment, multiple thread groups can be executed simultaneously on graphics multiprocessor 1934.
[0376] In at least one embodiment, graphics multiprocessor 1934 includes internal cache memory to perform load and store operations. In at least one embodiment, graphics multiprocessor 1934 can forgo the internal cache and use cache memory within processing cluster 1914 (e.g., L1 cache 1948). In at least one embodiment, each graphics multiprocessor 1934 also has access to L2 cache within a partition unit (e.g., partition units 1920A-1920N in FIG. 19 ), which is shared across all processing clusters 1914 and can be used to transfer data between threads. In at least one embodiment, graphics multiprocessor 1934 also has access to off-chip global memory, which can include one or more of local parallel processor memory and / or system memory. In at least one embodiment, any memory external to parallel processing unit 1902 can be used as global memory. In at least one embodiment, processing cluster 1914 includes multiple instances of graphics multiprocessor 1934, which can share common instructions and data, which can be stored in L1 cache 1948.
[0377] In at least one embodiment, each processing cluster 1914 may include a memory management unit ("MMU") 1945 configured to map virtual addresses to physical addresses. In at least one embodiment, one or more instances of the MMU 1945 may reside within the memory interface 1918 of FIG. 19 . In at least one embodiment, the MMU 1945 includes a set of page table entries (PTEs) that map virtual addresses to physical addresses of tiles and, optionally, to cache line indices. In at least one embodiment, the MMU 1945 may include a translation lookaside buffer (TLB) or cache that may reside within the graphics multiprocessor 1934 or an L1 cache or within the processing cluster 1914. In at least one embodiment, the physical addresses are processed to assign surface data access locality for efficient request interleaving between partition units. In at least one embodiment, the cache line index may be used to determine whether a request for a cache line is a hit or a miss.
[0378] In at least one embodiment, processing clusters 1914 can be configured such that each graphics multiprocessor 1934 is coupled to a texture unit 1936 to perform texture mapping operations, including determining texture sample locations, reading texture data, and filtering texture data. In at least one embodiment, texture data is read from an internal texture L1 cache (not shown) or from an L1 cache within the graphics multiprocessor 1934, and texture data is retrieved from an L2 cache, local parallel processor memory, or system memory as needed. In at least one embodiment, each graphics multiprocessor 1934 outputs processed tasks to a data crossbar 1940 to provide the processed tasks to another processing cluster 1914 for further processing or to store the processed tasks in an L2 cache, local parallel processor memory, or system memory via a memory crossbar 1916. In at least one embodiment, a preROP 1942 (pre-raster operations unit) is configured to receive data from graphics multiprocessor 1934 and direct the data to a ROP unit, which may be located with a partition unit as described herein (e.g., partition units 1920A-1920N of FIG. 19 ). In at least one embodiment, the PreROP 1942 unit may perform optimizations for color blending, organize pixel color data, and perform address translation.
[0379] Figure 1-19C The information stored in the database is shared with multiple components within a fifth generation new radio (5G-NR) radio access network. For example, in at least one embodiment, the parallel processor 1900 can be part of the system 100, 200 for executing the call flow charts 300, 400 and / or the processes 500, 600 to perform one or more 5G-NR network operations using the database.
[0380] Figure 19D A graphics multiprocessor 1934 is shown in accordance with at least one embodiment. In at least one embodiment, the graphics multiprocessor 1934 is coupled to a pipeline manager 1932 of a processing cluster 1914. In at least one embodiment, the graphics multiprocessor 1934 has an execution pipeline that includes, but is not limited to, an instruction cache 1952, an instruction unit 1954, an address mapping unit 1956, a register file 1958, one or more general purpose graphics processing unit (GPGPU) cores 1962, and one or more load / store units 1966. The GPGPU cores 1962 and the load / store units 1966 are coupled to a cache memory 1972 and a shared memory 1970 via a memory and cache interconnect 1968.
[0381] In at least one embodiment, the instruction cache 1952 receives a stream of instructions to be executed from the pipeline manager 1932. In at least one embodiment, the instructions are cached in the instruction cache 1952 and dispatched for execution by the instruction unit 1954. In at least one embodiment, the instruction unit 1954 can dispatch instructions as thread groups (e.g., warps), assigning each thread of the thread group to a different execution unit within the GPGPU core 1962. In at least one embodiment, instructions can access any local, shared, or global address space by specifying an address within the unified address space. In at least one embodiment, the address mapping unit 1956 can be used to convert addresses in the unified address space into different memory addresses that can be accessed by the load / store unit 1966.
[0382] In at least one embodiment, register file 1958 provides a set of registers for the functional units of graphics multiprocessor 1934. In at least one embodiment, register file 1958 provides temporary storage for operands for the data paths of the functional units (e.g., GPGPU core 1962, load / store unit 1966) connected to graphics multiprocessor 1934. In at least one embodiment, register file 1958 is divided between each functional unit such that a dedicated portion of register file 1958 is allocated to each functional unit. In at least one embodiment, register file 1958 is divided between the different warps being executed by graphics multiprocessor 1934.
[0383] In at least one embodiment, the GPGPU cores 1962 may each include a floating-point unit (FPU) and / or an integer arithmetic logic unit (ALU) for executing instructions for the graphics multiprocessor 1934. In at least one embodiment, the GPGPU cores 1962 may be architecturally similar or may differ in architecture. In at least one embodiment, a first portion of the GPGPU core 1962 includes a single-precision FPU and 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 arithmetic or enable variable-precision floating-point arithmetic. In at least one embodiment, the graphics multiprocessor 1934 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.
[0384] In at least one embodiment, the GPGPU core 1962 includes SIMD logic capable of executing a single instruction on multiple sets of data. In one embodiment, the GPGPU core 1962 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 by a single SIMD instruction. For example, in at least one embodiment, eight SIMT threads performing the same or similar operations can be executed in parallel by a single SIMD8 logic unit.
[0385] In at least one embodiment, memory and cache interconnect 1968 is an interconnect network that connects each functional unit of graphics multiprocessor 1934 to register file 1958 and shared memory 1970. In at least one embodiment, memory and cache interconnect 1968 is a crossbar interconnect that allows load / store unit 1966 to perform load and store operations between shared memory 1970 and register file 1958. In at least one embodiment, register file 1958 can operate at the same frequency as GPGPU core 1962, resulting in very low latency for data transfers between GPGPU core 1962 and register file 1958. In at least one embodiment, shared memory 1970 can be used to enable communication between threads executing on functional units within graphics multiprocessor 1934. In at least one embodiment, cache memory 1972 can be used, for example, as a data cache to cache texture data communicated between functional units and texture unit 1936. In at least one embodiment, shared memory 1970 can also be used as a program-managed cache. In at least one embodiment, in addition to automatically cached data stored in cache memory 1972, threads executing on GPGPU core 1962 may programmatically store data in shared memory.
[0386] 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 can be communicatively coupled to the host processor / core via a bus or other interconnect (e.g., a high-speed interconnect such as PCIe or NVLink). In at least one embodiment, the GPU can be integrated on the same package or chip as the core and communicatively coupled to the core via an internal processor bus / interconnect (i.e., internal to the package or chip). In at least one embodiment, regardless of the manner in which the GPU is connected, the processor core can assign work to the GPU in the form of a sequence of commands / instructions included in a work descriptor. In at least one embodiment, the GPU then uses dedicated circuitry / logic to efficiently process these commands / instructions.
[0387] Figure 1-19D The information stored in the database is shared with multiple components within a fifth generation new radio (5G-NR) radio access network. For example, in at least one embodiment, the graphics multiprocessor 1934 can be part of the systems 100, 200 to execute the call flow diagrams 300, 400 and / or the processes 500, 600 to perform one or more 5G-NR network operations using the database.
[0388] Figure 20 A multi-GPU computing system 2000 is shown in accordance with at least one embodiment. In at least one embodiment, multi-GPU computing system 2000 may include a processor 2002 coupled to a plurality of general-purpose graphics processing units (GPGPUs) 2006A-D via a host interface switch 2004. In at least one embodiment, host interface switch 2004 is a PCI Express switch device that couples processor 2002 to a PCI Express bus, over which processor 2002 can communicate with GPGPUs 2006A-D. GPGPUs 2006A-D may be interconnected via a set of high-speed P2P GPU-to-GPU links 2016. In at least one embodiment, GPU-to-GPU links 2016 connect to each of GPGPUs 2006A-D via a dedicated GPU link. In at least one embodiment, P2P GPU links 2016 enable direct communication between each GPGPU 2006A-D without requiring communication through host interface bus 2004 to which processor 2002 is connected. In at least one embodiment, with GPU-to-GPU traffic directed to P2P GPU link 2016, host interface bus 2004 remains available for system memory access or for communicating with other instances of multi-GPU computing system 2000, for example, via one or more network devices. While in at least one embodiment, GPGPUs 2006A-D are connected to processor 2002 via host interface switch 2004, in at least one embodiment, processor 2002 includes direct support for P2P GPU link 2016 and can connect directly to GPGPUs 2006A-D.
[0389] Figure 1-20 For sharing information stored in a database with multiple components within a fifth generation new radio (5G-NR) radio access network. For example, in at least one embodiment, the computing system 2000 can be part of the systems 100 and 200 to execute the call flowcharts 300 and 400 and / or the processes 500 and 600 to perform one or more 5G-NR network operations using the database.
[0390] Figure 21FIG2 is a block diagram of a graphics processor 2100 according to at least one embodiment. In at least one embodiment, graphics processor 2100 includes a ring interconnect 2102, a pipeline front end 2104, a media engine 2137, and graphics cores 2180A-2180N. In at least one embodiment, ring interconnect 2102 couples graphics processor 2100 to other processing units, including other graphics processors or one or more general-purpose processor cores. In at least one embodiment, graphics processor 2100 is one of many processors integrated within a multi-core processing system.
[0391] In at least one embodiment, the graphics processor 2100 receives batches of commands via a ring interconnect 2102. In at least one embodiment, the incoming commands are interpreted by a command streamer 2103 in a pipeline front end 2104. In at least one embodiment, the graphics processor 2100 includes scalable execution logic for performing 3D geometry processing and media processing via graphics cores 2180A-2180N. In at least one embodiment, for 3D geometry processing commands, the command streamer 2103 provides the commands to a geometry pipeline 2136. In at least one embodiment, for at least some media processing commands, the command streamer 2103 provides the commands to a video front end 2134, which is coupled to a media engine 2137. In at least one embodiment, the media engine 2137 includes a video quality engine (VQE) 2130 for video and image post-processing, and a multi-format encoding / decoding (MFX) 2133 engine for providing hardware-accelerated media data encoding and decoding. In at least one embodiment, the geometry pipeline 2136 and the media engine 2137 each generate execution threads for thread execution resources provided by at least one graphics core 2180A.
[0392] In at least one embodiment, the graphics processor 2100 includes scalable thread execution resources featuring modular cores 2180A-2180N (sometimes referred to as core slices), each of which has multiple sub-cores 2150A-2150N, 2160A-2160N (sometimes referred to as core sub-slices). In at least one embodiment, the graphics processor 2100 can have any number of graphics cores 2180A-2180N. In at least one embodiment, the graphics processor 2100 includes a graphics core 2180A having at least a first sub-core 2150A and a second sub-core 2160A. In at least one embodiment, the graphics processor 2100 is a low-power processor having a single sub-core (e.g., 2150A). In at least one embodiment, the graphics processor 2100 includes multiple graphics cores 2180A-2180N, each of which includes a set of first sub-cores 2150A-2150N and a set of second sub-cores 2160A-2160N. In at least one embodiment, each of the first sub-cores 2150A-2150N includes at least a first set of execution units 2152A-2152N and media / texture samplers 2154A-2154N. In at least one embodiment, each of the second sub-cores 2160A-2160N includes at least a second set of execution units 2162A-2162N and samplers 2164A-2164N. In at least one embodiment, each of the sub-cores 2150A-2150N, 2160A-2160N shares a set of shared resources 2170A-2170N. In at least one embodiment, the shared resources include shared cache memory and pixel operation logic.
[0393] Figure 1-21 The information stored in the database is shared with multiple components within a fifth generation new radio (5G-NR) radio access network. For example, in at least one embodiment, the graphics processor 2100 can be part of the system 100, 200 for executing the call flow charts 300, 400 and / or the processes 500, 600 to perform one or more 5G-NR network operations using the database.
[0394] Figure 22 is a block diagram illustrating a microarchitecture for a processor 2200 that may include logic circuitry for executing instructions, according to at least one embodiment. In at least one embodiment, the processor 2200 may execute instructions including x86 instructions, ARM instructions, specialized instructions for an application-specific integrated circuit (ASIC), and the like. In at least one embodiment, the processor 2210 may include registers for storing packed data, such as the 64-bit wide MMX registers in microprocessors enabled with MMX technology from Intel Corporation of Santa Clara, California.TM Registers. In at least one embodiment, MMX registers available in integer and floating point form can operate with packed data elements that accompany single instruction multiple data (“SIMD”) and streaming SIMD extensions (“SSE”) instructions. In at least one embodiment, 128-bit wide XMM registers associated with SSE2, SSE3, SSE4, AVX, or higher (generally referred to as “SSEx”) technology can hold such packed data operands. In at least one embodiment, processor 2210 can execute instructions to accelerate machine learning or deep learning algorithms, training, or inference.
[0395] In at least one embodiment, the processor 2200 includes an in-order front end ("front end") 2201 to fetch instructions to be executed and prepare the instructions for later use in the processor pipeline. In at least one embodiment, the front end 2201 may include several units. In at least one embodiment, an instruction prefetcher 2226 retrieves instructions from memory and provides the instructions to an instruction decoder 2228, which in turn decodes or interprets the instructions. For example, in at least one embodiment, the instruction decoder 2228 decodes the received instructions into one or more operations called "microinstructions" or "micro-operations" (also referred to as "micro-ops" or "micro-instructions") that the machine can execute. In at least one embodiment, the instruction decoder 2228 parses the instructions into an opcode and corresponding data and control fields, which can be used by the microarchitecture to perform the operations according to at least one embodiment. In at least one embodiment, the trace cache 2230 can assemble the decoded microinstructions into a program-ordered sequence or trace in the microinstruction queue 2234 for execution. In at least one embodiment, when trace cache 2230 encounters a complex instruction, microcode ROM 2232 provides the microinstructions necessary to complete the operation.
[0396] In at least one embodiment, some instructions may be converted into a single micro-op, while other instructions may require several micro-ops to complete the entire operation. In at least one embodiment, if more than four micro-ops are required to complete an instruction, the instruction decoder 2228 may access the microcode ROM 2232 to execute the instruction. In at least one embodiment, an instruction may be decoded into a smaller number of micro-ops for processing at the instruction decoder 2228. In at least one embodiment, if multiple micro-ops are required to complete the operation, the instruction may be stored in the microcode ROM 2232. In at least one embodiment, the trace cache 2230 references the entry point programmable logic array ("PLA") to determine the correct micro-op pointer for reading the microcode sequence from the microcode ROM 2232 to complete one or more instructions according to at least one embodiment. In at least one embodiment, after the microcode ROM 2232 completes the micro-op sequencing for the instruction, the front end 2201 of the machine may resume fetching micro-ops from the trace cache 2230.
[0397] In at least one embodiment, an out-of-order execution engine ("OOO engine") 2203 can prepare instructions for execution. In at least one embodiment, the OOO logic has multiple buffers to smooth and reorder the instruction flow to optimize performance as instructions flow down the pipeline and are scheduled for execution. In at least one embodiment, the OOO engine 2203 includes, but is not limited to, an allocator / register renamer 2240, a memory microinstruction queue 2242, an integer / floating-point microinstruction queue 2244, a memory scheduler 2246, a fast scheduler 2202, a slow / general purpose floating-point scheduler ("slow / general purpose FP scheduler") 2204, and a simple floating-point scheduler ("simple FP scheduler") 2206. In at least one embodiment, the fast scheduler 2202, the slow / general purpose floating-point scheduler 2204, and the simple floating-point scheduler 2206 are also collectively referred to as "microinstruction schedulers 2202, 2204, 2206." In at least one embodiment, the allocator / register renamer 2240 allocates the machine buffers and resources required for each microinstruction to execute in sequence. In at least one embodiment, the allocator / register renamer 2240 renames logical registers into entries in the register file. In at least one embodiment, the allocator / register renamer 2240 also allocates an entry for each microinstruction in one of two microinstruction queues: a memory microinstruction queue 2242 for memory operations and an integer / floating-point microinstruction queue 2244 for non-memory operations, preceding the memory scheduler 2246 and the microinstruction schedulers 2202, 2204, and 2206. In at least one embodiment, the microinstruction schedulers 2202, 2204, and 2206 determine when a microinstruction is ready to execute based on the readiness of its dependent input register operand sources and the availability of the execution resource microinstructions that need to be completed. The fast scheduler 2202 of at least one embodiment can schedule every half of the main clock cycle, while the slow / general floating-point scheduler 2204 and the simple floating-point scheduler 2206 can schedule once per main processor clock cycle. In at least one embodiment, microinstruction schedulers 2202, 2204, 2206 arbitrate on dispatch ports to schedule microinstructions for execution.
[0398] In at least one embodiment, execution block 2211 includes, but is not limited to, integer register file / branch network 2208, floating point register file / branch network ("FP register file / branch network") 2210, address generation units ("AGUs") 2212 and 2214, fast arithmetic logic units ("fast ALUs") 2216 and 2218, slow arithmetic logic unit ("slow ALU") 2220, floating point ALU ("FP") 2222, and floating point move unit ("FP move") 2224. In at least one embodiment, integer register file / branch network 2208 and floating point register file / bypass network 2210 are also referred to herein as "register files 2208, 2210." In at least one embodiment, AGUs 2212 and 2214, fast ALUs 2216 and 2218, slow ALU 2220, floating-point ALU 2222, and floating-point move unit 2224 are also referred to herein as "execution units 2212, 2214, 2216, 2218, 2220, 2222, and 2224." In at least one embodiment, execution block b11 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).
[0399] In at least one embodiment, register files 2208 and 2210 may be arranged between microinstruction schedulers 2202, 2204, and 2206 and execution units 2212, 2214, 2216, 2218, 2220, 2222, and 2224. In at least one embodiment, integer register file / branch network 2208 performs integer operations. In at least one embodiment, floating-point register file / branch network 2210 performs floating-point operations. In at least one embodiment, each of register files 2208 and 2210 may include, but is not limited to, a branch network that can bypass or forward recently completed results that have not yet been written to the register file to new dependent objects. In at least one embodiment, register files 2208 and 2210 can communicate data with each other. In at least one embodiment, integer register file / branch network 2208 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, floating point register file / branch network 2210 may include, but is not limited to, 128-bit wide entries, as floating point instructions typically have operands that are 64 to 128 bits wide.
[0400] In at least one embodiment, execution units 2212, 2214, 2216, 2218, 2220, 2222, and 2224 can execute instructions. In at least one embodiment, register files 2208 and 2210 store integer and floating-point data operand values required for microinstructions to execute. In at least one embodiment, processor 2200 can include, but is not limited to, any number of execution units 2212, 2214, 2216, 2218, 2220, 2222, and 2224, and combinations thereof. In at least one embodiment, floating-point ALU 2222 and floating-point move unit 2224 can execute floating-point, MMX, SIMD, AVX, SSE, or other operations, including specialized machine learning instructions. In at least one embodiment, floating-point ALU 2222 can include, but is not limited to, a 64-bit by 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 2216 and 2218. In at least one embodiment, fast ALUs 2216 and 2218 can perform fast operations with an effective latency of half a clock cycle. In at least one embodiment, most complex integer operations go to slow ALU 2220, as slow ALU 2220 may include, but is not limited to, integer execution hardware for long-latency operations, such as multipliers, shifts, flag logic, and branch processing. In at least one embodiment, memory load / store operations can be performed by ALUs 2212 and 2214. In at least one embodiment, fast ALUs 2216, 2218, and slow ALU 2220 can perform integer operations on 64-bit data operands. In at least one embodiment, fast ALUs 2216, 2218, and slow ALU 2220 can be implemented to support various data bit sizes, including 16, 32, 128, 226, and the like. In at least one embodiment, the floating point ALU 2222 and floating point shift unit 2224 can be implemented to support a range of operands having bits of various widths. In at least one embodiment, the floating point ALU 2222 and floating point shift unit 2224 can operate on 128-bit wide packed data operands in conjunction with SIMD and multimedia instructions.
[0401] In at least one embodiment, the microinstruction schedulers 2202, 2204, and 2206 schedule dependent operations before the parent load completes execution. In at least one embodiment, because microinstructions can be speculatively scheduled and executed in processor 2200, processor 2200 can also include logic for handling memory misses. In at least one embodiment, if a data load misses in the data cache, there may be dependent operations running in the pipeline that temporarily prevent the scheduler from having 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 allow independent operations to complete. In at least one embodiment, the scheduler and replay mechanism of at least one embodiment of the processor can also be designed to capture instruction sequences for text string comparison operations.
[0402] In at least one embodiment, the term "register" may refer to an on-board processor storage location that can be used as part of an instruction to identify an operand. In at least one embodiment, registers may be those that can be used from outside the processor (from a programmer's perspective). In at least one embodiment, registers may not be limited to a particular type of circuit. Instead, in at least one embodiment, registers can store data, provide data, and perform the functions described herein. In at least one embodiment, the registers described herein can be implemented by circuitry within the processor using a variety of different techniques, such as dedicated physical registers, physical registers dynamically allocated using register renaming, a combination of dedicated and dynamically allocated physical registers, and the like. In at least one embodiment, integer registers store 32-bit integer data. The register file of at least one embodiment also includes eight multimedia SIMD registers for packing data.
[0403] Figure 1-22 The information stored in the database is shared with multiple components within a fifth generation new radio (5G-NR) radio access network. For example, in at least one embodiment, the processor 2200 can be part of the system 100, 200 for executing the call flow diagrams 300, 400 and / or the processes 500, 600 to perform one or more 5G-NR network operations using the database.
[0404] Figure 23A block diagram of a processing system according to at least one embodiment is shown. In at least one embodiment, system 2300 includes one or more processors 2302 and one or more graphics processors 2308, and can be a single-processor desktop system, a multi-processor workstation system, or a server system with a large number of processors 2302 or processor cores 2307. In at least one embodiment, system 2300 is a processing platform incorporated within a system-on-chip (SoC) integrated circuit for use in mobile, handheld, or embedded devices.
[0405] In at least one embodiment, the system 2300 may include or be incorporated into a server-based gaming platform, including a gaming console, a mobile gaming console, a handheld gaming console, or an online gaming console, including a gaming and media console. In at least one embodiment, the system 2300 is a mobile phone, a smart phone, a tablet computing device, or a mobile internet device. In at least one embodiment, the processing system 2300 may also include a device coupled to or integrated into a wearable device, such as a smartwatch wearable device, a smart glasses device, an augmented reality device, or a virtual reality device. In at least one embodiment, the processing system 2300 is a television or set-top box device having one or more processors 2302 and a graphical interface generated by one or more graphics processors 2308.
[0406] In at least one embodiment, one or more processors 2302 each include one or more processor cores 2307 to process instructions that, when executed, perform operations for system and user software. In at least one embodiment, each of the one or more processor cores 2307 is configured to process a specific instruction set 2309. In at least one embodiment, the instruction set 2309 can facilitate complex instruction set computing (CISC), reduced instruction set computing (RISC), or computing via very long instruction words (VLIW). In at least one embodiment, the processor cores 2307 can each process a different instruction set 2309, which can include instructions that facilitate emulation of other instruction sets. In at least one embodiment, the processor cores 2307 can also include other processing devices, such as a digital signal processor (DSP).
[0407] In at least one embodiment, the processor 2302 includes a cache memory 2304. In at least one embodiment, the processor 2302 may have a single internal cache or multiple levels of in...
Claims
1. A processor, comprising: One or more circuits for enabling information stored in a database to be shared with a plurality of components within a fifth generation new radio, 5G-NR, access network.
2. The processor of claim 1 , wherein the one or more circuits are configured to further cause the database to send a request to at least one of the plurality of components in response to a request from an open radio access network (O-RAN) component.
3. The processor of claim 1 , wherein the information indicates one or more first 5G-NR signals of an O-RAN and one or more second 5G-NR signals outside the O-RAN. 4 . The processor of claim 1 , wherein the one or more circuits are configured to further cause the database to access the requested data in the database in response to receiving a request for data from at least one of the plurality of components.
5. The processor of claim 1, wherein the information comprises neural network training data.
6. The processor of claim 1, wherein the one or more circuits are configured to further cause the database to send a periodic data request to at least one of the plurality of components.
7. The processor of claim 1, wherein the database comprises an Ethernet interface for connecting to at least one of the plurality of components.
8. A method comprising: Enables information stored in a database to be shared with multiple components within a fifth generation new radio 5G-NR access network.
9. The method of claim 8, wherein at least two of the plurality of components are Open Radio Access Network (O-RAN) components that communicate with each other using an O-RAN interface.
10. The method according to claim 8, further comprising: In response to receiving a request for data from at least one of the plurality of components, the database is caused to identify among the databases that the database has the requested data.
11. The method according to claim 8, further comprising: The database is caused to convert at least a portion of the information into a format consistent with a component of the plurality of components.
12. The method of claim 8, wherein the information comprises time series data.
13. The method according to claim 8, further comprising: The database is caused to receive the information from an O-RAN component among the plurality of components and a non-O-RAN component among the plurality of components.
14. A system comprising: One or more processors configured to enable information stored in a database to be shared with a plurality of components within a fifth generation new radio 5G-NR access network.
15. The system of claim 14, wherein the one or more processors are configured to further cause the database to send the request to the plurality of components in response to a request from an open radio access network (O-RAN) component.
16. The system of claim 14, wherein the one or more processors are configured to further cause the database to recognize, in response to receiving a request for data from at least one of the plurality of components, that the requested data is not stored in the database.
17. The system of claim 14, wherein at least one of the plurality of components comprises one or more neural networks for performing one or more network operations.
18. The system of claim 14, wherein: The component receiving the information from the database is an O-RAN component or a non-O-RAN component.
19. The system of claim 14, wherein: At least two of the plurality of components are O-RAN components that communicate with each other using an O-RAN interface; and One of at least two components of the plurality of components includes two or more parts that are executed by different processors.
20. The system of claim 14, wherein the database comprises a physical interface for connecting to one or more of the plurality of components.
