Method for exchanging dynamic data with a digital twin of an autonomous vehicle

Abstract

The invention relates to computing. A method for exchanging dynamic data with a digital twin of an autonomous vehicle is implemented by registering domain names of autonomous vehicles in an ENUM registry and registering a domain name for a road infrastructure unit in the ENUM registry. A registry of services is created. Associations are assigned between autonomous vehicles, road infrastructure units, vehicles and intelligent transport system services. Data is received for requesting the execution of a service, and identification is made. DNS queries for a pool of ENUM domain names are formulated using a DNS server in order to retrieve resource records, which activate the requested intelligent transport system services that are relevant to the request in order to make a decision. A resource record is sent from the DNS server to the address of a link and decision analysis unit. Service parameters are identified for the subsequent formulation of a query to the intelligent transportation system service server, and responses to the requests are transmitted. The technical result consists in making it possible to exchange dynamic data with a digital twin of an autonomous vehicle.

Description

[0001] A METHOD FOR EXCHANGING DYNAMIC DATA WITH THE DIGITAL TWIN OF AN AUTONOMOUS VEHICLE

[0002] AREA OF TECHNOLOGY

[0003] The claimed technical solution generally relates to the field of computer technology, and in particular to an automated method for exchanging dynamic data with a digital twin of an autonomous vehicle.

[0004] LEVEL OF TECHNOLOGY

[0005] Known from the prior art is patent RU2754606C1 "METHOD OF IDENTIFYING A SERVICE IN THE ENUM STRUCTURE" by Aleksey Olegovich Ptashny et al., published 09 / 03 / 202E. This patent describes a method in which a request for obtaining information about a service is formed, a registry of services is first created, into which at least one record characterizing information about the service is first entered using the first network means, where the information about the service includes at least network addresses and service metadata, and the service registry is configured to change, supplement and remove a record characterizing the properties of the service, then using the second network means, at least one resource record is entered into the ENUM DNS zone of the domain associated with the telephone number, containing the type of service, a link to the registry of services, an identifier of the service in the registry, service parameters for further formation of an appeal to the registry of services, the number is converted,in a manner determined for ENUM, into the ENUM domain name, after which, using a third network means, a DNS query is generated to obtain resource records for the given ENUM domain name using DNS means, at least one resource record associated with the specified ENUM domain name of the telephone number is sent from the DNS server to the third network means in response to the DNS query, information about the service identifier, the type of service, links to the service registry, service parameters is determined from at least one resource record for further generation of a request to the service registry, a request to the service registry is generated and executed using the third network means, which at least contains the service identifier, in response to the request to the service registry, data about the network address and service metadata are sent from the service registry to the third network means.

[0006] The disadvantage of the known solution in this area of ​​technology is the lack of the ability to detail and specify the solution regarding the method of exchanging dynamic data with the digital twin of an autonomous vehicle, and the lack of the ability to apply the technology to autonomous vehicles in the environment of intelligent transport systems.

[0007] ESSENCE OF THE INVENTION

[0008] The proposed technical solution proposes a new approach to exchanging dynamic data with a digital twin of an autonomous vehicle.

[0009] The technical result consists in expanding the arsenal of technical means for solutions of this type.

[0010] The claimed technical result is achieved by implementing a method for exchanging dynamic data with a digital twin of an autonomous vehicle, comprising the following stages:

[0011] - create an ENUM registry of domain names of autonomous vehicles;

[0012] - register domain names of autonomous vehicles in the ENUM registry by converting the subscriber telephone number (MSISDN);

[0013] - after registration, the ENUM registry creates a corresponding resource record for the registered domain name on the DNS server, containing an indication of the type of service that may be requested by the autonomous vehicle from other vehicles and / or road infrastructure devices for decision-making, as well as the conditions, personalized for the autonomous vehicle, under which this service may be performed depending on the circumstances of the situation, place and time;

[0014] - register a domain name for a road infrastructure device in the ENUM registry by converting MSISDN;

[0015] - after registration, the ENUM registry creates a corresponding resource record for the registered domain name of the road infrastructure device on the DNS server, containing an indication of the type of service that can be processed by the road infrastructure device to make decisions depending on the requests received from the autonomous vehicle;

[0016] - create a registry of services, into which, on the server of the intelligent transport system service, at least one entry is previously entered that characterizes the properties of the intelligent transport system service;

[0017] - register the domain name of the service using a network technical solution and enter at least one resource record containing the type of service, links to the service registry, the service identifier in the ENUM registry, and service parameters for further formation of a request to the service registry; - assign associations between autonomous vehicles, road infrastructure devices, vehicles, and intelligent transport system services depending on the circumstances of the situation, time, and place in which they may be located;

[0018] - receive information from the on-board unit of an autonomous vehicle, including data necessary for a request to perform an intelligent transport system service, and identify it using the MSISDN, form a request to perform this service from the autonomous vehicle to the ENUM registry;

[0019] - form in the ENUM registry a pool of domain names of other vehicles and road infrastructure devices, the data from which is relevant for solving the service requested by the autonomous vehicle;

[0020] - generate DNS queries for the ENUM domain name pool using a DNS server to obtain resource records that activate the requested intelligent transport system services relevant to the autonomous vehicle request and send at least one resource record associated with the specified ENUM domain name from the DNS server to the address of the link and decision analysis unit;

[0021] - determine in the block for analyzing connections and decisions from at least one resource record information about the service identifier, the type of service, links to the service server, service parameters for further formation of a request to the server of the intelligent transport system service, and also, if necessary, services for receiving responses to requests to road infrastructure devices and / or other vehicles;

[0022] - transmit responses to requests from an autonomous vehicle while maintaining identification that can be used to make repeated requests to specific vehicles or road infrastructure devices, taking into account factors of dynamic changes in the circumstances of the situation, place and time in which the autonomous vehicle is located.

[0023] DESCRIPTION OF DRAWINGS

[0024] The implementation of the invention will be described below in accordance with the accompanying drawings, which are presented to clarify the essence of the invention and in no way limit the scope of the invention. The following drawings are attached to the application: Fig. 1 illustrates a diagram for registering domain names and services of an intelligent transport system.

[0025] Fig. 2 illustrates the solution of intelligent transport system services to a request from an autonomous vehicle.

[0026] DETAILED DESCRIPTION OF THE INVENTION

[0027] The following detailed description of the invention includes numerous implementation details to provide a clear understanding of the present invention. However, one skilled in the art will readily understand how the present invention may be used with or without these implementation details. In other instances, well-known methods, procedures, and components have not been described in detail to avoid obscuring the features of the present invention.

[0028] Furthermore, it will be clear from the foregoing description that the invention is not limited to the embodiment described. Numerous possible modifications, changes, variations, and substitutions, while preserving the spirit and form of the present invention, will be apparent to those skilled in the art.

[0029] The proposed technical solution is designed to implement a mechanism for selecting data exchange related to the speed, direction, positioning, operating parameters of autonomous vehicle components and assemblies, and the parameters of the autonomous vehicle's interaction with the external environment. These parameters can dynamically change in composition and values ​​depending on the autonomous vehicle's circumstances. Considering that in information systems, an object is a digital twin of a real object, subsequent references to autonomous vehicles or road infrastructure devices imply their digital twins.

[0030] Furthermore, the claimed technical solution relates to the field of intelligent transportation systems (ITS), specifically to methods for identifying and obtaining information from and for an autonomous vehicle based on requests from and for other autonomous vehicles and / or road infrastructure devices via telecommunications networks to solve problems relevant to the situation in which the autonomous vehicle is located, as well as intelligent transportation system services. Prior art includes systems for identifying and obtaining information according to protocols described in ISO and ETSI standards, which define information exchange processes between autonomous vehicles and / or road infrastructure devices. These standards define the general procedure for executing services, as well as the structure and composition of the data involved in information exchange scenarios.

[0031] The initial and most commonly used information exchange scenario is pre-defined rule settings for forwarding data between autonomous vehicles and / or road infrastructure devices.

[0032] The claimed solution implements the ability to determine the choice of the necessary solution depending on the circumstances of the situation, time and location, and the situation in which the autonomous vehicle is located, based on the management of the identification properties of road users and road infrastructure objects.

[0033] The objective of the claimed technical solution is to create a more universal method for identifying autonomous vehicles and the services and services of intelligent transport systems called by them under certain circumstances, which can be applied to any type of services and services, such as, but not limited to, road and lane topology, information about infrastructure and vehicles, traffic light control, priority passage control, including those that do not require a strictly predetermined order of operations.

[0034] The claimed technical solution determines the decision-making process for the exchange of dynamic data, such as, but not limited to, the position in the lane, the speed in the flow, the speed of the flow, the latitude and longitude of the location of the autonomous vehicle, the temperature of the road surface, the speed and direction of the wind, the type of road, the direction of movement, the yaw rate, in the environment of the intelligent transport system, and therefore can contribute to a reduction in the level of technical requirements for equipping autonomous technical means with respect to the number and complexity of sensors and computer algorithms for decision-making.

[0035] Below we will describe the concepts and terms necessary for understanding this technical solution.

[0036] An autonomous vehicle is a vehicle based on an autonomous control system that is fully automated and operates without a driver using sensors such as, but not limited to, determining the coordinates of the current geographic position and altitude, adaptive cruise control, electronic stability control, autonomous emergency braking, forward collision warning, magnetic linear speed sensors, pressure sensors, image recognition sensors, computer algorithms such as, but not limited to, local navigation, routing of autonomous vehicles, coordination of movements of autonomous vehicles at intersections, roundabouts and traffic light junctions, recognition of third-party transport infrastructure objects and other vehicles, formation of policies for the movement of autonomous vehicles depending on current environmental conditions, and electronic communication means.

[0037] An on-board unit of a vehicle is a device installed on a vehicle, including autonomous vehicles, identified by a subscriber telephone number and providing communication and interaction with road infrastructure devices, other vehicles or traffic management systems and supporting the data structure of the services of an intelligent transport system.

[0038] An autonomous vehicle identifier is a unique feature in the form of an ENUM domain name based on a subscriber number in the E.164 format (MSISDN) assigned to the on-board unit of an autonomous vehicle, which allows it to be distinguished in the electronic communications environment from other autonomous vehicles.

[0039] The road infrastructure device identifier is a unique feature in the form of an ENUM domain name based on a subscriber number in the E.164 format (MSISDN) assigned to a road infrastructure device, which allows it to be distinguished in the electronic communications environment from other road infrastructure devices.

[0040] A service identifier is a unique attribute in the form of a domain name assigned to a service used to solve problems of an intelligent transport system and allowing it to be clearly distinguished in the electronic communications environment.

[0041] An intelligent transport system service is a set of telecommunications and non-telecommunications services that provides interactive data exchange to an autonomous vehicle, has a unique or multiple network addresses, and interacts with other third-party applications by exchanging data upon requests from vehicles and / or road infrastructure devices.

[0042] The ENUM registry is an information and telecommunications hardware and software system that enables the registration and storage of information about the properties of autonomous vehicle identifiers and road infrastructure devices in the form of ENUM domain names. The service registry is an information and telecommunications hardware and software system that stores and, upon request, provides information about services, such as (but not limited to) network addresses responsible for processing service requests, protocols and rules for processing requests (request parameters, response receipt, and processing), authentication and authorization requirements, and other metadata. Services in the service registry must always have a unique identifier that can be used to query information about them.

[0043] A resource record is a record in the domain name system (DNS) about the correspondence between a domain name and service information, which contains data about the services (services) whose invocation and resolution is assigned to a given domain name, as well as about the conditions for invocation and resolution of the domain name,

[0044] A road infrastructure device is a device designed to exchange information with autonomous vehicles and other road infrastructure devices to make traffic control decisions or inform road users using sensors, computer algorithms, and electronic communications. This device supports the data structure of intelligent transport system services. Examples of road infrastructure devices include: a road side unit (RSU) (a device installed on road infrastructure (e.g., traffic lights or poles) that collects traffic data and transmits it to an on-board control unit (OBU) in a vehicle), a road controller, and a vehicle detector.

[0045] A digital twin is a service of an intelligent transport system created by third parties, the use of which allows the creation and access of data on an accurate model of the road network and its infrastructure.

[0046] A DNS server is a hardware and software solution for ensuring the functioning of the hierarchical domain name system in accordance with Internet standards, performing operations for recording and storing created resource records.

[0047] The method for exchanging dynamic data with the digital twin of an autonomous vehicle is as follows.

[0048] At the first stage, an ENUM registry (204) of domain names of autonomous vehicles (201) is created (Fig. 1).

[0049] The next stage is the registration of domain names of autonomous (208) vehicles (201) and the registration of domain names (209) of vehicles with an on-board unit (202) in the ENUM registry (204), by converting subscriber telephone numbers (MSISDN), which are assigned by operators to SIM cards installed on the PBX (201) and the vehicle (202).

[0050] After registration, the ENUM registry (204) creates a corresponding resource record about the registered domain name (211) on the DNS server (207), containing an indication of the type of service that can be requested by the vehicle (201) from other vehicles (202) and / or road infrastructure devices (203) to make decisions such as: changing the route of the vehicle, changing the speed limit of the vehicle, requesting the provision of priority passage, etc., as well as personalized conditions for the vehicle (201) such as the density of the traffic flow, the presence of priority passage objects, the duration of the current phase of traffic light objects, etc., under which this service can be performed depending on the circumstances of the situation, place and time.

[0051] They register a domain name (210) for a road infrastructure device (203) such as: RSU, road controller, transport detector, etc., in the ENUM registry (204), by converting MSISDN.

[0052] After registration, the ENUM registry (204) creates a corresponding resource record about the registered domain name (211) of the road infrastructure device (203) on the DNS server (207), containing an indication of the type of service that can be processed by the road infrastructure device (203) to make decisions depending on the requests received from the autonomous vehicle (201).

[0053] A register of services (205) is created, for example, a service for providing priority travel, a service for automated traffic control, etc., into which, on the server of the intelligent transport system service (206), at least one entry (212) is previously entered, characterizing the properties of the intelligent transport system service.

[0054] The domain name of the service is registered and at least one resource record is entered containing the type of service, links to the service registry (205), the service identifier in the ENUM registry (204), and service parameters for further formation of a request to the service registry (205).

[0055] Associations are assigned (214, 216, 218), in part a software binding of the ATS (201) with services (215, 217, 219) with which it can interact (receive and transmit information) is carried out, and the conditions for such interactions are also formed (for example, time of day, day of the week, relationship to organizations carrying out road works or works related to the maintenance and upkeep of roads) between the ATS (201), road infrastructure devices (203), vehicles (202) and services of the intelligent transport system depending on the circumstances of the situation, time and place in which they may be located.

[0056] They receive information from the on-board unit of the ATS (201), including data necessary for a request to perform an intelligent transport system service (Fig. 2), and identify it using the MSISDN, and form a request (224) to perform this service from the ATS (201) to the ENUM registry (204).

[0057] A pool of domain names (225) of other vehicles (202) and road infrastructure devices (203) whose data is relevant for resolving the service requested by the ATS (201) is formed in the ENUM registry (204). Based on the autonomous vehicle identification data via the MSISDN, the ENUM registry (204) determines the domain name and generates a request for its resolution (226) to the DNS server address (207). The resolving request (226) is intended to find the corresponding resource records that were created during the registration of the domain name of the autonomous vehicle (211), as well as resource records about the conditions for performing the required service under certain conditions (224), which were associated as a result of performing the operations (214, 220) and contain instructions for performing the service (206) required for the autonomous vehicle (201) under the established circumstances with the help of sensors and based on the criteria of its algorithmic and software (223).From the found resource records, network identifiers are extracted, by which it is necessary to contact the ITS service server (206), and a request for a service decision (226) relevant to the conditions contained in the request packet from the client application (224) is carried out. The service decision is performed due to resolving the network identifiers of services on the DNS server (207) and due to the fact that the circumstances of the service decision (206) may require obtaining data from road infrastructure devices (203) and / or other vehicles with on-board devices (202), requests for a decision of the ITS service may contain requests for obtaining data from these objects are additionally examined in the link and decision analysis block (222), after which the corresponding requests are sent to the address of the server of the required ITS service (228) and, if necessary, to the address of the road infrastructure device (229), as well as to the address of the vehicle or vehicles (230).Since the identification of all requests is unified due to the use of a domain name system and is of an end-to-end nature for all objects in the environment of operations, responses addressed to the autonomous vehicle (201) from the ITS service server (231), the road infrastructure device (232), and other vehicles (233) are sent to the address of the analysis, communications, and decision block (222), which analyzes the data and sends a decision (234) to the address of the client application of the autonomous vehicle (221), which ensures the processing of the incoming data and generates a response for the actuators of the autonomous vehicle (235) regarding the requested ITS service. In the next cycle, the autonomous vehicle, based on the data from its sensors and the decision-making criteria of the algorithmic and software, generates new requests (236).

[0058] DNS queries (226) are generated for the ENUM domain name pool using the DNS server (207) to obtain resource records that activate the requested services of the intelligent transport system for solving, relevant to the request of the autonomous vehicle (201) and at least one resource record (227) associated with the specified ENUM domain name (204) is sent from the DNS server (207) to the address of the connection and decision analysis unit (222).

[0059] In the block for analyzing connections and decisions (222), from at least one resource record, information is determined about the service identifier, the service type, links to the service server (206), service parameters for further formation of an appeal (228) to the server of the intelligent transport system service (206), and also, if necessary, services for receiving responses to requests (229, 230) to road infrastructure devices (203) and / or other vehicles (202).

[0060] They transmit responses to requests from the ATS (201) while maintaining identification, which can be used to make repeated requests to specific vehicles (202) or road infrastructure devices (203), taking into account factors of dynamic changes in the circumstances of the situation, place and time in which the autonomous vehicle (201) is located.

[0061] A computing system that provides the data processing necessary for the implementation of the claimed solution generally contains the following components: one or more processors, at least one memory, a data storage means, input / output interfaces, an input means, and network interaction means.

[0062] When executing machine-readable instructions contained in the RAM, the processor of the device is configured to perform the basic computing operations necessary for the operation of the device or the functionality of one or more of its components.

[0063] Memory is typically implemented as RAM, which is loaded with the necessary software logic to provide the required functionality. When implementing the proposed solution, the memory capacity required for its implementation is allocated. The data storage device can be an HDD, SSD, RAID array, network storage, flash memory, etc. This device enables long-term storage of various types of information.

[0064] Interfaces are standard means for connecting and operating peripherals and other devices, such as USB, RS232, RJ45, COM, HDMI, PS / 2, Lightning, etc.

[0065] The choice of interfaces depends on the specific device design, which may be a personal computer, mainframe, server cluster, thin client, smartphone, laptop, etc.

[0066] A keyboard may be used as a data input device in any embodiment of the system implementing the described method. The keyboard hardware may be any known hardware implementation: it could be a built-in keyboard used on a laptop or netbook, or a separate device connected to a desktop computer, server, or other computing device. The connection may be either wired, in which the keyboard cable is connected to a PS / 2 or USB port located on the desktop computer's system unit, or wireless, in which the keyboard exchanges data via a wireless communication channel, such as a radio channel, with a base station, which, in turn, is directly connected to the system unit, for example, to one of the USB ports.In addition to the keyboard, data input devices may also include: a joystick, display (touch screen), projector, touchpad, mouse, trackball, light pen, speakers, microphone, etc.

[0067] Network communication tools are selected from devices that provide network data reception and transmission, such as an Ethernet card, WLAN / Wi-Fi module, Bluetooth module, BLE module, NFC module, IrDA, RFID module, GSM modem, etc. These tools enable data exchange via a wired or wireless data transmission channel, such as WAN, PAN, LAN, Intranet, Internet, WLAN, WMAN, or GSM.

[0068] The device components are connected via a common data bus.

[0069] These application materials present a preferred embodiment of the claimed technical solution, which should not be used as limiting other particular embodiments of its implementation that do not go beyond the scope of the requested scope of legal protection and are obvious to specialists in the relevant field of technology. ii

Claims

CLAUSES OF THE INVENTION 1. A method for exchanging dynamic data with a digital twin of an autonomous vehicle, comprising the steps of: - create an ENUM registry of domain names of autonomous vehicles; - register domain names of autonomous vehicles in the ENUM registry by converting the subscriber telephone number (MSISDN); - after registration, the ENUM registry creates a corresponding resource record for the registered domain name on the DNS server, containing an indication of the type of service that may be requested by the autonomous vehicle from other vehicles and / or road infrastructure devices for decision-making, as well as the conditions, personalized for the autonomous vehicle, under which this service may be performed depending on the circumstances of the situation, place and time; - register a domain name for a road infrastructure device in the ENUM registry by converting MSISDN; - after registration, the ENUM registry creates a corresponding resource record for the registered domain name of the road infrastructure device on the DNS server, containing an indication of the type of service that can be processed by the road infrastructure device to make decisions depending on the requests received from the autonomous vehicle; - create a registry of services, into which, on the server of the intelligent transport system service, at least one entry is previously entered that characterizes the properties of the intelligent transport system service; - register the domain name of the service using a network technical solution and enter at least one resource record containing the type of service, links to the service registry, the service identifier in the ENUM registry, and service parameters for further generation of a request to the service registry; - assign associations between autonomous vehicles, road infrastructure devices, vehicles and intelligent transport system services depending on the circumstances of the situation, time and place in which they may be located; - receive information from the on-board unit of an autonomous vehicle, including data necessary for a request to perform an intelligent transport system service, and identify it using the MSISDN, form a request to perform this service from the autonomous vehicle to the ENUM registry; - form in the ENUM registry a pool of domain names of other vehicles and road infrastructure devices, the data from which is relevant for solving the service requested by the autonomous vehicle; - generate DNS queries for the ENUM domain name pool using the DNS server to obtain resource records that activate the requested intelligent transport system services relevant to the autonomous vehicle request and send at least one resource record associated with the specified ENUM domain name from the DNS server to the address of the link and decision analysis unit; - determine in the block for analyzing connections and decisions from at least one resource record information about the service identifier, the type of service, links to the service server, service parameters for further formation of a request to the server of the intelligent transport system service, and also, if necessary, services for receiving responses to requests to road infrastructure devices and / or other vehicles; - transmit responses to requests from an autonomous vehicle while maintaining identification that can be used to make repeated requests to specific vehicles or road infrastructure devices, taking into account factors of dynamic changes in the circumstances of the situation, place and time in which the autonomous vehicle is located.

Images