CN117528453A - Identification updating method and device and Internet of vehicles equipment - Google Patents
Identification updating method and device and Internet of vehicles equipment Download PDFInfo
- Publication number
- CN117528453A CN117528453A CN202210912393.8A CN202210912393A CN117528453A CN 117528453 A CN117528453 A CN 117528453A CN 202210912393 A CN202210912393 A CN 202210912393A CN 117528453 A CN117528453 A CN 117528453A
- Authority
- CN
- China
- Prior art keywords
- time
- update
- updating
- determining
- temporary identifier
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 123
- 230000008569 process Effects 0.000 claims description 57
- 230000003993 interaction Effects 0.000 claims description 31
- 230000003111 delayed effect Effects 0.000 claims description 19
- 230000002452 interceptive effect Effects 0.000 claims description 15
- 238000004590 computer program Methods 0.000 claims description 8
- 230000008859 change Effects 0.000 abstract description 14
- 230000001960 triggered effect Effects 0.000 description 8
- 230000004044 response Effects 0.000 description 7
- 238000012508 change request Methods 0.000 description 6
- 238000010586 diagram Methods 0.000 description 5
- 230000009471 action Effects 0.000 description 4
- 230000000694 effects Effects 0.000 description 4
- 230000006870 function Effects 0.000 description 3
- 230000007246 mechanism Effects 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 230000006978 adaptation Effects 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 2
- 230000008676 import Effects 0.000 description 2
- 235000016496 Panda oleosa Nutrition 0.000 description 1
- 240000000220 Panda oleosa Species 0.000 description 1
- 230000008901 benefit Effects 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 238000000354 decomposition reaction Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000001788 irregular Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 230000002035 prolonged effect Effects 0.000 description 1
- 230000006798 recombination Effects 0.000 description 1
- 238000005215 recombination Methods 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/06—Authentication
- H04W12/069—Authentication using certificates or pre-shared keys
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/30—Services specially adapted for particular environments, situations or purposes
- H04W4/40—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Multimedia (AREA)
- Computer Security & Cryptography (AREA)
- Databases & Information Systems (AREA)
- Traffic Control Systems (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The application discloses an identification updating method, an identification updating device and Internet of vehicles equipment, and relates to the technical field of Internet of vehicles. Acquiring a service request message, wherein the service request message comprises first information related to a reserved time length of a target service; determining a second updating moment of the temporary identifier according to the updating period of the temporary identifier of the vehicle and the first updating moment of the temporary identifier; wherein a time interval between the first update time and the second update time is the update period; determining a first duration between a current time and the second update time; wherein the current time is located between the first update time and the second update time; and determining the updating time of the temporary identifier according to the reserved time and the first time. Thus, the problem that the service cannot be continued due to the change of the equipment identity caused by the update of the temporary identifier is avoided.
Description
Technical Field
The present disclosure relates to the field of communications technologies, and in particular, to a method and an apparatus for updating an identifier, and an internet of vehicles device.
Background
In the internet of vehicles system, after the vehicle starts all (Vehicle to Everything, V2X) functions, i.e. periodically sends basic security message (Basic Safety Message, BSM) messages, in order to protect user privacy, prevent from being tracked, a privacy protection mechanism is designed: (1) The different vehicles are represented using randomly generated identifications that are independent of the true identity information of the vehicles. (2) The randomly generated identity needs to change randomly as the anonymous credential changes. By the mechanism, privacy protection of the identity of the vehicle can be achieved. However, in the process that the sender and the receiver need to perform multiple interactions, if the identifier needs to be updated, the two interaction parties cannot determine whether the identity of the other party changes, and the interaction may not be continued.
Disclosure of Invention
The purpose of the application is to provide a method and a device for updating an identifier and Internet of vehicles equipment, so that the problem that an interaction application scene cannot be normally executed due to a privacy protection mechanism in the prior art is solved.
In order to achieve the above object, an embodiment of the present application provides an identifier updating method, which is applied to an internet of vehicles device, and the method includes:
Acquiring a service request message, wherein the service request message comprises first information related to a reserved time length of a target service;
determining a second updating moment of the temporary identifier according to the updating period of the temporary identifier of the vehicle and the first updating moment of the temporary identifier; wherein a time interval between the first update time and the second update time is the update period;
determining a first duration between a current time and the second update time; wherein the current time is located between the first update time and the second update time;
and determining the updating time of the temporary identifier according to the reserved time and the first time.
Optionally, the determining, according to the reserved duration and the first duration, an update occasion of the temporary identifier includes:
when the reserved time length is longer than the first time length, determining the updating time according to the reserved time length and the updating period; and/or the number of the groups of groups,
and under the condition that the reserved time length is smaller than or equal to the first time length, determining the updating time of the temporary identifier as the second updating time.
Optionally, in the case that the reserved time period is longer than the first time period, determining the update opportunity according to the reserved time period and the update period includes any one of the following:
When the reserved time length is smaller than or equal to the update period, determining that the current update time is before triggering the target service, and the time interval between the next adjacent update time and the current update time is the update period;
when the reserved time period is longer than the update period, determining that the current update time is before triggering the target service, and deferring the next adjacent update time to a third update time, wherein the time interval between the third update time and the current update time is longer than or equal to the reserved time period;
and under the condition that the reserved time period is longer than the update period, determining that the current update time is before triggering the target service, and determining that the time interval between the next adjacent update time and the current update time is the update period, wherein at least one message of the target service carries an alternative temporary identifier, and the at least one message is a message sent and/or received before the next adjacent update time.
Optionally, after the step of determining the update opportunity of the temporary identifier, the method further includes:
And when the next adjacent updating time is in the execution process of the target service and the message of the target service does not carry the alternative temporary identifier, postponing the next adjacent updating time backwards before reaching the next adjacent updating time.
Optionally, the method further comprises:
in the case that the next adjacent update opportunity needs to be postponed is determined, the postponed duration of the next adjacent update opportunity is published in any one of the following manners:
issuing identification updating indication information, wherein the identification updating indication information carries the deferred duration;
controlling the first flag bit to be set, wherein the set time length is the deferred time length;
and controlling the second flag bit to be set until the time corresponding to the delayed next updating time.
Optionally, the method further comprises:
and in the case that the time interval between two adjacent updating occasions of the temporary identifier is determined to be larger than a first threshold value, the temporary identifier is forcedly updated.
Optionally, the first information includes at least one of the reserved time length and/or service information of the target service.
Optionally, the method further comprises:
and determining the reserved time length according to historical data related to the service information.
Optionally, the service information includes a service type and/or an interactive object class.
Optionally, the method further comprises:
determining the maximum duration of each interaction step in the target service according to the service type;
and determining the reserved time length according to the maximum time lengths.
Optionally, after the step of determining the reserved time length according to each of the maximum time lengths, the method further includes:
and adjusting the reserved time length according to the category of the interactive object.
In order to achieve the above object, an embodiment of the present application provides an identifier updating device, which is applied to an internet of vehicles device, and the device includes:
the system comprises an acquisition module, a service request module and a service request module, wherein the acquisition module is used for acquiring a service request message, and the service request message comprises first information related to the reserved time length of a target service;
the first determining module is used for determining a second updating moment of the temporary identifier according to the updating period of the temporary identifier of the vehicle and the first updating moment of the temporary identifier; wherein a time interval between the first update time and the second update time is the update period;
A second determining module, configured to determine a first duration between a current time and the second update time; wherein the current time is located between the first update time and the second update time;
and the third determining module is used for determining the updating time of the temporary identifier according to the reserved time length and the first time length.
In order to achieve the above object, an embodiment of the present application provides an internet of vehicles device, including a transceiver, a memory, a processor, and a computer program stored on the memory and running on the processor, where the processor implements the method for updating the identifier according to the first aspect when executing the computer program.
In order to achieve the above object, an embodiment of the present application provides a readable storage medium having stored thereon a program or instructions which, when executed by a processor, implement the method for updating an identifier according to the first aspect.
The technical scheme of the application has at least the following beneficial effects:
firstly, an internet of vehicles device acquires a service request message, wherein the service request message comprises first information related to reserved time length of a target service; secondly, determining a second updating moment of the temporary identifier according to the updating period of the temporary identifier of the vehicle and the first updating moment of the temporary identifier; wherein a time interval between the first update time and the second update time is the update period; thirdly, determining a first duration between the current time and the second updating time; wherein the current time is located between the first update time and the second update time; and finally, determining the updating time of the temporary identifier according to the reserved time length and the first time length. Therefore, the updating time of the temporary identifier is not in the process of executing the service, so that the condition of changing the vehicle identity in the process of executing the service can be avoided, and the problem that the service cannot be continuously executed due to the updating of the temporary identifier is solved.
Drawings
FIG. 1 is a schematic diagram of a collaborative lane change scenario;
FIG. 2 is a schematic diagram of a collaborative lane change interaction flow;
FIG. 3 is a flowchart illustrating a method for updating an identifier according to an embodiment of the present application;
fig. 4 is a schematic diagram of an embodiment of the present application applied to a collaborative lane change scenario;
fig. 5 is a schematic structural diagram of an identifier updating apparatus according to an embodiment of the present application;
fig. 6 is a schematic structural diagram of an internet of vehicles device according to an embodiment of the present application.
Detailed Description
In order to make the technical problems, technical solutions and advantages to be solved by the present application more apparent, the following detailed description will be given with reference to the accompanying drawings and the specific embodiments. In the following description, specific details such as specific configurations and components are provided merely to facilitate a thorough understanding of embodiments of the present application. It will therefore be apparent to those skilled in the art that various changes and modifications can be made to the embodiments described herein without departing from the scope and spirit of the application. In addition, descriptions of well-known functions and constructions are omitted for clarity and conciseness.
It should be appreciated that reference throughout this specification to "one embodiment" or "an embodiment" means that a particular feature, structure or characteristic described in connection with the embodiment is included in at least one embodiment of the present application. Thus, the appearances of the phrases "in one embodiment" or "in an embodiment" in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.
In various embodiments of the present application, it should be understood that the sequence numbers of the following processes do not mean the order of execution, and the order of execution of the processes should be determined by the functions and internal logic thereof, and should not constitute any limitation on the implementation process of the embodiments of the present application.
In the examples provided herein, it should be understood that "B corresponding to a" means that B is associated with a from which B may be determined. It should also be understood that determining B from a does not mean determining B from a alone, but may also determine B from a and/or other information.
In describing embodiments of the present application, some concepts used in the following description are first explained.
At present, application scenes of the internet of vehicles equipment comprise a first-stage application scene and a second-stage application scene (shown in the following table 1), the first-stage application scene is mostly in a broadcasting mode, a vehicle or Road Side Unit (RSU) continuously broadcasts own state information, other vehicles formulate related safety and efficiency strategies according to the received state information, in this case, interaction between a sender and a receiver is not needed, the second-stage application scene is mostly in a cooperation type scene, and one cooperation can be completed between the vehicle and the vehicle or the RSU through multiple interactions.
Table 1 one-stage and two-stage application list
For example, in a cooperative lane change scenario based on V2V, as shown in fig. 1, the vehicle EV-1 needs lane change during traveling, the vehicle EV-1 transmits a traveling intention and a lane change request to EV-2 of an adjacent lane, the vehicle EV-2 decides whether to give way according to its own situation, and feeds back a Guan Jue policy to the EV-1, and after receiving the decision, the EV-1 decides whether to execute a lane change action, and informs the EV-2 of the result.
An example of a specific interaction procedure is shown in fig. 2, in which the messages used are basic safety messages (Basic Safety Message, BSM) and vehicle intention and request (Vehicle Intention and Request, VIR) messages, BSM messages being real-time dynamic travel information of the vehicle, VIR messages being travel intention and request information of the vehicle, the two messages being associated by BSM temporary IDs, i.e. the source ID in the VIR message of EV-1 is the temporary ID of the BSM and the destination ID is the temporary ID of the BSM of EV-2.
However, in order to meet the requirements of privacy protection, the pseudonymous certificates used to represent the identity of the vehicle need to be replaced on an irregular basis, and for privacy protection, the continuous use of the same pseudonymous certificate should not exceed vCertChangeInterval (300 s) for any of the following cases:
The current position of the system is smaller than vCertChangeDistance (2 km) when the distance from the current position of the system to the last pseudonym certificate is changed, and the system should continue to use the existing pseudonym certificate at the moment;
at least 1 of the key event flags de_veccleeventflags are set, at which point the system should continue to use the existing pseudonym certificate until all of the key event flags are reset.
The BSM temporary ID also needs to be replaced when the pseudonym certificate is replaced.
Also taking fig. 2 as an example, after the EV-1 sends out the service flow 1, if the pseudonym certificate of the EV-1 needs to be changed, the BSM temporary ID of the pseudonym certificate also needs to be changed, and considering consistency among message sets, the temporary ID in the VIR message of the EV-1 should also be changed, and when the EV-2 replies to the response message, the EV-2 cannot recognize the identity of the EV-1 because both the pseudonym certificate of the EV-1 and the temporary ID of the VIR are changed, and then the EV-2 cannot determine whether to continue the interaction procedure with the EV-1, and the request procedure fails.
In view of the above problems, as shown in fig. 3, an embodiment of the present application provides an identifier updating method, which is applied to an internet of vehicles device, and the method includes:
step 301, acquiring a service request message, wherein the service request message comprises first information related to a reserved time length of a target service;
Here, it should be noted that, in the case where the internet of vehicles device is a sender vehicle, the step may specifically be to obtain, through internal implementation, a service request message generated by the internet of vehicles device; in the case that the internet of vehicles device is a receiver vehicle, the step may specifically be obtained by receiving a service request message sent by a sender vehicle;
step 302, determining a second update time of the temporary identifier according to the update period of the temporary identifier of the vehicle and the first update time of the temporary identifier; wherein a time interval between the first update time and the second update time is the update period;
as described above, the temporary identifier and the pseudonym certificate of the vehicle are periodically updated, and therefore, the present step may determine the time of the first update (the second update time, the time of updating the currently used temporary identifier) after the current time based on the time of the last update (the first update time, that is, the time of updating the currently used temporary identifier) before the current time in the preset update period;
step 303, determining a first duration between the current time and the second update time; wherein the current time is located between the first update time and the second update time;
In this step, the first duration is the remaining update duration in the current update period;
step 304, determining the update time of the temporary identifier according to the reserved time length and the first time length.
Firstly, an internet of vehicles device acquires a service request message, wherein the service request message comprises first information related to reserved time length of a target service; secondly, determining a second updating moment of the temporary identifier according to the updating period of the temporary identifier of the vehicle and the first updating moment of the temporary identifier; wherein a time interval between the first update time and the second update time is the update period; thirdly, determining a first duration between the current time and the second updating time; determining the remaining update duration of a current update period, wherein the current time is between the first update time and the second update time; and finally, determining the updating time of the temporary identifier according to the reserved time length and the first time length. In this way, the update timing can be set outside the target service execution process, that is: the update time of the temporary identifier is not in the process of executing the service, so that the condition of changing the identity of the vehicle in the process of executing the service can be avoided, and the problem that the service cannot be continuously executed due to the update of the temporary identifier is solved.
As an optional implementation manner, step 304, determining the update occasion of the temporary identifier according to the reserved duration and the first duration includes:
when the reserved time length is longer than the first time length, determining the updating time according to the reserved time length and the updating period; and/or the number of the groups of groups,
and under the condition that the reserved time length is smaller than or equal to the first time length, determining the updating time of the temporary identifier as the second updating time.
That is, the update timing may be determined based on a comparison result of the reserved period and the first period, such as: when the reserved time length is smaller than or equal to the first time length, the temporary identifier is indicated not to be updated in the execution process of the target service, and at this time, the temporary identifier can be updated according to a preset update period, that is, the first update time after the current time is determined to be the second update time; for another example, when the reserved time period is longer than the first time period, it indicates that if the temporary identifier is updated according to the existing update period, the temporary identifier is updated in the target service executing process, so that the temporary identifier is prevented from being updated in the target service executing process by deferring the update timing, so as to ensure smooth execution of the target service.
Here, it should be noted that one implementation example of this alternative implementation is shown in example one and example two below.
As a specific implementation manner, in the case that the reserved time period is longer than the first time period, the update opportunity is determined according to the reserved time period and the update period, where the update opportunity includes any one of the following:
(1) When the reserved time length is smaller than or equal to the update period, determining that the current update time is before triggering the target service, and the time interval between the next adjacent update time and the current update time is the update period;
in this step, if the reserved time length (estimated execution time length of the target service) is less than or equal to the update period, that is, when the interaction of the target service can be completed between two adjacent update times, the update of the temporary identifier is performed once before the target service is started, that is, the interaction of the target service is started immediately after the temporary identifier is updated, so that the interaction of the target service can be completed before the next update of the temporary identifier, and the situation that the target service cannot be performed due to the fact that the opposite terminal cannot distinguish identity due to the update of the temporary identifier in the execution process of the target service is avoided.
(2) When the reserved time period is longer than the update period, determining that the current update time is before triggering the target service, and deferring the next adjacent update time to a third update time, wherein the time interval between the third update time and the current update time is longer than or equal to the reserved time period;
in this step, if the reserved time period is longer than the update period, it indicates that the temporary identifier is updated according to the pre-configured update period, and the temporary identifier is updated in the target service execution process whenever the target service is started, so that the temporary identifier may be updated once before the target service starts, and then the time of the next update is postponed, that is: the time interval between the update of the temporary identifier before the target service starts and the update of the next adjacent temporary identifier is increased, so that the time interval is greater than or equal to the preset duration, the update of the temporary identifier can not be performed in the process of ensuring the execution of the target service, and the problem that the target service cannot be normally performed due to the update of the temporary identifier is avoided.
Here, it is to be noted that one specific example in this step is shown as example three below.
(3) And under the condition that the reserved time period is longer than the update period, determining that the current update time is before triggering the target service, and determining that the time interval between the next adjacent update time and the current update time is the update period, wherein at least one message of the target service carries an alternative temporary identifier, and the at least one message is a message sent and/or received before the next adjacent update time.
Here, it is to be noted that one specific example in this step is shown as example four in the following.
Similarly, in this step, if the reserved time period is longer than the update period, it indicates that the temporary identifier is updated according to the pre-configured update period, and when the target service is started, the temporary identifier is updated in the process of executing the target service, so that the temporary identifier may be updated once before the target service starts, and then, in the process of executing the target service, at least one interaction message before reaching the next update carries the temporary identifier and the alternative temporary identifier currently used, where the alternative temporary identifier is the temporary identifier after the temporary identifier is updated again, so that the corresponding relationship between the current temporary identifier of the target terminal and the updated temporary identifier can be clarified by the opposite terminal, and after the temporary update is performed again, the identity of the target terminal can be determined based on the updated temporary identifier, so that the target service can continue to execute.
Here, under the conditions of the above cases (1) and (2), if the actual execution duration of the target service is less than the reserved duration, the update procedure of the temporary identifier may be immediately executed by sending an update instruction or triggering the flag bit associated with the temporary identifier update to be reset.
In addition, in another implementation manner, when the reserved time period is longer than the first time period, the temporary identifier may be updated according to the configured update period (i.e., the update period and the update time are not changed), and in the execution process of the target service, the alternative temporary identifier is carried in at least one message before the update time is reached.
Further, as an optional implementation manner, in step 104, when determining the update of the temporary identifier, the method further includes:
and when the next adjacent updating time is in the execution process of the target service and the message of the target service does not carry the alternative temporary identifier, postponing the next adjacent updating time backwards before reaching the next adjacent updating time.
That is, if the temporary identifier needs to be updated in the actual execution process of the target service, and any message in the target service does not carry the alternative temporary identifier, if the temporary identifier is updated directly in the execution process of the target service, there may be a case that the opposite end (another device that performs service interaction with the internet of vehicles device that performs the method of the embodiment of the present application) cannot identify the identity of the home end (the internet of vehicles device that performs the method of the present application), so that the update time may be postponed again before the update time of the temporary identifier arrives, so that the update time is postponed until the target service is completed, which can avoid updating the temporary identifier in the execution process of the target service and ensure that the target service can be normally performed.
Further, as an optional implementation manner, after determining the update opportunity of the temporary identifier in step 104, the method further includes:
in the case that the next adjacent update opportunity needs to be postponed is determined, the postponed duration of the next adjacent update opportunity is published in any one of the following manners:
issuing identification updating indication information, wherein the identification updating indication information carries the deferred duration;
controlling the first flag bit to be set, wherein the set time length is the deferred time length; wherein, the first identifier may be de_veccleeventflags (data element vehicle event flag);
and controlling a second flag bit to be set until the time corresponding to the delayed adjacent next updating time, wherein the second flag bit can be a newly added field.
That is, in this alternative implementation manner, the time length of deferring the next update opportunity of the adjacent time may be notified by means of issuing the identification update instruction information, and the time length of deferring the next update opportunity of the adjacent time may also be determined by means of maintaining the state of the first flag bit; the deferred duration refers to a time length between a time corresponding to a next adjacent update time determined according to a preset update period and a time corresponding to a deferred next adjacent update time, and in addition, the second flag bit may be set and the setting state may be maintained to a time corresponding to the deferred next adjacent update time, that is: when the next adjacent updating time is determined to be delayed, setting the second flag bit, and keeping the setting state, until reaching the time corresponding to the next adjacent updating time after being delayed, controlling the second flag bit to reset, that is, triggering the updating process of the temporary identifier when the second flag bit is reset, so that the time corresponding to the update time after being delayed can be determined based on the time length of the first flag bit of the identifier updating indication information and the time corresponding to the next adjacent updating time determined according to the preset updating period, and the updating process of the temporary identifier can be executed when reaching the time corresponding to the update time after being delayed.
Further, as an alternative implementation, the method further includes:
and in the case that the time interval between two adjacent updating occasions of the temporary identifier is determined to be larger than a first threshold value, the temporary identifier is forcedly updated.
That is, after deferring the temporary identifier a plurality of times in succession, if the update time of the adjacent temporary identifiers is greater than the first threshold value set in advance, the temporary identifier may be forcedly updated, that is: no matter what kind of service interaction is currently performed, the interaction service should be canceled, and the temporary identifier and the pseudonym certificate should be forcedly updated, so that the situation that someone continuously initiates service interaction maliciously, which results in longer reserved time length, and the updating time of the temporary identifier (and the pseudonym certificate) is infinitely delayed can be avoided.
Here, it should be noted that a specific example of this alternative implementation is shown in example five below.
As an optional implementation manner, the first information includes at least one of the reserved duration and/or service information of the target service.
That is, the service request message may display a reservation duration indicating the target service, that is: the service request message directly carries the estimated execution time (reserved time) of the target service; and/or, the service request message may implicitly indicate a reservation duration of the target service, that is: the service request message carries service information of the target service, so that the reserved time length of the target service is estimated based on the service information.
On the basis that the first information includes a reserved time length and/or service information, as an optional implementation manner, the method further includes:
and determining the reserved time length according to historical data related to the service information.
That is, the present alternative implementation may determine the reserved time length of the target service based on the estimated time length or the actual time length that is once determined by the same type of target service or the same service information, that is, according to an empirical value.
As a specific implementation, the service information includes a service type and/or an interaction object class. On this basis, further, as an alternative implementation manner, the method further includes:
determining the maximum duration of each interaction step in the target service according to the service type;
and determining the reserved time length according to the maximum time lengths.
The alternative implementation may specifically be an interaction step required by determining the target service based on the service type, and an interaction timeout (a preset maximum duration required by each step) of each step.
Still further, as an optional implementation manner, after the step of determining the reserved time length according to each of the maximum time lengths, the method further includes:
And adjusting the reserved time length according to the category of the interactive object.
Specifically, the alternative implementation manner may determine the execution speed of the interactive object based on the category of the interactive object, so as to adjust the reserved time length of the target service based on the execution speed of the interactive object, so that the reserved time length is closer to the actual execution time length of the target service. For example, if the interactive object is an RSU, the reserved time period may be appropriately shortened so that the reserved time period is less than or equal to the preset time period, and if the interactive object is a vehicle, the reserved time period may be appropriately prolonged so that the reserved time period is greater than or equal to the preset time period.
The implementation process of the embodiment of the present application will be described below by taking an internet of vehicles device as a requesting vehicle as an example:
(1) When the vehicle initiates an interactive service request, the information is sent to an identification updating module (or an entity is not available) and a reserved time length is provided for the identification updating module or service information of the reserved time length can be deduced;
(2) The mark updating module compares the reserved time length and the time length from the next time of the update of the pseudonym certificate and the temporary mark, and decides whether to update the pseudonym certificate and the temporary mark.
(3-1) if the identifier updating module decides that the pseudonym certificate and the temporary identifier updating process should be performed first, the pseudonym certificate and the temporary identifier updating process can be directly triggered, and the triggering mode can be a mode of directly sending an updating instruction or a mode of resetting the second flag bit.
And (3-2) if the identifier updating module decides that the pseudonym certificate and temporary identifier updating process can not be performed or the updating process of the pseudonym certificate and the temporary identifier needs to be delayed, issuing the delayed time length by issuing the identifier updating instruction information, controlling the first flag bit and the like, or issuing the time corresponding to the delayed updating time by setting the second flag bit to the time corresponding to the delayed updating time, thereby triggering the updating process of the pseudonym certificate and the temporary identifier when the time corresponding to the delayed updating time is reached.
The implementation process of the embodiment of the present application will be described below by taking an internet of vehicles device as a cooperator vehicle as an example:
(1) When the vehicle receives the interactive service request, the reserved time length or service information from which the reserved time length can be deduced is also sent to the identifier updating module, and the identifier updating module compares the reserved time length with the time length from the next identifier updating and decides whether to carry out the identifier updating process or not.
(2-1) if the identifier updating module decides that the identifier updating process should be performed first, the identifier updating process may be triggered directly, or the pseudonym certificate and the temporary identifier updating process may be triggered by resetting the second flag bit. And after waiting for the requester to send the interactive service request again, responding.
And (2-2) if the updating module decides that the updating process can be performed without performing or delaying, the pseudonym certificate and temporary identifier updating process can be not triggered, the delayed time length is published by means of issuing the updating indication information of the identifier, controlling the setting of the first flag bit and the like, or the time corresponding to the delayed updating time is published by means of setting the second flag bit to the time corresponding to the delayed updating time, so that the updating process of the pseudonym certificate and the temporary identifier is triggered when the time corresponding to the delayed updating time is reached.
Here, it should be noted that, the above two examples are described with the identification update module as the execution body, and of course, the method of executing the embodiment of the present application may be performed not as an entity but as a program.
The following describes an identifier updating method according to the embodiment of the present application with reference to a specific scenario:
Example one: collaborative lane change scenario, timeout time
The requesting vehicle HV needs to change lanes in hopes of completing the collaboration process in conjunction with the collaborating vehicles RV1 and RV 2. The interaction flow of vehicles HV with RV1 and RV2 is shown in fig. 4, where the dashed line represents the latest response time; the solid line represents the actual response time.
For vehicle HV, after the request is sent, waiting for RV1 and RV2 response messages (traffic flow 2) is at most T intv1 The actual response time is T res’ -T req Compared with T intv1 Short. The service flow 5 is the end of the whole interaction process, and after the service flow 5 is sent, the process of updating the vehicle identification, namely T, can be normally performed 0HV ＝T intv1 +T intv3 。
When the vehicles RV1 and RV2 receive the request, they will send a response message to the vehicle HV, and after the response message (traffic flow 2) is sent, after receiving an acknowledgement message (traffic flow 3) of the vehicle HV, the process of updating the vehicle temporary identifier can be performed normally. The time consumption of the whole process is T intv2 I.e. T 0RV ＝T intv2 。
Therefore, for vehicle HV, after the application layer initiates the collaborative lane change request, the identifier management module should be triggered to make a decision first, if the first duration (T ID ) Reserved time (T) 0HV ) The identification update should be performed first, if T ID ≥T 0HV Then no identity update may be performed.
For vehicles RV1 and RV2, after receiving the request of vehicle HV, the identification management module should be triggered to make a decision, if T ID ≤T 0RV The identification update should be performed first, if T ID ≥T 0RV Then no identity update may be performed.
Example two: in the process of executing the current request, the collaboration request of other vehicles is received
The vehicle HV triggers a collaborative lane change request, which is performing the interactive procedure of example 1 with RV1 and RV 2. If a cooperative import request sent by the vehicle HV1 is received at this time, the vehicle HV is required to assist it in completing the vehicle import.
The vehicle HV makes a decision firstly, whether to respond to the incoming request of HV1 immediately or not, if the decision is that the incoming request of HV1 responds immediately, the current lane change request is stopped, then a mark management module is triggered, the mark updating residual time and the maximum timeout time of the cooperation process are compared, and then whether the mark needs to be updated or not is determined. After the collaborative import-exchange interaction procedure with HV1 is completed, if the previous lane-change request still needs to be executed, the operation is performed again according to the procedure in example one.
Example three: collaborative channel changing scene, estimated time and delayed update
As in the example one scenario, the requesting vehicle HV needs to change lanes in hopes of completing the collaboration process in conjunction with the collaborating vehicles RV1 and RV 2. The interaction flow of vehicles HV with RV1 and RV2 is shown in fig. 4:
in general, T intv1 And T intv2 Are known from standards or from the vehicle itself and can be considered basically as stable values. But T is intv3 It is a variable value that needs to be determined according to the environment around the vehicle.
For a vehicle HV, when determining the total time consumed for the collaborative lane-change interaction, a determination should be made based on the current environment or empirical values. For example, if there are fewer surrounding vehicles, T intv3 May be a small value, T if there are more surrounding vehicles intv3 It may be larger.
Due to T intv3 If the estimated time is the estimated time, the actual time and the value may be larger. For example:
if according to the estimated time T ID ≥T 0HV However, the vehicle cannot change the lane according to the estimated time in the lane changing process, resulting in T which is actually consumed 0HV’ Exceeding T ID The pseudonym certificate and the vehicle identification delay the updating time and are updated after the whole process is completed.
Example four: collaborative lane change, estimated time, carrying alternate ID
The precondition is the same as example three, but at the actual cost of T 0HV’ Exceeding T ID When, kana certificate and carThe vehicle identification is updated according to a given plan, but the N messages before the update carry the information of the vehicle identification ID1 in use and the latest vehicle identification ID2 in plan use, and/or the time when the vehicle identification ID2 takes effect. After the cooperator vehicles RV1 and RV2 receive the message, they can still identify the vehicle HV as the requesting party after the vehicle HV identification is changed from ID1 to ID 2.
Example five: forced stop over time
The precondition is the same as the third example, after the vehicle HV has sent the service flow 3, the vehicle cannot enter the transmission of the service flow 5 because the current environment vehicle cannot complete lane change for a long time, and the vehicle does not update the time T of the identification w If the predetermined limit has been exceeded, the vehicle HV should stop the interaction, send a cancellation request, trigger an update of the pseudonym certificate and the vehicle identification, and then decide if and when to trigger the previous lane change request as required.
As shown in fig. 5, an embodiment of the present application further provides an identifier updating apparatus, which is applied to an internet of vehicles device, where the apparatus includes:
an obtaining module 501, configured to obtain a service request message, where the service request message includes first information related to a reserved duration of a target service;
a first determining module 502, configured to determine a second update time of the temporary identifier according to an update period of the temporary identifier of the vehicle and the first update time of the temporary identifier; wherein a time interval between the first update time and the second update time is the update period;
a second determining module 503, configured to determine a first duration between a current time and the second update time; wherein the current time is located between the first update time and the second update time;
A third determining module 504, configured to determine an update opportunity of the temporary identifier according to the reserved duration and the first duration.
Optionally, the third determining module 504 includes:
a first determining submodule, configured to determine the update opportunity according to the reserved time length and the update period when the reserved time length is longer than the first time length; and/or the number of the groups of groups,
and the second determining submodule is used for determining the updating time of the temporary identifier as the second updating time under the condition that the reserved time length is smaller than or equal to the first time length.
Optionally, the first determining submodule is specifically configured to perform any one of the following:
when the reserved time length is smaller than or equal to the update period, determining that the current update time is before triggering the target service, and the time interval between the next adjacent update time and the current update time is the update period;
when the reserved time period is longer than the update period, determining that the current update time is before triggering the target service, and deferring the next adjacent update time to a third update time, wherein the time interval between the third update time and the current update time is longer than or equal to the reserved time period;
And under the condition that the reserved time period is longer than the update period, determining that the current update time is before triggering the target service, and determining that the time interval between the next adjacent update time and the current update time is the update period, wherein at least one message of the target service carries an alternative temporary identifier, and the at least one message is a message sent and/or received before the next adjacent update time.
Further, the apparatus further comprises:
and the deferral module is used for deferring the next adjacent update opportunity backwards before the next adjacent update opportunity is reached under the condition that the next adjacent update opportunity is located in the execution process of the target service and the message of the target service does not carry the alternative temporary identifier.
Further, the apparatus further comprises:
the issuing module is used for issuing the time length for deferring the next updating time of the adjacent in any one of the following modes under the condition that the next updating time of the adjacent is determined to be deferred:
issuing identification updating indication information, wherein the identification updating indication information carries the deferred duration;
Controlling the first flag bit to be set, wherein the set time length is the deferred time length;
and controlling the second flag bit to be set until the time corresponding to the delayed next updating time.
Further, the apparatus further comprises:
and the forced updating module is used for forcedly updating the temporary identifier under the condition that the time interval between two adjacent updating occasions of the temporary identifier is determined to be larger than a first threshold value.
Optionally, the first information includes at least one of the reserved time length and/or service information of the target service.
Further, the apparatus further comprises:
and a fourth determining module, configured to determine the reserved duration according to historical data related to the service information.
Optionally, the service information includes a service type and/or an interactive object class.
Further, the apparatus further comprises:
a fifth determining module, configured to determine a maximum duration of each interaction step in the target service according to the service type;
and a sixth determining module, configured to determine the reserved duration according to each of the maximum durations.
Further, the apparatus further comprises:
And the adjustment module is used for adjusting the reserved time length according to the category of the interactive object.
It should be noted that, the identifier updating device provided in the embodiment of the present application can implement all the method steps implemented in the embodiment of the identifier updating method, and can achieve the same technical effects, and specific details of the same parts and beneficial effects as those of the embodiment of the method in the embodiment are not repeated herein.
As shown in fig. 6, the embodiment of the present application further provides an internet of vehicles device, which includes a transceiver 610, a memory 620, a processor 600, and a computer program stored in the memory 620 and running on the processor 600, where when the processor 600 executes the computer program, the processes of the embodiment of the identifier updating method described above are implemented, and the same technical effects can be achieved, so that repetition is avoided, and no further description is given here.
The transceiver 610 is configured to receive and transmit data under the control of the processor 600.
Wherein in fig. 6, a bus architecture may comprise any number of interconnected buses and bridges, and in particular one or more processors represented by processor 600 and various circuits of memory represented by memory 620, linked together. The bus architecture may also link together various other circuits such as peripheral devices, voltage regulators, power management circuits, etc., which are well known in the art and, therefore, will not be described further herein. The bus interface provides an interface. Transceiver 610 may be a number of elements, including a transmitter and a receiver, providing a means for communicating with various other apparatus over a transmission medium. The user interface 1030 may also be an interface capable of interfacing with an internal connection requiring device for a different user device including, but not limited to, a keypad, display, speaker, microphone, joystick, etc.
The processor 600 is responsible for managing the bus architecture and general processing, and the memory 620 may store data used by the processor 600 in performing operations.
Those skilled in the art will appreciate that all or part of the steps of implementing the above-described embodiments may be implemented by hardware, or may be implemented by instructing the relevant hardware by a computer program comprising instructions for performing some or all of the steps of the above-described methods; and the computer program may be stored in a readable storage medium, which may be any form of storage medium.
In addition, the embodiment of the present application further provides a computer readable storage medium, where a program is stored, where the program, when executed by a processor, implements each process of the embodiment of the identifier updating method described above, and the same technical effects can be achieved, and for avoiding repetition, a detailed description is omitted herein. Among them, the computer readable storage medium is Read-Only Memory (ROM), random access Memory (Random Access Memory RAM), magnetic disk or optical disk, etc.
Furthermore, it should be noted that in the apparatus and method of the present application, it is apparent that the components or steps may be disassembled and/or assembled. Such decomposition and/or recombination should be considered as equivalent to the present application. Also, the steps of performing the above-described series of processes may naturally be performed in the order illustrated or in chronological order, but are not necessarily performed in chronological order, and some steps may be performed in parallel or independently of each other. It will be appreciated by those of ordinary skill in the art that all or any of the steps or components of the methods and apparatus of the present application may be implemented in hardware, firmware, software, or a combination thereof in any computing device (including processors, storage media, etc.) or network of computing devices, as would be apparent to one of ordinary skill in the art after reading the description herein.
Thus, the objects of the present application may also be achieved by running a program or set of programs on any computing device. The computing device may be a well-known general purpose device. The object of the present application can thus also be achieved by merely providing a program product containing program code for implementing the method or the apparatus. That is, such a program product also constitutes the present application, and a storage medium storing such a program product can also constitute the present application. It is apparent that the storage medium may be any known storage medium or any storage medium developed in the future.
Finally, it is further noted that relational terms such as first and second, and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Moreover, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or terminal that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
While the foregoing is directed to the preferred embodiments of the present application, it should be noted that modifications and adaptations to those embodiments may occur to one skilled in the art and that such modifications and adaptations are intended to be comprehended within the scope of the present application without departing from the principles set forth herein.
Claims (14)
1. An identification updating method, which is characterized by being applied to internet of vehicles equipment, comprising:
acquiring a service request message, wherein the service request message comprises first information related to a reserved time length of a target service;
determining a second updating moment of the temporary identifier according to the updating period of the temporary identifier of the vehicle and the first updating moment of the temporary identifier; wherein a time interval between the first update time and the second update time is the update period;
determining a first duration between a current time and the second update time; wherein the current time is located between the first update time and the second update time;
and determining the updating time of the temporary identifier according to the reserved time and the first time.
2. The method of claim 1, wherein the determining the update opportunity for the temporary identifier based on the reserved time period and the first time period comprises:
When the reserved time length is longer than the first time length, determining the updating time according to the reserved time length and the updating period; and/or the number of the groups of groups,
and under the condition that the reserved time length is smaller than or equal to the first time length, determining the updating time of the temporary identifier as the second updating time.
3. The method according to claim 2, wherein the determining the update opportunity based on the reserved time period and the update period in the case where the reserved time period is longer than the first time period includes any one of:
when the reserved time length is smaller than or equal to the update period, determining that the current update time is before triggering the target service, and the time interval between the next adjacent update time and the current update time is the update period;
when the reserved time period is longer than the update period, determining that the current update time is before triggering the target service, and deferring the next adjacent update time to a third update time, wherein the time interval between the third update time and the current update time is longer than or equal to the reserved time period;
And under the condition that the reserved time period is longer than the update period, determining that the current update time is before triggering the target service, and determining that the time interval between the next adjacent update time and the current update time is the update period, wherein at least one message of the target service carries an alternative temporary identifier, and the at least one message is a message sent and/or received before the next adjacent update time.
4. A method according to claim 3, wherein after the step of determining the update occasion of the temporary identity, the method further comprises:
and when the next adjacent updating time is in the execution process of the target service and the message of the target service does not carry the alternative temporary identifier, postponing the next adjacent updating time backwards before reaching the next adjacent updating time.
5. The method according to claim 3 or 4, characterized in that the method further comprises:
in the case that the next adjacent update opportunity needs to be postponed is determined, the postponed duration of the next adjacent update opportunity is published in any one of the following manners:
Issuing identification updating indication information, wherein the identification updating indication information carries the deferred duration;
controlling the first flag bit to be set, wherein the set time length is the deferred time length
And controlling the second flag bit to be set until the time corresponding to the delayed next updating time.
6. The method according to claim 1, wherein the method further comprises:
and in the case that the time interval between two adjacent updating occasions of the temporary identifier is determined to be larger than a first threshold value, the temporary identifier is forcedly updated.
7. The method according to claim 1, wherein the first information comprises at least one of the reservation duration and/or traffic information of the target traffic.
8. The method of claim 7, wherein the method further comprises:
and determining the reserved time length according to historical data related to the service information.
9. The method according to claim 8, wherein the service information comprises a service type and/or an interaction object class.
10. The method according to claim 9, wherein the method further comprises:
Determining the maximum duration of each interaction step in the target service according to the service type;
and determining the reserved time length according to the maximum time lengths.
11. The method of claim 10, wherein after the step of determining the reserved time length based on each of the maximum time lengths, the method further comprises:
and adjusting the reserved time length according to the category of the interactive object.
12. An identification updating apparatus, characterized by being applied to an internet of vehicles device, the apparatus comprising:
the system comprises an acquisition module, a service request module and a service request module, wherein the acquisition module is used for acquiring a service request message, and the service request message comprises first information related to the reserved time length of a target service;
the first determining module is used for determining a second updating moment of the temporary identifier according to the updating period of the temporary identifier of the vehicle and the first updating moment of the temporary identifier; wherein a time interval between the first update time and the second update time is the update period;
a second determining module, configured to determine a first duration between a current time and the second update time; wherein the current time is located between the first update time and the second update time;
And the third determining module is used for determining the updating time of the temporary identifier according to the reserved time length and the first time length.
13. An internet of vehicles device comprising a transceiver, a memory, a processor and a computer program stored on the memory and running on the processor, wherein the processor implements the method of updating the identity of any one of claims 1 to 11 when the computer program is executed by the processor.
14. A readable storage medium having stored thereon a program or instructions, which when executed by a processor, implements the identification updating method of any of claims 1 to 11.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210912393.8A CN117528453A (en) | 2022-07-29 | 2022-07-29 | Identification updating method and device and Internet of vehicles equipment |
| PCT/CN2023/102376 WO2024021954A1 (en) | 2022-07-29 | 2023-06-26 | Identifier updating method and apparatus, and internet of vehicles device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210912393.8A CN117528453A (en) | 2022-07-29 | 2022-07-29 | Identification updating method and device and Internet of vehicles equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117528453A true CN117528453A (en) | 2024-02-06 |
Family
ID=89705217
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210912393.8A Pending CN117528453A (en) | 2022-07-29 | 2022-07-29 | Identification updating method and device and Internet of vehicles equipment |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN117528453A (en) |
| WO (1) | WO2024021954A1 (en) |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP7097818B2 (en) * | 2016-04-19 | 2022-07-08 | 華為技術有限公司 | Transportation service acquisition method and related equipment |
| CN111817833B (en) * | 2019-04-12 | 2023-04-18 | 华硕电脑股份有限公司 | Method and apparatus for handling sidelink identifier change in a wireless communication system |
| EP3737124B1 (en) * | 2019-05-10 | 2022-03-02 | Volkswagen AG | A concept for addressing road users in wireless communications |
| CN114189836A (en) * | 2020-09-15 | 2022-03-15 | 大唐高鸿智联科技(重庆)有限公司 | Communication method for formation vehicles and vehicles |
-
2022
- 2022-07-29 CN CN202210912393.8A patent/CN117528453A/en active Pending
-
2023
- 2023-06-26 WO PCT/CN2023/102376 patent/WO2024021954A1/en unknown
Also Published As
| Publication number | Publication date |
|---|---|
| WO2024021954A1 (en) | 2024-02-01 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| Palazzi et al. | How Do You Quickly Choreograph Inter-Vehicular Communications? A Fast Vehicle-to-Vehicle Multi-Hop Broadcast Algorithm, Explained. | |
| CN105684508B (en) | The resource allocation based on cluster for vehicle-to-vehicle communication | |
| Meneguette et al. | SMART: an efficient resource search and management scheme for vehicular cloud-connected system | |
| Shahen Shah et al. | CB‐MAC: a novel cluster‐based MAC protocol for VANETs | |
| Park et al. | Application-level frequency control of periodic safety messages in the IEEE WAVE | |
| WO2017032100A1 (en) | Vehicle control method and apparatus, and vehicle internet system | |
| CN107347219B (en) | To the method and terminal of V2X traffic assignments resource | |
| US20230040934A1 (en) | Method for sidelink communication, device and storage medium | |
| WO2005024591A3 (en) | System and method for securely authorizing and distributing stored-value card data | |
| US20230063010A1 (en) | Method and apparatus for controlling vehicle to drive as platoon, electronic device, and storage medium | |
| KR102191884B1 (en) | Communication method and device | |
| CA2347089A1 (en) | Method for disseminating a message | |
| CN111083193A (en) | Long connection message sending method, server and storage medium | |
| WO2008141165A4 (en) | Managing distributed access to a shared medium | |
| US20110158178A1 (en) | System and method of edge caching when cummunicating data | |
| Feukeu et al. | Dynamic broadcast storm mitigation approach for VANETs | |
| JP6771559B2 (en) | Mobile communication device, mobile communication method, and mobile communication program | |
| WO2018086535A1 (en) | Uplink data sending method, terminal and network device | |
| CN111506443A (en) | Service calling method, device, equipment and storage medium | |
| CN117528453A (en) | Identification updating method and device and Internet of vehicles equipment | |
| Bujari | A network coverage algorithm for message broadcast in vehicular networks | |
| Mershad et al. | SCORE: Data scheduling at roadside units in vehicle ad hoc networks | |
| CN110944305B (en) | Data transmission method of V2X dual-mode terminal, 4G base station and terminal | |
| Cao et al. | A multi-hop reputation announcement scheme for VANETs | |
| US8897170B2 (en) | Communication apparatus and method for mobile terminal communication through a sensor network |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |