Method and system for processing log data

The aggregation and formatting of log data from diverse platforms into a common database enable efficient analysis and monitoring of network-enabled vehicles, addressing the challenge of non-uniform formatting and enhancing system performance and issue detection.

WO2024227941A1PCT designated stage expired Publication Date: 2024-11-07CUBIC TELECOM LTD
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
PCT/EP2024/062328
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-05-03
Filing Date
2024-05-03
Publication Date
2024-11-07

AI Technical Summary

Technical Problem

The analysis of log data from multiple network-connected platforms is challenging due to non-uniform formatting, making it difficult and time-consuming to monitor and audit the performance of systems like fleets of network-enabled vehicles, which rely on multiple vendors and platforms.

Method used

A method and system that aggregate and format log data from various platforms into a common database, using a data aggregator to establish connections, format raw log data, and associate it with vehicle identifiers, enabling real-time and retrospective analysis of network activity and performance.

Benefits of technology

This approach facilitates efficient and accurate comparison and analysis of software performance across networked platforms, providing comprehensive monitoring and alerting capabilities, especially during vehicle registration and network access, thus enhancing the overall system performance and issue detection.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure EP2024062328_07112024_PF_FP_ABST
    Figure EP2024062328_07112024_PF_FP_ABST
Patent Text Reader

Abstract

Methods and systems for recording within a common database network-related activity at one or more network-enabled vehicles and / or a plurality of log-producing platforms The method comprises, by a data aggregator: establishing network connections with each of the plurality of log-producing platforms; receiving a plurality of logs produced by one or more of the log-producing platforms; determining whether the received plurality of logs are present in the common database; and if the received plurality of logs are not present in the common database, producing formatted log data from the plurality of logs and adding the formatted log data to the common database.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] Title

[0002] Method and system for processing log data

[0003] Field

[0004] The present disclosure relates to a method and system for processing log data. In particular, the present disclosure relates to a method and system for recording network activity of a plurality of network-enabled vehicles and a plurality of log-producing platforms so as to facilitate the installation and configuration of software on the network-enabled vehicles.

[0005] Background

[0006] Computer-generated records of events, known as ‘logs’, can be used to monitor and investigate the operation of software. Logs typically relate to securityrelevant or operation-relevant events e.g. user logins, file / device creations, exceptions or system errors. For example, logs can record network-related activity, that is, activity or events which result from messages sent between platforms across a network. The messages may be calls sent via the network to or from the logproducing platforms. Logs aid in the debugging of software during development and facilitate real-time and near real-time auditing of software performance after deployment in real-world environments.

[0007] The format, syntax and semantics of data within logs is often platform-, application- and / or vendor-specific. This complicates the analysis of software performance in systems which rely on a plurality of network-connected platforms to function, where logs are typically produced by a variety of platforms according to a variety of formats. The non-uniform ity of log formatting makes analysis of logs computationally difficult and time consuming. Such problems are particularly acute in systems which rely on repeated calls being made between a plurality of network- connected platforms operated by separate vendors.

[0008] A fleet of network-enabled vehicles is an example of a system which relies on a multitude of network-connected platforms to operate effectively. Each platform, including Original Equipment Manufacturer, OEM, backend servers, user equipment and other computing devices, will create, record and store its own logs independently, for example during registration of a vehicle or device with a service and / or after deployment. Reviewing the performance of the system as a whole requires the ability to comprehensively search through and analyse the logs. While practical concerns often result in logs from only one or a limited number of the constituent platforms being analysed, such limited auditing provides an incomplete view of how well the system is operating, and some problems or issues may go undetected. There exists a need for a way to efficiently and accurately audit, review and analyse the performance of software which relies on a system of networked platforms.

[0009] Summary

[0010] Accordingly, there is provided a method as defined in claim 1 . A method as defined in claim 23 is also provided. Systems configured to carry out either method are also provided.

[0011] Advantageously, the present methods and systems provide a more efficient way of comparing, reviewing and / or analysing the performance of software and / or a system of networked platforms in real time, near-real time and / or retrospectively. This addresses a technical problem of how to deploy software in a distributed network.

[0012] Further advantageously, the present methods and systems facilitate analysis of logs collected by a plurality of platforms according to a plurality of formats, and the association of logs collected by a plurality of platforms with the components of a system to which the logs relate.

[0013] Further advantageously, the present methods and systems enable configuring a vehicle or a fleet of vehicles to access a network and / or to monitor network performance in a vehicle or a fleet of vehicles,

[0014] Further advantageously, the present methods and systems enable accurate monitoring of vehicle registration at one or more platforms.

[0015] Further advantageous embodiments are provided in the dependent claims.

[0016] According to an aspect of the invention there is provided a method of recording, within a common database, network-related activity at one or more network-enabled vehicles and / or a plurality of log-producing platforms, the, or each, vehicle of the one or more network-enabled vehicles being configured for communication with each of the plurality of log-producing platforms over a network, the method comprising: establishing, by a data aggregator, network connections with each of the plurality of log-producing platforms; receiving, by the data aggregator, a plurality of logs produced by one or more of the log-producing platforms, wherein each log of the plurality of logs records network-related activity at a network-enabled vehicle and / or a log-producing platform during registration or enrolment of a respective network-enabled vehicle with a respective log-producing platform; determining, by the data aggregator, whether the received plurality of logs are present in the common database; and if the received plurality of logs are not present in the common database, producing, by the data aggregator, formatted log data from the plurality of logs and adding the formatted log data to the common database.

[0017] Preferably the formatted log data contains vehicle identification information, a time stamp, and / or location data such as vehicle location data.

[0018] Preferably the plurality of log-producing platforms comprises at least a vehicle platform and a mobile telecommunication platform.

[0019] Preferably the method comprises registering or enrolling a vehicle or a plurality of vehicles with one or more of the log-producing platforms.

[0020] Preferably the method comprises identifying, by the data aggregator, a trigger event by cross-correlating data originating from each of the log-producing platforms in the common database.

[0021] Preferably the trigger event is identification of successful registration or enrolment of one or more vehicles with one or more of the log-producing platforms and / or a network service provider.

[0022] Preferably the trigger event is identification of non-registration or enrolment of one or more vehicles with one or more of the log-producing platforms and / or a network service provider.

[0023] Preferably the method further comprises, in response to the trigger event, generating an alert. Preferably the method further comprises, in response to the trigger event, authorising the, or each, vehicle to use the mobile communication network, one or more of the log-producing platforms and / or the network service provider.

[0024] Preferably the method further comprises: analysing the formatted log data in the common database to determine whether a predetermined condition has been met; and if the predetermined condition has been met, generating a report or notification.

[0025] Preferably the predetermined condition is met when an attempt to register or enrol one or more vehicles with the mobile communication network, a network service provider and / or one or more of the log-producing platforms is unsuccessful.

[0026] Preferably the predetermined condition is met when an attempt to register or enrol a predetermined number of vehicles with the mobile communication network, a network service provider and / or one or more of the log-producing platforms is unsuccessful.

[0027] Preferably each log-producing platform produces logs having a unique format.

[0028] Preferably the, or each, log comprises raw log data.

[0029] Preferably the step of producing formatted log data comprises formatting the raw log data according to a common data format.

[0030] Preferably the method comprises associating the logs and / or formatted log data with one or more vehicles.

[0031] Preferably the method comprises associating formatted log data in the common database with one or more vehicle identifiers.

[0032] Preferably the method comprises receiving logs in bulk.

[0033] Preferably the method comprises receiving logs via a web interface.

[0034] Preferably the method comprises receiving logs from each log-producing platform in real-time.

[0035] Preferably the method comprises analysing the data in the common database in real-time or in bulk after storage.

[0036] Preferably the plurality of vehicles is a fleet of vehicles. According to another aspect of the invention there is provided a system for recording network activity of a plurality of network-enabled vehicles within a common database, the system comprising a data aggregator configured to carry out the method.

[0037] According to a further aspect of the invention there is provided a method of processing log data from one or more log-producing platforms, wherein the or each log-producing platform is configured to produce logs of events relating to network- related activity at one or more network nodes, the method comprising: receiving raw log data from the, or each, log-producing platform, wherein the raw log data comprises events relating to network traffic at one or more network nodes; producing formatted log data from the received raw log data; determining whether the formatted log data is located in a database; and if the formatted log data is not located in the database, adding the formatted log data to the database.

[0038] According to a further aspect of the invention there is provided a system for processing log data from one or more log-producing platforms, the system comprising a data aggregator configured to carry out the method.

[0039] Brief Description of the Drawings

[0040] The present application will now be described with reference to the accompanying drawings in which:

[0041] Figure 1 is a schematic view of an environment in accordance with an aspect of the present teaching.

[0042] Figure 2 is a schematic view of a selected subset of the environment of Figure 1.

[0043] Figure 3 is a schematic view of network connectivity between a plurality of devices and a plurality of log-producing platforms in accordance with an aspect of the present teaching.

[0044] Figure 4 is a schematic view of an example process flow.

[0045] Figure 5 is a schematic view of a log ingestion engine in accordance with an aspect of the present teaching. Figure 6 is a schematic view of a method in accordance with an aspect of the present teaching.

[0046] Figure 7 is a schematic view of a method in accordance with an aspect of the present teaching.

[0047] Figure 8 is a schematic view of a method in accordance with an aspect of the present teaching.

[0048] Figure 9A to 9C are schematic views of a logs analysis dashboard for use with an aspect of the present teaching.

[0049] Figures 10A and 10B are views of a user interface for use with an aspect of the present teaching.

[0050] Figure 11 is a schematic view of a method in accordance with an aspect of the present teaching.

[0051] Figure 12 is a schematic view of a method in accordance with an aspect of the present teaching.

[0052] Detailed Description

[0053] Example environment 100

[0054] Figure 1 shows an example computing architecture or system environment 100 according to an aspect of the present teaching. The environment 100 is configured for the provision of network access to one or more devices, such as network-enabled vehicles or other Internet of Things, loT, devices. For example, the environment 100 can allow a car manufacturer or other Original Equipment Manufacturer, OEM, to provision one or more of their vehicles / devices to connect to one or more communications networks. The environment 100 also enables the evaluation and monitoring of device activity in real time, near real-time and / or retrospectively.

[0055] The environment 100 may be considered as comprising a plurality of layers 110-160. Each layer includes one or more platforms which produce logs (i.e. ‘logproducing platforms’). Logs are generated to record events that take place during the execution of software in a system, and provide traces of processes in a software development cycle. A log-producing platform produces logs when events, such as user logins, file / device creations, exceptions or system errors occur in a computer system. These events may occur in the operating system or in other software. A log is generated and recorded or saved for each such event. Logs can be used to monitor and understand the operation of the system as a whole during development, to debug problems in real time and / or during an audit.

[0056] Each log-producing platform in the environment 100 produces logs which record network-related activity. By “network-related activity” it is meant activity or events that occur at a log-producing platform which result from messages sent from or to the platform via a network. Logs which record network-related activity record events which occur at the log-producing platform. Logs which record network-related activity may contain information related to sent or received messages, successful or unsuccessful execution of processes, timeouts, exceptions, etc. Such logs are useful because they can be used to monitor and understand the operation of a logproducing platform in the context of a wider networked-system as a whole. Logs which record network-related activity may be collected for the following purposes: performance monitoring; fault detection and alerting; operational management; network troubleshooting; resource optimisation; network security; intrusion detection and prevention; incident analysis; and auditing.

[0057] In an example, each log-producing platform in environment 100 produces logs having a different, and unique, format. This format may be proprietary to the specific platform. This non-uniform ity of logs makes the comparison of logs generated in different platforms, and therefore the analysis of system performance, difficult and time-consuming. Per the present teaching, the service provider 142 in the aggregator layer 140 mitigates against these problems and difficulties by aggregating and storing logs from each log-producing platform in a common database according to a common format, allowing easier and faster analysis. In this context the service provider may be considered to have the functionality of a data aggregator.

[0058] At a conceptual top level, the environment 100 comprises a brands or OEM layer 110. The brands layer 110 comprises a plurality of OEM backend platforms 112a-j corresponding to Brands 1-10, respectively. Each OEM backend platform 112 corresponds to a backend or server of a particular brand or OEM, such as a vehicle manufacturer. Each OEM backend platform 112 is able to provide digital products for delivery to vehicles or other devices associated with that manufacturer. For example, the brand 4 backend platform 112d is configured to provide streaming services and / or specific APIs developed for particular models of vehicles (cars, lorries, trucks, etc.) belonging to brand 4 for delivery to those vehicle models via a network. Each OEM backend platform 112 includes computing devices such as servers which will produce and record logs in response to the execution of processes and sending / receiving messages to other platforms and devices.

[0059] The environment 100 comprises a Telematics Control Unit / Network Access Device, TCU / NAD, layer 120. The TCU / NAD layer 120 includes a plurality of network access devices, NADs, and telematic control units, TCUs, that can be used in devices, such as vehicles, requiring network connectivity. As will be understood by those of skill in the art, NADs are modules which allow internet connections to be made between mobile devices (e.g. vehicles requiring network connectivity) and networks (e.g. mobile communication networks such as 3G, 4G or 5G networks). TCUs, similarly have functionality that will be appreciated by those of ordinary skill, and are typically equipped with General Packet Radio Service, GPRS, Universal Mobile Telecommunications Service, UMTS, and Long-Term Evolution, LTE, hardware. TCUs are typically provided as embedded systems on board a vehicle or device that can wirelessly connect that vehicle or device to cloud services, other vehicles / devices and / or external platforms via e.g. vehicle-to-everything, V2X, standards. TCUs are adapted to collect telemetry data (e.g. position, speed, engine data, etc.) from sensors and / or sub-systems within a vehicle or device and can also provide in-vehicle connectivity via Wifi and Bluetooth. Being embedded within TCUs, NADs provide network access and allow communication of relevant telemetry data.

[0060] The TCU / NAD layer 120 comprises a plurality of TCUs / NADs 122a-g which are designed, optimized and configured for particular device applications, for example vehicular applications. Each TCU / NAD 122 can connect to at least one backend platform which includes computing devices such as servers and which will produce and record logs in response to the execution of processes at a that TCU / NAD 122 and sending / receiving messages from the TCU / NAD 122 to other platforms and devices. Furthermore, each TCU / NAD 122 can also produce its own records of logs in response to such events.

[0061] The SDP / Backend layer 130 includes a number of backends 132a-c of service delivery platforms, SDPs. SDPs provide on-demand access to cloud-based services such as APIs for data analytics, device provisioning and data management. The SDP / Backend layer 130 comprises a plurality of SDP backends 132 which are designed, optimized and configured for particular device applications, for example vehicular applications. For example, the backend 1 , labelled 132a, is a cloud-based backend solution configured to manage vehicle software updates and obtain vehicle status information, etc. Each backend 132 includes computing devices such as servers which produce and record logs in response to the execution of processes and sending / receiving messages to other platforms and devices.

[0062] The aggregation layer 140 of the environment 100 allows the collection and aggregation of data from a plurality of sources, such as the platforms in the other layers of the environment 100. Services in the aggregation layer 140 have visibility of the platforms in the brand layer 110, TCU / NAD layer 120, SDP Backend layer 130, SIM / Subman layer 150 and Network Services layer 160. By accessing, collecting and aggregating the data from the plurality of layers, the aggregation layer 140 is ideally placed to facilitate analysis of the overall system performance.

[0063] The aggregation layer 140 comprises a service provider, ACSP, 142 which includes a log ingestion engine 144 and database 146. The service provider 142, in particular the log ingestion engine 144, is configured for direct communication with the log-producing platforms in the other layers of environment 100, for example via a suitable network communications interface, which may be an ingress interface. The log ingestion engine 144 is configured for direct communication with the database 146, for example via a suitable network communications interface, which may be an egress interface.

[0064] As is explained in further detail below, the components of the service provider 142 in the aggregation layer 140 allow logs produced by log-producing platforms in the other layers of the environment 100 to be received, parsed, suitably formatted, augmented with further data and stored. The aggregation layer 140 and / or the components of the aggregation layer 140 may include computing devices such as servers which will produce and record logs in response to the execution of processes and sending / receiving messages to other platforms and devices.

[0065] The SIM / Subman layer 150 comprises a plurality of subscription managers, 152a, 152b that can provide SIM provisioning. Each subscription manager or ‘Subman’ is associated with a corresponding eSIM, which enables a device to connect to a cellular network provided by a chosen mobile network operator, MNO. In vehicular applications, subscription managers allow remote provisioning of a machine-to-machine, M2M, eSIM, in a particular device such as a vehicle. This allows the device, such as a vehicle, to connect to one or more cellular networks of one or more MNOs. Each subman 152 has a data preparation component (referred to as the SM-DP 154) and a secure routing component (referred to as the SM-SR 156). Each subscription manager 152 has at least one backend platform which includes computing devices such as servers and which will produce and record logs in response to the execution of processes and sending / receiving messages to other platforms and devices.

[0066] The network services layer 160 comprises a plurality of MNOs. MNOs provide wireless communications services to devices over a geographically-limited region. To allow a device such as a vehicle to connect to the cellular network of a chosen MNO, the M2M eSIM in the vehicle must contain or download a suitable profile 162.

[0067] The devices / vehicles in the present system are pre-loaded with a telecom or ‘bootstrap’ profile 162a which allows the device / vehicle, in particular the TCU / NAD in the device / vehicle, to connect to the cellular networks of over 190 MNOs. The devices / vehicles may also be provisioned, for example remotely provisioned, with one or more further profiles 162b to allow the device / vehicle to connect to the cellular networks of a particular local MNO. Each MNO has at least one backend platform which includes computing devices such as servers and which will produce and record logs in response to the execution of processes and sending / receiving messages to other platforms and devices.

[0068] Example platform selection

[0069] Enabling network access at a device such as a vehicle requires appropriate selections to be made from one or more of the layers of the environment 100. In vehicular applications, the selection is typically performed by the brand or OEM of the vehicle. For example, a particular vehicle OEM, having a fleet of vehicles of a particular brand, may provide network access to each vehicle in the fleet using their own backend platform and choose a TCU / NAD from the TCU / NAD layer 120 for incorporation within each vehicle. A SDP from the SDP / Backend layer 130 and a subscription manager (and associated M2M eSIM) from the SIM / Subman layer 150 will also be chosen. As will be appreciated the choice of MNO from the Network Services layer 160 is likely to be selected according to the choices available in the locality where the vehicles are to be deployed, and the choice of subscription manager will often depend on the MNO most likely to be used.

[0070] An example selection for a fleet of vehicles is shown in figure 2. In this example, each vehicle is a brand 4 vehicle to be sold in the USA. The vehicle OEM uses its own brand 4 backend platform 112d, the TCU / NAD chosen is TCU 5 (labelled 122e in figures 1 and 2), backend 1 (labelled 132a in figures 1 and 2) is chosen from the SDP / backend layer 130 to provide on-demand access to cloud-based services, and subman 2 (labelled 152b in figures 1 and 2) is chosen from the Sim / Subman layer 150 to provide SIM provisioning. Each vehicle will be preloaded with a bootstrap profile 162a. Since in this example the vehicles are to be deployed in the USA, a local MNO profile 162b is also downloaded to each vehicle so that each vehicle can access the cellular network of a preferred local MNO in the USA.

[0071] Example network architecture

[0072] Figure 3 shows connectivity between a fleet of vehicles 300 and a plurality of log-producing platforms over a cellular network 310. The fleet of vehicles 300 corresponds to a plurality of vehicles 302a, each of which is provisioned with a TCU / NAD (e.g. TCU 5). Cellular network 310 facilitates communication between chosen log-producing platforms (e.g. platforms chosen in the example of figure 2 i.e. the brand 4 backend platform 112d, TCU 5, the backend 1 , subman 2 and a backend platform of an appropriate MNO), and also between the log-producing platforms and the service provider 142 in the aggregation layer 140.

[0073] The service provider (e.g. service provider 142) is configured to access and collect data (particularly logs) from the log-producing platforms in the other layers. As will be explained in further detail below, the service provider is also configured for collecting further data such as logs via a user interface 320. The log-producing platforms in each layer are computing devices such as servers, each of which includes a database containing data such as logs. Example Process Flow 400

[0074] Once appropriate selections have been made (e.g. those shown in Figure 2), in order for each vehicle 302 to be admitted to the fleet 300 and be granted full network access and access to services, appropriate registration process(es) with one or more of the chosen platforms in each layer of system 100 must be completed. For example, each vehicle 302 must be registered with service provider 142 in the aggregation layer 140 as well as with the appropriate platforms in the brand layer 110, the SDP Backend layer 130, the SIM / Subman layer 150, and the Network Services layer 160. As will be appreciated, during this process of provisioning the vehicle for network access multiple messages will be sent between log-producing platforms and a plurality of logs potentially having unique and distinct formats will be produced.

[0075] Figure 4 discloses an example process flow 400 for the registration of a vehicle 302 with an loT Ecosystem Partner 406, which may be e.g. backend 1 (labelled 132a in figure 2). The example process flow 400 begins at 410 where a call from the OEM’s Backend Gateway 402 (e.g. brand 4 backend platform 112d in figure 2) sends an Initialise Registration call to the ACSP / IOT Aggregator 404 (e.g. service provider 142 in figure 2). This call instructs the ACSP / IOT Aggregator 404 to register the vehicle 302 with the IOT Ecosystem Partner 406 (e.g. backend 1 labelled 132a in figure 2). In response, a plurality of calls are sent between the ACSP / IOT Aggregator 404 and the IOT Ecosystem Partner 406. The sending / receiving of these messages, and the successful or unsuccessful execution of the associated processes, results in the creation of one or more logs by either or both of the ACSP / IOT Aggregator 404 and the IOT Ecosystem Partner 406.

[0076] As will be appreciated, logs created by different platforms (in this case the ACSP / IOT Aggregator 404 and the IOT Ecosystem Partner 406) will typically have different formats and will be stored in separate databases, making full visibility and analysis of system performance difficult. Furthermore, there is no guarantee that the logs will be formatted to include all appropriate information relevant to the system more generally, such as the identifier of the vehicle for which the registration is taking place. Logs Ingestion Pipeline

[0077] Figure 5 discloses a service provider 142 according to an embodiment of the teaching. The service provider 142 comprises a log ingestion engine 144 and a common database 146. The log ingestion engine 144 is configured for communication with each of a plurality of log-producing platforms (e.g. the platforms shown in figure 3) and the common database 146, for example via a network 310.

[0078] The log ingestion engine 144 of the service provider 142 is configured to receive data such as logs from each of the plurality of log producing platforms and / or devices such as vehicles, for example in response to and / or during the example process flow 400. The log ingestion engine 144 is further configured to format the received logs (e.g. logs produced in response to and / or during the example process flow 400) according to a common format. It may also be configured to augment the formatted log data with additional data such as device / vehicle identifiers and time stamps. The common database 146 is configured to store the formatted logs with the additional data for later retrieval and / or analysis. As will be appreciated, the log ingestion engine 144 and common database 146 may be stored on the same or different computing devices / servers and may be local or remote from one another.

[0079] Figure 6 shows a method 600 in accordance with an embodiment of the present teaching. The method 600 may be carried out by the example service provider 142 shown in Figures 1 , 2 and 5 and / or another suitably-configured data aggregation platform. The method 600 can be used to record network activity and events at a plurality of network-enabled devices such as vehicles and / or a plurality of log-producing platforms within a common database 144.

[0080] The method 600 comprises, at step 602, establishing individual network connections with each of a plurality of log-producing platforms. For example the service provider 142 shown in figure 2 may establish network connections with brand 4 backend platform 112d, TCU 5 (present in a vehicle), backend 1 , subman 2 and a backend platform of an appropriate MNO via network 310. Network connections may be established when each of the platforms connects to network 310 e.g. via local cellular networks.

[0081] At step 604 the method comprises receiving a plurality of logs from the plurality of log-producing platforms. Each of the logs received by the log ingestion engine 144 comprise raw log data. For example the service provider 142 shown in figure 2 may receive a plurality of logs from the brand 4 backend platform 112d, TCU 5, backend 1 , subman 2 and a backend platform of an appropriate MNO via network 310. Each log will be formatted according to a format of the respective platform which produced the log.

[0082] Step 605 shows an alternative or additional means of receiving logs i.e. via a user interface, such as the user interface 320 shown in figure 3. Each of the logs received by the log ingestion engine 144 in this way comprise raw log data, again formatted according to a format of the respective platform which produced the log. As will be explained in further detail below, the user interface 320 may also be used to provide the service provider 142 / logs ingestion engine 144 with a logs formatting scheme, such as an updated logs formatting scheme.

[0083] The method 600 comprises, at step 606, determining whether the log data received by the log ingestion engine 144 (either in step 604 or step 605) is present in the common database 146. This may be carried out by the log ingestion engine 144 which compares the file names of received logs with file names of logs stored in the common database 146.

[0084] If it is found at step 606 that the received log data is already present in the common database, the method proceeds to step 608 (following branch ‘Y’) where the received log data is discarded and not added to the common database 146. Not adding this data to the common database ensures efficiency of memory and removes the risk of storing duplicated data in the common database 146.

[0085] If it is found at step 606 that the log data is not present in the common database, the method 600 proceeds to step 610 (following branch ‘N’). In step 610 formatted log data is produced by the log ingestion engine 144. As will be appreciated, the order of steps 606 and 610 may be reversed, so that the received log data is formatted before it is determined whether the log data received by the log ingestion engine 144 is present in the common database 146.

[0086] The logs received by the log ingestion engine 144, either from a log-producing platform (step 604) or via a user interface 320 (step 605), comprise raw log data saved according to a unique or particular format that will be specific to the logproducing platform. At step 610 the log ingestion engine 144 processes received logs to produce a set of uniform logs, formatted according to a particular logs formatting scheme i.e. a common data format, for storage in the common database 146.

[0087] The logs formatting scheme is defined in a configuration file of the log ingestion engine 144. The logs formatting scheme contains information about how the logs ingestion engine 144 should format or re-format received and / or stored logs for storage in the common database 146. The logs ingestion engine 144 may be initially provisioned with a default logs formatting scheme, which may be updated.

[0088] The logs in the common database 146 are stored in a column format in a multidimensional database such as that provided by Snowflake. It will be appreciated that Snowflake is an example of a platform that can be used for cloud data warehousing. All data in Snowflake is stored in database tables and logically structured as collections of rows and columns. Within the present disclosure, reference will be made to Snowflake tables, but it will be understood that these are exemplary of database structures that could equivalently be used within the context of the present teaching and the present teaching should not be construed as being limited to any one proprietary type of database structure. Like other database structures, a Snowflake table includes a plurality of fields. In preferred embodiments, the Snowflake table configured for the purposes of the present teaching includes at least the following Fields:

[0089] • TimeGenerated: the time of generation of the log

[0090] • Json_data: the raw log data, in Json format

[0091] • LogName: the filename of the log

[0092] • Transactionld_g: the transaction ID of the log

[0093] • ProviderName_s: the name of the log-producing platform that produced the log

[0094] The logs ingestion engine 144 extracts data from the received logs and populates each of the fields in a temporary table, where possible, with data from the received log files.

[0095] Where further relevant data is available to the log ingestion engine 144, the received log data may be augmented with further data relevant data before it is sent to the common database 146. For example, further fields can be added to the Snowflake Table, and appropriate data added to those fields for each log. Such augmentation of the log data with additional data provides context and allows the identification of early warning signs of failures, and allows attribution of failure root cause to specific areas. As an example, the Snowflake table can include the following additional Field:

[0096] • VIN: vehicle identifier e.g. vehicle IMSI

[0097] In such embodiments the log ingestion engine 144 allows cross-correlation of data from different platforms using device identifiers (e.g. vehicle IMSI) and / or timestamps of the log files. This allows the identification of e.g. those particular vehicles or devices which are responsible for particular calls, or those particular vehicles or devices for which process failure rates are high.

[0098] At step 612 formatted log data is added to the common database 146. For example the log ingestion engine 144 sends the data for each field of the Snowflake table to the common database 146, which may be local or remote from the log ingestion engine 144. The method then returns to step 604 when further logs are received. Optionally at step 614 the service provider 142 waits before returning to step 604 and checking whether further logs have been received from the logproducing platforms.

[0099] The log ingestion engine 144 may receive an ongoing stream of data (i.e. logs) from each log-producing platform. Each log may relate to one vehicle of a plurality of vehicles, such as a fleet of vehicles. For example, a fleet of vehicles may be interacting with a single platform and the single platform may provide each log (each relating to a particular vehicle) to the aggregation layer.

[0100] Reformatting of data in the common database

[0101] After common database 146 has been populated with formatted log data, it may be necessary to subsequently extend or augment the Snowflake table with additional fields. For example, where it is necessary to investigate the execution of a particular call between two platforms for an entire fleet of vehicles, a field may be added to the Snowflake table in the common database 146. Data indicating whether the process associated with that call was successful or unsuccessful (as indicated by analysing the logs) can added to the new field. Figure 7 discloses a method for managing such updates to the Snowflake table and logs formatting scheme.

[0102] Figure 7 shows a method 700 in accordance with an aspect of the present teaching. The method 700 may be automated or semi-automated- for example by execution of a computer routine, such as a Python script, at the service provider 142 shown in figures 1 , 2 and 5.

[0103] The method 700 comprises, at step 702, receiving a new logs formatting scheme. The new logs formatting scheme may outline one or more new fields to be included in the Snowflake table, or may list one or more fields which are to be deleted from the Snowflake table. The new logs formatting scheme may be defined by a user and transmitted to the service provider 142 via the user interface 320.

[0104] At step 704 data already stored in the common database 146 is re-formatted according the new logs formatting scheme. Where the Snowflake table is to include a new field, the new field is added to the Snowflake table in the common database 146, respective data for the new field is extracted from each of the existing log files (in particular, the Json_data field) already stored in the database 146, and the new data is stored in the new field. In other words, the executable software - such as the exemplary Python script- may re-run through data saved in the Snowflake table to extract further data from the Json_data field to be stored in a new column of the Snowflake table. Where a field has been removed from the Snowflake table that field is deleted.

[0105] At step 706 the configuration file, which defines the way that the raw log data is formatted or re-formatted before being stored in the common database 146, is updated. For example, fields which are to be added to or deleted from the Snowflake table may be correspondingly adjusted in the configuration file. Updating the configuration file will ensure that newly-received logs will be sent to the common database 146 according to the new format.

[0106] Data analysis, triggering events and reports / notifications

[0107] Figure 8 discloses a method 800 in accordance with an aspect of the present teaching for monitoring and alerting on specific process flows across the full ecosystem and ecosystem partners. Specifically, method 800 can be used to monitor business process flows (e.g. end to end registration success with trigger API through to Service activation notification sent), individual API performance (number of calls to a platform that were returned etc.) and API / Process step failure counts. The method 800 can be used to identify errors and / or events of interest in a system comprising a plurality of network-enabled vehicles and / or a plurality of log-producing platforms.

[0108] The method 800 may be carried out by the service provider 142 shown in figures 1 , 2 and 5. The method 800 may be carried out concurrently with or directly after method 600 i.e. after step 612.

[0109] The method 800 comprises, at step 802, analysing formatted log data in the common database 146. This analysis can be carried out by a script, such as a Python script, run by the service provider 142. As will be appreciated, the content of any analysis script will be greatly simplified by the fact that a consistent formatting of data is used in the common database 146. In particular, the Json_data in the Snowflake table contains all the information contained in the received logs. For easy access, the logs can be filtered by LogName and the logs can be further used for advanced analytical purposes by parsing data in the Json_data field.

[0110] The method 800 comprises, at step 804, determining whether a predetermined condition or trigger event has been met. For example, the service provider 142 may determine whether a plurality of new vehicles 302, which are to be added to the fleet 300, have been successfully enrolled or registered with the backend platform 112d, backend 1 (labelled 132a in figures 1 and 2) and subman 2 (labelled 152b in figures 1 and 2).

[0111] As will be appreciated, any suitable predetermined conditions or triggering events may be used. The predetermined condition may be based on a percentage of logs indicating the failure of a particular process being below a predetermined threshold, expressed as a percentage. The predetermined condition may be met when an attempt to register or enrol one or more vehicles with a mobile communication network, a network service provider and / or one or more logproducing platforms is unsuccessful, or when an attempt to register or enrol a predetermined number of vehicles with the mobile communication network, a network service provider and / or one or more of the log-producing platforms is unsuccessful. Instead of or in addition to a predetermined condition having been met, the method 800 may comprise determining whether a trigger event, such as registration or enrolment of one or more vehicles with one or more log-producing platforms and / or a network service provider, has been met. The trigger event may reflect non-registration or enrolment of one or more vehicles with one or more logproducing platforms and / or a network service provider.

[0112] If it is found at step 804 that the predetermined condition has been met, the method 800 proceeds to step 806 (following branch ‘Y’). In step 806 a report or notification is generated. After the report or notification is generated it may be sent e.g. via email to a user or displayed on a user interface. The method 800 may return to step 802, for example after a delay 808, for example a 5 minute delay.

[0113] If it is found at step 804 that the predetermined condition has not been met, the method returns to step 802 (following branch ‘N’). A delay 806 may be used to prevent the analysis of data being repeated too quickly. For example, a delay of 5 minutes may be used so that step 802 is performed every 5 minutes. The method 800 may be carried out in response to a user command and / or continuously so that the data may be analysed in real-time, or in bulk after storage.

[0114] Figure 9A-9C are schematic views of a logs analysis dashboard, which may be the output of an analysis, such as the analysis in step 802 in which formatted log data in the common database 146 is analysed.

[0115] Figure 9A shows a time-series analysis of the success / failure rates of several calls made between platforms during a procedure in which a plurality of vehicles are registered with a plurality of log producing platforms. In particular, figure 9A shows a time-series analysis of the success / failure rates of M0D4 Registration requests, M0D4 Allocate requests and M0D4 Download requests for a plurality of vehicles during a registration procedure.

[0116] As shown, M0D4 Registration requests have a failure rate of 3.98%, M0D4 Allocate requests have a failure rate of 21 .95% and M0D4 Download Requests have a failure rate of 61 .74%. This means that e.g. 3.98% of M0D4 Registration requests are unsuccessful and must be re-sent. Figure 9B shows an overall failure rate of 26.51% for all calls. The predetermined condition in step 804 may be that the failure rate of M0D4 registration requests is above 10%. In the case of Figure 8B, the failure rate of M0D4 registration requests is 26.51 % and therefore this condition has been met, and a report or notification will be sent (step 806).

[0117] Figure 9C shows a table summarising the numbers of successful and unsuccessful registration procedures for a plurality of vehicles in a fleet. For the majority of (89.79%) vehicles, no failed returns are received and the devices are successfully registered. Figure 9C shows that over half of all calls result in failure, and are due to just 10.21 % of the vehicles being registered.

[0118] Web interface

[0119] Figures 10A and 10B show examples of a user interface 1000 which can be used to add logs to the common database 146. The user interface can be used to add logs individually or in bulk to the database 146. The user interface 1000 comprises a first screen 1010 (figure 9A) and a second screen 1020 (figure 9B). The first screen comprises four buttons: “ADD NEW LOG” button 1012; “UPDATE EXISTING LOGS” button 1014; “DOWNLOAD EXISTING LOGS” button 1016; and “RUN ADHOC PYTHON SCRIPT” button 1018. A further button “ADD NEW LOGS FORMATTING SCHEME” may also be included. The second screen 1020 comprises three editable data fields: an email field 1022, a log name field 1024 and a query field 1026.

[0120] Further embodiments

[0121] Figure 11 shows an example method 1100 for receiving and processing logs. Two tables are used: Table 1 which stores logs and Table 2 which stores logs and queries. Containerised implementations such as provided by a container comprising a first Python script and a Second Python script can also be used.

[0122] At step 1102 the method comprises establishing a connection to a Snowflake workspace. At step 1104 the method comprises reading the log names and queries from table 2 and stores them in a temporary dataframe (D1 ). At step 1106 the method comprises establishing a connection to a log analytics workspace. At step 1108 the method comprises looping through each of the log names and using the respective queries to extract logs. At step 1110 the method comprises storing the extracted queries in temporary dataframes D3. At step 1112, for each of the logs, the historical data is read from Table 1 and stored in a temporary dataframe D2. At step 1114 the extracted logs are compared with the historical logs and only new logs are stored in another temporary dataframe D4 to avoid duplicates. At step 1116 the temporary dataframe D4 is loaded into Table 1 .

[0123] Figure 12 shows an example method 1200 for receiving and processing logs via a web user interface.

[0124] At step 1202 one or more new logs are to be added to the common database via the web III. At step 1204 a user lands on an input page to submit the logs. At step 1206 the logs are checked for errors. If no errors are found at 1208, the logs are loaded into the snowflake table at step 1210. If errors are found at step 1212, the user is redirected to an error page with a retry button at step 1214. At step 1216 existing logs already in the database are to be updated. At step 1218 a user lands on an input page to submit the logs. At step 1220 it is checked whether the log already exists. If it is found that the log already exists (step 1222) the method proceeds to step 1224 where the log is updated in the Snowflake table. If it is found that the log does not exist in the database (step 1226), the method proceeds to step 1228 where the user is redirected to an error page with two options: either add the log as a new log at step 1230 or try again at step 1232. The method 1200 concludes at step 1234 with an acknowledgment page when a log has been successfully added to the database.

[0125] Modifications can be made to that herein described without departing from scope of the present application which is intended to be limited only insofar as is necessary in the light of the claims that follow.

[0126] The words comprises / comprising when used in this specification are to specify the presence of stated features, integers, steps or components but does not preclude the presence or addition of one or more other features, integers, steps, components or groups thereof.

Claims

Claims1 . A method of recording, within a common database, network-related activity at one or more network-enabled vehicles and / or a plurality of log-producing platforms, the, or each, vehicle of the one or more network-enabled vehicles being configured for communication with each of the plurality of log-producing platforms over a network, the method comprising: establishing, by a data aggregator, network connections with each of the plurality of log-producing platforms; receiving, by the data aggregator, a plurality of logs produced by one or more of the log-producing platforms, wherein each log of the plurality of logs records network-related activity at a network-enabled vehicle and / or a logproducing platform during registration or enrolment of a respective network- enabled vehicle with a respective log-producing platform; determining, by the data aggregator, whether the received plurality of logs are present in the common database; and if the received plurality of logs are not present in the common database, producing, by the data aggregator, formatted log data from the plurality of logs and adding the formatted log data to the common database.

2. The method according to claim 1 , wherein the formatted log data contains vehicle identification information, a time stamp, and / or location data such as vehicle location data.

3. The method according to claim 1 , wherein the plurality of log-producing platforms comprises at least a vehicle platform and a mobile telecommunication platform.

4. The method according to any preceding claim, wherein the method comprises registering or enrolling a vehicle or a plurality of vehicles with one or more of the log-producing platforms.

5. The method according to any preceding claim, wherein the method comprises identifying, by the data aggregator, a trigger event by cross-correlating data originating from each of the log-producing platforms in the common database.

6. The method according to claim 5, wherein the trigger event is identification of successful registration or enrolment of one or more vehicles with one or more of the log-producing platforms and / or a network service provider.

7. The method according to claim 5, wherein the trigger event is identification of non-registration or enrolment of one or more vehicles with one or more of the log-producing platforms and / or a network service provider.

8. The method according to claim 5, wherein the method further comprises, in response to the trigger event, generating an alert.

9. The method according to claim 5, wherein the method further comprises, in response to the trigger event, authorising the, or each, vehicle to use the mobile communication network, one or more of the log-producing platforms and / or the network service provider.

10. The method according to any preceding claim, wherein the method further comprises: analysing the formatted log data in the common database to determine whether a predetermined condition has been met; and if the predetermined condition has been met, generating a report or notification.11 . The method according to claim 10, wherein the predetermined condition is met when an attempt to register or enrol one or more vehicles with the mobile communication network, a network service provider and / or one or more of the log-producing platforms is unsuccessful.

12. The method according to claim 10, wherein the predetermined condition is met when an attempt to register or enrol a predetermined number of vehicles with the mobile communication network, a network service provider and / or one or more of the log-producing platforms is unsuccessful.

13. The method of any preceding claim, wherein each log-producing platform produces logs having a unique format.

14. The method according to any preceding claim, wherein the, or each, log comprises raw log data.

15. The method according to claim 13 or claim 14, wherein the step of producing formatted log data comprises formatting the raw log data according to a common data format.

16. The method according to any preceding claim, wherein the method comprises associating the logs and / or formatted log data with one or more vehicles.

17. The method according to claim 16, wherein the method comprises associating formatted log data in the common database with one or more vehicle identifiers.

18. The method according to any preceding claim, wherein the method comprises receiving logs in bulk, preferably via a web interface.

19. The method according to any preceding claim, wherein the method comprises receiving logs from each log-producing platform in real-time.

20. The method according to any preceding claim, wherein the method comprises analysing the data in the common database in real-time or in bulk after storage.21 . The method according to any preceding claim, wherein the plurality of vehicles is a fleet of vehicles.

22. A system for recording network activity of a plurality of network-enabled vehicles within a common database, the system comprising a data aggregator configured to carry out the method according to any preceding claim.

23. A method of processing log data from one or more log-producing platforms, wherein the or each log-producing platform is configured to produce logs of events relating to network-related activity at one or more network nodes, the method comprising: receiving raw log data from the, or each, log-producing platform, wherein the raw log data comprises events relating to network traffic at one or more network nodes; producing formatted log data from the received raw log data; determining whether the formatted log data is located in a database; and if the formatted log data is not located in the database, adding the formatted log data to the database.

24. A system for processing log data from one or more log-producing platforms, the system comprising a data aggregator configured to carry out the method according claim 23.

Citation Information

Patent Citations

  • Log collection, structuring and processing

    US20110314148A1

  • System and method for providing fleet cyber-security

    US20180351980A1