Information prioritization in wireless networks

Abstract

The present disclosure relates to information prioritization in wireless networks. Devices, systems, and techniques are disclosed that autonomously adjust the prioritization of information to be transmitted by a UE device. In at least one embodiment, a UE device autonomously adjusts the priority of information to be transmitted by adjusting a priority ranking parameter. In at least one embodiment, the priority ranking parameter is autonomously adjusted by a UE device monitoring packet statistics.

Description

Technical Field

[0001] In at least one embodiment, a user equipment (UE) device autonomously adjusts the priority of information it transmits in a wireless network (eg, by adjusting parameters or settings of its logical channels). Background Art

[0002] Information transmitted between a user equipment (UE) and another device in a wireless network can be prioritized based on many factors. Methods of prioritizing information to be transmitted can be improved in terms of time, quality, computing resources, and / or other considerations. BRIEF DESCRIPTION OF THE DRAWINGS

[0003] Figure 1 An example of a system for performing wireless data prioritization in accordance with at least one embodiment is shown;

[0004] Figure 2 An example of an architecture for performing wireless data prioritization in accordance with at least one embodiment is shown;

[0005] Figure 3A A schematic diagram illustrating a wireless data prioritization process performed by at least one embodiment is shown;

[0006] Figure 3B A schematic diagram illustrating a wireless data prioritization process performed by at least one embodiment is shown;

[0007] Figure 4 A schematic diagram illustrating a wireless data prioritization process performed by at least one embodiment is shown;

[0008] Figure 5 A flow chart illustrating a system for performing wireless data prioritization according to at least one embodiment is shown;

[0009] Figure 6 A flow chart illustrating a system for performing wireless data prioritization according to at least one embodiment is shown;

[0010] Figure 7 A flow chart illustrating a system for performing wireless data prioritization according to at least one embodiment is shown;

[0011] Figure 8 An example including a processor and modules according to at least one embodiment is shown;

[0012] Figure 9 is a block diagram illustrating a driver and / or runtime including one or more libraries for providing one or more application programming interfaces (APIs) according to at least one embodiment;

[0013] Figure 10 An example data center system is shown in accordance with at least one embodiment;

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

[0015] Figure 11B According to at least one embodiment, Figure 11A Examples of camera positions and fields of view for autonomous vehicles;

[0016] Figure 11C According to at least one embodiment Figure 11A A block diagram of an example system architecture for an autonomous vehicle;

[0017] Figure 11D is a diagram illustrating a method for one or more cloud-based servers and Figure 11A A diagram of a system for communicating between autonomous vehicles;

[0018] Figure 12 is a block diagram illustrating a computer system according to at least one embodiment;

[0019] Figure 13 is a block diagram illustrating a computer system according to at least one embodiment;

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

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

[0022] Figure 16A A computer system according to at least one embodiment is shown;

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

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

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

[0026] Figure 16E and Figure 16F illustrates a shared programming model according to at least one embodiment;

[0027] Figure 17 An exemplary integrated circuit and associated graphics processor are shown in accordance with at least one embodiment;

[0028] Figure 18A and Figure 18B An exemplary integrated circuit and associated graphics processor are shown in accordance with at least one embodiment;

[0029] Figure 19A and Figure 19B Additional exemplary graphics processor logic is shown in accordance with at least one embodiment;

[0030] Figure 20 A computer system according to at least one embodiment is shown;

[0031] Figure 21A A parallel processor according to at least one embodiment is shown;

[0032] Figure 21B shows a partition unit according to at least one embodiment;

[0033] Figure 21C illustrates a processing cluster according to at least one embodiment;

[0034] Figure 21D A graphics multiprocessor is shown in accordance with at least one embodiment;

[0035] Figure 22 A multi-graphics processing unit (GPU) system is shown in accordance with at least one embodiment;

[0036] Figure 23 A graphics processor according to at least one embodiment is shown;

[0037] Figure 24 is a block diagram illustrating a processor microarchitecture for a processor according to at least one embodiment;

[0038] Figure 25 illustrates at least a portion of a graphics processor according to one or more embodiments;

[0039] Figure 26 illustrates at least a portion of a graphics processor according to one or more embodiments;

[0040] Figure 27 illustrates at least a portion of a graphics processor according to one or more embodiments;

[0041] Figure 28 is a block diagram of a graphics processing engine of a graphics processor according to at least one embodiment;

[0042] Figure 29 is a block diagram of at least a portion of a graphics processor core according to at least one embodiment;

[0043] Figure 30A and Figure 30B Thread execution logic including an array of processing elements of a graphics processor core is shown in accordance with at least one embodiment;

[0044] Figure 31 illustrates a parallel processing unit ("PPU") in accordance with at least one embodiment;

[0045] Figure 32 illustrates a general processing cluster ("GPC") in accordance with at least one embodiment;

[0046] Figure 33 illustrates a memory partitioning unit of a parallel processing unit ("PPU") according to at least one embodiment;

[0047] Figure 34 A streaming multiprocessor is shown in accordance with at least one embodiment;

[0048] Figure 35 A network for communicating data within a 5G wireless communication network is shown in accordance with at least one embodiment;

[0049] Figure 36 illustrates a network architecture for a 5G LTE wireless network according to at least one embodiment;

[0050] Figure 37 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;

[0051] Figure 38 illustrates a radio access network that may be part of a 5G network architecture in accordance with at least one embodiment;

[0052] Figure 39 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;

[0053] Figure 40 An example high-level system according to at least one embodiment is shown;

[0054] Figure 41 shows the architecture of a network system according to at least one embodiment;

[0055] Figure 42 illustrates example components of a device according to at least one embodiment;

[0056] Figure 43 illustrates an example interface for a baseband circuit according to at least one embodiment;

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

[0058] Figure 45 shows the architecture of a network system according to at least one embodiment;

[0059] Figure 46 illustrates a control plane protocol stack according to at least one embodiment;

[0060] Figure 47 illustrates a user plane protocol stack according to at least one embodiment;

[0061] Figure 48 illustrates components of a core network according to at least one embodiment; and

[0062] Figure 49 Components of a system supporting network function virtualization (NFV) according to at least one embodiment are shown; and

[0063] Figure 50 Components of a system for accessing large language models in accordance with at least one embodiment are shown. DETAILED DESCRIPTION

[0064] In at least one embodiment, different types of information can be wirelessly transmitted according to different channel prioritizations. In at least one embodiment, control information dictates how wireless signals are transmitted. In at least one embodiment, a logical channel prioritization procedure dictates the priority each type of information should have, and the UE device then uses its radio to transmit higher priority information before lower priority information.

[0065] In at least one embodiment, a UE can modify its logical channel prioritization settings to avoid delays in transmitting certain types of information. In at least one embodiment, high-priority control data can have its logical channel prioritization parameters set to allow transmission of those high-priority signals greater bandwidth resources and higher queue placement than lower-priority data. In at least one embodiment, one or more systems adjust the priority of a certain type of information based on measurements of whether the transmission of that type of information was successful. In at least one embodiment, a UE device performs one or more adjustments to one or more logical channel prioritization parameters. In at least one embodiment, if the UE detects that control information was not successfully transmitted, the system executed by the UE can increase the priority of the control information so that more transmissions can be performed to compensate for the unsuccessful transmissions that must be performed again. In at least one embodiment, unsuccessful transmissions are detected based on packet statistics such as packet error rate, successful and / or failed transmissions of packets, and / or queue lengths for packets. In at least one embodiment, if the logical channel prioritization system executed by the UE detects that control information is being transmitted to the base station without errors, the logical channel prioritization system can lower the priority of the control information to allow additional transmissions to have a higher priority, resulting in more information being transmitted. In at least one embodiment, the UE device autonomously adjusts the priority of information to be transmitted based at least in part on one or more packet statistics, such that the UE device uses the one or more packet statistics to indicate that the priority of the information needs to be adjusted. In at least one embodiment, the logical channel prioritization system is used with any communication standards and protocols set by the Third Generation Partnership Project (3GPP), including but not limited to third generation (3G), fourth generation (4G), fifth generation new radio (5G NR), and sixth generation (6G) wireless access technologies.

[0066] Figure 1An example of a system 100 for performing wireless data prioritization according to at least one embodiment is shown. In at least one embodiment, system 100 includes a user equipment (UE) 102 having one or more processors 104, a user interface 106, one or more memory devices 108 having instructions 110 including one or more applications 112, one or more logical channel prioritization functions 114, one or more transmission functions 116, and one or more packet monitoring functions 118. In at least one embodiment, UE 102 wirelessly communicates with a base station 120 having one or more processors, one or more memory devices having one or more instructions 126 including radio resource control (RRC) signaling 128, and one or more transmission functions 130. In at least one embodiment, UE 102 and base station 120 communicate using a radio link 132, e.g., they can send, receive, or otherwise share information, such as data packets, reference signals, or other communications (e.g., as part of a wireless communication standard identified by the Institute of Electrical and Electronics Engineers (IEEE)). In at least one embodiment, the radio link includes radio frequency signals, channels, or other information used to connect or communicate with a 5G network. In at least one embodiment, apparatuses, systems, methods, and techniques are disclosed herein where adjustments to logical channel prioritization parameters are performed autonomously by UE 102. In at least one embodiment, autonomously adjusting one or more logical channel prioritization parameters can occur without requiring instructions from a base station to adjust the prioritization parameters. In at least one embodiment, apparatuses, systems, methods, and techniques are disclosed herein where logical channel prioritization 114 is performed by UE 102 to adjust the prioritization of transmissions.

[0067] In at least one embodiment, UE 102 causes one or more processors 104 to execute one or more instructions 110 stored in one or more memory devices 108. In at least one embodiment, one or more applications 112 are software that can request the use of one or more transport functions 116 to transmit data between UE 102 and base station 120. In at least one embodiment, one or more applications 112 are cellular voice calling, email viewing and sending software, and / or video viewing software. In at least one embodiment, one or more applications 112 request UE 102 to use radio link 132 and one or more transport functions 116 to transmit information uplink and / or downlink. In at least one embodiment, one or more applications 112 request the use of radio link 132 to upload and / or download video data, voice data, and text data. In at least one embodiment, logical channel prioritization 114 generates one or more logical channel prioritization parameters for transmission requests issued by one or more applications 112. In at least one embodiment, logical channels are identified by logical channel prioritization, wherein each channel has one or more prioritization parameters based on one or more policies of logical channel prioritization 114. In at least one embodiment, logical channel prioritization 114 adjusts the one or more logical channel prioritization parameters of the one or more logical channels based on one or more criteria being satisfied. In at least one embodiment, logical channel prioritization 114 autonomously adjusts the one or more logical channel prioritization parameters without receiving control instructions from base station 120. In at least one embodiment, logical channel prioritization 114 receives information from one or more packet monitoring functions 118 indicating that the one or more logical channel prioritization parameters should be adjusted. In at least one embodiment, logical channel prioritization 114 determines to adjust the one or more logical channel prioritization parameters based on information provided by the one or more packet monitoring functions 118.

[0068] In at least one embodiment, the one or more transmission functions include software executed by one or more processors for causing information to be transmitted uplink and / or downlink to the base station 120 using the radio link 132. In at least one embodiment, the one or more transmission functions 116 transmit information to the base station 120 using one or more logical channel prioritization parameters from the logical channel prioritization 114. In at least one embodiment, the one or more transmission functions use the logical channel prioritization parameters to identify a bit rate for transmitting information to the base station 120 using the radio link 132. In at least one embodiment, the one or more packet monitoring functions 118 monitor packet statistics, such as arrival rate, latency, packet error rate, successful and / or failed delivery of packets, and queue length for packets sent to the base station 120 using the radio link 132. In at least one embodiment, the packet monitoring function 118 generates reporting data for the packet statistics to be used by the logical channel prioritization 114.

[0069] In at least one embodiment, the base station 120 has one or more processors 122, one or more memory devices 124 storing one or more instructions 126, including one or more radio resource control (RRC) signaling 128, and one or more transmission functions 130. In at least one embodiment, the base station 120 causes the one or more processors 122 to execute the one or more instructions 126. In at least one embodiment, the RRC signaling 128 can be software that causes the base station 120 to send one or more RRC signals that cause one or more UE devices to adjust one or more parameters that control resources used to transmit information using the radio link 132. In at least one embodiment, the RRC signaling 128 uses the one or more transmission functions 130 to send the RRC signals to the UE 102 using the radio link 132.

[0070] In at least one embodiment, the processor 104 and / or the processor 122 may include one or more parallel processing units (PPUs), such as one or more graphics processing units (GPUs). In at least one embodiment, the processor 104 and / or the processor 122 may include one or more massively parallel GPUs. In at least one embodiment, a massively parallel GPU refers to a collection of one or more GPUs or any suitable processing units that can be used to execute various processes in parallel. In at least one embodiment, the processor 104 and / or the processor 122 may be implemented, for example, using a main central processing unit (CPU) complex, one or more microprocessors, one or more microcontrollers, a PPU (e.g., a GPU), one or more data processing units (DPUs), one or more arithmetic logic units (ALUs). In at least one embodiment, the processor 104 and / or the processor 122 may be Figures 10 to 50 as described in or with the embodiments depicted in Figures 10 to 50 In at least one embodiment, the memory device 108 and / or the memory device 124 (e.g., one or more non-transitory processor-readable media) may be implemented using volatile memory (e.g., dynamic random access memory (DRAM)) and / or non-volatile memory (e.g., hard drive, solid-state device (SSD)). In at least one embodiment, the user interface 106 is one or more input-output devices that allow a user to cause one or more instructions 110 to be executed by the processor 104. In at least one embodiment, the user interface 106 may be Figures 10 to 50 as described in or with the embodiments depicted in Figures 10 to 50 Any user interface used in conjunction with the embodiments depicted in .

[0071] Figure 2 An example of an architecture 200 for performing wireless data prioritization in accordance with at least one embodiment is shown. In at least one embodiment, the architecture 200 includes logical channel prioritization 202, which includes software for autonomously adjusting one or more prioritization parameters 214 of one or more logical channels 212 of a UE device without requiring instructions from a base station to adjust the prioritization parameters. In at least one embodiment, the one or more prioritization parameters 214 are associated with bit rate bandwidth allocations for the logical channels, queue placement for the logical channels, and / or timer offsets and settings for uplink and downlink availability times for the logical channels. In at least one embodiment, the architecture 200 is Figure 11 and 2. In at least one embodiment, the architecture 200 includes one or more packet monitoring functions 204 that generate packet information 206, one or more applications 208 that make transmission requests 210, one or more logical channel prioritization functions 202 having one or more logical channels 212 and one or more prioritization parameters 214, and one or more transmission functions 216.

[0072] In at least one embodiment, the packet monitoring function 204 generates packet information 206, which includes data related to packet statistics, packet error rates, successful and / or failed transmissions of packets, and queue lengths for packets transmitted by the UE device. In at least one embodiment, the packet monitoring function 204 provides the packet information 206 to the logical channel prioritization 202. In at least one embodiment, one or more applications are software being executed by the UE device and make one or more transmission requests 210 for data. In at least one embodiment, the application 208 generates the transmission request 210 that is provided to the logical channel prioritization 202.

[0073] In at least one embodiment, logical channel prioritization 202 receives one or more transmission requests 210 for uploading and / or downloading data to a base station over a wireless network. In at least one embodiment, logical channel prioritization 202 associates a logical channel 212 and prioritization parameters 214 with each transmission request 210. In at least one embodiment, a logical channel 212 is a set of resource control, transmission priority, and organization parameters associated with a transmission request 210. In at least one embodiment, a logical channel 212 has parameters associated with a guaranteed stream bit rate, a maximum stream bit rate, a packet delay budget, and a packet error rate target. In at least one embodiment, logical channel prioritization 202 associates one or more prioritization parameters 214 with each logical channel 212 associated with a transmission request 210. In at least one embodiment, the prioritization parameters 214 include a parameter, prioritizedBitRate, which is a bit rate allocation representing the amount of guaranteed or allocated bandwidth or data rate. In at least one embodiment, logical channel prioritization 202 adjusts the prioritization parameters 214 based on packet information 206 provided by packet monitoring function 204. In at least one embodiment, logical channel prioritization 202 uses packet information 206 to determine that one or more packet statistics indicate that one or more prioritization parameters 214 should be adjusted. In at least one embodiment, logical channel prioritization 202 autonomously adjusts one or more prioritization parameters 214 without receiving an instruction from a base station to adjust the prioritization parameters 214. In at least one embodiment, one or more transmission functions 216 cause data to be uploaded to and / or downloaded from the wireless network to satisfy one or more transmission requests 210 from one or more applications 208. In at least one embodiment, transmission function 216 uses logical channels 212 and prioritization parameters 214 to control transmissions and resource control parameters of the transmissions.

[0074] In at least one embodiment, the logical channel prioritization 202 performs prioritized bit rate adaptation. In at least one embodiment, based on the quality of service (QoS) requirements (e.g., guaranteed stream bit rate, maximum stream bit rate, packet delay budget, and packet error rate target) of the traffic carried on the associated logical channel 212, the UE's prioritization parameter 214 prioritizedBitRate is configured with an initial value of PBR0, and the logical channel prioritization 202 autonomously adjusts the value of the prioritization parameter 214 prioritizedBitRate from time to time to PBRt=PBR0+θt, where PBRt represents the value of the parameter prioritizedBitRate at time t, and θt is an offset value applied to adjust the initial value of prioritizedBitRate, and when t=0, θt=0.

[0075] In at least one embodiment, the UE device causes logical channel prioritization 202 to monitor whether a packet is successfully delivered in a Packet Data Convergence Protocol (PDCP) layer or is dropped in the PDCP layer. In at least one embodiment, when logical channel prioritization 202 observes that a packet is successfully delivered in the PDCP layer, logical channel prioritization 202 decrements an offset value θt of the prioritized bit rate by a value Δdown.

[0076] In at least one embodiment, when logical channel prioritization 202 observes that a packet is dropped in the PDCP layer, logical channel prioritization 202 increments the offset value θt of the prioritized bit rate by a value Δ up .

[0077] In at least one embodiment, the offset value θt is updated according to the following formula:

[0078] θ t =θ t-1 +Δ up ·e t -Δ down ·(1-e t ),t≥1

[0079] where e t is an error indicator, and if the packet is successfully transmitted in the PDCP layer, its value is 0, otherwise it is 1. In at least one embodiment, the interval between time t and t-1 can be specified or configured.

[0080] In at least one embodiment, the logical channel prioritization 202 monitors the received packet information 206 to understand the packet error rate in the PDCP layer and / or whether packets are dropped in the PDCP layer. In at least one embodiment, the packet error rate is calculated as the ratio of the number of packets lost to the total number of packets arriving within an observation window of a certain duration. In at least one embodiment, the duration is equal to the interval between time t and t-1. In at least one embodiment, when the logical channel prioritization 202 observes that the packet error rate in the PDCP layer is below a threshold, the logical channel prioritization 202 decrements the offset value θt of the prioritized bit rate by a value Δdown. In at least one embodiment, when the logical channel prioritization 202 observes that the packet error rate in the PDCP layer is above a threshold, the logical channel prioritization 202 increments the offset value θt of the prioritized bit rate by a value Δup.

[0081] In at least one embodiment, the logical channel prioritization 202 sets a target packet error rate T (eg, 0.001%) in the PDCP layer and selects a Δ that satisfies the following relationship: down and Δ up Value:

[0082]

[0083] In at least one embodiment, the target packet error rate T is small, resulting in Δ up >>Δ down In at least one embodiment, Δ down and Δ up The value of is chosen to satisfy the following relationship:

[0084]

[0085] In at least one embodiment, the logical channel prioritization 202 is configured with a threshold and hysteresis parameters. In at least one embodiment, when the logical channel prioritization 202 observes a packet error rate in the PDCP layer below [threshold - hysteresis], the logical channel prioritization 202 decrements the offset value θt of the prioritized bit rate by a value Δdown.

[0086] In at least one embodiment, when logical channel prioritization 202 observes a packet error rate in the PDCP layer higher than [threshold + hysteresis], logical channel prioritization 202 increments the offset value θt of the prioritized bit rate by a value Δup.

[0087] In at least one embodiment, the UE is configured with a timer, wherein the logical channel prioritization 202 starts the timer when it observes "packet error rate < threshold - hysteresis." In at least one embodiment, the timer is one or more software modules for measuring and recording. In at least one embodiment, when the timer is running, if the logical channel prioritization 202 observes "packet error rate >= threshold," the logical channel prioritization 202 stops the timer. In at least one embodiment, when the timer expires, the logical channel prioritization 202 decrements the offset value θt of the prioritized bit rate by a value Δdown. In at least one embodiment, when the logical channel prioritization 202 observes "packet error rate > threshold + hysteresis," the logical channel prioritization 202 starts the timer. In at least one embodiment, when the timer is running, if the logical channel prioritization 202 observes "packet error rate <= threshold," the logical channel prioritization 202 stops the timer. In at least one embodiment, when the timer expires, the logical channel prioritization 202 increments the offset value θt of the prioritized bit rate by a value Δup.

[0088] In at least one embodiment, the logical channel prioritization 202 monitors packet delivery / discarding in the radio link control (RLC) layer using the packet information 206, and the logical channel prioritization 202 determines to decrement / increment the prioritized bit rate accordingly. In at least one embodiment, the logical channel prioritization 202 monitors packet delivery / discarding in the MAC layer using the packet information 206, and the logical channel prioritization 202 determines to decrement / increment the prioritized bit rate accordingly.

[0089] In at least one embodiment, a network node (e.g., a gNB) uses cell-level radio resource control (RRC) signaling (e.g., broadcast signaling via a system information block or UE group common multicast signaling) to signal the values ​​of Δdown and Δup. In at least one embodiment, the network node (e.g., a gNB) uses UE-specific RRC signaling to signal the values ​​of Δdown and Δup. In at least one embodiment, the network node (e.g., a gNB) uses a medium access control (MAC) control element (CE) to signal the values ​​of Δdown and Δup. In at least one embodiment, the network node (e.g., a gNB) uses downlink control information (DCI) to signal the values ​​of Δdown and Δup. In at least one embodiment, the network node (e.g., a gNB) uses cell-level and / or UE-specific RRC signaling to configure a UE with a list of Δdown values ​​and a list of Δup values. In at least one embodiment, the network node uses a MAC CE to activate and deactivate Δdown values ​​in the Δdown value list and Δup values ​​in the Δup value list. In at least one embodiment, a network node (e.g., a gNB) configures a UE with a list of Δdown values ​​and a list of Δup values ​​using cell-level and / or UE-specific RRC signaling. In at least one embodiment, the network node uses DCI to activate and deactivate Δdown values ​​in the Δdown value list and Δup values ​​in the Δup value list.

[0090] In at least one embodiment, the UE is configured with threshold and hysteresis parameters based on the QoS requirements (e.g., guaranteed stream bit rate, maximum stream bit rate, packet delay budget, and packet error rate target) of the traffic carried on the associated logical channel 212. In at least one embodiment, the logical channel prioritization 202 monitors the queue length of the logical channel 212. In at least one embodiment, when the logical channel prioritization 202 observes "queue length < threshold - hysteresis," the logical channel prioritization 202 decrements the offset value θt of the prioritized bit rate by a value Δdown. In at least one embodiment, when the logical channel prioritization 202 observes "queue length > threshold + hysteresis," the logical channel prioritization 202 increments the offset value θt of the prioritized bit rate by a value Δup.

[0091] In at least one embodiment, the logical channel prioritization 202 starts a timer when the UE observes "queue length < threshold - hysteresis". In at least one embodiment, when the timer is running, when the logical channel prioritization 202 observes "queue length >= threshold", the logical channel prioritization 202 stops the timer. In at least one embodiment, when the timer expires, the logical channel prioritization 202 decrements the offset value θt of the prioritized bit rate by a value Δdown. In at least one embodiment, when the logical channel prioritization 202 observes "queue length > threshold + hysteresis", the logical channel prioritization 202 starts a timer. In at least one embodiment, when the timer is running, when the logical channel prioritization 202 observes "queue length <= threshold", the logical channel prioritization 202 stops the timer. In at least one embodiment, when the timer expires, the logical channel prioritization 202 increments the offset value θt of the prioritized bit rate by a value Δup.

[0092] In at least one embodiment, a first threshold value, a first hysteresis value, a first timer value, and / or a combination thereof are configured for logical channel prioritization 202 to determine the event "queue length < threshold - hysteresis". In at least one embodiment, a second threshold value, a second hysteresis value, a second timer value, and / or a combination thereof are configured for logical channel prioritization 202 to determine the event "queue length > threshold + hysteresis".

[0093] In at least one embodiment, when logical channel prioritization 202 determines to increment prioritization parameter 214, logical channel prioritization 202 autonomously adjusts the value of prioritization parameter 214 prioritizedBitRate to:

[0094] PBR t =PBR t-1 *(1+Δ up ),

[0095] Furthermore, when the logical channel prioritization 202 determines the decrementing prioritization parameter 214, the logical channel prioritization 202 autonomously adjusts the value of the prioritization parameter 214 prioritizedBitRate to:

[0096] PBR t =PBR t-1 *(1-Δ down )

[0097] In at least one embodiment, when logical channel prioritization 202 determines to increment prioritization parameter 214, logical channel prioritization 202 autonomously adjusts the value of prioritization parameter 214 prioritizedBitRate to:

[0098] PBR t =PBR t-1 *(1+Δ up )

[0099] Furthermore, when the logical channel prioritization 202 determines the decrementing prioritization parameter 214, the logical channel prioritization 202 autonomously adjusts the value of the prioritization parameter 214 prioritizedBitRate to:

[0100] PBR t =PBR t-1 -Δ down ,

[0101] In at least one embodiment, when logical channel prioritization 202 determines to increment prioritization parameter 214, logical channel prioritization 202 autonomously adjusts the value of prioritization parameter 214 prioritizedBitRate to:

[0102] PBR t =PBR t-1 +Δ up ,

[0103] Furthermore, when the logical channel prioritization 202 determines the decrementing prioritization parameter 214, the logical channel prioritization 202 autonomously adjusts the value of the prioritization parameter 214 prioritizedBitRate to:

[0104] PBR t =PBR t-1 *(1-Δ down )

[0105] In at least one embodiment, the logical channel prioritization 202 performs prioritized bit rate adaptation using reinforcement learning. In at least one embodiment, for the logical channel 212, the logical channel prioritization 202 establishes a state set, denoted by S, which consists of a set of elements representing the distribution of logical channel priorities. In at least one embodiment, the element represents the number of logical channels with a higher priority than the logical channel 212 in question. In at least one embodiment, based on a 5G NR wireless network having a maximum number of logical channels configurable to 30, the state set is represented as S = {0, 1, 2, ..., 29}. In at least one embodiment, the element is an (x, y) pair, where x represents the number of logical channels with a higher priority than the logical channel 212 in question, and y represents the number of logical channels with a lower priority than the logical channel 212 in question.

[0106] In at least one embodiment, logical channel prioritization 202 defines an action set, denoted A, consisting of a set of prioritized bit rates. In at least one embodiment, in a 5G NR network, the prioritized bit rate set is given by {kBps0, kBps8, kBps16, kBps32, kBps64, kBps128, kBps256, kBps512, kBps1024, kBps2048, kBps4096, kBps8192, kBps16384, kBps32768, kBps65536, infinity}, where the value kBps0 corresponds to 0 kilobytes / second, the value kBps8 corresponds to 8 kilobytes / second, the value kBps16 corresponds to 16 kilobytes / second, and so on. In at least one embodiment, the prioritized bit rate set forms action set A.

[0107] In at least one embodiment, logical channel prioritization 202 formulates a reward function, denoted by R(s,a), which represents the reward for taking action a∈A in state s∈S. In one example, the reward is 1 minus the packet error rate, where the packet error rate is calculated as the ratio of the number of packets lost to the total number of packets arriving within an observation window of some duration. In at least one embodiment, the observation window begins after the current action is taken and ends before the next action is taken.

[0108] In at least one embodiment, logical channel prioritization 202 formulates a Q value table, denoted as Q(s,a), which is iteratively updated and denoted as Q t (s, a), the updated Q value during the tth iteration. In at least one embodiment, the Q value is set to zero, for example,

[0109] In at least one embodiment, if the logical channel prioritization 202 receives an RRC reconfiguration that would cause a change in state s, the logical channel prioritization 202 sets the current state s based on the existing RRC configuration. t , and sets the next state s based on the newly received RRC reconfiguration (t+1) Otherwise, the logical channel prioritization 202 sets the current state s based on the existing RRC configuration t , and also sets the next state s based on the existing RRC configuration (t+1) .

[0110] In at least one embodiment, logical channel prioritization 202 selects the current state s t In at least one embodiment, the logical channel prioritization 202 sets a probability value ∈∈[0,1]. In at least one embodiment, the logical channel prioritization 202 generates a uniform random value in the interval [0,1]. In at least one embodiment, with probability ∈, the logical channel prioritization 202 randomly selects a prioritized bit rate value from the set A. In at least one embodiment, with probability 1-∈, the logical channel prioritization 202 selects the value of the prioritized bit rate in a given state s t The value of the prioritized bit rate that produces the maximum Q value under t =argmax a∈A Q(s t ,a).

[0111] In at least one embodiment, logical channel prioritization 202 is used in the current state s t In at least one embodiment, the logical channel prioritization 202 sets the learning rate β∈(0,1] and the discount factor γ∈[0,1]. In at least one embodiment, the logical channel prioritization 202 estimates the best future Q value as max a∈A Q t (s t+1 ,a), For example, the next state s (t+1) Insert the current Q value function Q t (s, a), and select the maximum value among the set of values ​​obtained by different actions a. In at least one embodiment, logical channel priority sorting 202 is performed by selecting the current state s t The prioritized bit rate a t To estimate the reward R t (s t ,a t ), which is 1 minus the packet error rate, where the packet error rate is calculated as the bit rate a after applying the prioritized tThe ratio of the number of packets lost to the total number of packets arriving within an observation window of some duration is then calculated. In at least one embodiment, the logical channel prioritization 202 will reward R t (s t ,a t ) and the estimated optimal future Q value max a∈A Q t (s t+1 ,a) (weighted by the discount factor γ) to obtain the new R t (s t ,a t )+γmax a∈A Q t (s t+1 ,a). In at least one embodiment, the logical channel prioritization 202 sets the current value Q t (s t ,a t )(weighted by 1-β) and the new value R t (s t ,a t )+γmax a∈A Q t (s t+1 ,a) (weighted by β) and use it to update the Q value, e.g.,

[0112]

[0113] In at least one embodiment, the logical channel prioritization 202 trains a neural network with parameters w to generate an approximate Q-value function Q(s, a; w). In at least one embodiment, the logical channel prioritization 202 iteratively selects its action a in the current state s. s , as shown below. In at least one embodiment, the logical channel prioritization 202 sets a probability value ∈∈[0,1]. In at least one embodiment, the logical channel prioritization 202 generates a uniform random value on the interval [0,1]. In at least one embodiment, with probability ∈, the logical channel prioritization 202 randomly selects a value of the prioritized bit rate from the set A. In at least one embodiment, with probability 1-∈, the logical channel prioritization 202 selects the value of the prioritized bit rate that produces the maximum Q value for a given state s, such as a s =argmax a∈A Q(s,a;w).

[0114] In at least one embodiment, logical channel prioritization 202 applies the selected prioritized bit rate a s And estimate the reward R(s,a s), which is 1 minus the packet error rate, where the packet error rate is calculated as the bit rate a after applying the prioritized s The ratio of the number of packets lost to the total number of packets arriving within an observation window of a certain duration after the state s is reached. In at least one embodiment, the logical channel prioritization 202 transitions from state s to state s', where s' represents the new logical channel priority distribution if the logical channel prioritization 202 receives an RRC reconfiguration that causes a change in state s, and s'=s otherwise.

[0115] In at least one embodiment, logical channel prioritization 202 assigns a quadruple (s, a s ,R(s,a s ),s′) are stored in batch P. In at least one embodiment, when the batch size is greater than a threshold m, the logical channel prioritization 202 samples a random small batch P of size m from the batch P. m , where P m,S Is only P m The state vector consists of the current states of all entries in P, and P m,S (i) is the state vector P of dimension m m,S The i-th current state in .

[0116] In at least one embodiment, logical channel prioritization 202 updates a Q-value function Q(s,a;w) at each step of training and updates a second Q-value function Q(s,a;w) at each multiple step of training.

[0117] In at least one embodiment, during the initial phase of training, the logical channel prioritization 202 uses the corresponding rewards to update the Q value, for example, Q(P m,S (i),a;w)←R(P m,S (i), a). In at least one embodiment, after an initial phase of training, the logical channel prioritization 202 updates the Q value using the corresponding reward plus the discounted maximum next step Q value, e.g. In at least one embodiment, logical channel prioritization 202 performs gradient descent to minimize a loss function, E, with respect to parameter w. s′ [R+λmax a′∈A Q(s′,a′;w hold )] and the expected squared error between Q(s,a;w). In at least one embodiment, after each multi-step training, w hold Will be updated to w.

[0118] In at least one embodiment, logical channel prioritization 202 is configured with an initial value of parameter priority of P0 based on the QoS requirements (e.g., guaranteed stream bit rate, maximum stream bit rate, packet delay budget, and packet error rate target) of the traffic carried on the associated logical channel 212, and autonomously adjusts the prioritization parameter 214 to P t =P0+η t , where P0 represents the value of the parameter priority at time t, η t is an offset value applied to adjust the initial value of the priority, and when t=0, η t =0.

[0119] In at least one embodiment, the logical channel prioritization 202 monitors whether packets are successfully delivered in the PDCP, RLC, and MAC layers and / or whether packets are dropped in the PDCP, RLC, and / or MAC layers. In at least one embodiment, when the logical channel prioritization 202 observes that packets are successfully delivered in the PDCP, RLC, and / or MAC layers, the logical channel prioritization 202 lowers the priority of the associated logical channel 212, for example, by offsetting the priority of the prioritization parameter 214 by a value n. t Increment by 1. In at least one embodiment, when the logical channel prioritization 202 observes that a packet is dropped in the PDCP, RLC, and / or MAC layer, the logical channel prioritization 202 increases the priority of the associated logical channel 212, for example, by offsetting the priority of the prioritization parameter 214 by a value n. t Decrement by 1.

[0120] In at least one embodiment, logical channel prioritization 202 monitors packet error rates and / or drops in the PDCP, RLC, and / or MAC layers using packet information 206. In at least one embodiment, the packet error rate is calculated as the ratio of the number of packets lost to the total number of packets arriving within an observation window of a certain duration. In at least one embodiment, the duration is equal to the interval between time t and time t-1. In at least one embodiment, when logical channel prioritization 202 observes that the packet error rate in the PDCP, RLC, and / or MAC layers is below a threshold, logical channel prioritization 202 lowers the priority of the associated logical channel 212, for example, by shifting the priority of prioritization parameter 214 by a value n. t Increment by 1. In at least one embodiment, when the logical channel prioritization 202 observes that the packet error rate in the PDCP, RLC, and / or MAC layer is above a threshold, the logical channel prioritization 202 increases the priority of the associated logical channel 212, for example, by offsetting the priority of the prioritization parameter 214 by a value n. t Decrement by 1.

[0121] In at least one embodiment, the logical channel prioritization 202 is configured with a threshold and a hysteresis parameter based on the QoS requirements (e.g., guaranteed stream bit rate, maximum stream bit rate, packet delay budget, and packet error rate target) of the traffic carried on the associated logical channel 212. In at least one embodiment, the logical channel prioritization 202 monitors the queue length of the logical channel 212. In at least one embodiment, when the logical channel prioritization 202 observes "queue length < threshold - hysteresis", the logical channel prioritization 202 lowers the priority of the associated logical channel 212, for example, by shifting the priority of the prioritization parameter 214 by an offset value n. t Increment by 1. In at least one embodiment, when the logical channel prioritization 202 observes "queue length > threshold + hysteresis", the logical channel prioritization 202 increases the priority of the associated logical channel 212, for example, by offsetting the priority of the prioritization parameter 214 by the value n. t Decrement by 1.

[0122] In at least one embodiment, when the logical channel prioritization 202 observes "queue length < threshold - hysteresis", the logical channel prioritization 202 starts a timer. In at least one embodiment, while the timer is running, when the logical channel prioritization 202 observes "queue length >= threshold", the logical channel prioritization 202 stops the timer. In at least one embodiment, when the timer expires, the logical channel prioritization 202 lowers the priority of the associated logical channel 212, for example, by offsetting the priority of the prioritization parameter 214 by a value η. t Incremented by 1. In at least one embodiment, when the logical channel prioritization 202 observes "queue length > threshold + hysteresis", the logical channel prioritization 202 starts the timer. In at least one embodiment, when the timer is running, when the logical channel prioritization 202 observes "queue length <= threshold", the logical channel prioritization 202 stops the timer. In at least one embodiment, when the timer expires, the logical channel prioritization 202 increases the priority of the associated logical channel 212, for example, by an offset value η of the priority of the prioritization parameter 214. t Decrement by 1.

[0123] In at least one embodiment, when logical channel prioritization 202 determines to increment the value of prioritization parameter 214, logical channel prioritization 202 autonomously adjusts the value of prioritization parameter 214 to P t =P t-1 *2, when the logical channel prioritization 202 determines to decrease the value of the prioritization parameter 214, the logical channel prioritization 202 autonomously adjusts the value of the prioritization parameter 214 to Pt =round(P t-1 *0.5).

[0124] In at least one embodiment, when logical channel prioritization 202 determines to increment the value of prioritization parameter 214, logical channel prioritization 202 autonomously adjusts the value of prioritization parameter 214 to P t =P t-1 *2, and when the logical channel prioritization 202 determines to decrement the value of the prioritization parameter 214, the logical channel prioritization 202 autonomously adjusts the value of the prioritization parameter 214 to P t =P t-1 -1.

[0125] In at least one embodiment, when logical channel prioritization 202 determines to increment the value of prioritization parameter 214, logical channel prioritization 202 autonomously adjusts the value of prioritization parameter 214 to P t =P t-1 +1, and when the logical channel prioritization 202 determines to decrement the value of the prioritization parameter 214, the logical channel prioritization 202 autonomously adjusts the value of the prioritization parameter 214 to P t =round(P t-1 *0.5).

[0126] In at least one embodiment, the logical channel prioritization 202 is configured with an initial value of the prioritization parameter 214 bucketSizeDuration of BSD0 and autonomously adjusts the value of the prioritization parameter 214 bucketSizeDuration to BSD based on the QoS requirements of the traffic carried on the associated logical channel 212 (e.g., guaranteed stream bit rate, maximum stream bit rate, packet delay budget, and packet error rate target). t =BSD0+σ t , among which BSD t represents the value of the priority sorting parameter 214 bucketSizeDuration at time t, σ t is the offset value applied to adjust the initial value of bucketSizeDuration. When t=0, σ t =0.

[0127] In at least one embodiment, the logical channel prioritization 202 monitors whether packets are successfully delivered in the PDCP, RLC, and MAC layers and / or whether packets are dropped in the PDCP, RLC, and / or MAC layers. In at least one embodiment, when the logical channel prioritization 202 observes that packets are successfully delivered in the PDCP, RLC, and / or MAC layers, the logical channel prioritization 202 offsets the bucket size duration by a value σ. t Decreasing value δ down In at least one embodiment, when logical channel prioritization 202 observes packets being dropped in the PDCP, RLC, and / or MAC layers, logical channel prioritization 202 offsets the bucket size duration by a value σ t Incremental value δ up .

[0128] In at least one embodiment, the logical channel prioritization 202 monitors packet error rates in the PDCP, RLC, and MAC layers and / or packets dropped in the PDCP, RLC, and / or MAC layers. In at least one embodiment, the packet error rate is calculated as the ratio of the number of packets lost to the total number of packets arriving within an observation window of a certain duration. In at least one embodiment, the duration is equal to the interval between time t and time t-1. In at least one embodiment, when the logical channel prioritization 202 observes that the packet error rate is below a threshold in the PDCP, RLC, and / or MAC layers, the logical channel prioritization 202 offsets the bucket size by a value σ for the duration. t Decreasing δ down In at least one embodiment, when the logical channel prioritization 202 observes that the packet error rate is higher than a threshold in the PDCP, RLC, and / or MAC layer, the logical channel prioritization 202 offsets the bucket size duration by a value σ t Incremental value δ up .

[0129] In at least one embodiment, the logical channel prioritization 202 is configured with threshold and hysteresis parameters based on the QoS requirements (e.g., guaranteed stream bit rate, maximum stream bit rate, packet delay budget, and packet error rate target) of the traffic carried on the associated logical channel 212. In at least one embodiment, the logical channel prioritization 202 monitors the queue length of the logical channel 212. In at least one embodiment, when the logical channel prioritization 202 observes "queue length < threshold - hysteresis", the logical channel prioritization 202 offsets the bucket size duration by a value σ t Decreasing δ dowIn at least one embodiment, when the logical channel prioritization 202 observes "queue length > threshold + hysteresis", the logical channel prioritization 202 offsets the bucket size duration by the value σ t Increasing δ up value.

[0130] In at least one embodiment, when the logical channel prioritization 202 observes "queue length < threshold - hysteresis", the logical channel prioritization 202 starts a timer. In at least one embodiment, when the timer is running, when the logical channel prioritization 202 observes "queue length >= threshold", the logical channel prioritization 202 stops the timer. In at least one embodiment, when the timer expires, the logical channel prioritization 202 increases the bucket size duration by an offset value σ. t Decreasing value δ down In at least one embodiment, when the logical channel prioritization 202 observes "queue length > threshold + hysteresis", the logical channel prioritization 202 starts a timer. In at least one embodiment, when the timer is running, when the logical channel prioritization 202 observes "queue length <= threshold", the logical channel prioritization 202 stops the timer. In at least one embodiment, when the timer expires, the logical channel prioritization 202 increases the bucket size duration by an offset value σ. t Incremental value δ up .

[0131] In at least one embodiment, when logical channel prioritization 202 determines to increment the bucket size duration, logical channel prioritization 202 autonomously adjusts the value of prioritization parameter 214 bucketSizeDuration to BSD t =BSD t-1 *(1+Δ up ), and when the logical channel prioritization 202 determines to decrement the bucket size duration, the logical channel prioritization 202 autonomously adjusts the value of the prioritization parameter 214 bucketSizeDuration to BSD t =BSD t-1 *(1-Δ down ).

[0132] In at least one embodiment, when logical channel prioritization 202 determines to increment the bucket size duration, logical channel prioritization 202 autonomously adjusts the value of prioritization parameter 214 bucketSizeDuration to BSD t =BSD t-1 *(1+Δ up), and when the logical channel prioritization 202 determines to decrement the bucket size duration, the logical channel prioritization 202 autonomously adjusts the value of the prioritization parameter 214 bucketSizeDuration to BSD t =BSD t-1 -Δ down .

[0133] In at least one embodiment, when logical channel prioritization 202 determines to increment the bucket size duration, logical channel prioritization 202 autonomously adjusts the value of prioritization parameter 214 bucketSizeDuration to BSD t =BSD t-1 +Δ up , and when the logical channel prioritization 202 determines to decrement the bucket size duration, the logical channel prioritization 202 autonomously adjusts the value of the prioritization parameter 214 bucketSizeDuration to BSD t =BSD t-1 *(1-Δ down ).

[0134] In at least one embodiment, logical channel prioritization 202 is performed by Figure 1 In at least one embodiment, the packet monitoring function 204 is performed by the UE 102, the processor 104 and / or the logical channel prioritization 114 in the embodiment. Figure 1 In at least one embodiment, the application 208 is executed by the UE 102, the processor 104 and / or the packet monitoring function 118 in the embodiment. Figure 1 In at least one embodiment, the transmission function 216 is performed by the UE 102, the processor 104 and / or the application 112 in the embodiment. Figure 1 In at least one embodiment, the architecture 200 may be implemented by the UE 102, the processor 104, and the transmission function 116. Figure 1 any of the components described in the Figure 1 Any component in Figure 2 The subject matter described herein is used in conjunction with the present invention.

[0135] Figure 3A Schematic diagram showing a process 300 of wireless data prioritization performed by at least one embodiment. In at least one embodiment, Figure 3A shows a timeline of autonomous updating of the prioritized bit rate based on the queue length when the timer expires, with an offset value θ tIn at least one embodiment, in process 300, at t=1, a timer is started and the monitored queue length is determined to be less than a threshold value minus a hysteresis. In at least one embodiment, in process 300, at t=4, the timer expires and the offset value θ is incremented / decremented accordingly. t Decrement value Δ down In at least one embodiment, in process 300, at t=6, a timer is started and the monitored queue length is determined to be greater than a threshold value minus a hysteresis. In at least one embodiment, in process 300, at t=4, the timer expires and the offset value θ is set. t Incremental value Δ down .

[0136] Figure 3B A schematic diagram illustrating a process 350 for wireless data prioritization performed by at least one embodiment is shown. In at least one embodiment, Figure 3B shows when the timer is stopped and the value θ t A timeline of autonomous updates of prioritized bit rates based on queue lengths while remaining constant. In at least one embodiment, in process 350, at t=1, a timer is started and the monitored queue length is determined to be less than a threshold value minus a hysteresis. In at least one embodiment, in process 350, at t=3, the queue length is determined to be greater than or equal to the threshold value, which results in an offset value θ t was determined to remain unchanged.

[0137] In at least one embodiment, process 300 may be performed by Figure 1 or Figure 2 any of the components described in the Figure 1 or Figure 2 Any component in Figure 3A In at least one embodiment, process 350 may be performed by Figure 1 or Figure 2 any of the components described in the Figure 1 or Figure 2 Any component can be used with Figure 3B The subject matter described herein is used in conjunction with the present invention.

[0138] Figure 4A diagram 400 illustrates a process for wireless data prioritization performed by at least one embodiment. In at least one embodiment, diagram 400 illustrates autonomous updating of a prioritized bit rate, employing both linear decreases and exponential increases. In at least one embodiment, the prioritized bit rate of diagram 400 is a bandwidth allocation provided by a logical channel prioritization system. In at least one embodiment, a triggering event 402 is a result of monitoring one or more packet statistics, and a threshold is met to cause an exponential increase 406 in the bandwidth allocation to the logical channel. In at least one embodiment, diagram 400 illustrates a linear decrease 404 in the bandwidth allocation to the logical channel occurring between triggering events 402.

[0139] In at least one embodiment, diagram 400 may depict Figure 1 、 Figure 2 or Figure 3A-Figure 3B the execution of any of said components, and Figure 1 or Figure 2 Any component can be used with Figure 4 The subject matter described herein is used in conjunction with the present invention.

[0140] Figure 5 A flowchart 500 of a system for performing wireless data prioritization according to at least one embodiment is shown. In at least one embodiment, a UE for performing the flowchart 500 is Figure 1 UE 102. In at least one embodiment, at block 502, the UE causes one or more prioritization parameters to be assigned to a logical channel in response to a transmission request by an application.

[0141] In at least one embodiment, at block 504, a logical channel prioritization system executed by a UE receives grouping information regarding one or more logical channels.

[0142] In at least one embodiment, at block 506, the logical channel prioritization system autonomously adjusts one or more prioritization parameters of the one or more logical channels based on the packet information associated with the one or more logical channels.

[0143] In at least one embodiment, at block 508, one or more transmission functions are performed by the UE using the one or more logical channels having the one or more autonomously adjusted prioritization parameters.

[0144] In at least one embodiment, the prioritization parameters in diagram 500 are Figure 2 In at least one embodiment, the flowchart 500 may be performed by Figure 1 or Figure 2 Any of the components is executed, and Figure 1 or Figure 2 Any component can be connected with Figure 5 The subject matter described herein is used in conjunction with the present invention.

[0145] Figure 6 A flowchart 600 of a system for performing wireless data prioritization according to at least one embodiment is shown. In at least one embodiment, a UE for performing the flowchart 600 is Figure 1 UE 102. In at least one embodiment, at block 602, the UE sets an initial value of the parameter prioritizedBitRate to PBR0.

[0146] In at least one embodiment, at block 604, the UE initializes an offset value Θt=0 at t=0.

[0147] In at least one embodiment, at block 606, at time t, the UE calculates a packet error rate.

[0148] In at least one embodiment, at decision block 608, the UE determines whether the packet error rate is below a threshold.

[0149] In at least one embodiment, if the UE determines that the packet error rate is below a threshold, then at block 610 the UE increments Θt by a value Δup.

[0150] In at least one embodiment, if the UE determines that the packet error rate is below a threshold, then at block 612 the UE decrements Θt by a value Δdown.

[0151] In at least one embodiment, at block 614, the UE updates the parameter prioritizedBitRate to PBR0+Θt.

[0152] In at least one embodiment, the parameter prioritizedBitRate in diagram 600 is Figure 2 In at least one embodiment, the flowchart 600 may be performed by Figure 1 or Figure 2 any of the components described in the Figure 1 or Figure 2 Any component in Figure 6 The subject matter described herein is used in conjunction with the present invention.

[0153] Figure 7 A flowchart 700 of a system for performing wireless data prioritization according to at least one embodiment is shown. In at least one embodiment, a UE for performing the flowchart 700 is Figure 1UE 102. In at least one embodiment, at block 702, a UE performing autonomous updating of prioritized bit rates using reinforcement learning formulates a state set (S) for logical channel priority distribution and an action set (A) for prioritized bit rates.

[0154] In at least one embodiment, at block 704, the UE sets the action probability ε, the learning rate β, the discount factor γ, and initializes the Q value to zero.

[0155] In at least one embodiment, at block 706, the UE sets the current state s according to the current logical channel priority distribution. t .

[0156] In at least one embodiment, at decision block 708, the UE determines whether an RRC reconfiguration of the logical channel priority distribution has been received.

[0157] In at least one embodiment, if the UE affirmatively determines block 708, then at block 710, the UE does not apply the RRC reconfiguration until t+1.

[0158] In at least one embodiment, at block 712, the UE sets the next state s according to the RRC reconfiguration. t+1 .

[0159] In at least one embodiment, if the UE determines negatively in block 708, then at block 714 the UE sets the next state s t+1 Set to current state t .

[0160] In at least one embodiment, at block 716, the UE generates a uniform random value on the interval [0, 1].

[0161] In at least one embodiment, at decision block 718, the UE determines whether the random value is greater than the action probability ε.

[0162] In at least one embodiment, if the UE affirmatively determines block 708, then at block 720, the UE selects to generate a t The prioritized bit rate values ​​for the maximum Q value.

[0163] In at least one embodiment, if the UE determines that the packet error rate is below the threshold, then at block 722 the UE awards R t (s t ,a t ) is calculated as 1 minus the estimated packet error rate.

[0164] In at least one embodiment, at block 724, the UE estimates the best future Q value to be max a∈A Qt (s t+1 ,a).

[0165] In at least one embodiment, at block 726, the UE updates the Q value to (1-β)Q t (s t ,a t )+β(R t (s t ,a t )+γmax a∈A Q t (s t+1 ,a)) and return to block 706.

[0166] In at least one embodiment, if the UE negatively determines block 718, then at block 728, the UE randomly selects a value for the prioritized bit rate.

[0167] In at least one embodiment, the Q value in graph 700 is Figure 2 In at least one embodiment, the flowchart 700 may be performed by Figure 1 or Figure 2 any of the components described in the Figure 1 or Figure 2 Any component in Figure 7 The subject matter described herein is used in conjunction with the present invention.

[0168] Figure 8 An example 800 including a processor and modules is shown in accordance with at least one embodiment. In at least one embodiment, the processor 805 executes one or more processes (e.g., the processes described herein) to execute an inference model, train a neural network model, fine-tune a trained neural network model, perform progressive sparsification, and / or determine a schedule for progressive sparsification. In at least one embodiment, the processor 805 executes one or more processes or uses components (e.g., in conjunction with Figures 1 to 7 components described).

[0169] In at least one embodiment, processor 805 includes one or more processors (e.g., in conjunction with Figures 10 to 50 ). In at least one embodiment, the processor 805 is any suitable processing unit and / or combination of processing units, such as one or more CPUs, GPUs, GPGPUs, PPUs, and / or variants thereof. In at least one embodiment, the processor 805 includes a logical channel prioritization module 810, a transmission module 815, a packet monitoring module 820, and / or a transmission request module 825, which are distributed among multiple processors that communicate via a bus, a network, by writing to a shared memory, and / or any suitable communication process (e.g., the communication process described herein).

[0170] In at least one embodiment, as used in any implementation described herein, unless the context clearly dictates otherwise or clearly to the contrary, a module refers 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 implementation described herein may include, for example, hardwired circuits, programmable circuits, state machine circuits, fixed function circuits, execution unit circuits, and / or firmware that stores instructions executed by programmable circuits, either individually or in any combination. In at least one embodiment, modules may be collectively or individually embodied as circuits that constitute part of a larger system, such as an integrated circuit (IC), a system on a chip (SoC), and the like. In at least one embodiment, a module is combined with any suitable processing unit and / or combination of processing units (e.g., one or more CPUs, GPUs, GPGPUs, PPUs, and / or variants thereof) to perform one or more processes.

[0171] In at least one embodiment, the logical channel prioritization module 810 performs one or more autonomous adjustments to one or more logical channel prioritization parameters. Figure 1 Logical channel priority 114, Figure 2 Logical channel priority sorting 202, Figure 5 Block 506, Figure 6 Block 614 and / or Figure 7 The functions and / or processes of block 726.

[0172] In at least one embodiment, the transmission module 815 performs one or more functions to upload and / or download information to a base station using a radio link. Figure 1 The transfer function 116 and / or Figure 2 The functions and / or processes of the transmission function 216.

[0173] In at least one embodiment, the packet monitoring module 820 performs one or more functions to monitor packet statistics, packet error rates, successful and / or failed transmissions of packets, and queue lengths of packets sent to the base station. Figure 1 The group monitoring function 118 and / or Figure 2 The functions and / or processes of the group monitoring function 204.

[0174] In at least one embodiment, the transmission request module 825 is one or more applications executed by the UE that make requests to the base station to upload and / or download data using a radio link. Figure 1 The functions and / or processes of the application 112 and / or Figure 2 Application 208.

[0175] Figure 9 9 is a block diagram illustrating a driver and / or runtime including one or more libraries for providing one or more application programming interfaces (APIs) according to at least one embodiment. In at least one embodiment, software program 902 is a software module. In at least one embodiment, software program 902 includes one or more software modules. In at least one embodiment, one or more APIs 910 are software instruction sets that, if executed, cause one or more processors to perform one or more computing operations. In at least one embodiment, one or more APIs 910 are distributed or otherwise provided as part of one or more libraries 906, runtime 904, driver 904, and / or any other grouping of software and / or executable code further described herein. In at least one embodiment, one or more APIs 910 perform one or more computing operations in response to a call from software program 902. In at least one embodiment, software program 902 is a collection of software codes, commands, instructions, or other text sequences that direct a computing device to perform one or more computing operations and / or call one or more other instruction sets, such as API 910 or API functions 912, to be executed.

[0176] In at least one embodiment, the API functions 912 include, but are not limited to, functions for verifying whether an object indicated in an image description is depicted in the image, functions for generating a textual description of visual content, functions for accepting natural language prompts to parse, edit, modify, and / or change an image description, functions for identifying whether an object described in a caption is depicted in the image to be described, and functions for generating an evaluation metric of the similarity between an input image to be captioned and a generated caption. In at least one embodiment, the functionality provided by one or more APIs 910 includes software functions 912, such as software functions that can be used to accelerate one or more portions of the software program 902 using one or more parallel processing units (PPUs) (e.g., graphics processing units (GPUs)). In at least one embodiment, the software program is a compiler.

[0177] In at least one embodiment, the API function 912 executes the logical channel prioritization module 810. In at least one embodiment, the API function 912 executes Figure 1 Logical channel priority 114, Figure 2 Logical channel priority sorting 202, Figure 5 Block 506, Figure 6 Block 614 and / or Figure 7 In at least one embodiment, the API function 912 executes the transport module 815. In at least one embodiment, the API function 912 executes Figure 1 The transfer function 116 and / or Figure 2 In at least one embodiment, the API function 912 executes the packet monitoring module 820. In at least one embodiment, the API function 912 executes Figure 1 The group monitoring function 118 and / or Figure 2 In at least one embodiment, the API function 912 executes the transmission request module 825. In at least one embodiment, the API function 912 executes Figure 1 Application 112 and / or Figure 2 The functions and / or processes of the application 208.

[0178] In at least one embodiment, the API 910 is a hardware interface to one or more circuits for performing one or more computing operations. In at least one embodiment, one or more software APIs 910 described herein are implemented as one or more circuits for performing operations in conjunction with Figures 1 to 8 In at least one embodiment, one or more software programs 902 include instructions that, if executed, cause one or more hardware devices and / or circuits to perform operations in conjunction with Figures 1 to 8 One or more techniques further described.

[0179] In at least one embodiment, a software program 902 (e.g., a user-implemented software program) utilizes one or more application programming interfaces (APIs) 910 to perform various computational operations, such as memory reservations, matrix multiplications, arithmetic operations, or any computational operations performed by a parallel processing unit (PPU) (e.g., a graphics processing unit (GPU)), as further described herein. In at least one embodiment, the one or more APIs 910 provide a set of callable functions 912 (referred to herein as APIs, API functions, and / or functions) that each perform one or more computational operations, such as computational operations associated with parallel computing. In at least one embodiment, the one or more APIs 910 provide functions 912 to adjust a description of an image. In at least one embodiment, the one or more APIs 910 provide functions 912 to cause a neural network to perform one or more operations, such as by returning the called function to a processor, where the processor invokes the neural network.

[0180] In at least one embodiment, one or more software programs 902 interact with or otherwise communicate with one or more APIs 910 to perform one or more computing operations using one or more PPUs (e.g., GPUs). In at least one embodiment, the one or more computing operations using the one or more PPUs include at least one or more groups of computing operations that are accelerated by being performed at least in part by the one or more PPUs. In at least one embodiment, the one or more software programs 902 interact with the one or more APIs 910 to facilitate parallel computing using remote or local interfaces.

[0181] In at least one embodiment, an interface is software instructions that, if executed, provide access to one or more functions 912 provided by one or more APIs 910. In at least one embodiment, a software program 902 uses a native interface when a software developer compiles one or more software programs 902 in conjunction with one or more libraries 906 that include or otherwise provide access to the one or more APIs 910. In at least one embodiment, the one or more software programs 902 are statically compiled in conjunction with precompiled libraries 906 or uncompiled source code that include instructions for executing the one or more APIs 910. In at least one embodiment, the one or more software programs 902 are dynamically compiled and linked to the one or more precompiled libraries 906 that include the one or more APIs 910 using a linker.

[0182] In at least one embodiment, a software program 902 uses a remote interface when a software developer executes a software program that utilizes a library 906 including one or more APIs 910 or otherwise communicates with it over a network or other remote communication medium. In at least one embodiment, the one or more libraries 906 including one or more APIs 910 are executed by a remote computing service (e.g., a computing resource service provider). In another embodiment, the one or more libraries 906 including one or more APIs 910 are executed by any other computing host that provides the one or more APIs 910 to the one or more software programs 902.

[0183] In at least one embodiment, a processor executing or using one or more software programs 902 calls, uses, executes, or otherwise implements one or more APIs 910 to allocate and otherwise manage memory to be used by the software programs 902. In at least one embodiment, one or more software programs 902 utilize one or more APIs 910 to allocate and otherwise manage memory to be used by one or more portions of the software programs 902 for acceleration using one or more PPUs (e.g., GPUs or any other accelerators or processors described further herein). These software programs 902 request the neural network to generate a modified bounding box based at least in part on the one or more second bounding boxes.

[0184] In at least one embodiment, API 910 is an API for facilitating parallel computing. In at least one embodiment, API 910 is any other API described further herein. In at least one embodiment, API 910 is provided by a driver and / or runtime 904. In at least one embodiment, API 910 is provided by a CUDA user-mode driver. In at least one embodiment, API 910 is provided by a CUDA runtime. In at least one embodiment, driver 904 is data values ​​and software instructions that, if executed, perform or otherwise facilitate the operation of one or more functions 912 of API 910 during the loading and execution of one or more portions of software program 902. In at least one embodiment, runtime 904 is data values ​​and software instructions that, if executed, perform or otherwise facilitate the operation of one or more functions 912 of API 910 during the execution of software program 902. In at least one embodiment, one or more software programs 902 utilize one or more APIs 910 implemented or otherwise provided by a driver and / or runtime 904 to perform combined arithmetic operations by the one or more software programs 902 during execution by one or more PPUs (e.g., GPUs).

[0185] In at least one embodiment, one or more software programs 902 utilize one or more APIs 910 provided by a driver and / or runtime 904 to perform combined arithmetic operations for one or more PPUs (e.g., GPUs). In at least one embodiment, the one or more APIs 910 provide combined arithmetic operations through the driver and / or runtime 904, as described above. In at least one embodiment, one or more software programs 902 utilize one or more APIs 910 provided by the driver and / or runtime 904 to allocate or otherwise reserve one or more blocks of memory 914 for one or more PPUs (e.g., GPUs). In at least one embodiment, one or more software programs 902 utilize one or more APIs 910 provided by the driver and / or runtime 904 to allocate or otherwise reserve blocks of memory. In at least one embodiment, the one or more APIs 910 are used to perform combined arithmetic operations, as described below in conjunction with Figures 1 to 8 Any of those operations described in .

[0186] To improve the usability of the software program 902 and / or optimize one or more portions of the software program 902 for acceleration by one or more PPUs (e.g., GPUs), in one embodiment, the one or more APIs 910 provide one or more API functions 912 to implement a scheduling system that can be used or utilized by one or more computing devices, as described above and in conjunction with Figures 1 to 8 Further description. In at least one embodiment, block diagram 900 depicts a processor comprising one or more circuits for executing one or more software programs to combine two or more application programming interfaces (APIs) into a single API. In at least one embodiment, block diagram 900 depicts a system comprising one or more processors for executing one or more software programs to combine two or more application programming interfaces (APIs) into a single API.

[0187] Data Center

[0188] Figure 10 An example data center 1000 is shown in which at least one embodiment may be used. In at least one embodiment, data center 1000 includes a data center infrastructure layer 1010, a framework layer 1020, a software layer 1030, and an application layer 1040.

[0189] In at least one embodiment, Figure 10As shown, the data center infrastructure layer 1010 may include a resource coordinator 1012, grouped computing resources 1014, and node computing resources ("node CRs") 1016(1)-1016(N), where "N" represents any integer, positive integer. In at least one embodiment, the node CRs 1016(1)-1016(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 1016(1)-1016(N) may be a server having one or more of the above-mentioned computing resources.

[0190] In at least one embodiment, the grouped computing resources 1014 may include separate groups of node CRs housed in one or more racks (not shown), or 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 1014 may include computing, networking, memory, or storage resources that can 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.

[0191] In at least one embodiment, resource coordinator 1012 may configure or otherwise control one or more nodes CR 1016(1)-1016(N) and / or grouped computing resources 1014. In at least one embodiment, resource coordinator 1012 may comprise a software design infrastructure ("SDI") management entity for data center 1000. In at least one embodiment, resource coordinator may comprise hardware, software, or some combination thereof.

[0192] In at least one embodiment, Figure 10As shown, framework layer 1020 includes a job scheduler 1032, a configuration manager 1034, a resource manager 1036, and a distributed file system 1038. In at least one embodiment, framework layer 1020 may include a framework that supports the software 1032 of software layer 1030 and / or one or more applications 1042 of application layer 1040. In at least one embodiment, software 1032 or applications 1042 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, framework layer 1020 may include, but is not limited to, a free and open source software web application framework, such as Apache Spark™ (hereinafter referred to as "Spark"), which can utilize distributed file system 1038 for large-scale data processing (e.g., "big data"). In at least one embodiment, job scheduler 1032 may include a Spark driver to facilitate scheduling workloads supported by various layers of data center 1000. In at least one embodiment, a configuration manager 1034 can be capable of configuring different layers, such as a software layer 1030 and a framework layer 1020 including Spark and a distributed file system 1038 for supporting large-scale data processing. In at least one embodiment, a resource manager 1036 can manage clustered or grouped computing resources mapped to or allocated to support the distributed file system 1038 and the job scheduler 1032. In at least one embodiment, the clustered or grouped computing resources can include grouped computing resources 1014 on the data center infrastructure layer 1010. In at least one embodiment, the resource manager 1036 can coordinate with the resource coordinator 1012 to manage these mapped or allocated computing resources.

[0193] In at least one embodiment, the software 1032 included in the software layer 1030 may include software used by at least a portion of the node CRs 1016(1)-1016(N), the grouped computing resources 1014, and / or the distributed file system 1038 of the framework layer 1020. 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.

[0194] In at least one embodiment, the one or more applications 1042 included in the application layer 1040 may include one or more types of applications used by at least a portion of the node CRs 1016(1)-1016(N), the grouped computing resources 1014, and / or the distributed file system 1038 of the framework layer 1020. 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.

[0195] In at least one embodiment, any of configuration manager 1034, resource manager 1036, and resource coordinator 1012 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 a data center operator of data center 1000 from making potentially poor configuration decisions and can avoid underutilized and / or poorly performing portions of the data center.

[0196] In at least one embodiment, data center 1000 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 data center 1000. 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 data center 1000.

[0197] In at least one embodiment, data center 1000 can use a CPU, application-specific integrated circuit (ASIC), GPU, 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.

[0198] In at least one embodiment, data center 1000 may be used to implement system 100 (see Figure 1 ), Architecture 200 (see Figure 2 ), Figure 300 (see Figure 3A), Figure 350 (see Figure 3B ), Figure 400 (see Figure 4 ), Flowchart 500 (see Figure 5 ), Flowchart 600 (see Figure 6 ), Flowchart 700 (see Figure 7 ), Example 800 (see Figure 8 ) and / or block diagram 900 (see Figure 9 ). In at least one embodiment, Figure 10 At least a portion of the system depicted in is used to implement a combination Figure 1-9 For example, in at least one embodiment, the system, technique, function, and / or process described herein may be used to implement one or more systems, techniques, functions, and / or processes. Figure 10 At least one component shown or described may be used to enable a UE device to Figure 1-9 One or more techniques, functions and / or processes described in any one of the foregoing may autonomously adjust the priority of information to be transmitted.

[0199] Figure 11A An example of an autonomous vehicle 1100 is shown, according to at least one embodiment. In at least one embodiment, autonomous vehicle 1100 (alternatively referred to herein as "vehicle 1100") 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 1100 can be a semi-tractor-trailer for hauling cargo. In at least one embodiment, vehicle 1100 can be an aircraft, a robotic vehicle, or another type of vehicle.

[0200] Automated driving vehicles may be described according to the levels of automation 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, dated June 15, 2018, Standard No. J3016-201609, dated September 30, 2016, and previous and future versions of this standard). In one or more embodiments, the vehicle 1100 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 1100 may be capable of conditional automation (Level 3), high automation (Level 4), and / or full automation (Level 5), depending on the embodiment.

[0201] In at least one embodiment, the vehicle 1100 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 1100 may include, but is not limited to, a propulsion system 1150, 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 1150 may be connected to a drive train of the vehicle 1100, which may include, but is not limited to, a transmission, to enable propulsion of the vehicle 1100. In at least one embodiment, the propulsion system 1150 may be controlled in response to receiving a signal from a throttle / accelerator 1152.

[0202] In at least one embodiment, when propulsion system 1150 is operating (e.g., when the vehicle is traveling), a steering system 1154 (which may include, but is not limited to, a steering wheel) is used to steer vehicle 1100 (e.g., along a desired path or route). In at least one embodiment, steering system 1154 may receive signals from steering actuator 1156. 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 1146 may be used to operate the vehicle brakes in response to signals received from brake actuator 1148 and / or brake sensors.

[0203] In at least one embodiment, the controller 1136 may include, but is not limited to, one or more system-on-chips ("SoCs") ( Figure 11A) and / or a graphics processing unit (“GPU”) provides signals (e.g., representing commands) to one or more components and / or systems of the vehicle 1100. For example, in at least one embodiment, the controller 1136 can send signals to operate vehicle brakes via a brake actuator 1148, to operate a steering system 1154 via one or more steering actuators 1156, and to operate a propulsion system 1150 via one or more throttles / accelerators 1152. In at least one embodiment, the controller 1136 can include one or more onboard (e.g., integrated) computing devices (e.g., a supercomputer) that processes sensor signals and outputs operational commands (e.g., signals representing commands) to implement autonomous driving and / or assist a driver in driving the vehicle 1100. In at least one embodiment, the one or more controllers 1136 may include a first controller 1136 for autonomous driving functionality, a second controller 1136 for functional safety functionality, a third controller 1136 for artificial intelligence functionality (e.g., computer vision), a fourth controller 1136 for infotainment functionality, a fifth controller 1136 for redundancy in emergency situations, and / or other controllers. In at least one embodiment, a single controller 1136 may handle two or more of the aforementioned functions, two or more controllers 1136 may handle a single function, and / or any combination thereof.

[0204] In at least one embodiment, the one or more controllers 1136 provide signals for controlling one or more components and / or systems of the vehicle 1100 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 1158 (e.g., one or more global positioning system sensors), one or more RADAR sensors 1160, one or more ultrasonic sensors 1162, one or more LIDAR sensors 1164, one or more inertial measurement unit (IMU) sensors 1166 (e.g., one or more accelerometers, one or more gyroscopes, one or more magnetic compasses, one or more magnetometers, etc.), one or more microphones 1196, one or more stereo cameras 1168, one or more wide angle cameras 1170 (e.g., fisheye cameras), one or more infrared cameras 1172, one or more surround cameras 1174 (e.g., 360 degree cameras), long range cameras (e.g., infrared cameras), and / or a combination of these. Figure 11A Not shown), mid-range camera ( Figure 11A), one or more speed sensors 1144 (e.g., for measuring the speed of the vehicle 1100), one or more vibration sensors 1142, one or more steering sensors 1140, one or more brake sensors (e.g., as part of a brake sensor system 1146), and / or other sensor types are received.

[0205] In at least one embodiment, one or more controllers 1136 may receive input (e.g., represented by input data) from a dashboard 1132 of the vehicle 1100 and provide output (e.g., represented by output data, display data, etc.) via a human machine interface ("HMI") display 1134, an audible annunciator, a speaker, and / or other components of the vehicle 1100. In at least one embodiment, the output may include information such as vehicle speed, velocity, time, map data (e.g., high-definition map ( Figure 11A ), location data (e.g., the location of the vehicle 1100, 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 1136, etc. For example, in at least one embodiment, the HMI display 1134 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.).

[0206] In at least one embodiment, the vehicle 1100 further includes a network interface 1124 that can communicate over one or more networks using one or more wireless antennas 1126 and / or one or more modems. For example, in at least one embodiment, the network interface 1124 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 1126 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 and SigFox) to enable communication between objects in the environment (e.g., vehicles, mobile devices).

[0207] In at least one embodiment, vehicle 1100 may be used to implement system 100 (see Figure 1 ), Architecture 200 (see Figure 2 ), Figure 300 (see Figure 3A ), Figure 350 (see Figure 3B ), Figure 400 (see Figure 4 ), Flowchart 500 (see Figure 5 ), Flowchart 600 (see Figure 6 ), Flowchart 700 (see Figure 7 ), Example 800 (see Figure 8 ) and / or block diagram 900 (see Figure 9 ). In at least one embodiment, Figure 11A At least a portion of the system depicted in is used to implement a combination Figure 1-9 For example, in at least one embodiment, the system, technique, function, and / or process described herein may be used to implement one or more systems, techniques, functions, and / or processes. Figure 11A At least one component shown or described may be used to enable a UE device to Figure 1-9 One or more techniques, functions and / or processes described in any one of the foregoing may autonomously adjust the priority of information to be transmitted.

[0208] Figure 11B According to at least one embodiment, Figure 11A 1100. 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 the vehicle 1100.

[0209] 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 1100. In at least one embodiment, the camera may operate at Automotive Safety Integrity Level (“ASIL”) B and / or other ASILs. In at least one embodiment, the camera type may have any image capture rate, such as 60 frames per second (fps), 120 fps, 240 fps, etc., 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 transparent pixel camera, such as a camera having an RCCC, RCCB, and / or RBGC filter array, may be used in an effort to improve light sensitivity.

[0210] 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).

[0211] 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 car (e.g., reflections from the dashboard reflecting in the windshield mirror) that may interfere with the camera's ability to capture image data. 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 car.

[0212] 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 1100 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 1136 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 of the same ADAS functions as LIDAR, including but not limited to emergency braking, pedestrian detection, and collision avoidance. In at least one embodiment, the forward-facing camera can also be used for ADAS functions and systems, including but not limited to lane departure warning ("LDW"), automatic cruise control ("ACC"), and / or other functions (e.g., traffic sign recognition).

[0213] 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 1170 can be used to sense objects entering from the periphery (e.g., pedestrians, people crossing the road, or bicycles). Although Figure 11BOnly one wide-angle camera 1170 is shown in FIG. 1 , however, in other embodiments, any number (including zero) of wide-angle cameras may be present on the vehicle 1100. In at least one embodiment, any number of remote cameras 1198 (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 1198 may also be used for object detection and classification, as well as basic object tracking.

[0214] In at least one embodiment, any number of stereo cameras 1168 may also be included in the forward-facing configuration. In at least one embodiment, one or more stereo cameras 1168 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 vehicle 1100's environment, including distance estimates for all points in the image. In at least one embodiment, one or more stereo cameras 1168 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 1100 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 1168 may be used in addition to those described herein.

[0215] In at least one embodiment, a camera having a field of view of a portion of the environment including the sides of the vehicle 1100 (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 1174 (e.g., Figure 11B Four surround cameras 1174 (shown) can be positioned on the vehicle 1100. In at least one embodiment, the one or more surround cameras 1174 can include, but are not limited to, any number and combination of wide-angle cameras 1170, 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 1100. In at least one embodiment, the vehicle 1100 can use three surround cameras 1174 (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.

[0216] In at least one embodiment, a camera having a field of view that includes a portion of the environment behind the vehicle 1100 (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 1198 and / or one or more mid-range cameras 1176, one or more stereo cameras 1168, one or more infrared cameras 1172, etc.), as described herein.

[0217] In at least one embodiment, vehicle 1100 may be used to implement system 100 (see Figure 1 ), Architecture 200 (see Figure 2 ), Figure 300 (see Figure 3A ), Figure 350 (see Figure 3B ), Figure 400 (see Figure 4 ), Flowchart 500 (see Figure 5 ), Flowchart 600 (see Figure 6 ), Flowchart 700 (see Figure 7 ), Example 800 (see Figure 8 ) and / or block diagram 900 (see Figure 9 ). In at least one embodiment, Figure 11B At least a portion of the system depicted in is used to implement a combination Figure 1-9 For example, in at least one embodiment, the system, technique, function, and / or process described herein may be used to implement one or more systems, techniques, functions, and / or processes. Figure 11B At least one component shown or described may be used to enable a UE device to Figure 1-9 One or more techniques, functions and / or processes described in any one of the foregoing may autonomously adjust the priority of information to be transmitted.

[0218] Figure 11C According to at least one embodiment, Figure 11A A block diagram of an example system architecture for an autonomous vehicle 1100 is provided. In at least one embodiment, Figure 11CEach of one or more components, one or more features, and one or more systems of vehicle 1100 is shown as being connected via bus 1102. In at least one embodiment, bus 1102 may include, but is not limited to, a CAN data interface (alternatively referred to herein as a "CAN bus"). In at least one embodiment, CAN may be a network internal to vehicle 1100 that facilitates control of various features and functions of vehicle 1100, such as brake actuation, acceleration, braking, steering, wipers, and the like. In one embodiment, bus 1102 may be configured with dozens or even hundreds of nodes, each with its own unique identifier (e.g., a CAN ID). In at least one embodiment, bus 1102 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, bus 1102 may be an ASIL B compliant CAN bus.

[0219] 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 1102, 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 1102 may be used to perform different functions and / or may be used for redundancy. For example, a first bus 1102 may be used for collision avoidance functionality, and a second bus 1102 may be used for actuation control. In at least one embodiment, each bus 1102 may communicate with any component of the vehicle 1100, and two or more buses 1102 may communicate with the same component. In at least one embodiment, each of any number of system-on-chips ("SoCs") 1104, each of one or more controllers 1136, and / or each computer within the vehicle may have access to the same input data (e.g., input from sensors in the vehicle 1100) and may be connected to a common bus, such as a CAN bus.

[0220] In at least one embodiment, the vehicle 1100 may include one or more controllers 1136, such as those described herein with respect to Figure 11A In at least one embodiment, the controller 1136 can be used for a variety of functions. In at least one embodiment, the controller 1136 can be coupled to any of the various other components and systems of the vehicle 1100 and can be used to control the vehicle 1100, the artificial intelligence of the vehicle 1100, the infotainment and / or other functions of the vehicle 1100.

[0221] In at least one embodiment, the vehicle 1100 may include any number of SoCs 1104. Each of the SoCs 1104 may include, but is not limited to, a central processing unit ("CPU(s)") 1106, a graphics processing unit ("GPU(s")) 1108, one or more processors 1110, one or more caches 1112, one or more accelerators 1114, one or more data stores 1116, and / or other components and features not shown. In at least one embodiment, the one or more SoCs 1104 may be used to control the vehicle 1100 in various platforms and systems. For example, in at least one embodiment, the one or more SoCs 1104 may be combined in a system (e.g., a system of the vehicle 1100) with a high-definition ("HD") map 1122 that may be downloaded from one or more servers (e.g., a system of the vehicle 1100) via a network interface 1124. Figure 11C ) to obtain map refreshes and / or updates.

[0222] In at least one embodiment, one or more CPUs 1106 may include a CPU cluster or CPU complex (alternatively referred to herein as a "CCPLEX"). In at least one embodiment, one or more CPUs 1106 may include multiple cores and / or a second level ("L2") cache. For example, in at least one embodiment, one or more CPUs 1106 may include eight cores in a mutually coupled multiprocessor configuration. In at least one embodiment, one or more CPUs 1106 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 1106 (e.g., CCPLEX) may be configured to support simultaneous cluster operations such that any combination of clusters of one or more CPUs 1106 may be active at any given time.

[0223] In at least one embodiment, one or more CPUs 1106 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 conserve 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 1106 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 compute unit or arithmetic unit.

[0224] In at least one embodiment, one or more GPUs 1108 may include an integrated GPU (or alternatively referred to herein as an "iGPU"). In at least one embodiment, one or more GPUs 1108 may be programmable and may be efficient for parallel workloads. In at least one embodiment, one or more GPUs 1108 may use an enhanced tensor instruction set. In one embodiment, one or more GPUs 1108 may include one or more streaming microprocessors, wherein each streaming microprocessor may include a level 1 ("L1") cache (e.g., an L1 cache having at least 96KB of storage capacity), and two or more streaming microprocessors may share an L2 cache (e.g., an L2 cache having 512KB of storage capacity). In at least one embodiment, one or more GPUs 1108 may include at least eight streaming microprocessors. In at least one embodiment, one or more GPUs 1108 may use a computing application programming interface (API). In at least one embodiment, one or more GPUs 1108 may use one or more parallel computing platforms and / or programming models (e.g., NVIDIA's CUDA).

[0225] In at least one embodiment, one or more GPUs 1108 can be power-optimized for optimal performance in automotive and embedded use cases. For example, in one embodiment, one or more GPUs 1108 can be fabricated on fin field-effect transistors (“FinFETs”). In at least one embodiment, each streaming microprocessor can include multiple mixed-precision processing cores partitioned into multiple blocks. For example, but not limited to, 64 PF32 cores and 32 PF64 cores can be partitioned into four processing blocks. In at least one embodiment, each processing block can be allocated 16 FP32 cores, 8 FP64 cores, 16 INT32 cores, two mixed-precision NVIDIA Tensor Cores for deep learning matrix arithmetic, a level-0 (“L0”) instruction cache, a warp scheduler, a dispatch unit, and / or a 64KB register file. In at least one embodiment, the streaming microprocessor can include independent parallel integer and floating-point datapaths to provide efficient execution of workloads that mix compute and addressing operations. In at least one embodiment, the streaming microprocessor can 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.

[0226] In at least one embodiment, one or more GPUs 1108 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.

[0227] In at least one embodiment, one or more GPUs 1108 may include unified memory technology. In at least one embodiment, address translation services ("ATS") support may be used to allow one or more GPUs 1108 to directly access one or more CPU 1106 page tables. In at least one embodiment, when one or more GPU 1108 memory management units ("MMUs") experience a miss, an address translation request may be sent to one or more CPUs 1106. In response, in at least one embodiment, one or more CPUs 1106 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 1108. 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 1106 and one or more GPUs 1108, thereby simplifying programming of one or more GPUs 1108 and porting applications to one or more GPUs 1108.

[0228] In at least one embodiment, one or more GPUs 1108 may include any number of access counters that can track the frequency with which one or more GPUs 1108 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.

[0229] In at least one embodiment, one or more SoCs 1104 may include any number of caches 1112, including those described herein. For example, in at least one embodiment, one or more caches 1112 may include a level 3 ("L3") cache available to one or more CPUs 1106 and one or more GPUs 1108 (e.g., connected to CPUs 1106 and GPUs 1108). In at least one embodiment, one or more caches 1112 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 or more, depending on the embodiment, although smaller cache sizes may be used.

[0230] In at least one embodiment, one or more SoCs 1104 may include one or more accelerators 1114 (e.g., hardware accelerators, software accelerators, or a combination thereof). In at least one embodiment, one or more SoCs 1104 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 computations. In at least one embodiment, the hardware acceleration cluster may be used to supplement one or more GPUs 1108 and offload some tasks of one or more GPUs 1108 (e.g., freeing up more cycles of one or more GPUs 1108 to perform other tasks). In at least one embodiment, one or more accelerators 1114 may be used for target workloads that are sufficiently stable to withstand acceleration testing (e.g., perception, convolutional neural networks (“CNNs”), recurrent neural networks (“RNNs”), etc.). In at least one embodiment, the CNNs may include region-based or region-based convolutional neural networks (“RCNNs”) and fast RCNNs (e.g., as used for object detection) or other types of CNNs.

[0231] In at least one embodiment, one or more accelerators 1114 (e.g., a hardware acceleration cluster) may include one or more deep learning accelerators ("DLAs"). One or more DLAs may include, but are not limited to, one or more Tensor Processing Units ("TPUs"), which may be configured to provide an additional 10 trillion operations per second for deep learning applications and reasoning. 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.). One or more DLAs may be further optimized for a specific set of neural network types and floating-point operations and reasoning. 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, INT8, INT16, and FP16 data types for features and weights, as well as post-processor functions. In at least one embodiment, one or more DLAs can 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 896; 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.

[0232] In at least one embodiment, a DLA can perform any function of one or more GPUs 1108, 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 1108. 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 1108 and / or other one or more accelerators 1114.

[0233] In at least one embodiment, one or more accelerators 1114 (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") 1138, 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.

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

[0235] In at least one embodiment, the DMA can enable components of the PVA to access system memory independently of one or more CPUs 1106. 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.

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

[0237] In at least one embodiment, each vector processor may include an instruction cache and may be coupled to a 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 the same computer vision algorithm, but 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 the same image, or even execute different algorithms on sequenced images or portions of images. In at least one embodiment, any number of PVAs may be included in the 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.

[0238] In at least one embodiment, one or more accelerators 1114 (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 1114. 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).

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

[0240] In at least one embodiment, one or more SoCs 1104 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.

[0241] In at least one embodiment, one or more accelerators 1114 (e.g., a hardware acceleration cluster) have broad uses for autonomous driving. In at least one embodiment, the PVA may 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 algorithmic domains that require predictable processing. In other words, the PVA excels at 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 1100, may be designed to run classic computer vision algorithms because they can be efficient at object detection and integer math.

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

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

[0244] 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 belief for each object detection. In at least one embodiment, the beliefs can be expressed or interpreted as probabilities, or as providing a relative "weight" of each detection relative to other detections. In at least one embodiment, the beliefs enable 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 beliefs 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 belief values. 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 1166 associated with vehicle 1100 heading, distance, 3D position estimates of objects obtained from the neural network and / or other sensors (e.g., one or more LIDAR sensors 1164 or one or more RADAR sensors 1160), etc.

[0245] In at least one embodiment, one or more SoCs 1104 (e.g., a hardware acceleration cluster) may include one or more data stores 1116 (e.g., memory). In at least one embodiment, one or more data stores 1116 may be on-chip memory of one or more SoCs 1104 that may store neural networks to be executed on one or more GPUs 1108 and / or DLAs. In at least one embodiment, one or more data stores 1116 may have a capacity large enough to store multiple instances of a neural network for redundancy and safety. In at least one embodiment, one or more data stores 1112 may include an L2 or L3 cache.

[0246] In at least one embodiment, one or more SoCs 1104 may include any number of processors 1110 (e.g., embedded processors). In at least one embodiment, the processors 1110 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 1104 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, manage one or more SoCs 1104 thermal and temperature sensors, and / or manage one or more SoCs 1104 power states. 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 1104 may use the ring oscillator to detect the temperature of one or more CPUs 1106, one or more GPUs 1108, and / or one or more accelerators 1114. 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 1104 into a lower power consumption state and / or place the vehicle 1100 into a driver's safe parking pattern (e.g., bringing the vehicle 1100 to a safe stop).

[0247] In at least one embodiment, one or more processors 1110 may further include a set of embedded processors that can be used as an audio processing engine. In at least one embodiment, the audio processing engine 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.

[0248] In at least one embodiment, one or more processors 1110 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.

[0249] In at least one embodiment, one or more processors 1110 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 1110 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 1110 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.

[0250] In at least one embodiment, one or more processors 1110 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 produce the final video, thereby generating 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 1170, one or more surround cameras 1174, 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 1104, 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 functions are available to the driver when the vehicle is operating in autonomous mode, but are otherwise disabled.

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

[0252] 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, and does not require one or more GPUs 1108 to continuously render new surfaces. In at least one embodiment, when one or more GPUs 1108 are powered and actively performing 3D rendering, the video image compositor can be used to offload one or more GPUs 1108 to improve performance and responsiveness.

[0253] In at least one embodiment, one or more of the SoCs 1104 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 1104 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.

[0254] In at least one embodiment, one or more of the SoCs 1104 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. The one or more SoCs 1104 may be configured to process data from cameras (e.g., via Gigabit multimedia serial links and Ethernet connections), sensors (e.g., one or more LIDAR sensors 1164, one or more RADAR sensors 1160, etc., which may be connected via Ethernet), data from the bus 1102 (e.g., vehicle 1100 speed, steering wheel position, etc.), data from one or more GNSS sensors 1158 (e.g., connected via Ethernet bus or CAN bus), etc. In at least one embodiment, one or more of the SoCs 1104 may further include dedicated high-performance mass storage controllers, which may include their own DMA engines and may be used to offload the one or more CPUs 1106 from routine data management tasks.

[0255] In at least one embodiment, one or more SoCs 1104 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 1104 can be faster, more reliable, and even more energy and space efficient than conventional systems. For example, in at least one embodiment, one or more accelerators 1114, when combined with one or more CPUs 1106, one or more GPUs 1108, and one or more data storage devices 1116, can provide a fast and efficient platform for level 3-5 autonomous vehicles.

[0256] 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., the C programming language) 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.

[0257] The embodiments described herein allow for the simultaneous and / or sequential execution of multiple neural networks and allow the results to be combined 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 1120) may include text and word recognition, 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 symbols and pass this semantic understanding to a path planning module running on the CPU Complex.

[0258] 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 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 1108.

[0259] 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 1100. 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 1104 provide protection against theft and / or carjacking.

[0260] In at least one embodiment, a CNN for emergency vehicle detection and identification can use data from microphone 1196 to detect and identify emergency vehicle sirens. In at least one embodiment, one or more SoCs 1104 use the 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 1158. 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 1162 to execute emergency vehicle safety routines, slow the vehicle, pull over, stop the vehicle, and / or idle the vehicle until the emergency vehicle passes.

[0261] In at least one embodiment, the vehicle 1100 may include one or more CPUs 1118 (e.g., one or more discrete CPUs or one or more dCPUs) that may be coupled to the one or more SoCs 1104 via a high-speed interconnect (e.g., PCIe). In at least one embodiment, the one or more CPUs 1118 may include an X86 processor, for example, and the one or more CPUs 1118 may be used to perform any of a variety of functions, including, for example, arbitrating potential inconsistent results between ADAS sensors and the one or more SoCs 1104, and / or monitoring the status and health of one or more controllers 1136 and / or an information system on a chip ("information SoC") 1130.

[0262] In at least one embodiment, the vehicle 1100 may include one or more GPUs 1120 (e.g., one or more discrete GPUs or one or more dGPUs) that may be coupled to the one or more SoCs 1104 via a high-speed interconnect (e.g., NVIDIA's NVLINK). In at least one embodiment, the one or more GPUs 1120 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 1100.

[0263] In at least one embodiment, vehicle 1100 may further include a network interface 1124, which may include, but is not limited to, one or more wireless antennas 1126 (e.g., one or more wireless antennas 1126 for different communication protocols, such as a cellular antenna, a Bluetooth antenna, etc.). In at least one embodiment, network interface 1124 may be used to enable wireless connectivity with other vehicles and / or computing devices (e.g., a passenger's client device) via the internet with a cloud (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 vehicle 1100 and the other vehicle, and / or an indirect link may be established (e.g., via a network and 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 vehicle 1100 with information about vehicles in its vicinity (e.g., vehicles in front of, to the sides of, and / or behind vehicle 1100). In at least one embodiment, this functionality may be part of the cooperative adaptive cruise control functionality of vehicle 1100.

[0264] In at least one embodiment, the network interface 1124 may include a SoC that provides modulation and demodulation functionality and enables one or more controllers 1136 to communicate over a wireless network. In at least one embodiment, the network interface 1124 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 well-known processes 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.

[0265] In at least one embodiment, the vehicle 1100 may further include one or more data stores 1128, which may include, but are not limited to, off-chip (e.g., one or more SoCs 1104) storage. In at least one embodiment, the one or more data stores 1128 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.

[0266] In at least one embodiment, the vehicle 1100 may further include one or more GNSS sensors 1158 (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 1158 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.

[0267] In at least one embodiment, the vehicle 1100 may further include one or more RADAR sensors 1160. One or more RADAR sensors 1160 may be used by the vehicle 1100 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. One or more RADAR sensors 1160 may use the CAN bus and / or bus 1102 (e.g., to transmit data generated by one or more RADAR sensors 1160) 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 1160 may be suitable for front, rear, and side RADAR use. In at least one embodiment, one or more RADAR sensors 1160 are pulse Doppler RADAR sensors.

[0268] In at least one embodiment, one or more RADAR sensors 1160 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). One or more RADAR sensors 1160 can help distinguish between static and moving objects and can be used by the ADAS system 1138 for emergency brake assistance and forward collision warning. In at least one embodiment, the one or more sensors 1160 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, having six antennas, with the central four antennas, can create a focused beam pattern designed to record the surroundings of the vehicle 1100 at higher speeds with minimal interference from traffic in adjacent lanes. In at least one embodiment, the additional two antennas can extend the field of view, allowing for quick detection of vehicles entering or leaving the vehicle's 1100 lane.

[0269] In at least one embodiment, as an example, a 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, a short-range RADAR system may include, but is not limited to, any number of RADAR sensors 1160 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 of the vehicle and nearby blind spots. In at least one embodiment, the short-range RADAR system can be used in the ADAS system 1138 for blind spot detection and / or lane change assistance.

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

[0271] In at least one embodiment, the vehicle 1100 can include one or more LIDAR sensors 1164. The one or more LIDAR sensors 1164 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 1164 can be functional safety level ASIL B. In at least one embodiment, the vehicle 1100 can include multiple (e.g., two, four, six, etc.) LIDAR sensors 1164 that can use Ethernet (e.g., provide data to a Gigabit Ethernet switch).

[0272] In at least one embodiment, one or more LIDAR sensors 1164 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 1164 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 1164 may be used. In such an embodiment, one or more LIDAR sensors 1164 may be implemented as small devices embedded in the front, rear, sides, and / or corners of the vehicle 1100. In at least one embodiment, one or more LIDAR sensors 1164 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 a range of 200 meters. In at least one embodiment, the forward-facing one or more LIDAR sensors 1164 may be configured for a horizontal field of view between 45 and 135 degrees.

[0273] In at least one embodiment, LIDAR technology (such as 3D flash LIDAR) may also be used. 3D flash LIDAR uses a laser flash as a transmission source to illuminate approximately 200 meters around vehicle 1100. 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 1100 to the object. In at least one embodiment, flash LIDAR can enable the generation of a highly accurate and distortion-free image 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 1100. 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 in the form of a 3D range point cloud and co-registered intensity data.

[0274] In at least one embodiment, the vehicle may further include one or more IMU sensors 1166. In at least one embodiment, the one or more IMU sensors 1166 may be located at the center of the rear axle of the vehicle 1100. In at least one embodiment, the one or more IMU sensors 1166 may include, for example, but not limited to, one or more accelerometers, one or more magnetometers, one or more gyroscopes, one or more magnetic compasses, and / or other sensor types. In at least one embodiment, for example, in a six-axis application, the one or more IMU sensors 1166 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 1166 may include, but not limited to, accelerometers, gyroscopes, and magnetometers.

[0275] In at least one embodiment, the one or more IMU sensors 1166 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 advanced Kalman filtering algorithms to provide estimates of position, velocity, and attitude; in at least one embodiment, the one or more IMU sensors 1166 can enable the vehicle 1100 to estimate heading without input from a magnetic sensor by directly observing and correlating velocity changes from GPS to the one or more IMU sensors 1166. In at least one embodiment, the one or more IMU sensors 1166 and the one or more GNSS sensors 1158 can be combined in a single integrated unit.

[0276] In at least one embodiment, the vehicle 1100 can include one or more microphones 1196 positioned within and / or around the vehicle 1100. In at least one embodiment, the one or more microphones 1196 can be used for emergency vehicle detection and identification, among other things.

[0277] In at least one embodiment, the vehicle 1100 may further include any number of camera types, including one or more stereo cameras 1168, one or more wide angle cameras 1170, one or more infrared cameras 1172, one or more surround cameras 1174, one or more long range cameras 1198, one or more mid range cameras 1176, 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 1100. In at least one embodiment, the type of camera used depends on the vehicle 1100. In at least one embodiment, any combination of camera types may be used to provide the necessary coverage around the vehicle 1100. 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 1100 may include six cameras, seven cameras, ten cameras, twelve cameras, or another 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. In at least one embodiment, the present disclosure previously referred to herein may provide a plurality of cameras. Figure 11A and Figure 11B Each camera can be described in more detail.

[0278] In at least one embodiment, the vehicle 1100 may further include one or more vibration sensors 1142. In at least one embodiment, the one or more vibration sensors 1142 may measure vibrations of a component (e.g., an axle) of the vehicle 1100. For example, in at least one embodiment, changes in vibration may indicate changes in the road surface. In at least one embodiment, when two or more vibration sensors 1142 are used, the difference between the vibrations may 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).

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

[0280] In at least one embodiment, the ACC system may utilize one or more RADAR sensors 1160, one or more LIDAR sensors 1164, and / or any number of cameras. In at least one embodiment, the ACC system may include a longitudinal ACC system and / or a lateral ACC system. In at least one embodiment, the longitudinal ACC system monitors and controls the distance to the vehicle immediately ahead of the vehicle 1100 and automatically adjusts the speed of the vehicle 1100 to maintain a safe distance from the vehicle ahead. In at least one embodiment, the lateral ACC system performs distance keeping and recommends that the vehicle 1100 change lanes when necessary. In at least one embodiment, lateral ACC is associated with other ADAS applications, such as LC and CW.

[0281] 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 1124 and / or one or more wireless antennas 1126. In at least one embodiment, the direct link may be provided by a vehicle-to-vehicle ("V2V") communication link, while the indirect link may be provided by an infrastructure-to-vehicle ("I2V") communication link. Typically, the V2V communication concept provides information about the vehicle immediately ahead (e.g., the vehicle immediately ahead of vehicle 1100 and in the same lane as it), while the I2V communication concept provides information about traffic further ahead. In at least one embodiment, the CACC system may include one or both of the I2V and V2V information sources. In at least one embodiment, given information about vehicles ahead of vehicle 1100, the CACC system may be more reliable and have the potential to improve the smoothness of traffic flow and reduce road congestion.

[0282] 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 1160, which are coupled to a dedicated processor, DSP, FPGA, and / or ASIC, which is electrically coupled to driver feedback, such as a display, speaker, and / or vibration 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.

[0283] 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 1160 coupled to a dedicated processor, DSP, FPGA, and / or ASIC. In at least one embodiment, when the AEB system detects a hazard, the AEB system 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.

[0284] 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 vehicle 1100 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 driver feedback such as a display, speaker, and / or vibration assembly. In at least one embodiment, a LKA system is a variation of the LDW system. If vehicle 1100 begins to leave its lane, the LKA system provides steering input or braking to correct vehicle 1100.

[0285] 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 1160 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.

[0286] 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 1100 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 1160 coupled to a dedicated processor, DSP, FPGA, and / or ASIC, which is electrically coupled to driver feedback such as a display, speaker, and / or vibration component.

[0287] 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 1100 itself decides whether to follow the results of the primary or secondary computer (e.g., the first controller 1136 or the second controller 1136). For example, in at least one embodiment, the ADAS system 1138 can be a backup and / or secondary 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 1138 can be provided to a supervisory MCU. In at least one embodiment, if the outputs from the primary and secondary computers conflict, the supervisory MCU determines how to reconcile the conflict to ensure safe operation.

[0288] In at least one embodiment, the primary computer can be configured to provide a belief score to the supervisory MCU to indicate the primary computer's belief in the selected outcome. In at least one embodiment, if the belief 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, in the event that the belief score does not meet the threshold, and in the event that the primary computer and the secondary computer indicate different outcomes (e.g., a conflict), the supervisory MCU can arbitrate between the computers to determine the appropriate outcome.

[0289] In at least one embodiment, the supervisory MCU can be configured to run a neural network that is trained and configured to determine, based at least in part on outputs from the primary and secondary computers, conditions under which the secondary computer provides a false alarm. 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 1104.

[0290] In at least one embodiment, the ADAS system 1138 may include an auxiliary computer that uses traditional computer vision rules to perform ADAS functions. 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 bug in the software running on the main computer, and a different software code running on the auxiliary computer provides the same 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 did not cause a significant error.

[0291] In at least one embodiment, the output of the ADAS system 1138 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 1138 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.

[0292] In at least one embodiment, the vehicle 1100 may further include an infotainment SoC 1130 (e.g., an in-vehicle infotainment system (IVI)). Although shown and described as an SoC, in at least one embodiment, the infotainment system 1130 may not be a SoC and may include, but is not limited to, two or more discrete components. In at least one embodiment, the infotainment SoC 1130 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 1100. For example, the infotainment SoC 1130 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 1134, 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 1130 may be further configured to provide information (e.g., visual and / or auditory) to a user of the vehicle, such as information from an ADAS system 1138, 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.

[0293] In at least one embodiment, the infotainment SoC 1130 can include any number and type of GPU functionality. In at least one embodiment, the infotainment SoC 1130 can communicate with other devices, systems, and / or components of the vehicle 1100 via a bus 1102 (e.g., a CAN bus, Ethernet, etc.). In at least one embodiment, the infotainment SoC 1130 can be coupled to a supervisory MCU so that the infotainment system's GPU can perform some autonomous driving functions in the event of a failure of the main controller 1136 (e.g., the vehicle's 1100 main computer and / or backup computer). In at least one embodiment, the infotainment SoC 1130 can cause the vehicle 1100 to enter a driver-to-safety stop mode, as described herein.

[0294] In at least one embodiment, the vehicle 1100 may further include an instrument panel 1132 (e.g., a digital instrument panel, an electronic instrument panel, a digital instrument panel, etc.). In at least one embodiment, the instrument panel 1132 may include, but is not limited to, a controller and / or a supercomputer (e.g., a discrete controller or a supercomputer). In at least one embodiment, the instrument panel 1132 may include, but is not limited to, any number and combination of a set of instruments, such as a speedometer, fuel level, oil pressure, a tachometer, an odometer, a turn indicator, a gear position indicator, one or more seat belt warning lights, one or more parking brake warning lights, one or more engine check 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 1130 and the instrument panel 1132. In at least one embodiment, the instrument panel 1132 may be included as part of the infotainment SoC 1130, or vice versa.

[0295] In at least one embodiment, vehicle 1100 may be used to implement system 100 (see Figure 1 ), Architecture 200 (see Figure 2 ), Figure 300 (see Figure 3A ), Figure 350 (see Figure 3B ), Figure 400 (see Figure 4 ), Flowchart 500 (see Figure 5 ), Flowchart 600 (see Figure 6 ), Flowchart 700 (see Figure 7 ), Example 800 (see Figure 8 ) and / or block diagram 900 (see Figure 9 ). In at least one embodiment, Figure 11C At least a portion of the system depicted in is used to implement a combination Figure 1-9 For example, in at least one embodiment, the system, technique, function, and / or process described herein may be used to implement one or more systems, techniques, functions, and / or processes. Figure 11C At least one component shown or described may be used to enable a UE device to Figure 1-9 One or more techniques, functions and / or processes described in any one of the foregoing may autonomously adjust the priority of information to be transmitted.

[0296] Figure 11D In accordance with at least one embodiment, a cloud-based server and Figure 11A 180. FIGURE 18 illustrates a diagram of a system 1177 for communicating between autonomous vehicles 1100. In at least one embodiment, system 1177 may include, but is not limited to, one or more servers 1178, one or more networks 1190, and any number and type of vehicles, including vehicle 1100. One or more servers 1178 may include, but is not limited to, multiple GPUs 1184(A)-1184(H) (collectively referred to herein as GPUs 1184), PCIe switches 1182(A)-1182(H) (collectively referred to herein as PCIe switches 1182), and / or CPUs 1180(A)-1180(B) (collectively referred to herein as CPUs 1180). GPUs 1184, CPUs 1180, and PCIe switches 1182 may be interconnected with high-speed connections, such as, but not limited to, NVLink interface 1188 developed by NVIDIA and / or PCIe connections 1186. The GPUs 1184 are connected via NVLink and / or NVSwitch SoCs, and the GPUs 1184 and PCIe switches 1182 are connected via a PCIe interconnect. In at least one embodiment, although eight GPUs 1184, two CPUs 1180, and four PCIe switches 1182 are shown, this is not intended to be limiting. In at least one embodiment, each of the one or more servers 1178 may include, but is not limited to, any number of GPUs 1184, CPUs 1180, and / or PCIe switches 1182 in any combination. For example, in at least one embodiment, one or more servers 1178 may each include eight, sixteen, thirty-two, and / or more GPUs 1184.

[0297] In at least one embodiment, one or more servers 1178 may receive image data representing an image from a vehicle via one or more networks 1190 that depicts unexpected or altered road conditions, such as recently begun road construction. In at least one embodiment, one or more servers 1178 may transmit a neural network 1192, an updated neural network 1192, and / or map information 1194, including, but not limited to, information regarding traffic and road conditions, to the vehicle via one or more networks 1190. In at least one embodiment, updates to the map information 1194 may include, but not limited to, updates to the HD map 1122, such as information regarding construction sites, potholes, service roads, flooding, and / or other obstacles. In at least one embodiment, the neural network 1192, the updated neural network 1192, and / or the map information 1194 may be generated by new training and / or experience represented by 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 1178 and / or other servers).

[0298] In at least one embodiment, one or more servers 1178 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 1190, and / or the machine learning model can be used by one or more servers 1178 to remotely monitor the vehicle.

[0299] In at least one embodiment, one or more servers 1178 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 1178 can include a deep learning supercomputer and / or a dedicated AI computer powered by one or more GPUs 1184, such as the DGX and DGX Station machines developed by NVIDIA. However, in at least one embodiment, one or more servers 1178 can include the deep learning infrastructure of a data center using CPU power.

[0300] In at least one embodiment, the deep learning infrastructure of one or more servers 1178 may be capable of fast, real-time inference and may use this capability to assess and verify the health of the processors, software, and / or related hardware in the vehicle 1100. For example, in at least one embodiment, the deep learning infrastructure may receive periodic updates from the vehicle 1100, such as an image sequence and / or objects that the vehicle 1100 has located within 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 1100, and if the results do not match and the deep learning infrastructure concludes that the AI ​​in the vehicle 1100 is malfunctioning, the one or more servers 1178 may send a signal to the vehicle 1100 to instruct the vehicle's 1100 fail-safe computer to take control, notify passengers, and complete a safe parking maneuver.

[0301] In at least one embodiment, one or more servers 1178 may include one or more GPUs 1184 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.

[0302] Computer system

[0303] Figure 12 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 1200 formed with a processor, 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 1200 may include, but is not limited to, components such as a processor 1202, whose execution units include logic to execute algorithms for processing data. In at least one embodiment, the computer system 1200 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 1200 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.

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

[0305] In at least one embodiment, the computer system 1200 may include, but is not limited to, a processor 1202, which may include, but is not limited to, one or more execution units 1208 to perform machine learning model training and / or inference according to the techniques described herein. In at least one embodiment, the system 1200 is a single-processor desktop or server system, but in another embodiment, the system 1200 may be a multi-processor system. In at least one embodiment, the processor 1202 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 1202 may be coupled to a processor bus 1210, which may transmit data signals between the processor 1202 and other components in the computer system 1200.

[0306] In at least one embodiment, processor 1202 may include, but is not limited to, a level 1 ("L1") internal cache memory ("cache") 1204. In at least one embodiment, processor 1202 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 1202. 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 1206 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.

[0307] In at least one embodiment, an execution unit 1208, including but not limited to logic for performing integer and floating point operations, is also located in the processor 1202. In at least one embodiment, the processor 1202 may also include a microcode ("ucode") read-only memory ("ROM") for storing microcode for certain macroinstructions. In at least one embodiment, the execution unit 1208 may include logic for processing a packed instruction set 1209. In at least one embodiment, by including the packed instruction set 1209 in the instruction set of the general-purpose processor, and the associated circuitry to execute the instructions, operations used by many multimedia applications may be performed using packed data in the general-purpose processor 1202. 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.

[0308] In at least one embodiment, execution unit 1208 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 1200 may include, but is not limited to, memory 1220. In at least one embodiment, memory 1220 may be implemented as a dynamic random access memory ("DRAM") device, a static random access memory ("SRAM") device, a flash memory device, or other storage device. In at least one embodiment, memory 1220 may store instructions 1219 and / or data 1221 represented by data signals that may be executed by processor 1202.

[0309] In at least one embodiment, the system logic chip can be coupled to the processor bus 1210 and the memory 1220. In at least one embodiment, the system logic chip can include, but is not limited to, a memory controller hub ("MCH") 1216, and the processor 1202 can communicate with the MCH 1216 via the processor bus 1210. In at least one embodiment, the MCH 1216 can provide a high-bandwidth memory path 1218 to the memory 1220 for instruction and data storage, as well as for storage of graphics commands, data, and textures. In at least one embodiment, the MCH 1216 can initiate data signals between the processor 1202, the memory 1220, and other components in the computer system 1200, and bridge data signals between the processor bus 1210, the memory 1220, and the system I / O 1222. 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 1216 may be coupled to the memory 1220 via a high-bandwidth memory path 1218 , and the graphics / video card 1212 may be coupled to the MCH 1216 via an Accelerated Graphics Port (“AGP”) interconnect 1214 .

[0310] In at least one embodiment, the computer system 1200 may use system I / O 1222, which is a proprietary hub interface bus, to couple the MCH 1216 to an I / O controller hub ("ICH") 1230. In at least one embodiment, the ICH 1230 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 1220, chipset, and processor 1202. Examples may include, but are not limited to, an audio controller 1229, a firmware hub ("Flash BIOS") 1228, a wireless transceiver 1226, a data store 1224, a traditional I / O controller 1223 including a user input and keyboard interface, a serial expansion port 1227 (e.g., a Universal Serial Bus (USB)), and a network controller 1234. In at least one embodiment, the data store 1224 may include a hard drive, a floppy disk drive, a CD-ROM device, a flash memory device, or other mass storage device.

[0311] In at least one embodiment, Figure 12 The system is shown as comprising interconnected hardware devices or "chips", while in other embodiments, Figure 12 A system on a chip (SoC) may be shown. In at least one embodiment, Figure 12The devices shown in can be interconnected with a proprietary interconnect, a standardized interconnect (e.g., PCIe), or some combination thereof. In at least one embodiment, one or more components of system 1200 are interconnected using a Compute Express Link (CXL) interconnect.

[0312] In at least one embodiment, system 1200 may be used to implement system 100 (see Figure 1 ), Architecture 200 (see Figure 2 ), Figure 300 (see Figure 3A ), Figure 350 (see Figure 3B ), Figure 400 (see Figure 4 ), Flowchart 500 (see Figure 5 ), Flowchart 600 (see Figure 6 ), Flowchart 700 (see Figure 7 ), Example 800 (see Figure 8 ) and / or block diagram 900 (see Figure 9 ). In at least one embodiment, Figure 12 At least a portion of the system depicted in is used to implement a combination Figure 1-9 For example, in at least one embodiment, the system, technique, function, and / or process described herein may be used to implement one or more systems, techniques, functions, and / or processes. Figure 12 At least one component shown or described may be used to enable a UE device to Figure 1-9 One or more techniques, functions and / or processes described in any one of the foregoing may autonomously adjust the priority of information to be transmitted.

[0313] Figure 13 1 is a block diagram illustrating an electronic device 1300 for utilizing a processor 1310 in accordance with at least one embodiment. In at least one embodiment, the electronic device 1300 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.

[0314] In at least one embodiment, system 1300 may include, but is not limited to, a processor 1310 communicatively coupled to any suitable number or kind of components, peripherals, modules, or devices. In at least one embodiment, processor 1310 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 13shows a system comprising interconnected hardware devices or "chips", while in other embodiments, Figure 13 An exemplary system on a chip (SoC) may be shown.

[0315] In at least one embodiment, Figure 13 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 13 One or more components of the system are interconnected using Compute Express Link (CXL) interconnect lines.

[0316] In at least one embodiment, Figure 13 It may include a display 1324, a touch screen 1325, a touchpad 1330, a near field communication unit (“NFC”) 1345, a sensor hub 1340, a thermal sensor 1339, a fast chipset (“EC”) 1335, a trusted platform module (“TPM”) 1338, BIOS / firmware / flash memory (“BIOS, FW Flash”) 1322, a DSP 1360, a drive “SSD or HDD” 1320 (e.g., a solid state disk (“SSD”) or a hard disk drive (“HDD”)), a wireless local area network unit (“WLAN”) 1350, a Bluetooth unit 1352, a wireless wide area network unit (“WWAN”) 1356, a global positioning system (GPS) 1355, a camera (“USB 3.0 camera”) 1354 (e.g., a USB 3.0 camera), or a low power double data rate (“LPDDR”) memory unit (“LPDDR3”) 1315 implemented with, for example, the LPDDR3 standard. These components may each be implemented in any suitable manner.

[0317] In at least one embodiment, other components may be communicatively coupled to processor 1310 via the components described above. In at least one embodiment, accelerometer 1341, ambient light sensor (“ALS”) 1342, compass 1343, and gyroscope 1344 may be communicatively coupled to sensor hub 1340. In at least one embodiment, thermal sensor 1339, fan 1337, keyboard 1336, and touchpad 1330 may be communicatively coupled to EC 1335. In at least one embodiment, speaker 1363, earphone 1364, and microphone (“mic”) 1365 may be communicatively coupled to audio unit (“audio codec and class-D amplifier”) 1364, which in turn may be communicatively coupled to DSP 1360. In at least one embodiment, audio unit 1364 may include, for example, but not limited to, an audio codec / decoder (“codec”) and a class-D amplifier. In at least one embodiment, SIM card (“SIM”) 1357 may be communicatively coupled to WWAN unit 1356. In at least one embodiment, components such as the WLAN unit 1350 and the Bluetooth unit 1352 and the WWAN unit 1356 may be implemented as a next generation form factor (NGFF).

[0318] In at least one embodiment, system 1300 may be used to implement system 100 (see Figure 1 ), Architecture 200 (see Figure 2 ), Figure 300 (see Figure 3A ), Figure 350 (see Figure 3B ), Figure 400 (see Figure 4 ), Flowchart 500 (see Figure 5 ), Flowchart 600 (see Figure 6 ), Flowchart 700 (see Figure 7 ), Example 800 (see Figure 8 ) and / or block diagram 900 (see Figure 9 ). In at least one embodiment, Figure 13 At least a portion of the system depicted in is used to implement a combination Figure 1-9 For example, in at least one embodiment, the system, technique, function, and / or process described herein may be used to implement one or more systems, techniques, functions, and / or processes. Figure 13 At least one component shown or described may be used to enable a UE device to Figure 1-9 One or more techniques, functions and / or processes described in any one of the foregoing may autonomously adjust the priority of information to be transmitted.

[0319] Figure 14 A computer system 1400 is shown in accordance with at least one embodiment. In at least one embodiment, the computer system 1400 is configured to implement the various processes and methods described throughout this disclosure.

[0320] In at least one embodiment, computer system 1400 includes, but is not limited to, at least one central processing unit ("CPU") 1402 connected to a communication bus 1410 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 1400 includes, but is not limited to, main memory 1404 and control logic (e.g., implemented as hardware, software, or a combination thereof), and data may be stored in main memory 1404 in the form of random access memory ("RAM"). In at least one embodiment, a network interface subsystem ("network interface") 1422 provides an interface to other computing devices and networks for receiving data from computer system 1400 and transmitting data to other systems.

[0321] In at least one embodiment, computer system 1400 includes, but is not limited to, input device 1408, parallel processing system 1412, and display device 1406, 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 1408 (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.

[0322] In at least one embodiment, system 1400 may be used to implement system 100 (see Figure 1 ), Architecture 200 (see Figure 2 ), Figure 300 (see Figure 3A ), Figure 350 (see Figure 3B ), Figure 400 (see Figure 4 ), Flowchart 500 (see Figure 5 ), Flowchart 600 (see Figure 6 ), Flowchart 700 (see Figure 7 ), Example 800 (see Figure 8 ) and / or block diagram 900 (see Figure 9 ). In at least one embodiment, Figure 14 At least a portion of the system depicted in is used to implement a combination Figure 1-9 For example, in at least one embodiment, the system, technique, function, and / or process described herein may be used to implement one or more systems, techniques, functions, and / or processes. Figure 14 At least one component shown or described may be used to enable a UE device to Figure 1-9One or more techniques, functions and / or processes described in any one of the foregoing may autonomously adjust the priority of information to be transmitted.

[0323] Figure 15 A computer system 1500 is shown in accordance with at least one embodiment. In at least one embodiment, computer system 1500 includes, but is not limited to, a computer 1510 and a USB stick 1520. In at least one embodiment, computer 1510 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 1510 includes, but is not limited to, a server, a cloud instance, a laptop computer, and a desktop computer.

[0324] In at least one embodiment, the USB stick 1520 includes, but is not limited to, a processing unit 1530, a USB interface 1540, and USB interface logic 1550. In at least one embodiment, the processing unit 1530 can be any instruction execution system, device, or device capable of executing instructions. In at least one embodiment, the processing unit 1530 can include, but is not limited to, any number and type of processing cores (not shown). In at least one embodiment, the processing core 1530 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 1530 is a tensor processing unit ("TPC") that is optimized to perform machine learning inference operations. In at least one embodiment, the processing core 1530 is a vision processing unit ("VPU") that is optimized to perform machine vision and machine learning inference operations.

[0325] In at least one embodiment, USB interface 1540 can be any type of USB connector or USB receptacle. For example, in at least one embodiment, USB interface 1540 is a USB 3.0 Type-C receptacle for data and power. In at least one embodiment, USB interface 1540 is a USB 3.0 Type-A connector. In at least one embodiment, USB interface logic 1550 can include any number and type of logic that enables processing unit 1530 to connect to a device (e.g., computer 1510) via USB connector 1540.

[0326] In at least one embodiment, system 1500 may be used to implement system 100 (see Figure 1 ), Architecture 200 (see Figure 2 ), Figure 300 (see Figure 3A ), Figure 350 (see Figure 3B ), Figure 400 (see Figure 4 ), Flowchart 500 (see Figure 5 ), Flowchart 600 (see Figure 6 ), Flowchart 700 (see Figure 7 ), Example 800 (see Figure 8 ) and / or block diagram 900 (see Figure 9 ). In at least one embodiment, Figure 15 At least a portion of the system depicted in is used to implement a combination Figure 1-9 For example, in at least one embodiment, the system, technique, function, and / or process described herein may be used to implement one or more systems, techniques, functions, and / or processes. Figure 15 At least one component shown or described may be used to enable a UE device to Figure 1-9 One or more techniques, functions and / or processes described in any one of the foregoing may autonomously adjust the priority of information to be transmitted.

[0327] Figure 16A An exemplary architecture is shown in which multiple GPUs 1610-1613 are communicatively coupled to multiple multi-core processors 1605-1606 via high-speed links 1640-1643 (e.g., buses / point-to-point interconnects, etc.). In one embodiment, the high-speed links 1640-1643 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.

[0328] Furthermore, in one embodiment, two or more GPUs 1610-1613 are interconnected via high-speed links 1629-1630, which may be implemented using the same or different protocols / links as used for high-speed links 1640-1643. Similarly, two or more multi-core processors 1605-1606 may be connected via high-speed link 1628, which may be a symmetric multiprocessor (SMP) bus running at 20 GB / s, 30 GB / s, 120 GB / s, or higher. Alternatively, the same protocol / links may be used (e.g., via a common interconnect fabric). Figure 16A All communications between the various system components shown in .

[0329] In one embodiment, each multi-core processor 1605-1606 is communicatively coupled to processor memory 1601-1602 via memory interconnects 1626-1627, respectively, and each GPU 1610-1613 is communicatively coupled to GPU memory 1620-1623 via GPU memory interconnects 1650-1653, respectively. Memory interconnects 1626-1627 and 1650-1653 can utilize the same or different memory access technologies. By way of example and not limitation, processor memory 1601-1602 and GPU memory 1620-1623 can be volatile memory, 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 can be non-volatile memory, such as 3D XPoint or Nano-Ram. In one embodiment, some portion of the processor memory 1601-1602 may be volatile memory, while another portion may be non-volatile memory (eg, using a two-level memory (2LM) hierarchy).

[0330] As described herein, although the various processors 1605-1606 and GPUs 1610-1613 may be physically coupled to specific memories 1601-1602, 1620-1623, 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 1601-1602 may each contain 64GB of system memory address space, and the GPU memories 1620-1623 may each contain 32GB of system memory address space (resulting in a total addressable memory size of 256GB in this example).

[0331] Figure 16B 16. Additional details are shown for the interconnection between the multi-core processor 1607 and the graphics acceleration module 1646 according to an exemplary embodiment. The graphics acceleration module 1646 may include one or more GPU chips integrated on a line card that is coupled to the processor 1607 via a high-speed link 1640. Alternatively, the graphics acceleration module 1646 may be integrated on the same package or chip as the processor 1607.

[0332] In at least one embodiment, the illustrated processor 1607 includes a plurality of cores 1660A-1660D, each having a translation lookaside buffer 1661A-1661D and one or more caches 1662A-1662D. In at least one embodiment, the cores 1660A-1660D may include various other components, not shown, for executing instructions and processing data. In at least one embodiment, the caches 1662A-1662D may include level 1 (L1) and level 2 (L2) caches. In addition, one or more shared caches 1656 may be included in the caches 1662A-1662D and shared by each group of cores 1660A-1660D. For example, one embodiment of the processor 1607 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. The processor 1607 and the graphics acceleration module 1646 are connected to the system memory 1614, which may include Figure 16A Processor memory 1601-1602 in.

[0333] Coherence is maintained for data and instructions stored in the various caches 1662A-1662D, 1656, and system memory 1614 via inter-core communication over the coherence bus 1664. For example, each cache may have cache coherence logic / circuitry associated therewith to communicate over the coherence bus 1664 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 1664 to snoop cache accesses.

[0334] In one embodiment, proxy circuitry 1625 communicatively couples graphics acceleration module 1646 to coherence bus 1664, thereby allowing graphics acceleration module 1646 to participate in a cache coherence protocol as a peer of cores 1660A-1660D. Interface 1635 provides connectivity to proxy circuitry 1625 via high-speed link 1640 (e.g., PCIe bus, NVLink, etc.), and interface 1637 connects graphics acceleration module 1646 to link 1640.

[0335] In one implementation, the accelerator integrated circuit 1636 provides cache management, memory access, context management, and interrupt management services on behalf of the graphics acceleration module's multiple graphics processing engines 1631, 1632, N. The graphics processing engines 1631, 1632, N may each comprise a separate graphics processing unit (GPU). Alternatively, the graphics processing engines 1631, 1632, 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 block image transfer (BLIT) engine. In at least one embodiment, the graphics acceleration module 1646 may be a GPU having multiple graphics processing engines 1631-1632, N, or the graphics processing engines 1631-1632, N may be individual GPUs integrated into a common package, line card, or chip.

[0336] In one embodiment, the accelerator integrated circuit 1636 includes a memory management unit (MMU) 1639 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 1614. The MMU 1639 may also include a translation lookaside buffer ("TLB") (not shown) for caching virtual / effective-to-physical / real address translations. In one implementation, cache 1638 may store commands and data for efficient access by the graphics processing engines 1631-1632, N. In at least one embodiment, data stored in cache 1638 and graphics memory 1633-1634, M is kept consistent with the core caches 1662A-1662D, 1656, and system memory 1614. As previously described, this task may be accomplished via proxy circuitry 1625 acting on behalf of cache 1638 and graphics memory 1633-1634, M (e.g., sending updates related to modifications / accesses of cache lines on processor caches 1662A-1662D, 1656 to cache 1638 and receiving updates from cache 1638).

[0337] A set of registers 1645 stores context data for threads executed by graphics processing engines 1631-1632, N, and context management circuitry 1648 manages thread contexts. For example, context management circuitry 1648 can perform save and restore operations to save and restore the context of various threads during context switches (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 1648 can store current register values ​​to a designated area in memory (e.g., identified by a context pointer) upon context switching. The register values ​​can then be restored upon returning to context. In one embodiment, interrupt management circuitry 1647 receives and processes interrupts received from system devices.

[0338] In one implementation, the MMU 1639 converts virtual / effective addresses from the graphics processing engine 1631 into real / physical addresses in the system memory 1614. One embodiment of the accelerator integrated circuit 1636 supports multiple (e.g., 4, 8, 16) graphics accelerator modules 1646 and / or other accelerator devices. The graphics accelerator module 1646 can be dedicated to a single application executing on the processor 1607, 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 1631-1632, 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.

[0339] In at least one embodiment, the accelerator integrated circuit 1636 acts as a bridge to the system for the graphics acceleration module 1646 and provides address translation and system memory cache services. In addition, the accelerator integrated circuit 1636 can provide virtualization facilities for the host processor to manage virtualization, interrupts, and memory management for the graphics processing engines 1631-1632.

[0340] Because the hardware resources of graphics processing engines 1631-1632, N are explicitly mapped into the real address space seen by host processor 1607, any host processor can directly address these resources using effective address values. In at least one embodiment, one function of accelerator integrated circuit 1636 is to physically separate graphics processing engines 1631-1632, N so that they appear to the system as independent units.

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

[0342] In one embodiment, to reduce data traffic on link 1640, a biasing technique can be used to ensure that the data stored in graphics memory 1633-1634, M is the data most frequently used by graphics processing engines 1631-1632, N, and preferably not used (at least not frequently) by cores 1660A-1660D. Similarly, in at least one embodiment, the biasing mechanism attempts to keep data needed by the core (and preferably not graphics processing engines 1631-1632, N) in the core's cache 1662A-1662D, 1656 and system memory 1614.

[0343] Figure 16C Another exemplary embodiment is shown in which an accelerator integrated circuit 1636 is integrated into the processor 1607. In this embodiment, the graphics processing engines 1631-1632, N communicate directly with the accelerator integrated circuit 1636 via the interface 1637 and the interface 1635 (which may also utilize any form of bus or interface protocol) through the high-speed link 1640. The accelerator integrated circuit 1636 can perform operations related to Figure 16B The operations described above are identical to those described above. However, due to its close proximity to the coherence bus 1664 and caches 1662A-1662D, 1656, 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 1636 and a programming model controlled by the graphics acceleration module 1646.

[0344] In at least one embodiment, graphics processing engines 1631-1632, 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 1631-1632, N, thereby providing virtualization within a VM / partition.

[0345] In at least one embodiment, graphics processing engines 1631-1632,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 1631-1632,N to allow each operating system to access them. For a single-partition system without a hypervisor, the operating system owns graphics processing engines 1631-1632,N. In at least one embodiment, the operating system can virtualize graphics processing engines 1631-1632,N to provide access to each process or application.

[0346] In at least one embodiment, the graphics acceleration module 1646 or individual graphics processing engines 1631-1632,N use a process handle to select a process element. In one embodiment, the process element is stored in the system memory 1614 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 1631-1632,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.

[0347] Figure 16D An exemplary accelerator integrated slice 1690 is shown. As used herein, a "slice" comprises a designated portion of the processing resources of an accelerator integrated circuit 1636. An application is an effective address space 1682 in system memory 1614 that stores process elements 1683. In one embodiment, process elements 1683 are stored in response to a GPU call 1681 from an application 1680 executing on processor 1607. Process elements 1683 contain the process state of the corresponding application 1680. A work descriptor (WD) 1684 contained in process element 1683 may be a single job requested by the application, or may contain a pointer to a job queue. In at least one embodiment, WD 1684 is a pointer to a job request queue in the application's address space 1682.

[0348] The graphics acceleration module 1646 and / or the individual graphics processing engines 1631-1632, 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 1684 to the graphics acceleration module 1646 to start a job in a virtualized environment can be included.

[0349] In at least one embodiment, a dedicated process programming model is implementation-specific. In this model, a single process owns a graphics acceleration module 1646 or an individual graphics processing engine 1631. Since the hypervisor initializes the accelerator integrated circuit 1636 for the owned partition when the graphics acceleration module 1646 is owned by a single process, the operating system initializes the accelerator integrated circuit 1636 for the owned process when the graphics acceleration module 1646 is assigned.

[0350] In operation, the WD fetch unit 1691 in the accelerator integrated slice 1690 fetches the next WD 1684, which includes an indication of work to be completed by one or more graphics processing engines of the graphics acceleration module 1646. Data from WD 1684 can be stored in registers 1645 and used by the MMU 1639, interrupt management circuitry 1647, and / or context management circuitry 1648, as shown. For example, one embodiment of the MMU 1639 includes segment / page roaming circuitry for accessing segment / page tables 1686 within the OS virtual address space 1685. The interrupt management circuitry 1647 can process interrupt events 1692 received from the graphics acceleration module 1646. When executing graphics operations, effective addresses 1693 generated by the graphics processing engines 1631-1632, N are converted into real addresses by the MMU 1639.

[0351] In one embodiment, the same set of registers 1645 is replicated for each graphics processing engine 1631-1632, N, and / or graphics acceleration module 1646, and the registers 1645 can be initialized by the hypervisor or operating system. Each of these replicated registers can be included in the accelerator integration slice 1690. Example registers that can be initialized by the hypervisor are shown in Table 1.

[0352]

[0353]

[0354] Example registers that may be initialized by the operating system are shown in Table 2.

[0355]

[0356] In one embodiment, each WD 1684 is specific to a particular graphics acceleration module 1646 and / or graphics processing engine 1631-1632, N. It contains all the information needed for the graphics processing engine 1631-1632, N to complete the work, or it can be a pointer to a memory location where the application has set up a command queue for the work to be done.

[0357] Figure 16E16. Additional details of an exemplary embodiment of a sharing model are shown. This embodiment includes a hypervisor real address space 1698 in which a process element list 1699 is stored. The hypervisor real address space 1698 is accessible via a hypervisor 1696 that virtualizes a graphics acceleration module engine for an operating system 1695.

[0358] 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 1646. There are two programming models where the graphics acceleration module 1646 is shared by multiple processes and partitions: time-sliced ​​sharing and graphics-directed sharing.

[0359] In this model, the hypervisor 1696 owns the graphics acceleration module 1646 and makes its functionality available to all operating systems 1695. For the graphics acceleration module 1646 to support virtualization through the hypervisor 1696, the graphics acceleration module 1646 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 1646 must provide a context save and restore mechanism, (2) the graphics acceleration module 1646 guarantees that the application's job requests are completed within a specified amount of time, including any transition errors, or the graphics acceleration module 1646 provides the ability to preempt job processing, and (3) fairness between graphics acceleration module 1646 processes must be ensured when operating in a directed shared programming model.

[0360] In at least one embodiment, an application 1680 is required to make an operating system 1695 system call using a graphics acceleration module 1646 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 1646 type describes the target acceleration function for the system call. In at least one embodiment, the graphics acceleration module 1646 type can be a system-specific value. In at least one embodiment, the WD is formatted specifically for the graphics acceleration module 1646 and can take the form of a graphics acceleration module 1646 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 1646. 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. If the implementation of the accelerator integrated circuit 1636 and graphics acceleration module 1646 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. Hypervisor 1696 can optionally apply the current privilege mask overwrite register (AMOR) value before placing the AMR into process element 1683. In at least one embodiment, CSRP is one of registers 1645 that contains the effective address of an area in the application's address space 1682 for graphics acceleration module 1646 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.

[0361] Upon receiving the system call, the operating system 1695 may verify that the application 1680 has been registered and granted permission to use the graphics acceleration module 1646. The operating system 1695 then uses

[0362] The information shown in Table 3 is used to call the management program 1696.

[0363]

[0364]

[0365] Upon receiving the hypervisor call, the hypervisor 1696 verifies that the operating system 1695 has registered and been granted permission to use the graphics acceleration module 1646. The hypervisor 1696 then places the process element 1683 into a linked list of process elements of the corresponding graphics acceleration module 1646 type. The process element may include the information shown in Table 4.

[0366]

[0367] In at least one embodiment, the hypervisor initializes the plurality of accelerator integrated slice 1690 registers 1645 .

[0368] like Figure 16F 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 1601-1602 and GPU memories 1620-1623. In this implementation, operations executed on GPUs 1610-1613 utilize the same virtual / effective memory address space to access processor memories 1601-1602, and vice versa, thereby simplifying programmability. In at least one embodiment, a first portion of the virtual / effective address space is allocated to processor memory 1601, a second portion is allocated to second processor memory 1602, a third portion is allocated to GPU memory 1620, 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 1601-1602 and GPU memories 1620-1623, thereby allowing any processor or GPU to access that memory using a virtual address mapped to any physical memory.

[0369] In one embodiment, bias / coherency management circuitry 1694A-1694E within one or more MMUs 1639A-1639E ensures cache coherency between the caches of one or more host processors (e.g., 1605) and GPUs 1610-1613 and implements biasing techniques that indicate the physical memory where certain types of data should be stored. Figure 16F Multiple instances of bias / coherence management circuits 1694A- 1694E are shown in , but bias / coherence circuits may be implemented within an MMU of one or more host processors 1605 and / or within an accelerator integrated circuit 1636 .

[0370] One embodiment allows GPU attached memory 1620-1623 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 1620-1623 as system memory without the heavy cache coherence overhead provides a favorable operating environment for GPU offloading. This arrangement allows software of the host processor 1605 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 1620-1623 without cache coherence overhead can be critical to the execution time of offloaded computations. For example, in situations with large amounts of streaming write memory traffic, cache coherence overhead can significantly reduce the effective write bandwidth seen by GPUs 1610-1613. 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.

[0371] 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 1620-1623, with or without a bias cache in GPUs 1610-1613 (e.g., to cache frequently / recently used entries in the bias table). Alternatively, the entire bias table can be maintained within the GPU.

[0372] In at least one embodiment, before actually accessing the GPU memory, the bias table entry associated with each access to the GPU attached memory 1620-1623 is accessed, resulting in the following operations. First, local requests from GPUs 1610-1613 whose pages are found in the GPU bias are forwarded directly to the corresponding GPU memory 1620-1623. Local requests from the GPU whose pages are found in the host bias are forwarded to processor 1605 (e.g., via a high-speed link as described above). In one embodiment, a request from processor 1605 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 1610-1613. 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 via a software-based mechanism, a hardware-assisted software-based mechanism, or, in limited cases, a purely hardware-based mechanism.

[0373] 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 1605 bias to GPU bias, but not for the reverse migration.

[0374] In one embodiment, cache coherence is maintained by temporarily rendering GPU-biased pages that cannot be cached by host processor 1605. To access these pages, processor 1605 may request access from GPU 1610, which may or may not immediately grant access. Therefore, to reduce communication between processor 1605 and GPU 1610, it is beneficial to ensure that GPU-biased pages are the pages required by the GPU and not the host processor 1605, and vice versa.

[0375] Figure 17 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.

[0376] Figure 1717 is a block diagram illustrating an exemplary system on a chip integrated circuit 1700 that can be fabricated using one or more IP cores according to at least one embodiment. In at least one embodiment, integrated circuit 1700 includes one or more application processors 1705 (e.g., CPUs), at least one graphics processor 1710, and may additionally include an image processor 1715 and / or a video processor 1720, any of which may be modular IP cores. In at least one embodiment, integrated circuit 1700 includes peripheral or bus logic, including a USB controller 1725, a UART controller 1730, an SPI / SDIO controller 1735, and an I.sup.2S / I.sup.2C controller 1740. In at least one embodiment, integrated circuit 1700 may include a display device 1745 coupled to one or more of a High-Definition Multimedia Interface (HDMI) controller 1750 and a Mobile Industry Processor Interface (MIPI) display interface 1755. In at least one embodiment, storage may be provided by a flash memory subsystem 1760, including flash memory and a flash memory controller. In at least one embodiment, a memory interface may be provided via a memory controller 1765 for accessing SDRAM or SRAM memory devices. In at least one embodiment, some integrated circuits also include an embedded security engine 1770 .

[0377] In at least one embodiment, circuit 1700 may be used to implement system 100 (see Figure 1 ), Architecture 200 (see Figure 2 ), Figure 300 (see Figure 3A ), Figure 350 (see Figure 3B ), Figure 400 (see Figure 4 ), Flowchart 500 (see Figure 5 ), Flowchart 600 (see Figure 6 ), Flowchart 700 (see Figure 7 ), Example 800 (see Figure 8 ) and / or block diagram 900 (see Figure 9 ). In at least one embodiment, Figure 17 At least a portion of the system depicted in is used to implement a combination Figure 1-9 For example, in at least one embodiment, the system, technique, function, and / or process described herein may be used to implement one or more systems, techniques, functions, and / or processes. Figure 17 At least one component shown or described may be used to enable a UE device to Figure 1-9 One or more techniques, functions and / or processes described in any one of the foregoing may autonomously adjust the priority of information to be transmitted.

[0378] Figure 18A and Figure 18BAn 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.

[0379] Figure 18A and Figure 18B is a block diagram illustrating an exemplary graphics processor for use within a SoC according to embodiments described herein. Figure 18A An exemplary graphics processor 1810 of a system-on-chip integrated circuit is shown that can be fabricated using one or more IP cores in accordance with at least one embodiment. Figure 18B An additional exemplary graphics processor 1840 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 18A The graphics processor 1810 is a low-power graphics processor core. In at least one embodiment, Figure 18B The graphics processor 1840 is a higher performance graphics processor core. In at least one embodiment, each of the graphics processors 1810, 1840 can be Figure 17 A variant of the graphics processor 1710.

[0380] In at least one embodiment, the graphics processor 1810 includes a vertex processor 1805 and one or more fragment processors 1815A-1815N (e.g., 1815A, 1815B, 1815C, 1815D through 1815N-1 and 1815N). In at least one embodiment, the graphics processor 1810 can execute different shader programs via separate logic, such that the vertex processor 1805 is optimized to perform operations for the vertex shader program, while the one or more fragment processors 1815A-1815N perform fragment (e.g., pixel) shading operations for the fragment or pixel or shader program. In at least one embodiment, the vertex processor 1805 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 1815A-1815N use the primitives and vertex data generated by the vertex processor 1805 to generate a frame buffer for display on a display device. In at least one embodiment, one or more fragment processors 1815A-1815N 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.

[0381] In at least one embodiment, graphics processor 1810 additionally includes one or more memory management units (MMUs) 1820A-1820B, one or more caches 1825A-1825B, and one or more circuit interconnects 1830A-1830B. In at least one embodiment, one or more MMUs 1820A-1820B provide a mapping of virtual to physical addresses for graphics processor 1810, including for vertex processor 1805 and / or fragment processors 1815A-1815N, which may reference vertex or image / texture data stored in memory, in addition to vertex or image / texture data stored in one or more caches 1825A-1825B. In at least one embodiment, one or more MMUs 1820A-1820B may synchronize with other MMUs within the system, including with other MMUs. Figure 17 One or more MMUs associated with one or more application processors 1705, graphics processor 1715, and / or video processor 1720 enable each processor 1705-1720 to participate in a shared or unified virtual memory system. In at least one embodiment, one or more circuit interconnects 1830A-1830B enable graphics processor 1810 to connect to other IP cores within the SoC via an internal bus of the SoC or via a direct connection.

[0382] In at least one embodiment, graphics processor 1840 includes Figure 18A One or more MMUs 1820A-1820B, caches 1825A-1825B, and circuit interconnects 1830A-1830B of the graphics processor 1810. In at least one embodiment, the graphics processor 1840 includes one or more shader cores 1855A-1855N (e.g., 1855A, 1855B, 1855C, 1855D, 1855E, 1855F through 1855N-1 and 1855N) 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 1840 includes an inter-core task manager 1845 that acts as a thread dispatcher to dispatch execution threads to one or more shader cores 1855A-1855N and a tiling unit 1858 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.

[0383] In at least one embodiment, processor 1810 may be used to implement system 100 (see Figure 1 ), Architecture 200 (see Figure 2 ), Figure 300 (see Figure 3A ), Figure 350 (see Figure 3B ), Figure 400 (see Figure 4 ), Flowchart 500 (see Figure 5 ), Flowchart 600 (see Figure 6 ), Flowchart 700 (see Figure 7 ), Example 800 (see Figure 8 ) and / or block diagram 900 (see Figure 9 ). In at least one embodiment, Figures 18A-18B At least a portion of the system depicted in is used to implement a combination Figure 1-9 For example, in at least one embodiment, the system, technique, function, and / or process described herein may be used to implement one or more systems, techniques, functions, and / or processes. Figures 18A-18B At least one component shown or described may be used to enable a UE device to Figure 1-9 One or more techniques, functions and / or processes described in any one of the foregoing may autonomously adjust the priority of information to be transmitted.

[0384] Figure 19A and Figure 19B Additional exemplary graphics processor logic according to embodiments described herein is shown. In at least one embodiment, Figure 19A Shows that can be included in Figure 17 Graphics core 1900 within graphics processor 1710 of FIG. 17 and, in at least one embodiment, may be such as Figure 18B Unified shader cores 1855A-1855N are shown. Figure 19B A highly parallel, general-purpose graphics processing unit 1930 suitable for deployment on a multi-chip module in at least one embodiment is shown.

[0385] In at least one embodiment, graphics core 1900 includes a shared instruction cache 1902, texture units 1918, and cache / shared memory 1920, which are common to execution resources within graphics core 1900. In at least one embodiment, graphics core 1900 may include multiple slices 1901A-1901N, or partitions of each core, and the graphics processor may include multiple instances of graphics core 1900. Slices 1901A-1901N may include support logic including local instruction caches 1904A-1904N, thread schedulers 1906A-1906N, thread dispatchers 1908A-1908N, and a set of registers 1910A-1910N. In at least one embodiment, slices 1901A-1901N may include a set of additional function units (AFUs 1912A-1912N), floating point units (FPUs 1914A-1914N), integer arithmetic logic units (ALUs 1916A-1916N), address calculation units (ACUs 1913A-1913N), double precision floating point units (DPFPUs 1915A-1915N), and matrix processing units (MPUs 1917A-1917N).

[0386] In at least one embodiment, the FPUs 1914A-1914N can perform single-precision (32-bit) and half-precision (16-bit) floating-point operations, while the DPFPUs 1915A-1915N perform double-precision (64-bit) floating-point operations. In at least one embodiment, the ALUs 1916A-1916N 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 1917A-1917N 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 1917-1917N 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 1912A-1912N can perform additional logical operations not supported by the floating-point or integer units, including trigonometric operations (e.g., sine, cosine, etc.).

[0387] In at least one embodiment, graphics core 1900 may be used to implement system 100 (see Figure 1 ), Architecture 200 (see Figure 2 ), Figure 300 (see Figure 3A ), Figure 350 (see Figure 3B ), Figure 400 (see Figure 4 ), Flowchart 500 (see Figure 5 ), Flowchart 600 (see Figure 6), Flowchart 700 (see Figure 7 ), Example 800 (see Figure 8 ) and / or block diagram 900 (see Figure 9 ). In at least one embodiment, Figure 19A At least a portion of the system depicted in is used to implement a combination Figure 1-9 For example, in at least one embodiment, the system, technique, function, and / or process described herein may be used to implement one or more systems, techniques, functions, and / or processes. Figure 19A At least one component shown or described may be used to enable a UE device to Figure 1-9 One or more techniques, functions and / or processes described in any one of the foregoing may autonomously adjust the priority of information to be transmitted.

[0388] Figure 19B A general purpose processing unit (GPGPU) 1930 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 1930 can be directly linked to other instances of GPGPU 1930 to create a multi-GPU cluster to increase the training speed for deep neural networks. In at least one embodiment, GPGPU 1930 includes a host interface 1932 to enable connection to a host processor. In at least one embodiment, host interface 1932 is a PCI Express interface. In at least one embodiment, host interface 1932 can be a vendor-specific communication interface or communication structure. In at least one embodiment, GPGPU 1930 receives commands from the host processor and uses a global scheduler 1934 to assign execution threads associated with those commands to a group of compute clusters 1936A-1936H. In at least one embodiment, compute clusters 1936A-1936H share cache memory 1938. In at least one embodiment, cache memory 1938 may serve as a higher level of cache for cache memory within compute clusters 1936A-1936H.

[0389] In at least one embodiment, GPGPU 1930 includes memory 1944A-1944B coupled to compute clusters 1936A-1936H via a set of memory controllers 1942A-1942B. In at least one embodiment, memory 1944A-1944B 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.

[0390] In at least one embodiment, computing clusters 1936A-1936H each include a set of graphics cores, e.g. Figure 19A The graphics core 1900 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 1936A-1936H 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.

[0391] In at least one embodiment, multiple instances of GPGPU 1930 can be configured to function as a compute cluster. In at least one embodiment, the communications used by compute clusters 1936A-1936H for synchronization and data exchange vary between embodiments. In at least one embodiment, multiple instances of GPGPU 1930 communicate via host interface 1932. In at least one embodiment, GPGPU 1930 includes an I / O hub 1939 that couples GPGPU 1930 to a GPU link 1940, enabling direct connections to other instances of GPGPU 1930. In at least one embodiment, GPU link 1940 is coupled to a dedicated GPU-to-GPU bridge that enables communication and synchronization between multiple instances of GPGPU 1930. In at least one embodiment, GPU link 1940 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 1930 reside in separate data processing systems and communicate via a network device accessible through host interface 1932. In at least one embodiment, GPU link 1940 may be configured to enable connection to a host processor in addition to or as an alternative to host interface 1932 .

[0392] In at least one embodiment, GPGPU 1930 can be configured to train neural networks. In at least one embodiment, GPGPU 1930 can be used within an inference platform. In at least one embodiment, where GPGPU 1930 is used for inference, the GPGPU can include fewer compute clusters 1936A-1936H than when the GPGPU is used to train a neural network. In at least one embodiment, the memory technology associated with memory 1944A-1944B 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 1930 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.

[0393] In at least one embodiment, GPGPU 1930 may be used to implement system 100 (see Figure 1 ), Architecture 200 (see Figure 2 ), Figure 300 (see Figure 3A ), Figure 350 (see Figure 3B ), Figure 400 (see Figure 4 ), Flowchart 500 (see Figure 5 ), Flowchart 600 (see Figure 6 ), Flowchart 700 (see Figure 7 ), Example 800 (see Figure 8 ) and / or block diagram 900 (see Figure 9 ). In at least one embodiment, Figure 19B At least a portion of the system depicted in is used to implement a combination Figure 1-9 For example, in at least one embodiment, the system, technique, function, and / or process described herein may be used to implement one or more systems, techniques, functions, and / or processes. Figure 19B At least one component shown or described may be used to enable a UE device to Figure 1-9 One or more techniques, functions and / or processes described in any one of the foregoing may autonomously adjust the priority of information to be transmitted.

[0394] Figure 20A block diagram of a computer system 2000 according to at least one embodiment is shown. In at least one embodiment, computer system 2000 includes a processing subsystem 2001 having one or more processors 2002 and a system memory 2004, which communicates via an interconnect path that may include a memory hub 2005. In at least one embodiment, memory hub 2005 may be a separate component within a chipset assembly or may be integrated within one or more processors 2002. In at least one embodiment, memory hub 2005 is coupled to an I / O subsystem 2011 via a communication link 2006. In one embodiment, I / O subsystem 2011 includes an I / O hub 2007, which enables computer system 2000 to receive input from one or more input devices 2008. In at least one embodiment, I / O hub 2007 may enable a display controller, which may be included in one or more processors 2002, to provide output to one or more display devices 2010A. In at least one embodiment, the one or more display devices 2010A coupled to the I / O hub 2007 may include local, internal, or embedded display devices.

[0395] In at least one embodiment, the processing subsystem 2001 includes one or more parallel processors 2012 coupled to a memory hub 2005 via a bus or other communication link 2013. In at least one embodiment, the communication link 2013 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 2012 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 2012 form a graphics processing subsystem that can output pixels to one of one or more display devices 2010A coupled via an I / O hub 2007. In at least one embodiment, the one or more parallel processors 2012 can also include a display controller and display interface (not shown) to enable direct connection to one or more display devices 2010B.

[0396] In at least one embodiment, a system storage unit 2014 can be connected to the I / O hub 2007 to provide a storage mechanism for the computer system 2000. In at least one embodiment, an I / O switch 2016 can be used to provide an interface mechanism to enable connections between the I / O hub 2007 and other components, such as a network adapter 2018 and / or a wireless network adapter 2017 that can be integrated into the platform, as well as various other devices that can be added via one or more add-on devices 2020. In at least one embodiment, the network adapter 2018 can be an Ethernet adapter or another wired network adapter. In at least one embodiment, the wireless network adapter 2019 can include one or more of Wi-Fi, Bluetooth, near field communication (NFC), or other network devices including one or more radio devices.

[0397] In at least one embodiment, computer system 2000 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 2007. 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 20 Communication paths for various components in a chip, such as NV-Link high-speed interconnect or interconnect protocol.

[0398] In at least one embodiment, one or more parallel processors 2012 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 2012 include circuits optimized for general-purpose processing. In at least one embodiment, the components of computer system 2000 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 2012, memory hub 2005, processor 2002, and I / O hub 2007 can be integrated into a system-on-chip (SoC) integrated circuit. In at least one embodiment, the components of computer system 2000 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 2000 can be integrated into a multi-chip module (MCM), which can be interconnected with other multi-chip modules to form a modular computer system.

[0399] In at least one embodiment, system 2000 may be used to implement system 100 (see Figure 1 ), Architecture 200 (see Figure 2 ), Figure 300 (see Figure 3A ), Figure 350 (see Figure 3B ), Figure 400 (see Figure 4 ), Flowchart 500 (see Figure 5 ), Flowchart 600 (see Figure 6 ), Flowchart 700 (see Figure 7 ), Example 800 (see Figure 8 ) and / or block diagram 900 (see Figure 9 ). In at least one embodiment, Figure 20 At least a portion of the system depicted in is used to implement a combination Figure 1-9 For example, in at least one embodiment, the system, technique, function, and / or process described herein may be used to implement one or more systems, techniques, functions, and / or processes. Figure 20 At least one component shown or described may be used to enable a UE device to Figure 1-9 One or more techniques, functions and / or processes described in any one of the foregoing may autonomously adjust the priority of information to be transmitted.

[0400] processor

[0401] Figure 21A 2100 in accordance with at least one embodiment. In at least one embodiment, the various components of the parallel processor 2100 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 2100 is shown as a processor according to an exemplary embodiment. Figure 20 A variation of the one or more parallel processors 2012 is shown.

[0402] In at least one embodiment, parallel processor 2100 includes a parallel processing unit (PPU) 2102. In at least one embodiment, PPU 2102 includes an I / O unit (I / O) ...

[0403] In at least one embodiment, when host interface 2106 receives command buffers via I / O unit 2104, host interface 2106 can direct work operations to execute those commands to front end 2108. In at least one embodiment, front end 2108 is coupled to scheduler 2110, which is configured to distribute commands or other work items to processing cluster array 2112. In at least one embodiment, scheduler 2110 ensures that processing cluster array 2112 is properly configured and in a valid state before distributing tasks to processing cluster array 2112. In at least one embodiment, scheduler 2110 is implemented by firmware logic executing on a microcontroller. In at least one embodiment, the microcontroller-implemented scheduler 2110 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 2112. In at least one embodiment, host software can authenticate workloads for scheduling on processing array 2112 through one of multiple graphics processing doorbells. In at least one embodiment, the workload may then be automatically distributed across the processing array 2112 by scheduler 2110 logic within a microcontroller that includes scheduler 2110 .

[0404] In at least one embodiment, the processing cluster array 2112 may include up to "N" processing clusters (e.g., cluster 2114A, cluster 2114B, through cluster 2114N). In at least one embodiment, each cluster 2114A-2114N of the processing cluster array 2112 may execute a large number of concurrent threads. In at least one embodiment, the scheduler 2110 may allocate work to the clusters 2114A-2114N of the processing cluster array 2112 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 the scheduler 2110 or may be assisted in part by compiler logic during the compilation of program logic configured to be executed by the processing cluster array 2112. In at least one embodiment, different clusters 2114A-2114N of the processing cluster array 2112 may be assigned to process different types of programs or to perform different types of computations.

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

[0406] In at least one embodiment, the processing cluster array 2112 is configured to perform parallel graphics processing operations. In at least one embodiment, the processing cluster array 2112 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, the processing cluster array 2112 may be configured to execute shader programs related to graphics processing, such as, but not limited to, vertex shaders, tessellation shaders, geometry shaders, and pixel shaders. In at least one embodiment, the parallel processing units 2102 may transfer data from system memory via the I / O units 2104 for processing. In at least one embodiment, during processing, the transferred data may be stored in on-chip memory (e.g., parallel processor memory 2122) during processing and then written back to system memory.

[0407] In at least one embodiment, when parallel processing unit 2102 is used to perform graphics processing, scheduler 2110 can be configured to divide the processing workload into tasks of approximately equal size to better distribute graphics processing operations to multiple clusters 2114A-2114N of processing cluster array 2112. In at least one embodiment, portions of processing cluster array 2112 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 2114A-2114N can be stored in a buffer to allow the intermediate data to be transferred between clusters 2114A-2114N for further processing.

[0408] In at least one embodiment, the processing cluster array 2112 can receive processing tasks to be executed via the scheduler 2110, which receives commands defining the processing tasks from the front end 2108. In at least one embodiment, the processing tasks 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, the scheduler 2110 can be configured to obtain an index corresponding to a task, or can receive the index from the front end 2108. In at least one embodiment, the front end 2108 can be configured to ensure that the processing cluster array 2112 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.).

[0409] In at least one embodiment, each of the one or more instances of parallel processing unit 2102 can be coupled to parallel processor memory 2122. In at least one embodiment, parallel processor memory 2122 can be accessed via memory crossbar 2116, which can receive memory requests from processing cluster array 2112 and I / O unit 2104. In at least one embodiment, memory crossbar 2116 can access parallel processor memory 2122 via memory interface 2118. In at least one embodiment, memory interface 2118 can include multiple partition units (e.g., partition unit 2120A, partition unit 2120B, through partition unit 2120N), each of which can be coupled to a portion of parallel processor memory 2122 (e.g., a memory unit). In at least one embodiment, the plurality of partition units 2120A-2120N are configured to be equal to the number of memory cells, such that the first partition unit 2120A has a corresponding first memory cell 2124A, the second partition unit 2120B has a corresponding memory cell 2124B, and the Nth partition unit 2120N has a corresponding Nth memory cell 2124N. In at least one embodiment, the number of partition units 2120A-2120N may not be equal to the number of memory devices.

[0410] In at least one embodiment, memory units 2124A-2124N 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 2124A-2124N 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 2124A-2124N, allowing partition units 2120A-2120N to write portions of each render target in parallel to efficiently use the available bandwidth of parallel processor memory 2122. In at least one embodiment, local instances of parallel processor memory 2122 may be eliminated in favor of a unified memory design utilizing system memory in combination with local cache memory.

[0411] In at least one embodiment, any of the clusters 2114A-2114N in the processing cluster array 2112 can process data to be written to any memory unit 2124A-2124N within the parallel processor memory 2122. In at least one embodiment, the memory crossbar 2116 can be configured to transmit the output of each cluster 2114A-2114N to any partition unit 2120A-2120N or another cluster 2114A-2114N, which can perform other processing operations on the output. In at least one embodiment, each cluster 2114A-2114N can communicate with a memory interface 2118 via the memory crossbar 2116 to read from or write to various external storage devices. In at least one embodiment, memory crossbar switch 2116 has connections to memory interface 2118 for communicating with I / O unit 2104, as well as connections to local instances of parallel processor memory 2122, thereby enabling processing units within different processing clusters 2114A-2114N to communicate with system memory or other memory that is not local to parallel processing unit 2102. In at least one embodiment, memory crossbar switch 2116 can use virtual channels to separate traffic flows between clusters 2114A-2114N and partition units 2120A-2120N.

[0412] In at least one embodiment, multiple instances of parallel processing unit 2102 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 2102 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 2102 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 2102 or parallel processor 2100 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.

[0413] Figure 21B is a block diagram of a partition unit 2120 according to at least one embodiment. In at least one embodiment, the partition unit 2120 is Figure 21A2120N。In at least one embodiment, the partition unit 2120 includes an L2 cache 2121, a frame buffer interface 2125, and an ROP 2126 (raster operation unit). The L2 cache 2121 is a read / write cache that is configured to perform load and store operations received from the memory crossbar switch 2116 and the ROP 2126. In at least one embodiment, the L2 cache 2121 outputs read misses and urgent write-back requests to the frame buffer interface 2125 for processing. In at least one embodiment, updates can also be sent to the frame buffer via the frame buffer interface 2125 for processing. In at least one embodiment, the frame buffer interface 2125 communicates with memory units in the parallel processor memory (such as Figure 21A interacts with one of the memory units 2124A-2124N (e.g., within parallel processor memory 2122).

[0414] In at least one embodiment, ROP 2126 is a processing unit that performs raster operations such as stenciling, z-testing, blending, etc. In at least one embodiment, ROP 2126 then outputs the processed graphics data that is stored in graphics memory. In at least one embodiment, ROP 2126 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 2126 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 the depth and color data on a per-tile basis.

[0415] In at least one embodiment, ROP 2126 is included within each processing cluster (e.g., Figure 21A In at least one embodiment, read and write requests for pixel data are transmitted through the memory crossbar 2116 rather than through the pixel fragment data transfer. In at least one embodiment, the processed graphics data can be displayed on a display device such as a Figure 20 2010), routed by processor 2002 for further processing, or by Figure 21A One of the processing entities within parallel processor 2100 is routed for further processing.

[0416] Figure 21C is a block diagram of a processing cluster 2114 within a parallel processing unit according to at least one embodiment. In at least one embodiment, a processing cluster is Figure 21AIn at least one embodiment, processing cluster 2114 can be configured to execute many threads in parallel, where the term "thread" refers to an instance of a particular program executed on a particular 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.

[0417] In at least one embodiment, the operation of the processing cluster 2114 can be controlled by a pipeline manager 2132 that assigns processing tasks to SIMT parallel processors. In at least one embodiment, the pipeline manager 2132 Figure 21A The scheduler 2110 receives instructions and manages the execution of these instructions through the graphics multiprocessor 2134 and / or the texture unit 2136. In at least one embodiment, the graphics multiprocessor 2134 is an exemplary instance of a SIMT parallel processor. However, in at least one embodiment, various types of SIMT parallel processors with different architectures may be included within the processing cluster 2114. In at least one embodiment, one or more instances of the graphics multiprocessor 2134 may be included within the processing cluster 2114. In at least one embodiment, the graphics multiprocessor 2134 may process data, and the data crossbar 2140 may be used to distribute the processed data to one of multiple possible destinations (including other shader units). In at least one embodiment, the pipeline manager 2132 may facilitate the distribution of processed data by specifying the destination of the processed data to be distributed via the data crossbar 2140.

[0418] In at least one embodiment, each graphics multiprocessor 2134 within a processing cluster 2114 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.

[0419] In at least one embodiment, instructions transmitted to the processing cluster 2114 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 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 the graphics multiprocessor 2134. In at least one embodiment, a thread group can include fewer threads than the number of processing engines within the graphics multiprocessor 2134. 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 cycle being processed by the thread group. In at least one embodiment, a thread group can also include more threads than the number of processing engines within the graphics multiprocessor 2134. In at least one embodiment, when a thread group includes more threads than the number of processing engines within the graphics multiprocessor 2134, processing can be performed in consecutive clock cycles. In at least one embodiment, multiple thread groups can be executed simultaneously on the graphics multiprocessor 2134.

[0420] In at least one embodiment, the graphics multiprocessor 2134 includes internal cache memory to perform load and store operations. In at least one embodiment, the graphics multiprocessor 2134 can abandon the internal cache and use cache memory within the processing cluster 2114 (e.g., L1 cache 2148). In at least one embodiment, each graphics multiprocessor 2134 can also access a partition unit (e.g., Figure 21A L2 cache within partition units 2120A-2120N) of the graphics multiprocessor 2134 is shared across all processing clusters 2114 and can be used to transfer data between threads. In at least one embodiment, graphics multiprocessor 2134 can also access 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 2102 can be used as global memory. In at least one embodiment, processing cluster 2114 includes multiple instances of graphics multiprocessor 2134, which can share common instructions and data, which can be stored in L1 cache 2148.

[0421] In at least one embodiment, each processing cluster 2114 may include a memory management unit ("MMU") 2145 configured to map virtual addresses to physical addresses. In at least one embodiment, one or more instances of the MMU 2145 may reside in Figure 21A21. In at least one embodiment, the MMU 2145 includes a set of page table entries (PTEs) that are used to map virtual addresses to physical addresses of tiles and optionally to cache line indices. In at least one embodiment, the MMU 2145 may include an address translation lookaside buffer (TLB) or a cache that may reside within the graphics multiprocessor 2134 or L1 cache or processing cluster 2114. In at least one embodiment, the physical address is 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.

[0422] In at least one embodiment, the processing clusters 2114 can be configured such that each graphics multiprocessor 2134 is coupled to a texture unit 2136 to perform texture mapping operations, which determine texture sample locations, read texture data, and filter 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 2134, and retrieved from an L2 cache, local parallel processor memory, or system memory as needed. In at least one embodiment, each graphics multiprocessor 2134 outputs processed tasks to a data crossbar 2140 to provide the processed tasks to another processing cluster 2114 for further processing or to store the processed tasks in an L2 cache, local parallel processor memory, or system memory via the memory crossbar 2116. In at least one embodiment, a PreROP 2142 (pre-raster operations unit) is configured to receive data from the graphics multiprocessor 2134 and direct the data to a ROP unit, which can communicate with a partition unit (e.g., a partition unit) as described herein. Figure 21A In at least one embodiment, the PreROP 2142 unit can perform optimizations for color blending, organize pixel color data, and perform address translation.

[0423] In at least one embodiment, parallel processor 2100 may be used to implement system 100 (see Figure 1 ), Architecture 200 (see Figure 2 ), Figure 300 (see Figure 3A ), Figure 350 (see Figure 3B ), Figure 400 (see Figure 4 ), Flowchart 500 (see Figure 5 ), Flowchart 600 (see Figure 6 ), Flowchart 700 (see Figure 7 ), Example 800 (see Figure 8 ) and / or block diagram 900 (see Figure 9 ). In at least one embodiment, Figure 21A At least a portion of the system depicted in is used to implement a combination Figure 1-9 For example, in at least one embodiment, the system, technique, function, and / or process described herein may be used to implement one or more systems, techniques, functions, and / or processes. Figure 21A At least one component shown or described may be used to enable a UE device to Figure 1-9 One or more techniques, functions and / or processes described in any one of the foregoing may autonomously adjust the priority of information to be transmitted.

[0424] Figure 21D A graphics multiprocessor 2134 is shown in accordance with at least one embodiment. In at least one embodiment, the graphics multiprocessor 2134 is coupled to a pipeline manager 2132 of a processing cluster 2114. In at least one embodiment, the graphics multiprocessor 2134 has an execution pipeline that includes, but is not limited to, an instruction cache 2152, an instruction unit 2154, an address mapping unit 2156, a register file 2158, one or more general purpose graphics processing unit (GPGPU) cores 2162, and one or more load / store units 2166. The GPGPU cores 2162 and the load / store units 2166 are coupled to a cache memory 2172 and a shared memory 2170 via a memory and cache interconnect 2168.

[0425] In at least one embodiment, the instruction cache 2152 receives a stream of instructions to be executed from the pipeline manager 2132. In at least one embodiment, the instructions are cached in the instruction cache 2152 and dispatched for execution by the instruction unit 2154. In one embodiment, the instruction unit 2154 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 2162. 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 2156 can be used to convert addresses in the unified address space into different memory addresses that can be accessed by the load / store unit 2166.

[0426] In at least one embodiment, register file 2158 provides a set of registers for the functional units of graphics multiprocessor 2134. In at least one embodiment, register file 2158 provides temporary storage for operands for the data paths of the functional units (e.g., GPGPU core 2162, load / store unit 2166) connected to graphics multiprocessor 2134. In at least one embodiment, register file 2158 is divided between each functional unit such that a dedicated portion of register file 2158 is allocated to each functional unit. In at least one embodiment, register file 2158 is divided between the different warps being executed by graphics multiprocessor 2134.

[0427] In at least one embodiment, the GPGPU cores 2162 may each include a floating-point unit (FPU) and / or an integer arithmetic logic unit (ALU) for executing instructions of the graphics multiprocessor 2134. The GPGPU cores 2162 may be architecturally similar or may differ in architecture. In at least one embodiment, a first portion of the GPGPU core 2162 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 2134 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.

[0428] In at least one embodiment, the GPGPU core 2162 includes SIMD logic capable of executing a single instruction on multiple sets of data. In one embodiment, the GPGPU core 2162 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.

[0429] In at least one embodiment, the memory and cache interconnect 2168 is an interconnect network that connects each functional unit of the graphics multiprocessor 2134 to the register file 2158 and the shared memory 2170. In at least one embodiment, the memory and cache interconnect 2168 is a crossbar interconnect that allows the load / store unit 2166 to perform load and store operations between the shared memory 2170 and the register file 2158. In at least one embodiment, the register file 2158 can operate at the same frequency as the GPGPU core 2162, resulting in very low latency for data transfers between the GPGPU core 2162 and the register file 2158. In at least one embodiment, the shared memory 2170 can be used to enable communication between threads executing on the functional units within the graphics multiprocessor 2134. In at least one embodiment, the cache memory 2172 can be used, for example, as a data cache to cache texture data communicated between the functional units and the texture unit 2136. In at least one embodiment, the shared memory 2170 can also be used as a program-managed cache. In at least one embodiment, in addition to automatically cached data stored in cache memory 2172, threads executing on GPGPU core 2162 may programmatically store data in shared memory.

[0430] 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 (e.g., internal to the package or chip). In at least one embodiment, regardless of how the GPU is connected, the processor core can assign work to the GPU in the form of a sequence of commands / instructions contained in a work descriptor. In at least one embodiment, the GPU then uses dedicated circuitry / logic to efficiently process these commands / instructions.

[0431] In at least one embodiment, multiprocessor 2134 may be used to implement system 100 (see Figure 1 ), Architecture 200 (see Figure 2 ), Figure 300 (see Figure 3A ), Figure 350 (see Figure 3B ), Figure 400 (see Figure 4 ), Flowchart 500 (see Figure 5 ), Flowchart 600 (see Figure 6), Flowchart 700 (see Figure 7 ), Example 800 (see Figure 8 ) and / or block diagram 900 (see Figure 9 ). In at least one embodiment, Figure 21D At least a portion of the system depicted in is used to implement a combination Figure 1-9 For example, in at least one embodiment, the system, technique, function, and / or process described herein may be used to implement one or more systems, techniques, functions, and / or processes. Figure 21D At least one component shown or described may be used to enable a UE device to Figure 1-9 One or more techniques, functions and / or processes described in any one of the foregoing may autonomously adjust the priority of information to be transmitted.

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

[0433] In at least one embodiment, system 2200 may be used to implement system 100 (see Figure 1 ), Architecture 200 (see Figure 2 ), Figure 300 (see Figure 3A), Figure 350 (see Figure 3B ), Figure 400 (see Figure 4 ), Flowchart 500 (see Figure 5 ), Flowchart 600 (see Figure 6 ), Flowchart 700 (see Figure 7 ), Example 800 (see Figure 8 ) and / or block diagram 900 (see Figure 9 ). In at least one embodiment, Figure 22 At least a portion of the system depicted in is used to implement a combination Figure 1-9 For example, in at least one embodiment, the system, technique, function, and / or process described herein may be used to implement one or more systems, techniques, functions, and / or processes. Figure 22 At least one component shown or described may be used to enable a UE device to Figure 1-9 One or more techniques, functions and / or processes described in any one of the foregoing may autonomously adjust the priority of information to be transmitted.

[0434] Figure 23 2 is a block diagram of a graphics processor 2300 according to at least one embodiment. In at least one embodiment, graphics processor 2300 includes a ring interconnect 2302, a pipeline front end 2304, a media engine 2337, and graphics cores 2380A-2380N. In at least one embodiment, ring interconnect 2302 couples graphics processor 2300 to other processing units, including other graphics processors or one or more general-purpose processor cores. In at least one embodiment, graphics processor 2300 is one of many processors integrated within a multi-core processing system.

[0435] In at least one embodiment, the graphics processor 2300 receives batches of commands via a ring interconnect 2302. In at least one embodiment, the incoming commands are interpreted by a command streamer 2303 in a pipeline front end 2304. In at least one embodiment, the graphics processor 2300 includes scalable execution logic for performing 3D geometry processing and media processing via graphics cores 2380A-2380N. In at least one embodiment, for 3D geometry processing commands, the command streamer 2303 provides the commands to a geometry pipeline 2336. In at least one embodiment, for at least some media processing commands, the command streamer 2303 provides the commands to a video front end 2334, which is coupled to a media engine 2337. In at least one embodiment, the media engine 2337 includes a video quality engine (VQE) 2330 for video and image post-processing, and a multi-format encoding / decoding (MFX) 2333 engine for providing hardware-accelerated media data encoding and decoding. In at least one embodiment, the geometry pipeline 2336 and the media engine 2337 each generate execution threads for thread execution resources provided by at least one graphics core 2380A.

[0436] In at least one embodiment, the graphics processor 2300 includes scalable thread execution resources featuring modular cores 2380A-2380N (sometimes referred to as core slices), each of which has multiple sub-cores 2350A-2350N, 2360A-2360N (sometimes referred to as core sub-slices). In at least one embodiment, the graphics processor 2300 can have any number of graphics cores 2380A-2380N. In at least one embodiment, the graphics processor 2300 includes a graphics core 2380A having at least a first sub-core 2350A and a second sub-core 2360A. In at least one embodiment, the graphics processor 2300 is a low-power processor having a single sub-core (e.g., 2350A). In at least one embodiment, the graphics processor 2300 includes multiple graphics cores 2380A-2380N, each of which includes a set of first sub-cores 2350A-2350N and a set of second sub-cores 2360A-2360N. In at least one embodiment, each of the first sub-cores 2350A-2350N includes at least a first set of execution units 2352A-2352N and media / texture samplers 2354A-2354N. In at least one embodiment, each of the second sub-cores 2360A-2360N includes at least a second set of execution units 2362A-2362N and samplers 2364A-2364N. In at least one embodiment, each of the sub-cores 2350A-2350N, 2360A-2360N shares a set of shared resources 2370A-2370N. In at least one embodiment, the shared resources include shared cache memory and pixel operation logic.

[0437] In at least one embodiment, graphics processor 2300 may be used to implement system 100 (see Figure 1 ), Architecture 200 (see Figure 2 ), Figure 300 (see Figure 3A ), Figure 350 (see Figure 3B ), Figure 400 (see Figure 4 ), Flowchart 500 (see Figure 5 ), Flowchart 600 (see Figure 6 ), Flowchart 700 (see Figure 7 ), Example 800 (see Figure 8 ) and / or block diagram 900 (see Figure 9 ). In at least one embodiment, Figure 23 At least a portion of the system depicted in is used to implement a combination Figure 1-9 For example, in at least one embodiment, the system, technique, function, and / or process described herein may be used to implement one or more systems, techniques, functions, and / or processes. Figure 23 At least one component shown or described may be used to enable a UE device to Figure 1-9One or more techniques, functions and / or processes described in any one of the foregoing may autonomously adjust the priority of information to be transmitted.

[0438] Figure 24 is a block diagram illustrating a microarchitecture for a processor 2400, which may include logic circuitry for executing instructions, according to at least one embodiment. In at least one embodiment, the processor 2400 may execute instructions including x86 instructions, ARM instructions, specialized instructions for application-specific integrated circuits (ASICs), and the like. In at least one embodiment, the processor 2400 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. In at least one embodiment, the MMX registers, available in integer and floating-point form, may operate with packed data elements with Single Instruction Multiple Data ("SIMD") and Streaming SIMD Extensions ("SSE") instructions. In at least one embodiment, the 128-bit-wide XMM registers associated with SSE2, SSE3, SSE4, AVX, or later (generally referred to as "SSEx") technology may store such packed data operands. In at least one embodiment, the processor 2410 may execute instructions to accelerate machine learning or deep learning algorithms, training, or inference.

[0439] In at least one embodiment, the processor 2400 includes an in-order front end ("front end") 2401 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 2401 may include several units. In at least one embodiment, an instruction prefetcher 2426 retrieves instructions from memory and provides the instructions to an instruction decoder 2428, which in turn decodes or interprets the instructions. For example, in at least one embodiment, the instruction decoder 2428 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 2428 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 2430 can assemble the decoded microinstructions into a program-ordered sequence or trace in the microinstruction queue 2434 for execution. In at least one embodiment, when trace cache 2430 encounters a complex instruction, microcode ROM 2432 provides the microinstructions necessary to complete the operation.

[0440] 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 2428 may access the microcode ROM 2432 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 2428. In at least one embodiment, if multiple micro-ops are required to complete the operation, the instruction may be stored in the microcode ROM 2432. In at least one embodiment, the trace cache 2430 references the entry point programmable logic array ("PLA") to determine the correct micro-op pointer for reading the microcode sequence from the microcode ROM 2432 to complete one or more instructions according to at least one embodiment. In at least one embodiment, after the microcode ROM 2432 completes the micro-op sequencing for the instruction, the front end 2401 of the machine may resume fetching micro-ops from the trace cache 2430.

[0441] In at least one embodiment, an out-of-order execution engine ("OOO engine") 2403 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 go down the pipeline and are scheduled for execution. The OOO engine 2403 includes, but is not limited to, an allocator / register renamer 2440, a memory microinstruction queue 2442, an integer / floating-point microinstruction queue 2444, a memory scheduler 2446, a fast scheduler 2402, a slow / general purpose floating-point scheduler ("slow / general purpose FP scheduler") 2404, and a simple floating-point scheduler ("simple FP scheduler") 2406. In at least one embodiment, the fast scheduler 2402, the slow / general purpose floating-point scheduler 2404, and the simple floating-point scheduler 2406 are also collectively referred to as "microinstruction schedulers 2402, 2404, 2406." In at least one embodiment, the allocator / register renamer 2440 allocates the machine buffers and resources required for each microinstruction to execute in sequence. In at least one embodiment, the allocator / register renamer 2440 renames logical registers into entries in the register file. In at least one embodiment, the allocator / register renamer 2440 also allocates an entry for each microinstruction in one of two microinstruction queues: a memory microinstruction queue 2442 for memory operations and an integer / floating-point microinstruction queue 2444 for non-memory operations, preceding the memory scheduler 2446 and the microinstruction schedulers 2402, 2404, 2406. In at least one embodiment, the microinstruction schedulers 2402, 2404, 2406 determine when a microinstruction is ready to execute based on the readiness of their dependent input register operand sources and the availability of the execution resource microinstructions that need to be completed. The fast scheduler 2402 of at least one embodiment can schedule every half of the main clock cycle, while the slow / general floating-point scheduler 2404 and the simple floating-point scheduler 2406 can schedule once per main processor clock cycle. In at least one embodiment, microinstruction schedulers 2402, 2404, 2406 arbitrate dispatch ports to schedule microinstructions for execution.

[0442] In at least one embodiment, execution block 2411 includes, but is not limited to, integer register file / branch network 2408, floating point register file / branch network ("FP register file / branch network") 2410, address generation units ("AGUs") 2412 and 2414, fast arithmetic logic units ("fast ALUs") 2416 and 2418, slow arithmetic logic unit ("slow ALU") 2420, floating point ALU ("FP") 2422, and floating point move unit ("FP move") 2424. In at least one embodiment, integer register file / branch network 2408 and floating point register file / bypass network 2410 are also referred to herein as "register files 2408, 2410." In at least one embodiment, AGUs 2412 and 2414, fast ALUs 2416 and 2418, slow ALU 2420, floating-point ALU 2422, and floating-point move unit 2424 are also referred to herein as "execution units 2412, 2414, 2416, 2418, 2420, 2422, and 2424." In at least one embodiment, execution block 2411 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).

[0443] In at least one embodiment, register files 2408 and 2410 may be arranged between microinstruction schedulers 2402, 2404, and 2406 and execution units 2412, 2414, 2416, 2418, 2420, 2422, and 2424. In at least one embodiment, integer register file / branch network 2408 performs integer operations. In at least one embodiment, floating-point register file / branch network 2410 performs floating-point operations. In at least one embodiment, each of register files 2408 and 2410 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 2408 and 2410 can communicate data with each other. In at least one embodiment, integer register file / branch network 2408 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 2410 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.

[0444] In at least one embodiment, execution units 2412, 2414, 2416, 2418, 2420, 2422, and 2424 can execute instructions. In at least one embodiment, register files 2408 and 2410 store integer and floating-point data operand values ​​required for microinstructions to execute. In at least one embodiment, processor 2400 can include, but is not limited to, any number of execution units 2412, 2414, 2416, 2418, 2420, 2422, and 2424, and combinations thereof. In at least one embodiment, floating-point ALU 2422 and floating-point move unit 2424 can perform floating-point, MMX, SIMD, AVX, SSE, or other operations, including specialized machine learning instructions. In at least one embodiment, floating-point ALU 2422 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 2416 and 2418. In at least one embodiment, fast ALUs 2416 and 2418 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 2420, as slow ALU 2420 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 2412 and 2414. In at least one embodiment, fast ALU 2416, fast ALU 2418, and slow ALU 2420 can perform integer operations on 64-bit data operands. In at least one embodiment, fast ALU 2416, fast ALU 2418, and slow ALU 2420 can be implemented to support various data bit sizes, including 16, 32, 128, 256, and the like. In at least one embodiment, the floating point ALU 2422 and floating point shift unit 2424 can be implemented to support a range of operands having bits of various widths. In at least one embodiment, the floating point ALU 2422 and floating point shift unit 2424 can operate on 128-bit wide packed data operands in conjunction with SIMD and multimedia instructions.

[0445] In at least one embodiment, the microinstruction schedulers 2402, 2404, and 2406 schedule dependent operations before the parent load completes execution. In at least one embodiment, because microinstructions can be speculatively scheduled and executed in processor 2400, processor 2400 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.

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

[0447] In at least one embodiment, processor 2400 may be used to implement system 100 (see Figure 1 ), Architecture 200 (see Figure 2 ), Figure 300 (see Figure 3A ), Figure 350 (see Figure 3B ), Figure 400 (see Figure 4 ), Flowchart 500 (see Figure 5 ), Flowchart 600 (see Figure 6 ), Flowchart 700 (see Figure 7 ), Example 800 (see Figure 8 ) and / or block diagram 900 (see Figure 9 ). In at least one embodiment, Figure 24 At least a portion of the system depicted in is used to implement a combination Figure 1-9 For example, in at least one embodiment, the system, technique, function, and / or process described herein may be used to implement one or more systems, techniques, functions, and / or processes. Figure 24At least one component shown or described may be used to enable a UE device to Figure 1-9 One or more techniques, functions and / or processes described in any one of the foregoing may autonomously adjust the priority of information to be transmitted.

[0448] Figure 25 A block diagram of a processing system according to at least one embodiment is shown. In at least one embodiment, system 2500 includes one or more processors 2502 and one or more graph...

Claims

1. A processor, comprising: One or more circuits configured to enable a user equipment (UE) device to autonomously adjust the priority of information to be transmitted. 2 . The processor of claim 1 , wherein the UE device autonomously adjusts one or more logical channel priority parameters to adjust the priority of information to be transmitted. 3 . The processor of claim 1 , wherein the UE device autonomously adjusts the priority of information to be transmitted based at least in part on one or more packet statistics. The processor of claim 1 , wherein the UE device autonomously adjusts one or more bit rates to adjust a priority of information to be transmitted. 5 . The processor of claim 1 , wherein the UE device autonomously adjusts one or more logical channel priority parameters based at least in part on a timer.

6. The processor of claim 1, wherein the UE device autonomously adjusts one or more logical channel priority parameters based at least in part on a packet error rate.

7. The processor of claim 1 , wherein the UE device autonomously adjusts the priority of information to be transmitted based at least in part on predicting one or more logical channel priority parameters by a neural network.

8. A system comprising: One or more processors configured to enable a user equipment (UE) device to autonomously adjust the priority of information to be transmitted.

9. The system of claim 8, wherein the UE device autonomously adjusts one or more logical channel priority parameters to adjust the priority of information to be transmitted.

10. The system of claim 8, wherein the UE device autonomously adjusts the priority of information to be transmitted based at least in part on one or more packet statistics.

11. The system of claim 8, wherein the UE device autonomously adjusts one or more bit rates to adjust the priority of information to be transmitted.

12. The system of claim 8, wherein the UE device autonomously adjusts one or more logical channel priority parameters based at least in part on a timer.

13. The system of claim 8, wherein the UE device autonomously adjusts one or more logical channel priority parameters based at least in part on a packet error rate.

14. The system of claim 8, wherein the UE device autonomously adjusts the priority of information to be transmitted based at least in part on predicting one or more logical channel priority parameters by a neural network.

15. A method comprising: The user equipment (UE) device is used to autonomously adjust the priority of information to be transmitted.

16. The method according to claim 15, further comprising: One or more logical channel priority parameters are adjusted to adjust the priority of information to be transmitted.

17. The method according to claim 15, further comprising: Inference is performed using a neural network to predict one or more logical channel priority parameters to be used to adjust the priority of information to be transmitted.

18. The method according to claim 15, further comprising: One or more bit rate allocations are adjusted to adjust the priority of information to be transmitted.

19. The method according to claim 15, further comprising: One or more logical channel priority parameters are adjusted based at least in part on the packet error rate.

20. The method of claim 15, further comprising: One or more packet statistics are monitored to indicate autonomous adjustment of the priority of the information.

Images