WO2020227803A1 - Method of detecting incomplete electronic record sets using sequential numbering - Google Patents
Method of detecting incomplete electronic record sets using sequential numbering Download PDFInfo
- Publication number
- WO2020227803A1 WO2020227803A1 PCT/CA2019/050654 CA2019050654W WO2020227803A1 WO 2020227803 A1 WO2020227803 A1 WO 2020227803A1 CA 2019050654 W CA2019050654 W CA 2019050654W WO 2020227803 A1 WO2020227803 A1 WO 2020227803A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- message
- sender
- sequence
- text
- text message
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
- H04L51/21—Monitoring or handling of messages
- H04L51/216—Handling conversation history, e.g. grouping of messages in sessions or threads
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
- H04L51/58—Message adaptation for wireless communication
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/12—Applying verification of the received information
Definitions
- TITLE Method of Detecting Incomplete Electronic Record Sets using Sequential Numbering
- the present invention overcomes the disadvantages of the prior art by providing a method of verifying the completeness and order of data transmitted in a sequence from a data provider to a data receiver by verifying the sequential history of the data elements.
- Text messages each have a destination address (GSM Specification # 23.040) and a user-accessible field such as the user data.
- the method of the present invention includes the steps of identifying the receiver for a text message to be sent by the sender and then generating a current sequence marker for the receiver.
- the current sequence marker represents a next predicted sequence identifier in a sequence of text messages between the sender and receiver. For example, if the sequence of messages between the sender and receiver includes 76 messages and the sequence marker is configured to be a numeric integer, then the last sequence identifier used would be 76 and the next sequence identifier (76 +1 or 77) would result in the current sequence marker being 77.
- sequence identifiers comprise alphabetical characters (AA, AB, AC, etc.) and the last sequence identifier used was AG, then the next predicted sequence identifier would be AH, hence the current sequence marker would be AH.
- the next step in the method is to insert the current sequence marker into the user-accessible field of the text message and then send the message to the recipient.
- the sequence marker is formed from a sequence of alphanumeric characters which are human readable. Health records, social media network messages and records of financial transactions, including e- commerce transactions, would similarly benefit from sequential numbering.
- Figure 1 is a schematic view of the system of the present invention showing the system of the present invention being used to send a text message from a Sender A to a Recipient B.
- the system of the present invention shown generally as item 10, consists of two text-messaging-capable computing devices 12 and 14 in communication with each other via a network 16.
- Network 16 could be a telecom network, a local area network or the internet, but for most practical applications, network 16 is a cellular network.
- Network 16 is capable of facilitating Text Messaging using 3GPP TS 23.040 or other standards or proprietary methods of transporting text messages, that can send Sender A’s message 22 to Sender A’s cellular network 37.
- Sender A’s cellular network 37 then forwards Sender A’s message 22 via Network 16, again using standards or proprietary methods of transporting text messages, to Recipient B’s cellular network 38, where it may reside or be made available via network 16 to Recipient B’s text message application 18 via Network 16 using standards or proprietary methods for transporting text messages.
- Data source 20 contains data about text messages and also contains data about the history of previously sent text messages. It is essential that data source 20 contains the contact information of recipients and be operative for the storage and retrieval of sequence identifier 26 for each recipient.
- data source 20 could be operative in several forms, including (i) a traditional relational database such as Microsoft SQL Server; or (ii) a delimited text file database containing the contact information of recipients and sequence identifier 26 for each recipient; or (iii) a data file containing the contact information of recipients and sequence identifier 26 for each recipient; or (iv) a record of previously sent messages (hereinafter referred to as the“message history”) stored in their native format within Sender A’s text message application 18, and process 2, or otherwise accessible by Sender A; or (v) some other record of, or copy of, the message history that contains the contact information of recipients and sequence identifier 26 for each recipient.
- a traditional relational database such as Microsoft SQL Server
- a delimited text file database containing the contact information of recipients and sequence identifier 26 for each recipient
- a data file containing the contact information of recipients and sequence identifier 26 for each recipient or
- a record of previously sent messages hereinafter referred to as the“message history”
- data source 20 is a traditional database, a data file, or a message history, it is accessible by and interoperable with the other components of the present invention, as described herein.
- Data source 20 includes data about the components of previously sent messages from Sender A to text message recipients, and may also include the full or partial text and other data (e.g., multimedia data types) that comprise previously sent messages, including (i) message header fields such as destination address 24, and (ii) the message bodies of previously sent text messages.
- data e.g., multimedia data types
- data source 20 Regardless of where data source 20 resides, or whether data source 20 is a traditional database or another form of accessible message history, its purpose is to contain information about previously sent messages, including the addresses 24 of message recipients and sequence identifier 26 for each recipient, or next sequence marker 30 for each recipient, or both sequence identifier 26 and next sequence marker 30 for each recipient.
- data source 20 is an accessible message history of previously sent messages
- the contact information of recipients and also sequence identifier 26 is retrievable or discernible. For example, by reading the message history, such as those found in a data folder of previously sent messages within text message application 18 or located somewhere else on computing device 12, Sender A (manually) or process 2 (programmatically) could discern what the next sequence marker 30 would be.
- Sender A’s computing device 12 is a network- 16-enabled device such as a desktop or laptop computer, a smartphone, tablet, smart TV, or another type of device.
- Computing device 12 could be a single device, a server, or a plurality of servers and devices, and is configured as a text message sender and uses text message application 18, and possibly also process 2, to send text messages to clients such as Recipient B.
- Text message application 18 may reside on the local computing device 12 or a local server, or be accessible via the network 16.
- Computing device 12 and text message application 18 also have access to a data source 20 (as a database or an accessible message history) that may reside on the local device 12, or a local server, or a local network, or somewhere within the cloud, or on the sender’s cellular network 37.
- a data source 20 (as a database or an accessible message history) that may reside on the local device 12, or a local server, or a local network, or somewhere within the cloud, or on the sender’s cellular network 37.
- data source 20 is operatively coupled to text message application 18.
- computing device 12 is configured to send text message(s) 22 from Sender A to Recipient B, and more particularly between computing devices 12 and 14 which are operated or otherwise controlled by Sender A and Recipient B respectively.
- Receiver B’s computing device 14 is a network- 16-enabled device such as a desktop or laptop computer, a smartphone, tablet, smart TV, or another type of device.
- Receiver B’s computing device 14 has access to text message application 18 which is (i) an application such as Android Messenger, or other application, that resides on computing device 14; or (ii) an internet-based or cloud-based message service such as Apple’s iMessage which is accessible by a web browser such as Google Chrome, Microsoft Internet Explorer, Mozilla Firefox, or Safari, or others; or (iii) a hybrid of the foregoing two approaches.
- Names of message recipients, destination address(es) 24 and other relevant information about a plurality of contacts are stored in data source 20 (as a database or an accessible message history).
- Data source 20 is operatively coupled to sequence identifier 26.
- sequence identifier 26 is to enumerate each text message communication from Sender A to each of Sender A’s individual recipient contacts and to maintain a component of data source 20 (as a database or an accessible message history) for each contact, such that every successive message from Sender A to each of its contacts is identified by the next value in a predictable sequence that is intuitively known and understood in the recipients’ language and/or culture.
- this predictable sequence consists of the standard Arabic whole numbers, and the number 76 represents the most recent sequence marker from the messages that have previously been sent from Sender A to Recipient B, and in this example the number 77 represents the next sequence marker 30 that would be used in a future message being sent from Sender A to Recipient B.
- Sender A’s sequence identifier 26 for its text message correspondence with Recipient B consists of a simple incrementing Arabic numerical sequence. (In the first text message communication from Sender A to Recipient B, a starting message sequence identifier would have to be used. This starting sequence number could be the Arabic numeral 1 or could be another number used to start a sequence.) Recipient B may notice that the sequence marker for the most recent text message was 76, and that, therefore, the sequence marker for the next legitimate and expected message from Sender A should be 77.
- text message senders also use process 2, which is an application or script used in conjunction with text message application 18 to create and send texts to receivers.
- the text message application 18 that creates the characters for a user-accessible header field would execute an alternative process 2 that programmatically inserts an appropriate next sequence marker 30 into one of the fields within the text message.
- the next sequence marker 30 becomes embedded within and is part of text message.
- next sequential marker 30 means it is easier for Recipient B to quickly and more easily identify a missing text message and request that Sender A re-send the message.
- the present invention assists its human users in recognizing and understanding the significance of sequence identifier 26 and sequence marker 30 (which in this embodiment are similar to page numbers). Once the human user has recognized or learned of the significance of the sequence identifier(s), no further specialized knowledge is required.
- Recipient B may also be assisted in understanding that a text message purporting to be from Sender A but that is lacking either the correct next sequence marker 30 or any sequence marker at all may be a phishing or fraud attempt and should be considered to be suspicious and worthy of further investigation. This assistance could come if some combination of text message application 18, data source 20 (as a database or an accessible message history) and process 2 alerted Recipient B if the next sequential marker 30 that was received as part of text message 22 does not match the expected sequential identifier; that is, if the sequence is out of order.
- Text message application 18 interoperating with other components, could, for example, change the text message to a different colour, alert Recipient B using an on-screen message on computing device 14, or otherwise provide a notification to Recipient B that a message should be treated as a suspicious message or that a message in the sequence has not been received and is missing.
- the cellular network 37 may insert the next sequence marker 30 if no sequence identifier is detected in a sender's text message, thus providing the network’s client base with the means to identify and prevent missing text messages.
- the process of the present invention could be applied to any digital message whatsoever, including any person, entity, or process(es) capable of sending digital messages and embedding the next sequence marker 30 within a user-accessible header field 36 or any other part of the message, include header fields and the body of the message.
- authenticity of data sent from a data sender to a receiver is verified and data is flagged as suspicious if the expected sequence number is not received.
- Numbering the elements in a sequence of data transmissions sent from a data provider to a data receiver can be useful for automated or manual fraud detection (by human overseers or anti-fraud algorithms), data analysis, verifying completeness and integrity of data, making sure no data elements in the sequences have been missed, and for audit purposes. Numbering individual messages in a sequence of digitally encoded coherent signals in packets of data, in data streams (i.e., a sequence of data elements transmitted or made available over time) or sets of data that are transmitted in discrete chunks or batches would be of benefit.
- sequence identifiers for other messaging systems could be generated using a database or a history of data received from a data providers.
- the sequence numbering could be stored in an attribute field or header that is transported with and forms part of the data transmission (e.g., packet identifier, data segment identifier, data point identifier, timestamp field, geodata field, subject identifier, any other field or metadata field about the data stream contents), or contained within the raw data of the data stream itself.
- data streams are telemetry and diagnostic information from connected devices (Internet of Things), email, financial transactions (including e-commerce transactions), streaming media, health records, text/SMS/MMS messages and information from social media networks.
- the present invention can be adapted to sequentially numbering the individual health records that comprise a patient’s cumulative medical file.
- doctors and other health service providers study individual records in a patient file based on their chronological presentation; however there is no easy way for the doctor to tell whether any specific record or document is missing, nor where that missing document would occur in the sequence of known health records.
- Social media networks would also benefit from using sequential numbering within social network messages (or“posts”) such as tweets in Twitter, posts in Facebook, and messages in Facebook Messenger.
- posts such as tweets in Twitter, posts in Facebook, and messages in Facebook Messenger.
- the system can be adapted to generate the sequence identifier from a database or an accessible message history and then inserting the next sequence identifier within a header field for the message or within the body of the message itself. This makes it easier to identify specific posts, can validate the authenticity of messages/posts (if they contain the correct, predicted sequence ID) and can flag a message/post as suspicious (if the correct sequence ID is not present). If a message is missing, the recipient can ask the sender to re-send the message.
Abstract
Description
Claims
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
GB2118071.6A GB2600029B (en) | 2019-05-15 | 2019-05-15 | Method of detecting incomplete electronic record sets using sequential numbering |
PCT/CA2019/050654 WO2020227803A1 (en) | 2019-05-15 | 2019-05-15 | Method of detecting incomplete electronic record sets using sequential numbering |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/CA2019/050654 WO2020227803A1 (en) | 2019-05-15 | 2019-05-15 | Method of detecting incomplete electronic record sets using sequential numbering |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2020227803A1 true WO2020227803A1 (en) | 2020-11-19 |
Family
ID=73290085
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CA2019/050654 WO2020227803A1 (en) | 2019-05-15 | 2019-05-15 | Method of detecting incomplete electronic record sets using sequential numbering |
Country Status (2)
Country | Link |
---|---|
GB (1) | GB2600029B (en) |
WO (1) | WO2020227803A1 (en) |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8023973B2 (en) * | 2007-01-03 | 2011-09-20 | Motorola Solutions, Inc. | Expandable text messaging service protocol for use with a two-way radio transceiver |
US20150006894A1 (en) * | 2013-07-01 | 2015-01-01 | Infosys Limited | Method and system for secure data communication between a user device and a server |
-
2019
- 2019-05-15 WO PCT/CA2019/050654 patent/WO2020227803A1/en active Application Filing
- 2019-05-15 GB GB2118071.6A patent/GB2600029B/en active Active
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8023973B2 (en) * | 2007-01-03 | 2011-09-20 | Motorola Solutions, Inc. | Expandable text messaging service protocol for use with a two-way radio transceiver |
US20150006894A1 (en) * | 2013-07-01 | 2015-01-01 | Infosys Limited | Method and system for secure data communication between a user device and a server |
Also Published As
Publication number | Publication date |
---|---|
GB2600029B (en) | 2023-02-22 |
GB202118071D0 (en) | 2022-01-26 |
GB2600029A (en) | 2022-04-20 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US9819634B2 (en) | Organizing messages in a messaging system using social network information | |
US20190281004A1 (en) | System and method for detecting confidential information emails | |
CN108564339B (en) | Account management method, device, terminal equipment and storage medium | |
US8683311B2 (en) | Generating structured data objects from unstructured web pages | |
JP2020511059A (en) | Information authentication method and system | |
US20170104785A1 (en) | Generating highly realistic decoy email and documents | |
US20130013927A1 (en) | Automated Entity Verification | |
CN106909811B (en) | Method and device for processing user identification | |
CN112714406B (en) | Method, device and equipment for realizing 5G message conversion | |
CN107943873B (en) | Knowledge graph establishing method, knowledge graph establishing device, computer equipment and storage medium | |
US20210258271A1 (en) | System and methods for integrating social network information | |
US20220029787A1 (en) | Citation and Attribution Management Methods and Systems | |
US11431749B2 (en) | Method and computing device for generating indication of malicious web resources | |
US20150213460A1 (en) | Continuing-education certificate validation | |
WO2017016384A1 (en) | Short message processing method, information processing method and device, mobile terminal and storage medium | |
US20190362442A1 (en) | System and method for prediction of email addresses of certain individuals and verification thereof | |
CN111078737A (en) | Commonality analysis method and device, data processing equipment and readable storage medium | |
US20180033110A1 (en) | Apparatus, method and system to verify meta data of a person | |
CN103685254A (en) | Common account information safety detecting method and server | |
CN107360331B (en) | Short message display method | |
WO2018145637A1 (en) | Method and device for recording web browsing behavior, and user terminal | |
US20230262040A1 (en) | Method of Detecting Incomplete Electronic Record Sets using Sequential Numbering | |
WO2020227803A1 (en) | Method of detecting incomplete electronic record sets using sequential numbering | |
KR102531661B1 (en) | System for providing phishing warning service using contents based blocking | |
US20230412534A1 (en) | Method of Detecting Incomplete Instant Messaging Record Sets using Sequential Numbering |
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: 19928482 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
ENP | Entry into the national phase |
Ref document number: 202118071 Country of ref document: GB Kind code of ref document: A Free format text: PCT FILING DATE = 20190515 |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 19928482 Country of ref document: EP Kind code of ref document: A1 |