WO2015182281A1 - 車載情報システム及びその情報処理方法 - Google Patents

車載情報システム及びその情報処理方法 Download PDF

Info

Publication number
WO2015182281A1
WO2015182281A1 PCT/JP2015/061847 JP2015061847W WO2015182281A1 WO 2015182281 A1 WO2015182281 A1 WO 2015182281A1 JP 2015061847 W JP2015061847 W JP 2015061847W WO 2015182281 A1 WO2015182281 A1 WO 2015182281A1
Authority
WO
WIPO (PCT)
Prior art keywords
log
server
vehicle
transaction identifier
message
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/JP2015/061847
Other languages
English (en)
French (fr)
Japanese (ja)
Inventor
元 土田
松原　大典
亨輔 鶴巣
靖 永井
澤尻　晴彦
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Faurecia Clarion Electronics Co Ltd
Original Assignee
Clarion Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Clarion Co Ltd filed Critical Clarion Co Ltd
Priority to CN201580002524.7A priority Critical patent/CN105706062B/zh
Priority to EP15799906.1A priority patent/EP3151124A4/en
Priority to US15/125,369 priority patent/US10009220B2/en
Publication of WO2015182281A1 publication Critical patent/WO2015182281A1/ja
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/069—Management of faults, events, alarms or notifications using logs of notifications; Post-processing of notifications
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/32—Monitoring with visual or acoustical indication of the functioning of the machine
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/34—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90—Details of database functions independent of the retrieved data types
    • G06F16/95—Retrieval from the web
    • G06F16/951—Indexing; Web crawling techniques
    • G—PHYSICS
    • G07—CHECKING-DEVICES
    • G07C—TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
    • G07C5/00—Registering or indicating the working of vehicles
    • G07C5/008—Registering or indicating the working of vehicles communicating information to a remotely located station
    • G—PHYSICS
    • G07—CHECKING-DEVICES
    • G07C—TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
    • G07C5/00—Registering or indicating the working of vehicles
    • G07C5/08—Registering or indicating performance data other than driving, working, idle, or waiting time, with or without registering driving, working, idle or waiting time
    • G07C5/0841—Registering performance data
    • G07C5/085—Registering performance data using electronic data carriers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0677—Localisation of faults
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/04—Processing captured monitoring data, e.g. for logfile generation
    • H04L43/045—Processing captured monitoring data, e.g. for logfile generation for graphical visualisation of monitoring data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
    • G—PHYSICS
    • G07—CHECKING-DEVICES
    • G07C—TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
    • G07C5/00—Registering or indicating the working of vehicles
    • G07C5/08—Registering or indicating performance data other than driving, working, idle, or waiting time, with or without registering driving, working, idle or waiting time
    • G07C5/0816—Indicating performance data, e.g. occurrence of a malfunction
    • G07C5/0825—Indicating performance data, e.g. occurrence of a malfunction using optical means

Definitions

  • the present invention relates to an in-vehicle information system in which a communication terminal and an in-vehicle terminal cooperate to access a server and an information processing method thereof.
  • an in-vehicle terminal such as a car navigation system is connected to a data center, and various car navigations are related through the communication line.
  • Telematics systems that provide services are known.
  • the data center collects log data stored in the in-vehicle terminal or the portable terminal, and analyzes the trouble occurring in the in-vehicle terminal or the portable terminal on the data center side. To be done.
  • a Web server that has received a request from a client generates a transaction ID (Identification) that identifies a series of processes, circulates between a plurality of servers, and outputs a log including the transaction ID.
  • the person in charge who received the complaint that the screen display is slow from the client terminal searches the log corresponding to the condition that “the total processing time is more than a certain time”, and after narrowing down by transaction ID, which part of the processing took time Determine.
  • Patent Document 1 when a failure occurs in communication between the in-vehicle terminal and the portable terminal, since the transaction ID is not issued in the in-vehicle terminal and the portable terminal, which process caused the failure It becomes difficult to analyze. In addition, even when a request from the in-vehicle terminal to the server does not reach the server, the server cannot issue a transaction ID for the request that has not arrived, so analyze which process caused the failure. Difficult to do.
  • An object of the present invention is to provide an in-vehicle information system and an information processing method thereof that can output information for identifying a fault location by storing at least information that can be commonly managed by the in-vehicle terminal, the portable terminal, and the server as a log. Is to provide.
  • the present invention generates a first transaction identifier that identifies a series of transactions defined by the request when the vehicle-mounted terminal constituting the vehicle-mounted information system transmits the request to the server. And saves the request in the in-vehicle log buffer, and transmits the request including the first transaction identifier to the portable terminal.
  • the portable transaction buffer stores the first transaction identifier in the portable log buffer.
  • the server sends the request to the server, and when the server receives the request, the first transaction identifier is provided on the condition that the first transaction identifier exists in the received request. In the server log buffer, provided that the received request does not have the first transaction identifier.
  • a second transaction identifier for identifying the processing of the received request is generated, and on the condition that an event has occurred, a first message for displaying the content of the event and the second transaction identifier are related
  • the first message code is generated, the second transaction identifier and the first message code are stored in the server log buffer, and a response is transmitted, the first transaction identifier is stored in the server log buffer.
  • a response including the first transaction identifier, the first message, and the first message code is transferred to the portable terminal, and the first transaction is stored in the server log buffer.
  • the first message and the first message code are provided on the condition that no identifier exists.
  • the mobile terminal receives any of the responses, the mobile terminal stores the information added to the received response in the portable log buffer and receives the response.
  • the response is transferred to the in-vehicle terminal, and when the in-vehicle terminal receives the response, the information added to the response is stored in the in-vehicle log buffer, and the first message and the first message are stored. It is characterized by outputting a code.
  • the present invention it is possible to output information for identifying a fault location by storing at least information that can be managed in common by the in-vehicle terminal, the portable terminal, and the server as a log.
  • Example 1 the transaction ID generated by the in-vehicle terminal is used in the data center.
  • FIG. 1 is a block diagram showing a first embodiment of an in-vehicle information system according to the present invention.
  • the in-vehicle information system includes an in-vehicle terminal 10, a portable terminal 20, and a data center 40 as a telematics system, and the in-vehicle terminal 10 and the portable terminal 20 are connected to each other via an inter-terminal network 60.
  • the mobile terminal 20 is connected to the data center 40 via the Internet network 70 and to the external service 71.
  • the Internet network 70 is configured by a carrier network (NW) line provided by a communication carrier of the mobile terminal 20 or an ISP network provided by an Internet service provider (ISP).
  • NW carrier network
  • ISP Internet service provider
  • the data center 40 and the mobile terminal 20 are connected to an external service 71 via the Internet network 70.
  • the external service 71 provides a service different from the data center 40 to the mobile terminal 20 and the in-vehicle terminal 10 via the Internet network 70.
  • the data center 40 is a computer device having information processing resources such as a CPU (Central Processing Unit), a memory, and an input / output interface, and is an application (AP) server that provides services to users of the in-vehicle terminal 10 and the mobile terminal 20
  • AP application
  • 41 and the log management server 50 are connected to each other. Note that the application server group 41 and the log management server 50 can be distributed and arranged in a plurality of data centers instead of being integrated and arranged in one data center 40.
  • FIG. 2 is a configuration diagram of the in-vehicle terminal.
  • an in-vehicle terminal 10 includes an input unit 11 for inputting information by a user operation, a display unit 12 for displaying information to the user, an in-vehicle terminal control unit 13 for controlling the entire in-vehicle terminal 10, and an external A memory card interface (IF) 14 for identifying a memory card as a storage device, a connection interface (IF) 15 for communicating with a device such as a portable terminal, and a log buffer (for storing logs output from the in-vehicle terminal control unit 13) An in-vehicle log buffer) 16 and an in-vehicle terminal application 17 executed on the in-vehicle terminal control unit 13.
  • the connection interface 15 is connected to the mobile terminal 20 via the inter-terminal network 60.
  • the inter-terminal network 60 for example, a cable, IEEE802.15.1, IEEE802.11 series, or the like can be used.
  • the in-vehicle terminal application 17 is composed of, for example, an application program for car navigation.
  • the in-vehicle terminal control unit 13 can display car navigation information on the screen of the display unit 12 by executing the in-vehicle terminal application 17.
  • cTID is used as a transaction ID (first transaction identifier) for uniquely identifying a series of transactions specified by the request.
  • the request including the generated transaction ID (cTID) is transferred to the portable terminal 20 via the connection interface 15 and the inter-terminal network 60.
  • the in-vehicle terminal application 17 transfers the request including the transaction ID (cTID) to the portable terminal 20, and then stores the transaction ID (cTID) in the log buffer 16 as a transmission log or a communication log together with time information.
  • a log such as a transmission log, a communication log, or an application log is stored in a storage medium such as the log buffer 16, it is assumed that time information at the time of log storage is included.
  • the in-vehicle terminal application 17 generates an HMI message code that encodes information such as an HMI (Human Machine Interface) message for displaying the failure content and the failure content, for example, when the failure is detected as an event, An application log including the generated HMI message and HMI message code is stored in the log buffer 16.
  • HMI Human Machine Interface
  • FIG. 3 is a configuration diagram of the mobile terminal.
  • a mobile terminal 20 includes an input unit 21 for inputting information by a user's operation, a display unit 22 for displaying information to the user, a mobile terminal control unit 23 for controlling the entire mobile terminal 20, and the Internet.
  • 70 includes an external communication interface (IF) 24 that communicates with the outside through a network, a connection interface (IF) 25 that connects to a device such as an in-vehicle terminal, and a mobile terminal application 26 that is executed on the mobile terminal control unit 23.
  • a mobile terminal application log buffer 27 is arranged in the mobile terminal application 26.
  • the mobile terminal application 26 includes a mobile terminal application program.
  • the mobile terminal control unit 23 executes the mobile terminal application 26 and displays information on the screen of the display unit 22 according to the mobile terminal application 26.
  • the mobile terminal application 26 receives the request transferred from the in-vehicle terminal 10 via the connection interface 25 in order to transmit the request to the data center 40 in cooperation with the in-vehicle terminal 10, the transaction ID (cTID ) Is stored in the log buffer 26 as a communication log, and then the request including the received transaction ID (cTID) is transmitted to the data center 40 via the external communication interface 25 and the Internet network 70.
  • the mobile terminal application 26 stores a request transmission log including a transaction ID (cTID) in the log buffer 27 as a communication log.
  • the mobile terminal application 26 when a failure is detected, the mobile terminal application 26 generates an HMI message code that encodes information such as an HMI message and failure content for displaying the failure content, and the generated HMI message and The application log including the HMI message code is stored in the log buffer 27.
  • the application installed in the portable terminal 20 and the portable terminal application 26 provided by the service provider of the data center 50 is provided.
  • the execution screen of the mobile terminal application 26 executed by the mobile terminal 20 is transferred to the in-vehicle terminal 10 through the connection interface 25, and the in-vehicle terminal control unit 13 of the in-vehicle terminal 10 controls the screen size of the execution screen.
  • controlling the screen transfer to be displayed on the display unit 12 or executing the in-vehicle terminal application 17 installed in the in-vehicle terminal 10 on the in-vehicle terminal control unit 13, and the in-vehicle terminal application 17 is connected via the connection interface 15.
  • the screen display for displaying the execution screen on the display unit 12 using the service of the data center 50 is used.
  • the screen display for displaying the execution screen on the display unit 12 using the service of the data center 50 is used.
  • FIG. 4 is a block diagram of the AP server.
  • an AP server 41 includes an AP server application 42 that operates on the AP server, middleware 43 that controls the operation of the AP server 41, a communication interface 44 that connects to other AP servers and the Internet network 70, an AP
  • the log buffer 45 stores various logs output by the server application 42, the middleware 43, and the like.
  • the AP server application 42 is an application program that operates on a CPU that performs overall control of the AP server 41.
  • the AP server application 42 exchanges information with other AP servers 41 and the mobile terminal 20 via the connection interface 44.
  • the request reception log is stored in the log buffer 45.
  • the AP server 41 to which the AP server application 42 belongs is an AP server 41 that returns a response to the mobile terminal 20
  • the AP server application 42 that has received the request executes the process according to the received request, and the processing result
  • the processing result is stored in the log buffer (server log buffer) 45 as an application log.
  • the AP server application 42 encodes an HMI message for displaying the failure content and information such as the failure content.
  • the application log including the generated HMI message and the HMI message code is stored in the log buffer 27, and the transaction ID (cTID) added to the request and the response message in which the generated HMI message and the HMI message code are recorded are stored.
  • the response transmission log including the transaction ID (cTID), the HMI message, and the HMI message code is stored in the log buffer 27 through the connection interface 44.
  • the AP server application 42 that has received the request uses a transaction ID (as a identifier for identifying a series of transactions specified by the received request).
  • sTID a transaction ID
  • sTID and the generated transaction ID (sTID) is managed as a second transaction identifier.
  • the transaction ID (sTID) is composed of information having a larger data capacity than the transaction ID (cTID) generated by the in-vehicle terminal 10 and is managed according to an algorithm defined by each AP server 41. It is managed as common information.
  • the AP server 41 to which the AP server application 42 belongs is not the AP server 41 that returns a response to the mobile terminal 20
  • the AP server application 42 that has received the request stores the request reception log in the log buffer 45 and then receives it.
  • the request is transferred to another AP server (AP server that processes the request) 41.
  • FIG. 5 is a configuration diagram of the log management server.
  • the log management server 50 includes a log collection unit 51 that collects logs output from the in-vehicle terminal 10, the mobile terminal 20, and the AP server 41, and logs collected from the in-vehicle terminal 10, the mobile terminal 20, and the AP server 41.
  • a log database (DB) 54 to be stored a log analysis unit 52 for analyzing the log stored in the log DB 54, a PC connected to the in-vehicle terminal 10, the portable terminal 20, and the AP server 41 and displaying a log analysis result
  • a connection interface 53 connected to a display device (not shown).
  • the log collection unit 51 is a program that operates on a CPU that performs overall control of the log collection unit 51, and has a function of collecting logs from the mobile terminal 20 and the AP server 41.
  • the log analysis unit 52 is a program that operates on a CPU that performs overall control of the log collection unit 51.
  • the log analysis unit 52 analyzes a log stored in the log DB 54 and displays the analysis result via the connection interface 53 on the mobile terminal 20 or the display. It has a function to transfer to the device.
  • the log database 54 exists in the log management server 50, but the log database 54 may be arranged on a server different from the log management server 50.
  • FIG. 6 is a configuration diagram of the HMI message code.
  • an HMI message code 100 is indicated by an identifier 101 for identifying a server or an application that has detected an error, an error number 102 indicating a failure content, I (Information), W (Warning), E (Error), and the like. Error level 103 and a lower number 104 indicating the lower digits of the transaction ID.
  • the identifier 101 uses 2-digit information. A three-digit number is used as the error number 102, and the failure content is classified corresponding to this number. One-digit information is used for the error level. For the lower number 104, information of 6 digits among the lower digits of the transaction ID is used.
  • the lower number 104 of the transaction ID is composed of the last six digits of the transaction ID (sTID)
  • the lower number 104 is associated with the transaction ID (sTID). That is, the transaction ID (sTID) generated by the AP server 41 can be specified by referring to the lower number 104 in the HMI message code 100.
  • the setting of the number of digits of information used for the HMI message code 100 can be arbitrarily changed. Further, information other than the identifier 101 to the lower number 104 can be added to the HMI message code 100, and only a part of the information from the identifier 101 to the lower number 104 can be added to the HMI message code 100. .
  • FIG. 7 is a sequence diagram for explaining the processing of the first embodiment.
  • the in-vehicle terminal application 16 on the in-vehicle terminal 10 transmits a request to the AP server 41 in the data center 40 via the portable terminal application 26 on the portable terminal 20, This is an example when a failure is detected.
  • the process is started.
  • the executed in-vehicle terminal application 17 Prior to transmitting the request to the data center 40, the executed in-vehicle terminal application 17 generates cTID as a transaction identifier for identifying a series of transactions specified in the request (S10), and a request including the generated cTID. Is transmitted to the portable terminal 20 as a request message (S11), and a request transmission log (car-mounted log) including cTID is stored in the log buffer 16 as a communication log (S12).
  • the mobile terminal application 26 on the mobile terminal 20 When receiving a request from the in-vehicle terminal 10, the mobile terminal application 26 on the mobile terminal 20 stores a request reception log (portable log) including cTID in the log buffer 27 as a communication log (S13), and then stores the cTID.
  • the request including the request message is transferred to the data center 40 as a request message (S14), and the request transmission log including the cTID is stored in the log buffer 27 as a communication log (S15).
  • the AP server 41 that has received the request transmitted from the mobile terminal 20, for example, the AP server application 42 of the AP server 41-1 existing in the forefront in the data center 40, receives a request reception log (server log) including cTID Is stored in the log buffer 45 as a communication log (S16). Thereafter, in the case of the AP server to which the AP server 41-1 itself transmits a response, processing is executed according to the received request, and the processing result is returned as a response to the portable terminal 20 Send to.
  • server log request reception log
  • S16 communication log
  • the AP server 41-1 itself is not an AP server that transmits a response
  • the AP server application 42 of the AP server 41-1 uses a request including a cTID as a request message in the data center 40 instead of transmitting a response. Is transferred to another AP server (AP server that processes the request) 41 (S17), and a request transfer log including cTID is stored in the log buffer 45 as a communication log (S18).
  • the AP server application 42 of the AP server 41-n that has received the request transferred from the AP server 41-1 stores the request reception log including the cTID in the log buffer 45 as a communication log (S19). Thereafter, the AP server application 42 of the AP server 41-n executes processing according to the received request. In this process, for example, when a failure is detected as an event (S20), an HMI message and an HMI message code are generated. (S21) The application log including the generated HMI message and HMI message code and the cTID added to the request is stored in the log buffer 45 (S22), and the generated HMI message and HMI message code and the request are added to the request.
  • a response including the cTID is transmitted to the AP server 41-1 as a response message (S23), and a communication log including the HMI message code and the cTID is stored in the log buffer 45 as a response transmission log indicating that the response has been transmitted (S23). S24).
  • the log buffer 45 uses a response reception log including the HMI message, the HMI message code, and the cTID as a communication log. (S25), the response message including the HMI message, the HMI message code, and the cTID is transferred to the portable terminal 20 (S26), and the response transmission log including the HMI message code and the cTID is stored in the log buffer 45 as a communication log. Save (S27).
  • the mobile terminal application 26 of the mobile terminal 20 receives a response message as a response from the AP server 41-1, the response reception log including the HMI message, the HMI message code, and the cTID is stored in the log buffer 27 as a communication log.
  • the response message including the HMI message, the HMI message code, and the cTID is transferred to the in-vehicle terminal 10 (S29), and then the response transmission log including the HMI message code and the cTID is used as the communication log as the log buffer 27. (S30).
  • the in-vehicle terminal application 17 of the in-vehicle terminal 10 stores a response reception log including the HMI message code and cTID in the log buffer 16 as a communication log (S 31).
  • the added HMI message and HMI message code are displayed on the screen of the display unit 12 (S32), and the processing in this routine is terminated.
  • FIG. 8 is a sequence diagram for explaining log analysis processing.
  • the user of the in-vehicle terminal 10 reads the HMI message code 100 displayed on the screen of the display unit 12 of the in-vehicle terminal 10, the user operates the in-vehicle terminal 10, and the system administrator of the data center 40 This is started by contacting the HMI message code 100 for specifying the log to be processed.
  • the in-vehicle terminal application 17 of the in-vehicle terminal 10 is stored in the log buffer 16 based on the information input to the input unit 11.
  • the log (application log or communication log) in which the HMI message code 100 is recorded is extracted from the existing log, and the extracted log is transmitted to the log management server 50 of the data center 40 via the portable terminal 20 (S51).
  • the mobile terminal application 26 of the mobile terminal 20 cooperates with the in-vehicle terminal 10 to transmit a log (application log or communication log) in which the HMI message code 100 is recorded among logs stored in the log buffer 27 to the Internet.
  • the data is transmitted to the log management server 50 of the data center 40 via the network 70.
  • a method of transmitting the logs stored in the log buffer 16 and the log buffer 27 to the log management server 50 of the data center 40 a method of transmitting from the mobile terminal 20 to the log management server 50 via the Internet network 70, There is a method of recording a log on a memory card or the like connected to the memory card interface 14 of the terminal 10 and then transmitting the log recorded on the memory card to the log management server 50 of the data center 40 via a PC.
  • the log collection unit 51 of the log management server 50 receives the log transmitted from the in-vehicle terminal 10 (S51), and the received log is Store in the log database (DB) 54 (S52).
  • the log analysis unit 52 of the log management server 50 receives information by the system administrator's log analysis operation, for example, the HMI message code 100 (S53), the log analysis unit 52 receives information by the system administrator's operation.
  • the log database 54 is searched based on the log (S54), and the communication log and the application log are extracted from the logs stored in the log database 54 as the log in which the HMI message code 100 is recorded (S55).
  • the log database 54 stores logs automatically collected from the AP server 41 and logs collected from the AP server 41 during log analysis.
  • the log analysis unit 52 of the log management server 50 transfers the created sequence image to the in-vehicle terminal 10, and on the log analysis screen of the display unit 12, the order relationship between the communication log and the application log (in accordance with time series). It is also possible to display an image of a sequence indicating the order relationship).
  • FIG. 9 is a flowchart for explaining the log analysis processing. This processing is specific contents of steps S53 to S56 in FIG.
  • the log analysis unit 52 of the log management server 50 When the system administrator inputs the HMI message code notified by the user to the log management server 50 as information for specifying the log to be analyzed (S60), the log analysis unit 52 of the log management server 50 The log database 54 is searched based on the HMI message code 100, which is information input by the operation of the administrator, and communication is performed as a log in which the HMI message code 100 is recorded from the logs stored in the log database 54.
  • the log and the application log are detected (S61), and it is determined whether the communication log and the application log exist as a log in which the HMI message code 100 is recorded in the log stored in the log database 54 (S62). ).
  • step S63 If the log analysis unit 52 obtains a positive determination result in step S63, that is, if there is a log in which the HMI message code 100 is recorded in the log stored in the log database 54, the HMI message code 100
  • the communication log and app log with cTID recorded as the transaction ID are identified, and the order relationship (time series relationship) between the identified communication log and app log is organized according to the time information of each log. (S63), a sequence including the communication log and the application log in which the order relation is arranged is created, and an image of the created sequence is displayed on the log analysis screen managed by the system administrator (S64).
  • S64 system administrator
  • step S62 when a negative determination result is obtained in step S62, that is, when there is no log in which the HMI message code 100 is recorded in the log stored in the log database 54, the log analysis unit 52 is not applicable. (Information indicating that there is no log to be analyzed) is displayed on the log analysis screen (S65), and the processing in this routine is terminated.
  • the in-vehicle terminal ID and information such as the time when the failure occurred are used to uniquely identify the transaction in which the failure occurred. be able to.
  • FIG. 10 is a configuration diagram showing a display example of the log analysis screen.
  • a sequence image created by the log analysis unit 52 is displayed on the log analysis screen 120 of the display unit 12 or a PC (Personal Computer) managed by the system administrator.
  • the log analysis screen 120 includes logs stored in the log database 54, communication logs 131 to 134 as communication logs and application logs in which the HMI message code 100 and the transaction ID cTID are recorded, and application logs.
  • the log 135 and the communication logs 136 to 139 are displayed as a sequence image in chronological order according to the stored time information.
  • the details of the communication log 131 can be browsed by clicking the communication log 131.
  • the communication processing time 140 between the communication log 131 and the communication log 132 it is possible to know which process took a long time out of a series of transactions.
  • the application log 135 the details of the application log output by the AP server 41 can be viewed.
  • information that can be managed in common by the in-vehicle terminal 10, the mobile terminal 20, and each AP server 41 for example, information for identifying a fault location by storing the HMI message code 100 as a log at least. It can be output (displayed). For this reason, the system administrator uses the communication logs 131 to 134, the application log 135, the communication logs 136 to 139, the communication processing time between the communication logs, and the information of the HMI message code 100 to determine the location of the failure and the failure.
  • the contents can be specified. For example, a communication failure between the in-vehicle terminal 10 and the mobile terminal 20 can be specified.
  • the AP server 41 can execute the process using the cTID added to the request without generating the sTID having a large data capacity, the process is simplified as compared with the case where the process for generating the sTID is required. can do.
  • Example 2 In this embodiment, the transaction ID generated by the in-vehicle terminal 10 is not transmitted to the data center 40. This is because when it is assumed that a plurality of vendor in-vehicle terminals 10 are connected to the data center 40, the data center 40 cannot handle the transaction ID transmitted from each in-vehicle terminal 10, and the data center 40 has its own. Consider using the transaction ID of.
  • the mobile terminal 20 transmits a request to the data center 40
  • only the request is transmitted to the data center 40 without adding the transaction ID (cTID) generated by the in-vehicle terminal 10 to the request.
  • cTID transaction ID
  • the AP server 41 of the data center 40 receives the request, an sTID (second transaction identifier) is generated as a transaction ID for identifying a series of transactions specified in the received request, and the generated sTID is The processing of the received request is managed by each AP server 41, and the other configuration is the same as that of the first embodiment.
  • FIG. 11 is a sequence diagram for explaining the processing of the second embodiment.
  • the in-vehicle terminal application 16 on the in-vehicle terminal 10 transmits a request to the AP server 41 in the data center 40 via the portable terminal application 26 on the portable terminal 20, This is an example when a failure is detected.
  • step S70 to step S73 is the same as the processing from step S10 to step S13 in the first embodiment.
  • the mobile terminal application 26 on the mobile terminal 20 When the mobile terminal application 26 on the mobile terminal 20 receives a request from the in-vehicle terminal 10, it stores a request reception log including cTID as a communication log in the log buffer 27, and then transfers a request-only request message to the data center 40. Then, a request transmission log including cTID, which is a log indicating that only the request has been transmitted, is stored in the log buffer 27 as a communication log (S75).
  • the AP server 41 that has received the request transmitted from the mobile terminal 20, for example, the AP server application 42 of the AP server 41-1 existing in the forefront in the data center 40, receives it on condition that only the request has been received.
  • STID second transaction identifier
  • STID is generated as a transaction ID for uniquely identifying a series of transactions specified in the requested request (S76)
  • a request including sTID is received as a log indicating that only the request has been received.
  • the log is saved as a communication log in the log buffer 45 (S77), and then the AP server application 42 of the AP server 41-1 performs processing according to the received request in the case of the AP server to which the AP server 41-1 itself transmits a response. Is executed, and the processing result is stored in the log buffer 45 as an application log, and the processing result is transmitted to the portable terminal 20 as a response.
  • the AP server 41-1 itself is not an AP server that transmits a response
  • the AP server application 42 of the AP server 41-1 uses a request including an sTID as a request message in the data center 40 instead of transmitting a response. Is transferred to another AP server (AP server 41-n that processes the request) 41 (S78), and a request transfer log including sTID is stored in the log buffer 45 as a communication log (S79).
  • the AP server application 42 of the AP server 41-n that has received the request transferred from the AP server 41-1 stores the request reception log including the sTID in the log buffer 45 as a communication log (S80). Thereafter, the AP server application 42 of the AP server 41-n executes processing according to the received request. In this process, for example, when a failure is detected as an event (S81), an HMI message and an HMI message code are generated. (S82) The application log including the generated HMI message and HMI message code and the sTID added to the request is stored in the log buffer 45 (S83), and the generated HMI message and HMI message code and the request are added to the request.
  • a response including the sTID is transmitted to the AP server 41-1 as a response message (S84), and a communication log including the HMI message code and sTID is stored in the log buffer 45 as a response transmission log indicating that the response has been transmitted. (S85).
  • the AP server application 42 of the AP server 41-1 stores a response reception log including the HMI message code and sTID in the log buffer 45 as a communication log (S86). ), The response message including the HMI message and the HMI message code is transferred to the portable terminal 20 (S87), and the response transmission log including the HMI message code and sTID is stored in the log buffer 45 as a communication log as a log indicating that the response has been transmitted. Save (S88).
  • the mobile terminal application 26 of the mobile terminal 20 receives the response message including the HMI message and the HMI message code as a response from the AP server 41-1, the response reception log including the HMI message code and the cTID stored in step S75.
  • the log buffer 27 Is stored in the log buffer 27 as a communication log (S89), a response message including an HMI message and an HMI message code is transferred to the in-vehicle terminal 10 (S90), and then the response message is transferred to the in-vehicle terminal 10 as a log.
  • the response transmission log including the HMI message code and cTID is stored in the log buffer 27 as a communication log (S91).
  • the in-vehicle terminal application 17 of the in-vehicle terminal 10 receives the response message including the HMI message and the HMI message code from the mobile terminal 20, the response reception log including the HMI message code and the cTID stored in step S72 is logged as a communication log.
  • the data is stored in the buffer 16 (S92), and then the HMI message and the HMI message code added to the response message are displayed on the screen of the display unit 12 (S93), and the processing in this routine is terminated.
  • the process of fault isolation is the same as the sequence of FIG. 8 (steps S50 to S56).
  • FIG. 12 is a flowchart for explaining the log analysis processing. This process is the specific contents of steps S53 to S56 in FIG. 8. Of steps S100 to S105, the process of step S103 is different from the process of step S63 of FIG. This is the same as the processing in the step of FIG.
  • step S102 If the log analysis unit 52 obtains a positive determination result in step S102, that is, if there is a log in which the HMI message code 100 is recorded in the log stored in the log database 54, the HMI message code 100
  • the communication log and application log in which at least one of cTID or sTID is recorded as the transaction ID are identified, and the order relationship (time-series relationship) between the identified communication log and application log is the time Organize according to the information (S103).
  • the log analysis unit 52 creates a sequence in which communication logs and application logs arranged in order are arranged, and displays a log analysis screen including an image of the created sequence on a display unit managed by the system administrator. It is displayed (S104).
  • the system administrator can specify the failure location and the failure content by manipulating the sequence image displayed on the log analysis screen.
  • FIG. 13 is a configuration diagram showing a display example of a log analysis screen in the second embodiment.
  • a sequence image created by the log analysis unit 52 is displayed on the log analysis screen 120 of the PC managed by the display unit 12 or the system administrator.
  • the log analysis screen 120 includes a log stored in the log database 54 as a communication log and an application log in which at least one of the HMI message code 100 and the transaction ID cTID or sTID is recorded.
  • 151 to 153, the application log 154, and the communication logs 155 to 156 are displayed as sequence images in chronological order according to the stored time information.
  • the details of the communication log 151 can be viewed by clicking the communication log 151.
  • the communication processing time 157 between the communication log 151 and the communication log 152 it can be understood which process took a long time out of a series of transactions.
  • the application log 154 the details of the application log output by the mobile terminal 20 can be viewed.
  • the sequence after the communication log 153 has not reached the data center 40 the request transmitted from the in-vehicle terminal 10 to the portable terminal 20 has not reached the AP server 41 of the data center 40 from the portable terminal 20. I understand that.
  • FIG. 14 is another configuration diagram of the HMI message.
  • the HMI message 110 when using HTTP (Hypertext Transfer Protocol) communication is configured from information for identifying a device that has detected a failure.
  • information related to the X-HMI-message defined as an additional header of HTTP is recorded.
  • a language 111, a message text 112, an HMI message code 113, and a transaction ID 114 are recorded. Note that the information recorded in the HMI message 110 can be increased or decreased as necessary.
  • the system administrator can determine the failure from the information of the communication logs 131 to 134, the application log 135, the communication logs 136 to 139, the communication processing time between the communication logs, and the HMI message code 100. It is possible to identify the location and the content of the failure. For example, it is possible to specify a communication failure between the in-vehicle terminal 10 and the mobile terminal 20, a failure in which a request transmitted from the in-vehicle terminal 10 has not reached the AP server 41, or the like.
  • the mobile terminal 20 when the request from the mobile terminal 20 does not reach the data center 40 and the mobile terminal 20 detects a failure, the mobile terminal 20 generates an HMI message and an HMI message code, and the generated HMI message and HMI message code. Can also be transmitted to the in-vehicle terminal 10.
  • the in-vehicle terminal 10 stores a communication log indicating that the HMI message and the HMI message code have been received.
  • the in-vehicle terminal 10 and the mobile terminal 20 do not need to store sTID having a large data capacity as a log, and may store the cTID and the HMI message code 100 as a log.
  • 27 can be configured as a log buffer having a data capacity smaller than that of the log buffer 45.
  • Example 3 push data is distributed from the AP server 41 in the data center 40 to the in-vehicle terminal 10.
  • the AP server 41 of the data center 40 identifies the push data distribution processing.
  • the transaction ID As the transaction ID, sTID (third transaction identifier) is generated, and the generated sTID is used to manage the push data by each AP server 41.
  • the push data means data that the AP server 41 in the data center 40 actively distributes.
  • FIG. 15 is a sequence diagram for explaining the processing of the third embodiment. This process is an example when a failure is detected as an event in the AP server 41 in the data center 40 when the push data is distributed from the AP server 41 in the data center 40 to the in-vehicle terminal 10.
  • an AP server for generating push data for example, the server application 42 of the AP server 41-n generates push data for distribution to the in-vehicle terminal 10 (S110), and distributes the generated push data.
  • STID third transaction identifier
  • STID is generated as a transaction ID for uniquely identifying a series of transactions (S111), and an application log including the sTID is stored in the log buffer 45.
  • S112 push data and sTID are transmitted to, for example, the AP server 41-1 for distributing the push data to the mobile terminal 20 (S113), and the push data transmission log including the sTID is logged as a communication log.
  • the data is stored in the buffer 45 (S114).
  • the AP server application 42 of the AP server 41-1 that has received the push data and sTID stores the communication log including the sTID in the log buffer 45 (S115). Thereafter, the AP server application 42 of the AP server 41-1 executes processing for distributing the received push data. In this process, for example, when a failure is detected as an event (S116), the HMI message ( (Second message) and HMI message code (second message code) are generated (S117), and the application log including the generated HMI message and HMI message code and sTID is stored in the log buffer 45 (S118). Push data including the generated HMI message and HMI message code is transmitted to the mobile terminal 20 (S119), and a communication log including the HMI message code and sTID is stored in the log buffer 45 (S120).
  • the mobile terminal application 26 of the mobile terminal 20 that has received the push data including the HMI message and the HMI message code is an identifier for identifying push data distribution processing, and as a transaction ID for uniquely identifying a series of transactions, cTID (fourth transaction identifier) is generated (S121), and an application log indicating that the cTID has been generated is stored in the log buffer 27 (S122).
  • the push data with the cTID added is transmitted to the in-vehicle terminal 10 together with the HMI message and the HMI message code (S123), and a communication log including the HMI message code and the cTID is stored in the log buffer 27 (S124).
  • the in-vehicle terminal application 17 of the in-vehicle terminal 10 that has received the information including the HMI message and the push data including the HMI message code and the cTID stores the communication log including the HMI message code and the cTID in the log buffer 16 (S125). Thereafter, the HMI message and the HMI message code in the received information are displayed on the screen of the display unit 12 (S126), and the processing in this routine is terminated.
  • the process of fault isolation is the same as the sequence of FIG. 8 (steps S50 to S56). Also, the log analysis process and the process for displaying the log analysis screen are the same as those in the examples of FIGS.
  • the in-vehicle log, the portable log, and the server log as search targets, there is a log in which the HMI message (second message) is recorded in the search target.
  • a log specified by sTID (third transaction identifier) related to the HMI message (second message) and a log specified by cTID (fourth transaction identifier) are extracted from search targets, A log sequence is created according to the time information of the extracted log, and a log analysis screen including an image of the created sequence is displayed.
  • the system administrator displays the information displayed on the log analysis screen. From the information (communication log, communication processing time between application log and communication log, and HMI message code), it is possible to identify the fault location and the content of the fault.
  • the log buffer 16 of the in-vehicle terminal 10 and the log buffer 27 of the mobile terminal do not need to store the sTID generated by the AP server 41, so the data capacity of the log buffers 16, 27 Can be made smaller than the data capacity of the log buffer 45 of the AP server 41.
  • this invention is not limited to the above-mentioned Example, Various modifications are included.
  • the above-described embodiments have been described in detail for easy understanding of the present invention, and are not necessarily limited to those having all the configurations described.
  • a part of the configuration of one embodiment can be replaced with the configuration of another embodiment, and the configuration of another embodiment can be added to the configuration of one embodiment.
  • each of the above-described configurations, functions, etc. may be realized by hardware by designing a part or all of them, for example, by an integrated circuit.
  • Each of the above-described configurations, functions, and the like may be realized by software by interpreting and executing a program that realizes each function by the processor.
  • Information such as programs, tables, and files that realize each function is stored in memory, a hard disk, a recording device such as an SSD (Solid State Drive), an IC (Integrated Circuit) card, an SD (Secure Digital) memory card, a DVD ( It can be recorded on a recording medium such as Digital Versatile Disc).

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Data Mining & Analysis (AREA)
  • Quality & Reliability (AREA)
  • Databases & Information Systems (AREA)
  • Computer Hardware Design (AREA)
  • Health & Medical Sciences (AREA)
  • Computing Systems (AREA)
  • General Health & Medical Sciences (AREA)
  • Medical Informatics (AREA)
  • Debugging And Monitoring (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
PCT/JP2015/061847 2014-05-27 2015-04-17 車載情報システム及びその情報処理方法 Ceased WO2015182281A1 (ja)

Priority Applications (3)

Application Number Priority Date Filing Date Title
CN201580002524.7A CN105706062B (zh) 2014-05-27 2015-04-17 车载信息系统及其信息处理方法
EP15799906.1A EP3151124A4 (en) 2014-05-27 2015-04-17 On-board information system and information processing method therefor
US15/125,369 US10009220B2 (en) 2014-05-27 2015-04-17 In-vehicle information system and information processing method thereof

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2014-109539 2014-05-27
JP2014109539A JP6200376B2 (ja) 2014-05-27 2014-05-27 車載情報システム及びその情報処理方法

Publications (1)

Publication Number Publication Date
WO2015182281A1 true WO2015182281A1 (ja) 2015-12-03

Family

ID=54698622

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2015/061847 Ceased WO2015182281A1 (ja) 2014-05-27 2015-04-17 車載情報システム及びその情報処理方法

Country Status (5)

Country Link
US (1) US10009220B2 (enExample)
EP (1) EP3151124A4 (enExample)
JP (1) JP6200376B2 (enExample)
CN (1) CN105706062B (enExample)
WO (1) WO2015182281A1 (enExample)

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR102330380B1 (ko) * 2014-10-28 2021-11-23 현대모비스 주식회사 차량 기반 통신 서비스 검증 시스템
JP6573572B2 (ja) * 2016-04-26 2019-09-11 株式会社日立製作所 ログ情報解析装置およびログ情報解析方法
CN106407480B (zh) * 2016-11-29 2020-02-04 北京世纪高通科技有限公司 一种信息查询方法和系统
CN113873000A (zh) * 2020-06-30 2021-12-31 上海博泰悦臻网络技术服务有限公司 通过无线终端传输车机系统日志的方法
JP7447848B2 (ja) * 2021-03-05 2024-03-12 株式会社デンソー 車両用装置、サーバ、及び通信管理方法
KR102683547B1 (ko) * 2021-05-13 2024-07-10 주식회사 엘지유플러스 Avn 디바이스 진단을 위한 방법 및 장치
US11900137B2 (en) * 2022-02-15 2024-02-13 Sap Se Configurable in-application event logging service
ES2998778T3 (en) * 2022-05-13 2025-02-21 Nagravision Sarl Method of securely streaming digital content over content delivery network
JP2024008630A (ja) * 2022-07-08 2024-01-19 株式会社デンソー 車載機、車両ネットワークシステム

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2003228498A (ja) * 2002-02-05 2003-08-15 Toshiba Corp 履歴データ収集システムおよび履歴データ収集プログラム
JP2014182715A (ja) * 2013-03-21 2014-09-29 Clarion Co Ltd 車載機器システム、携帯端末及び車載機

Family Cites Families (20)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1562119A1 (en) * 2004-02-03 2005-08-10 Alcatel Method for providing a repair service
JP2005275753A (ja) * 2004-03-24 2005-10-06 Denso Corp 車載装置及び車載システム
US8090691B2 (en) * 2004-08-13 2012-01-03 Computer Associates Think, Inc. System and method for variable block logging with log-ahead buffers
US20080122691A1 (en) * 2006-11-27 2008-05-29 Carani Sherry L Tracking system and method with multiple time zone selector, dynamic screens and multiple screen presentations
US20080125965A1 (en) * 2006-11-27 2008-05-29 Carani Sherry L Tracking System and Method with Automatic Map Selector and Geo Fence Defining Features
US20080121690A1 (en) * 2006-11-27 2008-05-29 Carani Sherry L Ubiquitous Tracking System and Method
US20080122656A1 (en) * 2006-11-27 2008-05-29 Carani Sherry L Tracking System and Method with Multiple Language Selector, Dynamic Screens and Multiple Screen Presentations
US20080125964A1 (en) * 2006-11-27 2008-05-29 Carani Sherry L Tracking System and Method with Automatic Map Selector And Geo Fence Defining Features
JP5192226B2 (ja) * 2007-12-27 2013-05-08 株式会社日立製作所 待機系計算機の追加方法、計算機及び計算機システム
JP2009253564A (ja) * 2008-04-04 2009-10-29 Fuji Xerox Co Ltd ログ情報提供装置、ログ管理システム及びプログラム
JP4612715B2 (ja) * 2008-09-05 2011-01-12 株式会社日立製作所 情報処理システム、データ更新方法およびデータ更新プログラム
JP2011239143A (ja) * 2010-05-10 2011-11-24 Denso Corp 記録システム、車載機及び携帯機
US9864772B2 (en) * 2010-09-30 2018-01-09 International Business Machines Corporation Log-shipping data replication with early log record fetching
US9792612B2 (en) * 2010-11-23 2017-10-17 Echostar Technologies L.L.C. Facilitating user support of electronic devices using dynamic matrix code generation
CN102542788B (zh) * 2010-12-30 2014-10-22 上海博泰悦臻电子设备制造有限公司 车载信息控制装置和方法
CN102571877B (zh) * 2010-12-31 2016-03-30 上海博泰悦臻电子设备制造有限公司 车载信息同步服务系统和方法
JP5673391B2 (ja) 2011-06-28 2015-02-18 富士通株式会社 情報処理装置、ログ処理方法、及びプログラム
US9069655B2 (en) * 2011-12-28 2015-06-30 JVC Kenwood Corporation On-vehicle apparatus, and method and computer program for transmitting positional information
JP5767998B2 (ja) * 2012-03-30 2015-08-26 クラリオン株式会社 車載機およびその制御方法と遠隔操作システム
US9459911B2 (en) * 2012-06-29 2016-10-04 International Business Machines Corporation Dynamically adjusting a log level of a transaction

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2003228498A (ja) * 2002-02-05 2003-08-15 Toshiba Corp 履歴データ収集システムおよび履歴データ収集プログラム
JP2014182715A (ja) * 2013-03-21 2014-09-29 Clarion Co Ltd 車載機器システム、携帯端末及び車載機

Non-Patent Citations (1)

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

Also Published As

Publication number Publication date
CN105706062A (zh) 2016-06-22
EP3151124A4 (en) 2018-02-14
US20170099177A1 (en) 2017-04-06
JP2015225473A (ja) 2015-12-14
CN105706062B (zh) 2018-10-16
EP3151124A1 (en) 2017-04-05
US10009220B2 (en) 2018-06-26
JP6200376B2 (ja) 2017-09-20

Similar Documents

Publication Publication Date Title
JP6200376B2 (ja) 車載情報システム及びその情報処理方法
US10560465B2 (en) Real time anomaly detection for data streams
CN105357038B (zh) 监控虚拟机集群的方法和系统
US11175913B2 (en) Elastic application framework for deploying software
JP5018774B2 (ja) 監視装置、監視システム、監視方法およびプログラム
CN109710615B (zh) 数据库的访问管理方法、系统、电子设备和存储介质
US20110153748A1 (en) Remote forensics system based on network
CN111309550A (zh) 应用程序的数据采集方法、系统、设备和存储介质
US9960975B1 (en) Analyzing distributed datasets
CN111046011A (zh) 日志收集方法、系统、节点、电子设备及可读存储介质
CN112506755A (zh) 日志采集方法、装置、计算机设备和存储介质
CN110928934A (zh) 一种用于业务分析的数据处理方法和装置
JP2010128597A (ja) 情報処理装置及び情報処理装置の運用方法
CN107295086B (zh) 集群会话防丢失方法及系统
JP2015064872A (ja) 監視システム、システム及び監視方法
JP4764300B2 (ja) ストリームデータ管理システム、ストリームデータ管理方法およびそのプログラム
JP2021157340A (ja) データ連携システムおよびａｐｉプラットフォーム
US20170223136A1 (en) Any Web Page Reporting and Capture
JP6412641B2 (ja) 通信リンクの送信方法、装置及び端末
KR101146742B1 (ko) ＳａａＳ의 분산된 세션 관리 방법 및 그 관리 시스템
JP2005157727A (ja) ログ処理方法及びその処理プログラム並びに実施システム
US20140365681A1 (en) Data management method, data management system, and data management apparatus
CN117176613B (zh) 一种数据采集方法和装置
CN112882992A (zh) 用于显示信息的方法和装置
US8244746B2 (en) Parallel linking system and parallel linking method

Legal Events

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

Ref document number: 15799906

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 15125369

Country of ref document: US

REEP Request for entry into the european phase

Ref document number: 2015799906

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2015799906

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE