CN111966422A - Localized plug-in service method and device, electronic equipment and storage medium - Google Patents

Localized plug-in service method and device, electronic equipment and storage medium Download PDF

Info

Publication number
CN111966422A
CN111966422A CN202010681509.2A CN202010681509A CN111966422A CN 111966422 A CN111966422 A CN 111966422A CN 202010681509 A CN202010681509 A CN 202010681509A CN 111966422 A CN111966422 A CN 111966422A
Authority
CN
China
Prior art keywords
plug
light service
service
information
light
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202010681509.2A
Other languages
Chinese (zh)
Inventor
陈祖家
郑炎平
刘备
赵欢
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Beijing Agilestar Technology Co ltd
Original Assignee
Beijing Agilestar Technology Co ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Beijing Agilestar Technology Co ltd filed Critical Beijing Agilestar Technology Co ltd
Priority to CN202010681509.2A priority Critical patent/CN111966422A/en
Publication of CN111966422A publication Critical patent/CN111966422A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44Arrangements for executing specific programs
    • G06F9/445Program loading or initiating
    • G06F9/44521Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading
    • G06F9/44526Plug-ins; Add-ons

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Stored Programmes (AREA)

Abstract

The embodiment of the application provides a localized plug-in service method, a localized plug-in service device, electronic equipment and a storage medium, and the embodiment of the application receives a plug-in calling request input by a target object; determining a light service plug-in to be called according to the plug-in calling request; if the light service plug-in is found in the local plug-in library, acquiring running environment information, and judging whether the light service plug-in is available according to the running environment information; if the light service plug-in is determined to be available, calling the light service plug-in to package the light service plug-in into light service for the target object to use the request, the probability of conflict between the plug-in and the three-party software running environment can be reduced by locally acquiring the plug-in, the called plug-in can be further ensured to be available by combining the running environment information, and the effect of high cohesion and low coupling can be realized even in the case of one-to-many scenes.

Description

Localized plug-in service method and device, electronic equipment and storage medium
Technical Field
The present application relates to the field of plug-in services, and in particular, to a localized plug-in service method, apparatus, electronic device, and storage medium.
Background
Along with internet of things's development, when external equipment type pushed out new, it was convenient to bring for people, and in the practical application of business input, a platform seat customer end generally can be connected with multiple external equipment, for example: at present, manufacturers of external equipment mainly provide calling equipment plug-ins (dynamic library dll files), developers carry out secondary development, the equipment plug-ins provided by the manufacturers are called to generate Activex controls, and users access the plug-ins (Activex controls) obtained by the secondary development through an IE browser to call the equipment, so that the collection of user information is realized.
However, in the process of calling the external device, since the start of the plug-in depends on the browser, compatibility problems such as the version of the browser is different from the version required by the plug-in or the host operating environment may occur, so that the device cannot be normally used.
Disclosure of Invention
In order to solve the technical problem that in the prior art, because the start of the plug-in depends on the IE browser, compatibility problems that the browser version is different from the plug-in required version or the host runs and the like may occur, and the device cannot be normally used, the application provides a localized plug-in service method, device, electronic device and storage medium.
In a first aspect, an embodiment of the present application provides a localized plug-in service method, applied to a host, where the method includes:
receiving a calling plug-in request input by a target object;
determining a light service plug-in to be called according to the plug-in calling request;
if the light service plug-in is found in the local plug-in library, acquiring running environment information, and judging whether the light service plug-in is available according to the running environment information;
and if the light service plug-in is determined to be available, packaging the light service plug-in into light service for the target object to use.
Optionally, the operating environment information includes: the step of judging whether the light service plug-in is available according to the operating environment information by the plug-in dependency relationship and the validity period and/or the plug-in information of the light service plug-in comprises the following steps:
determining a target plug-in on which the light service plug-in depends according to the dependency relationship, and judging whether the target plug-in is stored in the local plug-in library;
if the target plug-in is stored in the local plug-in library, judging whether the validity period of the light service plug-in is behind the current moment or not, and/or judging whether the plug-in information is consistent with preset reference information or not.
Optionally, the method further comprises:
determining a plurality of running objects on which the light service plug-in depends according to the running environment information;
determining a target plug-in used for generating the running object for each running object which is not found in the running objects, and judging whether the equipment identifier corresponding to the target plug-in is located in a permission list;
and if the equipment identifier corresponding to the target plug-in is located in a permission list, operating the target plug-in to obtain the operation object generated by the target plug-in.
Optionally, before the step of receiving a call plug-in request entered by the target object, the method further includes:
acquiring device identifications of a plurality of devices connected with the host end;
determining equipment to be controlled according to the operation of selecting the equipment identifier of the target object;
if the equipment identifier of the equipment to be controlled is positioned in the permission list, generating a plug-in calling request according to the equipment identifier of the equipment to be controlled;
or, if the device identifier of the device to be controlled is not located in the permission list, acquiring the configuration information of the device to be controlled;
and if the configuration information meets the preset registration condition, writing the equipment identifier of the equipment to be controlled into the permission list.
Optionally, the creating process of the local plug-in library includes:
acquiring a plurality of light service plug-ins and plug-in information of each light service plug-in;
determining a target object and an access address which are depended by the light service plug-in and configuration information according to the plug-in information;
performing security verification on the configuration information;
if the configuration information passes the safety verification, finding the target object in the local plug-in library;
if the target object is not found in the local plug-in library, acquiring the target object from a preset information library and storing the target object in the local plug-in library;
and storing the light service plug-in the local plug-in library, and generating a calling interface of the light service plug-in according to the access address.
Optionally, the method further comprises:
determining equipment identification, authorization information and dependent plug-in information according to the configuration information;
judging whether the equipment identification is positioned in a permission list;
if the equipment identifier is located in the permission list, judging whether the authorization information meets a preset authorization condition;
and if the authorization information meets the preset authorization condition, determining a dependent plug-in according to the dependent plug-in information, and if the dependent plug-in is located in the local plug-in library, determining that the configuration information passes the safety verification.
Optionally, the method further comprises:
traversing a plurality of the light services in the host side;
when the light service is determined to be failed, re-executing the step of encapsulating the light service plug-in into the light service to restart the light service;
when the light service is determined to be online, performing update detection on the light service;
and if the light service plug-in is determined to be updated, acquiring an installation part corresponding to the light service plug-in from an update database, and updating the light service by using the installation part.
In a second aspect, an embodiment of the present application provides a localized plug-in service device, including:
the receiving module is used for receiving a plug-in calling request input by a target object;
the determining module is used for determining the light service plug-in to be called according to the plug-in calling request;
the judging module is used for acquiring running environment information if the light service plug-in is found in a local plug-in library, and judging whether the light service plug-in is available according to the running environment information;
and the packaging module is used for calling the light service plug-in to package the light service plug-in into light service for the target object to use if the light service plug-in is determined to be available.
In a third aspect, the present application provides an electronic device, comprising a memory and a processor, wherein the memory stores a computer program operable on the processor, and the processor implements the steps of the method according to any one of the first aspect when executing the computer program.
In a fourth aspect, a computer readable medium having non-volatile program code executable by a processor, the program code causing the processor to perform the method of any of the first aspects.
Compared with the prior art, the technical scheme provided by the embodiment of the application has the following advantages: the method comprises the steps of receiving a plug-in calling request input by a target object; determining a light service plug-in to be called according to the plug-in calling request; if the light service plug-in is found in the local plug-in library, acquiring running environment information, and judging whether the light service plug-in is available according to the running environment information; if the light service plug-in is determined to be available, calling the light service plug-in to package the light service plug-in into light service for the target object to use according to the request, avoiding the conflict between the plug-in and the three-party software running environment by locally acquiring the plug-in, further ensuring the availability of the called plug-in by combining the running environment information, and realizing the effect of high cohesion and low coupling even in the face of one-to-many scenes.
Drawings
The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the application and together with the description serve to explain the application and not to limit the application. In the drawings:
FIG. 1 is a flow chart of a localized plug-in service method provided by an embodiment of the present application;
FIG. 2 is a diagram illustrating a dependency relationship of a light service plug-in provided by an embodiment of the present application;
FIG. 3 is a flowchart illustrating the steps of authenticating a target plug-in provided by an embodiment of the present application;
FIG. 4 is a flow chart of another localized plug-in service method provided by an embodiment of the present application;
fig. 5 is a flowchart of the steps of authenticating the device according to the embodiment of the present application;
FIG. 6 is a flow chart of a local plug-in library creation process provided by an embodiment of the present application;
FIG. 7 is a flow chart of local resource access control provided by an embodiment of the present application;
FIG. 8 is a flow chart of another localized plug-in service method provided by an embodiment of the present application;
FIG. 9 is a flowchart illustrating the steps of authentication of the light service plugin according to an embodiment of the present disclosure;
FIG. 10 is a flowchart of the steps for update management of a light service plug-in provided by an embodiment of the present application;
FIG. 11 is a flowchart of the light service plugin failure processing steps provided by an embodiment of the present application;
FIG. 12 is a flowchart of the steps provided by an embodiment of the present application for a light service plug-in update;
fig. 13 is a block diagram of a localized plug-in service device according to an embodiment of the present application;
fig. 14 is a schematic structural diagram of an electronic device according to an embodiment of the present application.
DETAILED DESCRIPTION OF EMBODIMENT (S) OF INVENTION
In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
Currently, with the development of internet technology, cloud services gradually form a new scale trend in combination with edge computing, and in the aspect of cloud computing centralized processing, the front end puts higher requirements on convenience and instantaneity operation response, and meanwhile, the complexity of a network environment and a local PC is variable, and higher requirements are put on the security of a desktop end. In order to meet the development of a high-real-time low-delay software system, improve the response time efficiency and the system stability of the system, and improve the operation and use safety of a local end, at present, most of the software systems meet the business requirements of users by adopting a plug-in integrated management mode, for example, in an actual application scene, a desktop client is generally connected with various external devices (identity card reading equipment, handwriting screen equipment, high-speed shooting instrument equipment, scanning equipment, fingerprint recording equipment and the like), at present, a manufacturer of the external devices provides calling equipment plug-ins (dynamic library dll files), developers carry out secondary development, call the equipment plug-ins provided by the manufacturer to generate Activex controls, and users access the plug-ins (Activex controls) obtained by secondary development through an IE browser to call the equipment to realize the acquisition of user information. However, in the process of calling the external device, because the start of the plug-in depends on the IE browser, compatibility problems that the browser version is different from the plug-in required version or the host operating environment and the like may occur, so that the device cannot be normally used, based on this, the embodiment of the present application first provides a localized plug-in service method, which is applied to the host side, as shown in fig. 1, where the method includes:
step S101, receiving a plug-in calling request input by a target object;
in this step, the target object may be an administrator on the host side or an object of a business service, which is determined according to the actual situation, and this is not specifically limited in this embodiment of the present application.
In the embodiment of the present application, the request for calling the plug-in is determined according to the business requirements of the target object, for example, in an actual application, a user needs to start a printer connected to the host, and at this time, the printer plug-in needs to be called, that is, a request for calling the printer plug-in is generated.
In addition, the plug-in corresponding to the plug-in calling request may also be an application plug-in, for example, in an actual application, when an administrator operates a host (or may be a common user), the application a needs to be called, that is, a call request of the application a plug-in is generated, and the content of the specific plug-in calling request may be determined according to an actual situation.
Step S102, determining a light service plug-in to be called according to the plug-in calling request;
in practical application, the plug-in calling request comprises a plug-in identifier, namely, the light service plug-in needed to be called by the target object can be determined by identifying the plug-in identifier.
In this step, the light service plug-in may be a PE (installation plug-in), a dll (dynamic library) file, or an exe (executable program).
Step S103, if the light service plug-in is found in a local plug-in library, acquiring running environment information, and judging whether the light service plug-in is available according to the running environment information;
in the embodiment of the application, firstly, whether the light service plug-in which the target object needs to call is in the local plug-in library is judged, wherein the local plug-in library can be a storage area in the host side for storing the light service plug-in, then, if the light service plug-in is found in the local plug-in library, the current operating environment information is obtained, wherein the runtime environment information may include a target object (e.g. C + + object) required by an application system (e.g. Windows) and a plug-in on the host side, and finally determining whether the light service plug-in is available according to the runtime environment information, namely, whether the operating environment information is consistent with the configuration information of the light service plug-in is judged to ensure that the light service plug-in can be used in the current operating environment, in addition, the method and the device can reduce the probability of conflict between the plug-in and the three-party software running environment by locally acquiring the plug-in.
And step S104, if the light service plug-in is determined to be available, packaging the light service plug-in into light service for the target object to use.
In this step, when it is determined that the light service plug-in is available, the light service plug-in is packaged into a light service, and in practical application, after the light service plug-in is packaged into the light service, the light service may be a target object in the host end for business support, or a light service may be arranged to be online to serve a remote target object, which is not specifically limited in this embodiment of the present application.
The light service plug-in can be packaged into light service when a user needs to call, and can also be packaged with the light service in advance for the user to select and use, and the specific situation can be determined according to the actual situation.
The method comprises the steps of receiving a calling plug-in request input by a target object, determining a light service plug-in to be called according to the calling plug-in request, and firstly determining the light service plug-in needed by the target object; if the light service plug-in is found in the local plug-in library, acquiring running environment information of a current running environment, and judging whether the light service plug-in is available according to the running environment information so as to ensure that the plug-in needing to be called can be started under the running environment of the current running environment, and the problem of conflict between the light service plug-in and the running environment of three-party software can be avoided by acquiring the light service plug-in from the local, so that the light service plug-in is run in a compatible manner of crossing browsers and going an ActiveX control (ocx control); if the light service plug-in is determined to be available, calling the light service plug-in to package the light service plug-in into light service for the target object to use according to the request, and even facing a scene with one-to-many (such as many external devices in a station or devices installed in the station), the effect of high cohesion and low coupling can be achieved.
Further, the light service plug-in the local plug-in library may be downloaded by an administrator or provided from a manufacturer of the device, so that a security problem may be involved, for which, in another embodiment provided by the present application, the operating environment information includes: in step S103, the step of determining whether the light service plug-in is available according to the operating environment information includes:
firstly, determining a target plug-in on which the light service plug-in depends according to the dependency relationship, and judging whether the target plug-in is stored in the local plug-in library;
in this application embodiment, it is required to determine whether a target plug-in on which a light service plug-in depends stores the target plug-in, and in actual application, a dependency relationship between the light service plug-ins may be a call relationship of a C + + object, as shown in fig. 2, it is assumed that a plug-in a and a plug-in B are present in a host end, and the C + + object generated in the activation process of the plug-in a is service a and service B, and the service B needs to be called in the operation process of the plug-in B to generate a service C, i.e., the plug-in B depends on the plug-in a, and the plug-in a also needs to call the service C generated by the plug-in B, so the plug-in a also depends on the plug-in B.
Secondly, if the target plug-in is stored in the local plug-in library, judging whether the validity period of the light service plug-in is at the current moment;
in the embodiment of the application, whether the light service plugin is located within the validity period can be further determined by combining with the life cycle of the light service plugin, and specifically, by obtaining the comparison between the current time and the validity period of the light service plugin, a determination result of whether the light service plugin is valid can be determined, so that the unavailable light service plugin is prevented from being called.
And in addition, judging whether the plug-in information is consistent with preset reference information.
In this embodiment of the present application, the plug-in information may include a name, a version number, a calculated MD5 value, a dependent file, an accessible directory of the light service plug-in, a storage directory of the light service plug-in, and other information related to the plug-in, specifically, the preset reference information is consistent with an authentication item included in the plug-in information, and may be obtained from a manufacturer in advance, or may be entered by an administrator.
Further, in this embodiment of the present application, the authentication process for the light service plug-in the host local plug-in library may further include an authentication process for a target plug-in on which the light service plug-in depends, as shown in fig. 3, including:
step S301, determining a plurality of running objects depended by the light service plug-in according to the running environment information;
in this step, the runtime environment information includes runtime object information on which the light service plug-in depends, that is, a plurality of runtime objects (C + + objects) on which the light service plug-in depends can be directly determined from the runtime environment information.
In practical application, the operation object may refer to an object obtained by encapsulating a target file that is relied on by the light service plug-in, for example, in a case of background registration, a plurality of plug-ins that are relied on by the input light service plug-in may be multi-dll files, and dlls are called as the operation object at this time.
Step S302, aiming at each running object which is not found in the running objects, determining a target plug-in for generating the running object;
in this step, a plurality of running objects on which the service plug-in depends may be generated by the same target plug-in or may be generated by different target plug-ins, and in this case, for each running object not found in the plurality of running objects, a target plug-in for generating the running object needs to be determined.
Step S303, judging whether the device identification corresponding to the target plug-in is positioned in a permission list;
in this step, unregistered devices can be screened out by judging whether the device identifier corresponding to the target plug-in is located in the permission list, so that the possibility that the host side is invaded is reduced.
Step S304, if the device identifier corresponding to the target plug-in is located in a permission list, running the target plug-in to obtain the running object generated by the target plug-in.
In practical application, the dependency relationship between the light service plug-ins may be a call relationship of a C + + object, and in the above embodiment, it is assumed that a plug-in a and a plug-in B are present in a host, the C + + object generated in the activation process of the plug-in a is the service a and the service B, and the service B needs to be called in the operation process of the plug-in B to generate the service C, and the plug-in B depends on the plug-in a, which also needs to call the service C generated by the plug-in B, so the plug-in a also depends on the plug-in B.
In addition, if the device identifier corresponding to the target plug-in is not located in the permission list, it indicates that the device to which the target plug-in belongs may have an insecurity factor, and in order to protect the host from a malicious attack by the device, the target plug-in is not allowed to be called.
Along with internet of things's development, when external equipment type pushed out new, it was convenient to bring for people, and in the practical application of business input, a platform seat customer end generally can be connected with multiple external equipment, for example: identification card reading equipment, handwriting screen equipment, high-speed shooting instrument equipment, scanning equipment, fingerprint recording equipment and the like. Therefore, in the embodiment of the present application, a process of performing authentication management on an external device when the external device is detected is further provided, and before receiving a call plug-in request entered by a target object in step S101, as shown in fig. 4, the method further includes:
step S410, acquiring device identifications of a plurality of devices connected with the host end;
in this step, for the actual situation that one host end may connect multiple devices, in the embodiment of the present application, the device identifiers of the multiple devices connected to the host end are first determined, and then authentication detection is performed on the devices, so as to improve the security of the host end.
Step S420, determining equipment to be controlled according to the operation of selecting the equipment identifier of the target object;
in the embodiment of the application, an interface for selecting the equipment by the user can be provided, the equipment identifier is corresponding to the operation of selecting the equipment by the user, and finally the equipment which needs to be controlled by the user is determined.
Step S421, if the device identifier of the device to be controlled is in the permission list, generating a plug-in calling request according to the device identifier of the device to be controlled;
in the embodiment of the application, the permission list may be a permission list automatically generated after the light service plug-in and the device information are registered in the background, and only the device entering the permission list is considered to be safe and available, and a plug-in calling request corresponding to the device identifier of the device to be controlled is generated.
In addition, in step S422, if the device identifier of the device to be controlled is not located in the permission list, obtaining configuration information of the device to be controlled;
in this step, the configuration information of the device to be controlled may include: the device type, device model, manufacturer information, vendor identification code vid (vendor id), product identification code pid (product id), and the like are input, but the specific inclusion may be determined according to actual circumstances.
Step S423, if the configuration information meets the preset registration condition, writing the device identifier of the device to be controlled into the permission list.
In this embodiment of the present application, the preset registration condition may include multiple sub-conditions that correspond to information items in the configuration information one by one, for example, in an actual case, the preset registration condition includes: the specific preset registration condition includes content which can be determined according to actual conditions.
In practical application, as shown in fig. 5, when a new external device D needs to be connected to the desk host for use, first, the external device information needs to be registered in the management background, and information such as the device type, the device model, the manufacturer information, the vendor identification code vid (vendor id) and the product identification code pid (product id) is input and stored in the background database. Then, when the agent host calls the external device D, the main flow is as shown in fig. 2, and the external device information M of the local agent host is obtained through the maintenance service module in the localized desktop light service2And to M2Encrypting to obtain encrypted information M2'. Secondly, the user sends the encrypted information to the background service through the maintenance service in the running supporting middleware service in the background service system. Thirdly, the background maintenance module updates M2' information is decrypted to obtain the plaintext information M after decryption2. And finally, the registered device information in the database is checked in a traversing way, and if the device D information exists in the database, the device D is a normally used safety device. Otherwise, recording the device as an unregistered device and not using the unregistered device.
In the embodiment of the present application, a specific embodiment of a process for creating a local plug-in library is further provided, as shown in fig. 6, including:
step S601, acquiring a plurality of light service plug-ins and plug-in information of each light service plug-in;
the plug-in information in this step may include the target object and the access address that the light service plug-in depends on and the configuration information, but is not limited to this, and the specific setting may be determined according to the actual situation.
Step S602, determining a target object and an access address which are depended by the light service plug-in and configuration information according to the plug-in information;
in this step, according to the content in the plug-in information, the target object and the access address and the configuration information on which the light service plug-in depends can be determined, so as to perform security authentication on all aspects of the plug-in information.
Step S603, carrying out security verification on the configuration information;
step S604, if the configuration information passes the security verification, finding the target object in the local plug-in library;
in this step, the step of performing security verification on the configuration information may specifically adopt a mode of traversing a preset white list to determine whether the light service plug-in is a registered security plug-in, so as to prevent a malicious attack behavior of the plug-in.
Wherein the configuration information may include: the method comprises the following steps of storing information such as a version number, a calculated MD5 value, a dependent file, a light service plug-in accessible directory and a light service plug-in storage directory, and correspondingly storing contents corresponding to various information in configuration information in a white list for comparing and checking the configuration information contents.
Step S605, if the target object is not found in the local plug-in library, acquiring the target object from a preset information library and storing the target object in the local plug-in library;
in this embodiment of the application, if the target object does not exist, the target object may be obtained from a preset information base, where the preset information base may be set at a host side or may be an information base used in a cloud side for storing the target object, the target object refers to a dependent file (e.g., a C + + object) on which the micro service plug-in depends, and after the target object is obtained, the target object is stored in a local client storage space, where the stored partial data cannot be modified or deleted for an ordinary user, and an administrator user may directly perform data arrangement and processing.
Step S606, storing the light service plug-in the local plug-in library, and generating the calling interface of the light service plug-in according to the access address.
In practical application, the process of acquiring the light service plug-in can be realized by address resolution, and in order to ensure data security, the process can also be realized by protocol resolution, and the specific implementation process can be selected according to practical situations.
In the embodiment of the application, in order to protect the security of the light service plug-in and the locally stored data, the data is subjected to access control, a storage space (namely, a local plug-in library) is newly created at a local client, and the local plug-in library is used for storing the light service plug-in and plug-in information (such as data relevant to the localization middleware.)
In practical application, as shown in fig. 7, in the background registration process, plug-in information of a light service plug-in to be registered is input, if a target object determined according to the plug-in information is not in a local plug-in library, a target object is obtained from a preset information library and stored in the local plug-in library (i.e. a database), in addition, plug-in information may also be stored in the local plug-in library so as to facilitate to see the target object on which the light service plug-in depends, or plug-in information may be stored in other storage areas of the host, specifically, according to practical situations, when a local client of the light service plug-in is updated, a white list may be traversed first to obtain dependent plug-in information of the micro service plug-in to be called, whether a dependent file of the micro service plug-in to be updated exists locally, and if not, after obtaining the target object from the information library, the target object is stored in a storage space of the local client, the storage part data can not be modified and deleted for common users, an administrator user can directly perform data sorting and processing, in the actual application scene of the background registration process, a directory which a plug-in needs to access is input, in the process of loading a control, security control of the directory is performed, specifically, authorized local directory information can be directly accessed through a calling interface of a light service plug-in, if an access address is not obtained from the plug-in information in the actual application, default local directory information can be accessed, on one hand, access security is guaranteed, and on the other hand, attack behaviors of malicious plug-ins are prevented.
Further, as shown in fig. 8, an embodiment of the present application further provides a method for determining that the configuration information passes the security check, including:
step S801, determining equipment identification, authorization information and dependent plug-in information according to the configuration information;
step S802, judging whether the equipment identifier is positioned in a permission list;
step S803, if the device identifier is located in the permission list, determine whether the authorization information meets a preset authorization condition;
step S804, if the authorization information accords with the preset authorization condition, determining a dependent plug-in according to the dependent plug-in information, and if the dependent plug-in is located in the local plug-in library, determining that the configuration information passes the safety verification.
In the embodiment of the application, the configuration information includes an equipment identifier, authorization information and dependent plug-in information, and first of all, it is determined whether the equipment identifier is in a permission list, if the equipment identifier is in the permission list, it is verified that the equipment is an equipment which has completed registration at a host, and then it is determined whether the authorization information meets a preset authorization condition, if the authorization information meets the preset authorization condition, it is verified that the light service plug-in passes trust authorization of a manufacturer or the host, and finally, the dependent plug-in is determined according to the dependent plug-in information, if the dependent plug-in is in the local plug-in library, it is verified that the light service plug-in can run at the host, and finally, it is determined that the configuration information passes security verification.
Step S805, storing the light service plug-in the local plug-in library.
In practical application, a new light service plug-in needs to be registered in a management background, information such as a name, a version number, a digital signature, a calculated MD5 value, a dependent file, a light service plug-in accessible directory and a light service plug-in storage directory is input, and the information is stored in a background database. Or generating a white list to prepare for the authentication part of the following light service plug-in. The process includes an authentication management part for the light service plug-in, as shown in fig. 9, and is described in detail below, the maintenance service accesses the local specific storage area in real time to find the plug-in to be called locally. The local specific storage area refers to a storage area for localized light service (localized middleware) access and storage control. The maintenance service obtains the plug-in related information, such as the name of the light service plug-in, the version number, the value of the file MD5, the digital signature of the light service plug-in, and the like. And uploading the plug-in information to the background. Or download the white list from the background. And traversing the stored plug-in list (or traversing a white list downloaded to the local side) to check whether the plug-in information list is registered, and if the light service plug-in is registered, allowing the light service plug-in to be called by the local side. Otherwise, the service plug-in is prompted to be an unregistered plug-in and is not called.
In another embodiment provided by the present application, there is also provided an update management method for a light service plug-in, as shown in fig. 10, including:
step S1001, traversing a plurality of light services in the host end;
step S1002, when the light service is determined to be failed, re-executing the step of encapsulating the light service plug-in into the light service to restart the light service;
in this step, a specific embodiment for determining the light service failure may be determined according to an actual situation, in an actual application, as shown in fig. 11, when a light service plug-in a host end fails (may fail in a process of using the device or may fail in a process of updating the plug-in), the front end sends a host end failure help-seeking request, the request message is in a json data format, and is encrypted by using an encryption algorithm a, the management service receives the request message, decrypts the encrypted message to obtain a decrypted message, and analyzes the request message; the management service sends a request to the maintenance service, encrypts the message by adopting an encryption algorithm B and informs the maintenance service to respond to the request sent by the front end of the service system; the maintenance service receives the request message, decrypts the encrypted message to obtain a decrypted message, and analyzes the request message; the maintenance service responds to the request, firstly, the maintenance service captures local system information (such as system error information, CPU utilization rate, memory utilization rate and the like) and screen resource information in real time and uploads the local system information and the screen resource information to a background, wherein the screen resource information refers to screen recording information of a host side when a problem occurs, and the host side is remotely accessed. Meanwhile, the log service pushes the service and the plug-in real time to call and run the log to a background; the background analyzes the log and can check the real-time information of the error of the local client screen at any time; the problem is quickly searched, and the problem is efficiently positioned and solved.
Step S1003, when the light service is determined to be on line, updating and detecting the light service;
in practical application, in a background registration process, dependent plug-in information of a light service plug-in to be registered is input, the dependent information is stored in a database, when a local client of the light service plug-in is updated, a white list is traversed first, dependent plug-in information of a micro service plug-in to be called is obtained, whether a dependent file of the light service plug-in to be updated exists locally or not is obtained, if the dependent file does not exist, updating and downloading are carried out, the dependent file is stored in the local plug-in library of the local client, part of data is stored, modification and deletion operations cannot be carried out on common users, and manager users can directly carry out data sorting and processing. In the background registration process, a directory to be accessed by the plug-in is input, and in the control loading process, the security control of the directory is carried out, so that on one hand, the access security is ensured, and on the other hand, the attack behavior of malicious plug-ins is prevented.
Step S1004, if it is determined that the light service plug-in is updated, acquiring an installation part corresponding to the light service plug-in from an update database, and updating the light service by using the installation part.
In practical application, according to the update part of the light service plug-in by the authentication operation, the update service detects in real time whether the local light service plug-in is the latest light service plug-in to be called, as shown in fig. 12, specifically described below, the update service acquires the relevant information of the local light service plug-in and the service in real time, such as the version number, the MD5 value, the digital signature, and other information; the updating service accesses the white list generated by the background in the downloading registration process to the local in real time; the update service traverses the white list to see if the local light service plug-in (or service) is the latest version and if the update flag bit needs to be updated. If an update is required, the update service sends a request to download the plug-in (e.g., C + + plug-in) or service for downloading. And meanwhile, checking the dependent file of the light service plug-in (or service) in the white list, traversing whether the dependent file exists locally, and if the dependent file does not exist, continuously sending a request for downloading the dependent file by the updating service to download the updating dependent file.
In another embodiment provided by the present application, there is also provided a localized plug-in service apparatus, as shown in fig. 13, including:
the receiving module 01 is used for receiving a plug-in calling request input by a target object;
the determining module 02 is used for determining the light service plug-in to be called according to the plug-in calling request;
the judging module 03 is configured to obtain operating environment information if the light service plug-in is found in the local plug-in library, and judge whether the light service plug-in is available according to the operating environment information;
and the packaging module 04 is configured to call the light service plug-in to package the light service plug-in into light service for the target object to use if it is determined that the light service plug-in is available.
In yet another embodiment of the present application, there is also provided an electronic device including: the system comprises a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory complete mutual communication through the communication bus;
a memory for storing a computer program;
and the processor is used for realizing the localized plug-in service method in the embodiment of the method when executing the program stored in the memory.
According to the electronic equipment provided by the embodiment of the application, the processor executes the program stored in the memory to realize the purpose of receiving the calling plug-in request input by the target object; determining a light service plug-in to be called according to the plug-in calling request; if the light service plug-in is found in the local plug-in library, acquiring running environment information, and judging whether the light service plug-in is available according to the running environment information; if the light service plug-in is determined to be available, calling the light service plug-in to package the light service plug-in into light service, so that the target object can use the light service according to the request, the probability of the conflict between the plug-in and the three-party software operating environment can be reduced by locally acquiring the plug-in, and the availability of the called plug-in can be further ensured by combining with the operating environment information, and even in a one-to-many scene, the communication bus 1140 mentioned in the electronic device can achieve the effect of high-cohesion low coupling, and can be a peripheral component interconnect standard (PCI) bus or an Extended Industrial Standard Architecture (EISA) bus or the like. The communication bus 1140 may be divided into an address bus, a data bus, a control bus, and the like. For ease of illustration, only one thick line is shown in FIG. 14, but this is not intended to represent only one bus or type of bus.
The communication interface 1120 is used for communication between the electronic device and other devices.
The memory 1130 may include a Random Access Memory (RAM), and may also include a non-volatile memory (non-volatile memory), such as at least one disk memory. Optionally, the memory may also be at least one memory device located remotely from the processor.
The processor 1110 may be a general-purpose processor, and includes a Central Processing Unit (CPU), a Network Processor (NP), and the like; the integrated circuit may also be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic device, or discrete hardware components.
In still another embodiment of the present application, there is also provided a computer-readable storage medium having stored thereon a program of an information transmission method, which when executed by a processor, performs the steps of the localized plug-in service of the method embodiment.
In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. The procedures or functions according to the embodiments of the present application are all or partially generated when the computer program instructions are loaded and executed on a computer. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by wire (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wirelessly (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device, such as a server, a data center, etc., that incorporates one or more of the available media. The usable medium may be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid state disk (ssd)), among others.
Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used herein in the description of the present application is for the purpose of describing particular embodiments only and is not intended to be limiting of the application.
Finally, it should be noted that: the above embodiments are only used for illustrating the technical solutions of the present application, and not for limiting the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some or all of the technical features may be equivalently replaced; and the modifications or the substitutions do not make the essence of the corresponding technical solutions depart from the scope of the technical solutions of the embodiments of the present application.

Claims (10)

1. A localized plug-in service method applied to a host side, the method comprising:
receiving a calling plug-in request input by a target object;
determining a light service plug-in to be called according to the plug-in calling request;
if the light service plug-in is found in the local plug-in library, acquiring running environment information, and judging whether the light service plug-in is available according to the running environment information;
and if the light service plug-in is determined to be available, packaging the light service plug-in into light service for the target object to use.
2. The localized plugin service method of claim 1, wherein the runtime environment information includes: the step of judging whether the light service plug-in is available according to the operating environment information by the plug-in dependency relationship and the validity period and/or the plug-in information of the light service plug-in comprises the following steps:
determining a target plug-in on which the light service plug-in depends according to the dependency relationship, and judging whether the target plug-in is stored in the local plug-in library;
if the target plug-in is stored in the local plug-in library, judging whether the validity period of the light service plug-in is behind the current moment or not, and/or judging whether the plug-in information is consistent with preset reference information or not.
3. The localized plugin service method of claim 2, further comprising:
determining a plurality of running objects on which the light service plug-in depends according to the running environment information;
determining a target plug-in used for generating the running object for each running object which is not found in the running objects, and judging whether the equipment identifier corresponding to the target plug-in is located in a permission list;
and if the equipment identifier corresponding to the target plug-in is located in a permission list, operating the target plug-in to obtain the operation object generated by the target plug-in.
4. The localized plugin service method of claim 1, prior to the step of receiving a target object entry invoking plugin request, further comprising:
acquiring device identifications of a plurality of devices connected with the host end;
determining equipment to be controlled according to the operation of selecting the equipment identifier of the target object;
if the equipment identifier of the equipment to be controlled is positioned in the permission list, generating a plug-in calling request according to the equipment identifier of the equipment to be controlled;
or, if the device identifier of the device to be controlled is not located in the permission list, acquiring the configuration information of the device to be controlled;
and if the configuration information meets the preset registration condition, writing the equipment identifier of the equipment to be controlled into the permission list.
5. The localized plugin service method of claim 1, wherein the creation process of the local plugin library comprises:
acquiring a plurality of light service plug-ins and plug-in information of each light service plug-in;
determining a target object and an access address which are depended by the light service plug-in and configuration information according to the plug-in information;
performing security verification on the configuration information;
if the configuration information passes the safety verification, finding the target object in the local plug-in library;
if the target object is not found in the local plug-in library, acquiring the target object from a preset information library and storing the target object in the local plug-in library;
and storing the light service plug-in the local plug-in library, and generating a calling interface of the light service plug-in according to the access address.
6. The localized plugin service method of claim 5, further comprising:
determining equipment identification, authorization information and dependent plug-in information according to the configuration information;
judging whether the equipment identification is positioned in a permission list;
if the equipment identifier is located in the permission list, judging whether the authorization information meets a preset authorization condition;
and if the authorization information meets the preset authorization condition, determining a dependent plug-in according to the dependent plug-in information, and if the dependent plug-in is located in the local plug-in library, determining that the configuration information passes the safety verification.
7. The localized plugin service method of claim 1, further comprising:
traversing a plurality of the light services in the host side;
when the light service is determined to be failed, re-executing the step of encapsulating the light service plug-in into the light service to restart the light service;
when the light service is determined to be online, performing update detection on the light service;
and if the light service plug-in is determined to be updated, acquiring an installation part corresponding to the light service plug-in from an update database, and updating the light service by using the installation part.
8. A localized plug-in service apparatus, comprising:
the receiving module is used for receiving a plug-in calling request input by a target object;
the determining module is used for determining the light service plug-in to be called according to the plug-in calling request;
the judging module is used for acquiring running environment information if the light service plug-in is found in a local plug-in library, and judging whether the light service plug-in is available according to the running environment information;
and the packaging module is used for calling the light service plug-in to package the light service plug-in into light service for the target object to use if the light service plug-in is determined to be available.
9. An electronic device, comprising a memory and a processor, wherein the memory stores a computer program operable on the processor, and wherein the processor implements the steps of the method according to any of the preceding claims 1 to 7 when executing the computer program.
10. A computer-readable medium having non-volatile program code executable by a processor, wherein the program code causes the processor to perform the method of any of claims 1 to 7.
CN202010681509.2A 2020-07-15 2020-07-15 Localized plug-in service method and device, electronic equipment and storage medium Pending CN111966422A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202010681509.2A CN111966422A (en) 2020-07-15 2020-07-15 Localized plug-in service method and device, electronic equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202010681509.2A CN111966422A (en) 2020-07-15 2020-07-15 Localized plug-in service method and device, electronic equipment and storage medium

Publications (1)

Publication Number Publication Date
CN111966422A true CN111966422A (en) 2020-11-20

Family

ID=73361480

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202010681509.2A Pending CN111966422A (en) 2020-07-15 2020-07-15 Localized plug-in service method and device, electronic equipment and storage medium

Country Status (1)

Country Link
CN (1) CN111966422A (en)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112416459A (en) * 2020-11-23 2021-02-26 杭州当虹科技股份有限公司 System for solving version strong dependence between micro services
CN113050985A (en) * 2021-04-19 2021-06-29 中国工商银行股份有限公司 Front-end engineering dependence automatic registration method and device
CN113656093A (en) * 2021-08-02 2021-11-16 珠海格力电器股份有限公司 Plug-in configuration method, device, equipment and storage medium

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104348836A (en) * 2014-10-31 2015-02-11 北京奇虎科技有限公司 Method and client end for loading website information
CN104699427A (en) * 2013-12-06 2015-06-10 无锡韩光电器有限公司 Remote printing method and system
US20150271348A1 (en) * 2014-03-18 2015-09-24 Ricoh Company, Ltd. Information processing system, information processing apparatus, and information processing method
CN105138352A (en) * 2015-07-31 2015-12-09 百度在线网络技术(北京)有限公司 Method and apparatus for installing application plugins
CN106657265A (en) * 2016-11-14 2017-05-10 晶赞广告(上海)有限公司 Service framework system
CN110457145A (en) * 2019-08-19 2019-11-15 四川久远银海软件股份有限公司 A kind of cross-platform browser peripheral hardware call method

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104699427A (en) * 2013-12-06 2015-06-10 无锡韩光电器有限公司 Remote printing method and system
US20150271348A1 (en) * 2014-03-18 2015-09-24 Ricoh Company, Ltd. Information processing system, information processing apparatus, and information processing method
CN104348836A (en) * 2014-10-31 2015-02-11 北京奇虎科技有限公司 Method and client end for loading website information
CN105138352A (en) * 2015-07-31 2015-12-09 百度在线网络技术(北京)有限公司 Method and apparatus for installing application plugins
CN106657265A (en) * 2016-11-14 2017-05-10 晶赞广告(上海)有限公司 Service framework system
CN110457145A (en) * 2019-08-19 2019-11-15 四川久远银海软件股份有限公司 A kind of cross-platform browser peripheral hardware call method

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112416459A (en) * 2020-11-23 2021-02-26 杭州当虹科技股份有限公司 System for solving version strong dependence between micro services
CN112416459B (en) * 2020-11-23 2024-03-01 杭州当虹科技股份有限公司 System for solving version strong dependence among micro services
CN113050985A (en) * 2021-04-19 2021-06-29 中国工商银行股份有限公司 Front-end engineering dependence automatic registration method and device
CN113050985B (en) * 2021-04-19 2024-02-06 中国工商银行股份有限公司 Front-end engineering dependency automatic registration method and device
CN113656093A (en) * 2021-08-02 2021-11-16 珠海格力电器股份有限公司 Plug-in configuration method, device, equipment and storage medium

Similar Documents

Publication Publication Date Title
US10354068B2 (en) Anonymized application scanning for mobile devices
CN108289098B (en) Authority management method and device of distributed file system, server and medium
WO2022193513A1 (en) Docker-based data processing method and related device
CN111966422A (en) Localized plug-in service method and device, electronic equipment and storage medium
EP3552098A1 (en) Operating system update management for enrolled devices
US9344406B2 (en) Information processing device, information processing method, and computer program product
JP2015508549A (en) Identify Trojanized applications for mobile environments
CN110555293A (en) Method, apparatus, electronic device and computer readable medium for protecting data
US20170302701A1 (en) Integrated application scanning and mobile enterprise computing management system
US11727101B2 (en) Methods and systems for verifying applications
US20140026228A1 (en) Information processing apparatus and control method
CN110390184B (en) Method, apparatus and computer program product for executing applications in the cloud
US20220253297A1 (en) Automated deployment of changes to applications on a cloud computing platform
CN108777691B (en) Network security protection method and device
US20220277179A1 (en) Barcode-based enrollment of devices with a management service
US10771462B2 (en) User terminal using cloud service, integrated security management server for user terminal, and integrated security management method for user terminal
CN111200593A (en) Application login method and device and electronic equipment
CN111737232A (en) Database management method, system, device, equipment and computer storage medium
US10158623B2 (en) Data theft deterrence
CN109889410B (en) Method, system, device, proxy equipment and storage medium for testing service function
KR101700413B1 (en) Method and system for integrity check of integrit of program
CN111538566A (en) Mirror image file processing method, device and system, electronic equipment and storage medium
JP7445017B2 (en) Mobile application forgery/alteration detection method using user identifier and signature collection, computer program, computer readable recording medium, and computer device
CN112464225A (en) Request processing method, request processing device and computer readable storage medium
JP5357927B2 (en) COMMUNICATION DEVICE, DATA ACCESS METHOD, AND DATA ACCESS PROGRAM

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination