• 专利附录
  • 专利说明
  • 权利要求
  • 类似技术
  • 同族专利
  • 引用文献
  • 法律状态
  • 优先权
    • 专利摘要:
    Method and system for providing diagnostic services for connected devices The service wizard allows users to diagnose and repair connected devices remotely or locally using appropriate information. The diagnostic service wizard includes a knowledge base with semantic models that manage heterogeneous sources of characteristic information distributed in internet locations and external storage locations, typically accessed over the internet. Heterogeneous sources of information include feature profiles device statuses of device histories and / or aggregated information of similar devices from different users, electronic technical manuals and / or user generated content and analyzed knowledge. and aggregated from sources of knowledge.
    公开号:FR3014579A1
    申请号:FR1462164
    申请日:2014-12-10
    公开日:2015-06-12
    发明作者:Tassilo Barth；Mansimar Aneja；Ji Eun Kim；Stefan Jungmayr
    申请人:Robert Bosch GmbH；
    IPC主号:
    专利说明:

    [0001] Field of the Invention The present invention relates to an internet diagnostic wizard for the analysis of devices. The invention relates generally to the field of diagnosing the operation of a device in case of difficulty or failure and more particularly the invention relates to a method and a system for assisting the diagnostic services to find outages connected device. State of the art Complex electrical and electromechanical devices can fail under normal operating conditions. Many such devices are found in homes or other places and the user often does not have the appropriate technical knowledge to repair. However, in many cases, the same users with access to information and / or the assistance of specialized technicians could repair certain failures or restore the correct operation of the device. Although the main source of diagnostic instructions is in the user manual or technical manual associated with the device, such manuals are often difficult for users to understand. In addition, as systems become increasingly complex and interconnected, such as heating, ventilation and air conditioning systems, specialized and experienced staff are needed and often even specialists are faced with systems that are not familiar to them. The Internet as a vast source of information has developed a new opportunity to repair devices. The term "internet system" applies to all internet systems and in particular the internet itself, applying the internet protocol TCP / IP which is accessed by a system of hyperlinks known as the www system or simply web. Although the present description relates to applications directly related to an embodiment using the Internet and www, this does not limit the description that can be applied to other similar systems.
    [0002] On the Internet, some users come together in communities to ask questions, provide information and help. Such communities make it possible to improve the solutions proposed in the user guides since these technical manuals are often very structured, provide concise explanations for technicians and also use specialized, limited terminology. However, these instructions omit useful details about symptoms, causes, and solutions, and only give tips that are reduced to the extreme for diagnosing a failure. More specifically, descriptions of symptoms made by non-specialists such as device users often do not use the usual language used by technicians to describe such symptoms and do not correspond to the standard, standardized code of practice. which is in the user manual. However, community resources describe symptoms using less technical language with broader descriptive terminology and detailed explanations of symptoms and solutions. The defects are presented with their causes. In addition, experts often share their knowledge of alternative and time-saving solutions as opposed to manufacturers' procedures. Overall, community sources allow users to understand and evaluate the feasibility of different solutions in different forms of resources including text, images, photos and videos. Other sources of information are available for diagnostic services and can be found on the internet if we know how to proceed. For example, there are parts catalogs, technical user manuals or data related to manufacturer or vendor devices, such as a list of approved installers. This information is spread across multiple Internet locations and often requires different solutions to access information. Unfortunately all the resources, which are found in paper manuals, electronic files or copies of other information sources accessible by internet do not give information available in the usual way and reliable source. In addition, with the introduction of connected devices, those connected to the Internet provide at least indications of the current operating state of the device that can be used by those who use a community source to diagnose difficulties. Initially, internet networks connect users to existing information. However, as the internet has evolved, there is the internet of things with uniquely identifiable objects, feature devices and a virtual representation of the object that are presented and available on the internet. Many companies routinely control remote control and control of accessible devices. However, currently, the control and control services available via the internet are limited to the phase of putting the product life cycle into effect, that is to say after the purchase of the product 15 by the consumer. In addition, all value-added services, which are possible when the consumer cooperates with the connected device throughout the life cycle of the product from the design to the introduction of the product and thereafter, are not fully utilized. A usual difficulty encountered by a user in different fields is the lack of immediate assistance when the device is in difficulty. Organized and understandable diagnostic solutions for complex devices are not provided as web-based applications that are accessible anywhere where the internet is accessible. Similarly, the information is distributed among 25 different sites often managed by different people of an organization and the information is only available with external management by a different company than the one who made the device. Accordingly, there should be a place on the internet where a community of participants with an interest in one or more devices can access information related to the operation and maintenance of the device. DESCRIPTION AND ADVANTAGES OF THE INVENTION The present invention relates to a semantic knowledge base which makes it possible to access different sources of information via a single interface and / or unified interfaces. While different sources of information even accessible over the internet are often isolated and not related to each other, the present invention provides access to dispersed information sources. The relationship between information in an internet-based system according to the invention makes it possible to determine the extent of difficulties related to a device. Diagnostic solutions with relationships between similar instructions, causes and other entities are obtained from multiple sources of information that previously were only accessible or understood by a senior technician with years of experience. The internet-oriented architecture according to the present invention allows the user to access the diagnostic service anywhere he can access the internet. The connected devices are remotely accessible by the users to enable them to diagnose the state of a device. Diagnostic services are used by users to interact with both physical devices connected to the internet and with diagnostic services when subcomponents / parts are tuned, modified or replaced. The diagnostic service wizard provides the user with the most characteristic information by determining device information such as model number, peripherals, or parts, common faults related to the device connected with the device. history of maintenance, current steps and context in the diagnostic process.
    [0003] The information presented to the user is deduced from the analysis of semantic models that integrate heterogeneous knowledge information distributed and stored on an internal database and a server as well as external knowledge available on the internet or on the web. The semantic knowledge is derived by the identification of the functions inherent in the device and the parts according to the type or the meaning. A diagnostic service component in one embodiment predicts future failures by analyzing device behaviors and predicting a notified failure to the user to take preventative actions. The diagnostic services component has expandable features to assist advanced diagnostic services that are added by analyzing additional data made available over time by similar devices and user profiles.
    [0004] Users participate in diagnostic services through different information channels provided by a platform to share and provide assistance. The disclosed methods and systems provide uniform access to heterogeneous sources of information through a single, unified interface. The methods and systems provide the most characteristic and up-to-date information for users who have difficulties with their connected devices. A method for providing diagnostic services of a device has been developed. This method comprises the following steps of generating an ontology with a server, this ontology comprising the diagnostic model with several diagnostic concepts containing at least the defects, the symptoms, the causes and the solutions and defining the relationships between each concept. and diagnostic data set relating to a device model corresponding to the device, each diagnostic data being associated with at least one of the diagnostic concepts, recording the ontology in a memory accessible to the device. server, to receive a user diagnostic request for the device by the input device, the latter cooperating with the user interface, this user interface being connected to the server by a network, to identify at least one diagnostic concept associated with the diagnostic request by searching for ontology with the server and providing the identified diagnostic concept and the diagnostic data associated with at least this identified diagnostic concept. A system has been developed to provide diagnostic services for a device. The system includes: a memory configured to record an ontology, the ontology includes * a diagnostic model having a set of diagnostic concepts including at least the defects, symptoms, causes and solutions, and defining the relationships between each of the diagnostic concepts, and a set of diagnostic data relating to a device model corresponding to the device, each diagnostic data being associated with at least one of the diagnostic concepts, and a server cooperating with the memory, the server being configured to * receive a diagnostic request from a user of the device via an input device, this input device cooperating with the user interface, this user interface being connected to the server by the intermediate of a network, and * identify at least one diagnostic concept associated with the diagnostic demand by seeking ontology with c the server and outputting at least one identified diagnostic concept and the diagnostic data associated with the diagnostic concept identified by the user. The present invention allows users to virtually immediately obtain online service support and communities to effectively manage diagnostic services. Reactions and actions can be undertaken to resolve user issues during the diagnostic service process, improve system capabilities, and provide solutions through learning and adaptation. Drawings The present invention will be described hereinafter in more detail with the aid of the accompanying drawings, in which: FIG. 1 shows a diagnostic service system configured to allow a user to control and diagnose a state of a Fig. 2 is a block diagram of the Diagnostic Service System diagnostic assistance services of Fig. 1; Fig. 3 is a block diagram of a method for applying the service system of the diagnostic service system; Figure 4 shows a user interface displaying the details of a fault condition, Figure 5 shows a user interface displaying a recommended maintenance step, Figure 6 shows a user interface. displaying the components of a device, Figure 7 shows a user interface showing the location of an identified component in a solution of a problem of the device, the Figure 8 shows a user interface displaying a summary table of the diagnostic session, Figure 9 shows a user interface displaying an invoice for the parts and the work necessary to resolve a malfunction of the device, Figure 10 shows a block diagram of an ontological model for constructing the diagnostic assistance service component of Fig. 2; Fig. 11 shows a user interface displaying a reaction form for a specific diagnosis and fault repair; .
    [0005] DESCRIPTION OF EMBODIMENTS FIG. 1 shows a block diagram of a diagnostics service system 100 configured to allow the user to control and diagnose the state of one or more internet-connected devices 102. service 100 includes an internet-connected diagnostic assistant component 104 via a network (not shown) which according to one embodiment includes any number of different types of networks, including one or more wide area networks, intranets or one or more distributed networks, such as a local area network, a satellite communication network, a public network, a metropolitan area network. The transmission of information from the service component 104 to the internet 102 according to one or more embodiments comprises a wired or wireless link or any other known or later developed element that can provide electronic data to and from connected elements. An A 106 device having a connector is coupled to the Internet 102. A device B 108 without connectors is coupled to an adapter or gate 110 which provides one or more communication stacks for coupling the device to the internet 102. The service component 104 communicates with devices 106 and 108 connected to the internet. The service component 104, according to various embodiments, is stored on a server located at the manufacturer of the device, a device installer, a contractor or other server located on the internet or accessible via the internet 102. The state of the device is set update for the service component 104 over the internet 102 and / or the state of the updated device is recorded as a device history in an internal memory of the service component 104. However, the data storage in other modes of realization is located anywhere, allowing the data to be accessible by the system user. In another embodiment, the state of the device is obtained directly from the device. Accordingly, the state of the device can be determined by the device itself or from another data storage or memory location external to the device. The service component is accessible from any location using the user interface 112 which includes internet connections such as smart phones, tablets, PC personal computers, APPS applications and services. Access to the service components 104 is provided by the interface 112 as is generally known to those skilled in the art. The applications / user interfaces 112 in various embodiments are directly connected to the internet 102 and to the diagnostic assistant service 104 or directly to the diagnostic assistant service 104. FIG. 2 is a block diagram of the diagnostic service system component 104 of diagnostic service system 100 of FIG. 1. Service component 104 includes an ontology model for diagnostic component 200 which comprises a set of diagnostic models. ontology. In this context, an ontology model is an explicit specification of a device design model that is typically oriented to the functions and characteristics of the device. Each of the ontology models is focused on a single product that includes taxonomy of product information including the non-model team and a taxonomy of manufacturer information such as brand, subcomponents and spare parts information. . Many different types of products are included in the diagnostic component 200 which includes similar product type information. The diagnostic component also includes a diagnostic ontology model having a taxonomy that represents the symptoms, defects, causes and solutions for each of the types of products depicted. These ontology models are either defined by manuals, an expert domain, an engineer or are automatically provided programmatically from information given by system users.
    [0006] Companies including manufacturers and service providers have multiple sources of information available internally. These internal data sources include maintenance parts catalogs, technical manuals and human resources related to data for customer use such as the list of licensed installers. The internal data is identified as an internal data source component 202 in Figure 2. Although represented as being compiled as a single data source, the internal data of the service component 104 does not require a physical location to one place. In addition to the internal data sources, the external data sources indicated as external data sources 204 in Figure 2 contain information about the diagnostic products and services, the examples of external data sources include data generated by the data source. user in the community of participants related to the field of products and social media data including videos, texts, images available on the internet. These external data sources are used for other program services. External data sources are identified, stored and cataloged in different data formats, including structured data such as SQL (structured query language) database and unstructured data such as folder or semistructured data such as the HTML hypertext language. The service component 204 includes an extractor component 206 operatively coupled to the internal and external data source component 202, 204. The extractor component 206 includes one or more program packets configured to extract the characteristic information from the data sources. internal and external and load the extracted knowledge into a triple storage component 208. The triple storage or memory component 208 takes the extracted information provided by the extractor component 206 and organizes the information according to the concept descriptions or to model the information. information extracted according to a type of product, defect, symptom and solution. Triple data is a data entity based on subject-predicate-object configuration.
    [0007] The triple storage component 208 includes program components configured to organize the extracted data according to ontology model representations which, in different embodiments, include an RDF resource description frame or a web ontology language. OWL standardized by the WWW Consortium (W3C). Extractor 206 operates periodically to extract new knowledge from internal data sources and external data sources by respective components 202,204. Service component 104 further includes a diagnostic service module or component 210 having one or more program packets configured to provide the diagnostic related services including a remote service status check and / or a guided repair guide with step-by-step instructions. Examples of functionality in the diagnostics service module 210 include in various embodiments the following questions: 1) For a symptom S, what are the possible causes of S and the solutions to remedy S 2) For a component C what solutions and symptoms are concerned by component C 3) For a product P what defects, causes and symptoms can affect the product P 4) For an SO solution, what are the necessary steps to run the SO solution 5) For a maintenance history (sequence of maintenance steps) what is the next maintenance step to be performed in a resolution procedure A learning and matching component 212 is coupled to cooperate with the diagnostic service component 200. The learning and matching component 212 adapts the present information to the knowledge base that is available. for the triple storage component 208. This adapted information is updated in time, continuously to translate the changes in information. The adapted information is based on the analysis of information in the knowledge base with any prior art method for statistical analysis, machine learning and data search. Fig. 3 shows an embodiment of a procedure 300 for constructing the diagnostic service system 100. The procedure 300 comprises the following steps 1 to 6 which correspond to the numbers shown in Fig. 3. 1. Domain of the experts comprising an engineer 302, a diagnostic method model for a selected domain relating to a particular device and a taxonomy of the selected device and sub-components of the device. The results of this step are necessarily the ontology model component 304, such as a diagnostic ontology model and a product ontology model. 2. Information such as spare parts information is grouped into a semantic knowledge database that is present on ontology models. The semantic knowledge database is derived from the Spare Parts / Terminology database 306. 3. Extractor programs are developed to extract information from device technical manuals, community solutions and other sources of knowledge. 308. The extracted information is cataloged and identified by the specialist engineer 302 using metadata, linked information and metadata identifiers, stored in a database 310. In the described embodiment, the information is used. RDF frame as a metadata template. 4. The extracted knowledge is tagged with the ontology concepts that are defined in ontology model component 304. Depending on the relationships defined in the ontologies, one interferes with additional relationships. 5. The extended RDF data is loaded into the triple memory 208 of Figure 2. In addition, an index of textual elements allows quick search access. The user interface program is developed and is available to the end user 312 through a graphical user interface 314. The end user 312 includes the owners and one or more installers who have access to the described ontologies. and databases to configure information as needed. Figs. 4-9 show a set of user interface screens available to a user / participant by the user interface application 112 of Fig. 1. Fig. 4 shows a user interface 400 displaying the details of a fault state generated in response to a search made by the user. The user interface shown includes a lookup table 401. The lookup table allows the user to enter semantic queries by typing the text in a search box or by selecting options from pull-down menus. In the interface screen as presented, the user selects from a number of search topics available in the drop-down menu 402. As shown, the user selects "default" so that the information related to the default or the defect symptoms are retrieved by the diagnostic assistant service component 104. Other research topics available in the drop-down menu include the product type, components, and user manuals. In this example, the user has chosen the fault number 232 that enters a field box 404. The entry is done by typing the number 232 or by locating a drop-down menu available by the field box 404. As soon as the search button 406 is selected, the system provides an output field 408 for the fault 232. The output field 408 of this embodiment identifies the fault as an external switch contact with a more detailed description of the fault. the number of previous events and the number of symptoms 232. The user interface screen 400 further comprises a manual presentation solution corresponding to the button 410 that the user chooses if the recovered fault appears as applying to the symptom that the user has detected. FIG. 5 shows a user interface displaying a recommended maintenance step if the user selects the button 410 of FIG. 4. If selected, a user interface screen 504 corresponding to the step The following is displayed on the user interface 112. The screen 500 is displayed below the solution table of the manual 502 near the search table 401. The table of the solution by the manual 502 includes the information related to the next step in field 504, the history in field 506, the community solutions linked in field 508. Field 504 describes an action to be performed which relates to one or more buttons 510 that the user must select to indicate if the problem has been solved. Field 506 describes the history of past attempts to block the difficulty and includes a date, a user, an exit, a type, and an activity to fix the problem. The text of any of these fields in different embodiments includes a hyperlink text that is useful to the user. For example, any interesting component in a solution is displayed as hyperlinked text. An interesting component may include a part to be replaced by a spare part. Field 508 includes related community solutions including questions asked, identification by date, such as the time, date and identity of the requester as well as the conversation between the user and the individual discussing the solutions of the applicant. problem with the user. Each of the fields in one embodiment contains hyperlinked text for semantically linking the detected components. Figure 6 shows a user interface 600 displaying parts of the device. The parts or components of the device are presented in response to the user selecting hyperlink text "external switch" hyperlink 509 of Fig. 5. By selecting the hyperlink text "external switch", the user interface 600 displays the drawing the "external switch" and additional parts to show the environment in which the external switch is located. In addition, the displayed parts indicate alternatives to the fault state. In some embodiments, the component 602 detail window may be used to allow the user to select the component that he considers or believes to be necessary to repair or that would otherwise be related to the fault diagnosis. of the device. Each of the presented components interacts with the user, i.e. the user selects the component of interest to obtain additional information about the selected component such as common defects, symptoms and causes. related to the component. According to another embodiment, one wonders about the component chosen to display the details. As shown in the user interface 600, the component drawing is available in the component detail window 602. FIG. 7 shows a highlighted window 700 showing the location of a component identified in the procedure of implementation of a solution to the problem of the device. The interesting component is selected in the user interface 600; the selected component may be displayed in the highlighted window 700 as a component of a larger set using the select button 704. An assembly chart 702, for example, is displayed and the location of the selected component is presented in the assembly. A projection button on chart 704 (see also Figure 5) is selected to project or highlight the selected component in the diagram. Figure 8 shows a global session window 800 displaying a summary table of the diagnostic session. The end-of-session button 802 is chosen to display the summary table as an overview of the session. In addition to the summary of the current diagnostic session displayed, there is also the display of previous diagnostic sessions. An invoice button 804 generates an invoice. FIG. 9 shows a global detail session window 900 presenting the bill 902 of the pieces and the work required and / or used to solve the problem of the malfunction of the device in response to the selection of the billing button 804 of FIG. 8. The resulting invoice includes the items that would be used in the device to solve the problem as well as the workload. The total cost is also displayed. The invoice 902 according to one embodiment is the actual invoice generated by the installer who performed the work or who will do the work to remedy the malfunction of the device. The invoice 902 is provided to the user, as an estimate, or as final invoice for parts and services. According to another embodiment, the invoice 902 is generated by and for the end user in the form of a quote, or actual cost of parts and services. The information on the invoice is an indication to the end user indicating the cost so that the end user can decide whether he intends to remedy the malfunction himself. In another embodiment, the "work" entry is linked to a particular installer or service provider and indicates the service costs that will be billed by that particular entity. Although the 902 is presented as a window that opens on the web solutions center screen, other user interface layouts are possible. The window may include a print button or a save button to save the invoice. According to another embodiment, the invoice 902 opens in pdf format of the document that can be registered and / or printed. Other user interfaces are within the scope of the present invention to provide a summary of the bill. FIG. 10 shows an embodiment of the ontology model for diagnostics 200 of FIG. 2. As shown in FIG. 10, the ontology model comprises a knowledge component 220 configured to include a component of defects 222, a symptom component 224, a cause component 226, a solution component 228 and a solution step component 230. The symptom component 224 is configured to provide an epiphenomenon of the defect. The epiphenomenal indication is an indicator of a symptom with more than one indicator indicating the same symptom. The symptom component 224 includes a fault code component provided by the internet-connected device 102 in FIG. 1. A comfort component has an observed, potentially ambiguous symptom (typically a cold room, a burner which is noise) which may indicate some types of defects but are not always available. The fault code provided by the device comprises, according to one embodiment, one of the two types of error code and display code. The fault component 222 includes a detected fault component recognized by the diagnostic unit of the device and a defect described, given as a verbal summary of a symptom description. The detected faults are triggered by a primary symptom and are plotted on a fault code. The cause component 226 has component parts responsible for a particular fault. The configuration cause component 226 determines whether a fault results from improper programming or misuse of the device. A cause of malfunction component is generally associated with a broken component. The causes are detected by checks and are applied to the symptom component 224 by a proprietary string. The solution step component 230 includes a control component which provides an observation of the setting for the purpose of finding the cause of the fault. An action component determines the arrival of a subsequent adjustment variation for the purpose of eliminating the cause. As soon as a solution step is over, there is a maintenance activity instance to perform that is provided to the system user.
    [0008] Solution component 228 provides a solution procedure in a prescribed sequential form. A component of unstructured solutions gives an unorganized set of appropriate instructions to arrive at the solution. An output component 232 provides a positive or negative determination of an output of the procedure to be applied to find a solution. A holding component 234 is configured to allow any end user, installer or technician to find a solution to a symptom related to the scanned device. The maintenance component 234 identifies the user type by the selection of the user by the maintenance component 234. Choosing the user type instructs the knowledge component 220 to perform the analysis of the operations and / or symptoms of the device. The knowledge component 220 configures the type of analysis to be performed based on the type of user. For example, if an end user does the analysis, the presented solutions are configured to be less technical than if the maintenance was done by an installer. A source component 236 provides a link to each diagnostic concept case that is related to sources of information found in the manuals, or is a community source of information. Other embodiments of the ontology model 200 are within the scope of the present invention wherein the knowledge component 220 is configured to encompass more or fewer components as described. In addition, ontology or ontologies allow the description of devices and device states that vary according to the activated device and the anticipated user for the ontological model. Fig. 11 shows a feedback form 1100 in which the user of the diagnostic service, provides the current causes of input of the actions taken for a given fault. The feedback form 1100 has a text field 1104 which receives the feedback text information t. The feedback form 1100 collects the reaction data to allow the training and adaptation module 212 to modify the knowledge of the registered domain in association with the ontology model 200. The diagnostic server 210 optionally transmits the data in reaction to computer systems associated with other service providers and component manufacturers.
    [0009] It should be noted that variants of what has been described above and other features and functions or alternatives are advantageously combined in many other systems, applications or methods. Different prior or unanticipated alternatives, modifications, variations or improvements may therefore be provided to those specialists who are also concerned with the following embodiments. These embodiments are non-limiting examples. First Embodiment: A mechanism that provides an intelligent diagnostic assistant by integrating different resources that are often isolated from each other. Resources include: 1) device profile, device status, device history and / or compiled information for similar devices from different users, 2) electronic technical manuals, and / or 3) user-generated content. internally in the system and externally, and 4) an aggregate and analyzed knowledge of previous sources of knowledge.
    [0010] Second embodiment: a mechanism for building a semantic knowledge base and making the semantic knowledge system interactive via the internet. Third embodiment: a mechanism for extracting useful information from external knowledge with navigation by a browser or forum source and other communities.
    [0011] Fourth embodiment: semantic model of diagnostics applicable to multiple domains. Fifth embodiment: remote diagnostics that know the context and provide the most characteristic information by analyzing the state of the device, prior actions and / or specialists. Sixth embodiment: remote diagnostic service, adaptive, based on user reaction and actions. Figure 11 shows an example of a user interface for receiving a reaction on the occurrence of diagnostic / repair service. Seventh embodiment: a mechanism for learning and adapting diagnostic services according to the user's reactions and actions by applying a new knowledge discovered over time.
    [0012] Eighth embodiment: a mechanism for adding a new value to the diagnostic service by recorded actions, part replacement and time spent for service. An example of new added service values is a service that automatically generates invoices and allows the user to modify the invoice if necessary.25
    权利要求:
    Claims (7)
    [0001]
    CLAIMS 1 °) A method for providing diagnostic services of a connected device to find and predict failures of this device comprising the following steps of: - generating an ontology with a server, the ontology comprising: diagnostic system having a set of diagnostic concepts including at least the defects, symptoms, causes and solutions and defining the relationship between each of the diagnostic concepts, and a diagnostic data set relating to a device model corresponding to device, each diagnostic data being associated with at least one of the diagnostic concepts, - registering the ontology in a memory accessible by the server, - receiving a diagnostic request from a user of the device via an input device, the latter being connected so as to cooperate with the user interface which itself is connected to the server via a network, - identifying at least one diagnostic concept that is associated with the diagnostic request by searching the ontology with the server, outputting the identified concept for at least one diagnostic and the associated diagnostic data to the identified diagnosis concept, for the user, and - take appropriate measures to remedy the faults thus diagnosed.
    [0002]
    2) Method according to claim 1, characterized in that the operation of receiving corresponds to the receipt of a semantic request from the user.
    [0003]
    The method according to claim 1, characterized in that the receiving operation further comprises: displaying a graphic description of a set of parts of the user's device, and receiving a selecting a part of the device by the user with reference to the graphic description of the part set.
    [0004]
    4) Method according to claim 1, characterized in that the identification of at least one diagnostic concept further comprises the following steps of: - identifying at least one defect, a symptom and a cause associated with the request for diagnostic, and - identify at least one solution related to the identified defect, the symptom and the cause.
    [0005]
    Method according to claim 4, characterized in that the output supply comprises diagnostic data output with at least one solution for the user, the diagnostic data comprising at least one procedure for implementing the solution.
    [0006]
    The method according to claim 5, characterized in that the output operation further comprises displaying a graphic image of the device for the user, the graphic description highlighting the parts referenced by the procedure of implementation of the solution.
    [0007]
    7. The method according to claim 1, characterized in that the generating operation further comprises all of the diagnostic information of at least one internet source and at least one external source. for providing diagnostic services of a connected device to find and predict failures of the device characterized in that it comprises: - a memory configured to record an ontology, the ontology comprising: * a diagnostic model having a set of diagnostic concepts, at least one of which includes defects, symptoms, causes and solutions, and defining relationships between each of the diagnostic concepts, and a diagnostic data set relating to the device model corresponding to the device, each diagnostic data being associated with at least one of the diagnostic concepts, and - a server cooperating with the memory and configured to: diagnostic request from a user of the device by an input device, the latter cooperating with the user interface and the latter being connected to the server by a network, * identifying at least one diagnostic concept associated with the diagnostic request by searching the ontology with the server, * output at least the concept of diagnostic and diagnostic data associated with the diagnostic concept identified for the user.and * means to allow the user to take appropriate measures to remedy the failures so diagnosed. 9 °) System according to claim 8, characterized in that the server is further configured to receive a semantic request from the user. 10 °) System according to claim 8, characterized in that the server is further configured to: - display a graphic description of a set of parts of the device to the user, and - receive a selection of parts of the user device with reference to the graphic description of the set of parts. System according to claim 8, characterized in that the server is further configured to - identify at least one fault, a symptom and a cause associated with the diagnostic request, and - identify at least one solution related to the fault, to the symptom and the cause. System according to claim 11, characterized in that the server is further configured to output diagnostic data associated with at least one solution to the user, the diagnostic data comprising at least one diagnostic procedure. implementation of the solution. 13 °) System according to claim 12, characterized in that the server is further configured to display a graphical description of the device of the user, this graphic description highlighting the parts referenced by the implementation procedure of the user. solution. 14 °) System according to claim 8, characterized in that the server is further configured to extract all the diagnostic information from at least one internal source and at least one external source.
    类似技术:
    公开号 | 公开日 | 专利标题
    FR3014579A1|2015-06-12|INTERNET DIAGNOSTIC ASSISTANT FOR DEVICE ANALYSIS
    US8666921B2|2014-03-04|Technical support agent and technical support service delivery platform
    US20160343001A1|2016-11-24|Multi-channel customer support and service
    US20180247648A1|2018-08-30|Machine-learning digital assistants
    US7565338B2|2009-07-21|Method and system for sharing knowledge
    US8161325B2|2012-04-17|Recommendation of relevant information to support problem diagnosis
    US8788875B2|2014-07-22|Remote computer diagnostic system and method
    US7516103B1|2009-04-07|Method and apparatus for facilitating electronic acquisition and maintenance of goods and services via the internet
    US20080034060A1|2008-02-07|System and method for providing network-based technical support to an end user
    CA2714804C|2017-04-25|System and method for providing diagnostic services
    US7890318B2|2011-02-15|Informing troubleshooting sessions with device data
    US20160314627A1|2016-10-27|System and Method for Facilitated Collaboration between Automotive Mechanics
    US20090063175A1|2009-03-05|Methods and systems for providing multiple support options
    JP2002041131A|2002-02-08|Maintenance information management system and method for providing maintenance plan
    US20050172170A1|2005-08-04|Application of live machine data to customer support fault isolation processes
    WO2011083496A1|2011-07-14|Crm application for analysing and generating actionable reports based on activity of users on a product portal
    Geiger2016|Personalized task recommendation in crowdsourcing systems
    US9014365B1|2015-04-21|Systems and methods for state information exchange
    Tsai et al.2003|Ontology-mediated integration of intranet web services
    US11157706B2|2021-10-26|Omnichannel data communications system using artificial intelligence | based machine learning and predictive analysis
    FR3014585A1|2015-06-12|SYSTEM AND METHOD FOR MANAGING PRODUCT SERVICE PRODUCTS AND PARTICIPANTS BY INTERNET
    KR102260822B1|2021-06-07|Scanning and managing apparatus on cloud security compliance
    CN113779128A|2021-12-10|Medical data system docking method, device, equipment and storage medium
    LUCKY2017|User-Driven Composition of Web APIs
    Candiello et al.2009|Advanced quality tools for egovernment services
    同族专利:
    公开号 | 公开日
    WO2015086448A1|2015-06-18|
    EP3080718A1|2016-10-19|
    US20160306691A1|2016-10-20|
    FR3014579B1|2018-02-09|
    US10019305B2|2018-07-10|
    引用文献:
    公开号 | 申请日 | 公开日 | 申请人 | 专利标题
    JPH0830458A|1994-07-20|1996-02-02|Hitachi Inf Syst Ltd|Problem solution support system|
    EP1236986A2|2001-02-05|2002-09-04|The Boeing Company|Diagnostic system and method|
    WO2009077776A2|2007-12-18|2009-06-25|Bae Systems Plc|Assisting failure mode and effects analysis of a system comprising a plurality of components|
    US20100057677A1|2008-08-27|2010-03-04|Sap Ag|Solution search for software support|
    US20100121841A1|2008-11-13|2010-05-13|Microsoft Corporation|Automatic diagnosis of search relevance failures|
    WO2010142977A1|2009-06-12|2010-12-16|Bae Systems Plc|Assisting failure mode and effects analysis of a system|
    US6535865B1|1999-07-14|2003-03-18|Hewlett Packard Company|Automated diagnosis of printer systems using Bayesian networks|
    US7171585B2|2003-11-26|2007-01-30|International Business Machines Corporation|Diagnosing faults and errors from a data repository using directed graphs|
    US7890318B2|2007-05-23|2011-02-15|Xerox Corporation|Informing troubleshooting sessions with device data|
    US8738607B2|2010-05-11|2014-05-27|International Business Machines Corporation|Extracting portions of an abstract database for problem determination|
    US9413893B2|2012-04-05|2016-08-09|Assurant, Inc.|System, method, apparatus, and computer program product for providing mobile device support services|
    US8977909B2|2012-07-19|2015-03-10|Dell Products L.P.|Large log file diagnostics system|US20150199626A1|2014-01-10|2015-07-16|Bank Of America Corporation|Incident Recordation and Repair|
    US9977415B2|2015-07-03|2018-05-22|Afero, Inc.|System and method for virtual internet of thingsdevices and hubs|
    JP6631908B2|2015-09-07|2020-01-15|パナソニックＩｐマネジメント株式会社|Information processing apparatus, failure cause identification method, and program|
    US20170286204A1|2016-04-04|2017-10-05|Honeywell International Inc.|Fault propagation in a building automation system|
    SE542124C2|2016-06-17|2020-02-25|Irisity Ab Publ|A monitoring system for security technology|
    US10747606B1|2016-12-21|2020-08-18|EMC IP Holding Company LLC|Risk based analysis of adverse event impact on system availability|
    US10621026B2|2017-06-04|2020-04-14|Apple Inc.|Auto bug capture|
    US20200136924A1|2018-10-31|2020-04-30|Hewlett Packard Enterprise Development Lp|Network Device Snapshot|
    US11249872B1|2020-06-26|2022-02-15|Xilinx, Inc.|Governor circuit for system-on-chip|
    法律状态:
    2015-12-18| PLFP| Fee payment|Year of fee payment: 2 |
    2016-10-14| PLSC| Publication of the preliminary search report|Effective date: 20161014 |
    2016-12-21| PLFP| Fee payment|Year of fee payment: 3 |
    2017-12-19| PLFP| Fee payment|Year of fee payment: 4 |
    2019-12-19| PLFP| Fee payment|Year of fee payment: 6 |
    2020-12-18| PLFP| Fee payment|Year of fee payment: 7 |
    优先权:
    申请号 | 申请日 | 专利标题
    US201361914647P| true| 2013-12-11|2013-12-11|
    US61/914647|2013-12-11|
    [返回顶部]