Data service tracker module for a communication system and method for determining a set of data couplings

By using the data service tracking module in the avionics system to identify and record data coupling between transaction sources and transaction destinations, the problem of unknown data coupling relationship in the system is solved, the reliability and security of data access are realized, and the system is improved Operational efficiency.

CN113992455BActive Publication Date: 2024-12-06GE AVIATION SYSTEMS LLC
View PDF 7 Cites 0 Cited by

Patent Information

Application Number
CN202110779550.8
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Priority Date
2020-07-09
Filing Date
2021-07-09
Publication Date
2024-12-06
Estimated Expiration
2041-07-09

AI Technical Summary

Technical Problem

In avionics systems, it is difficult to determine and monitor data coupling relationships, resulting in system troubleshooting and development delays, and failure to effectively understand the existence of data objects, affecting the normal operation of the system.

Method used

The data service tracking module is adopted to receive and identify transaction communication data through a communication mechanism, establish and record data coupling between transaction sources and transaction destinations, and ensure the authorization and correctness of access.

Benefits of technology

It realizes the identification and recording of data coupling during real-time operations, ensures the correctness and security of data access, reduces the difficulty of troubleshooting and development, and improves the reliability and efficiency of the system.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN113992455B_ABST
    Figure CN113992455B_ABST
Patent Text Reader

Abstract

A data service tracking module and a method for determining a set of data couplings in a communication system include receiving transaction communications from a communication mechanism, the transaction communications defining access between a transaction source and a transaction destination, and recording transaction communications data defining the data couplings to define a set of data couplings authorized for transaction communications in the communication system.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present disclosure relates to a method and apparatus for determining a set of data couplings between a communication transaction pair, and more particularly, to a method and apparatus for determining a set of data couplings in response to a communication transaction. Background Art

[0002] For contemporary aircraft, the avionics "platform" consists of various components such as sensors, sensor data concentrators, data communication networks, RF sensors and communication devices, computing elements, effectors, and graphical displays. These components must share information with each other through data communication networks. In these systems, data is sampled, published, and transferred between publishers (such as data writers) and subscribers (such as data subscribers). Summary of the invention

[0003] In one aspect, the present disclosure relates to a data service tracking module for a communication system, comprising: an interface having a communication mechanism, the interface being operable to receive transaction communication data between a transaction source and a transaction destination; and a controller module, the controller module being configured to receive the transaction communication data, identify transaction communication aspects of the transaction communication data, and establish a set of data couplings for the communication system, the transaction communication aspects including at least a transaction source and a transaction destination, each data coupling defining a transaction source and a transaction destination.

[0004] On the other hand, the present disclosure relates to a communication system, including: a shared memory, the shared memory defines at least one data storage; a process, the process accesses at least one data storage through a communication mechanism; a data service tracker module, the data service tracker module is communicatively connected to the communication mechanism and is configured to identify access between at least one data storage and the process through the communication mechanism, and record transaction communication data related to the access to establish a set of data coupling between the shared memory and the process, the transaction communication data at least including the access initiator and the access type.

[0005] On the other hand, the present disclosure relates to a method for determining a set of data couplings in a communication system, the method comprising: receiving, by a data service tracker module, transaction communications in real time from a communication mechanism, the transaction communications defining access between a transaction source and a transaction destination; identifying, by the data service tracker module, aspects of the transaction communications to define transaction communications data, the transaction communications data defining data couplings between the transaction source and the transaction destination; and recording, by the data service tracker module, the transaction communications data defining the data couplings to define a set of data couplings authorized for transaction communications in the communication system.

[0006] These and other features, aspects and advantages of the present disclosure will become better understood with reference to the following description and appended claims.The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate various aspects of the present disclosure and, together with the description, serve to explain the principles of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0007] This specification sets forth a complete and disclosed content of the specification for one of ordinary skill in the art, including the best mode thereof, with reference to the accompanying drawings, in which:

[0008] Figure 1 is a schematic top view of an aircraft and a communication network according to various aspects described herein.

[0009] Figure 2 is a schematic diagram of a communication system having a set of processes and a shared memory according to various aspects described herein.

[0010] Figure 3 is a schematic diagram of communications within a system having a set of processes and shared memory in accordance with various aspects described herein.

[0011] Figure 4 is an example flow chart illustrating a method of determining a set of data couplings according to various aspects described herein. DETAILED DESCRIPTION

[0012] Aspects of the present disclosure are illustrated in the context of an aircraft having a data network that interconnects a common or shared memory that is accessible to multiple sensors, systems, and components of the aircraft. However, aspects of the present disclosure can be implemented in any environment, including in the context of a single system, partition, operational component, line replaceable unit (LRU), etc., using readers and writers that access or store data through a common or shared memory. As used herein, terms like "reader," "writer," or "client" can represent a remote relationship with a shared memory or data store (e.g., another separate entity), while a "server" can represent a similar relationship with a shared memory or data store. In addition, a "reader" entity of a shared memory can represent an entity that has "access" to the shared memory data to read, view, or otherwise receive data from the shared memory data store. In contrast to a "reader," a "writer" entity may include availability or authorization to submit changes to a memory location, which is the storage or overwriting of data, values, commands, instructions, or any other data, element, or identifier to a memory location, regardless of what function the data, element, or identifier performs, and regardless of the functionality or implementation of the environment, device, system, or method. In one non-limiting example, authorization to edit data for a writer entity may be limited to a specific subset of shared memory. In another non-limiting example, a single entity may simultaneously have "reader" or "read" access to a first subset of shared memory data, and "writer" or "write" access to a second subset of shared memory data. In another non-limiting example, a single entity may have overlapping "read" or "write" access to shared memory data.

[0013] As used herein, a "regulated" system is a system that has restricted access, such as write access to data or values ​​of the system, whereby only approved or authorized entities, parties, functions, etc., are able or otherwise permitted to access the regulated or restricted elements. In one non-limiting example, only a single authorized function may have write access to a particular data element.

[0014] Although a "set" of various elements will be described, it will be understood that a "set" may include any number of corresponding elements, including only one element. In addition, as used herein, although a sensor may be described as "sensing" or "measuring" a corresponding value, sensing or measuring may include determining a value indicative of or associated with the corresponding value, rather than directly sensing or measuring the value itself. The sensed or measured value may be further provided to additional components. For example, the value may be provided to a controller module or processor, and the controller module or processor may process the value to determine a representative value or an electrical characteristic representing the value.

[0015] Connection references (e.g., attachment, connection, connection and combination) should be interpreted broadly and may include intermediate members between element sets and relative movement between elements, unless otherwise specified. In some communication instances, connection references may be interpreted as describing entities or elements of communication connections, including through intermediate communications or communication media. Communication instances may include, but are not limited to, software module interactions, read and write access to memory data, etc. Therefore, connection references do not necessarily infer that two elements are directly connected and have a fixed relationship with each other. In a non-limiting example, the connection or disconnection can be selectively configured to provide, enable, disable, etc., electrical connections between corresponding elements. Non-limiting example distribution bus connection or disconnection can be enabled or operated by switches, bus connection logic, or any other connector that enables or disables the power-on of electrical loads downstream of the bus. In addition, as used herein, "electrical connection" or "electrical connection" may include wired or wireless connections. The exemplary drawings are for illustration purposes only, and the sizes, positions, orders, and relative sizes reflected in the drawings may vary.

[0016] In addition, as used herein, a "controller" or "controller module" may include a component configured or adapted to provide instructions, control, operation, or any form of communication for an operable component to achieve its operation. The controller module may include any known processor, microcontroller, or logic device, including, but not limited to: a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), a full authority digital engine control (FADEC), a proportional controller (P), a proportional integral controller (PI), a proportional differential controller (PD), a proportional integral differential controller (PID controller), a hardware accelerated logic controller (e.g., for encoding, decoding, transcoding, etc.), etc., or a combination thereof. The controller module of the non-limiting example may be configured or adapted to run, operate, or otherwise execute program code to achieve an operation or functional result, including performing various methods, functions, processing tasks, calculations, comparisons, sensing or measurement values, etc., to enable or achieve the technical operations or operations described herein. The operation or functional result may be based on one or more inputs, stored data values, sensed or measured values, true or false indications, etc. Although "program code" is described, non-limiting examples of operable or executable instruction sets may include routines, programs, objects, components, data structures, algorithms, etc., which have the technical effect of performing a particular task or implementing a particular abstract data type. In another non-limiting example, the controller module may also include a processor-accessible data storage component, including memory, whether transient, volatile or non-transient, or non-volatile memory.

[0017] Other non-limiting examples of memory may include random access memory (RAM), read-only memory (ROM), flash memory, or one or more different types of portable electronic memory, such as optical disks, DVDs, CD-ROMs, flash drives, universal serial bus (USB) drives, etc., or any suitable combination of these types of memory. In one example, the program code may be stored in a machine-readable format accessible to the processor in the memory. In addition, the memory may store various data, data types, sensed or measured data values, inputs, generated or processed data, etc. accessible to the processor, providing instructions, controls or operations to achieve the functions or operational results described herein. In another non-limiting example, the control module may include comparing a first value with a second value, and operating or controlling the operation of an additional component based on satisfying the comparison. For example, when a sensed, measured or provided value is compared with another value (including a stored or predetermined value), the satisfaction of the comparison used herein may result in an action, function or operation that can be controlled by the controller module. As used, the term "satisfy" or "satisfactory" comparison refers to a first value satisfying a second value, such as being equal to or less than the second value, or within a value range of the second value. It will be appreciated that such a determination may be readily altered to be satisfied by a positive / negative comparison or a true / false comparison.Example comparisons may include comparing a sensed or measured value to a threshold or threshold range.

[0018] As used herein, a "data store" may include a data value stored in a memory, where the data value is only accessible for write access by one or more functions, programs, processes, entities, etc. ("writers"). Write access to a data store may be controlled or otherwise regulated by a digital security mechanism understood by those skilled in the art. Although only a limited subset of writers have write access to a data store, a data store may have or include multiple functions, programs, processes, or entities that have read access to read, view, or otherwise receive data in a one-way relationship. In contrast to a data store, a "data store queue" may include a data value or set of data values ​​stored in a memory, where the data value is accessed for write access by a combination of one or more functions, programs, entities, etc. Write access to a data store queue may be controlled or otherwise regulated by a digital security mechanism understood by those skilled in the art. In addition, a data store queue may include only a single function, program, or entity that can read, view, or otherwise receive data in a one-way relationship. In a non-limiting example, such a read operation may be "one-time" or destructive (e.g., deleting data after the access operation).

[0019] Reference will now be made in detail to various aspects of the disclosure, one or more of which are non-limiting examples of which are illustrated in the figures. Each example is provided in an explanatory, disclosed manner, rather than as a limitation to the disclosure. In fact, it will be apparent to those skilled in the art that various modifications and variations may be made to the disclosure without departing from the scope or spirit of the disclosure. Therefore, it is intended that the disclosure be intended to encompass such modifications and variations within the scope of the appended claims and their equivalents.

[0020] Although example aspects of the present disclosure are discussed with reference to avionics systems, the subject matter described herein may be used with or applied to internal data of other systems, vehicles, machines, industrial or mechanical assets or components without departing from the scope of the present disclosure.

[0021] The exemplary drawings are for illustration purposes only, and the dimensions, positions, orders, and relative sizes reflected in the drawings may vary.

[0022] Reference now Figure 1 , shows an example aircraft 10 having a fuselage and at least one turbine engine, shown as a left engine system 12 and a right engine system 14. The left engine system 12 and the right engine system 14 may be substantially identical. Although turbine engines 12, 14 are illustrated, the aircraft 10 may include fewer or more engine systems, or alternative propulsion engine systems, such as propeller-based engines.

[0023] The aircraft 10 is shown to further include a plurality of sensors, systems and components, collectively referred to as line replaceable units (LRUs) 16, 18, and at least one server 20 or computing unit, shown as two flight management systems, or flight control computers, located proximate to each other near the nose of the aircraft 10. The at least one server 20 may further include memory.

[0024] The LRUs 16, 18 and server 20 may be communicatively interconnected via transmission or communication lines, such as a communication network 22, that define a data communication mechanism through at least a portion of the aircraft 10. Additional LRUs 16, 18 may be included. Although server 20 is described, various aspects of the present disclosure may include any computing system, flight computer, or display system that displays data from multiple systems.

[0025] The memory of the server 20 may include random access memory (RAM), flash memory, or one or more different types of portable electronic memory, or any suitable combination of these types of memory. The LRU 16, 18 or server 20 may be operably coupled to the memory so that the LRU 16, 18 or server 20 or any computer program or process thereon may access at least a portion of the memory (e.g., "shared memory").

[0026] Figure 1 The aircraft 10 shown in the figure is only a schematic diagram of a non-limiting example environment of the present disclosure and is used to illustrate that multiple LRUs 16, 18 and servers 20 can be located throughout the aircraft 10. The exact location of the LRUs 16, 18 and servers 20 is not relevant to the aspects of the present disclosure. In addition, more or fewer LRUs 16, 18 or servers 20 can be included in various aspects of the present disclosure.

[0027] The communication network 22 is schematically illustrated as a bus, but may include a number of data communication connectors and interfaces, such as Ethernet or fiber optic cables, and routing or switching components to facilitate communication interconnections between the LRUs 16, 18 and the server 20. In addition, the configuration and operation of the communication network 22 may be defined by a set of general standards or regulations applicable to a particular aircraft environment. For example, the communication network 22 on the aircraft 10 may be defined by, or configured in accordance with, the ARINC 664 (A664) standard, the ARINC 429 (A429) standard, or the ARINC 653 (A653) standard.

[0028] Figure 2 A schematic diagram of a communication system 30 having a set of processes 32 and a shared memory 34 according to various aspects described herein is illustrated. Although a set of processes 32 is shown, the set of processes 32 may include independent data network entities, including but not limited to LRUs 16, 18. In addition, the set of processes 32 may include reader entities or processes, writer entities or processes, or reader and writer entities or processes (i.e., "reader / writer"). The shared memory 34 may include a set of data stores 36, each of which is designated, allocated, or otherwise used to store a specific set of data or data values. The shared memory 34 may further include a verification module 38, which is operably configured to regulate read access, write access, or a combination thereof to the set of data stores 36. Various aspects of the verification module 38 may include authorizing or otherwise verifying "authorized" access based on a predetermined authorization list or "approved" entity for specific access, cryptographically secure access (e.g., access enabled or authorized by a code, digital signature, etc.), or another mechanism understood by those skilled in the art. In contrast to an "authorized" access or transaction, an "unauthorized" access or transaction may include a transaction request that is rejected, not submitted to memory, or otherwise not authenticated by authentication module 38, and whose transaction request is not executed by communication system 30. Although shared memory 34 is shown, shared memory 34 may include independent data network entities, including but not limited to server 20.

[0029] The set of processes 32 may be communicatively coupled to a shared memory 34 of the communication system 30 via a network interface 40, including but not limited to the communication network 22. Non-limiting aspects of the network interface 40 may include a network mesh, a wired or wireless communication interface, a communication signal conductor (e.g., a transmission line of the communication network 22), a network switch, a data router or routing mechanism, and the like.

[0030] The communication system 30 is further shown to include a data service tracker module 42. The data service tracker module 42 may further include memory, shown as a first memory 44 and a second memory 46. As shown, the data service tracker module 42 may selectively be communicatively connected to at least one or both of the shared memory 34 and the network interface 40. For example, a set of processes 32 may include a first process 48 or LRU 16, 18, such as an airspeed sensor, a second process 50 or LRU 16, 18, such as an avionics flight computer, and a third process 52 or LRU 16, 18, such as a navigation component. Likewise, in a non-limiting example, the shared memory 34 may include a first data store 54, a second data store 56, and a third data store 58 representing airspeed values ​​stored at predetermined storage locations in the shared memory.

[0031] During operation of the communication system 30, the aircraft 10, etc., the first process 48 or the airspeed sensor may sense or measure the airspeed. In response to sensing the airspeed, the first process 48 may be controllably operated to transmit, transfer, or otherwise communicate the airspeed or a value representative of the airspeed to a predetermined memory storage location of the shared memory 34, such as the first data store 54, for storing the sensed airspeed value. The sensed airspeed value may be communicated to the shared memory via the network interface 40 or the communication network 22, wherein, for example, the verification module 38 ensures, approves, or otherwise verifies that the first process 48 is authorized to write or submit the sensed airspeed value to the first data store 54. In another non-limiting example, the verification module 38 may be communicatively coupled to the data service tracker module 42, such as via an interface, and may determine whether the desired transaction communication is determined to be authorized or unauthorized, and may report the determination to the data service tracker module 42.

[0032] In another example of the communication system 30, a second process 50, such as an avionics flight computer, may read, request, or otherwise require a sensed airspeed value stored in the first data store 54. For example, the second process 50 may actively request read access to the data stored in the first data store 54, and the second process 50's read access to the shared memory 34 may be authenticated or otherwise confirmed by the authentication module 38. In this case, the request and the resulting communication of the data stored in the first data store 54 may be communicated from or to the second process 50 via the network interface 40 or the communication network 22.

[0033] In another non-limiting example, the second process 50 may alternatively or additionally receive data stored in the first data store 54 via silent or "triggerless" communication, such as scheduled based communication, periodic transmission, etc. In this sense, the second process 50 may still receive access to the data of the first data store 54, such as read access, but without having to make a "request" for the data. In addition, aspects of the present disclosure may be included in which the second process 50 may be further enabled or authorized to return a data value related to airspeed (i.e., a second data value) or a derivative thereof, and save the second data value to the first data store 54 or another data store 56, 58, as described herein, based on an authorized storage value. In this sense, the second process 50 may be adapted or configured for read access and write access to the same, or different, data stores 54, 56, 58 of the shared memory 34.

[0034] Aspects of the communication system 30 may be included wherein a data service tracker module 42 is configured, adapted, or otherwise operably enabled to identify, track, manage, or correlate connections, communications, and data accesses between entities accessing the shared memory 34, including, but not limited to, a set of processes 32. For example, the data service tracker module 42 may be communicatively coupled to either or both of the network interface 40 or the shared memory 34. When a communication, request, demand, or transaction to access (e.g., read or write) the shared memory 34 is communicated, the data service tracker module 42 may receive, record, or otherwise log aspects of the communication.

[0035] Aspects of transactional communications may further include identifying aspects of its data, including but not limited to a sending source or transaction source (e.g., one of a group of processes 32, or in some cases, a shared memory 34, if a data store data is sent to the group of processes 32), a destination receiver or transaction destination (e.g., a shared memory 34, or a specific shared memory 34 or server 20 in a group of shared memories 34 or servers 20, or in some cases, a group of processes 32), or even a specific memory being accessed (e.g., which one or more of a group of data stores 36). These aspects of transactional communications may include, but are not limited to, transactional communication data, or data related to transactional communications itself. The data service tracker module 42 may be adapted or configured to identify aspects of transactional communications by receiving and interpreting, utilizing, parsing, or otherwise identifying sub-portions of the communication itself, such as network addresses, data header information, frame information, payload information, etc. In another non-limiting example, the data service tracker module 42 may be adapted or configured to further identify time-based aspects of transactional communications, such as timestamps, etc. In one non-limiting example, the data service tracker module 42 may be adapted or configured to perform the actions described herein via a controller module (not shown). This example may include origin timing aspects, destination timing aspects, response timing aspects, or combinations thereof. Non-limiting aspects of timing, such as timestamps, may be based on the transaction communication itself (e.g., timestamps in the communication data header), or based on an independent clock resident in or otherwise derived from the data service tracker module 42. In this non-limiting example, the set of data couplings may further include timestamps for the transaction communication data.

[0036] In one non-limiting aspect, at least a portion of the transaction communications may be received through an optional connection to the network interface 40, such that each transaction communication that passes through the network interface 40 may be received by the data service tracker module 42. In another non-limiting aspect, at least a portion of the transaction communications may be received through an optional connection to the shared memory 34, for example, through an interface that identifies or otherwise communicates read and write transactions to the shared memory 34 or its data stores 54, 56, 58. In one example, if or when the verification module 38 authorizes or verifies transaction access, the verification module 38 may be utilized to identify or otherwise communicate the read and write transactions. In another non-limiting aspect of the present disclosure, the data service tracker module 42 is optionally communicatively connected to both the shared memory 34 and the network interface 40, and receives transaction communications aspects from each other.

[0037] The data service tracker module 42, in response to receiving a set of transaction communications, can in turn establish a set of data couplings of the communication system based on the set of transaction communications. The set of data couplings can identify known or determined connections between a sending source and a receiving source, and can be further stored in one of the memories 44, 46 of the data service tracker module 42. As explained, the data source can be an originating requestor of a data store 36 access request, such as one of a set of processes 32, a shared memory 34, a verification module 38, etc. Similarly, the receiving source can be a destination to receive a data store 36 access request, such as one of a set of processes 32, a shared memory 34, a verification module 38, or the corresponding data store 36 itself. In this sense, the data service tracker module 42 can establish a set of data couplings, tables, databases, etc., defining a set of known or valid data access interactions. In a non-limiting example, the set of data couplings can include at least recording a transaction source and a transaction destination of the transaction communication.

[0038] In one non-limiting example based on the transactions previously described, the data service tracker module 42 may record, identify, store, or otherwise generate a data coupling entry defining an association between the first process 48 and the first data store 54. The association may include timestamps or timing aspects of transactions or transaction communications during operation of the communication system 30, including, but not limited to: access by the first process 48 to the first data store 54 includes a write access; whether the access is verified by the verification module 38; whether the access or transaction is successfully completed, etc., or a combination thereof. In another non-limiting example aspect, the data coupling may further include data representing the data coupling, access, etc., including, but not limited to, coupling status (e.g., active or inactive), cryptographic hashes representing one or more data couplings or sub-portions of a coupling, etc.

[0039] Similarly, in another non-limiting example based on the transactions previously described, the data service tracker module 42 may record, identify, store, or otherwise generate data coupling entries that define the second process 50 and the first data store 54 as associated with a read access, the second process 50 as associated with the first data store 54 (or another data store 56, 58) by a write access, and so on. In this example, a single data coupling entry in the memory 44, 46 representing the association between the first data store 54 and the second process 50 may include the coupling of the read access and the write access. In another example, a unique data coupling entry in the memory 44, 46 may represent a single association between the first data store 54 and the second process 50, such as a first entry representing a read access by the second process 50 and a second entry representing a write access by the second process 50. In another non-limiting example, transaction communications originated between the first data storage 54 to the second process 50 by the shared memory 34 or the verification module 38, etc. may further include separate or unique data coupling entries in the memories 44, 46 of the data service tracker module 42 because the origin or destination recipient is opposite compared to the access transaction originated for the second process 50.

[0040] Thus, aspects of the present disclosure may be included where the communication system 30 includes a data service tracker module 42 that can generate, establish, identify, log, or otherwise record a set of data couplings based on access transactions occurring through the communication system 30. In this sense, non-limiting aspects of the present disclosure may be used, included, or otherwise utilized to generate or establish a list of entities that request access, verify access, publish data, subscribe to data, or otherwise interact with data stored in the shared memory 34. This list of entities that interact with data stored in the shared memory 34 may be further utilized, for example, to verify communication system operation, ensure that access to the shared memory 34 is operating as expected or designed, identify possible errors in accessing or attempting to access shared memory components, etc. In another non-limiting example, a set of data coupling entries or a list of data coupling entries may be further utilized to recreate or demonstrate an ordered list of shared memory 34 accesses, for example, through the timing aspects of the data couplings, as described herein.

[0041] In some communication systems 30, including those in avionics systems or aircraft, it may be difficult to discern which entities, processes, etc., reside on or as nodes of the communication system 30 and have or lack memory access to the shared memory 34. During testing, prototyping, or in-situ operation of the communication system 30, it may be further difficult to ensure or monitor shared memory 34 access. Technical effects of aspects of the present disclosure may include providing or enabling a data service tracker module 42 to identify and record data couplings between endpoints, as described herein. Additionally, technical effects of aspects of the present disclosure may further include operating the data service tracker module 42 during real-time or run-time of the communication system to establish or generate a set of data coupling entries when accessing the shared memory 34.

[0042] Non-limiting aspects of the present disclosure may be included where, for example, different data coupling entries, or different portions of a single data coupling entry may be stored in one or more memory 44, 46 portions of the data service tracker module 42. In another non-limiting example, the data coupling entries may be further searchable to determine or verify programming, authorized access, timing windows, or source or destination entries through any of the above-described recorded transaction communication aspects. In another non-limiting example, a connection between endpoints may be established, tracked, recorded, etc. only after a specific event (e.g., a specific sequence of events) occurs. For example, in one non-limiting example, after an ordered tracking of write accesses is practiced by a transaction source, the coupling may be tracked and then a read access is performed by the transaction source or transaction destination. Additional ordered events or sequences of events are envisioned to establish the coupling.

[0043] Figure 3 Another communication system 130 according to another aspect of the present disclosure is illustrated. Communication system 130 is similar to communication system 30; therefore, like parts will be identified by like numerals increased by 100, and it will be understood that the description of like parts of communication system 30 applies to communication system 130 unless otherwise specified. One difference is that Figure 3 The communication system 130 may include communications within the containment system 160, such as a single computer, operating system, node, system partition, etc. In contrast, the communication system 30 includes independent data network entities, as described.

[0044] As shown, the communication system 130 may include a shared memory 134, a set of data stores 136, 154, 156, 158, and an authentication module 138, similar to the components previously described. One difference is that the components 134, 136, 138, 154, 156, 158 are contained in, stored in, or otherwise become sub-components of the containment system 160, rather than another network node, such as the server 20. In a non-limiting example, this may include aspects where the shared memory is only accessed within the containment system 160. The communication system 130 is also shown to include a set of processes 132, 148, 150, 152, which may be processes 132, 148, 150, 152 utilized only by the contained system 160, for example. In a non-limiting example, aspects of the set of processes 132, 148, 150, 152, shared memory 134 (or subcomponents 136, 138, 154, 156, 158 thereof) may be operably enabled via a controller module 152 having a processor 154 and a memory 156 as described herein for executing or otherwise operably enabling access to the set of processes 132, shared memory 134, or a subset thereof.

[0045] The communication system 130 further includes a data service tracker module 142, and may further include memory, including a first memory 144 and a second memory 146 as shown. The data service tracker module 142 may be selectively communicatively connected to at least one or both of the shared memory 134, the set of processes 132, or a combination or subset thereof. For example, the set of processes 132 may be operably connected to the shared memory 134 through a communication system 130 or containment system 160 mechanism to achieve communication, including but not limited to an application programmable interface (API), a system call, a programming library call, etc., collectively referred to as a communication mechanism 122. In non-limiting aspects of the present disclosure, the data service tracker module 142 may be enabled or operably adapted to notice, detect, view, record, track, or otherwise determine when the communication mechanism 122 transmits, transfers, or otherwise communicates a shared memory 134 transaction utilized within the containment system 160, as described herein. This detection is schematically illustrated by a dotted loop 162, including the communication mechanism 122 between the set of processes 132 and the shared memory 134.

[0046] As described herein, during operation, the data service tracker module 142 may be adapted, configured, or operatively enabled to identify, track, manage, or correlate connections, communications, and data accesses between entities accessing the shared memory 134, including, but not limited to, a set of processes 132. When a communication, request, demand, or transaction to access (e.g., read or write) the shared memory 134 is communicated via the communication mechanism 122, the data service tracker module 142 may receive, record, or otherwise log aspects of the transactional communication, e.g., based on the authentication module 138, triggerless communication, etc. Aspects of the transactional communication may further include identifying aspects as described herein, and may further establish a set of data couplings based on a set of transactional communications in turn, as described herein.

[0047] Thus, aspects of the present disclosure may be included where the communication system 130 includes a data service tracker module 142 that can generate, establish, identify, log, or otherwise record a set of data couplings based on access transactions occurring through the communication system 130. In this sense, non-limiting aspects of the present disclosure may be used, included, or otherwise utilized to generate or establish a list of entities that request access, verify access, publish data, subscribe to data, or otherwise interact with data stored in the shared memory 134. This list of entities that interact with data stored in the shared memory 134 may be further utilized, for example, to verify communication system operation, ensure that access to the shared memory 134 is operating as expected or designed, identify possible errors in accessing or attempting to access shared memory components, etc. In another non-limiting example, a set of data coupling entries or a list of data coupling entries may be further utilized to recreate or demonstrate an ordered list of shared memory 134 accesses, for example, through the timing aspects of the data couplings, as described herein.

[0048] Figure 4 A flow chart is shown demonstrating a method 200 of determining a set of data couplings in accordance with various aspects described herein. The method 200 begins at 210 with receiving a data transaction communication by the data service tracker module 42, 142. The method 200 continues at 220 with identifying aspects of the data coupling by the data service tracker module 42, 142. As described herein, the identification of aspects of the data coupling may include source information, destination information, authentication information, etc. The method 200 then continues by recording aspects of the data coupling in the memory 44, 46, 144, 146, for example, to establish or define a set of data couplings describing, for example, publish-subscriber data coupling pairs, authorized readers, authorized writers, and the like.

[0049] The described order is for illustrative purposes only and is not meant to limit method 200 in any way, as it will be appreciated that the various parts of the method may be performed in a different logical order, may include additional or intermediate parts, or the described parts of the method may be divided into multiple parts, or the described parts of the method may be omitted without affecting the described method.

[0050] In addition to the aspects and configurations shown in the above figures, the present disclosure also contemplates many other possible aspects and configurations. For example, non-limiting aspects of the present disclosure may be included in which the data service tracking module 42, 142 can be selectively enabled or disabled as needed. For example, the data service tracking module 42, 142 can be enabled during testing, development, etc., and then can be disabled during field production or installation of the communication system 30, 130. In another non-limiting example, the data service tracking module 42, 142 can be selectively enabled during regression testing, upgrade testing, or failure analysis of the field communication system 30, 130, and then disabled again at a later time.

[0051] Aspects disclosed herein provide a communication system for defining a set of data couplings by a data service tracker module 42, 142. A technical effect is that the above aspects are capable of defining or generating a set of data coupling pairs, data, etc., defining communication transactions between a first entity and a second entity, component, etc. An advantage that can be achieved in the above aspects is that the above enables a defined set of data coupling pairs, enabling the definition and awareness of all data coupling pairs of the communication system 30, 130, developed or defined by the operation of the communication system 30, 130, without requiring the communication system 30, 130 to have knowledge or defined knowledge, or predetermined knowledge of authorized data couplings. Utilizing aspects of the present disclosure, the coupling status of the identified or defined list of data coupling pairs can then be tracked, for example, to ensure correct or intended operation of the data coupling pairs, including whether the coupling status between the pairs has been practiced or not practiced, data coupling tracking, checking time stamp transactions, etc. In addition, these aspects can be utilized during the design, prototyping, and verification of the communication system 30, 130, including comparing a set of data couplings to expected communications or transaction communications, as expected or designed.

[0052] Another advantage of the aspects described herein can include solving the following problems, where data couplings are often unknown. For example, not knowing what data objects exist, not knowing what data objects exist, partially knowing what data objects exist, or in environments where it is difficult to know what data objects exist, not knowing what data objects exist completely, or having delays or inefficiencies in determining the knowledge of what data objects exist, or not having a mechanism to monitor memory accesses (e.g., reads or writes), can cause delays in troubleshooting, coding, development, or fault analysis of system implementations. In addition, by developing a set of data couplings during real-time operation of the communication system 30, 130, low-overhead and low-effort tracking and verification of memory accesses can be accomplished or achieved.

[0053] To the extent not already described, the various features and configurations of the various aspects may be used in combination with one another as desired. The fact that a feature is not illustrated in all aspects does not mean that it cannot be illustrated, but rather for the sake of brevity of description. Thus, various features of different aspects may be mixed and matched as desired to form new aspects, whether or not the new aspects are explicitly described. Any combination or permutation of the features described herein is included in the present disclosure.

[0054] This written description uses examples to disclose aspects of the disclosure, including the best mode, and also to enable those skilled in the art to practice aspects of the disclosure, including making and using any device or system and performing any combined methods. The patentable scope of the invention is defined by the claims, and may include other examples that occur to those skilled in the art. Such other examples are intended to be within the scope of the claims if they have structural elements that do not differ from the literal language of the claims, or if they include equivalent structural elements that do not differ significantly from the literal language of the claims.

[0055] Further content of the present invention is provided by the subject matter of the following clauses.

[0056] A data service tracker module for a communication system, comprising: an interface having a communication mechanism, the interface being operable to receive transaction communication data between a transaction source and a transaction destination; and a controller module, the controller module being configured to receive the transaction communication data, identify transaction communication aspects of the transaction communication data, and establish a set of data couplings for the communication system, the transaction communication aspects including at least a transaction source and a transaction destination, each data coupling defining a transaction source and a transaction destination.

[0057] The data service tracker module according to any preceding clause, wherein the controller module is further configured to identify the transaction communication aspects by interpreting or parsing the transaction communication data.

[0058] The data service tracker module according to any of the preceding clauses, wherein the controller module is configured to establish a set of data couplings using at least one of a network address, communication transaction data header information, communication transaction data frame information, or communication transaction payload information.

[0059] The data service tracker module of any preceding clause, wherein the controller module is further configured to identify whether the transaction communication aspect comprises one of an authorized transaction communication or an unauthorized transaction communication.

[0060] The data service tracker module according to any of the preceding clauses, further comprising a second interface having a verification module configured to determine whether the transaction communication data is an authorized transaction communication or an unauthorized transaction communication and communicate the determination to the controller module.

[0061] The data service tracker module according to any preceding clause, wherein the controller module is further configured to time stamp the transaction communication data and establish a set of data couplings, each data coupling further defining a time stamp for the transaction communication data.

[0062] The data service tracker module according to any preceding clause, wherein the communication mechanism is a network interface interconnecting a set of transaction sources with a set of transaction destinations.

[0063] The data service tracker module according to any of the preceding clauses, wherein the communication mechanism is one of an application programmable interface, a system call or a programming library call.

[0064] A communication system includes: a shared memory, the shared memory defines at least one data storage; a process, the process accesses the at least one data storage through a communication mechanism; a data service tracker module, the data service tracker module is communicatively connected to the communication mechanism and is configured to identify access between at least one data storage and the process through the communication mechanism, and record transaction communication data related to the access to establish a set of data coupling between the shared memory and the process, the transaction communication data at least including the access initiator and the access type.

[0065] A communication system according to any of the preceding clauses, further comprising a set of processes and a set of data stores, each of the set of processes accessing at least one of the set of data stores, and wherein the data service tracker module is configured to establish a set of data couplings by identifying and recording transaction communication data associated with each access between the set of processes and the set of data stores.

[0066] The communication system according to any of the preceding clauses, the access type can include one of read access, write access, or read and write access.

[0067] The communication system according to any of the preceding clauses, further comprising a verification module configured to enforce a predetermined access type for each access between at least one data store and a process.

[0068] A communication system according to any of the preceding clauses, wherein the transaction communication data comprises at least a subset of a network address, communication transaction data header information, communication transaction data frame information or communication transaction payload information.

[0069] A communication system according to any preceding clause, wherein the data service tracker module is configured to establish a set of all data couplings between shared memories and processes during runtime of the communication system without knowledge of predetermined data couplings of the communication system.

[0070] A communication system according to any preceding clause, wherein the communication mechanism is one of an application programmable interface, a system call or a programming library call.

[0071] A method for determining a set of data couplings in a communication system, the method comprising: receiving transaction communications in real time from a communication mechanism by a data service tracker module, the transaction communications defining access between a transaction source and a transaction destination; identifying aspects of the transaction communications by the data service tracker module to define transaction communications data, the transaction communications data defining data couplings between the transaction source and the transaction destination; and recording the transaction communications data defining the data couplings by the data service tracker module to define a set of data couplings authorized for transaction communications in the communication system.

[0072] A method according to any preceding clause, further comprising comparing a set of data couplings authorized for transactional communications with a predetermined set of expected data couplings authorized for transactional communications.

[0073] A method according to any preceding clause, further comprising identifying a real-time timestamp of said transaction communication and recording the timestamp in the transaction communication data.

[0074] A method according to any preceding clause, wherein the data service tracker module lacks knowledge of predetermined data couplings of the communication system, and wherein recording transactional communications data establishes in real time a set of data couplings authorized for transactional communications in the communication system.

[0075] A method according to any preceding clause, further comprising comparing a set of data couplings authorized for transactional communications with an expected set of expected data couplings authorized for transactional communications.

Claims

1. A data service tracker module for a vehicle containing a communication system, characterized in that: include: an interface having a communication mechanism operable to receive transaction communication data between a transaction source and a transaction destination, the transaction source and the transaction destination both being within the contained communication system, and wherein the transaction destination has a shared memory defining a set of data storage; and a controller module, the controller module being within the contained communication system, the controller module being configured to receive the transactional communication data, identify transactional communication aspects of the transactional communication data, and establish a set of data couplings of the contained communication system, the transactional communication aspects comprising at least the transactional source and at least one of the set of data stores of the shared memory, each data coupling defining the transactional source and the at least one of the set of data stores of the shared memory; Wherein, the controller module is further configured to enable definition and awareness of all data couplings of the accommodating communication system and track coupling states of the identified or defined set of data couplings to ensure correct or intended operation of the data coupling pairs.

2. The data service tracker module according to claim 1, characterized in that: in, The controller module is further configured to identify transaction communication aspects by interpreting or parsing the transaction communication data.

3. The data service tracker module according to claim 2, characterized in that: in, The controller module is configured to establish the set of data couplings using at least one of a network address, communication transaction data header information, communication transaction data frame information, or communication transaction payload information.

4. The data service tracker module according to claim 1 or 2, characterized in that: in, The controller module is further configured to identify whether the transaction communication aspect comprises one of an authorized transaction communication or an unauthorized transaction communication.

5. The data service tracker module according to claim 4, characterized in that: Further included is a second interface having a verification module configured to determine whether the transaction communication data is an authorized transaction communication or an unauthorized transaction communication and communicate the determination to the controller module.

6. The data service tracker module according to claim 1 or 2, characterized in that: in, The controller module is further configured to time stamp the transactional communication data and establish the set of data couplings, each data coupling further defining a time stamp of the transactional communication data.

7. The data service tracker module according to claim 1 or 2, characterized in that: in, The communication mechanism is a network interface interconnecting a set of transaction sources with a set of transaction destinations.

8. The data service tracker module according to claim 1 or 2, characterized in that: in, The communication mechanism is one of an application programmable interface, a system call, or a programming library call.

9. A communication system for a vehicle, characterized in that: include: a shared memory, the shared memory defining at least one data storage; a process accessing the at least one data store via a communication mechanism operable to receive transaction communications data between a transaction source and a transaction destination, the transaction source and the transaction destination both being within the containing communication system; a data service tracker module, the data service tracker module being communicatively connected to the communication mechanism and configured to identify accesses between the at least one data store and the process through the communication mechanism and record transaction communication data related to the accesses to establish a set of data couplings between the shared memory and the process, the transaction communication data comprising at least an access initiator and an access type; Wherein, the data service tracker module enables definition and awareness of all data couplings of the accommodating communication system and tracks coupling states of the identified or defined set of data couplings to ensure correct or intended operation of data coupling pairs.

10. The accommodating communication system according to claim 9, characterized in that: Further comprising a set of processes and a set of data stores, each of the set of processes accessing at least one of the set of data stores, and wherein the data service tracker module is configured to establish a set of data couplings by identifying and recording transaction communication data associated with each access between the set of processes and the set of data stores.

11. The accommodating communication system according to claim 9 or 10, characterized in that: in, The access type can include one of read access, write access, or read and write access.

12. The accommodative communication system according to claim 11, characterized in that: Further included is a verification module configured to enforce a predetermined access type for each access between the at least one data store and the process.

13. The accommodative communication system according to claim 9 or 10, characterized in that: in, The transaction communication data at least includes a subset of a network address, communication transaction data header information, communication transaction data frame information or communication transaction payload information.

14. The accommodative communication system according to claim 9 or 10, characterized in that: in, The data service tracker module is configured to establish a set of all data couplings between the shared memory and the process during runtime of the hosted communication system without knowledge of predetermined data couplings of the hosted communication system.

15. The accommodative communication system according to claim 9 or 10, characterized in that: in, The communication mechanism is one of an application programmable interface, a system call, or a programming library call.

16. A method for determining a set of data couplings in a resident communication system for a vehicle, characterized in that: The method comprises: receiving, by a data service tracker module, a transaction communication in real time from a communication mechanism, the transaction communication defining access between a transaction source and a transaction destination, and wherein the transaction destination has a shared memory defining a set of data stores; identifying, by the data service tracker module, aspects of the transactional communication to define transactional communication data defining a data coupling between the transactional source and at least one of the set of data stores of the shared memory; and recording, by the data service tracker module, the transactional communications data defining the data couplings to define a set of data couplings authorized for transactional communications in the accommodating communications system; wherein the data service tracker module enables definition and awareness of all data couplings of the accommodating communication system and tracks coupling states of the identified or defined set of data couplings to ensure correct or intended operation of the data coupling pairs; Wherein, the transaction source and the transaction destination are both within the accommodating communication system.

17. The method according to claim 16, characterized in that Further included is comparing the set of data couplings authorized for transactional communications with a predetermined set of expected data couplings authorized for transactional communications.

18. The method according to claim 16 or 17, characterized in that Further comprising identifying a real-time timestamp of the transaction communication and recording the timestamp in the transaction communication data.

19. The method according to claim 16 or 17, characterized in that in, The data service tracker module lacks knowledge of predetermined data couplings of the accommodating communication system, and wherein recording the transactional communication data establishes in real time the set of data couplings authorized for transactional communications in the accommodating communication system.

20. The method according to claim 16 or 17, characterized in that Further included is comparing the set of data couplings authorized for transactional communications to an expected set of expected data couplings authorized for transactional communications.

Citation Information

Patent Citations

  • Transaction based shared data operations in a multiprocessor environment

    CN102622276A

  • Management of transactional memory access requests by a cache memory

    CN104375958A

  • Tracking for affairs coincide variation of database

    CN1540513A

  • Systems and methods for context-aware network message filtering

    EP3618400A2

  • Data distribution system and method for distributing data in a vehicle

    US20120316700A1