Electronic device, method for electronic device, and computer readable storage medium

Abstract

The present disclosure provides an electronic device and a method for the electronic device, and a computer readable storage medium. The electronic device comprises: at least one processor; and at least one memory including computer program code, wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the electronic device to perform: determining, for each of a plurality of sensors that transmit data via wireless communication, a priority initial value of a data transmission priority of the sensor, the priority initial value being associated with an applicable scenario; and determining, based on at least the priority initial value, a final priority value of the data transmission priority of the sensor.

Description

Electronic device, method for electronic device, and computer-readable storage medium

[0001] This application claims priority to the Chinese patent application filed with the China Patent Office on December 25, 2023, with application number 202311806375.2 and invention name “Electronic device, method for electronic device and computer-readable storage medium”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of wireless communications, and in particular, to determining the priority of sensor data transmitted via wireless communications, and more particularly, to an electronic device, a method for an electronic device, and a computer-readable storage medium. Background Art

[0003] For example, in an intelligent transportation system, there are multiple onboard sensors in connected vehicles, as well as numerous roadside sensors. For the management and dispatching side of the intelligent transportation system, determining the data transmission priority of these numerous sensors is a critical issue, significantly impacting the efficient and stable operation of the entire intelligent transportation system. Summary of the Invention

[0004] A brief overview of the present disclosure is provided below to provide a basic understanding of certain aspects of the present disclosure. It should be understood that this overview is not an exhaustive overview of the present disclosure. It is not intended to identify key or important aspects of the present disclosure, nor is it intended to limit the scope of the present disclosure. Its purpose is simply to present certain concepts in a simplified form as a prelude to the more detailed description discussed later.

[0005] According to one aspect of the present disclosure, an electronic device is provided, comprising: at least one processor; and at least one memory including computer program code, wherein the at least one memory and the computer program code are configured to, through the at least one processor, enable the electronic device to execute: determining, for each of a plurality of sensors that transmit data via wireless communication, an initial priority value of the data transmission priority of the sensor, the initial priority value being associated with an applicable scenario; and determining, based at least on the initial priority value, a final priority value of the data transmission priority of the sensor.

[0006] According to another aspect of the present disclosure, a method for an electronic device is provided, including: determining, for each sensor of a plurality of sensors that transmit data via wireless communication, an initial priority value of the data transmission priority of the sensor, the initial priority value being associated with an applicable scenario; and determining, based at least on the initial priority value, a final priority value of the data transmission priority of the sensor.

[0007] According to other aspects of the present disclosure, a computer program code and a computer program product for implementing the above-mentioned method for an electronic device, as well as a computer-readable storage medium having the computer program code for implementing the above-mentioned method for an electronic device recorded thereon are also provided.

[0008] The electronic device and method according to the embodiments of the present application can determine the final priority value of sensor data transmission for different applicable scenarios, so that sensor data can be appropriately selected in consideration of the current applicable scenario, which is conducive to improving accuracy and efficiency.

[0009] These and other advantages of the present disclosure will become more apparent through the following detailed description of the preferred embodiments of the present disclosure in conjunction with the accompanying drawings.

[0010] In addition, it should be noted that although the background technology only mentions the determination of sensor data transmission priority in intelligent transportation systems, it does not limit the present application. That is, the scope of application of the present application is not limited to intelligent transportation systems, but can be applied to any situation where there are multiple sensors and the sensor data priority of each sensor needs to be determined. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] In order to further illustrate the above and other advantages and features of the present disclosure, the following is a further detailed description of the specific embodiments of the present disclosure in conjunction with the accompanying drawings. The drawings, together with the detailed description below, are included in this specification and form a part of this specification. Elements with the same function and structure are represented by the same reference numerals. It should be understood that these drawings only depict typical examples of the present disclosure and should not be regarded as limiting the scope of the present disclosure. In the drawings:

[0012] FIG1 shows a functional module block diagram of an electronic device according to an embodiment of the present application;

[0013] FIG2 shows an example of a sensor data transmission priority scenario table in the context of an intelligent transportation system;

[0014] FIG3 shows a functional module block diagram of an electronic device according to an embodiment of the present application;

[0015] Figure 4 shows a classic feedback control architecture;

[0016] FIG5 shows an example of the information flow between the cloud and the vehicle side and the roadside unit (RSU) side when the electronic device is set in the cloud;

[0017] FIG6 shows an example of the information flow between the cloud, the vehicle, and the RSU when the electronic device is provided on the vehicle side;

[0018] FIG7 shows an example of the information flow between the cloud, the vehicle, and the RSU when the electronic device is provided on the RSU;

[0019] FIG8 shows a flowchart of a method for an electronic device according to an embodiment of the present application;

[0020] FIG9 is a block diagram showing an example of a schematic configuration of a server;

[0021] FIG10 is a block diagram showing a first example of a schematic configuration of an eNB or gNB to which the technology of the present disclosure may be applied;

[0022] FIG11 is a block diagram illustrating a second example of a schematic configuration of an eNB or gNB to which the technology of the present disclosure may be applied;

[0023] FIG12 is a block diagram showing an example of a schematic configuration of a smartphone to which the technology of the present disclosure can be applied;

[0024] FIG13 is a block diagram showing an example of a schematic configuration of a car navigation device to which the technology of the present disclosure can be applied; and

[0025] FIG14 is a block diagram of an exemplary structure of a general-purpose personal computer in which the method and / or apparatus and / or system according to the embodiments of the present disclosure may be implemented. DETAILED DESCRIPTION

[0026] Exemplary embodiments of the present disclosure are described below with reference to the accompanying drawings. For the sake of clarity and conciseness, not all features of an actual implementation are described in this specification. However, it should be understood that in the process of developing any such actual implementation, many implementation-specific decisions must be made in order to achieve the developer's specific goals, such as compliance with system and business-related constraints, which may vary from implementation to implementation. In addition, it should be understood that although the development work may be very complex and time-consuming, it is a routine task for those skilled in the art who benefit from the contents of this disclosure.

[0027] It is also necessary to explain here that, in order to avoid obscuring the present disclosure due to unnecessary details, the accompanying drawings only show the device structure and / or processing steps that are closely related to the solution according to the present disclosure, while other details that are not closely related to the present disclosure are omitted.

[0028] <First embodiment>

[0029] In this embodiment, an electronic device 100 is provided for determining the transmission priority of sensor data for different application scenarios. In the following description, the intelligent transportation system will be mainly used as an exemplary application scenario, but as mentioned above, this is not restrictive and is only for the convenience and clarity of description.

[0030] Figure 1 shows a functional module block diagram of an electronic device 100 according to this embodiment. As shown in Figure 1, the electronic device 100 includes: a first determination unit 101, configured to determine an initial priority value of the data transmission priority of the sensor for each of a plurality of sensors that transmit data via wireless communication, where the initial priority value is associated with an applicable scenario; and a second determination unit 102, configured to determine a final priority value of the data transmission priority of the sensor based at least on the initial priority value.

[0031] The first determination unit 101 and the second determination unit 102 can be implemented by one or more processing circuits and at least one memory. The processing circuit can be implemented as a chip, a processor, etc., for example. The at least one memory can be any form of storage device such as RAM, ROM, flash memory, etc. The at least one memory is used to store, for example, computer program code and data required for the processing circuit to perform processing. Furthermore, it should be understood that the various functional units in the electronic device shown in FIG1 are merely logical modules divided according to the specific functions they implement, and are not intended to limit specific implementation methods.

[0032] In the case where the electronic device 100 is applied to an intelligent transportation system, the electronic device 100 can be set on one of the cloud side, the roadside unit (RSU) side and the vehicle side. The cloud side is, for example, the network side, the cloud server side or the edge server side, and the network side can include, for example, one of the core network and the base station side. In addition, the electronic device 100 can also be set on the RSU side or the vehicle side, and the vehicle side mentioned here can be more generally various user devices located on the vehicle and capable of accessing various sensors. For example, in the example of the enhanced Internet of Vehicles business application architecture defined by CCSA, the electronic device 100 can be set in one or more of the central subsystem, the roadside unit (RSU) and the multi-access edge computing platform (MEC).

[0033] It should also be noted that the electronic device 100 can be implemented at the chip level, or it can also be implemented at the device level. For example, the electronic device 100 can work as a server, base station, vehicle or user equipment itself, and may also include external devices such as memory, transceiver (not shown in the figure). The memory can be used to store programs and related data information that need to be executed to implement various functions of the server, base station, vehicle or user equipment. The transceiver may include one or more communication interfaces to support communication with different devices (for example, other servers, base stations, vehicles or user equipment, etc.), and the implementation form of the transceiver is not specifically limited here.

[0034] It should be noted that the ordinal numbers such as first and second in this article are only used for the purpose of distinction and do not represent any meaning of order, priority, etc.

[0035] In addition, the sensors mentioned in this embodiment can be set on one of the cloud, RSU, and vehicle to sense the surrounding environment, traffic conditions, vehicle conditions, etc. Sensors include but are not limited to image sensors, lidar, millimeter wave radar, temperature sensors, etc. Among them, multiple sensors can be distributed across multiple device bodies. For example, multiple sensors can be distributed across different vehicles, or some can be distributed across vehicles and some can be distributed across RSUs, which is not restrictive.

[0036] When the electronic device 100 is applied to an intelligent transportation system, the applicable scenario may be one of multiple traffic scenarios, and examples of traffic scenarios will be given in the following description.

[0037] As an example, the first determination unit 101 may determine the initial priority value based on a pre-built sensor data transmission priority scenario table (hereinafter referred to as the priority scenario table). The priority scenario table may be constructed offline. In the priority scenario table, the initial transmission priority value of the sensor data corresponds one-to-one to the applicable scenario corresponding to the sensor data. The first determination unit 101 may determine the initial priority value of the sensor data by searching the current applicable scenario.

[0038] In addition, in the sensor data transmission priority scenario table, the initial priority value is also associated with the sensor type of the sensor. For example, in the same applicable scenario, sensor data from different types of sensors are assigned different initial priority values.

[0039] The first determination unit 101 may also be configured to dynamically adjust the initial priority value in the sensor data transmission priority scenario table based on signaling interactions with the device body on which the sensor is installed. This can make the priority scenario table more accurate. The sensor data transmission priority scenario table may be device-specific. For example, if the applicable scenario itself changes or the sensor type of the device body changes, the initial priority value may be dynamically adjusted.

[0040] For example, in the sensor data transmission priority scenario table, the initial priority values ​​of various sensors are different from each other, thereby improving the discrimination.

[0041] For ease of understanding, Figure 2 shows an example of a sensor data transmission priority scenario table for an intelligent transportation system. Rows are divided by scenario. In this example, there are two levels of scenarios to facilitate quick table lookup: the first level is abstract traffic scenarios, such as going straight, changing lanes, and intersections, and the second level is specific traffic scenarios, such as following a vehicle, overtaking, and waiting at an intersection. Columns are divided by sensor type. In this example, there are two levels of sensor types to facilitate quick and accurate lookup: the first level categorizes sensors based on whether they are onboard or roadside, and the second level is specific sensor types, such as image sensors, millimeter-wave radars, and lidars. For example, the initial priority values ​​in this table can be jointly determined by experienced traffic managers and drivers, and the value range can be jointly selected by the setters. There are no specific restrictions, but it is important to avoid situations where the initial priority values ​​are identical, so that a certain degree of differentiation is achieved when constructing the table.

[0042] When the electronic device 100 is set in the cloud, the sensor data transmission priority scenario table can be constructed and maintained by the electronic device 100. When the electronic device 100 is set in the RSU end or the vehicle end, the electronic device 100 may further include a communication unit 103 (as shown in FIG3 ), which is configured to obtain a pre-constructed sensor data transmission priority scenario table for determining an initial priority value from the cloud.

[0043] The second determination unit 102 determines the final priority value based on the initial priority value. In this process, the second determination unit 102 can take other factors into consideration based on the initial priority value to make the assessment of the priority more accurate. Other factors include, for example, the communication delay of data transmission, the accuracy of the perception results, etc. Specifically, since the system status, especially the status of the traffic system, is dynamically changing, if the communication delay is too large, the information reflected by the sensor data is no longer meaningful. In addition, the accuracy of the perception result reflects its data quality. If the accuracy is low and the degree of deviation is large, the value of the sensor data is also low.

[0044] Of course, any other factors may also be ignored, and the second determining unit 102 may determine the final priority value based solely on the initial priority value, for example, determining that the final priority value is equal to the initial priority value.

[0045] In one example, the first determination unit 101 is further configured to determine at least one of the communication delay of data transmission from the sensor and the accuracy of the perception result of the sensor, and the second determination unit 102 is configured to determine the final priority value of the sensor based on at least one of the communication delay and the accuracy and the initial priority value.

[0046] For example, the first determination unit 101 can determine the communication delay by interacting with the short byte message between the sensor. Specifically, the electronic device 100, for example, sends short bytes to each other at a higher frequency through a separate communication link and thread resource between the communication unit 103 and the sensor. The short byte message content may only include a timestamp. The first determination unit 101 subtracts the sending timestamp in the received short byte message from the receiving timestamp to obtain the communication delay between the electronic device 100 and the sensor. At regular intervals, all sensors can use the electronic device 100 as the quasi-synchronized system time. The electronic device 100 here can also be called a scheduling end, for example, located on the cloud or network side. Taking into account the instantaneous fluctuations in communication, the median or average value of the communication delay recorded in the last few seconds can be used as the value of the communication delay for the sensor's data transmission.

[0047] The first determination unit 101 can determine the accuracy of the sensor's perception result based on the comparison between the sensor's sensing result for a specific location and the true value. That is, the accuracy of the perception result is determined by calibration. For example, in the scenario of an intelligent transportation system, the true value can be calibrated in advance at a specific location on a specific road. When an intelligent vehicle equipped with a sensor arrives, the perception result of the sensor is uploaded to the electronic device 100. The first determination unit 101 of the electronic device 100 compares the perception result with the calibrated true value to complete the timely refresh of the sensor's perception accuracy. In an intelligent transportation system, if the accuracy of the sensor's perception result is low, that is, the degree of deviation is large, the intelligent vehicle's decision-making, planning and control based on the perception result will result in a large control deviation. The direct result is that the driving safety of the intelligent car cannot be guaranteed. Therefore, it is of great significance to measure the accuracy of the sensor's perception result.

[0048] If at least one of the initial priority value, communication delay, and accuracy of the perception results does not meet their respective predetermined requirements, the second determination unit 102 may determine the final priority value of the sensor as the minimum possible priority value, i.e., set the priority of the sensor's transmission data to the lowest, indicating that the sensor data has very low reference value or essentially no reference value. For example, the minimum possible value may be 0. Specifically, the second determination unit 102 may determine whether the initial priority value, communication delay, and accuracy of the perception results meet their respective predetermined requirements in any order, and if any one factor does not meet its predetermined requirements, the final priority value is determined as the minimum possible priority value, and no further determination is made on the remaining factors.

[0049] For example, the predetermined requirement for the initial priority value includes that the initial priority value must be higher than the predetermined priority value. In other words, the data of the sensor whose initial priority value is lower than the predetermined priority value is not transmitted or used.

[0050] The predetermined priority can be dynamically set based on one or more of the current load, communication status and characteristics of the sensor. In a distributed multi-agent sensor architecture, different sensor nodes may be in different environmental conditions and have different computing capabilities and communication resources. In order to better adapt to this heterogeneity, a personalized minimum priority threshold, that is, the predetermined priority described above, can be dynamically set according to the actual situation of each sensor node. For example, the sensor can periodically report its current load and communication status, such as the current network congestion, to the electronic device 100. The second determination unit 102 (or the first determination unit 101) adjusts the minimum priority thresholds of different sensors based on this information, so as to better adapt to the differences between sensors and thus more finely control the priority of data transmission.

[0051] The predetermined requirement for the communication delay includes that the communication delay is lower than the predetermined delay. As mentioned above, this is because sensor data with excessively large communication delay may not be meaningful in providing effective information.

[0052] The predetermined requirement for accuracy includes accuracy being higher than a predetermined threshold. As mentioned above, this is because sensor data with low accuracy is meaningless or even harmful to correct decision-making, so the accuracy of the sensor data needs to be checked and filtered.

[0053] It should be understood that the order in which the first determining unit 101 determines factors such as the initial priority value, the communication delay, and the accuracy of the perception result is not limited, and the determination of these factors can be performed in any order.

[0054] For example, the second determining unit 102 may be configured to weight the initial priority value based on at least one of communication delay and accuracy to determine the final priority value of the sensor. The second determining unit 102 may determine the final priority value based on the following formula (1).

[0055] Priority final =α1*α2*Priority initial (1)

[0056] Among them, α1 is the weight corresponding to the communication delay, α2 is the weight corresponding to the accuracy, and Priority initial The initial value of the sensor's data transmission priority, Priority final The final priority value for sensor data transmission.

[0057] For example, the second determining unit 102 may be configured to: determine a weight value corresponding to accuracy based on the impact of accuracy on the control error level; and / or determine a weight value corresponding to communication delay based on a linear mapping from communication delay to weight value.

[0058] Specifically, the weight value α1 corresponding to the communication delay can be linearly mapped to [0, 1] within a certain range according to the size of the communication delay value.

[0059] The weight value α2 corresponding to the accuracy can be obtained based on the quantitative evaluation of the impact of perception accuracy on control. Figure 4 shows a classic feedback control architecture, which is applied to intelligent transportation systems to control the vehicle based on the vehicle state with deviation, where x is the actual state of the vehicle, is the biased vehicle state estimate, e is the deviation between the current and desired vehicle states, and u is the control variable. Based on this feedback control architecture, repeated simulations or on-vehicle experiments can be used to determine vehicle control error levels at different sensor data accuracies. Specifically, without loss of generality, assuming that the data deviation follows a Gaussian distribution, a relationship between sensor data accuracy and vehicle control error can be established. For a given deviation level, corresponding to a Gaussian distribution of sensor perception data with a mean of zero and a specific variance, the cumulative probability density of the vehicle's control error at this perception accuracy can be calculated—that is, the probability of keeping the vehicle's tracking error within a certain range. By repeatedly experimenting with varying noise levels, a table of vehicle control error levels at different sensor data accuracies can be obtained. Since the cumulative probability density itself ranges from [0 to 1], it can be directly used as the value of α2 for weighting.

[0060] In addition, the second determining unit 102 may be further configured to dynamically adjust at least one of the weight value corresponding to the communication delay and the weight value corresponding to the accuracy according to actual conditions or requirements. The adjustment may be performed at regular intervals or in response to a corresponding trigger event.

[0061] For example, when communication quality is high, the differences in α1 across sensors are minimal, making it difficult to distinguish sensor data transmission priorities using only the original α2. In this case, α2 can be increased by a certain ratio to improve differentiation. For example, when the accuracy of sensing results is high, the differences in α2 across sensors are minimal, making it difficult to distinguish sensor data transmission priorities using only the original α1. In this case, α1 can be increased by a certain ratio to improve differentiation. For example, when both communication quality and sensing accuracy are high, the differences in α1 and α2 are small, making it difficult to distinguish sensor data transmission priorities using only the original α1 and α2. In this case, α1 and α2 can be increased by a certain ratio to improve differentiation. Furthermore, in specific scenarios and emergencies, the demand for data from sensors at a certain location or type of sensor may increase rapidly and temporarily. In this case, rapid dynamic adjustment can be achieved by simultaneously increasing α1 and α2 for the corresponding sensors. When the demand disappears, α1 and α2 for the corresponding sensors can be adjusted back to normal values.

[0062] After the second determining unit 102 determines the final priority value, the communication unit 103 may send a sensor sharing entity activation instruction to the device corresponding to the sensor based on the final priority value.

[0063] For example, the second determining unit 102 may also determine the sensor for data sharing based on the final priority value, and the communication unit 103 sends a sensor sharing entity activation instruction to the device corresponding to the sensor for data sharing.

[0064] Furthermore, the communication unit 103 may provide the final priority value to the device corresponding to the sensor, so that the device transmits the sensing data based on the final priority value. For example, if the final priority value is lower than the priority value required by the service or other device, the sensing data is not transmitted. For example, the final priority value may be included in the sensor sharing entity activation instruction.

[0065] It should be noted that the operations of the electronic device 100 described above may be performed after receiving the sensing data from the sensor, or may be performed before receiving the sensing data from the sensor, which is not restrictive.

[0066] To facilitate understanding, a schematic diagram of the information flow between the electronic device 100 and the vehicle side in an example scenario of an intelligent transportation system is given below.

[0067] FIG5 shows an example of the information flow between the cloud and the vehicle side and the RSU side when the electronic device 100 is set in the cloud. As shown in FIG5 , HV (Host vehicle) and RV (Remote Vehicle) 1 and RV2 are examples of vehicle sides, and RSU is an example of roadside unit. It should be understood that the number of vehicles and RSUs is not limited to the case shown in the figure. This is only an example. For example, HV is a target vehicle that is equipped with an on-board unit and runs an application, or a vehicle that currently has a demand for sensor data. RV is a background vehicle that can cooperate with the host vehicle to broadcast V2X messages at regular intervals. RSU is a hardware unit installed on the roadside that can realize V2X communication and support V2X applications.

[0068] The HV, RV1, RV2, and RSU report wireless channel quality to the cloud, enabling the electronic device 100 to, for example, determine the communication latency of each sensor's data transmission. The HV, RV1, RV2, and RSU also report sensor characteristics to the cloud, including, for example, the sensor's current load, communication status, characteristics, and sensing results for specific locations used for calibration, so that the electronic device 100 can determine information such as the type and accuracy of each sensor. Furthermore, based on the reports from the HV, RV1, RV2, and RSU, the electronic device 100 can determine or adjust various parameters used in determining initial and final priority values, such as the predetermined thresholds, predetermined requirements, and weights described above. The electronic device 100 establishes and stores a sensor data transmission priority scenario table in the cloud. As previously described, the electronic device 100 also adjusts this sensor data transmission priority scenario table based on signaling interactions between the cloud and the vehicle. Furthermore, as previously described, the electronic device 100 can determine the initial sensor priority value based on this priority scenario table and determine the final sensor priority value based on this initial priority value, as well as the communication latency and the accuracy of the sensing results.

[0069] The electronic device 100 sends a sensor sharing entity activation instruction to each RV and RSU based on the final priority value. For example, the sensor sharing entity activation instruction may include the final priority value of the sensor of the corresponding RV or RSU determined by the electronic device 100, so that the corresponding RV or RSU transmits the perception data based on the final priority value. For example, when the final priority value is lower than the priority value required by the HV, the perception data is not transmitted. In the example of Figure 5, a situation is shown in which only RV1 and RSU share sensor data, while RV2 does not share sensor data, because, for example, the final priority value of the sensor of RV2 is too low. In addition, the electronic device 100 can also determine the sensor to be shared based on the final priority value, and send a sensor sharing entity activation instruction to the device (RV or RSU) corresponding to the sensor to be shared. For example, the electronic device 100 determines that the final priority values ​​of the sensors of RV1 and RSU meet the requirements based on the final priority value so that data sharing can be performed, and therefore only sends a sensor sharing entity activation instruction to RV1 and RSU. After receiving the sensor sharing entity activation instruction, RV1 and RSU confirm that their final priority values ​​meet the requirements and thus send their sensor data to HV.

[0070] FIG6 shows an example of the information flow between the cloud and the vehicle side and the RSU side when the electronic device 100 is located at the HV side. As shown in FIG6, similar to FIG5, HV, RV1, RV2 and RSU report wireless channel quality and sensor feature to the cloud. The HV can obtain at least a portion of these reports from the cloud, or the HV can obtain corresponding reports from the RV and RSU via instructions from the cloud, or the HV directly obtains corresponding reports from the RV and RSU. The electronic device 100 can determine the communication delay of each sensor, the accuracy of the perception results, etc. based on the obtained reports. In addition, the electronic device 100 obtains the sensor data transmission priority scenario table from the cloud, and determines the initial priority value of each sensor based on the priority scenario table. The electronic device 100 determines the final priority value of each sensor based on the initial priority value, communication delay, accuracy of the perception results, etc. of each sensor.

[0071] Subsequently, similar to Figure 5, HV can determine the sensors to be shared based on the final priority value, and send a sensor sharing entity activation instruction to the device (RV or RSU) corresponding to the sensor to be shared. Here, HV can send the sensor sharing entity activation instruction via the cloud. In the case where only RV1 and RSU receive the sensor sharing entity activation instruction, RV1 and RSU send their sensor data to HV, and RV2 does not share its sensor data. In addition, HV can also send the final priority value of the sensor of the corresponding RV or RSU determined as a sensor sharing entity activation instruction to RV and RSU. In this case, RV1, RV2 and RSU all receive the sensor sharing entity activation instruction, but when it is determined that the final priority value is lower than the priority value required by HV, the transmission of perception data is not performed.

[0072] Figure 7 shows an example of the information flow between the cloud, the vehicle, and the RSU, when electronic device 100 is located at the RSU. The only difference is that the RSU obtains the sensor data transmission priority scenario table from the cloud and determines the final priority value. The specific implementation of this information flow will be briefly described below, and details similar to those in Figures 5 and 6 will not be repeated.

[0073] HV, RV1, RV2 and RSU report wireless channel quality and sensor feature reports to the cloud. RSU can obtain at least part of these reports from the cloud, or RSU can obtain corresponding reports from RV and RSU via instructions from the cloud, or RSU directly obtains corresponding reports from RV and RSU. The electronic device 100 on the RSU can determine the communication delay of each sensor, the accuracy of the perception results, etc. based on the obtained reports. In addition, the electronic device 100 determines the initial priority value of each sensor based on the priority scenario table obtained from the cloud, and determines the final priority value of each sensor based on the initial priority value, communication delay, accuracy of the perception results, etc.

[0074] The electronic device 100 activates the sensor sharing entity based on the determined final priority value. For example, the sensors to be shared can be determined on the RSU side based on the determined final priority value, and a sensor sharing entity activation instruction can be sent to the devices corresponding to these sensors. In the example of Figure 7, the devices corresponding to the sensors to be shared include RV1 and the RSU itself, and the RSU can send a sensor sharing entity activation instruction to RV1. In addition, the RSU can send the determined final priority value of the sensor of the corresponding RV as a sensor sharing entity activation instruction to the RV. In this case, both RV1 and RV2 receive the sensor sharing entity activation instruction, but for example, because RV2 determines that its final priority value is lower than the priority value required by the HV, the perception data is not transmitted. Similarly, the RSU can send the sensor sharing entity activation instruction via the cloud.

[0075] It should be noted that the information flows shown in FIG. 5 to FIG. 7 are merely exemplary and not restrictive.

[0076] In summary, the electronic device 100 according to this embodiment is capable of determining the final priority value for sensor data transmission based on different applicable scenarios, thereby appropriately selecting sensor data based on the current applicable scenario, thereby improving accuracy and efficiency. Furthermore, when determining the final priority value, the electronic device 100 can also take factors such as communication latency and the accuracy of the sensor data into account and dynamically adjust the value, thereby making the priority determination more accurate.

[0077] <Second embodiment>

[0078] In the process of describing the electronic device in the above embodiments, it is obvious that some processes or methods are also disclosed. Below, an overview of these methods is given without repeating some of the details already discussed above, but it should be noted that although these methods are disclosed in the process of describing the electronic device, these methods do not necessarily use the components described or are not necessarily performed by those components. For example, the embodiments of the electronic device can be partially or completely implemented using hardware and / or firmware, and the methods for the electronic device discussed below can be completely implemented by a computer-executable program, although these methods can also use the hardware and / or firmware of the electronic device.

[0079] Figure 8 shows a flowchart of a method for an electronic device according to an embodiment of the present application. As shown in Figure 8, the method includes: for each sensor of a plurality of sensors that transmit data via wireless communication, determining an initial priority value of the data transmission priority of the sensor, the initial priority value being associated with an applicable scenario (S11); and determining a final priority value of the data transmission priority of the sensor based at least on the initial priority value (S12). The method can be performed on the electronic device side. In the scenario of an intelligent transportation system, the electronic device can be set on one of the cloud, RSU side, and vehicle side as described above. The cloud is, for example, a network side, a cloud server side, or an edge server side, and the network side can, for example, include one of a core network and a base station side. The vehicle side can more generally be various user devices located on the vehicle and capable of accessing various sensors. The sensor can be set on one of the cloud, RSU side, and vehicle side. The applicable scenario can be one of multiple traffic scenarios.

[0080] Among them, multiple sensors can be distributed on multiple device bodies.

[0081] In one example, in step S11, the initial priority value may be determined based on a pre-established sensor data transmission priority scenario table. For example, in the sensor data transmission priority scenario table, the initial priority value may also be associated with the sensor type of the sensor. For example, the sensor data transmission priority scenario table may be device-specific. In the sensor data transmission priority scenario table, the initial priority value of each sensor may be set to be different from one another.

[0082] In addition, although not shown in the figure, the above method may further include dynamically adjusting the initial priority value in the sensor data transmission priority scenario table based on signaling interaction with the device body on which the sensor is set.

[0083] In step S11, at least one of a communication delay of data transmission from the sensor and an accuracy of a sensing result of the sensor may also be determined. Furthermore, in step S12, a final priority value of the sensor may be determined based on at least one of the communication delay and the accuracy and the initial priority value.

[0084] For example, the communication latency can be determined by exchanging short byte messages with the sensor. The accuracy can be determined based on comparing the sensor's sensing result for a specific location with the true value.

[0085] For example, when at least one of the communication delay, the accuracy, and the initial priority value does not meet respective predetermined requirements, the final priority value of the sensor is determined to be the minimum possible priority value.

[0086] It should be noted that the order in which the steps for determining the initial priority value, communication delay, and accuracy are executed is not restricted and can be performed in any order. Accordingly, the order in which the determination of whether the initial priority value, communication delay, and accuracy meet their respective predetermined requirements is also not restricted and can be performed in any order. For example, if one of the initial priority value, communication delay, or accuracy does not meet its predetermined requirements, the final priority value of the sensor is determined to be the minimum possible priority value, and no further determination of whether the remaining factors meet the predetermined requirements is performed.

[0087] For example, in step S12, the initial priority value may be weighted based on at least one of communication delay and accuracy to determine the final priority value of the sensor. For example, the weight value corresponding to the accuracy may be determined based on the impact of the accuracy on the control error level; and / or the weight value corresponding to the communication delay may be determined based on a linear mapping from the communication delay to the weight value.

[0088] At least one of the weight values ​​corresponding to communication delay and accuracy can also be dynamically adjusted based on actual conditions or requirements. For example, the predetermined requirement for communication delay includes that the communication delay is less than a predetermined delay, the predetermined requirement for accuracy includes that the accuracy is greater than a predetermined threshold, and the predetermined requirement for the initial priority value includes that the initial priority value is greater than a predetermined priority value. The predetermined priority value can be dynamically set based on one or more of the current load, communication status, and characteristics of the sensor.

[0089] In addition, as shown in FIG8 , the above method may further include step S13 : sending a sensor sharing entity activation instruction to a device corresponding to the sensor based on the final priority value.

[0090] For example, the final priority value may be included in a sensor sharing entity activation instruction and provided to a device corresponding to the sensor, so that the device transmits the sensing data based on the final priority value.

[0091] Alternatively, the sensor to be shared with may be determined based on the final priority value, and a sensor sharing entity activation instruction may be sent to a device corresponding to the sensor to be shared with.

[0092] In addition, when the electronic device is set on the RSU segment or the vehicle end, the above method also includes the following steps: obtaining a pre-built sensor data transmission priority scenario table for determining the initial priority value from the cloud.

[0093] Although not shown in Figure 8, the above method may further include a step before step S11: receiving data from the sensor. That is, the determination of the final priority value may be performed before or after receiving the data, which is not restrictive.

[0094] The above method corresponds to the electronic device 100 in the first embodiment, and the relevant detailed description has been given in the first embodiment and will not be repeated here.

[0095] The technology of the present disclosure can be applied to various products.

[0096] For example, the electronic device 100 can be implemented as any type of server, such as a tower server, a rack server, and a blade server. The electronic device 100 can be a control module installed on the server (such as an integrated circuit module including a single chip, and a card or blade inserted into a slot of a blade server).

[0097] In addition, the electronic device 100 can also be implemented as various base stations. The base station can be implemented as any type of evolved Node B (eNB) or gNB (5G base station). eNB includes, for example, macro eNB and small eNB. Small eNB can be an eNB that covers a cell smaller than a macro cell, such as a pico eNB, micro eNB, and home (femto) eNB. Similar situations can also be encountered for gNB. Alternatively, the base station can be implemented as any other type of base station, such as a NodeB and a base transceiver station (BTS). The base station may include: a main body (also referred to as a base station device) configured to control wireless communications; and one or more remote radio heads (RRHs) located at a different place from the main body. In addition, various types of user equipment can work as a base station by temporarily or semi-permanently performing base station functions.

[0098] The electronic device 100 can be implemented as various user devices. The user device can be implemented as a mobile terminal (such as a smartphone, a tablet personal computer (PC), a notebook PC, a portable game terminal, a portable / dongle-type mobile router, and a digital camera) or an in-vehicle terminal (such as a car navigation device). The user device can also be implemented as a terminal that performs machine-to-machine (M2M) communication (also known as a machine type communication (MTC) terminal). In addition, the user device can be a wireless communication module (such as an integrated circuit module including a single chip) installed on each of the above terminals.

[0099] [Application examples about servers]

[0100] 9 is a block diagram illustrating an example of a schematic configuration of a server 700 to which the technology of the present disclosure may be applied. The server 700 includes a processor 701 , a memory 702 , a storage device 703 , a network interface 704 , and a bus 706 .

[0101] The processor 701 may be, for example, a central processing unit (CPU) or a digital signal processor (DSP), and controls the functions of the server 700. The memory 702 includes a random access memory (RAM) and a read-only memory (ROM), and stores data and programs executed by the processor 701. The storage device 703 may include a storage medium such as a semiconductor memory and a hard disk.

[0102] The network interface 704 is a wired communication interface for connecting the server 700 to a wired communication network 705. The wired communication network 705 may be a core network such as an evolved packet core (EPC) or a packet data network (PDN) such as the Internet.

[0103] The bus 706 connects the processor 701, the memory 702, the storage device 703, and the network interface 704 to each other. The bus 706 may include two or more buses each having a different speed (such as a high-speed bus and a low-speed bus).

[0104] In the server 700 shown in FIG9 , the first determination unit 101, the second determination unit 102, and the communication unit 103 of the electronic device 100 may be implemented by the processor 701. For example, the processor 701 may determine the final priority value of the sensor data transmission and activate sensor data sharing by executing the functions of the first determination unit 101, the second determination unit 102, and the communication unit 103.

[0105] [Application examples for base stations]

[0106] (First application example)

[0107] Figure 10 is a block diagram illustrating a first example of a schematic configuration of an eNB or gNB to which the techniques of this disclosure can be applied. Note that the following description uses an eNB as an example, but is equally applicable to gNBs. An eNB 800 includes one or more antennas 810 and a base station device 820. The base station device 820 and each antenna 810 can be connected to each other via an RF cable.

[0108] Each of the antennas 810 includes a single or multiple antenna elements (such as multiple antenna elements included in a multiple-input multiple-output (MIMO) antenna) and is used for base station device 820 to transmit and receive wireless signals. As shown in FIG10 , eNB 800 may include multiple antennas 810. For example, multiple antennas 810 may be compatible with multiple frequency bands used by eNB 800. Although FIG10 shows an example in which eNB 800 includes multiple antennas 810, eNB 800 may also include a single antenna 810.

[0109] The base station device 820 includes a controller 821 , a memory 822 , a network interface 823 , and a wireless communication interface 825 .

[0110] The controller 821 may be, for example, a CPU or a DSP, and operates various functions of the higher layers of the base station device 820. For example, the controller 821 generates data packets based on the data in the signal processed by the wireless communication interface 825, and transmits the generated packets via the network interface 823. The controller 821 may bundle data from multiple baseband processors to generate bundled packets, and transmit the generated bundled packets. The controller 821 may have logic functions for performing the following controls: the control may be radio resource control, radio bearer control, mobility management, admission control, and scheduling. The control may be performed in conjunction with a nearby eNB or core network node. The memory 822 includes RAM and ROM, and stores programs executed by the controller 821 and various types of control data (such as a terminal list, transmission power data, and scheduling data).

[0111] The network interface 823 is a communication interface for connecting the base station device 820 to the core network 824. The controller 821 can communicate with the core network node or another eNB via the network interface 823. In this case, the eNB 800 and the core network node or other eNBs can be connected to each other through a logical interface (such as an S1 interface and an X2 interface). The network interface 823 can also be a wired communication interface or a wireless communication interface for a wireless backhaul line. If the network interface 823 is a wireless communication interface, the network interface 823 can use a higher frequency band for wireless communication than the frequency band used by the wireless communication interface 825.

[0112] The wireless communication interface 825 supports any cellular communication scheme, such as Long Term Evolution (LTE) and LTE-Advanced, and provides wireless connectivity to terminals located in the cell of the eNB 800 via the antenna 810. The wireless communication interface 825 may typically include, for example, a baseband (BB) processor 826 and RF circuitry 827. The BB processor 826 can perform various signal processing functions, such as encoding / decoding, modulation / demodulation, and multiplexing / demultiplexing, and performs various types of signal processing for layers such as Layer 1 (L1), Medium Access Control (MAC), Radio Link Control (RLC), and Packet Data Convergence Protocol (PDCP). In place of the controller 821, the BB processor 826 may have some or all of the aforementioned logical functions. The BB processor 826 may be a memory that stores communication control programs, or a module including a processor configured to execute programs and associated circuitry. Program updates can modify the functionality of the BB processor 826. This module may be a card or blade inserted into a slot in the base station device 820. Alternatively, the module may be a chip mounted on the card or blade. Meanwhile, the RF circuit 827 may include, for example, a mixer, a filter, and an amplifier, and transmit and receive wireless signals via the antenna 810 .

[0113] As shown in FIG10 , the wireless communication interface 825 may include multiple BB processors 826. For example, multiple BB processors 826 may be compatible with multiple frequency bands used by the eNB 800. As shown in FIG10 , the wireless communication interface 825 may include multiple RF circuits 827. For example, multiple RF circuits 827 may be compatible with multiple antenna elements. Although FIG10 illustrates an example in which the wireless communication interface 825 includes multiple BB processors 826 and multiple RF circuits 827, the wireless communication interface 825 may also include a single BB processor 826 or a single RF circuit 827.

[0114] In the eNB 800 shown in FIG10 , the communication unit 103 and transceiver of the electronic device 100 may be implemented by the wireless communication interface 825. At least a portion of the functionality may also be implemented by the controller 821. For example, the controller 821 may determine the final priority value for sensor data transmission and activate sensor data sharing by executing the functions of the first determination unit 101, the second determination unit 102, and the communication unit 103.

[0115] (Second application example)

[0116] FIG11 is a block diagram illustrating a second example of a schematic configuration of an eNB or gNB to which the techniques of this disclosure can be applied. Note that similarly, the following description uses an eNB as an example, but is equally applicable to a gNB. An eNB 830 includes one or more antennas 840, a base station device 850, and an RRH 860. The RRH 860 and each antenna 840 can be connected to each other via an RF cable. The base station device 850 and the RRH 860 can be connected to each other via a high-speed line such as an optical fiber cable.

[0117] Each of the antennas 840 includes a single or multiple antenna elements (such as multiple antenna elements included in a MIMO antenna) and is used for RRH 860 to transmit and receive wireless signals. As shown in FIG11 , eNB 830 may include multiple antennas 840. For example, multiple antennas 840 may be compatible with multiple frequency bands used by eNB 830. Although FIG11 shows an example in which eNB 830 includes multiple antennas 840, eNB 830 may also include a single antenna 840.

[0118] Base station device 850 includes a controller 851, a memory 852, a network interface 853, a wireless communication interface 855, and a connection interface 857. Controller 851, memory 852, and network interface 853 are the same as controller 821, memory 822, and network interface 823 described with reference to FIG.

[0119] The wireless communication interface 855 supports any cellular communication scheme (such as LTE and LTE-Advanced) and provides wireless communication to terminals located in the sector corresponding to the RRH 860 via the RRH 860 and the antenna 840. The wireless communication interface 855 may generally include, for example, a BB processor 856. The BB processor 856 is the same as the BB processor 826 described with reference to FIG. 10, except that the BB processor 856 is connected to the RF circuit 864 of the RRH 860 via the connection interface 857. As shown in FIG. 11, the wireless communication interface 855 may include multiple BB processors 856. For example, the multiple BB processors 856 may be compatible with multiple frequency bands used by the eNB 830. Although FIG. 11 shows an example in which the wireless communication interface 855 includes multiple BB processors 856, the wireless communication interface 855 may also include a single BB processor 856.

[0120] The connection interface 857 is an interface for connecting the base station device 850 (wireless communication interface 855) to the RRH 860. The connection interface 857 may also be a communication module for connecting the base station device 850 (wireless communication interface 855) to the RRH 860 for communication in the high-speed line.

[0121] The RRH 860 includes a connection interface 861 and a wireless communication interface 863 .

[0122] The connection interface 861 is an interface for connecting the RRH 860 (wireless communication interface 863) to the base station device 850. The connection interface 861 may also be a communication module for communication in the above-mentioned high-speed line.

[0123] The wireless communication interface 863 transmits and receives wireless signals via the antenna 840. The wireless communication interface 863 may generally include, for example, an RF circuit 864. The RF circuit 864 may include, for example, a mixer, a filter, and an amplifier, and transmits and receives wireless signals via the antenna 840. As shown in FIG11 , the wireless communication interface 863 may include multiple RF circuits 864. For example, multiple RF circuits 864 may support multiple antenna elements. Although FIG11 shows an example in which the wireless communication interface 863 includes multiple RF circuits 864, the wireless communication interface 863 may also include a single RF circuit 864.

[0124] In the eNB 830 shown in FIG11 , the communication unit 103 and transceiver of the electronic device 100 may be implemented by the wireless communication interface 855 and / or the wireless communication interface 863. At least a portion of the functionality may also be implemented by the controller 851. For example, the controller 851 may determine the final priority value for sensor data transmission and activate sensor data sharing by executing the functions of the first determination unit 101, the second determination unit 102, and the communication unit 103.

[0125] [Application examples on user devices]

[0126] (First application example)

[0127] 12 is a block diagram showing an example of a schematic configuration of a smartphone 900 to which the technology of the present disclosure can be applied. The smartphone 900 includes a processor 901, a memory 902, a storage device 903, an external connection interface 904, a camera 906, a sensor 907, a microphone 908, an input device 909, a display device 910, a speaker 911, a wireless communication interface 912, one or more antenna switches 915, one or more antennas 916, a bus 917, a battery 918, and an auxiliary controller 919.

[0128] The processor 901 may be, for example, a CPU or a system on a chip (SoC), and controls the functions of the application layer and other layers of the smartphone 900. The memory 902 includes RAM and ROM, and stores data and programs executed by the processor 901. The storage device 903 may include storage media such as semiconductor memories and hard disks. The external connection interface 904 is an interface for connecting external devices (such as memory cards and universal serial bus (USB) devices) to the smartphone 900.

[0129] The camera 906 includes an image sensor such as a charge coupled device (CCD) and a complementary metal oxide semiconductor (CMOS) and generates a captured image. The sensor 907 may include a group of sensors such as a measurement sensor, a gyroscope sensor, a geomagnetic sensor, and an acceleration sensor. The microphone 908 converts the sound input to the smartphone 900 into an audio signal. The input device 909 includes, for example, a touch sensor, a keypad, a keyboard, a button, or a switch configured to detect a touch on the screen of the display device 910, and receives an operation or information input from the user. The display device 910 includes a screen such as a liquid crystal display (LCD) and an organic light emitting diode (OLED) display and displays an output image of the smartphone 900. The speaker 911 converts the audio signal output from the smartphone 900 into sound.

[0130] The wireless communication interface 912 supports any cellular communication scheme (such as LTE and LTE-Advanced) and performs wireless communications. The wireless communication interface 912 may typically include, for example, a BB processor 913 and an RF circuit 914. The BB processor 913 may perform, for example, encoding / decoding, modulation / demodulation, and multiplexing / demultiplexing, and may also perform various types of signal processing for wireless communications. Meanwhile, the RF circuit 914 may include, for example, mixers, filters, and amplifiers, and transmit and receive wireless signals via an antenna 916. Note that while the figure shows a scenario where one RF link is connected to one antenna, this is merely illustrative, and also encompasses scenarios where one RF link is connected to multiple antennas via multiple phase shifters. The wireless communication interface 912 may be a chip module on which the BB processor 913 and RF circuit 914 are integrated. As shown in FIG12 , the wireless communication interface 912 may include multiple BB processors 913 and multiple RF circuits 914. While FIG12 illustrates an example in which the wireless communication interface 912 includes multiple BB processors 913 and multiple RF circuits 914, the wireless communication interface 912 may also include a single BB processor 913 or a single RF circuit 914.

[0131] In addition, in addition to the cellular communication scheme, the wireless communication interface 912 can support other types of wireless communication schemes, such as a short-range wireless communication scheme, a near-field communication scheme, and a wireless local area network (LAN) scheme. In this case, the wireless communication interface 912 may include a BB processor 913 and an RF circuit 914 for each wireless communication scheme.

[0132] Each of the antenna switches 915 switches a connection destination of the antenna 916 between a plurality of circuits (eg, circuits for different wireless communication schemes) included in the wireless communication interface 912 .

[0133] Each of the antennas 916 includes a single or multiple antenna elements (such as multiple antenna elements included in a MIMO antenna) and is used for transmitting and receiving wireless signals via the wireless communication interface 912. As shown in FIG12 , the smartphone 900 may include multiple antennas 916. Although FIG12 shows an example in which the smartphone 900 includes multiple antennas 916, the smartphone 900 may also include a single antenna 916.

[0134] In addition, the smartphone 900 may include an antenna 916 for each wireless communication scheme. In this case, the antenna switch 915 may be omitted from the configuration of the smartphone 900.

[0135] The bus 917 connects the processor 901, the memory 902, the storage device 903, the external connection interface 904, the camera 906, the sensor 907, the microphone 908, the input device 909, the display device 910, the speaker 911, the wireless communication interface 912, and the auxiliary controller 919. The battery 918 supplies power to the various blocks of the smartphone 900 shown in FIG12 via feeders, which are partially shown as dotted lines in the figure. The auxiliary controller 919 operates the minimum necessary functions of the smartphone 900, for example, in sleep mode.

[0136] In the smartphone 900 shown in FIG12 , the communication unit 103 and the transceiver of the electronic device 100 may be implemented by the wireless communication interface 912. At least a portion of the functionality may also be implemented by the processor 901 or the auxiliary controller 919. For example, the processor 901 or the auxiliary controller 919 may determine the final priority value for sensor data transmission and activate sensor data sharing by executing the functions of the first determination unit 101, the second determination unit 102, and the communication unit 103.

[0137] (Second application example)

[0138] 13 is a block diagram showing an example of a schematic configuration of a car navigation device 920 to which the technology of the present disclosure can be applied. The car navigation device 920 includes a processor 921, a memory 922, a global positioning system (GPS) module 924, a sensor 925, a data interface 926, a content player 927, a storage medium interface 928, an input device 929, a display device 930, a speaker 931, a wireless communication interface 933, one or more antenna switches 936, one or more antennas 937, and a battery 938.

[0139] The processor 921 may be, for example, a CPU or an SoC, and controls a navigation function and other functions of the car navigation apparatus 920. The memory 922 includes a RAM and a ROM, and stores data and programs executed by the processor 921.

[0140] The GPS module 924 measures the position (such as latitude, longitude, and altitude) of the car navigation device 920 using GPS signals received from GPS satellites. The sensor 925 may include a group of sensors such as a gyroscope sensor, a geomagnetic sensor, and an air pressure sensor. The data interface 926 is connected to, for example, the in-vehicle network 941 via an unillustrated terminal and acquires data generated by the vehicle (such as vehicle speed data).

[0141] The content player 927 reproduces content stored in a storage medium (such as a CD or DVD) inserted into the storage medium interface 928. The input device 929 includes, for example, a touch sensor, button, or switch configured to detect a touch on the screen of the display device 930, and receives an operation or information input from the user. The display device 930 includes a screen such as an LCD or OLED display and displays an image of a navigation function or reproduced content. The speaker 931 outputs the sound of the navigation function or the reproduced content.

[0142] The wireless communication interface 933 supports any cellular communication scheme (such as LTE and LTE-Advanced) and performs wireless communication. The wireless communication interface 933 may generally include, for example, a BB processor 934 and an RF circuit 935. The BB processor 934 may perform, for example, encoding / decoding, modulation / demodulation, and multiplexing / demultiplexing, and perform various types of signal processing for wireless communication. Meanwhile, the RF circuit 935 may include, for example, a mixer, a filter, and an amplifier, and transmit and receive wireless signals via an antenna 937. The wireless communication interface 933 may also be a chip module on which the BB processor 934 and the RF circuit 935 are integrated. As shown in Figure 13, the wireless communication interface 933 may include multiple BB processors 934 and multiple RF circuits 935. Although Figure 13 shows an example in which the wireless communication interface 933 includes multiple BB processors 934 and multiple RF circuits 935, the wireless communication interface 933 may also include a single BB processor 934 or a single RF circuit 935.

[0143] In addition, in addition to the cellular communication scheme, the wireless communication interface 933 can support other types of wireless communication schemes, such as a short-range wireless communication scheme, a near field communication scheme, and a wireless LAN scheme. In this case, for each wireless communication scheme, the wireless communication interface 933 can include a BB processor 934 and an RF circuit 935.

[0144] Each of the antenna switches 936 switches a connection destination of the antenna 937 between a plurality of circuits included in the wireless communication interface 933 , such as circuits for different wireless communication schemes.

[0145] Each of the antennas 937 includes a single or multiple antenna elements (such as multiple antenna elements included in a MIMO antenna) and is used for transmitting and receiving wireless signals via the wireless communication interface 933. As shown in FIG13, the car navigation device 920 may include multiple antennas 937. Although FIG13 shows an example in which the car navigation device 920 includes multiple antennas 937, the car navigation device 920 may also include a single antenna 937.

[0146] Furthermore, the car navigation device 920 may include an antenna 937 for each wireless communication scheme. In this case, the antenna switch 936 may be omitted from the configuration of the car navigation device 920.

[0147] The battery 938 supplies power to the respective blocks of the car navigation device 920 shown in Fig. 13 via a feeder line, which is partially shown as a dotted line in the figure. The battery 938 accumulates the power supplied from the vehicle.

[0148] In the car navigation device 920 shown in FIG13 , the communication unit 103 and transceiver of the electronic device 100 may be implemented by the wireless communication interface 933. At least a portion of the functionality may also be implemented by the processor 921. For example, the processor 921 may determine the final priority value for sensor data transmission and activate sensor data sharing by executing the functions of the first determination unit 101, the second determination unit 102, and the communication unit 103.

[0149] The technology of the present disclosure can also be implemented as an in-vehicle system (or vehicle) 940 including a car navigation device 920, an in-vehicle network 941, and one or more blocks of a vehicle module 942. The vehicle module 942 generates vehicle data (such as vehicle speed, engine speed, and fault information) and outputs the generated data to the in-vehicle network 941.

[0150] The basic principles of the present disclosure are described above in conjunction with specific embodiments. However, it should be pointed out that for those skilled in the art, it is understandable that all or any steps or components of the methods and devices of the present disclosure can be implemented in any computing device (including a processor, storage medium, etc.) or a network of computing devices in the form of hardware, firmware, software, or a combination thereof. This can be achieved by those skilled in the art using their basic circuit design knowledge or basic programming skills after reading the description of the present disclosure.

[0151] Furthermore, the present disclosure also provides a program product storing machine-readable instruction codes. When the instruction codes are read and executed by a machine, the method according to the embodiment of the present disclosure can be executed.

[0152] Accordingly, the storage medium for carrying the program product storing the machine-readable instruction code is also included in the disclosure of the present invention, including but not limited to a floppy disk, an optical disk, a magneto-optical disk, a memory card, a memory stick, and the like.

[0153] When the present disclosure is implemented through software or firmware, the programs constituting the software are installed from a storage medium or a network to a computer with a dedicated hardware structure (such as the general-purpose computer 1400 shown in Figure 14). When various programs are installed on the computer, it can perform various functions, etc.

[0154] In FIG14 , a central processing unit (CPU) 1401 executes various processes according to a program stored in a read-only memory (ROM) 1402 or a program loaded from a storage section 1408 to a random access memory (RAM) 1403. In the RAM 1403, data required when the CPU 1401 executes various processes, etc., is also stored as needed. The CPU 1401, the ROM 1402, and the RAM 1403 are connected to each other via a bus 1404. An input / output interface 1405 is also connected to the bus 1404.

[0155] The following components are connected to the input / output interface 1405: an input section 1406 (including a keyboard, a mouse, etc.), an output section 1407 (including a display such as a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and speakers, etc.), a storage section 1408 (including a hard disk, etc.), and a communication section 1409 (including a network interface card such as a LAN card, a modem, etc.). The communication section 1409 performs communication processing via a network such as the Internet. A drive 1410 may also be connected to the input / output interface 1405 as needed. A removable medium 1411 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc. is installed in the drive 1410 as needed, so that a computer program read therefrom is installed in the storage section 1408 as needed.

[0156] In the case of realizing the above-described series of processing by software, a program constituting the software is installed from a network such as the Internet or a storage medium such as the removable medium 1411 .

[0157] It should be understood by those skilled in the art that such storage media is not limited to the removable medium 1411 shown in FIG. 14 , which stores the program and is distributed separately from the device to provide the program to the user. Examples of the removable medium 1411 include magnetic disks (including floppy disks (registered trademark)), optical disks (including compact disk read-only memories (CD-ROMs) and digital versatile disks (DVDs)), magneto-optical disks (including minidiscs (MDs) (registered trademark)), and semiconductor memories. Alternatively, the storage medium may be the ROM 1402, a hard disk included in the storage section 1408, or the like, in which the program is stored and distributed to the user together with the device containing the program.

[0158] It should also be noted that in the apparatus, method, and system of the present disclosure, each component or step can be decomposed and / or recombined. Such decomposition and / or recombination should be regarded as equivalent solutions of the present disclosure. Furthermore, the steps of performing the above series of processes can naturally be performed in chronological order according to the order of description, but do not necessarily need to be performed in chronological order. Certain steps can be performed in parallel or independently of each other.

[0159] Finally, it should be noted that the terms "comprises," "includes," or any other variations thereof are intended to encompass non-exclusive inclusion, such that a process, method, article, or apparatus that includes a list of elements includes not only those elements but also other elements not explicitly listed, or elements inherent to such process, method, article, or apparatus. Furthermore, in the absence of further limitations, an element defined by the phrase "comprises a ..." does not preclude the presence of additional identical elements in the process, method, article, or apparatus that includes the element.

[0160] Although the embodiments of the present disclosure have been described in detail above with reference to the accompanying drawings, it should be understood that the embodiments described above are merely illustrative of the present disclosure and are not intended to limit the present disclosure. Those skilled in the art will appreciate that various modifications and variations can be made to the above embodiments without departing from the spirit and scope of the present disclosure. Therefore, the scope of the present disclosure is solely defined by the appended claims and their equivalents.

Claims

1. An electronic device, comprising: at least one processor; and at least one memory, including computer program code, wherein the at least one memory and the computer program code are configured to, by means of the at least one processor, cause the electronic device to perform: for each of a plurality of sensors that transmit data via wireless communication, determining an initial priority value of the data transmission priority of the sensor, the initial priority value being associated with an applicable scenario; and determining a final priority value of the data transmission priority of the sensor based at least on the initial priority value.

2. The electronic device according to claim 1, wherein, The at least one memory and the computer program code are further configured to, by means of the at least one processor, cause the electronic device to perform: determining the initial priority value based on a pre - constructed sensor data transmission priority scenario table.

3. The electronic device according to claim 2, wherein, In the sensor data transmission priority scenario table, the initial priority value is further associated with the sensor type of the sensor.

4. The electronic device according to claim 2, wherein, The at least one memory and the computer program code are further configured to, by means of the at least one processor, cause the electronic device to: dynamically adjust the initial priority value in the sensor data transmission priority scenario table based on signaling interaction with the device body where the sensor is set.

5. The electronic device according to claim 4, wherein, The sensor data transmission priority scenario table is specific to the device body.

6. The electronic device according to claim 2, wherein, In the sensor data transmission priority scenario table, the initial priority values of the respective sensors are different from each other.

7. The electronic device according to claim 1, wherein, The at least one memory and the computer program code are further configured to, by means of the at least one processor, cause the electronic device to perform: determining at least one of the communication delay of data transmission from the sensor and the accuracy of the sensing result of the sensor; and determining the final priority value of the sensor based on at least one of the communication delay and the accuracy and the initial priority value.

8. The electronic device according to claim 7, wherein, The at least one memory and the computer program code are further configured to, by means of the at least one processor, cause the electronic device to perform: in a case where at least one of the communication delay, the accuracy, and the initial priority value does not meet its respective predetermined requirement, determining the final priority value of the sensor as the smallest possible value of the priority value.

9. The electronic device according to claim 7, wherein, The at least one memory and the computer program code are further configured to, by means of the at least one processor, cause the electronic device to perform: weighting the initial priority value based on at least one of the communication delay and the accuracy to determine the final priority value of the sensor.

10. The electronic device according to claim 9, wherein, The at least one memory and the computer program code are further configured to, by means of the at least one processor, cause the electronic device to perform: determining a weight value corresponding to the accuracy based on the influence of the accuracy on the control error level; and / or determining a weight value corresponding to the communication delay based on a linear mapping of the communication delay to the weight value.

11. The electronic device according to claim 9, wherein, The at least one memory and the computer program code are further configured to, by means of the at least one processor, cause the electronic device to perform: Dynamically adjust at least one of the weight value corresponding to the communication delay and the weight value corresponding to the accuracy according to the actual situation or requirements.

12. The electronic device according to claim 8, wherein, The predetermined requirements for the communication delay include that the communication delay is lower than a predetermined delay, the predetermined requirements for the accuracy include that the accuracy is higher than a predetermined threshold, and the predetermined requirements for the initial priority value include that the initial priority value is higher than a predetermined priority.

13. The electronic device according to claim 12, wherein, The predetermined priority is dynamically set according to one or more of the current load, communication status, and characteristics of the sensor.

14. The electronic device according to claim 7, wherein, The at least one memory and the computer program code are further configured to cause the electronic device to perform, via the at least one processor: Determine the communication delay through short-byte message interaction with the sensor; and Determine the accuracy based on the comparison between the sensing result of the sensor for a specific location and the ground truth.

15. The electronic device according to claim 1, wherein, The at least one memory and the computer program code are further configured to cause the electronic device to perform, via the at least one processor: Send a sensor sharing entity activation instruction to the device corresponding to the sensor based on the final priority value.

16. The electronic device according to claim 15, wherein, The at least one memory and the computer program code are further configured to cause the electronic device to perform, via the at least one processor: Include the final priority value in the sensor sharing entity activation instruction to provide it to the device corresponding to the sensor, so that the device transmits sensing data based on the final priority value.

17. The electronic device according to claim 15, wherein, The at least one memory and the computer program code are further configured to cause the electronic device to perform, via the at least one processor: Determine the sensors for which data sharing is to be performed based on the final priority value and send a sensor sharing entity activation instruction to the device corresponding to the sensors for which data sharing is to be performed.

18. The electronic device according to claim 1, wherein, The multiple sensors are distributed on multiple device bodies.

19. The electronic device according to claim 1, wherein, The applicable scenario is one of multiple traffic scenarios.

20. The electronic device according to claim 1, wherein, The electronic device is disposed on one of the cloud, roadside unit side, and vehicle side, and the sensor is disposed on one of the cloud, roadside unit side, and vehicle side.

21. The electronic device according to claim 20, wherein, In the case where the electronic device is disposed on the roadside unit side or the vehicle side, the at least one memory and the computer program code are further configured to cause the electronic device to perform, via the at least one processor: Obtain a pre-constructed sensor data transmission priority scenario table for determining the initial priority value from the cloud.

22. A method for an electronic device, comprising: For each of a plurality of sensors that transmit data via wireless communication, determine an initial priority value of the data transmission priority of the sensor, the initial priority value being associated with an applicable scenario; And Determine a final priority value of the data transmission priority of the sensor based at least on the initial priority value.

23. A computer-readable storage medium having computer-executable instructions stored thereon, which when executed by a processor cause the processor to perform the method according to claim 22.

Images