WO2018000425A1 - Data exchange method, data logger, and unattended device - Google Patents

Abstract

Disclosed is a data exchange method, comprising: receiving by way of an open interface a message to request an application data-packet sequence number; responding to the request message and allocating a data-packet sequence number for the external device; by way of the open interface, sending the allocated data-packet sequence number to the external device. Also disclosed are a data logger and unattended device.

Description

Data interaction method, data recorder and unmanned device

[Technical Field]

The present application relates to the field of data recording, and in particular to a data interaction method, a data logger, and an unmanned device.

 【Background technique】

Data storage in the prior art generally requires a storage space for the data. For dynamic data with a final length that is undetermined, such as real-time parameters acquired from sensors, the storage space also needs to be dynamically allocated. Dynamically allocated storage space is more complex and has a lower storage density. If you need to store multiple dynamic data, it will significantly reduce efficiency.

 [Summary of the Invention]

In order to at least partially solve the above problem, the present invention provides a data interaction method, the method includes: receiving, by an open interface, a request message of an application data packet sequence number sent by an external device; and responding to the request message, assigning a data packet sequence number to the external device; The interface sends the assigned packet sequence number to the external device.

The method further includes: receiving, by the open interface, data sent by the external device, where the data includes the data packet serial number; and writing the data to the memory.

The writing data to the memory includes: adding a corresponding time stamp to the data; and writing the data added with the time stamp to the memory.

The read data request sent by the external device is received via the open interface; the data stored in the memory is read in response to the request and sent to the external device via the open interface.

Wherein, the external device is a device other than the flight controller for recording the running state of the unmanned device and writing data to the data recorder.

The data includes one or both of the following: simulation data generated by the developer according to the development design needs to simulate the operating state of the unmanned device, or flight data.

In order to at least partially solve the above problems, the present invention provides a data interaction method, the method comprising: transmitting a request message for requesting a data packet sequence number to a data logger via an open interface of the data logger; and receiving the data logger to respond to the request message The serial number of the packet.

The method further includes: writing data including the data packet serial number to the data recorder via the open interface.

The data further includes a corresponding timestamp.

The method further includes: writing configuration data including a corresponding data packet sequence number to the data recorder via the open interface, where the configuration data is used to indicate a data format in the corresponding data packet.

The method further includes: reading data from the data recorder via the open interface; and grouping the read data by using the data packet serial number to obtain different data packets.

The data further includes a corresponding timestamp; further comprising: sorting the data in the data packet according to a timestamp; and parsing the sorted data packet.

The parsing the sorted data packet includes: parsing the sorted data packet by using the configuration data.

The data includes one or two of the following: simulation data and flight data generated by the developer according to the development design requirements for simulating the operating state of the unmanned device.

In order to at least partially solve the above problems, the present invention provides a data logger, the device comprising: a controller, a memory and an interface circuit, the controller respectively connecting the memory and the interface circuit; the controller is configured to receive the application sent by the external device via the interface circuit The request message of the packet sequence number; the response request message allocates the packet sequence number to the external device; and transmits the assigned packet sequence number to the external device via the interface circuit.

The controller is further configured to receive data sent by the external device via the interface circuit, where the data includes a data packet sequence number; and the data is written into the memory.

The controller is further configured to add a corresponding time stamp to the data; and write the time-stamped data into the memory.

The controller is further configured to receive, by the interface circuit, a read data request sent by the external device; in response to the request, read the data stored in the memory and send the data to the external device via the interface circuit.

Wherein, the external device is a device other than the flight controller for recording the running state of the unmanned device and writing data to the data recorder.

The data includes one or both of the following: simulation data generated by the developer according to the development design needs to simulate the operating state of the unmanned device, or flight data.

In order to at least partially solve the above problems, the present invention provides an unmanned device comprising: a writing device and the data logger according to any of the above; the writing device for an open interface via the data logger A request message for requesting a data packet sequence number is sent to the data logger, and the data packet number assigned by the data logger in response to the request message is received.

Wherein, the writing device is further configured to write data including the data packet serial number to the data logger via the open interface.

The data further includes a corresponding timestamp.

The writing device is further configured to write configuration data including a corresponding data packet serial number to the data recorder via the open interface, wherein the configuration data is used to indicate a data format in the corresponding data packet.

There is further included a reading device for reading data from the data recorder via the open interface; the read data is grouped by the packet number to obtain different data packets.

The data further includes a corresponding timestamp; the reading device is further configured to sort the data in the data packet according to a timestamp; and parse the sorted data packet.

The reading device further uses the configured configuration data to parse the sorted data packets.

Wherein, the writing device is a device other than the flight controller for recording the operating state of the unmanned device and writing data to the data recorder.

The invention has the beneficial effects of distinguishing different data by using the data packet serial number by applying the data packet serial number, without specifying a storage space, improving efficiency and realizing simplicity.

 [Description of the Drawings]

1 is a flow chart of a first embodiment of a data interaction method of the present invention;

2 is a flow chart of a second embodiment of a data interaction method of the present invention;

3 is a flow chart of a third embodiment of a data interaction method of the present invention;

4 is a flow chart of a fourth embodiment of a data interaction method of the present invention;

FIG. 5 is a flowchart of a fifth embodiment of a data interaction method according to the present invention; FIG.

6 is a flowchart of a sixth embodiment of a data interaction method of the present invention;

7 is a flowchart of a seventh embodiment of a data interaction method of the present invention;

8 is a flow chart of an eighth embodiment of a data interaction method of the present invention;

9 is a flowchart of a ninth embodiment of a data interaction method of the present invention;

Figure 10 is a schematic structural view of a first embodiment of the data logger of the present invention;

Figure 11 is a schematic structural view of a second embodiment of the data logger of the present invention;

Figure 12 is a schematic view showing the structure of the first embodiment of the unmanned device of the present invention.

【detailed description】

The invention will now be described in detail in conjunction with the drawings and embodiments.

As shown in FIG. 1, the first embodiment of the data interaction method of the present invention includes:

S11: Receive a request message of an application packet sequence number sent by the external device via the open interface.

The executor of the external device may be a device other than the executor of the embodiment, and the external device is coupled to the executor of the embodiment through the open interface. An external device can apply for one or more packet sequence numbers, and each packet can include data in one or more formats.

S12: The data packet sequence number is allocated to the external device in response to the request message.

It is determined whether the number of the data packet sequence number is greater than or equal to the threshold value, and if it is less than the threshold value, the data packet sequence number is allocated to the external device in response to the request message; otherwise, the error information is directly returned to the external device.

S13: Send the allocated packet sequence number to the external device via the open interface.

The external device can write the corresponding data by using the assigned packet sequence number.

Through the implementation of the embodiment, before the external device writes the data, the data request packet sequence number is used, and the data packet sequence number is used to distinguish different data, and the storage space is not required, which improves efficiency and is simple to implement.

The execution body of this embodiment may be a data recorder of an unmanned device, and the unmanned device may be an unmanned aerial vehicle, an unmanned ship, an unmanned vehicle, etc., and the unmanned aerial vehicle is taken as an example, and the data recorder may be a drone. The black box is used to record the flight data during the flight of the drone. It can be an independent hardware device or a unit integrated inside the flight controller. The flight controller records the operating status of the unmanned device and the corresponding flight data. Write to the data logger.

In an embodiment of the data interaction method of the present invention, the external device is a device other than a flight controller for recording the operating state of the unmanned device and writing data to the data recorder, such as a smart battery, a control program, and a remote controller. The onboard devices that are external to the developer, etc., can be directly connected to the data logger in a wired or wireless manner, or can be connected to the data logger through a flight controller. Of course, in other embodiments of the data interaction method of the present invention, the external device can also be a flight controller.

As shown in FIG. 2, the second embodiment of the data interaction method of the present invention is based on the first embodiment of the data interaction method of the present invention. After step S13, the method further includes:

S14: Receive data sent by the external device via the open interface.

The data contains the assigned packet sequence number. The data includes at least one of the following: the simulation data generated by the developer according to the development design needs to simulate the operating state of the unmanned device, the flight data, and the configuration information acquired from the remote controller or the control program.

S15: Write data to the memory.

The data can be processed as necessary before writing, such as protocol conversion, serial-to-parallel conversion, or adding necessary information such as start flag, end flag, and verification information. The data stored in the memory is arranged in order according to the writing time. If the memory is full, the writing can be stopped and an error is reported, or part of the data can be automatically deleted and the writing can be continued from the earliest part of the writing time.

As shown in FIG. 3, the third embodiment of the data interaction method of the present invention is based on the second embodiment of the data interaction method of the present invention. Step S15 includes:

S151: Add a corresponding timestamp to the data.

The timestamp may be a string identifying the time at which the timestamp was added, may be used to indicate when the data was written to the memory, or may be a string identifying the time at which the data was received.

S152: Write time-stamped data into the memory.

Timestamps can be used for sorting data within the same packet for subsequent collation and analysis of the data.

Through the implementation of the embodiment, the data recorder uniformly adds a corresponding time stamp to the data, and the external device does not need to add a time stamp to simplify the operation of the external device. Of course, in other embodiments of the data interaction method of the present invention, the external device may add a timestamp by itself, and the data logger may add a timestamp or not.

As shown in FIG. 4, the fourth embodiment of the data interaction method of the present invention is based on the first embodiment of the data interaction method of the present invention, and further includes:

S16: Receive a read data request sent by an external device via an open interface.

The external device that sends the read data request and the external device that writes the data may be the same device or different devices. An external device can request to read data for all packets, or just read data for a specified number of packets.

S17: Read the data stored in the memory in response to the request and send it to the external device via the open interface.

When the external device only reads data of a specified number of data packets, the data logger can send all the readable data stored in the memory to the external device to be filtered by the external device to find out the data to be read. You can filter the data you want to read and send it to an external device.

This embodiment can be combined with any of the above embodiments.

As shown in FIG. 5, the fifth embodiment of the data interaction method of the present invention includes:

S21: Send a request message for requesting a data packet sequence number to the data logger via an open interface of the data logger.

The execution body of this embodiment is an external device that writes data to the data logger, and is coupled to the data logger through an open interface. The data logger can be a data logger for an unmanned device. The unmanned device can be a drone, an unmanned ship, an unmanned vehicle, etc., taking a drone as an example, and the data logger can be a black box for the drone. The flight data during the flight of the drone can be recorded as a stand-alone hardware device or as a unit integrated inside the flight controller. The external device may be other than a flight controller for recording the operating state of the unmanned device and writing data to the data logger, such as a smart battery, a control program, a remote controller, an onboard device external to the developer, etc. The external device can be directly connected to the data logger in a wired or wireless manner, or can be connected to the data logger via a flight controller. Of course, the external device can also be a flight controller.

An external device can apply for one or more packet sequence numbers, and each packet can include data in one or more formats.

S22: Receive a data packet sequence number assigned by the data recorder in response to the request message.

The packet number assigned by the data logger in response to the request message is received via the open interface of the data logger.

Through the implementation of the embodiment, before the external device writes the data, the data request packet sequence number is used, and the data packet sequence number is used to distinguish different data, and the storage space is not required, which improves efficiency and is simple to implement.

As shown in FIG. 6, the sixth embodiment of the data interaction method of the present invention is based on the fifth embodiment of the data interaction method of the present invention. After step S22, the method further includes:

S23: Write data including the data packet serial number to the data logger via the open interface.

Data including the packet number is sent to the data logger via the open interface to write the data. The data includes at least one of the following: the simulation data generated by the developer according to the development design needs to simulate the operating state of the unmanned device, the flight data, and the configuration information acquired from the remote controller or the control program.

In an embodiment of the data interaction method of the present invention, the data further includes a corresponding timestamp, and the timestamp can be used for data sorting in the same data packet, so as to perform subsequent data collation and analysis. The timestamp is added to the data by the external device, and is generally a timestamp indicating the time at which the data was generated, or a timestamp indicating the time at which the data was transmitted.

As shown in FIG. 7, the seventh embodiment of the data interaction method of the present invention is based on the fifth embodiment of the data interaction method of the present invention, and further includes:

S20: Write configuration data including a corresponding packet sequence number to the data logger via the open interface.

The configuration data is used to represent the data format in the corresponding packet. The corresponding data packet sequence number included in the configuration data includes a configuration data packet sequence number indicating that the data is configuration data, and may further include configuration data for indicating a data packet sequence number in which the data format is allocated. The data logger may send the configuration packet sequence number and the assigned packet sequence number to the external device together, or may separately send the configuration packet sequence number, for example, during the initialization of the external device.

This embodiment can be combined with the sixth embodiment of the data interaction method of the present invention. At this time, the step S20 can be performed before, during or after the step S23.

As shown in FIG. 8, the eighth embodiment of the data interaction method of the present invention is based on the fifth embodiment of the data interaction method of the present invention, and further includes:

S24: Reading data from the data logger via an open interface.

You can read the data of all the packets, or you can read only the data of several specified packets.

S25: The read data is grouped by using the packet sequence number to obtain different data packets.

As shown in FIG. 9, the ninth embodiment of the data interaction method of the present invention is based on the eighth embodiment of the data interaction method of the present invention. After step S25, the method further includes:

S26: Sort the data in the data packet by timestamp.

The data in the data packet includes corresponding timestamps, which are generally sorted in ascending order of timestamps.

S27: Parse the sorted data packet.

Generally, the sorted data in the data packet is parsed by using the configuration data corresponding to the data packet, and is represented by graphics, numbers, characters, etc., and can perform operations such as measurement and calculation.

As shown in FIG. 10, the first embodiment of the data logger of the present invention comprises a controller 1, a memory 2 and an interface circuit 3, and the controller 1 is connected to the memory 2 and the interface circuit 3, respectively.

The interface circuit 3 includes an open interface, and is coupled to an external device through an open interface for transmitting and receiving data, and is an interface for the data recorder to communicate with an external device.

The controller 1 controls the operation of the data logger, and the controller 1 can also be called an MCU (Microcontroller) Unit, micro control unit). Controller 1 may be an integrated circuit chip with signal processing capabilities. Controller 1 can also be a general purpose processor, digital signal processor (DSP), application specific integrated circuit (ASIC), off-the-shelf programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware component . The general purpose processor may be a microprocessor or the processor or any conventional processor or the like.

The memory 2 is used to store instructions and data necessary for the operation of the controller 1, and data received by the interface circuit 3. The memory may include a main memory and a cache in which the rate of buffering is higher than the main memory, and data received through the interface circuit 3 may be temporarily stored in the buffer and then written to the main memory.

The controller 1 is configured to receive a request message of the application packet sequence number sent by the external device via the interface circuit 3, assign a packet sequence number to the external device in response to the request message, and transmit the assigned packet sequence number to the external device via the interface circuit 3.

In an embodiment of the data logger of the present invention, the controller is further configured to receive data transmitted by the external device via the interface circuit, wherein the data includes a data packet sequence number; and the data is written to the memory.

In an embodiment of the data logger of the present invention, the controller is further configured to add a corresponding timestamp to the data; and write the timestamped data to the memory.

In an embodiment of the data logger of the present invention, the controller is further configured to receive a read data request sent by the external device via the interface circuit; read the data stored in the memory in response to the request and transmit the data to the external device via the interface circuit.

In an embodiment of the data logger of the present invention, the external device is a device other than the flight controller for recording the operational status of the unmanned device and writing data to the data logger.

In an embodiment of the data logger of the present invention, the data includes at least one of the following: a simulation data generated by the developer according to the development design to simulate the operating state of the unmanned device, flight data, and obtained from a remote controller or a control program. Configuration information.

The functions of the various parts of the data loggers of the present invention may be specifically referred to the description in the corresponding embodiments of the data interaction method of the present invention, and are not repeated here.

As shown in FIG. 11, the first embodiment of the unmanned device of the present invention comprises: a data logger 10 and a writing device 20, which is a data logger as described in any embodiment of the data logger of the present invention.

The writing device 20 is configured to transmit a request message for requesting a data packet number to the data recorder via an open interface in the interface circuit of the data logger 10, and receive a data packet number assigned by the data logger 10 in response to the request message via the open interface.

In an embodiment of the unmanned device of the present invention, the writing device is further for writing data including the data packet number to the data logger via the open interface.

In an embodiment of the unmanned device of the present invention, the data further includes a corresponding time stamp.

In an embodiment of the unmanned device of the present invention, the writing device is further configured to write configuration data including a corresponding data packet number to the data recorder via the open interface, wherein the configuration data is used to indicate a data format in the corresponding data packet.

As shown in FIG. 12, the second embodiment of the unmanned device of the present invention further includes a reading device 30 based on the first embodiment of the unmanned device of the present invention. The reading device 30 is for reading data from the data logger 10 via an open interface; the read data is grouped by the packet number to obtain different packets. The reading device 30 and the writing device 20 shown in the drawing are two separate devices, and the actual reading device 30 and the writing device 20 can also be integrated.

In an embodiment of the unmanned device of the present invention, the data further includes a corresponding time stamp; the reading device is further configured to sort the data in the data packet according to a time stamp; and parse the sorted data packet.

In an embodiment of the unmanned device of the present invention, the reading device is further configured to parse the sorted data packet by using the configuration data.

In an embodiment of the unmanned device of the present invention, the writing device is other than a flight controller for recording the operating state of the unmanned device and writing data to the data logger.

The functions of the various parts in the embodiments of the present invention are specifically described in the corresponding embodiments of the data interaction method of the present invention, and are not repeated here.

In several embodiments provided by the present invention, it should be understood that the disclosed data loggers and unmanned devices can be implemented in other ways. For example, the data recorder and the unmanned device implementation described above are merely illustrative. For example, the division of the module or resource unit is only a logical function division, and the actual implementation may have another division manner. For example, multiple resource units or components may be combined or integrated into another system, or some features may be omitted or not implemented. In addition, the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or resource unit, and may be in an electrical, mechanical or other form.

The resource units described as separate components may or may not be physically separated. The components displayed as resource units may or may not be physical resource units, that is, may be located in one place, or may be distributed to multiple networks. On the resource unit. Some or all of the resource units may be selected according to actual needs to achieve the purpose of the solution of the present embodiment.

In addition, each functional resource unit in each embodiment of the present invention may be integrated into one processing resource unit, or each resource unit may exist physically separately, or two or more resource units may be integrated into one resource unit. The above integrated resource unit can be implemented in the form of hardware or in the form of a software function resource unit.

The integrated resource unit, if implemented in the form of a software functional resource unit and sold or used as a standalone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention, which is essential or contributes to the prior art, or all or part of the technical solution, may be embodied in the form of a software product stored in a storage medium. A number of instructions are included to cause a computer device (which may be a personal computer, server, or network device, etc.) or a processor to perform all or part of the steps of the methods of the various embodiments of the present invention. The foregoing storage medium includes: a U disk, a mobile hard disk, a read only memory (ROM, Read-Only) Memory, random access memory (RAM), disk or optical disk, and other media that can store program code.

The above is only the embodiment of the present invention, and is not intended to limit the scope of the invention, and the equivalent structure or equivalent process transformations made by the description of the invention and the drawings are directly or indirectly applied to other related technologies. The fields are all included in the scope of patent protection of the present invention.

Claims (28)

1. A data interaction method, comprising:

   Receiving, by the open interface, a request message of an application packet sequence number sent by the external device;

   Allocating a data packet sequence number to the external device in response to the request message;

   Transmitting the assigned packet sequence number to the external device via the open interface.
2. The method of claim 1 further comprising:

   Receiving data transmitted by an external device via an open interface, wherein the data includes the data packet sequence number;

   The data is written to the memory.
3. The method of claim 2 wherein:

   The writing the data to the memory comprises:

   Adding a corresponding timestamp to the data;

   Data that joins the timestamp is written to the memory.
4. The method according to any one of claims 1 to 3, further comprising:

   Receiving a read data request sent by the external device via the open interface;

   The data stored in the memory is read in response to the request and sent to the external device via the open interface.
5. A method according to any one of claims 1 to 4, characterized in that

   The external device is a device other than the flight controller for recording the operating state of the unmanned device and writing data to the data logger.
6. A method according to any one of claims 1 to 5, wherein

   The data includes one or both of the following: simulation data generated by the developer according to the development design needs to simulate the operational status of the unmanned device, or flight data.
7. A data interaction method, comprising:

   Sending a request message for requesting a data packet sequence number to the data logger via an open interface of the data logger;

   Receiving a data packet sequence number assigned by the data logger in response to the request message.
8. The method of claim 7 further comprising:

   Data including the packet number is written to the data logger via the open interface.
9. Method according to claim 7 or 8, characterized in that

   The data further includes a corresponding timestamp.
10. The method according to any one of claims 7 to 9, further comprising:

    The configuration data including the corresponding data packet sequence number is written to the data recorder via the open interface, wherein the configuration data is used to indicate a data format in the corresponding data packet.
11. The method according to any one of claims 7 to 10, further comprising:

    Reading data from the data logger via the open interface;

    The read data is grouped by the packet sequence number to obtain different data packets.
12. The method of claim 11 wherein

    The data further includes a corresponding time stamp;

    The method further includes:

    Sorting data in the data packet according to the timestamp;

    Parsing the sorted data packet.
13. The method of claim 12 wherein:

    The parsing the sorted data packet includes:

    The sorted data packet is parsed using the configuration data.
14. A method according to any one of claims 7 to 13, wherein

    The data includes one or both of the following: simulation data generated by the developer according to the development design needs to simulate the operational status of the unmanned device, or flight data.
15. A data logger, comprising:

    a controller, a memory and an interface circuit, the controller respectively connecting the memory and the interface circuit;

    The controller is configured to receive, by using the interface circuit, a request message of an application data packet sequence number sent by an external device; and in response to the request message, assign a data packet sequence number to the external device; and the data packet to be allocated via the interface circuit The serial number is sent to the external device.
16. A data logger according to claim 15 wherein:

    The controller is further configured to receive data transmitted by the external device via the interface circuit, wherein the data includes the data packet sequence number; and the data is written to a memory.
17. A data logger according to claim 16 wherein:

    The controller is further configured to add a corresponding timestamp to the data; write data that adds the timestamp to the memory.
18. A data logger according to any one of claims 15-17, wherein

    The controller is further configured to receive a read data request sent by the external device via the interface circuit; read data stored in the memory in response to the request and send the data to the external via the interface circuit device.
19. A data logger according to any one of claims 15-18, wherein

    The external device is a device other than the flight controller for recording the operating state of the unmanned device and writing data to the data logger.
20. A data logger according to any one of claims 15 to 19, wherein

    The data includes one or both of the following: simulation data generated by the developer according to the development design needs to simulate the operational status of the unmanned device, or flight data.
21. An unmanned device, comprising:

    A writing device and the data logger of any one of claims 15-20;

    The writing device is configured to send a request message for requesting a data packet sequence number to the data recorder via an open interface of the data recorder, and receive a data packet sequence number allocated by the data recorder in response to the request message.
22.  The unmanned device according to claim 21, wherein

    The writing device is further configured to write data including the data packet serial number to the data logger via the open interface.
23. The unmanned device according to claim 21 or 22, characterized in that

    The data further includes a corresponding timestamp.
24. The unmanned device according to any one of claims 21 to 23, characterized in that

    The writing device is further configured to write configuration data including the corresponding data packet sequence number to the data recorder via the open interface, wherein the configuration data is used to indicate a data format in the corresponding data packet.
25. The unmanned device according to any one of claims 21 to 24, further comprising a reading device,

    The reading device is configured to read data from the data logger via the open interface; the read data is grouped by the data packet sequence number to obtain different data packets.
26. The unmanned device according to claim 25, wherein

    The data further includes a corresponding time stamp;

    The reading device is further configured to sort the data in the data packet according to the timestamp; and parse the sorted data packet.
27. The unmanned device according to claim 26, wherein

    The reading device is further configured to parse the sorted data packet by using the configuration data.
28. The unmanned device according to any one of claims 21 to 27, characterized in that

    The writing device is other than a flight controller for recording an operating state of the unmanned device and writing data to the data logger.