Instruction file pushing method and device, equipment and medium

Abstract

The invention relates to a description file pushing method and device, equipment and a medium. The method comprises the following steps: after a user terminal is connected with an intelligent device, determining whether the user terminal is connected with the intelligent device for the first time; if the user terminal is connected with the intelligent device for the first time, obtaining device information of the intelligent device and a user tag of the user terminal; on the basis of the equipment information, default description files corresponding to the equipment information are obtained from a description file library, and the default description files corresponding to the equipment information are stored in the description file library; and generating and pushing a personalized description file to the user terminal according to the user tag and the default description file. According to the method, when the user terminal is connected with the intelligent device for the first time, the default description file is obtained through the device information, the default description file is adjusted and modified based on the user tag, the personalized description file exclusive to the user is obtained, and finally the personalized description file is pushed to the user terminal.

Description

TECHNICAL FIELD

[0001] The present application belongs to the field of intelligent electrical appliances, and particularly relates to a method and device for pushing instruction files, an equipment and a medium. BACKGROUND

[0002] With the development of science and technology and the increasing use demand of people, more and more intelligent devices begin to appear in people's daily life. Since the program functions, control parameters and the like contained in different types of intelligent devices have great differences, the user needs to know the instruction file in advance when using the intelligent device.

[0003] In the prior art, in order to avoid the omission of the instruction file and the fact that the user cannot accurately know the program functions, control parameters and the like contained in the intelligent device, all relevant matters are usually listed in detail in the instruction file.

[0004] However, different users have different preferences for the same intelligent device, and the user needs to spend a lot of time when searching for the information needed by himself in the instruction file. SUMMARY

[0005] In order to solve the above problems in the prior art, that is, in order to facilitate the user to quickly find the information needed by himself from the device instruction file when facing different intelligent devices, the present application provides a method and device for pushing instruction files, an equipment and a medium.

[0006] In a first aspect, the present application provides a method for pushing instruction files, comprising:

[0007] After the user terminal is connected to the intelligent device, it is determined whether the user terminal is connected to the intelligent device for the first time;

[0008] If the user terminal is connected to the intelligent device for the first time, the device information of the intelligent device and the user label of the user terminal are obtained;

[0009] Based on the device information, the default instruction file corresponding to the device information is obtained from the instruction file library, wherein the instruction file library stores the default instruction file corresponding to each device information respectively;

[0010] According to the user label and the default instruction file, a personalized instruction file is generated and pushed to the user terminal.

[0011] In a possible implementation manner, the default instruction file contains a plurality of default instruction information, and the generation of the personalized instruction file according to the user label and the default instruction file comprises:

[0012] The association degree between each default instruction information in the default instruction file and the user label is obtained.

[0013] The default description information with the association degree higher than the preset association degree is taken as personalized description information, and the personalized description information is written into a personalized description file;

[0014] The default description information with the association degree not higher than the preset association degree is taken as to-be-deleted description information, and the to-be-deleted description information is written into a to-be-deleted description file.

[0015] In a possible implementation, the obtaining of the association degree of each default description information in the default description file and the user tag comprises:

[0016] obtaining feature information of each default description information, wherein the feature information comprises applicable population information;

[0017] when the user tag does not satisfy the applicable population information, determining that the association degree of the default description information and the user tag is not higher than a preset association degree;

[0018] when the user tag satisfies the applicable population information, determining that the association degree of the default description information and the user tag is higher than a preset association degree.

[0019] In a possible implementation, before the obtaining of the user tag of the user terminal, the method further comprises:

[0020] obtaining basic information and historical use data of the user terminal;

[0021] determining a user tag according to the basic information and the historical use data.

[0022] In a possible implementation, after the generating and pushing of the personalized description file to the user terminal according to the user tag and the default description file, the method further comprises:

[0023] obtaining feedback information of the user terminal to the personalized description file, wherein the feedback information comprises confirmation and modification;

[0024] if the feedback information is the confirmation, deleting the to-be-deleted description file, and establishing a binding relationship of the personalized description file, the user terminal and the intelligent device, and storing the binding relationship in the description file library.

[0025] In a possible implementation, if the feedback information is the modification, the method further comprises:

[0026] sending the to-be-deleted description file to the user terminal;

[0027] obtaining a selection operation of the user terminal on the to-be-deleted description information in the to-be-deleted description file;

[0028] writing the to-be-deleted description information selected by the user terminal into the personalized description file, and deleting the to-be-deleted description file.

[0029] In a possible implementation, the method further includes:

[0030] if the user terminal is not connected to the smart device for the first time, when the description file obtaining request of the user terminal is obtained, searching the personalized description file bound by the user terminal and the smart device from the description file library;

[0031] pushing the personalized description file bound by the user terminal and the smart device to the user terminal.

[0032] In a second aspect, the application provides a description file pushing device, including:

[0033] a first processing module configured to determine whether the user terminal is connected to the smart device for the first time after the user terminal is connected to the smart device;

[0034] a second processing module configured to obtain device information of the smart device and a user tag of the user terminal if the user terminal is connected to the smart device for the first time;

[0035] a third processing module configured to obtain a default description file corresponding to the device information from a description file library based on the device information, wherein the description file library stores a default description file corresponding to each device information respectively;

[0036] a fourth processing module configured to generate and push a personalized description file to the user terminal according to the user tag and the default description file.

[0037] In a third aspect, the application provides a description file pushing device, including at least one processor and a memory;

[0038] the memory stores computer execution instructions;

[0039] the at least one processor executes the computer execution instructions stored in the memory, so that the at least one processor executes the description file pushing method as described above.

[0040] In a fourth aspect, the application provides a computer readable storage medium, which stores a computer program, and the computer program is executed by a processor to implement the steps of the description file pushing method as described above.

[0041] The application provides a description file pushing method, device, equipment and medium. After a user terminal connects an intelligent device, it is determined whether the user terminal connects the intelligent device for the first time. If the user terminal connects the intelligent device for the first time, device information of the intelligent device and a user label of the user terminal are acquired. Based on the device information, a default description file corresponding to the device information is acquired from a description file library. The description file library stores a default description file corresponding to each device information. According to the user label and the default description file, a personalized description file is generated and pushed to the user terminal.

[0042] In the above method, when the user terminal connects the intelligent device for the first time, the default description file is acquired through the device information of the intelligent device, and the personalized description file adapted to the user label is obtained based on the user label of the user terminal and the default description file, so that the user can quickly acquire the device application description information required by the user from the personalized description file, and the efficiency of searching and using information by the user is improved. BRIEF DESCRIPTION OF DRAWINGS

[0043] The accompanying drawings, which are incorporated herein and constitute part of the specification, illustrate embodiments consistent with the application and, together with the description, serve to explain the principles of the application.

[0044] Figure 1 An application scenario diagram provided for an embodiment of the application;

[0045] Figure 2 A flow of a description file pushing method provided for an embodiment of the application Figure 1 ;

[0046] Figure 3 A flow of a description file pushing method provided for an embodiment of the application Figure 2 ;

[0047] Figure 4 A flow of a description file pushing method provided for an embodiment of the application Figure 3 ;

[0048] Figure 5 A structural diagram of a description file pushing device provided for an embodiment of the application;

[0049] Figure 6 A hardware diagram of a description file pushing device provided for an embodiment of the application.

[0050] Through the above drawings, the specific embodiments of the application have been shown, and more detailed descriptions will be given in the following. The drawings and the text description are not intended to limit the scope of the concept of the application by any means, but to illustrate the concept of the application to those skilled in the art by referring to specific embodiments. DETAILED DESCRIPTION

[0051] In order to make the objects, technical solutions and advantages of the present application clearer, the technical solutions in the present application will be described clearly and completely below with reference to the drawings in the present application. Obviously, the described embodiments are only some of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative work fall within the scope of protection of the present application.

[0052] The terms "first", "second", "third", "fourth" and the like in the description, claims, and drawings of the present application (if any) are used to distinguish similar objects, and do not necessarily have to describe a particular sequential or chronological order. It should be understood that the data thus used can be interchanged under appropriate circumstances, so that the embodiments of the present application described herein can be implemented in an order other than that illustrated or described herein.

[0053] In the embodiments of the present application, the words "exemplary" or "for example" are used to mean example, illustration, or description. Any embodiment or design solution described as "exemplary" or "for example" in the present application should not be interpreted as being more preferred or having more advantages than other embodiments or design solutions. Rather, the use of "exemplary" or "for example" is intended to present the relevant concept in a particular manner.

[0054] With the development of science and technology and the update iteration of smart appliance technology, more and more smart devices begin to enter people's field of vision. The program functions, control parameters, etc. of these smart devices are also in the process of continuous improvement and perfection, so as to improve people's quality of life and efficiency. When facing different categories of smart devices, people can clearly and completely know the program functions contained in the device and how to control the device to run by using the instruction file.

[0055] However, the traditional instruction file cannot adapt to the use needs and habits of different users, resulting in the need for users to read the instruction file throughout when using the smart device, so as to obtain the information required by themselves.

[0056] Therefore, the present application proposes a personalized pushing method of smart device instruction file. After judging that the user terminal is connected to the smart device for the first time, the device information of the smart device and the user label of the user terminal are obtained. Then, the device information is used to search for the default instruction file corresponding to the device information in the instruction file library storing a large number of default instruction files. After searching, the default instruction file is adjusted and modified based on the user label to obtain a personalized instruction file belonging to the user. Finally, the personalized instruction file is pushed to the user terminal.

[0057] The following will be described in combination with Figure 1The application scenario of the present application is described.

[0058] Figure 1 An application scenario diagram is provided for an embodiment of the present application. As shown in the figure, the scenario includes a server end 101, a user terminal 102 (taking a smart phone as an example) and a smart device 103 (taking a smart washing machine as an example). The user terminal 102 can also be other devices that can interact with the server end 101 and the smart device 103, such as a notebook computer, a smart bracelet and a tablet computer, etc. Similarly, the smart device 103 can also be a smart dryer, a sweeping robot and an air conditioner, etc. In this embodiment, the execution subject is the server end 101. Figure 1

[0059] The user terminal 102 can receive the personalized instruction file pushed by the server end 101 and can display the personalized instruction file on the user terminal 102 for the user to view in detail.

[0060] The smart device 103 can send device information to the server end 101. The connection mode of the smart device 103 and the user terminal 102 is not limited in this embodiment, for example, the connection can be made by scanning a two-dimensional code, and the connection can also be made by a verification code, etc.

[0061] The server end 101 can obtain the device information of the smart device 103 and can maintain the user tag of the user terminal 102. The server end 101 is also provided with an instruction file library, which stores the default instruction file corresponding to each device information, the personalized instruction file and the binding relationship of the user terminal 102 and the smart device 103.

[0062] When the user terminal 102 is connected to the smart device 103, the server end 101 will first determine whether they are connected for the first time. If so, the server end 101 will obtain the device information of the smart device 103 and the user tag of the user terminal 102, then obtain the default instruction file corresponding to the device information from the instruction file library based on the device information, and finally adjust and modify the default instruction file according to the user tag to obtain the personalized instruction file, and push the personalized instruction file to the user terminal 102.

[0063] Based on the mutual cooperation between the above-mentioned devices, the adaptation degree of the device instruction file and the user characteristics can be improved, and the efficiency of the user to find and use the device instruction information can also be improved.

[0064] The technical solutions of the present application and how the technical solutions of the present application solve the above-mentioned technical problems will be described in detail in the following specific embodiments. The following specific embodiments can be implemented independently, or can be combined with each other. For the same or similar concepts or processes, some embodiments can not be described again. ​

[0065] Figure 2 A flowchart of a method for pushing explanatory documents provided in this application embodiment Figure 1 .like Figure 2 As shown, the method includes:

[0066] S201. After the user terminal connects to the smart device, determine whether the user terminal is connecting to the smart device for the first time.

[0067] In the above scheme, if the user terminal is connecting to the smart device for the first time, the user manual of the smart device needs to be pushed to the user terminal so that the user can know how to use the smart device based on the user manual; if the user terminal is not connecting to the smart device for the first time, it means that the user terminal has already obtained the user manual before.

[0068] S202. If the user terminal is connecting to the smart device for the first time, obtain the device information of the smart device and the user tag of the user terminal.

[0069] In this step, after confirming that the two are connecting for the first time, it is necessary to push the device user manual to the user terminal. The device information can be used to identify the type and model of the smart device, thereby distinguishing the smart device. Due to individual differences, different users have different needs for using smart devices. Therefore, user manuals adapted to user characteristics can be generated based on the user tags of the user terminal.

[0070] In this embodiment, user tags for the user terminal need to be established in advance. User tags for the user terminal can be established based on the user terminal's basic information such as age, gender, occupation, as well as past habits, preferences, and historical data of using smart devices. For example, the user terminal's basic information and historical usage data can be obtained; and the user tags can be determined based on the basic information and historical usage data.

[0071] S203. Based on the device information, obtain the default specification file corresponding to the device information from the specification file library, wherein the specification file library stores the default specification file corresponding to each device information.

[0072] In the above scheme, different smart devices correspond to different device information, and different device information corresponds to different default instruction files. The default instruction file can be a file that fully explains the program functions, control parameters and other related matters of the smart device, or it can be a general instruction file for the smart device.

[0073] S204. Generate and push personalized instruction files to the user's terminal based on user tags and default instruction files.

[0074] In the above solution, after determining the default instruction file corresponding to the smart device, the default instruction file can be optimized according to the user tags to obtain a personalized instruction file adapted to the user tags, so that the user can view a more concise and clear device usage instructions on the user terminal.

[0075] If the user terminal is not connecting to the smart device for the first time, it means that a personalized instruction file has been generated and sent to the user terminal before. In this case, the personalized instruction file can be directly found from the instruction file library and pushed. For example, if the user terminal is not connecting to the smart device for the first time, when the user terminal requests the instruction file, the personalized instruction file bound to the user terminal and the smart device is found from the instruction file library; and the personalized instruction file bound to the user terminal and the smart device is pushed to the user terminal.

[0076] In this embodiment of the application, when the user terminal connects to the smart device for the first time, a default instruction file is obtained through the device information of the smart device, and a personalized instruction file adapted to the user tag is obtained based on the user tag of the user terminal and the aforementioned default instruction file. This enables the user to quickly obtain the device-appropriate instruction information they need from the personalized instruction file, thereby improving the efficiency of the user in finding and using information.

[0077] The following is combined Figure 3 The following specific embodiments illustrate the implementation process of generating personalized documentation based on user tags and default documentation in the documentation push method of this application.

[0078] Figure 3 A flowchart of a method for pushing explanatory documents provided in this application embodiment Figure 2 .like Figure 3 As shown, the method includes:

[0079] S301. Obtain the feature information of each default instruction in the default instruction file. The feature information includes the applicable population information. The default instruction file contains multiple default instruction information.

[0080] In this step, user tags can reflect a user's personal status and smart device usage. Therefore, the correlation between the default instruction information in the default instruction file and the user tags can be determined based on the type of user group.

[0081] S302. When the user tags meet the applicable population information, determine that the correlation between the default description information and the user tags is higher than the preset correlation.

[0082] In the above scheme, if the user tags match the applicable user type of the default description information, it can be considered that the correlation between the user tags and the default description information is high and exceeds the preset correlation.

[0083] S303, write the default explanation information with the association degree higher than the preset association degree as the personalized explanation information into the personalized explanation file.

[0084] In this step, if the association degree between the user tag and a certain default explanation information is higher than the preset association degree, it indicates that the default explanation information is the explanation information that the user needs to know, and the default explanation information can be written into the personalized explanation file.

[0085] S304, when the user tag does not satisfy the applicable population information, it is determined that the association degree between the default explanation information and the user tag is not higher than the preset association degree.

[0086] In the above scheme, the applicable population type of the user tag and the default explanation information is not matched, that is, the association degree between the user tag and the default explanation information is considered to be low, and it is impossible to exceed the preset association degree.

[0087] For example, taking a smart washing machine as an example, the default explanation file of the smart washing machine contains the related explanation of the child lock. The child lock is applicable to the population containing children. If the user tag indicates that there are children in the user's family, it is considered that the association degree between the child lock related explanation and the user tag is higher than the preset association degree. If the user tag indicates that there are no children in the user's family, it is considered that the association degree between the child lock related explanation and the user tag is not higher than the preset association degree.

[0088] S305, write the default explanation information with the association degree not higher than the preset association degree as the to-be-deleted explanation information into the to-be-deleted explanation file.

[0089] In this step, if the association degree between the user tag and a certain default explanation information is not higher than the preset association degree, it indicates that the default explanation information is very likely to be the explanation information that the user does not need to know, and at this time, the default explanation information can be written into the to-be-deleted explanation file and temporarily retained.

[0090] Similarly, taking the smart washing machine as an example, if the association degree between the child lock related explanation and the user tag is higher than the preset association degree, the related explanation of the child lock is written into the personalized explanation file. If the association degree between the child lock related explanation and the user tag is not higher than the preset association degree, the related explanation of the child lock is written into the to-be-deleted explanation file.

[0091] In the embodiment of the application, the association degree between the user tag and the default explanation information is determined through the user tag and the applicable population information of each default explanation information. Only when the user tag satisfies the applicable population information, it is considered that the association degree between the two is above the preset threshold, and the default explanation information is written into the personalized explanation file.

[0092] The above is only an example of the application, and the application is not limited to the above example. Figure 4And specific embodiments illustrate the description file pushing method of the present application, after pushing the personalized description file to the user terminal, the implementation process of the personalized description file is adjusted according to the user feedback.

[0093] Figure 4 The flow of a description file pushing method provided by the embodiment of the present application Figure 3 As shown in Figure 4 , the method comprises:

[0094] S401, obtaining the feedback information of the user terminal to the personalized description file, the feedback information comprising confirmation and modification.

[0095] In the above scheme, after the default description file is optimized according to the user label to obtain the personalized description file adapted to the user, it is further needed to determine whether the user is satisfied with the optimized personalized description file according to the feedback of the user, and when the user is not satisfied, the modification and adjustment are timely carried out.

[0096] S402, if the feedback information is confirmation, the to-be-deleted description file is deleted, and the binding relationship of the personalized description file, the user terminal and the intelligent device is established, and the binding relationship is stored in the description file library.

[0097] In this step, if the user is satisfied with the optimized personalized description file, the to-be-deleted description file can be immediately deleted to release the storage space, and then the personalized description file, the user terminal and the intelligent device are bound, and the binding relationship is stored in the description file library, so that when the user terminal connects the intelligent device subsequently, the personalized description file bound is directly fed back to the user terminal.

[0098] S403, if the feedback information is modification, the to-be-deleted description file is sent to the user terminal.

[0099] In the above scheme, if the user is not satisfied with the optimized personalized description file, the to-be-deleted description file is sent to the user terminal, so that the user terminal selects the description information in the to-be-deleted description file which the user wants to supplement in the personalized description file.

[0100] S404, obtaining the selection operation of the user terminal to the to-be-deleted description information in the to-be-deleted description file.

[0101] In this step, the user can view all the to-be-deleted description information in the to-be-deleted description file on the user terminal, and the to-be-deleted description information can be selected in the process of the user viewing, so as to be added to the previous personalized description file subsequently.

[0102] S405, the to-be-deleted description information selected by the user terminal is written into the personalized description file, and the to-be-deleted description file is deleted.

[0103] In the above scheme, the user-checked to-be-deleted instruction information is written into the personalized instruction file to perfect the personalized instruction file according to the user's will, and then the to-be-deleted instruction file is deleted to release the storage space.

[0104] In the embodiment of the application, whether the personalized instruction file is secondarily optimized is determined according to the feedback of the user terminal to the personalized instruction file. If the user terminal confirms the personalized instruction file, secondary optimization is not needed. If the feedback of the user terminal is modification, the previously generated to-be-deleted instruction file is displayed to the user, and after the user selects the desired to-be-deleted instruction information, the selected to-be-deleted instruction information is added to the personalized instruction file to perfect the instruction file.

[0105] In combination with the above embodiments, the instruction file pushing method provided by the embodiment of the application, when the user terminal connects the smart device, first determines whether the user terminal is first connected to the smart device. If the user terminal is first connected to the smart device, the device information of the smart device and the user tag of the user terminal are obtained. Then, the device information is used to search for the default instruction file corresponding to the device information in the instruction file library storing a large number of default instruction files. After the default instruction file is found, the default instruction file is modified based on the user tag to obtain the personalized instruction file belonging to the user. Finally, the personalized instruction file is pushed to the user terminal. If the user terminal is not first connected to the smart device, the personalized instruction file bound to the user terminal and the smart device is directly searched from the instruction file library, and then the personalized instruction file is pushed to the user terminal.

[0106] Figure 5 A structural schematic diagram of an instruction file pushing device provided by the embodiment of the application is shown in FIG. 1. Figure 5 As shown in FIG. 1, the instruction file pushing device can include various functional modules for implementing the above instruction file pushing method, and any functional module can be realized by software and / or hardware.

[0107] For example, the instruction file pushing device can include a first processing module 501, a second processing module 502, a third processing module 503, and a fourth processing module 504.

[0108] The first processing module 501 is configured to determine whether the user terminal is first connected to the smart device after the user terminal connects the smart device.

[0109] The second processing module 502 is configured to obtain the device information of the smart device and the user tag of the user terminal if the user terminal is first connected to the smart device.

[0110] The third processing module 503 is configured to acquire a default instruction file corresponding to the device information from an instruction file library based on the device information, wherein the instruction file library stores a default instruction file corresponding to each device information.

[0111] The fourth processing module 504 is configured to generate and push a personalized instruction file to the user terminal according to the user label and the default instruction file.

[0112] Optionally, the second processing module 502 is further configured to, if the user terminal is not connected to the smart device for the first time, find a personalized instruction file bound to the user terminal and the smart device from the instruction file library when the instruction file acquisition request of the user terminal is acquired, and push the personalized instruction file bound to the user terminal and the smart device to the user terminal.

[0113] Optionally, the fourth processing module 504 is further configured to acquire basic information and historical use data of the user terminal, and determine the user label according to the basic information and the historical use data.

[0114] Optionally, the fourth processing module 504 is further configured to acquire feature information of each default instruction information, the feature information including applicable population information, determine that the association degree of the default instruction information and the user label is not higher than a preset association degree when the user label does not satisfy the applicable population information, and determine that the association degree of the default instruction information and the user label is higher than the preset association degree when the user label satisfies the applicable population information.

[0115] Optionally, the fourth processing module 504 is further configured to acquire feedback information of the user terminal on the personalized instruction file, the feedback information including confirmation and modification, delete the to-be-deleted instruction file and establish a binding relationship among the personalized instruction file, the user terminal and the smart device if the feedback information is the confirmation, and store the binding relationship in the instruction file library.

[0116] Optionally, the fourth processing module 504 is further configured to, if the feedback information is the modification, send the to-be-deleted instruction file to the user terminal, acquire a selection operation of the user terminal on the to-be-deleted instruction information in the to-be-deleted instruction file, and write the to-be-deleted instruction information selected by the user terminal into the personalized instruction file and delete the to-be-deleted instruction file.

[0117] ​The specification file pushing apparatus is used for executing the technical solutions provided by the foregoing specification file pushing method embodiments, and has similar implementation principles and technical effects to those of the foregoing method embodiments, which will not be described here again.

[0118] The application further provides a specification file pushing device, comprising at least one processor and a memory.

[0119] The memory stores computer execution instructions.

[0120] The at least one processor executes the computer execution instructions stored in the memory, so that the at least one processor executes the specification file pushing method.

[0121] Figure 6 A hardware schematic diagram of the specification file pushing device provided by the embodiment of the application is shown in the figure. Figure 6 As shown in the figure, the specification file pushing device 60 provided by the embodiment comprises at least one processor 601 and a memory 602. The device 60 further comprises a communication component 603. The processor 601, the memory 602 and the communication component 603 are connected through a bus 604.

[0122] In the specific implementation process, the at least one processor 601 executes the computer execution instructions stored in the memory 602, so that the at least one processor 601 executes the specification file pushing method as described above.

[0123] The specific implementation process of the processor 601 can refer to the method embodiments described above, which has similar implementation principles and technical effects, and will not be described here again.

[0124] In the above Figure 6 As shown in the embodiment, it should be understood that the processor can be a central processing unit (English: Central Processing Unit, for short: CPU), and can also be other general-purpose processors, digital signal processors (English: Digital Signal Processor, for short: DSP), application specific integrated circuits (English: Application Specific Integrated Circuit, for short: ASIC) and the like. The general-purpose processor can be a microprocessor, or the processor can also be any conventional processor, etc. The steps of the method disclosed in the application can be directly embodied as the execution of the hardware processor, or executed by the combination of hardware and software modules in the processor.

[0125] The memory can contain a random access memory (Random Access Memory, for short: RAM), and can also include a non-volatile memory (Non-volatile Memory, for short: NVM), for example, at least one disk memory.

[0126] The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, the bus in the drawings of the present application does not limit to only one bus or one type of bus.

[0127] The present application also provides a computer readable storage medium, which stores computer execution instructions, and when a processor executes the computer execution instructions, the method for pushing a statement file is realized.

[0128] The computer readable storage medium described above can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk. The readable storage medium can be any available medium that can be accessed by a general-purpose or special-purpose computer.

[0129] An exemplary readable storage medium is coupled to the processor, so that the processor can read information from the readable storage medium, and can write information to the readable storage medium. Of course, the readable storage medium can also be a component of the processor. The processor and the readable storage medium can be located in an application specific integrated circuit (ASIC). Of course, the processor and the readable storage medium can also exist as discrete components in the device.

[0130] The division of the units is only a logical functional division, and in actual implementation, there can be another division manner, for example, a plurality of units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between the units or components shown or discussed can be indirect coupling or communication connection through some interfaces, devices or units, which can be electrical, mechanical or other forms.

[0131] The units described as separate components may or may not be physically separate, and the components displayed as units may or may not be physical units, i.e. may be located in one place, or may be distributed on multiple network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the embodiment scheme.

[0132] In addition, the functional units in various embodiments of the application can be integrated in one processing unit, or each unit can exist physically, or two or more units can be integrated in one unit.

[0133] If the functions are realized in the form of software functional units and sold or used as independent products, they can be stored in a computer readable storage medium. Based on this understanding, the technical solutions of the application or the part of the prior art that essentially contributes to the prior art or part of the technical solutions can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes a plurality of instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in various embodiments of the application. The aforementioned storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM, Read-Only Memory), a random access memory (RAM, Random Access Memory), a magnetic disk or an optical disk, and various media that can store program codes.

[0134] Those skilled in the art can understand that all or part of the steps of the above-mentioned method embodiments can be completed by program instruction related hardware. The aforementioned program can be stored in a computer readable storage medium. The program executes the steps of the above-mentioned method embodiments when executed; and the aforementioned storage medium includes: ROM, RAM, magnetic disk or optical disk, and various media that can store program codes.

[0135] So far, the technical solutions of the application have been described in combination with the preferred embodiments shown in the drawings, but those skilled in the art can easily understand that the protection scope of the application is obviously not limited to these specific embodiments, and the above embodiments are only used to illustrate the technical solutions of the application, not to limit it; although the application has been described in detail with reference to the above embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the above embodiments, or make equivalent replacement for part or all of the technical features; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the scope of the technical solutions of the embodiments of the application.

Claims

1. A method for pushing instructional documents, characterized in that, include: After the user terminal connects to the smart device, it is determined whether the user terminal is connecting to the smart device for the first time; If the user terminal connects to the smart device for the first time, then the device information of the smart device and the user tag of the user terminal are obtained; Based on the device information, a default specification file corresponding to the device information is obtained from the specification file library, wherein the specification file library stores a default specification file corresponding to each device information. Based on the user tags and the default description file, a personalized description file is generated and pushed to the user terminal.

2. The method according to claim 1, characterized in that, The default description file contains multiple default description information. The step of generating a personalized description file based on the user tag and the default description file includes: Obtain the correlation degree between each default description information in the default description file and the user tag; The default description information with a correlation higher than the preset correlation is used as personalized description information, and the personalized description information is written into the personalized description file; The default description information with a correlation degree not higher than the preset correlation degree is used as the description information to be deleted, and the description information to be deleted is written into the description file to be deleted.

3. The method according to claim 2, characterized in that, The step of obtaining the correlation between each default description information in the default description file and the user tag includes: Obtain the feature information of each default description, including the applicable population information; When the user tag does not meet the applicable population information, it is determined that the correlation between the default description information and the user tag is not higher than the preset correlation. When the user tag meets the applicable population information, it is determined that the correlation between the default description information and the user tag is higher than the preset correlation.

4. The method according to claim 3, characterized in that, Before obtaining the user tag of the user terminal, the method further includes: Obtain the basic information and historical usage data of the user terminal; User tags are determined based on the basic information and the historical usage data.

5. The method according to claim 3, characterized in that, After generating and pushing a personalized instruction file to the user terminal based on the user tag and the default instruction file, the method further includes: Obtain feedback information from the user terminal regarding the personalized description file, including confirmation and modification; If the feedback information is confirmation, the instruction file to be deleted is deleted, and a binding relationship is established between the personalized instruction file, the user terminal, and the smart device, and the binding relationship is stored in the instruction file library.

6. The method according to claim 5, characterized in that, If the feedback information is a modification, the method further includes: Send the deletion description file to the user terminal; Obtain the user terminal's selection operation for the deletion description information in the deletion description file; The user terminal selects the description information to be deleted and writes it into the personalized description file, and then deletes the description file to be deleted.

7. The method according to claim 6, characterized in that, The method further includes: If the user terminal is not connecting to the smart device for the first time, when a request to obtain the user terminal's documentation is received, the personalized documentation bound to the user terminal and the smart device is searched from the documentation library. The personalized description file bound to the user terminal and the smart device is pushed to the user terminal.

8. A document delivery device, characterized in that, include: The first processing module is used to determine whether the user terminal is connecting to the smart device for the first time after the user terminal connects to the smart device. The second processing module is used to obtain the device information of the smart device and the user tag of the user terminal if the user terminal connects to the smart device for the first time. The third processing module is used to obtain the default specification file corresponding to the device information from the specification file library based on the device information, wherein the specification file library stores the default specification file corresponding to each device information. The fourth processing module is used to generate and push a personalized instruction file to the user terminal based on the user tag and the default instruction file.

9. A document delivery device, characterized in that, include: At least one processor and memory; The memory stores computer-executed instructions; The at least one processor executes computer execution instructions stored in the memory, causing the at least one processor to perform the documentation push method as described in any one of claims 1 to 7.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the steps of the documentation push method as described in any one of claims 1 to 7.

Images