WO2017114400A1 - 时序数据检测方法及装置 - Google Patents

时序数据检测方法及装置 Download PDF

Info

Publication number
WO2017114400A1
WO2017114400A1 PCT/CN2016/112486 CN2016112486W WO2017114400A1 WO 2017114400 A1 WO2017114400 A1 WO 2017114400A1 CN 2016112486 W CN2016112486 W CN 2016112486W WO 2017114400 A1 WO2017114400 A1 WO 2017114400A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
time series
lost
series data
time
Prior art date
Application number
PCT/CN2016/112486
Other languages
English (en)
French (fr)
Inventor
于琦
姜艳平
曾米奇
Original Assignee
华为技术有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP16881189.1A priority Critical patent/EP3393085B1/en
Publication of WO2017114400A1 publication Critical patent/WO2017114400A1/zh
Priority to US16/023,490 priority patent/US10911970B2/en
Priority to US17/091,710 priority patent/US11979761B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/10—Scheduling measurement reports ; Arrangements for measurement reports
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/06—Generation of reports
    • H04L43/067—Generation of reports using time frame reporting
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0823—Errors, e.g. transmission errors
    • H04L43/0847—Transmission error
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]

Definitions

  • Embodiments of the present invention relate to data detection technologies, and in particular, to a timing data detection method and apparatus.
  • M2M Machine to Machine
  • time series data or time series data
  • time series data has time. Sequence, dynamic, infinite and unpredictable.
  • oneM2M model is used for storage and transmission of time series data, wherein in the oneM2M model, time series resources and time series instance resources are used to describe data attributes of time series data.
  • the time series data is received and stored through the attribute description of the time series resource and the time series instance resource, but in the data receiving process, it is difficult to avoid data loss, how to perform the time series data loss detection in the M2M model. Reporting is a problem that needs to be solved urgently.
  • the embodiment of the invention provides a method, a device and a device for detecting time series data, so as to implement detection and reporting of lost time series data in the M2M data transmission system.
  • an embodiment of the present invention provides a timing data detecting method, where the method is applied to a data transmission system, including:
  • the data loss notification information is sent to the target device.
  • the method further includes:
  • time series data based on the data information carried by the time series data from the data source device, it is determined whether there is missing time series data during data reception.
  • the method further includes:
  • the first request message carries the following parameters: a maximum lost data amount, a current lost data amount, and a lost data list;
  • the timing resource includes the maximum lost data amount, the current lost data amount, and the The maximum lost data volume attribute, the current lost data volume attribute, and the missing data list attribute respectively established by the lost data list;
  • the maximum lost data amount attribute is used to record the maximum number of lost time series data
  • the current lost data amount attribute is used to record the number of currently lost time series data
  • the lost data list is used to record the lost time series data. Time information and / or serial number.
  • the parameter carried in the first request message further includes: a maximum waiting time
  • the timing resource further includes a longest waiting time attribute established according to the longest waiting time, wherein the longest waiting time attribute is used to identify that the unreceived time series data is determined to be the longest waiting time of the lost time series data. time.
  • the parameter carried in the first request message further includes: a time series data loss notification trigger parameter;
  • the timing resource further includes a subscription resource, where the subscription resource includes a lost data subscription event set according to the time series data loss notification trigger parameter;
  • the lost data subscription event includes the data loss notification trigger condition according to the time series data loss notification trigger parameter setting.
  • the method further includes:
  • the subscription resource is a sub-resource of the time-series resource, and the second request message carries a timing data loss notification trigger parameter;
  • the subscription resource includes a lost data subscription event according to the time series data loss notification trigger parameter setting
  • the lost data subscription event includes the data loss notification trigger condition according to the time series data loss notification trigger parameter setting.
  • the determining, according to time information carried by the time series data from the data source device, whether there is missing time series data during data receiving including:
  • Whether or not there is missing time series data during data reception is determined according to the cycle time carried by the received periodic time series data or the continuity of the sequence number corresponding to the cycle time.
  • the determining whether there is any missing time series data during the data receiving process according to the cycle time carried by the received periodic time series data or the continuity of the sequence number corresponding to the cycle time includes:
  • the time-series data that has not been received after waiting for the preset duration is determined as the lost timing data.
  • the method further includes:
  • the data loss notification triggering condition includes:
  • an embodiment of the present invention provides a time series data detecting method, where the method is applied to a data transmission system, including:
  • time series data carries the data information, the data information including time information and/or sequence number
  • the data receiving device determines, according to the time information and/or the sequence number carried in the received time-series data, whether there is missing time-series data during the data receiving process; Losing time series data, storing data information of the lost time series data; the data receiving device further determining whether a preset data loss notification trigger condition is currently reached; if the data loss notification trigger condition is reached, then the target device is Send a data loss notification message.
  • the method before the sending the time series data to the data receiving device, the method further includes:
  • the first request message carries the following parameters: a maximum lost data amount, a current lost data amount, and a lost data list; and the data receiving device uses, according to the maximum lost data amount, the current lost data amount, and the lost The maximum lost data volume attribute, the current lost data volume attribute, and the missing data list attribute respectively established in the time series resource of the data list;
  • the maximum lost data amount attribute is used to record the maximum number of lost time series data
  • the current lost data amount attribute is used to record the number of currently lost time series data
  • the lost data list is used to record the lost time series data. Time information and / or serial number.
  • the parameter carried in the first request message further includes: a longest waiting time, where the data receiving device establishes a longest waiting time attribute in the time series resource according to the maximum waiting time, The longest waiting time attribute is used for the longest waiting time that the time series data not received by the data receiving device identifier is determined to be lost time series data.
  • the parameter that is carried by the first request message further includes: a time series data loss notification trigger parameter, where the data receiving device sets the lost data in the subscription resource of the time series resource according to the time series data loss notification trigger parameter.
  • the lost data subscription event includes the data loss notification trigger condition according to the time series data loss notification trigger parameter setting.
  • the method further includes:
  • the second request message carries a time-series data loss notification triggering parameter, where the data receiving device uses a lost data subscription event set according to the time-series data loss notification trigger parameter in the created subscription resource; the lost data subscription event
  • the data loss notification trigger condition according to the time series data loss notification trigger parameter setting is included.
  • an embodiment of the present invention provides a timing data detecting apparatus, where the apparatus is applied to a data transmission system, including:
  • a first determining module configured to determine, according to data information carried by the time series data from the data source device, whether there is missing time series data during data receiving, wherein the data information includes time information and/or a sequence number;
  • a storage module configured to save data information of the lost time series data if there is missing time series data
  • a second determining module configured to determine whether a preset data loss notification trigger condition is currently reached
  • the notification message sending module is configured to send the data loss notification information to the target device if the data loss notification trigger condition is reached.
  • the first determining module is further configured to:
  • time series data based on the data information carried by the time series data from the data source device, it is determined whether there is missing time series data during data reception.
  • the device further includes: a timing resource establishing module, configured to determine, according to the data information carried in the time series data from the data source device, whether there is any missing timing data during the data receiving process, according to the data source device Requesting to establish a first request message of a timing resource to establish a timing resource;
  • a timing resource establishing module configured to determine, according to the data information carried in the time series data from the data source device, whether there is any missing timing data during the data receiving process, according to the data source device Requesting to establish a first request message of a timing resource to establish a timing resource;
  • the first request message carries the following parameters: a maximum lost data amount, a current lost data quantity, and a lost data list; and the timing resource includes the maximum loss according to the maximum The amount of data, the current amount of lost data, and the maximum lost data amount attribute, the current lost data amount attribute, and the missing data list attribute respectively established by the lost data list;
  • the maximum lost data amount attribute is used to record the maximum number of lost time series data
  • the current lost data amount attribute is used to record the number of currently lost time series data
  • the lost data list is used to record the lost time series data. Time information and / or serial number.
  • the parameter carried in the first request message further includes: a maximum waiting time
  • the timing resource further includes a longest waiting time attribute established according to the longest waiting time, wherein the longest waiting time attribute is used to identify that the unreceived time series data is determined to be the longest waiting time of the lost time series data. time.
  • the parameter carried in the first request message further includes: a time series data loss notification trigger parameter;
  • the timing resource further includes a subscription resource, where the subscription resource includes a lost data subscription event set according to the time series data loss notification trigger parameter;
  • the lost data subscription event includes the data loss notification trigger condition according to the time series data loss notification trigger parameter setting.
  • the device further includes:
  • a subscription resource establishing module configured to establish a subscription resource by establishing a second request message of the subscription resource according to the request from the data source device;
  • the subscription resource is a sub-resource of the time-series resource, and the second request message carries a timing data loss notification trigger parameter;
  • the subscription resource includes a lost data subscription event according to the time series data loss notification trigger parameter setting
  • the lost data subscription event includes the data loss notification trigger condition according to the time series data loss notification trigger parameter setting.
  • the first determining module is specifically configured to:
  • Whether or not there is missing time series data during data reception is determined according to the cycle time carried by the received periodic time series data or the continuity of the sequence number corresponding to the cycle time.
  • the first determining module is specifically configured to:
  • the time-series data that has not been received after waiting for the preset duration is determined as the lost timing data.
  • the second determining module is further configured to determine whether a lost data subscription event is set in the pre-established subscription resource.
  • the data loss notification triggering condition includes:
  • an embodiment of the present invention provides a timing data detecting apparatus, where the apparatus is applied to a data transmission system, including:
  • time series data generating module configured to generate time series data according to data information of data to be sent, wherein the time series data carries the data information, where the data information includes time information and/or a sequence number;
  • a first sending module configured to send the time series data to the data receiving device, where the data receiving device determines whether there is a data receiving process according to the time information and/or the sequence number carried by the received time series data. Lost time series data; if there is missing time series data, saving data information of the lost time series data; the data receiving device further determines whether a preset data loss notification trigger condition is currently reached; if the data loss notification is reached The trigger condition sends a data loss notification message to the target device.
  • the sending module is further configured to: before sending the time series data to the data receiving device, send, to the data receiving device, a first request message requesting the data receiving device to establish a timing resource;
  • the first request message carries the following parameters: a maximum lost data amount, a current lost data amount, and a lost data list; and the data receiving device is configured to use the maximum lost data according to the data.
  • the maximum lost data amount attribute is used to record the maximum number of lost time series data
  • the current lost data amount attribute is used to record the number of currently lost time series data
  • the lost data list is used to record the lost time series data. Time information and / or serial number.
  • the parameter carried in the first request message further includes: a longest waiting time, where the data receiving device establishes a longest waiting time attribute in the time series resource according to the maximum waiting time, The longest waiting time attribute is used for the longest waiting time that the time series data not received by the data receiving device identifier is determined to be lost time series data.
  • the parameter that is carried by the first request message further includes: a time series data loss notification trigger parameter, where the data receiving device sets the lost data in the subscription resource of the time series resource according to the time series data loss notification trigger parameter.
  • the lost data subscription event includes the data loss notification trigger condition according to the time series data loss notification trigger parameter setting.
  • the device further includes: a second sending module, configured to send, to the data receiving device, a second request message for requesting the data receiving device to establish a subscription resource;
  • the second request message carries a time-series data loss notification triggering parameter, where the data receiving device uses a lost data subscription event set according to the time-series data loss notification trigger parameter in the created subscription resource; the lost data subscription event
  • the data loss notification trigger condition according to the time series data loss notification trigger parameter setting is included.
  • the data receiving device determines, according to the time information of the time series data that has been received, whether there is missing data information time series data during the data receiving process, and the target data is met when the data loss notification trigger condition is met.
  • the device reports the information of the lost time series data, thereby realizing the detection and reporting of the lost time series data in the data transmission system.
  • FIG. 1 is a schematic diagram showing the representation of unique attributes in a time series resource
  • FIG. 2 is a schematic diagram showing the representation of unique attributes in a time series instance resource
  • FIG. 3 is a flow chart showing a method for detecting time series data according to an embodiment of the present invention.
  • FIG. 5 is a schematic diagram showing the representation after adding three unique attributes in the time series resource
  • FIG. 6 is a flowchart of a method for detecting time series data according to Embodiment 3 of the present invention.
  • FIG. 7 is a flowchart of a method for detecting time series data according to Embodiment 4 of the present invention.
  • FIG. 8 is a schematic diagram showing a first representation after adding four unique attributes in a time series resource
  • FIG. 9 is a flowchart of a method for detecting time series data according to Embodiment 5 of the present invention.
  • FIG. 10 is a flowchart showing a method for detecting time series data according to Embodiment 6 of the present invention.
  • FIG. 11 is a flow chart showing a method for detecting time series data according to Embodiment 7 of the present invention.
  • FIG. 12 is a flowchart showing a method for detecting time series data according to Embodiment 8 of the present invention.
  • FIG. 13 is a flowchart showing a method for detecting time series data according to Embodiment 9 of the present invention.
  • FIG. 14 is a schematic structural diagram of a time series data detecting apparatus according to an embodiment of the present invention.
  • FIG. 15 is a schematic structural diagram of a time series data detecting apparatus according to Embodiment 2 of the present invention.
  • FIG. 16 is a block diagram showing the structure of a time series data detecting apparatus according to an embodiment of the present invention.
  • the time series data involved in the M2M application can be divided into periodic times according to the trigger type. Sequence data and event-triggered timing data.
  • a vehicle travel track playback function is provided, which requires the vehicle to periodically send its own location information to a data storage center (such as the cloud) in a 30 second cycle, wherein the transmitted location information can be Including: time, longitude, latitude, speed and other information.
  • the time series data is periodically transmitted by the vehicle terminal, the data transmitted each time is changed, and the vehicle terminal can always send the location information to the data storage center if time and space permit.
  • the smoke alarm when the smoke alarm detects that the smoke concentration in the air reaches a set threshold, an alarm is issued and the event information is sent to the data storage center of the M2M, and the specifically reported event information may include an event occurrence.
  • Information such as time, triggered sensor number and location.
  • the event information sent by the smoke alarm in this example is triggered by a specific event, and the type of time series data is randomly unpredictable, so the generated time series data is also unpredictable.
  • the time series data with time information is different from the traditional data.
  • the time information is one of the distinguishing features of the time series data distinguishing from other traditional data.
  • the time information describes the data between the data stream and the event.
  • a many-to-one or one-to-one mapping relationship that not only reflects the order relationship between data elements and the distribution of data elements in the time domain, but also has important semantic information when describing time-series data operations.
  • the time series data not only reflects the state of the object at a certain moment, but also reflects the overall situation of the object in the past. It can even predict the future development trend of the data object through various means and methods.
  • the oneM2M standard is a combination of M2M communication and Internet of Things (Thing of Internet) communication.
  • data is described by using time series ( ⁇ timeSeries>) and timing instance ( ⁇ timeSeriesInstance>), wherein the time series instance resource is a sub-resource of the time series resource, and the time series data can be realized by the two resources. Storage.
  • the oneM2M standard includes a common attribute, a universal attribute, and a specified attribute, where the unique attribute exists only in the time series resource and the time series instance resource.
  • Figure 1 shows a representation of a unique attribute in a timing resource.
  • Figure 2 shows a representation of the unique attributes in the timing instance resource.
  • the timing resource also contains a subscription ( ⁇ subcription>) resource, which
  • the read resource is a sub-resource of the time series resource.
  • the subscription resource includes an event notification rule (eventNotificationCreteria) and a notification content type (notificationContentType).
  • EventNotificationCreteria an event notification rule
  • NotificationContentType a notification content type
  • the data source device or other attributes that need to obtain related notification messages can subscribe to the related notification information through the subscription resource, and the event notification rule can be specifically
  • the trigger condition for the notification event is set in (eventNotificationCreteria).
  • the time series instance resource is a sub-resource of the time series resource
  • the data object is stored in the content attribute of the time series instance resource
  • the content attribute is saved in the data generation time (dataGenerationTime) attribute. The time at which the data object is saved.
  • the oneM2M standard shown in Figure 1 and Figure 2 implements the collection and storage of time series data, but how to detect and report the lost time series data is still an urgent technical problem to be solved.
  • FIG. 3 is a flowchart of a time series data detecting method according to an embodiment of the present invention.
  • the time series data detecting method shown in FIG. 3 is applied to an M2M data transmission system for implementing loss detection of time series data in an M2M data transmission system.
  • the execution body of the time series data detecting method in this embodiment is a data receiving device, wherein the implementation body of the data receiving device may be an AE (application entity) and a CSE (common service entity), etc., for example,
  • AE application entity
  • CSE common service entity
  • Step S11 Determine whether there is missing time series data during data reception according to time information and/or sequence number carried by the time series data from the data source device.
  • the data source device sends the generated time series data to the data receiving device, and the data receiving device determines whether the value in the missing data detection parameter in the pre-generated time series resource is true, if the parameter is true or When 1, it is determined that the value in the missing data detection parameter is true.
  • the data receiving device may determine, according to the data information of the time series data, whether there is data lost during the data receiving process, for example, the time series data sent by the data source device to the data receiving device is a period.
  • the timing data the data receiving device can determine whether there is missing data according to the periodic characteristics of the time series data.
  • the periodic time series data received by the data receiving device includes t1, t2, t4, and t5, where t1, t2, t4, and t5 1, 2, 4, and 5 can represent the generation time, transmission time, or The number corresponding to the corresponding time, the time interval between adjacent time or adjacent number is one cycle, and the data receiving device determines whether there is missing data according to the number or time in the received time series data. In this example, t3 is missing, the data The receiving device can determine that t3 is lost during data reception.
  • the data source device may perform the triggering time number on the plurality of event-time data sequentially generated, and the data receiving device may determine whether there is missing timing data according to the number of the received event-time data.
  • Step S12 If there is missing time series data, the data information of the lost time series data is saved.
  • the data receiving device determines data information of the lost time series data, such as time information generated by the lost time series data, serial number information, etc., when there is data lost during data reception. Specifically, the data receiving device may determine the data information of the lost time series data according to the time information of the received time series data.
  • Step S13 It is determined whether the preset data loss notification trigger condition is currently reached.
  • the data receiving device After the data receiving device saves the time information and/or the sequence number of the lost time series data, it further determines whether a lost data subscription event is set in the pre-established subscription resource; if yes, determines whether the lost data subscription event is currently reached.
  • a pre-set data loss notification trigger condition After the data receiving device saves the time information and/or the sequence number of the lost time series data, it further determines whether a lost data subscription event is set in the pre-established subscription resource; if yes, determines whether the lost data subscription event is currently reached.
  • a pre-set data loss notification trigger condition A pre-set data loss notification trigger condition.
  • Step S14 If the data loss notification trigger condition is reached, the data loss notification information is sent to the target device.
  • the time series data detecting method of the embodiment of the present invention is executed based on the M2M data transmission standard, in which the data receiving device determines, according to the time information of the time series data that has been received, whether there is missing data information time series data during the data receiving process, and The information of the lost time series data is reported to the target device when the data loss notification trigger condition is met, thereby realizing the detection and reporting of the lost time series data in the M2M data transmission system.
  • FIG. 4 is a flowchart of a method for detecting a time series data according to a second embodiment of the present invention.
  • the method is applied to an M2M data transmission system, and the main body of the method is a data receiving device.
  • the specific execution steps of the method include:
  • Step S21 Establish a first request message of the timing resource according to the request from the data source device, and establish a timing resource.
  • the first request message received by the data receiving device carries the following parameters: a maximum amount of lost data, a current amount of lost data, and a list of lost data.
  • the data receiving device establishes a maximum lost data amount attribute, a current lost data quantity attribute, and a lost data list attribute respectively in the time series resource according to the maximum lost data amount, the current lost data amount, and the lost data list in the first request message.
  • FIG. 5 shows a schematic diagram of the representation after adding three unique attributes to the time series resource.
  • the timing resource shown in FIG. 5 adds a maximum lost data amount attribute (maxMissingNr), a current missing data amount (currentMissingNr) attribute, and a missing data list (missingList) attribute to the time series resource shown in FIG. 1.
  • maxMissingNr maximum lost data amount attribute
  • currentMissingNr currentMissingNr
  • missingList missing data list
  • Table 1 shows the attribute information of the maximum lost data amount attribute, the current lost data amount attribute, and the missing data list attribute added in the time series resource.
  • the maximum lost data (maxMissingNr) attribute is used to record the maximum number of lost time series data (generally a preset fixed value), and the current lost data amount (currentMissingNr) attribute is used to record the current loss.
  • the number of time series data, the missing data list missingList) is used to record the data information of the lost time series data, wherein the data receiving device will store the earliest value when the value in the current lost data amount exceeds the value set in the maximum lost data amount.
  • the data information of the incoming at least one time series data is deleted from the lost data list, whereby the data information of the newly detected lost time series data can be continuously inserted in the lost data list.
  • Step S22 Establish a second request message of the sequence instance resource according to the request from the data source device, and establish a sequence instance resource.
  • the established timing instance resource is shown in FIG. 2, and the sequential instance resource is a sub-resource of the sequential resource.
  • Step S23 Establish a third request message of the subscription resource according to the request from the data source device, and establish a subscription resource.
  • the third request message received by the data receiving device in the embodiment carries a time series data loss notification trigger parameter; the subscription resource includes a lost data subscription event set according to the time series data loss notification trigger parameter; the lost data subscription The event includes the data loss notification trigger condition according to the time series data loss notification trigger parameter setting.
  • the data source device establishes a subscription resource by requesting the data receiving device, and requests the data receiving device to create a lost data subscription event in the subscription resource, and the lost data subscription event includes a data loss notification trigger condition, thereby enabling the data receiving device to lose the timing
  • the data is detected, and when the condition is met, the data receiving device is triggered to send related information of the lost time series data to the target device.
  • the target device may be a data source device, or may be another device that needs to obtain time series data loss information.
  • the data loss device triggers the data loss notification triggering condition according to the received time series data loss notification trigger parameter, including: whether the current time reaches the reporting time set in the preset lost data reporting period; and/or, Whether the number of time series data that has been lost has reached the preset number of reports.
  • Table 2 shows a specific definition of the time series data loss notification trigger parameter (time series Criteria) in the third request message.
  • the data receiving device establishes a data loss notification trigger condition in the event notification rule (eventNotificationCreteria) attribute of the subscription resource according to the time series data loss notification trigger parameter.
  • eventNotificationCreteria event notification rule
  • Step S24 determining whether the value in the missing data detection parameter in the pre-established time series resource is true; if true, performing step S25; otherwise, the lost data subscription event in the subscription resource returns a lost data detection error or cannot perform loss data detection. And other feedback information.
  • the missing data detection (missing dataDetect) parameter is further included in the time series resource generated by the data receiving device.
  • the value in the lost data detection parameter is true or 1
  • the value in the lost data detection parameter is determined to be true.
  • the data receiving device detects whether there is missing timing data during data reception.
  • Step S25 Determine whether there is missing time series data during data reception according to time information and/or sequence number carried by the time series data from the data source device.
  • Step S26 If there is missing time series data, the data information of the lost time series data is saved.
  • step S27 when the data loss notification trigger condition is set in the subscription resource, it is determined whether the preset data loss notification trigger condition is currently reached.
  • Step S28 If the data loss notification trigger condition is reached, the data loss notification information is sent to the target device.
  • the data loss notification information is sent to the data receiving device, where the sent notification information may include only the data loss prompt information, or may include Specific information about lost time series data.
  • the time series data detecting method of the embodiment of the present invention implements detection and reporting of lost data in M2M.
  • FIG. 6 is a flow chart showing a method for detecting time series data according to Embodiment 3 of the present invention.
  • the time series data detecting method shown in FIG. 6 is a specific example of the time series data detecting method shown in FIG. 4, and the main processing steps of the method include:
  • Step S201 The data source device sends a first request message requesting the data receiving device to create a timing resource to the data receiving device, where the first request message carries the following parameters: a maximum lost data amount (maxMissingNr), and a current lost data amount (currentMissingNr) ) and the missing data list (missingList).
  • maximumMissingNr a maximum lost data amount
  • currentMissingNr currentMissingNr
  • Step S202 The data receiving device creates a time-series resource according to the received first request message, where the newly added attribute in the created time-series resource includes the maximum lost data amount (maxMissingNr) attribute and the current lost data quantity (currentMissingNr) as shown in Table 1. Attributes and missing data list (missingList) attributes.
  • Step S203 After the data receiving device successfully creates the time series resource, the first response message is sent to the data source device.
  • Step S204 The data source device sends a second request message requesting the data receiving device to create a sequence instance resource to the data receiving device.
  • Step S205 The data receiving device creates a time series instance resource according to the received second request message, where the time series instance resource is a child resource of the time series resource created in step S202.
  • the data source device may request the data receiving device to create a plurality of time series instance resources, wherein the plurality of time series instance resources created are the child resources of the time series resource.
  • Step S206 After the data receiving device successfully creates the sequence instance resource, the second response message is sent to the data source device.
  • Step S207 The data source device sends a request to the data receiving device to create a data receiving device.
  • the third request message of the subscription resource is configured, wherein the third request message carries the time series data loss notification trigger parameter (ie, timeSeriesCriteria, time series standard), and the definition rules of the time series data loss notification trigger parameter are as shown in Table 2.
  • the number parameter in the timeSeriesCriteria is set to 4, and when the data receiving device detects that the number of lost time series data reaches four, a data loss notification message is sent to the target device.
  • the data receiving device can send a data loss notification message to the target device every 10 minutes according to the detected time series data condition.
  • the data receiving device takes 10 minutes as a monitoring period, and when the number of time series data lost in the current monitoring period reaches 4, The target device sends a data loss notification message, otherwise the data receiving device enters the statistics of the number of lost time series data in the next monitoring period.
  • the timeSeriesCriteria parameter is set to: when the number parameter is set to 4 or the monitoring period is set to 10 min, the number of lost time series data reaches 4 or the current monitoring time reaches 10 minutes, as long as one of the conditions is met, the target device is triggered.
  • the operation of sending a data loss notification message is set to: when the number parameter is set to 4 or the monitoring period is set to 10 min, the number of lost time series data reaches 4 or the current monitoring time reaches 10 minutes, as long as one of the conditions is met, the target device is triggered. The operation of sending a data loss notification message.
  • Step S208 The data receiving device creates a subscription resource according to the third request message.
  • the data receiving device includes: in the process of creating the subscription resource, the data receiving device creates a data loss notification event according to the timeSeriesCriteria carried in the third request message, and includes a data loss notification triggering condition in the data loss notification event.
  • the data receiving device establishes a data loss notification trigger condition in the event notification rule (eventNotificationCreteria) attribute of the subscription resource according to the time series data loss notification trigger parameter.
  • eventNotificationCreteria event notification rule
  • Step S209 After the data receiving device succeeds in creating the time series resource, the third response message is sent to the data source device.
  • Step S210 The data receiving device collects and stores the time series data, and compares the number of timings. According to the loss detection and reporting.
  • the timing resource generated by the data receiving device further includes a missing data detection parameter, and before determining the time series data, further determining whether the value in the missing data detection parameter is true, when the data detection parameter is lost.
  • the data receiving device detects whether there is missing time series data during data reception; if the value in the lost data detection parameter is not true, the lost data subscription event in the subscription resource returns a lost data detection error. Or feedback information such as lost data detection cannot be performed.
  • the data receiving device reports the lost time series data including:
  • the data receiving device determines that the current status meets the data loss notification condition set in the subscription resource
  • the data loss notification message (Notify Request) is sent to the target device.
  • the data receiving device may determine, according to the notification content type (notificationContentType) in the subscription resource.
  • the content carried in the data loss notification message may, for example, carry a missing data list (missingList) and/or a current lost data amount (currentMissingNr).
  • the data receiving device inserts the data generation time (dataGenerationTime) and/or sequence number (sequenceNr) of the lost time series data into the missing data list (missingList) every time a time series data loss is detected during the time series data loss detection process. In the middle, and the value of the current lost data (currenMissingNr) is increased by one. When the value of the current lost data amount (currenMissingNr) reaches the value set in the maximum missing number (max Missing Nr), the data receiving device will lose the earliest at least one data generation time (dataGenerationTime) and/or sequence in the missing list (missingList). The sequenceNr is deleted for inserting the data generation time (dataGenerationTime) and/or the sequence number (sequenceNr) of the newly detected lost time series data.
  • the number parameter in the timeSeriesCriteria is set to 4, and when the data receiving device detects that the number of lost time series data reaches 4 (for example, the lost time series data includes t1, t5, t10, t11), the data receiving device transmits to the target device.
  • the data loss notification message the specific data receiving device may send the notification message of the data loss only to the target device according to the setting in the notification content type (notificationContentType), or carry the missing data list (missingList) and/or in the data loss notification message.
  • the current amount of data lost currentMissingNr).
  • the monitoring period in the timeSeriesCriteria is set to be 10 minutes.
  • the data receiving device can send a data loss notification message to the target device every 10 minutes regardless of whether the lost time series data is detected, or the data receiving device determines the current Whether the lost time series data is detected within the monitoring period (10 minutes), if detected, the data loss notification message is reported to the target device at the end of the current period and the lost data detection is entered in the next period, if no loss is detected in the current period The time series data goes directly to the next cycle for loss timing data detection.
  • the data receiving device detects whether the number of time series data lost in the current monitoring period (within 10 minutes) reaches 4, and if so, to the target device. Send a data loss notification message, otherwise it will not be sent.
  • the parameter in the timeSeriesCriteria is set to: when the number parameter is set to 4 or the monitoring period is set to 10 min, the data receiving device determines whether the currently detected lost time series data reaches 4 or whether the reporting time set is reached (10). Minutes), as long as one of the conditions is met, a data loss notification message is sent to the target device.
  • Step S211 The data receiving device sends a data loss notification message to the target device.
  • the data receiving device sends a data loss notification message to the target device.
  • the specific process may include: the data receiving device sends a notification request message (Notify Request) to the target device, where the notification request message carries specific notification content, such as a missing data list (missingList) and/or Or the current lost data amount (currentMissingNr); the target device returns a notification response message to the data receiving device after receiving the notification message sent by the data receiving device.
  • FIG. 7 is a flowchart of a method for detecting time series data according to Embodiment 4 of the present invention.
  • the method is applied to an M2M data transmission system, and the main body of the implementation is a data receiving device, such as a storage cloud.
  • the method in this embodiment is shown in FIG.
  • the maximum loss data amount, the current lost data amount, the lost data list, and the longest waiting time are added to the time series resource, and the data loss notification trigger condition is set in the event notification rule attribute of the subscription resource, so that the data receiving device is in the When the loss condition of the detected time series data meets the trigger condition of the data loss notification, the data loss notification message is sent to the target device.
  • the specific execution steps of the method include:
  • Step S31 Establish a first request message of the timing resource according to the request from the data source device, and establish a timing resource.
  • the first request message received by the data receiving device carries the following parameters: maximum lost data amount, current lost data amount, lost data list, and maximum waiting time.
  • the data receiving device establishes a maximum lost data amount attribute, a current lost data quantity attribute, a lost data list attribute, and a longest according to the maximum lost data amount, the current lost data amount, the lost data list, and the longest waiting time in the first request message, respectively. Waiting time attribute.
  • FIG. 8 is a schematic diagram showing a first representation after adding four unique attributes in a time series resource.
  • Table 3 shows the attribute information of the maximum lost data amount attribute, the current lost data amount attribute, and the missing data list attribute added in the time series resource.
  • the maximum lost data volume attribute, the current lost data volume attribute, and the missing data list attribute in Table 3 have the same meanings as in the second embodiment, and are not described again.
  • the newly added longest waiting time attribute is used to identify the unreceived time series data. The longest wait time determined to be missing timing data.
  • Step S32 Establish a second request message of the sequence instance resource according to the request from the data source device, and establish a sequence instance resource.
  • the established timing instance resource is shown in FIG. 2, and the sequential instance resource is a sub-resource of the sequential resource.
  • Step S33 Establish a third request for the subscription resource according to the request from the data source device. Information, create a subscription resource.
  • the third request message received by the data receiving device in the embodiment carries a time series data loss notification trigger parameter; the subscription resource includes a lost data subscription event set according to the time series data loss notification trigger parameter; the lost data subscription The event includes the data loss notification trigger condition according to the time series data loss notification trigger parameter setting.
  • the data source device establishes a subscription resource by requesting the data receiving device, and requests the data receiving device to create a lost data subscription event in the subscription resource, and the lost data subscription event includes a data loss notification trigger condition, thereby enabling the data receiving device to lose the timing
  • the data is detected, and when the condition is met, the data receiving device is triggered to send related information of the lost time series data to the target device.
  • the third request message received by the data receiving device in the embodiment carries the time series data loss notification trigger parameter; the subscription resource includes a data loss notification trigger condition set according to the time series data loss notification trigger parameter.
  • the data loss notification triggering parameters set in this embodiment are the same as those in Table 2 in the second embodiment, and are not described again.
  • Step S34 determining whether the value in the missing data detection parameter in the pre-established time series resource is true; if true, executing step S35; otherwise, the lost data subscription event in the subscription resource returns a lost data detection error or cannot perform loss data detection. And other feedback information.
  • the missing data detection (missing dataDetect) parameter is further included in the time series resource generated by the data receiving device.
  • the value in the lost data detection parameter is true or 1
  • the value in the lost data detection parameter is determined to be true.
  • the data receiving device detects whether there is missing timing data during data reception.
  • Step S35 Determine whether there is missing time series data during data reception according to time information and/or sequence number carried by the time series data from the data source device.
  • Step S36 If there is unreceived time series data, it is determined whether there is still unreceived time series data after waiting for the preset time length.
  • Step S37 If there is still unscheduled time series data, the time series data that has not been received after waiting for the preset time length is determined as the lost time series data.
  • the values of the preset durations in the present embodiment S36 and S37 are the same as those in the longest waiting time (maxDetectingTime) in Table 3.
  • Step S38 When the data loss notification trigger condition is set in the subscription resource, it is determined whether the data loss notification trigger condition in the subscription resource is currently reached.
  • Step S39 If the data loss notification trigger condition is reached, the data loss notification information is sent to the target device.
  • the longest waiting time attribute is set in the embodiment of the present invention, and the data receiving device determines that there is an unreceived timing, in order to avoid the occurrence of a misjudgment.
  • the data receiving device determines that there is an unreceived timing, in order to avoid the occurrence of a misjudgment.
  • it waits for a preset duration, and determines whether the timing data is received after the preset duration, and if it is still not received, determines that the timing data is lost timing data.
  • the time series data detecting method of the embodiment of the invention can improve the accuracy of data loss detection and reporting.
  • FIG. 9 is a flow chart showing a method for detecting time series data according to Embodiment 5 of the present invention.
  • the time series data detecting method shown in FIG. 9 is a specific example of the time series data detecting method shown in FIG. 7.
  • the main processing steps of the method include:
  • Step S301 The data source device sends a first request message requesting the data receiving device to create a timing resource to the data receiving device, where the first request message carries the parameter maximum lost data amount (maxMissingNr), the current lost data amount (currentMissingNr), Missing data list (missingList) and maximum waiting time (maxDetectingTime).
  • maxMissingNr the parameter maximum lost data amount
  • currentMissingNr the current lost data amount
  • MissingList Missing data list
  • maxDetectingTime maximum waiting time
  • Step S302 The data receiving device creates a time series resource according to the received first request message, where the newly added attribute in the created time series resource includes the maximum lost data quantity (maxMissingNr) attribute and the current lost data quantity (currentMissingNr) as shown in Table 3. Attribute, missing data list (missingList) attribute and maximum wait time (maxDetectingTime) attribute.
  • Step S303 After the data receiving device succeeds in creating the time series resource, the first response message is sent to the data source device.
  • Step S304 The data source device sends a second request message requesting the data receiving device to create a time series instance resource to the data receiving device.
  • Step S305 The data receiving device creates a sequence instance resource according to the received second request message, where the sequence instance resource is a sub-resource of the time series resource created in step S302.
  • the data source device may request the data receiving device to create a plurality of time series instance resources, wherein the plurality of time series instance resources created are the child resources of the time series resource.
  • Step S306 After the data receiving device creates the sequence instance resource successfully, the data source device is sent to the data source device. Send a second response message.
  • Step S307 The data source device sends a third request message requesting the data receiving device to create a subscription resource to the data receiving device, where the third request message carries the time series data loss notification trigger parameter (ie, timeSeriesCriteria, time series standard), and the time series data.
  • time series data loss notification trigger parameter ie, timeSeriesCriteria, time series standard
  • the number parameter in the Time Series Criteria is set to 4, and when the data receiving device detects that the number of lost time series data reaches four, a data loss notification message is sent to the target device.
  • the data reception sends a data loss notification message to the target device every 10 minutes.
  • the data receiving device takes 10 minutes as a monitoring period, and when the number of time series data lost in the current monitoring period reaches 4, The target device sends a data loss notification message, otherwise the data receiving device enters the statistics of the number of lost time series data in the next monitoring period.
  • the timeSeriesCriteria parameter is set to: when the number parameter is set to 4 or the monitoring period is set to 10 min, when the lost time series data reaches 4 or the current monitoring time reaches 10 minutes, as long as one of the conditions is met, the target device is triggered.
  • the operation of sending a data loss notification message is set to: when the number parameter is set to 4 or the monitoring period is set to 10 min, when the lost time series data reaches 4 or the current monitoring time reaches 10 minutes, as long as one of the conditions is met.
  • Step S308 The data receiving device creates a subscription resource according to the third request message.
  • the data receiving device includes: in the process of creating the subscription resource, the data receiving device creates a data loss notification event according to the timeSeriesCriteria carried in the third request message, and includes a data loss notification triggering condition in the data loss notification event.
  • the data receiving device establishes a data loss notification trigger condition in the event notification rule (eventNotificationCreteria) attribute of the subscription resource according to the time series data loss notification trigger parameter.
  • eventNotificationCreteria event notification rule
  • Step S309 After the data receiving device succeeds in creating the time series resource, the third response message is sent to the data source device.
  • Step S310 The data receiving device collects and stores the time series data, and performs loss detection and reporting on the time series data.
  • the timing resource generated by the data receiving device further includes a missing data detection parameter, and before determining the time series data, further determining whether the value in the missing data detection parameter is true, when the data detection parameter is lost.
  • the data receiving device detects whether there is missing time series data during data reception; if the value in the lost data detection parameter is not true, the lost data subscription event in the subscription resource returns a lost data detection error. Or feedback information such as lost data detection cannot be performed.
  • the data receiving device loses the time series data based on the maximum waiting time (maxDetectingTime), the maximum lost data amount (maxMissingNr), the current lost data amount (currentMissingNr), and the missing data list (missingList) parameter in the time series resource. Detection and reporting.
  • the data receiving device performs loss detection on the time series data, and the data receiving device determines, according to the time information carried in the time series data from the data source device, whether there is missing time series data during the data receiving process; if there is an unreceived
  • the time series data determines whether there is still unreceived time series data after waiting for the preset time length; if there is still unreceived time series data, the time series data that has not been received after waiting for the preset time length is determined to be lost. Time series data.
  • the data receiving device When the data receiving device reports the time series data, the data receiving device sends a data loss notification message (Notify Request) to the target device when the current status meets the data loss notification condition set in the subscription resource.
  • the data receiving device can be subscribed according to the subscription.
  • the notification content type (notificationContentType) in the resource determines the content carried in the data loss notification message, for example, may carry a missing data list (missingList) and/or current lost data amount (currentMissingNr).
  • the data receiving device inserts the data generation time (dataGenerationTime) and/or sequence number (sequenceNr) of the lost time series data into the missing data list (missingList) every time a time series data loss is detected during the time series data loss detection process. In the middle, and the value of the current lost data (currenMissingNr) is increased by one. The value of the current lost data (currenMissingNr) reaches the maximum number of lost When the value is set in (maxMissingNr), the data receiving device deletes the earliest at least one data generation time (dataGenerationTime) and/or sequence number (sequenceNr) in the missing data list (missingList) for inserting the newly detected loss timing. The data generation time (dataGenerationTime) and/or sequence number (sequenceNr) of the data.
  • the number parameter in the timeSeriesCriteria is set to 4, and when the data receiving device detects that the number of lost time series data reaches 4 (for example, the lost time series data includes t1, t5, t10, t11), the data receiving device transmits to the target device.
  • the data loss notification message the specific data receiving device may send the notification message of the data loss only to the target device according to the setting in the Notification Content Type, or carry the missing data list (missingList) and the data loss notification message. / or the current amount of lost data (currentMissingNr).
  • the monitoring period in the timeSeriesCriteria is set to be 10 minutes.
  • the data receiving device can send a data loss notification message to the target device every 10 minutes regardless of whether the lost time series data is detected, or the data receiving device determines the current Whether the lost time series data is detected within the monitoring period (10 minutes), if detected, the data loss notification message is reported to the target device at the end of the current period and the lost data detection is entered in the next period, if no loss is detected in the current period The time series data goes directly to the next cycle for loss timing data detection.
  • the data receiving device detects whether the number of time series data lost in the current monitoring period (within 10 minutes) reaches 4, and if so, to the target device. Send a data loss notification message, otherwise it will not be sent.
  • the parameter in the timeSeriesCriteria is set to: when the number parameter is set to 4 or the monitoring period is set to 10 min, the data receiving device determines whether the currently detected lost time series data reaches 4 or whether the reporting time set is reached (10). Minutes), as long as one of the conditions is met, a data loss notification message is sent to the target device.
  • Step S311 The data receiving device sends a data loss notification message to the target device.
  • the data receiving device sends a data loss notification message to the target device.
  • the specific process may include: the data receiving device sends a notification request message (Notify Request) to the target device, where the notification request message carries specific notification content, such as a missing data list (missingList) and/or Or the current amount of lost data (currentMissingNr); the target device receives the data receiving device to send The notification message returns a notification response message to the data receiving device.
  • FIG. 10 is a flowchart of a method for detecting time series data according to Embodiment 6 of the present invention.
  • the method is applied to an M2M data transmission system, and the main body of the method is a data receiving device, such as a storage cloud.
  • the method in this embodiment is shown in FIG.
  • the maximum loss data amount, the current lost data amount, the missing data list, and the time series data loss notification trigger parameter are added to the time series resource, and the data loss notification trigger condition is set in the event notification rule attribute of the subscription resource, so that the data is made.
  • the receiving device sends a data loss notification message to the target device when the loss condition of the detection time data meets the data loss notification triggering condition.
  • the specific execution steps of the method include:
  • Step S401 The data source device sends a first request message requesting the data receiving device to create a timing resource to the data receiving device.
  • the first request message carries the following parameters: a maximum lost data amount, a current lost data amount, a lost data list, and a time series data loss notification trigger parameter.
  • Step S402 The data receiving device establishes a timing resource according to the first request message.
  • the data receiving device establishes a maximum lost data amount attribute and a current lost data quantity in the time series resource according to the maximum lost data quantity, the current lost data quantity, the missing data list, and the time series data loss notification trigger parameter in the received first request message. Attributes, missing data list attributes, and time series data loss notification parameter attributes.
  • Table 4 shows the attribute information of the maximum lost data amount attribute, the current lost data amount attribute, the missing data list attribute, and the time series data loss notification parameter attribute added in the time series resource.
  • the maximum lost data volume attribute, the current lost data volume attribute, and the missing data list attribute in Table 4 in this embodiment are the same as those in the first embodiment of Table 1, and are not described again.
  • the time series data loss notification triggering parameter attribute in Table 4 is The time series data loss notification in Table 2 triggers the same in the parameter definition table, and will not be described again.
  • Step S403 After the data receiving device successfully creates the time series resource, the first response message is sent to the data source device.
  • Step S404 The data source device sends a second request message requesting the data receiving device to create a sequence instance resource to the data receiving device.
  • Step S405 The data receiving device creates a time series instance resource according to the received second request message, where the time series instance resource is a child resource of the time series resource created in step S402.
  • Step S406 After the data receiving device creates the sequence instance resource successfully, the data source device is sent to the data source device. Send a second response message.
  • Step S407 The data source device sends a third request message requesting the data receiving device to create a subscription resource to the data receiving device.
  • Step S408 The data receiving device creates a subscription resource according to the third request message and the data loss notification trigger parameter in the first request message.
  • the data receiving device includes: in the process of creating the subscription resource, the data receiving device creates a data loss notification event according to the data loss notification trigger parameter in the first request message, and includes a data loss notification trigger condition in the data loss notification event.
  • the data receiving device establishes a data loss notification trigger condition in the event notification rule (eventNotificationCreteria) attribute of the subscription resource according to the time series data loss notification trigger parameter.
  • eventNotificationCreteria event notification rule
  • Step S409 After the data receiving device successfully creates the time series resource, the data receiving device sends a third response message to the data source device.
  • Step S410 The data receiving device collects and stores the time series data, and performs loss detection and reporting on the time series data.
  • the timing resource generated by the data receiving device further includes a missing data detection parameter, and before determining the time series data, further determining whether the value in the missing data detection parameter is true, when the data detection parameter is lost.
  • the data receiving device detects whether there is missing time series data during data reception; if the value in the lost data detection parameter is not true, the lost data subscription event in the subscription resource returns a lost data detection error. Or feedback information such as lost data detection cannot be performed.
  • the method for performing the loss detection and reporting on the time series data in the data receiving device in this embodiment is the same as that in the second embodiment, and details are not described herein again.
  • Step S411 The data receiving device sends a data loss notification message to the target device.
  • the data receiving device sends a data loss notification message to the target device.
  • the specific process may include: the data receiving device sends a notification request message (Notify Request) to the target device, where the notification request message carries specific notification content, such as a missing data list (missingList) and/or Or the current lost data amount (currentMissingNr); the target device returns a notification response message to the data receiving device after receiving the notification message sent by the data receiving device.
  • FIG. 11 is a flowchart of a method for detecting time series data according to Embodiment 7 of the present invention.
  • the method is applied to an M2M data transmission system, and the main body of the implementation is a data receiving device, such as a storage cloud.
  • the method in this embodiment is shown in FIG.
  • the five attributes of the maximum lost data amount, the current lost data amount, the lost data list, the longest waiting time, and the time series data loss notification trigger parameter are added to the time series resource, and the data loss notification is set in the event notification rule attribute of the subscription resource.
  • the triggering condition is such that the data receiving device sends a data loss notification message to the target device when the loss condition of the detected time series data meets the data loss notification triggering condition.
  • the specific execution steps of the method include:
  • Step S501 The data source device sends a first request message requesting the data receiving device to create a timing resource to the data receiving device.
  • the first request message carries the following parameters: a maximum lost data amount, a current lost data amount, a lost data list, and a time series data loss notification trigger parameter.
  • Step S502 The data receiving device establishes a timing resource according to the first request message.
  • the data receiving device establishes a maximum lost data amount attribute and a current lost data quantity in the time series resource according to the maximum lost data quantity, the current lost data quantity, the missing data list, and the time series data loss notification trigger parameter in the received first request message. Attributes, missing data list attributes, and time series data loss notification attributes.
  • Table 5 shows the attribute information of the maximum lost data amount attribute, the current lost data amount attribute, the missing data list attribute, and the time series data loss notification attribute added in the time series resource.
  • the maximum lost data amount attribute, the current lost data quantity attribute, the lost data list attribute, and the time series data loss notification attribute in Table 5 in this embodiment are the same as those in Table 4, and the longest waiting time attribute in Table 5 is not described again. The same as in 4, no longer repeat them.
  • Step S503 After the data receiving device successfully creates the timing resource, the first response message is sent to the data source device.
  • Step S504 The data source device sends a second request message requesting the data receiving device to create a time series instance resource to the data receiving device.
  • Step S505 The data receiving device creates a timing instance according to the received second request message.
  • the resource, wherein the time series instance resource is a child resource of the time series resource created in step S502.
  • Step S506 After the data receiving device successfully creates the sequence instance resource, the second response message is sent to the data source device.
  • Step S507 The data source device sends a third request message requesting the data receiving device to create a subscription resource to the data receiving device.
  • Step S508 The data receiving device creates a subscription resource according to the third request message and the data loss notification trigger parameter in the first request message.
  • the data receiving device includes: in the process of creating the subscription resource, the data receiving device creates a data loss notification event according to the data loss notification trigger parameter in the first request message, and includes a data loss notification trigger condition in the data loss notification event.
  • the data receiving device establishes a data loss notification trigger condition in the event notification rule (eventNotificationCreteria) attribute of the subscription resource according to the time series data loss notification trigger parameter.
  • eventNotificationCreteria event notification rule
  • Step S509 After the data receiving device successfully creates the time series resource, the data receiving device sends a third response message to the data source device.
  • Step S510 The data receiving device collects and stores the time series data, and performs loss detection and reporting on the time series data.
  • the timing resource generated by the data receiving device further includes a missing data detection parameter, and before determining the time series data, further determining whether the value in the missing data detection parameter is true, when the data detection parameter is lost.
  • the data receiving device detects whether there is missing time series data during data reception; if the value in the lost data detection parameter is not true, the lost data subscription event in the subscription resource returns a lost data detection error. Or feedback information such as lost data detection cannot be performed.
  • the method for performing the loss detection and reporting on the time series data by the data receiving device in this embodiment is the same as that in the fourth embodiment, and details are not described herein again.
  • Step S511 The data receiving device sends a data loss notification message to the target device.
  • the data receiving device sends a data loss notification message to the target device.
  • the specific process may include: the data receiving device sends a notification request message (Notify Request) to the target device, where the notification request message carries specific notification content, such as a missing data list (missingList) and/or Or when The amount of data lost before (currentMissingNr); the target device returns a notification response message to the data receiving device after receiving the notification message sent by the data receiving device.
  • FIG. 12 is a flowchart of a method for detecting time series data according to Embodiment 8 of the present invention.
  • the method is applied to an M2M data transmission system, and the main body of execution is a data source device, wherein the data source device refers to various devices capable of generating time series data.
  • the main steps of the method of this embodiment include:
  • Step S61 Generate time series data according to the data information of the data to be transmitted, wherein the time series data carries data information, and the data information includes time information and/or sequence number.
  • Step S62 Send the time series data to the data receiving device.
  • the time-series data sent to the data receiving device is used by the data receiving device to determine whether there is missing time-series data during the data receiving process according to the time information and/or the sequence number carried in the received time-series data; if there is a lost timing Data, the data information of the lost time series data is saved; the data receiving device further determines whether the preset data loss notification trigger condition is currently reached; if the data loss notification trigger condition is reached, the data loss notification information is sent to the target device.
  • FIG. 13 is a flowchart of a method for detecting time series data according to Embodiment 9 of the present invention. The method is applied to an M2M data transmission system, and the main steps include:
  • Step S71 Generate time series data according to data information of data to be transmitted, wherein the time series data carries data information, and the data information includes time information and/or sequence number.
  • Step S72 Send a first request message requesting the data receiving device to establish a timing resource to the data receiving device.
  • the first request message carries the following parameters: a maximum lost data amount, a current lost data amount, and a lost data list, and is used by the data receiving device to establish a maximum in the time series resource according to the maximum lost data amount, the current lost data amount, and the lost data list.
  • the maximum lost data amount attribute is used to record the maximum number of lost time series data
  • the current lost data amount attribute is used to record the number of currently lost time series data
  • the lost data list is used to record the time information and/or sequence of the lost time series data. Numbering.
  • Step S73 Receive a first response message sent by the data receiving device after the establishment of the time series resource is completed.
  • Step S74 Send a second request message requesting the data receiving device to establish a time series instance resource to the data receiving device.
  • Step S75 Receive a second response message that is sent by the data receiving device after the establishment of the sequence instance resource is completed.
  • the timing instance resource is a sub-resource of the timing resource; the timing resource and the timing instance resource are used to store the attribute information of the time series data.
  • Step S76 Send a third request message requesting the data receiving device to establish a subscription resource to the data receiving device.
  • the third request message carries a time series data loss notification trigger parameter, and is used by the data receiving device in the created subscription resource according to the time series data loss notification trigger parameter set missing data subscription event; the lost data subscription event includes the basis The data loss notification trigger condition for the timing data loss notification trigger parameter setting.
  • Step S77 Receive a third response message that is sent by the data receiving device after the subscription resource is established.
  • the embodiment of the present invention further provides the ninth embodiment, and the ninth embodiment is improved on the basis of the eighth embodiment.
  • the first request message sent to the data receiving device further carries the longest waiting time.
  • the data receiving device establishes a longest waiting time attribute in the timing resource according to the longest waiting time, wherein the longest waiting time attribute is used for the longest waiting for the time series data not received by the data receiving device identifier to be determined as the lost time series data time.
  • the embodiment of the present invention further provides a tenth embodiment.
  • the tenth embodiment is improved on the basis of the eighth embodiment.
  • the first request message sent to the data receiving device further carries a timing data loss notification trigger.
  • the parameter is used by the data receiving device to set a lost data subscription event in the subscription resource of the time series resource according to the time series data loss notification trigger parameter, and the data loss notification trigger condition is set according to the time series data loss notification trigger parameter setting.
  • the embodiment of the present invention further provides the eleventh embodiment, and the eleventh embodiment is improved on the basis of the ninth request, wherein the first request message sent to the data receiving device further carries the time series data loss in the embodiment.
  • the notification trigger parameter is used by the data receiving device to set a lost data subscription event in the subscription resource of the time series resource according to the time series data loss notification trigger parameter, and the lost data subscription event includes data loss according to the time series data loss notification trigger parameter setting. Lost notification trigger condition.
  • the third request message no longer carries the timing data loss notification trigger parameter.
  • FIG. 14 is a schematic structural diagram of a time series data detecting apparatus according to an embodiment of the present invention.
  • the apparatus is applied to a data transmission system.
  • the apparatus includes a first determining module 81, a storage module 82, and a second determining module. 83, where:
  • the first determining module 81 is configured to determine, according to the data information carried in the time series data from the data source device, whether there is missing time series data in the data receiving process, where the data information includes time information and/or a sequence number;
  • the storage module 82 is configured to save the data information of the lost time series data if there is missing time series data;
  • the second determining module 83 is configured to determine whether a preset data loss notification trigger condition is currently reached.
  • the notification message sending module is configured to send the data loss notification information to the target device if the data loss notification trigger condition is reached.
  • the first determining module 81 is further configured to:
  • time series data based on the data information carried by the time series data from the data source device, it is determined whether there is missing time series data during data reception.
  • the time series data detecting apparatus further includes: a timing resource establishing module, configured to determine, according to the data information carried in the time series data from the data source device, whether there is any missing time series data during the data receiving process, according to The data source device requests to establish a first request message of the timing resource to establish a timing resource;
  • the first request message carries the following parameters: a maximum lost data volume, a current lost data volume, and a lost data list; the timing resource includes a maximum lost data amount respectively established according to the maximum lost data amount, the current lost data volume, and the lost data list respectively. Attributes, current lost data volume attributes, and missing data list attributes;
  • the maximum lost data amount attribute is used to record the maximum number of lost time series data
  • the current lost data amount attribute is used to record the number of currently lost time series data
  • the missing data list is used for Record the time information and/or sequence number of the lost time series data.
  • the parameter carried in the first request message further includes: a maximum waiting time
  • the timing resource also includes a longest latency attribute established according to the longest waiting time, wherein the longest latency attribute is used to identify the maximum waiting time for the unreceived timing data to be determined as missing timing data.
  • the parameter carried in the first request message further includes: a time series data loss notification trigger parameter;
  • the timing resource further includes a subscription resource, and the subscription resource includes a lost data subscription event set according to the timing data loss notification trigger parameter setting;
  • the Lost Data Subscription event contains a data loss notification trigger condition based on the timing data loss notification trigger parameter setting.
  • the time series data detecting device further includes:
  • a subscription resource establishing module configured to establish a subscription resource by establishing a second request message of the subscription resource according to the request from the data source device;
  • the subscription resource is a sub-resource of the time-series resource, and the second request message carries a timing data loss notification trigger parameter;
  • the subscription resource includes a missing data subscription event set according to the time series data loss notification trigger parameter
  • the Lost Data Subscription event contains a data loss notification trigger condition based on the timing data loss notification trigger parameter setting.
  • the first determining module 81 is specifically configured to:
  • Whether or not there is missing time series data during data reception is determined according to the cycle time carried by the received periodic time series data or the continuity of the sequence number corresponding to the cycle time.
  • the first determining module 81 is specifically configured to:
  • the time-series data that has not been received after waiting for the preset duration is determined as the lost timing data.
  • the second determining module 83 is further configured to determine whether a lost data subscription event is set in the pre-established subscription resource.
  • the data loss notification triggering condition includes:
  • FIG. 15 is a schematic structural diagram of a time series data detecting apparatus according to Embodiment 2 of the present invention.
  • the apparatus is applied to a data transmission system.
  • the apparatus includes: a time series data generating module 91 and a first sending module 92, wherein :
  • the time series data generating module 91 is configured to generate time series data according to the data information of the data to be sent, wherein the time series data carries data information, where the data information includes time information and/or a sequence number;
  • the first sending module 92 is configured to send the time series data to the data receiving device, and the data receiving device determines, according to the time information and/or the sequence number carried in the received time series data, whether there is a missing timing in the data receiving process. Data; if there is missing time series data, the data information of the lost time series data is saved; the data receiving device further determines whether the preset data loss notification trigger condition is currently reached; if the data loss notification trigger condition is reached, the data is sent to the target device. Lost notification information.
  • the first sending module 92 is further configured to: before sending the time series data to the data receiving device, send a first request message requesting the data receiving device to establish a timing resource to the data receiving device;
  • the first request message carries the following parameters: a maximum amount of lost data, a current amount of lost data, and a missing data list; and a maximum value established by the data receiving device according to the maximum lost data amount, the current lost data amount, and the lost data list in the time series resource respectively.
  • the maximum lost data amount attribute is used to record the maximum number of lost time series data, currently lost
  • the lost data attribute is used to record the number of time series data that is currently lost
  • the lost data list is used to record the time information and/or sequence number of the lost time series data.
  • the parameter carried in the first request message further includes: a maximum waiting time, where the data receiving device establishes a longest waiting time attribute in the time series resource according to the longest waiting time, wherein the longest waiting time The attribute is used for the maximum waiting time when the time-series data not received by the data receiving device identification is determined to be lost timing data.
  • the parameter carried by the first request message further includes: a time series data loss notification trigger parameter, configured to: the data receiving device sets a lost data subscription event in the subscription resource of the time series resource according to the time series data loss notification trigger parameter, and is lost.
  • the data subscription event contains a data loss notification trigger condition based on the timing data loss notification trigger parameter setting.
  • the time series data detecting apparatus further includes: a second sending module, configured to send, to the data receiving device, a second request message for requesting the data receiving device to establish a subscription resource;
  • the second request message carries a timing data loss notification trigger parameter, and is used by the data receiving device in the created subscription resource according to the time-series data loss notification trigger parameter setting loss data subscription event; the lost data subscription event includes triggering according to the time series data loss notification The data loss notification trigger condition of the parameter setting.
  • FIG. 16 is a block diagram showing the structure of a time series data detecting apparatus according to an embodiment of the present invention.
  • the time series data detecting apparatus 1400 includes a communication interface 1401, a memory 1403, and a processor 1402, wherein the communication interface 1401, the processor 1402, the memory 1403 are connected to each other through a bus 1404; and the bus 1404 may be a peripheral component A standard component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus.
  • PCI peripheral component A standard component interconnect
  • EISA extended industry standard architecture
  • the bus can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in Figure 16, but it does not mean that there is only one bus or one type of bus.
  • the communication interface 1401 is for communicating with the transmitting end.
  • the memory 1403 is configured to store a program.
  • the program can include program code, the program code including computer operating instructions.
  • the memory 1403 may include a random access memory (RAM), and may also include a non-volatile memory such as at least one disk storage.
  • the processor 1402 executes the program stored in the memory 1403 to implement the method of the foregoing method embodiment of the present invention:
  • the data loss notification information is sent to the target device.
  • the processor 1402 may be a general-purpose processor, including a central processing unit (CPU), a network processor (NP Processor, etc.), or a digital signal processor (DSP), an application specific integrated circuit. (ASIC), Field Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware component.
  • CPU central processing unit
  • NP Processor network processor
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA Field Programmable Gate Array
  • the time series data detecting device of the embodiment determines whether there is missing data information time series data in the data receiving process according to the time information of the time series data that has been received, and reports the lost data to the target device when the data loss notification trigger condition is met.
  • the information of the time series data thereby realizing the detection and reporting of the lost time series data in the data transmission system.
  • the aforementioned program can be stored in a computer readable storage medium.
  • the program when executed, performs the steps including the foregoing method embodiments; and the foregoing storage medium includes various media that can store program codes, such as a ROM, a RAM, a magnetic disk, or an optical disk.

Abstract

本发明实施例涉及数据检测技术，尤其涉及一种时序数据检测方法及装置。一种时序数据检测方法，所述方法应用于数据传输系统中，包括：根据来自数据源设备的时序数据所携带的数据信息，确定在数据接收过程中是否有丢失的时序数据，其中所述数据信息包括时间信息和/或序列编号；若有丢失的时序数据，则保存所述丢失的时序数据的数据信息；确定当前是否达到预设的数据丢失通知触发条件；若达到所述数据丢失通知触发条件，则向目标设备发送数据丢失通知信息。本发明实施例的时序数据检测方法及装置，能够在数据传输系统中实现对丢失时序数据的检测和上报。

Description

时序数据检测方法及装置 技术领域
本发明实施例涉及数据检测技术，尤其涉及一种时序数据检测方法及装置。
背景技术
M2M(Machine to Machine，机器对机器)是终端与终端之间进行对话的算法模型，在M2M应用中存在一种比较特殊的数据类型—时序数据(或称为时间序列数据)，时序数据具有时间先后顺序、动态性、无限性以及不可预知性等特点。
现有技术中，采用oneM2M模型进行时序数据的存储传输，其中在oneM2M模型中，利用时序资源以及时序实例资源描述时序数据的数据属性。
上述oneM2M模型中，通过时序资源以及时序实例资源的属性描述实现了时序数据的接收存储，但在数据接收过程中，难以避免的会存在数据的丢失，在M2M模型中如何进行时序数据丢失检测和上报是亟待解决的一个问题。
发明内容
本发明实施例提供了一种时序数据检测方法、装置及设备，以在M2M数据传输系统中实现对丢失时序数据的检测和上报。
第一方面，本发明实施例提供了一种时序数据检测方法，所述方法应用于数据传输系统中，包括：
根据来自数据源设备的时序数据所携带的数据信息，确定在数据接收过程中是否有丢失的时序数据，其中所述数据信息包括时间信息和/或序列编号；
若有丢失的时序数据，则保存所述丢失的时序数据的数据信息；
确定当前是否达到预设的数据丢失通知触发条件；
若达到所述数据丢失通知触发条件，则向目标设备发送数据丢失通知信息。
可选的，所述根据来自数据源设备的时序数据所携带的数据信息，确定在数据接收过程中是否有丢失的时序数据之前，还包括：
确定预先建立的时序资源中缺失数据检测参数中的数值是否为真；
若为真，则根据来自数据源设备的时序数据所携带的数据信息，确定在数据接收过程中是否有丢失的时序数据。
可选的，所述根据来自数据源设备的时序数据所携带的数据信息，确定在数据接收过程中是否有丢失的时序数据之前，还包括：
根据来自数据源设备的请求建立时序资源的第一请求消息，建立时序资源；
其中，所述第一请求消息中携带以下参数：最大丢失数据量、当前丢失数据量以及丢失数据列表；所述时序资源中包括根据所述最大丢失数据量、所述当前丢失数据量以及所述丢失数据列表分别建立的最大丢失数据量属性、当前丢失数据量属性以及丢失数据列表属性；
所述最大丢失数据量属性用于记录丢失的时序数据的最大数目，所述当前丢失数据量属性用于记录当前丢失的时序数据的数目，所述丢失数据列表用于记录已丢失的时序数据的时间信息和/或序列编号。
可选的，所述第一请求消息携带的参数中还包括：最长等待时间；
所述时序资源中还包括根据所述最长等待时间建立的最长等待时间属性，其中，所述最长等待时间属性用于标识未接收到的时序数据被确定为丢失时序数据的最长等待时间。
可选的，所述第一请求消息携带的参数中还包括：时序数据丢失通知触发参数；
所述时序资源中还包括订阅资源，所述订阅资源中包括根据所述时序数据丢失通知触发参数设置的丢失数据订阅事件；
所述丢失数据订阅事件中包含根据所述时序数据丢失通知触发参数设置的所述数据丢失通知触发条件。
可选的，所述方法还包括：
根据来自所述数据源设备的请求建立订阅资源的第二请求消息，建 立订阅资源；
其中，所述订阅资源为所述时序资源的子资源，所述第二请求消息中携带时序数据丢失通知触发参数；
所述订阅资源中包括根据所述时序数据丢失通知触发参数设置的丢失数据订阅事件；
所述丢失数据订阅事件中包含根据所述时序数据丢失通知触发参数设置的所述数据丢失通知触发条件。
可选的，所述根据来自数据源设备的时序数据所携带的时间信息，确定在数据接收过程中是否有丢失的时序数据，包括：
接收来自于所述数据源设备的周期性时序数据；
根据接到的所述周期性时序数据携带的周期时间或者与所述周期时间对应的序列编号的连续性，确定在数据接收过程中是否有丢失的时序数据。
可选的，所述根据接到的所述周期性时序数据携带的周期时间或者与所述周期时间对应的序列编号的连续性，确定在数据接收过程中是否有丢失的时序数据，包括：
根据所述接到的所述周期性时序数据携带的周期时间或者与所述周期时间对应的序列编号的连续性，确定是否存在未接收到的时序数据；
若存在未接收到的时序数据，则在等待预设时长之后确定是否仍有未接收到的时序数据；
若仍有未接收到的时序数据，则将所述在等待预设时长之后仍未接收到的时序数据确定为已丢失的时序数据。
可选的，所述确定当前是否达到预设的数据丢失通知触发条件之前，还包括：
确定预先建立的订阅资源中是否设置有丢失数据订阅事件；
若有，则确定当前是否达到所述丢失数据订阅事件中预先设置的数据丢失通知触发条件。
可选的，所述数据丢失通知触发条件包括：
当前时间是否达到预设的丢失数据上报周期中所设定的上报时间；
和/或，
当前已丢失的时序数据的数量是否达到预设的上报数量。
第二方面，本发明实施例提供了一种时序数据检测方法，所述方法应用于数据传输系统中，包括：
根据待发送的数据的数据信息，生成时序数据，其中，所述时序数据携带所述数据信息，所述数据信息包括时间信息和/或序列编号；
将所述时序数据发送给数据接收设备，用于所述数据接收设备根据接收到的时序数据所携带的时间信息和/或序列编号，确定在数据接收过程中是否有丢失的时序数据；若有丢失的时序数据，则保存所述丢失的时序数据的数据信息；所述数据接收设备还确定当前是否达到预设的数据丢失通知触发条件；若达到所述数据丢失通知触发条件，则向目标设备发送数据丢失通知信息。
可选的，所述将所述时序数据发送给数据接收设备之前，还包括：
向所述数据接收设备发送请求所述数据接收设备建立时序资源的第一请求消息；
所述第一请求消息中携带以下参数：最大丢失数据量、当前丢失数据量以及丢失数据列表；用于所述数据接收设备根据所述最大丢失数据量、所述当前丢失数据量以及所述丢失数据列表在时序资源中分别建立的最大丢失数据量属性、当前丢失数据量属性以及丢失数据列表属性；
所述最大丢失数据量属性用于记录丢失的时序数据的最大数目，所述当前丢失数据量属性用于记录当前丢失的时序数据的数目，所述丢失数据列表用于记录已丢失的时序数据的时间信息和/或序列编号。
可选的，所述第一请求消息携带的参数中还包括：最长等待时间，用于所述数据接收设备根据所述最长等待时间，在所述时序资源中建立最长等待时间属性，其中，所述最长等待时间属性用于所述数据接收设备标识未接收到的时序数据被确定为丢失时序数据的最长等待时间。
可选的，所述第一请求消息携带的参数中还包括：时序数据丢失通知触发参数，用于所述数据接收设备根据所述时序数据丢失通知触发参数在时序资源的订阅资源中设置丢失数据订阅事件，所述丢失数据订阅事件中包含根据所述时序数据丢失通知触发参数设置的所述数据丢失通知触发条件。
可选的，所述方法还包括：
向所述数据接收设备发送用于请求所述数据接收设备建立订阅资源的第二请求消息；
所述第二请求消息中携带时序数据丢失通知触发参数，用于所述数据接收设备在创建的订阅资源中根据所述时序数据丢失通知触发参数设置的丢失数据订阅事件；所述丢失数据订阅事件中包含根据所述时序数据丢失通知触发参数设置的所述数据丢失通知触发条件。
第三方面，本发明实施例提供了一种时序数据检测装置，所述装置应用于数据传输系统中，包括：
第一确定模块，用于根据来自数据源设备的时序数据所携带的数据信息，确定在数据接收过程中是否有丢失的时序数据，其中所述数据信息包括时间信息和/或序列编号；
存储模块，用于若有丢失的时序数据，则保存所述丢失的时序数据的数据信息；
第二确定模块，用于确定当前是否达到预设的数据丢失通知触发条件；
通知消息发送模块，用于若达到所述数据丢失通知触发条件，则向目标设备发送数据丢失通知信息。
可选的，所述第一确定模块，还用于：
根据来自数据源设备的时序数据所携带的数据信息，确定在数据接收过程中是否有丢失的时序数据之前，确定预先建立的时序资源中缺失数据检测参数中的数值是否为真；
若为真，则根据来自数据源设备的时序数据所携带的数据信息，确定在数据接收过程中是否有丢失的时序数据。
可选的，所述装置还包括：时序资源建立模块，用于根据来自数据源设备的时序数据所携带的数据信息，确定在数据接收过程中是否有丢失的时序数据之前，根据来自数据源设备的请求建立时序资源的第一请求消息，建立时序资源；
其中，所述第一请求消息中携带以下参数：最大丢失数据量、当前丢失数据量以及丢失数据列表；所述时序资源中包括根据所述最大丢失 数据量、所述当前丢失数据量以及所述丢失数据列表分别建立的最大丢失数据量属性、当前丢失数据量属性以及丢失数据列表属性；
所述最大丢失数据量属性用于记录丢失的时序数据的最大数目，所述当前丢失数据量属性用于记录当前丢失的时序数据的数目，所述丢失数据列表用于记录已丢失的时序数据的时间信息和/或序列编号。
可选的，所述第一请求消息携带的参数中还包括：最长等待时间；
所述时序资源中还包括根据所述最长等待时间建立的最长等待时间属性，其中，所述最长等待时间属性用于标识未接收到的时序数据被确定为丢失时序数据的最长等待时间。
可选的，所述第一请求消息携带的参数中还包括：时序数据丢失通知触发参数；
所述时序资源中还包括订阅资源，所述订阅资源中包括根据所述时序数据丢失通知触发参数设置的丢失数据订阅事件；
所述丢失数据订阅事件中包含根据所述时序数据丢失通知触发参数设置的所述数据丢失通知触发条件。
可选的，所述装置还包括：
订阅资源建立模块，用于根据来自所述数据源设备的请求建立订阅资源的第二请求消息，建立订阅资源；
其中，所述订阅资源为所述时序资源的子资源，所述第二请求消息中携带时序数据丢失通知触发参数；
所述订阅资源中包括根据所述时序数据丢失通知触发参数设置的丢失数据订阅事件；
所述丢失数据订阅事件中包含根据所述时序数据丢失通知触发参数设置的所述数据丢失通知触发条件。
可选的，所述第一确定模块，具体用于：
接收来自于所述数据源设备的周期性时序数据；
根据接到的所述周期性时序数据携带的周期时间或者与所述周期时间对应的序列编号的连续性，确定在数据接收过程中是否有丢失的时序数据。
可选的，所述第一确定模块，具体用于：
根据所述接到的所述周期性时序数据携带的周期时间或者与所述周期时间对应的序列编号的连续性，确定是否存在未接收到的时序数据；
若存在未接收到的时序数据，则在等待预设时长之后确定是否仍有未接收到的时序数据；
若仍有未接收到的时序数据，则将所述在等待预设时长之后仍未接收到的时序数据确定为已丢失的时序数据。
可选的，所述第二确定模块，还用于确定预先建立的订阅资源中是否设置有丢失数据订阅事件；
若有，则确定当前是否达到所述丢失数据订阅事件中预先设置的数据丢失通知触发条件。
可选的，所述数据丢失通知触发条件包括：
当前时间是否达到预设的丢失数据上报周期中所设定的上报时间；
和/或，
当前已丢失的时序数据的数量是否达到预设的上报数量。
第四方面，本发明实施例提供了一种时序数据检测装置，所述装置应用于数据传输系统中，包括：
时序数据生成模块，用于根据待发送的数据的数据信息，生成时序数据，其中，所述时序数据携带所述数据信息，所述数据信息包括时间信息和/或序列编号；
第一发送模块，用于将所述时序数据发送给数据接收设备，用于所述数据接收设备根据接收到的时序数据所携带的时间信息和/或序列编号，确定在数据接收过程中是否有丢失的时序数据；若有丢失的时序数据，则保存所述丢失的时序数据的数据信息；所述数据接收设备还确定当前是否达到预设的数据丢失通知触发条件；若达到所述数据丢失通知触发条件，则向目标设备发送数据丢失通知信息。
可选的，所述发送模块，还用于将所述时序数据发送给数据接收设备之前，向所述数据接收设备发送请求所述数据接收设备建立时序资源的第一请求消息；
所述第一请求消息中携带以下参数：最大丢失数据量、当前丢失数据量以及丢失数据列表；用于所述数据接收设备根据所述最大丢失数据 量、所述当前丢失数据量以及所述丢失数据列表在时序资源中分别建立的最大丢失数据量属性、当前丢失数据量属性以及丢失数据列表属性；
所述最大丢失数据量属性用于记录丢失的时序数据的最大数目，所述当前丢失数据量属性用于记录当前丢失的时序数据的数目，所述丢失数据列表用于记录已丢失的时序数据的时间信息和/或序列编号。
可选的，所述第一请求消息携带的参数中还包括：最长等待时间，用于所述数据接收设备根据所述最长等待时间，在所述时序资源中建立最长等待时间属性，其中，所述最长等待时间属性用于所述数据接收设备标识未接收到的时序数据被确定为丢失时序数据的最长等待时间。
可选的，所述第一请求消息携带的参数中还包括：时序数据丢失通知触发参数，用于所述数据接收设备根据所述时序数据丢失通知触发参数在时序资源的订阅资源中设置丢失数据订阅事件，所述丢失数据订阅事件中包含根据所述时序数据丢失通知触发参数设置的所述数据丢失通知触发条件。
可选的，所述装置还包括：第二发送模块，用于向所述数据接收设备发送用于请求所述数据接收设备建立订阅资源的第二请求消息；
所述第二请求消息中携带时序数据丢失通知触发参数，用于所述数据接收设备在创建的订阅资源中根据所述时序数据丢失通知触发参数设置的丢失数据订阅事件；所述丢失数据订阅事件中包含根据所述时序数据丢失通知触发参数设置的所述数据丢失通知触发条件。
本发明实施例的时序数据检测方法，数据接收设备根据已经接收到的时序数据的时间信息，确定在数据接收过程中是否有丢失的数据信息时序数据，并在满足数据丢失通知触发条件时向目标设备上报丢失的时序数据的信息，从而实现了在数据传输系统中实现对丢失时序数据的检测和上报。
附图说明
为了更清楚地说明本发明实施例或现有技术中的技术方案，下面将对实施例或现有技术描述中所需要使用的附图作一简单地介绍，显而易见地，下面描述中的附图是本发明的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动性的前提下，还可以根据这些附图获得 其他的附图。
图1示出了时序资源中特有属性的表示示意图；
图2示出了时序实例资源中特有属性的表示示意图；
图3示出了本发明实施例一时序数据检测方法的流程图；
图4示出了本发明实施例二时序数据检测方法的流程图；
图5示出了时序资源中增加三个特有属性后的表示示意图；
图6示出了本发明实施例三时序数据检测方法的流程图；
图7示出了本发明实施例四时序数据检测方法的流程图；
图8示出了时序资源中增加四个特有属性后的第一表示示意图；
图9示出了本发明实施例五时序数据检测方法的流程图；
图10示出了本发明实施例六时序数据检测方法的流程图；
图11示出了本发明实施例七时序数据检测方法的流程图；
图12示出了本发明实施例八时序数据检测方法的流程图；
图13示出了本发明实施例九时序数据检测方法的流程图；
图14示出了本发明实施例一时序数据检测装置的结构示意图；
图15示出了本发明实施例二时序数据检测装置的结构示意图；
图16示出了本发明实施例时序数据检测设备的结构示意图。
具体实施方式
为使本发明实施例的目的、技术方案和优点更加清楚，下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例是本发明一部分实施例，而不是全部的实施例。基于本发明中的实施例，本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例，都属于本发明保护的范围。
本发明实施例附图及表格中的：
“1”表示属性或子资源存在且唯一；
“0..1”表示属性或子资源可以不存在，如果存在只能唯一；
“0..n”表示属性或子资源可以不存在，如果存在，可以有多个；
“1..n”表示子资源至少有一个存在；
“L”表示属性的属性值是一个多个数据组成的列表。
M2M应用中涉及的时序数据根据触发类型不同，可以分为周期性时 序数据和事件触发的时序数据。
例如，在某车管家应用中，设置有车辆行驶轨迹回放功能，该功能要求车辆以30秒为周期定期向数据存储中心(如云端)发送一次自己的位置信息，其中在发送的位置信息中可以包括：时间、经度、纬度、速度等信息。在该实例中，时序数据由车辆终端定期发送，每次发送的数据是变化的，而且在时间与空间允许的情况下，车辆终端可以一直向数据存储中心发送位置信息。
又例如，在智能家居中，当烟雾报警器检测到空气中的烟雾浓度达到设定阈值时，发出报警并将该事件信息发送给M2M的数据存储中心，具体上报的事件信息可以包括事件发生的时间、触发的传感器编号及位置等信息。与上一实例中的车辆位置信息定期发送不同，本实例中烟雾报警器发送的事件信息由特定事件触发产生，该类型时序数据是随机不可预知的，因此产生的时序数据也是不可预知的。
从上述两个例子可以看出，带有时间信息的时序数据不同于传统数据，时间信息是时序数据区别于其它传统数据的显著特点之一，时间信息描述了数据流中数据和事件之间的一种多对一或一对一的映射关系，它不仅反映了数据元素之间的先后次序关系以及数据元素在时间域内的分布情况，而且在描述时序数据操作时具有重要的语义信息。时序数据不仅反映出某一刻对象的状态，还反映了对象在过去的一个整体情况，甚至可以通过各种手段、方法去预测数据对象未来的发展趋势。
oneM2M标准是M2M通信和物联网(Thing of Internet)通信相结合的标准。在现有的oneM2M标准中，采用时序(<timeSeries>)和时序实例(<timeSeriesInstance>)两种资源来描述数据，其中时序实例资源是时序资源的子资源，通过这两种资源可以实现时序数据的存储。
oneM2M标准中包含一般属性(common attribute)、普遍属性(universal attribute)和特有属性(specified attribute)，其中特有属性只存在于时序资源和时序实例资源中。
图1示出了时序资源中特有属性的表示示意图。
图2示出了时序实例资源中特有属性的表示示意图。
如图1所示，时序资源中还包含订阅(<subcription>)资源，其中订 阅资源为时序资源的子资源。在订阅资源中包含事件通知规则(eventNotificationCreteria)以及通知内容类型(notificationContentType)等属性，数据源设备或其它需要获取相关通知消息的属性可以通过订阅资源订阅相关的通知信息，具体的可以在事件通知规则(eventNotificationCreteria)中设置通知事件的触发条件。
图1和图2所示的oneM2M资源模型中，时序实例资源是时序资源的子资源，数据对象存放在时序实例资源的内容(content)属性中，数据生成时间(dataGenerationTime)属性中保存了内容属性中保存的数据对象的产生时间。
图1和图2所示的oneM2M标准中实现了时序数据的收集和保存，但如何检测和上报丢失的时序数据仍是亟需解决的技术问题。
图3示出了本发明实施例一时序数据检测方法的流程图，如图3所示的时序数据检测方法应用于M2M数据传输系统中，用于实现M2M数据传输系统中时序数据的丢失检测和上报。本实施例时序数据检测方法的执行主体为数据接收设备，其中数据接收设备的实现主体可以为AE(application entity，应用实体)及CSE(common services entity，公共服务实体)等，具体的例如可以为如存储云端，本实施例方法的处理步骤如图3所示包括：
步骤S11：根据来自数据源设备的时序数据所携带的时间信息和/或序列编号，确定在数据接收过程中是否有丢失的时序数据。
本发明实施例中，数据源设备将生成的时序数据发送给数据接收设备，数据接收设备确定预先生成的时序资源中丢失数据检测(missingDataDetect)参数中的数值是否为真，如该参数为ture或为1时，确定丢失数据检测参数中的数值为真。
当丢失数据检测参数中的数值为真时，数据接收设备可以根据时序数据的数据信息，确定在数据接收过程中是否有丢失的数据，例如，数据源设备发送给数据接收设备的时序数据为周期性时序数据，数据接收设备可以根据时序数据的周期特点确定是否有丢失的数据，例如，数据接收设备接收到的周期性时序数据包括t1、t2、t4、t5，其中t1、t2、t4、t5中的1、2、4及5可以分别表示时序数据的生成时间、发送时间或者与 相应时间对应的编号，相邻时间或相邻编号之间的时间间隔为一个周期，数据接收设备根据接收到的时序数据中的编号或者时间确定是否有丢失的数据，该示例中缺少t3，数据接收设备可以确定在数据接收过程中丢失了t3。
对于事件触发型时序数据，数据源设备可以对连续产生的多个事件性时序数据按照触发时间编号，数据接收设备根据接收到的事件性时序数据的编号可以确定是否有丢失的时序数据。
步骤S12：若有丢失的时序数据，则保存丢失的时序数据的数据信息。
数据接收设备确定在数据接收过程中有丢失的数据时，保存丢失的时序数据的数据信息，如丢失的时序数据产生的时间信息、序列号信息等。具体的，数据接收设备可以根据接收到的时序数据的时间信息确定丢失的时序数据的数据信息。
步骤S13：确定当前是否达到预设的数据丢失通知触发条件。
数据接收设备保存了丢失的时序数据的时间信息和/或序列编号后，进一步确定预先建立的订阅资源中是否设置有丢失数据订阅事件；若有，则确定当前是否达到所述丢失数据订阅事件中预先设置的数据丢失通知触发条件。
步骤S14：若达到数据丢失通知触发条件，则向目标设备发送数据丢失通知信息。
本发明实施例的时序数据检测方法基于M2M数据传输标准执行，在该方法中数据接收设备根据已经接收到的时序数据的时间信息，确定在数据接收过程中是否有丢失的数据信息时序数据，并在满足数据丢失通知触发条件时向目标设备上报丢失的时序数据的信息，从而实现了在M2M数据传输系统中实现对丢失时序数据的检测和上报。
图4示出了本发明实施例二时序数据检测方法的流程图，该方法应用于M2M数据传输系统中，执行的主体为数据接收设备，如图4所示，该方法的具体执行步骤包括：
步骤S21：根据来自数据源设备的请求建立时序资源的第一请求消息，建立时序资源。
数据接收设备接收到的第一请求消息中携带以下参数：最大丢失数据量、当前丢失数据量以及丢失数据列表。
数据接收设备根据第一请求消息中的最大丢失数据量、当前丢失数据量以及丢失数据列表，在时序资源中分别建立最大丢失数据量属性、当前丢失数据量属性以及丢失数据列表属性。
图5示出了时序资源中增加三个特有属性后的表示示意图。图5所示的时序资源在图1所示的时序资源基础上增加了最大丢失数据量属性(maxMissingNr)、当前丢失数据量(currentMissingNr)属性以及丢失数据列表(missingList)属性。
表1示出了时序资源中增加的最大丢失数据量属性、当前丢失数据量属性以及丢失数据列表属性的属性信息。
表1 时序资源中新增加的三个属性的属性信息
Figure PCTCN2016112486-appb-000001
如图5和表1所示，最大丢失数据量(maxMissingNr)属性用于记录丢失的时序数据的最大数目(一般为预设的固定值)，当前丢失数据量(currentMissingNr)属性用于记录当前丢失的时序数据的数目，丢失数据列表missingList)用于记录已丢失的时序数据的数据信息，其中，在当前丢失数据量中的数值超过最大丢失数据量中设置的数值时，数据接收设备将最早存入的至少一个时序数据的数据信息从丢失数据列表中删除，由此可以在该丢失数据列表中继续插入新检测到的丢失时序数据的数据信息。
步骤S22：根据来自数据源设备的请求建立时序实例资源的第二请求消息，建立时序实例资源。
其中，建立的时序实例资源如图2所示，时序实例资源为时序资源的子资源。
步骤S23：根据来自数据源设备的请求建立订阅资源的第三请求消息，建立订阅资源。
本实施例中数据接收设备接收到的第三请求消息中携带时序数据丢失通知触发参数；所述订阅资源中包括根据所述时序数据丢失通知触发参数设置的丢失数据订阅事件；所述丢失数据订阅事件中包含根据所述时序数据丢失通知触发参数设置的所述数据丢失通知触发条件。
数据源设备通过请求数据接收设备建立订阅资源，并请求数据接收设备在订阅资源中创建丢失数据订阅事件，丢失数据订阅事件中包含数据丢失通知触发条件，由此可以使数据接收设备对丢失的时序数据进行检测，并在满足条件时触发数据接收设备向目标设备发送丢失的时序数据的相关信息。
本发明实施例中，目标设备可以为数据源设备，也可以为需要获取时序数据丢失信息的其它设备。
本实施例中，数据接收设备根据接收到的时序数据丢失通知触发参数设置的数据丢失通知触发条件包括：当前时间是否达到预设的丢失数据上报周期中所设定的上报时间；和/或，当前已丢失的时序数据的数量是否达到预设的上报数量。
如表2示出了第三请求消息中携带时序数据丢失通知触发参数(timeSeriesCriteria，时间序列标准)的具体定义。
表2 时序数据丢失通知触发参数定义表
Figure PCTCN2016112486-appb-000002
Figure PCTCN2016112486-appb-000003
本发明实施例中，数据接收设备根据时序数据丢失通知触发参数在订阅资源的事件通知规则(eventNotificationCreteria)属性中建立数据丢失通知触发条件。
步骤S24：确定预先建立的时序资源中缺失数据检测参数中的数值是否为真；若为真，执行步骤S25；否则，订阅资源中的丢失数据订阅事件返回丢失数据检测错误或无法进行丢失数据检测等反馈信息。
本发明实施例中，在数据接收设备生成的时序资源中还包括丢失数据检测(missingDataDetect)参数，当丢失数据检测参数中的数值为ture或为1时，确定丢失数据检测参数中的数值为真。当丢失数据检测参数为真时，数据接收设备检测在数据接收过程中是否有丢失的时序数据。
步骤S25：根据来自数据源设备的时序数据所携带的时间信息和/或序列编号，确定在数据接收过程中是否有丢失的时序数据。
步骤S26：若有丢失的时序数据，则保存丢失的时序数据的数据信息。
步骤S27：订阅资源中设置有数据丢失通知触发条件时，确定当前是否达到预设的数据丢失通知触发条件。
步骤S28：若达到数据丢失通知触发条件，则向目标设备发送数据丢失通知信息。
例如，当前时序数据丢失的个数达到数据丢失通知触发条件中设置的个数时，向数据接收设备发送数据丢失通知信息，其中，发送的通知信息中可以仅包括数据丢失提示信息，也可以包含丢失的时序数据的具体信息。
本发明实施例的时序数据检测方法在M2M实现了丢失数据的检测和上报。
图6示出了本发明实施例三时序数据检测方法的流程图。图6所示的时序数据检测方法为图4所示的时序数据检测方法的一种具体示例，该方法的主要处理步骤包括：
步骤S201：数据源设备向数据接收设备发送请求在数据接收设备创建时序资源的第一请求消息，其中在第一请求消息中携带以下参数：最大丢失数据量(maxMissingNr)、当前丢失数据量(currentMissingNr)以及丢失数据列表(missingList)。
步骤S202：数据接收设备根据接收到的第一请求消息创建时序资源，其中创建的时序资源中新增加的属性如表1所示包括最大丢失数据量(maxMissingNr)属性、当前丢失数据量(currentMissingNr)属性以及丢失数据列表(missingList)属性。
步骤S203：数据接收设备创建时序资源成功后，向数据源设备发送第一响应消息。
步骤S204：数据源设备向数据接收设备发送请求在数据接收设备创建时序实例资源的第二请求消息。
步骤S205：数据接收设备根据接收到的第二请求消息创建时序实例资源，其中时序实例资源为步骤S202中创建的时序资源的子资源。
数据源设备可以请求数据接收设备创建多个时序实例资源，其中创建的多个时序实例资源均为时序资源的子资源。
步骤S206：数据接收设备创建时序实例资源成功后，向数据源设备发送第二响应消息。
步骤S207：数据源设备向数据接收设备发送请求在数据接收设备创 建订阅资源的第三请求消息，其中在第三请求消息中携带时序数据丢失通知触发参数(即timeSeriesCriteria，时间序列标准)，时序数据丢失通知触发参数的定义规则如表2所示。
根据表2中所示的时序数据丢失通知触发参数的定义，当时序数据丢失达到指定数目和/或到达指定时长进行通知，可能情况如下：
例如，timeSeriesCriteria中的数目参数设置为4，当数据接收设备检测到丢失的时序数据数目达到4个时，向目标设备发送数据丢失通知消息。
例如，timeSeriesCriteria中的监测周期设置为时长为10min，则数据接收设备可以根据检测到的时序数据状况每隔10分钟向目标设备发送一次数据丢失通知消息。
又例如，timeSeriesCriteria中的数目参数设置为4且监测周期的时长设置为10min，则数据接收设备以10分钟为一个监测周期，且在当前监测周期内丢失的时序数据的数目达到4个时，向目标设备发送数据丢失通知消息，否则数据接收设备进入下一个监测周期内重新进行丢失时序数据的数目统计。
又例如，timeSeriesCriteria中参数设置为：数目参数设置为4或监测周期设置为10min，则丢失的时序数据数目达到4个或者当前监测的时间达到10分钟时，只要满足其中一个条件即触发向目标设备发送数据丢失通知消息的操作。
步骤S208：数据接收设备根据第三请求消息创建订阅资源。
具体的，数据接收设备在创建订阅资源的过程中包括：数据接收设备根据第三请求消息中携带的timeSeriesCriteria创建数据丢失通知事件，在数据丢失通知事件中包含数据丢失通知触发条件。
本发明实施例中，数据接收设备根据时序数据丢失通知触发参数在订阅资源的事件通知规则(eventNotificationCreteria)属性中建立数据丢失通知触发条件。
步骤S209：数据接收设备创建时序资源成功后，向数据源设备发送第三响应消息。
步骤S210：数据接收设备对时序数据进行收集和存储，并对时序数 据进行丢失检测和上报。
本实施例中，数据接收设备生成的时序资源中还包括丢失数据检测(missingDataDetect)参数，在对时序数据进行检测之前，还进一步确定丢失数据检测参数中的数值是否为真，当丢失数据检测参数中的数值为ture或为1时，确定丢失数据检测参数中的数值为真。当丢失数据检测参数为真时，数据接收设备检测在数据接收过程中是否有丢失的时序数据；若丢失数据检测参数中的数值不为真，订阅资源中的丢失数据订阅事件返回丢失数据检测错误或无法进行丢失数据检测等反馈信息。
数据接收设备对丢失的时序数据进行上报包括：
数据接收设备确定当前状况符合订阅资源中设置的数据丢失通知条件时，向目标设备发送数据丢失通知消息(Notify Request)，具体的，数据接收设备可以根据订阅资源中的通知内容类型(notificationContentType)确定在数据丢失通知消息中携带的内容，例如可以携带丢失数据列表(missingList)和/或当前丢失数据量(currentMissingNr)。
数据接收设备在时序数据丢失检测过程中，每当检测到一个时序数据丢失，便会将这个丢失的时序数据的数据生成时间(dataGenerationTime)和/或序列编号(sequenceNr)插入到丢失数据列表(missingList)中，且当前丢失数据量(currenMissingNr)的值加一。在当前丢失数据量(currenMissingNr)的数值达到最大丢失数量(max Missing Nr)中设置的数值时，数据接收设备将丢失数据列表(missingList)中最早的至少一个数据生成时间(dataGenerationTime)和/或序列编号(sequenceNr)删除，以用于插入新检测到的丢失时序数据的数据生成时间(dataGenerationTime)和/或序列编号(sequenceNr)。
例如，timeSeriesCriteria中的数目参数设置为4，当数据接收设备检测到丢失的时序数据数目达到4个时(如，丢失的时序数据包括t1,t5,t10,t11)，数据接收设备向目标设备发送数据丢失通知消息，具体的数据接收设备可以依据通知内容类型(notificationContentType)中的设置，仅向目标设备发送数据丢失的通知消息，或者在数据丢失通知消息中携带丢失数据列表(missingList)和/或当前丢失数据量(currentMissingNr)。
又例如，timeSeriesCriteria中的监测周期设置为时长为10min，具体实施时数据接收设备可以无论是否检测到丢失时序数据均每隔10分钟向目标设备发送一次数据丢失通知消息，或者，数据接收设备确定当前监测周期(10分钟)内是否检测到丢失时序数据，若检测到则在当前周期结束时向目标设备上报数据丢失通知消息并进入下一个周期的丢失数据检测，若在当前周期内未检测到丢失时序数据则直接进入下一个周期进行丢失时序数据检测。
进一步例如，timeSeriesCriteria中的数目参数设置为4且监测周期的时长设置为10min，则数据接收设备检测在当前监测周期(10分钟内)丢失的时序数据数目是否达到4个，若达到则向目标设备发送数据丢失通知消息，否则不发送。
又例如，timeSeriesCriteria中的参数设置为：数目参数设置为4或监测周期设置为10min，则数据接收设备确定当前检测到的丢失时序数据是否达到4个或是否达到监测周期设定的上报时间(10分钟)，只要满足其中一个条件则向目标设备发送数据丢失通知消息。
步骤S211：数据接收设备向目标设备发送数据丢失通知消息。
数据接收设备向目标设备发送数据丢失通知消息具体过程可以包括：数据接收设备向目标设备发送通知请求消息(Notify Request)，通知请求消息中携带具体的通知内容，如丢失数据列表(missingList)和/或当前丢失数据量(currentMissingNr)；目标设备接收到数据接收设备发送的通知消息后向数据接收设备返回通知响应消息。
图7示出了本发明实施例四时序数据检测方法的流程图，该方法应用于M2M数据传输系统中，执行的主体为数据接收设备，如存储云端，本实施例方法在图1所示的时序资源中增加了最大丢失数据量、当前丢失数据量、丢失数据列表以及最长等待时间四个属性，并且在订阅资源的事件通知规则属性中设置了数据丢失通知触发条件，使得数据接收设备在检测时序数据的丢失状况满足数据丢失通知触发条件时，向目标设备发送数据丢失通知消息，如图7所示，该方法的具体执行步骤包括：
步骤S31：根据来自数据源设备的请求建立时序资源的第一请求消息，建立时序资源。
数据接收设备接收到的第一请求消息中携带以下参数：最大丢失数据量、当前丢失数据量、丢失数据列表以及最长等待时间。
数据接收设备根据第一请求消息中的最大丢失数据量、当前丢失数据量、丢失数据列表以及最长等待时间，分别建立最大丢失数据量属性、当前丢失数据量属性、丢失数据列表属性以及最长等待时间属性。
图8示出了时序资源中增加四个特有属性后的第一表示示意图。
表3示出了时序资源中增加的最大丢失数据量属性、当前丢失数据量属性以及丢失数据列表属性的属性信息。
表3 时序资源中新增加的四个属性的属性信息
Figure PCTCN2016112486-appb-000004
表3中最大丢失数据量属性、当前丢失数据量属性、丢失数据列表属性与实施例二中的含义相同，不再赘述，新增加的最长等待时间属性，用于标识未接收到的时序数据被确定为丢失时序数据的最长等待时间。
步骤S32：根据来自数据源设备的请求建立时序实例资源的第二请求消息，建立时序实例资源。
其中，建立的时序实例资源如图2所示，时序实例资源为时序资源的子资源。
步骤S33：根据来自数据源设备的请求建立订阅资源的第三请求消 息，建立订阅资源。
本实施例中数据接收设备接收到的第三请求消息中携带时序数据丢失通知触发参数；所述订阅资源中包括根据所述时序数据丢失通知触发参数设置的丢失数据订阅事件；所述丢失数据订阅事件中包含根据所述时序数据丢失通知触发参数设置的所述数据丢失通知触发条件。
数据源设备通过请求数据接收设备建立订阅资源，并请求数据接收设备在订阅资源中创建丢失数据订阅事件，丢失数据订阅事件中包含数据丢失通知触发条件，由此可以使数据接收设备对丢失的时序数据进行检测，并在满足条件时触发数据接收设备向目标设备发送丢失的时序数据的相关信息。
本实施例中数据接收设备接收到的第三请求消息中携带时序数据丢失通知触发参数；订阅资源中包括根据时序数据丢失通知触发参数设置的数据丢失通知触发条件。
本实施例中设置的数据丢失通知触发参数与实施例二中的表2内容相同，不再赘述。
步骤S34：确定预先建立的时序资源中缺失数据检测参数中的数值是否为真；若为真，执行步骤S35；否则，订阅资源中的丢失数据订阅事件返回丢失数据检测错误或无法进行丢失数据检测等反馈信息。
本发明实施例中，在数据接收设备生成的时序资源中还包括丢失数据检测(missingDataDetect)参数，当丢失数据检测参数中的数值为ture或为1时，确定丢失数据检测参数中的数值为真。当丢失数据检测参数为真时，数据接收设备检测在数据接收过程中是否有丢失的时序数据。
步骤S35：根据来自数据源设备的时序数据所携带的时间信息和/或序列编号，确定在数据接收过程中是否有丢失的时序数据。
步骤S36：若存在未接收到的时序数据，则在等待预设时长之后确定是否仍有未接收到的时序数据。
步骤S37：若仍有未接收到的时序数据，则将在等待预设时长之后仍未接收到的时序数据确定为已丢失的时序数据。
本实施例S36及S37中的预设时长的值与表3中最长等待时间(maxDetectingTime)中的值相同。
步骤S38：订阅资源中设置有数据丢失通知触发条件时，确定当前是否达到订阅资源中的数据丢失通知触发条件。
步骤S39：若达到数据丢失通知触发条件，则向目标设备发送数据丢失通知信息。
考虑到数据接收过程中，会存在由于路由问题延迟接收到的时序数据，为了避免误判情况的发生，本发明实施例中设置最长等待时间属性，当数据接收设备确定有未接收到的时序数据时，等待预设时长，并在预设时长后确定是否接收到该时序数据，若仍未接收到，则确定该时序数据为丢失时序数据。本发明实施例的时序数据检测方法可以提高数据丢失性检测和上报的准确性。
图9示出了本发明实施例五时序数据检测方法的流程图。图9所示的时序数据检测方法为图7所示的时序数据检测方法的一种具体示例，该方法的主要处理步骤包括：
步骤S301：数据源设备向数据接收设备发送请求在数据接收设备创建时序资源的第一请求消息，其中在第一请求消息中携带参数最大丢失数据量(maxMissingNr)、当前丢失数据量(currentMissingNr)、丢失数据列表(missingList)以及最长等待时间(maxDetectingTime)。
步骤S302：数据接收设备根据接收到的第一请求消息创建时序资源，其中创建的时序资源中新增加的属性如表3所示包括最大丢失数据量(maxMissingNr)属性、当前丢失数据量(currentMissingNr)属性、丢失数据列表(missingList)属性以及最长等待时间(maxDetectingTime)属性。
步骤S303：数据接收设备创建时序资源成功后，向数据源设备发送第一响应消息。
步骤S304：数据源设备向数据接收设备发送请求在数据接收设备创建时序实例资源的第二请求消息。
步骤S305：数据接收设备根据接收到的第二请求消息创建时序实例资源，其中时序实例资源为步骤S302中创建的时序资源的子资源。
数据源设备可以请求数据接收设备创建多个时序实例资源，其中创建的多个时序实例资源均为时序资源的子资源。
步骤S306：数据接收设备创建时序实例资源成功后，向数据源设备 发送第二响应消息。
步骤S307：数据源设备向数据接收设备发送请求在数据接收设备创建订阅资源的第三请求消息，其中在第三请求消息中携带时序数据丢失通知触发参数(即timeSeriesCriteria，时间序列标准)，时序数据丢失通知触发参数的定义规则如表2所示。
根据表2中所示的时序数据丢失通知触发参数的定义，当时序数据丢失达到指定数目和/或到达指定时长进行通知，可能情况如下：
例如，Time Series Criteria中的数目参数设置为4，当数据接收设备检测到丢失的时序数据数目达到4个时，向目标设备发送数据丢失通知消息。
例如，timeSeriesCriteria中的监测周期设置为时长为10min，则数据接收每隔10分钟向目标设备发送一次数据丢失通知消息。
又例如，timeSeriesCriteria中的数目参数设置为4且监测周期的时长设置为10min，则数据接收设备以10分钟为一个监测周期，且在当前监测周期内丢失的时序数据的数目达到4个时，向目标设备发送数据丢失通知消息，否则数据接收设备进入下一个监测周期内重新进行丢失时序数据的数目统计。
又例如，timeSeriesCriteria中参数设置为：数目参数设置为4或监测周期设置为10min，则丢失的时序数据数据达到4个或者当前监测的时间达到10分钟时，只要满足其中一个条件即触发向目标设备发送数据丢失通知消息的操作。
步骤S308：数据接收设备根据第三请求消息创建订阅资源。
具体的，数据接收设备在创建订阅资源的过程中包括：数据接收设备根据第三请求消息中携带的timeSeriesCriteria创建数据丢失通知事件，在数据丢失通知事件中包含数据丢失通知触发条件。
本发明实施例中，数据接收设备根据时序数据丢失通知触发参数在订阅资源的事件通知规则(eventNotificationCreteria)属性中建立数据丢失通知触发条件。
步骤S309：数据接收设备创建时序资源成功后，向数据源设备发送第三响应消息。
步骤S310：数据接收设备对时序数据进行收集和存储，并对时序数据进行丢失检测和上报。
本实施例中，数据接收设备生成的时序资源中还包括丢失数据检测(missingDataDetect)参数，在对时序数据进行检测之前，还进一步确定丢失数据检测参数中的数值是否为真，当丢失数据检测参数中的数值为ture或为1时，确定丢失数据检测参数中的数值为真。当丢失数据检测参数为真时，数据接收设备检测在数据接收过程中是否有丢失的时序数据；若丢失数据检测参数中的数值不为真，订阅资源中的丢失数据订阅事件返回丢失数据检测错误或无法进行丢失数据检测等反馈信息。
本发明实施例中，数据接收设备基于时序资源中的最长等待时间(maxDetectingTime)、最大丢失数据量(maxMissingNr)、当前丢失数据量(currentMissingNr)以及丢失数据列表(missingList)参数对时序数据进行丢失检测和上报。
具体的，数据接收设备对时序数据进行丢失检测包括：数据接收设备根据来自数据源设备的时序数据所携带的时间信息，确定在数据接收过程中是否有丢失的时序数据；若存在未接收到的时序数据，则在等待预设时长之后确定是否仍有未接收到的时序数据；若仍有未接收到的时序数据，则将在等待预设时长之后仍未接收到的时序数据确定为已丢失的时序数据。
数据接收设备对时序数据进行上报包括：数据接收设备确定当前状况符合订阅资源中设置的数据丢失通知条件时，向目标设备发送数据丢失通知消息(Notify Request)，具体的，数据接收设备可以根据订阅资源中的通知内容类型(notificationContentType)确定在数据丢失通知消息中携带的内容，例如可以携带丢失数据列表(missingList)和/或当前丢失数据量(currentMissingNr)。
数据接收设备在时序数据丢失检测过程中，每当检测到一个时序数据丢失，便会将这个丢失的时序数据的数据生成时间(dataGenerationTime)和/或序列编号(sequenceNr)插入到丢失数据列表(missingList)中，且当前丢失数据量(currenMissingNr)的值加一。在当前丢失数据量(currenMissingNr)的数值达到最大丢失数量 (maxMissingNr)中设置的数值时，数据接收设备将丢失数据列表(missingList)中最早的至少一个数据生成时间(dataGenerationTime)和/或序列编号(sequenceNr)删除，以用于插入新检测到的丢失时序数据的数据生成时间(dataGenerationTime)和/或序列编号(sequenceNr)。
例如，timeSeriesCriteria中的数目参数设置为4，当数据接收设备检测到丢失的时序数据数目达到4个时(如，丢失的时序数据包括t1,t5,t10,t11)，数据接收设备向目标设备发送数据丢失通知消息，具体的数据接收设备可以依据通知内容类型(Notification Content Type)中的设置，仅向目标设备发送数据丢失的通知消息，或者在数据丢失通知消息中携带丢失数据列表(missingList)和/或当前丢失数据量(currentMissingNr)。
又例如，timeSeriesCriteria中的监测周期设置为时长为10min，具体实施时数据接收设备可以无论是否检测到丢失时序数据均每隔10分钟向目标设备发送一次数据丢失通知消息，或者，数据接收设备确定当前监测周期(10分钟)内是否检测到丢失时序数据，若检测到则在当前周期结束时向目标设备上报数据丢失通知消息并进入下一个周期的丢失数据检测，若在当前周期内未检测到丢失时序数据则直接进入下一个周期进行丢失时序数据检测。
进一步例如，timeSeriesCriteria中的数目参数设置为4且监测周期的时长设置为10min，则数据接收设备检测在当前监测周期(10分钟内)丢失的时序数据数目是否达到4个，若达到则向目标设备发送数据丢失通知消息，否则不发送。
又例如，timeSeriesCriteria中的参数设置为：数目参数设置为4或监测周期设置为10min，则数据接收设备确定当前检测到的丢失时序数据是否达到4个或是否达到监测周期设定的上报时间(10分钟)，只要满足其中一个条件则向目标设备发送数据丢失通知消息。
步骤S311：数据接收设备向目标设备发送数据丢失通知消息。
数据接收设备向目标设备发送数据丢失通知消息具体过程可以包括：数据接收设备向目标设备发送通知请求消息(Notify Request)，通知请求消息中携带具体的通知内容，如丢失数据列表(missingList)和/或当前丢失数据量(currentMissingNr)；目标设备接收到数据接收设备发送 的通知消息后向数据接收设备返回通知响应消息。
图10示出了本发明实施例六时序数据检测方法的流程图，该方法应用于M2M数据传输系统中，执行的主体为数据接收设备，如存储云端，本实施例方法在图1所示的时序资源中增加了最大丢失数据量、当前丢失数据量、丢失数据列表以及时序数据丢失通知触发参数四个属性，并且在订阅资源的事件通知规则属性中设置了数据丢失通知触发条件，使得数据接收设备在检测时序数据的丢失状况满足数据丢失通知触发条件时，向目标设备发送数据丢失通知消息，如图10所示，该方法的具体执行步骤包括：
步骤S401：数据源设备向数据接收设备发送请求在数据接收设备创建时序资源的第一请求消息。
其中，第一请求消息中携带以下参数：最大丢失数据量、当前丢失数据量、丢失数据列表以及时序数据丢失通知触发参数。
步骤S402：数据接收设备根据第一请求消息，建立时序资源。
数据接收设备根据接收到的第一请求消息中的最大丢失数据量、当前丢失数据量、丢失数据列表以及时序数据丢失通知触发参数，在时序资源中分别建立最大丢失数据量属性、当前丢失数据量属性、丢失数据列表属性以及时序数据丢失通知参数属性。
表4示出了时序资源中增加的最大丢失数据量属性、当前丢失数据量属性、丢失数据列表属性以及时序数据丢失通知参数属性的属性信息。
表4 时序资源中新增加的四个属性的属性信息
Figure PCTCN2016112486-appb-000005
Figure PCTCN2016112486-appb-000006
本实施例中表4中的最大丢失数据量属性、当前丢失数据量属性、丢失数据列表属性与实施例二表1中的相同，不再赘述，表4中的时序数据丢失通知触发参数属性与表2中的时序数据丢失通知触发参数定义表中的相同，不再赘述。
步骤S403：数据接收设备创建时序资源成功后，向数据源设备发送第一响应消息。
步骤S404：数据源设备向数据接收设备发送请求在数据接收设备创建时序实例资源的第二请求消息。
步骤S405：数据接收设备根据接收到的第二请求消息创建时序实例资源，其中时序实例资源为步骤S402中创建的时序资源的子资源。
步骤S406：数据接收设备创建时序实例资源成功后，向数据源设备 发送第二响应消息。
步骤S407：数据源设备向数据接收设备发送请求在数据接收设备创建订阅资源的第三请求消息。
步骤S408：数据接收设备根据第三请求消息以及第一请求消息中的数据丢失通知触发参数创建订阅资源。
具体的，数据接收设备在创建订阅资源的过程中包括：数据接收设备根据第一请求消息中的数据丢失通知触发参数创建数据丢失通知事件，在数据丢失通知事件中包含数据丢失通知触发条件。
本发明实施例中，数据接收设备根据时序数据丢失通知触发参数在订阅资源的事件通知规则(eventNotificationCreteria)属性中建立数据丢失通知触发条件。
步骤S409：数据接收设备创建时序资源成功后，向数据源设备发送第三响应消息。
步骤S410：数据接收设备对时序数据进行收集和存储，并对时序数据进行丢失检测和上报。
本实施例中，数据接收设备生成的时序资源中还包括丢失数据检测(missingDataDetect)参数，在对时序数据进行检测之前，还进一步确定丢失数据检测参数中的数值是否为真，当丢失数据检测参数中的数值为ture或为1时，确定丢失数据检测参数中的数值为真。当丢失数据检测参数为真时，数据接收设备检测在数据接收过程中是否有丢失的时序数据；若丢失数据检测参数中的数值不为真，订阅资源中的丢失数据订阅事件返回丢失数据检测错误或无法进行丢失数据检测等反馈信息。
进一步，本实施例中数据接收设备对时序数据进行丢失检测和上报的方法与实施例二中相同，不再赘述。
步骤S411：数据接收设备向目标设备发送数据丢失通知消息。
数据接收设备向目标设备发送数据丢失通知消息具体过程可以包括：数据接收设备向目标设备发送通知请求消息(Notify Request)，通知请求消息中携带具体的通知内容，如丢失数据列表(missingList)和/或当前丢失数据量(currentMissingNr)；目标设备接收到数据接收设备发送的通知消息后向数据接收设备返回通知响应消息。
图11示出了本发明实施例七时序数据检测方法的流程图，该方法应用于M2M数据传输系统中，执行的主体为数据接收设备，如存储云端，本实施例方法在图1所示的时序资源中增加了最大丢失数据量、当前丢失数据量、丢失数据列表、最长等待时间、时序数据丢失通知触发参数五个属性，并且在订阅资源的事件通知规则属性中设置了数据丢失通知触发条件，使得数据接收设备在检测时序数据的丢失状况满足数据丢失通知触发条件时，向目标设备发送数据丢失通知消息，如图11所示，该方法的具体执行步骤包括：
步骤S501：数据源设备向数据接收设备发送请求在数据接收设备创建时序资源的第一请求消息。
其中，第一请求消息中携带以下参数：最大丢失数据量、当前丢失数据量、丢失数据列表以及时序数据丢失通知触发参数。
步骤S502：数据接收设备根据第一请求消息，建立时序资源。
数据接收设备根据接收到的第一请求消息中的最大丢失数据量、当前丢失数据量、丢失数据列表以及时序数据丢失通知触发参数，在时序资源中分别建立最大丢失数据量属性、当前丢失数据量属性、丢失数据列表属性以及时序数据丢失通知属性。
表5示出了时序资源中增加的最大丢失数据量属性、当前丢失数据量属性、丢失数据列表属性以及时序数据丢失通知属性的属性信息。
表5 时序资源中新增加的五个属性的属性信息
Figure PCTCN2016112486-appb-000007
Figure PCTCN2016112486-appb-000008
本实施例中表5中的最大丢失数据量属性、当前丢失数据量属性、丢失数据列表属性以及时序数据丢失通知属性与表4中的相同，不再赘述，表5中的最长等待时间属性与4中相同，不再赘述。
步骤S503：数据接收设备创建时序资源成功后，向数据源设备发送第一响应消息。
步骤S504：数据源设备向数据接收设备发送请求在数据接收设备创建时序实例资源的第二请求消息。
步骤S505：数据接收设备根据接收到的第二请求消息创建时序实例 资源，其中时序实例资源为步骤S502中创建的时序资源的子资源。
步骤S506：数据接收设备创建时序实例资源成功后，向数据源设备发送第二响应消息。
步骤S507：数据源设备向数据接收设备发送请求在数据接收设备创建订阅资源的第三请求消息。
步骤S508：数据接收设备根据第三请求消息以及第一请求消息中的数据丢失通知触发参数创建订阅资源。
具体的，数据接收设备在创建订阅资源的过程中包括：数据接收设备根据第一请求消息中的数据丢失通知触发参数创建数据丢失通知事件，在数据丢失通知事件中包含数据丢失通知触发条件。
本发明实施例中，数据接收设备根据时序数据丢失通知触发参数在订阅资源的事件通知规则(eventNotificationCreteria)属性中建立数据丢失通知触发条件。
步骤S509：数据接收设备创建时序资源成功后，向数据源设备发送第三响应消息。
步骤S510：数据接收设备对时序数据进行收集和存储，并对时序数据进行丢失检测和上报。
本实施例中，数据接收设备生成的时序资源中还包括丢失数据检测(missingDataDetect)参数，在对时序数据进行检测之前，还进一步确定丢失数据检测参数中的数值是否为真，当丢失数据检测参数中的数值为ture或为1时，确定丢失数据检测参数中的数值为真。当丢失数据检测参数为真时，数据接收设备检测在数据接收过程中是否有丢失的时序数据；若丢失数据检测参数中的数值不为真，订阅资源中的丢失数据订阅事件返回丢失数据检测错误或无法进行丢失数据检测等反馈信息。
进一步，本实施例中数据接收设备对时序数据进行丢失检测和上报的方法与实施例四中相同，不再赘述。
步骤S511：数据接收设备向目标设备发送数据丢失通知消息。
数据接收设备向目标设备发送数据丢失通知消息具体过程可以包括：数据接收设备向目标设备发送通知请求消息(Notify Request)，通知请求消息中携带具体的通知内容，如丢失数据列表(missingList)和/或当 前丢失数据量(currentMissingNr)；目标设备接收到数据接收设备发送的通知消息后向数据接收设备返回通知响应消息。
图12示出了本发明实施例八时序数据检测方法的流程图，该方法应用于M2M数据传输系统中，执行的主体为数据源设备，其中数据源设备是指各类能够产生时序数据的设备，如监测传感器等，本实施例方法的主要步骤包括：
步骤S61：根据待发送的数据的数据信息，生成时序数据，其中，时序数据携带数据信息，数据信息包括时间信息和/或序列编号。
步骤S62：将时序数据发送给数据接收设备。
其中，发送给数据接收设备的时序数据用于数据接收设备根据接收到的时序数据所携带的时间信息和/或序列编号，确定在数据接收过程中是否有丢失的时序数据；若有丢失的时序数据，则保存丢失的时序数据的数据信息；数据接收设备还确定当前是否达到预设的数据丢失通知触发条件；若达到数据丢失通知触发条件，则向目标设备发送数据丢失通知信息。
图13示出了本发明实施例九时序数据检测方法的流程图，该方法应用于M2M数据传输系统中，主要步骤包括：
步骤S71：根据待发送的数据的数据信息，生成时序数据，其中，时序数据携带数据信息，数据信息包括时间信息和/或序列编号。
步骤S72：向数据接收设备发送请求数据接收设备建立时序资源的第一请求消息。
第一请求消息中携带以下参数：最大丢失数据量、当前丢失数据量以及丢失数据列表，用于数据接收设备根据最大丢失数据量、当前丢失数据量以及丢失数据列表在时序资源中分别建立的最大丢失数据量属性、当前丢失数据量属性以及丢失数据列表属性；
最大丢失数据量属性用于记录丢失的时序数据的最大数目，当前丢失数据量属性用于记录当前丢失的时序数据的数目，丢失数据列表用于记录已丢失的时序数据的时间信息和/或序列编号。
步骤S73：接收数据接收设备在时序资源建立完成后发送的第一响应消息。
步骤S74：向数据接收设备发送请求数据接收设备建立时序实例资源的第二请求消息。
步骤S75：接收数据接收设备在时序实例资源建立完成后发送的第二响应消息。
其中，时序实例资源为时序资源的子资源；时序资源及时序实例资源用于保存时序数据的属性信息。
步骤S76：向数据接收设备发送请求数据接收设备建立订阅资源的第三请求消息。
本实施例中，第三请求消息中携带时序数据丢失通知触发参数，用于数据接收设备在创建的订阅资源中根据时序数据丢失通知触发参数设置的丢失数据订阅事件；丢失数据订阅事件中包含根据时序数据丢失通知触发参数设置的数据丢失通知触发条件。
步骤S77：接收数据接收设备在订阅资源建立完成后发送的第三响应消息。
本发明实施例还提供了实施例九，本实施例九在实施例八的基础上进行改进，其中本实施例中在向数据接收设备发送的第一请求消息中还携带最长等待时间，用于数据接收设备根据最长等待时间，在时序资源中建立最长等待时间属性，其中，最长等待时间属性用于数据接收设备标识未接收到的时序数据被确定为丢失时序数据的最长等待时间。
本发明实施例还提供了实施例十，本实施例十在在实施例八的基础上进行改进，其中本实施例中在向数据接收设备发送的第一请求消息中还携带时序数据丢失通知触发参数，用于数据接收设备根据时序数据丢失通知触发参数在时序资源的订阅资源中设置丢失数据订阅事件，丢失数据订阅事件中包含根据时序数据丢失通知触发参数设置的数据丢失通知触发条件。
本发明实施例还提供了实施例十一，本实施例十一在在实施例九的基础上进行改进，其中本实施例中在向数据接收设备发送的第一请求消息中还携带时序数据丢失通知触发参数，用于数据接收设备根据时序数据丢失通知触发参数在时序资源的订阅资源中设置丢失数据订阅事件，丢失数据订阅事件中包含根据时序数据丢失通知触发参数设置的数据丢 失通知触发条件。在第三请求消息不再携带时序数据丢失通知触发参数。
图14示出了本发明实施例一时序数据检测装置的结构示意图，该装置应用于数据传输系统中，如图14所示，该装置包括第一确定模块81、存储模块82和第二确定模块83，其中：
第一确定模块81，用于根据来自数据源设备的时序数据所携带的数据信息，确定在数据接收过程中是否有丢失的时序数据，其中数据信息包括时间信息和/或序列编号；
存储模块82，用于若有丢失的时序数据，则保存丢失的时序数据的数据信息；
第二确定模块83，用于确定当前是否达到预设的数据丢失通知触发条件；
通知消息发送模块，用于若达到数据丢失通知触发条件，则向目标设备发送数据丢失通知信息。
在上述实施例中，第一确定模块81，还用于：
根据来自数据源设备的时序数据所携带的数据信息，确定在数据接收过程中是否有丢失的时序数据之前，确定预先建立的时序资源中缺失数据检测参数中的数值是否为真；
若为真，则根据来自数据源设备的时序数据所携带的数据信息，确定在数据接收过程中是否有丢失的时序数据。
在上述实施例中，时序数据检测装置还包括：时序资源建立模块，用于根据来自数据源设备的时序数据所携带的数据信息，确定在数据接收过程中是否有丢失的时序数据之前，根据来自数据源设备的请求建立时序资源的第一请求消息，建立时序资源；
其中，第一请求消息中携带以下参数：最大丢失数据量、当前丢失数据量以及丢失数据列表；时序资源中包括根据最大丢失数据量、当前丢失数据量以及丢失数据列表分别建立的最大丢失数据量属性、当前丢失数据量属性以及丢失数据列表属性；
最大丢失数据量属性用于记录丢失的时序数据的最大数目，当前丢失数据量属性用于记录当前丢失的时序数据的数目，丢失数据列表用于 记录已丢失的时序数据的时间信息和/或序列编号。
在上述实施例中，第一请求消息携带的参数中还包括：最长等待时间；
时序资源中还包括根据最长等待时间建立的最长等待时间属性，其中，最长等待时间属性用于标识未接收到的时序数据被确定为丢失时序数据的最长等待时间。
在上述实施例中，第一请求消息携带的参数中还包括：时序数据丢失通知触发参数；
时序资源中还包括订阅资源，订阅资源中包括根据时序数据丢失通知触发参数设置的丢失数据订阅事件；
丢失数据订阅事件中包含根据时序数据丢失通知触发参数设置的数据丢失通知触发条件。
在上述实施例中，时序数据检测装置还包括：
订阅资源建立模块，用于根据来自数据源设备的请求建立订阅资源的第二请求消息，建立订阅资源；
其中，订阅资源为时序资源的子资源，第二请求消息中携带时序数据丢失通知触发参数；
订阅资源中包括根据时序数据丢失通知触发参数设置的丢失数据订阅事件；
丢失数据订阅事件中包含根据时序数据丢失通知触发参数设置的数据丢失通知触发条件。
在上述实施例中，第一确定模块81，具体用于：
接收来自于数据源设备的周期性时序数据；
根据接到的周期性时序数据携带的周期时间或者与周期时间对应的序列编号的连续性，确定在数据接收过程中是否有丢失的时序数据。
在上述实施例中，第一确定模块81，具体用于：
根据接到的周期性时序数据携带的周期时间或者与周期时间对应的序列编号的连续性，确定是否存在未接收到的时序数据；
若存在未接收到的时序数据，则在等待预设时长之后确定是否仍有未接收到的时序数据；
若仍有未接收到的时序数据，则将在等待预设时长之后仍未接收到的时序数据确定为已丢失的时序数据。
在上述实施例中，第二确定模块83，还用于确定预先建立的订阅资源中是否设置有丢失数据订阅事件；
若有，则确定当前是否达到丢失数据订阅事件中预先设置的数据丢失通知触发条件。
在上述实施例中，数据丢失通知触发条件包括：
当前时间是否达到预设的丢失数据上报周期中所设定的上报时间；
和/或，
当前已丢失的时序数据的数量是否达到预设的上报数量。
图15示出了本发明实施例二时序数据检测装置的结构示意图，该装置应用于数据传输系统中，如图15所示，该装置包括：时序数据生成模块91及第一发送模块92，其中：
时序数据生成模块91，用于根据待发送的数据的数据信息，生成时序数据，其中，时序数据携带数据信息，数据信息包括时间信息和/或序列编号；
第一发送模块92，用于将时序数据发送给数据接收设备，用于数据接收设备根据接收到的时序数据所携带的时间信息和/或序列编号，确定在数据接收过程中是否有丢失的时序数据；若有丢失的时序数据，则保存丢失的时序数据的数据信息；数据接收设备还确定当前是否达到预设的数据丢失通知触发条件；若达到数据丢失通知触发条件，则向目标设备发送数据丢失通知信息。
在上述实施例中，第一发送模块92，还用于将时序数据发送给数据接收设备之前，向数据接收设备发送请求数据接收设备建立时序资源的第一请求消息；
第一请求消息中携带以下参数：最大丢失数据量、当前丢失数据量以及丢失数据列表；用于数据接收设备根据最大丢失数据量、当前丢失数据量以及丢失数据列表在时序资源中分别建立的最大丢失数据量属性、当前丢失数据量属性以及丢失数据列表属性；
最大丢失数据量属性用于记录丢失的时序数据的最大数目，当前丢 失数据量属性用于记录当前丢失的时序数据的数目，丢失数据列表用于记录已丢失的时序数据的时间信息和/或序列编号。
在上述实施例中，第一请求消息携带的参数中还包括：最长等待时间，用于数据接收设备根据最长等待时间，在时序资源中建立最长等待时间属性，其中，最长等待时间属性用于数据接收设备标识未接收到的时序数据被确定为丢失时序数据的最长等待时间。
在上述实施例中，第一请求消息携带的参数中还包括：时序数据丢失通知触发参数，用于数据接收设备根据时序数据丢失通知触发参数在时序资源的订阅资源中设置丢失数据订阅事件，丢失数据订阅事件中包含根据时序数据丢失通知触发参数设置的数据丢失通知触发条件。
在上述实施例中，时序数据检测装置还包括：第二发送模块，用于向数据接收设备发送用于请求数据接收设备建立订阅资源的第二请求消息；
第二请求消息中携带时序数据丢失通知触发参数，用于数据接收设备在创建的订阅资源中根据时序数据丢失通知触发参数设置的丢失数据订阅事件；丢失数据订阅事件中包含根据时序数据丢失通知触发参数设置的数据丢失通知触发条件。
图16示出了本发明实施例时序数据检测设备的结构示意图。如图16所示，时序数据检测设备1400包括通信接口1401、存储器1403和处理器1402，其中，通信接口1401、处理器1402、存储器1403、通过总线1404相互连接；总线1404可以是外设部件互连标准(peripheral component interconnect，简称PCI)总线或扩展工业标准结构(extended industry standard architecture，简称EISA)总线等。总线可以分为地址总线、数据总线、控制总线等。为便于表示，图16中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
通信接口1401用于与发送端通信。存储器1403，用于存放程序。具体地，程序可以包括程序代码，程序代码包括计算机操作指令。存储器1403可能包含随机存取存储器(random access memory，简称RAM)，也可能还包括非易失性存储器(non-volatile memory)，例如至少一个磁盘存储器。
处理器1402执行存储器1403所存放的程序，实现本发明前述方法实施例的方法：
包括：
根据来自数据源设备的时序数据所携带的数据信息，确定在数据接收过程中是否有丢失的时序数据，其中数据信息包括时间信息和/或序列编号；
若有丢失的时序数据，则保存丢失的时序数据的数据信息；
确定当前是否达到预设的数据丢失通知触发条件；
若达到数据丢失通知触发条件，则向目标设备发送数据丢失通知信息。
上述的处理器1402可以是通用处理器，包括中央处理器(Central Processing Unit，简称CPU)、网络处理器(Network Processor，简称NP)等；还可以是数字信号处理器(DSP)、专用集成电路(ASIC)、现场可编程门阵列(FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。
本实施例的时序数据检测设备，根据已经接收到的时序数据的时间信息，确定在数据接收过程中是否有丢失的数据信息时序数据，并在满足数据丢失通知触发条件时向目标设备上报丢失的时序数据的信息，从而实现了在数据传输系统中实现对丢失时序数据的检测和上报。
本领域普通技术人员可以理解：实现上述各方法实施例的全部或部分步骤可以通过程序指令相关的硬件来完成。前述的程序可以存储于一计算机可读取存储介质中。该程序在执行时，执行包括上述各方法实施例的步骤；而前述的存储介质包括：ROM、RAM、磁碟或者光盘等各种可以存储程序代码的介质。
最后应说明的是：以上各实施例仅用以说明本发明的技术方案，而非对其限制；尽管参照前述各实施例对本发明进行了详细的说明，本领域的普通技术人员应当理解：其依然可以对前述各实施例所记载的技术方案进行修改，或者对其中部分或者全部技术特征进行等同替换；而这些修改或者替换，并不使相应技术方案的本质脱离本发明各实施例技术方案的范围。

Claims (30)

  1. 一种时序数据检测方法，其特征在于，所述方法应用于数据传输系统中，包括：
    根据来自数据源设备的时序数据所携带的数据信息，确定在数据接收过程中是否有丢失的时序数据，其中所述数据信息包括时间信息和/或序列编号；
    若有丢失的时序数据，则保存所述丢失的时序数据的数据信息；
    确定当前是否达到预设的数据丢失通知触发条件；
    若达到所述数据丢失通知触发条件，则向目标设备发送数据丢失通知信息。
  2. 根据权利要求1所述的方法，其特征在于，所述根据来自数据源设备的时序数据所携带的数据信息，确定在数据接收过程中是否有丢失的时序数据之前，还包括：
    确定预先建立的时序资源中缺失数据检测参数中的数值是否为真；
    若为真，则根据来自数据源设备的时序数据所携带的数据信息，确定在数据接收过程中是否有丢失的时序数据。
  3. 根据权利要求1或2所述的方法，其特征在于，所述根据来自数据源设备的时序数据所携带的数据信息，确定在数据接收过程中是否有丢失的时序数据之前，还包括：
    根据来自数据源设备的请求建立时序资源的第一请求消息，建立时序资源；
    其中，所述第一请求消息中携带以下参数：最大丢失数据量、当前丢失数据量以及丢失数据列表；所述时序资源中包括根据所述最大丢失数据量、所述当前丢失数据量以及所述丢失数据列表分别建立的最大丢失数据量属性、当前丢失数据量属性以及丢失数据列表属性；
    所述最大丢失数据量属性用于记录丢失的时序数据的最大数目，所述当前丢失数据量属性用于记录当前丢失的时序数据的数目，所述丢失数据列表用于记录已丢失的时序数据的时间信息和/或序列编号。
  4. 根据权利要求3所述的方法，其特征在于，所述第一请求消息携带的参数中还包括：最长等待时间；
    所述时序资源中还包括根据所述最长等待时间建立的最长等待时间属性，其中，所述最长等待时间属性用于标识未接收到的时序数据被确定为丢失时序数据的最长等待时间。
  5. 根据权利要求3或4所述的方法，其特征在于，所述第一请求消息携带的参数中还包括：时序数据丢失通知触发参数；
    所述时序资源中还包括订阅资源，所述订阅资源中包括根据所述时序数据丢失通知触发参数设置的丢失数据订阅事件；
    所述丢失数据订阅事件中包含根据所述时序数据丢失通知触发参数设置的所述数据丢失通知触发条件。
  6. 根据权利要求3或4所述的方法，其特征在于，所述方法还包括：
    根据来自所述数据源设备的请求建立订阅资源的第二请求消息，建立订阅资源；
    其中，所述订阅资源为所述时序资源的子资源，所述第二请求消息中携带时序数据丢失通知触发参数；
    所述订阅资源中包括根据所述时序数据丢失通知触发参数设置的丢失数据订阅事件；
    所述丢失数据订阅事件中包含根据所述时序数据丢失通知触发参数设置的所述数据丢失通知触发条件。
  7. 根据权利要求1所述的方法，其特征在于，所述根据来自数据源设备的时序数据所携带的时间信息，确定在数据接收过程中是否有丢失的时序数据，包括：
    接收来自于所述数据源设备的周期性时序数据；
    根据接到的所述周期性时序数据携带的周期时间或者与所述周期时间对应的序列编号的连续性，确定在数据接收过程中是否有丢失的时序数据。
  8. 根据权利要求7所述的方法，其特征在于，所述根据接到的所述周期性时序数据携带的周期时间或者与所述周期时间对应的序列编号的连续性，确定在数据接收过程中是否有丢失的时序数据，包括：
    根据所述接到的所述周期性时序数据携带的周期时间或者与所述周 期时间对应的序列编号的连续性，确定是否存在未接收到的时序数据；
    若存在未接收到的时序数据，则在等待预设时长之后确定是否仍有未接收到的时序数据；
    若仍有未接收到的时序数据，则将所述在等待预设时长之后仍未接收到的时序数据确定为已丢失的时序数据。
  9. 根据权利要求1所述的方法，其特征在于，所述确定当前是否达到预设的数据丢失通知触发条件之前，还包括：
    确定预先建立的订阅资源中是否设置有丢失数据订阅事件；
    若有，则确定当前是否达到所述丢失数据订阅事件中预先设置的数据丢失通知触发条件。
  10. 根据权利要求1所述的方法，其特征在于，所述数据丢失通知触发条件包括：
    当前时间是否达到预设的丢失数据上报周期中所设定的上报时间；
    和/或，
    当前已丢失的时序数据的数量是否达到预设的上报数量。
  11. 一种时序数据检测方法，其特征在于，所述方法应用于数据传输系统中，包括：
    根据待发送的数据的数据信息，生成时序数据，其中，所述时序数据携带所述数据信息，所述数据信息包括时间信息和/或序列编号；
    将所述时序数据发送给数据接收设备，用于所述数据接收设备根据接收到的时序数据所携带的时间信息和/或序列编号，确定在数据接收过程中是否有丢失的时序数据；若有丢失的时序数据，则保存所述丢失的时序数据的数据信息；所述数据接收设备还确定当前是否达到预设的数据丢失通知触发条件；若达到所述数据丢失通知触发条件，则向目标设备发送数据丢失通知信息。
  12. 根据权利要求11所述的方法，其特征在于，所述将所述时序数据发送给数据接收设备之前，还包括：
    向所述数据接收设备发送请求所述数据接收设备建立时序资源的第一请求消息；
    所述第一请求消息中携带以下参数：最大丢失数据量、当前丢失数 据量以及丢失数据列表；用于所述数据接收设备根据所述最大丢失数据量、所述当前丢失数据量以及所述丢失数据列表在时序资源中分别建立的最大丢失数据量属性、当前丢失数据量属性以及丢失数据列表属性；
    所述最大丢失数据量属性用于记录丢失的时序数据的最大数目，所述当前丢失数据量属性用于记录当前丢失的时序数据的数目，所述丢失数据列表用于记录已丢失的时序数据的时间信息和/或序列编号。
  13. 根据权利要求12所述的方法，其特征在于，所述第一请求消息携带的参数中还包括：最长等待时间，用于所述数据接收设备根据所述最长等待时间，在所述时序资源中建立最长等待时间属性，其中，所述最长等待时间属性用于所述数据接收设备标识未接收到的时序数据被确定为丢失时序数据的最长等待时间。
  14. 根据权利要求12或13所述的方法，其特征在于，所述第一请求消息携带的参数中还包括：时序数据丢失通知触发参数，用于所述数据接收设备根据所述时序数据丢失通知触发参数在时序资源的订阅资源中设置丢失数据订阅事件，所述丢失数据订阅事件中包含根据所述时序数据丢失通知触发参数设置的所述数据丢失通知触发条件。
  15. 根据权利要求12或13所述的方法，其特征在于，所述方法还包括：
    向所述数据接收设备发送用于请求所述数据接收设备建立订阅资源的第二请求消息；
    所述第二请求消息中携带时序数据丢失通知触发参数，用于所述数据接收设备在创建的订阅资源中根据所述时序数据丢失通知触发参数设置的丢失数据订阅事件；所述丢失数据订阅事件中包含根据所述时序数据丢失通知触发参数设置的所述数据丢失通知触发条件。
  16. 一种时序数据检测装置，其特征在于，所述装置应用于数据传输系统中，包括：
    第一确定模块，用于根据来自数据源设备的时序数据所携带的数据信息，确定在数据接收过程中是否有丢失的时序数据，其中所述数据信息包括时间信息和/或序列编号；
    存储模块，用于若有丢失的时序数据，则保存所述丢失的时序数据 的数据信息；
    第二确定模块，用于确定当前是否达到预设的数据丢失通知触发条件；
    通知消息发送模块，用于若达到所述数据丢失通知触发条件，则向目标设备发送数据丢失通知信息。
  17. 根据权利要求16所述的装置，其特征在于，所述第一确定模块，还用于：
    根据来自数据源设备的时序数据所携带的数据信息，确定在数据接收过程中是否有丢失的时序数据之前，确定预先建立的时序资源中缺失数据检测参数中的数值是否为真；
    若为真，则根据来自数据源设备的时序数据所携带的数据信息，确定在数据接收过程中是否有丢失的时序数据。
  18. 根据权利要求16或17所述的装置，其特征在于，所述装置还包括：时序资源建立模块，用于根据来自数据源设备的时序数据所携带的数据信息，确定在数据接收过程中是否有丢失的时序数据之前，根据来自数据源设备的请求建立时序资源的第一请求消息，建立时序资源；
    其中，所述第一请求消息中携带以下参数：最大丢失数据量、当前丢失数据量以及丢失数据列表；所述时序资源中包括根据所述最大丢失数据量、所述当前丢失数据量以及所述丢失数据列表分别建立的最大丢失数据量属性、当前丢失数据量属性以及丢失数据列表属性；
    所述最大丢失数据量属性用于记录丢失的时序数据的最大数目，所述当前丢失数据量属性用于记录当前丢失的时序数据的数目，所述丢失数据列表用于记录已丢失的时序数据的时间信息和/或序列编号。
  19. 根据权利要求18所述的装置，其特征在于，所述第一请求消息携带的参数中还包括：最长等待时间；
    所述时序资源中还包括根据所述最长等待时间建立的最长等待时间属性，其中，所述最长等待时间属性用于标识未接收到的时序数据被确定为丢失时序数据的最长等待时间。
  20. 根据权利要求18或19所述的装置，其特征在于，所述第一请求消息携带的参数中还包括：时序数据丢失通知触发参数；
    所述时序资源中还包括订阅资源，所述订阅资源中包括根据所述时序数据丢失通知触发参数设置的丢失数据订阅事件；
    所述丢失数据订阅事件中包含根据所述时序数据丢失通知触发参数设置的所述数据丢失通知触发条件。
  21. 根据权利要求18或19所述的装置，其特征在于，所述装置还包括：
    订阅资源建立模块，用于根据来自所述数据源设备的请求建立订阅资源的第二请求消息，建立订阅资源；
    其中，所述订阅资源为所述时序资源的子资源，所述第二请求消息中携带时序数据丢失通知触发参数；
    所述订阅资源中包括根据所述时序数据丢失通知触发参数设置的丢失数据订阅事件；
    所述丢失数据订阅事件中包含根据所述时序数据丢失通知触发参数设置的所述数据丢失通知触发条件。
  22. 根据权利要求16所述的装置，其特征在于，所述第一确定模块，具体用于：
    接收来自于所述数据源设备的周期性时序数据；
    根据接到的所述周期性时序数据携带的周期时间或者与所述周期时间对应的序列编号的连续性，确定在数据接收过程中是否有丢失的时序数据。
  23. 根据权利要求22所述的装置，其特征在于，所述第一确定模块，具体用于：
    根据所述接到的所述周期性时序数据携带的周期时间或者与所述周期时间对应的序列编号的连续性，确定是否存在未接收到的时序数据；
    若存在未接收到的时序数据，则在等待预设时长之后确定是否仍有未接收到的时序数据；
    若仍有未接收到的时序数据，则将所述在等待预设时长之后仍未接收到的时序数据确定为已丢失的时序数据。
  24. 根据权利要求16所述的装置，其特征在于，所述第二确定模块，还用于确定预先建立的订阅资源中是否设置有丢失数据订阅事件；
    若有，则确定当前是否达到所述丢失数据订阅事件中预先设置的数据丢失通知触发条件。
  25. 根据权利要求16所述的装置，其特征在于，所述数据丢失通知触发条件包括：
    当前时间是否达到预设的丢失数据上报周期中所设定的上报时间；
    和/或，
    当前已丢失的时序数据的数量是否达到预设的上报数量。
  26. 一种时序数据检测装置，其特征在于，所述装置应用于数据传输系统中，包括：
    时序数据生成模块，用于根据待发送的数据的数据信息，生成时序数据，其中，所述时序数据携带所述数据信息，所述数据信息包括时间信息和/或序列编号；
    第一发送模块，用于将所述时序数据发送给数据接收设备，用于所述数据接收设备根据接收到的时序数据所携带的时间信息和/或序列编号，确定在数据接收过程中是否有丢失的时序数据；若有丢失的时序数据，则保存所述丢失的时序数据的数据信息；所述数据接收设备还确定当前是否达到预设的数据丢失通知触发条件；若达到所述数据丢失通知触发条件，则向目标设备发送数据丢失通知信息。
  27. 根据权利要求26所述的装置，其特征在于，所述发送模块，还用于将所述时序数据发送给数据接收设备之前，向所述数据接收设备发送请求所述数据接收设备建立时序资源的第一请求消息；
    所述第一请求消息中携带以下参数：最大丢失数据量、当前丢失数据量以及丢失数据列表；用于所述数据接收设备根据所述最大丢失数据量、所述当前丢失数据量以及所述丢失数据列表在时序资源中分别建立的最大丢失数据量属性、当前丢失数据量属性以及丢失数据列表属性；
    所述最大丢失数据量属性用于记录丢失的时序数据的最大数目，所述当前丢失数据量属性用于记录当前丢失的时序数据的数目，所述丢失数据列表用于记录已丢失的时序数据的时间信息和/或序列编号。
  28. 根据权利要求27所述的装置，其特征在于，所述第一请求消息携带的参数中还包括：最长等待时间，用于所述数据接收设备根据所述 最长等待时间，在所述时序资源中建立最长等待时间属性，其中，所述最长等待时间属性用于所述数据接收设备标识未接收到的时序数据被确定为丢失时序数据的最长等待时间。
  29. 根据权利要求27或28所述的装置，其特征在于，所述第一请求消息携带的参数中还包括：时序数据丢失通知触发参数，用于所述数据接收设备根据所述时序数据丢失通知触发参数在时序资源的订阅资源中设置丢失数据订阅事件，所述丢失数据订阅事件中包含根据所述时序数据丢失通知触发参数设置的所述数据丢失通知触发条件。
  30. 根据权利要求27或28所述的装置，其特征在于，所述装置还包括：第二发送模块，用于向所述数据接收设备发送用于请求所述数据接收设备建立订阅资源的第二请求消息；
    所述第二请求消息中携带时序数据丢失通知触发参数，用于所述数据接收设备在创建的订阅资源中根据所述时序数据丢失通知触发参数设置的丢失数据订阅事件；所述丢失数据订阅事件中包含根据所述时序数据丢失通知触发参数设置的所述数据丢失通知触发条件。
PCT/CN2016/112486 2015-12-31 2016-12-27 时序数据检测方法及装置 WO2017114400A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
EP16881189.1A EP3393085B1 (en) 2015-12-31 2016-12-27 Method and device for time sequence data detection
US16/023,490 US10911970B2 (en) 2015-12-31 2018-06-29 Method and apparatus for detecting time series data
US17/091,710 US11979761B2 (en) 2015-12-31 2020-11-06 Method and apparatus for detecting time series data

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201511031852.8 2015-12-31
CN201511031852.8A CN106937241B (zh) 2015-12-31 2015-12-31 时序数据检测方法及装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/023,490 Continuation US10911970B2 (en) 2015-12-31 2018-06-29 Method and apparatus for detecting time series data

Publications (1)

Publication Number Publication Date
WO2017114400A1 true WO2017114400A1 (zh) 2017-07-06

Family

ID=59224609

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/112486 WO2017114400A1 (zh) 2015-12-31 2016-12-27 时序数据检测方法及装置

Country Status (4)

Country Link
US (2) US10911970B2 (zh)
EP (1) EP3393085B1 (zh)
CN (1) CN106937241B (zh)
WO (1) WO2017114400A1 (zh)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111830913A (zh) * 2019-04-22 2020-10-27 北京国电智深控制技术有限公司 一种数据获取方法及装置
CN112398797B (zh) * 2019-08-19 2023-05-02 贵州白山云科技股份有限公司 数据传输方法、接收装置、发送装置、介质、设备及系统
CN111224756B (zh) * 2019-12-26 2022-07-12 东软集团股份有限公司 确定数据传输异常的方法、装置、存储介质及电子设备
CN114205259A (zh) * 2021-12-07 2022-03-18 施耐德电气（中国）有限公司 一种网关上数异常诊断方法和装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1701566A (zh) * 2003-03-26 2005-11-23 松下电器产业株式会社 无线电信息通信系统
US20130226613A1 (en) * 2012-02-23 2013-08-29 Robert Bosch Gmbh System and Method for Estimation of Missing Data in a Multivariate Longitudinal Setup
CN103368787A (zh) * 2012-03-28 2013-10-23 索尼公司 信息处理装置、信息处理方法和程序
CN104750830A (zh) * 2015-04-01 2015-07-01 东南大学 时间序列数据的周期挖掘方法

Family Cites Families (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20020089478A (ko) * 2000-04-17 2002-11-29 노오텔 네트웍스 리미티드 무선 통신용 물리층 및 링크층에서의 ａｒｑ 프로토콜의협력
US20060056421A1 (en) * 2004-09-10 2006-03-16 Interdigital Technology Corporation Reducing latency when transmitting acknowledgements in mesh networks
US8755407B2 (en) * 2005-02-18 2014-06-17 Qualcomm Incorporated Radio link protocols for enhancing efficiency of multi-link communication systems
JP4978327B2 (ja) * 2007-06-19 2012-07-18 富士通株式会社 再送制御方法及びその装置
CN102495851B (zh) 2011-11-17 2014-11-05 百度在线网络技术（北京）有限公司 时序数据的存储和查询方法、系统及装置
CN104247323B (zh) * 2012-02-24 2018-07-13 马维尔国际贸易有限公司 基于下层反馈的跨层调度
WO2013169183A1 (en) * 2012-05-11 2013-11-14 Telefonaktiebolaget L M Ericsson (Publ) Methods and apparatus for detecting frame number discontinuities between radio nodes
EP2878098B1 (en) * 2012-07-27 2018-11-21 Telefonaktiebolaget LM Ericsson (publ) User equipment node, server node and methods performed in such nodes for performing file repair procedure
US10034023B1 (en) * 2012-07-30 2018-07-24 Google Llc Extended protection of digital video streams
CN103269260A (zh) * 2013-06-03 2013-08-28 腾讯科技（深圳）有限公司 数据传输方法、数据接收端、数据发送端和数据传输系统
KR102208119B1 (ko) * 2013-09-27 2021-01-27 엘지전자 주식회사 M2m 시스템에서 통지 메시지 전달 방법 및 이를 위한 장치
CN103605805B (zh) 2013-12-09 2016-10-26 冶金自动化研究设计院 一种海量时序数据的存储方法
JP6135529B2 (ja) * 2014-02-04 2017-05-31 横河電機株式会社 情報表示装置、情報処理装置、情報表示システム、および情報表示方法

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1701566A (zh) * 2003-03-26 2005-11-23 松下电器产业株式会社 无线电信息通信系统
US20130226613A1 (en) * 2012-02-23 2013-08-29 Robert Bosch Gmbh System and Method for Estimation of Missing Data in a Multivariate Longitudinal Setup
CN103368787A (zh) * 2012-03-28 2013-10-23 索尼公司 信息处理装置、信息处理方法和程序
CN104750830A (zh) * 2015-04-01 2015-07-01 东南大学 时间序列数据的周期挖掘方法

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3393085A4 *

Also Published As

Publication number Publication date
US20180310196A1 (en) 2018-10-25
EP3393085B1 (en) 2022-05-11
CN106937241A (zh) 2017-07-07
US20210058811A1 (en) 2021-02-25
US10911970B2 (en) 2021-02-02
US11979761B2 (en) 2024-05-07
CN106937241B (zh) 2021-05-18
EP3393085A1 (en) 2018-10-24
EP3393085A4 (en) 2018-10-24

Similar Documents

Publication Publication Date Title
WO2017114400A1 (zh) 时序数据检测方法及装置
JP2011505751A (ja) 近接関係を用いたモバイル機器の動作の修正
CN108418743B (zh) 一种聊天室消息分发方法、装置及电子设备
CN111093159B (zh) 一种消息推送方法、装置、服务器及计算机可读存储介质
RU2015128657A (ru) Способ и устройство для сообщения о запросе на вызов
CN109982034B (zh) 视频监控系统中的访问请求处理方法及装置
US10548029B2 (en) Systems and methods for identifying a cell type and cell communication capabilities from cellular broadcast data
US10219133B2 (en) Notification message transmission method and device, and computer storage medium
TWI771480B (zh) 轉發聊天信息的方法、裝置和電子設備
CN105704338A (zh) 一种混音方法、混音设备及系统
CN106717068B (zh) 一种nan设备之间的距离测量方法及nan设备
WO2020063381A1 (zh) 数据通信方法、服务器装置、客户端装置和介质
US9009248B2 (en) Apparatus and method of performing discovery based on priority level in distributed network, and method of determining discovery back-off time
JP6621075B2 (ja) リソース取得方法および装置
WO2015154459A1 (zh) 订阅资源变更通知的方法及装置
CN110213155B (zh) 通信处理方法、装置及相关设备、存储介质
WO2016169441A1 (zh) 消息推送方法及装置
CN107220811B (zh) 流程中节点激活的方法及装置
CN112860431B (zh) 微服务节点的连接方法、系统、设备及存储介质
CN107852366B (zh) 减少网状网络中的延时的方法、中继节点和计算机可读存储介质
CN110019025B (zh) 一种流数据处理方法和装置
CN108966160B (zh) 一种短信处理方法、装置及计算机可读存储介质
CN113543022A (zh) 发射功率的确定方法、装置、对讲机、设备及存储介质
WO2021052289A1 (zh) 事件通知方法、系统、服务器设备、计算机存储介质
CN103581237B (zh) 一种实现ParlayX和ParlayREST距离通知的方法

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 16881189

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 2016881189

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2016881189

Country of ref document: EP

Effective date: 20180716