CN116016676A - Method, device, equipment and medium for operating data in plug-in - Google Patents

Method, device, equipment and medium for operating data in plug-in Download PDF

Info

Publication number
CN116016676A
CN116016676A CN202211586685.3A CN202211586685A CN116016676A CN 116016676 A CN116016676 A CN 116016676A CN 202211586685 A CN202211586685 A CN 202211586685A CN 116016676 A CN116016676 A CN 116016676A
Authority
CN
China
Prior art keywords
component
plug
proxy
request
determining
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
CN202211586685.3A
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 QIYI Century Science and Technology Co Ltd
Original Assignee
Beijing QIYI Century Science and 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 QIYI Century Science and Technology Co Ltd filed Critical Beijing QIYI Century Science and Technology Co Ltd
Priority to CN202211586685.3A priority Critical patent/CN116016676A/en
Publication of CN116016676A publication Critical patent/CN116016676A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02DCLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D10/00Energy efficient computing, e.g. low power processors, power management or thermal management

Landscapes

  • Stored Programmes (AREA)

Abstract

The embodiment of the application provides a method, a device, equipment and a medium for operating data in a plug-in, wherein the method comprises the following steps: receiving a use request, and determining the type of a component to be used and a first component to be used in the plug-in based on the use request; after identifying the first component as an unregistered component, acquiring a keyword corresponding to the first component; determining a first proxy component corresponding to the first component based on the corresponding relation between the keywords and the proxy components, wherein the first proxy component is registered through an application program; based on the use request, a first operation request is obtained, wherein the first operation request carries an operation to be executed by the first component; sending a first operation request to a first proxy component; and the first component is called by the first proxy component so that the first component executes the operation corresponding to the first operation request in the plug-in. By adopting the scheme, the data can be operated in the plug-in.

Description

Method, device, equipment and medium for operating data in plug-in
Technical Field
The present disclosure relates to the field of intelligent hardware technologies, and in particular, to a method, an apparatus, a device, and a medium for operating on data in a plug-in unit.
Background
With the development of society, the social division is finer and finer, and many enterprises generally have a remarkable advantage on one aspect and cannot manufacture the whole product. For example, for an automobile, a strong term for a vehicle enterprise is in making a vehicle, and software programs are not an advantage of the vehicle enterprise; for software players, video enterprises have a prominent advantage in this regard, with many customers. The current implementation scheme of the internet of vehicles SDK (Software Development Kit ) is to package a video middle station SDK for a video company, externally provide an apk-format plug-in and jar-format interface, and realize operations such as video playing, account login and the like. That is, by installing the plug-in on the application of the vehicle-enterprise equipment, the vehicle-enterprise equipment can play the video provided by the video enterprise through the plug-in. The current way of calling data for external modes by using plug-ins is as follows: the database is placed at the vehicle enterprise equipment end, and database operations such as login account number, play record inquiry and the like are realized by calling the database on the vehicle enterprise equipment, so that when the user performs the operations such as login account number, play record inquiry and the like, the user is influenced by a network to inevitably generate time delay, and the user experience is poor under the condition of poor network. In addition, the database is arranged on the vehicle enterprise equipment end, and the vehicle enterprise is used for controlling the database, so that the safety problems such as data leakage and the like are easy to occur.
The four modules of Android can provide data service, broadcast service, interface service and background service, and the modules are packaged in the plug-in, namely, the data is stored in the plug-in, so that the problems can be effectively solved. However, there is no technical solution in the prior art for packaging components within a package. In addition, as is well known, four components of Android can be used only by registration, however, software application service companies only provide plug-ins and plug-ins, the registration of the components cannot be realized through the plug-ins, and even if the components are packaged in the plug-ins, the components in the plug-ins cannot be used, so that the operation on data cannot be realized in the plug-ins.
Disclosure of Invention
The embodiment of the application aims to provide a method, a device, equipment and a medium for operating data in a plug-in unit so as to realize the operation of the data in the plug-in unit. The specific technical scheme is as follows:
in a first aspect of the embodiments of the present application, a method for operating data in a plug-in is provided, which is applied to an electronic device of an Android system, where a plug-in is installed on an application program of the electronic device, and the method includes:
receiving a use request, and determining the type of a component to be used in the plug-in and a first component to be used based on the use request; wherein the package has at least one type of component and at least one first component to be used encapsulated therein;
After the first component is identified as an unregistered component, acquiring a keyword corresponding to the first component; wherein the key words are fields for representing functions realized by the component;
determining a first proxy component corresponding to the first component based on the corresponding relation between the keyword and the proxy component, wherein the first proxy component is registered through the application program; wherein the key words correspond to the agent components through indexes;
acquiring a first operation request based on the use request, wherein the first operation request carries an operation to be executed by the first component;
and sending the first operation request to the first proxy component, and calling the first component by the first proxy component so that the first component executes the operation corresponding to the first operation request in the plug-in.
Optionally, the step of determining the type of the component to be used based on the use request includes:
if the use request is for providing a data service, determining the type of the component to be used as a content provider ContentProvider;
if the use request is for providing the broadcast service, determining the type of the component to be used as a broadcast receiver BroadCastReceiver;
If the use request is for providing background Service, determining the type of the component to be used as Service;
and if the use request is for providing interface service, determining the type of the component to be used as Activity.
Optionally, the step of determining the first component to be used based on the use request includes:
and determining a keyword according to the use request, and determining a first component to be used according to the corresponding relation between the keyword and the component.
Optionally, the step of obtaining the first proxy component corresponding to the first component based on the correspondence between the keyword and the proxy component includes:
acquiring an index list of the proxy component;
acquiring the package name of an application program, and mapping index information of a first proxy component from the index list according to a keyword corresponding to the first component and the package name of the application program;
determining a first proxy component corresponding to the first component based on index information of the first proxy component;
the index information comprises package names of application programs and keywords corresponding to the proxy components, and the keywords corresponding to the first component are identical to the keywords corresponding to the first proxy component.
Optionally, the step of obtaining the first operation request based on the usage request includes:
extracting a demand keyword of the use request;
and determining a first operation request corresponding to the use request based on the mapping relation between the demand keywords and the operation request.
When the type of the component to be used is determined to be a content provider ContentProvider, and the first component to be used is determined to be a first ContentProvider;
the first operation request is to add data, and the operation corresponding to the operation request is to add data to the first ContentProvider;
the first operation request is deleting data, and the operation corresponding to the operation request is inquiring data from the first ContentProvider;
the first operation request is modification data, and the operation corresponding to the operation request is modification data from the first ContentProvider;
the first operation request is query data, and the operation corresponding to the operation request is query data in the first ContentProvider.
In a second aspect of the embodiments of the present application, there is further provided a device for operating data in a plug-in, where the device is applied to an electronic device of an Android system, and a plug-in is installed on an application program of the electronic device, where the device includes:
The first determining module is used for receiving a use request and determining the type of a component to be used in the plug-in and a first component to be used based on the use request; wherein the package has at least one type of component and at least one first component to be used encapsulated therein;
the first acquisition module is used for acquiring keywords corresponding to the first component after identifying that the first component is an unregistered component; wherein the key words are fields for representing functions realized by the component;
the second determining module is used for determining a first proxy component corresponding to the second component based on the corresponding relation between the keywords and the proxy components; the first proxy component registers through the application program, and the keywords correspond to the proxy components through indexes;
the second acquisition module is used for acquiring a first operation request based on the use request, wherein the first operation request carries an operation to be executed by the first component;
the calling module is used for sending the first operation request to the first proxy component; and the first component is called by the first proxy component, so that the first component executes the operation corresponding to the first operation request in the plug-in.
Optionally, the first determining module is specifically configured to:
if the use request is for providing a data service, determining the type of the component to be used as a content provider ContentProvider;
if the use request is for providing broadcast service, determining that the type of the component to be used is BroadCastReceiver;
if the use request is for providing background Service, determining the type of the component to be used as Service;
and if the use request is for providing interface service, determining the type of the component to be used as Activity.
Optionally, the first determining module is further configured to:
and acquiring the keywords from the use request, and determining a first component to be used according to the corresponding relation between the keywords and the components.
Optionally, the second determining module is specifically configured to:
acquiring an index list of the proxy component;
acquiring the package name of an application program, and mapping index information of a first proxy component from the index list according to a keyword corresponding to the first component and the package name of the application program;
determining a first proxy component corresponding to the first component based on index information of the first proxy component;
the index information comprises package names of application programs and keywords corresponding to the proxy components, and the keywords corresponding to the first component are identical to the keywords corresponding to the first proxy component.
Optionally, the second obtaining module is specifically configured to:
extracting a demand keyword of the use request;
and determining a first operation request corresponding to the use request based on the mapping relation between the demand keywords and the operation request.
Optionally, when it is determined that the component type to be used is a content provider ContentProvider and the first component to be used is a first ContentProvider;
the first operation request is to add data, and the operation corresponding to the operation request is to add data to the first ContentProvider;
the first operation request is deleting data, and the operation corresponding to the operation request is inquiring data from the first ContentProvider;
the first operation request is modification data, and the operation corresponding to the operation request is modification data from the first ContentProvider;
the first operation request is query data, and the operation corresponding to the operation request is query data in the first ContentProvider.
In yet another aspect of the embodiments of the present application, there is also provided a computer readable storage medium having a computer program stored therein, which when executed by a processor implements any of the methods of operating on data within a plug-in unit described above.
In yet another aspect of the embodiments of the present application, there is also provided a computer program product containing instructions that, when run on a computer, cause the computer to perform any of the above-described methods of operating on data within a plug-in.
In the technical scheme provided by the embodiment of the application, the components are packaged in the plug-in, the application program registers the proxy component, after receiving the use request of the user, the electronic equipment determines the type of the component to be used in the plug-in and the first component to be used based on the use request, and after recognizing that the first component is an unregistered component, the electronic equipment acquires the keyword corresponding to the first component, and further determines the first proxy component of the first component based on the correspondence between the keyword and the proxy component. After obtaining a first operation request based on the use request, sending the first operation request to the first proxy component, and calling the first component in the plug-in through the first proxy component so that the first component executes an operation corresponding to the first operation request in the plug-in. Because the first proxy component is registered, but the first component to be used in the plug-in is not registered, the application program can identify the first proxy component and can not identify the first component, so after obtaining the operation request based on the use request, the operation request is sent to the first proxy component, and then the operation request is returned to the first component by the first proxy component, the first component can execute the operation corresponding to the operation request in the plug-in, thereby completing the operation on the data in the plug-in.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below.
Fig. 1 is a first flowchart of a method for operating on data in a plug-in unit according to an embodiment of the present application;
FIG. 2 is a second flowchart of a method for operating on data in a plug-in according to an embodiment of the present disclosure;
fig. 3 is a signaling schematic diagram of a method for operating on data in a plug-in unit according to an embodiment of the present application;
fig. 4 is a schematic structural diagram of an apparatus for operating on data in a card according to an embodiment of the present application;
fig. 5 is a schematic structural diagram of an electronic device according to an embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application.
For ease of understanding, the terminology appearing in the present application is explained first:
plug in (plug in) is a program written in an application program interface conforming to a certain specification. It can only run under a program-specified system platform (possibly supporting multiple platforms simultaneously) and cannot run separately from the specified platform.
Software development kit (Software Development Kit, SDK): typically, a collection of development tools are created by some software engineers for a particular software package, software framework, hardware platform, operating system, etc. when the application software is built.
Android package (Apk): and packaging the engineering compiled by the Android SDK into an installation program file, wherein the installation program file is in an Apk format, the Apk file is in a zip format, the suffix name is modified into the Apk, and the installation program file can be installed by directly transmitting the Apk file into an Android simulator or an Android terminal for execution.
And (3) a host: also referred to as Application (APP) hosts, plug-ins may be dynamically loaded based on the hosts for ease of development and to improve the efficiency of Application release.
Plug-in: the system is also called a dynamic plug-in and a dynamic file, which refer to an independent file containing a part of executable codes of an Android platform, and can be an Apk file, a Dex file, a Zip file and the like, and the operation of the system requires a host to provide a set of operation mechanism.
And (3) assembly: the Android application program is composed of some scattered and associated components, and is bound together through one project and is a foundation stone of the Android application program, for example, in the embodiment of the application program, the Android application program is mainly taken as an example, and the components represent four components of an Android platform: the components all need to be registered for use, activity, service, content Provider, and broadcast receiver (Broadcast Receiver).
The Activity is a window for interaction between an Android program and a user, is the most basic one in an Android building block, needs to keep the state of each interface, does a lot of persistent things, and properly manages the life cycle and some jump logic; the Service background serves for Activity, encapsulates a complete functional logic implementation, accepts upper-layer instructions and completes related things; the Content Provider is an access mode of third party application data provided by Android, and has the main functions of serving as a platform, providing data sharing and providing a data adding, deleting and checking function; broadcast Receiver receives one or more intents (Intent) as trigger events, receives related messages, performs some simple processing, converts the messages into a Notification, and unifies the Android event broadcasting model.
In order to solve the technical problem that the data cannot be operated in the plug-in, the application provides a method, a device, equipment and a medium for operating the data in the plug-in, which can be applied to various electronic equipment, such as mobile phones, tablets, vehicle-mounted terminals and the like. The operating system of the electronic device executing the scheme is an Android system, an application program can be installed on the electronic device, and a plug-in provided by a software service company is installed in the application program.
The following describes in detail a method for operating data in a plug-in unit, where the method is applied to an electronic device of an Android system, and a plug-in unit is installed on an application program of the electronic device, as shown in fig. 1, and the method includes:
s11, receiving a use request, and determining the type of a component to be used and a first component to be used in the plug-in based on the use request, wherein at least one type of component and at least one first component to be used are packaged in the plug-in.
In the embodiment of the application, the operating system of the electronic device is an Android system, and the plug-in provided by the software service company is installed on the application program on the electronic device, so that the corresponding function of the plug-in can be realized by running the plug-in at the same time when the application program runs. An application running a plug-in can be understood as the host of the plug-in. The process of starting the application program comprises a process of initializing the application program, wherein whether the application program is provided with a plug-in or not can be determined in the initializing process, and whether the plug-in runs successfully or not can be determined.
For example, when the electronic device is a vehicle-mounted terminal and the software service company is a video service company, a plug-in provided by the video service company is installed on an application program of the vehicle-mounted terminal, a user starts the application program to run the application program, the video plug-in installed in the application program also runs simultaneously, and the user can play videos provided by the video service company through the plug-in.
In this embodiment of the present application, different types of components may be packaged in the package, and multiple components of the same type may also be packaged in the package. For example, 1 Activity type component, 1 Service type component, 2 BroadCastReceiver type component, and 3 ContentProvider type component may be packaged within the plug-in. Of course, other types of components may be encapsulated within the insert, and the types and numbers of components are not specifically limited in this application.
The use request is a request issued by the user for his needs. For example, the use request may include: logging in an account, searching a play record and the like. The user can send a use request to the electronic equipment, and after the electronic equipment receives the use request, a plug-in installed on an application program of the electronic equipment can also know the use request. The plug-in may then determine the type of component to be used in the plug-in based on the use request and determine the first component to be used.
In one embodiment, when the use request is to provide a data service, then the component type to be used in the plug-in may be determined to be ContentProvider.
The data service shares the data or performs operations such as adding, deleting, checking and the like on the data in the database. Taking the video plug-in as an example, when the use request is to query the video play record, i.e. search the play record of the user from the database storing the play record of the user, at this time, it can be determined that the use request of the user needs to provide a data service, and further it is determined that the component type to be used in the plug-in is ContentProvider.
In one embodiment, when the use request is to provide a broadcast service, then the component type to be used in the plug-in may be determined to be BroadCastReceiver.
The broadcast service performs global monitoring on broadcast information sent by an application program or a system of the electronic device. The BroadCastReceiver component may receive broadcast information from an application or system. Continuing the above example, when the plug-in is a video plug-in, when the use request is to collect video, the application may send a broadcast message to the BroadCastReceiver component to synchronize the plug-in with the video collection state. At this time, it may be determined that the user's use request is to provide a broadcast service, and further it is determined that the component type to be used in the plug-in is BroadCastReceiver.
In one embodiment, when the use request is to provide a background Service, then the type of component to be used in the plugin may be determined to be Service.
The background service completes the appointed operation of the user in the background. The Service component can process network transactions, play music, etc. in the background. Continuing the above example, when the plug-in is a video plug-in, when the use request is a background play video, the application may send a command to the Service component to play the video in the background, so that the plug-in plays the video in the background. At this time, it can be determined that the user's use request is to provide a background Service, and further, it is determined that the type of the component to be used in the plugin is Service.
In one embodiment, when the use request is to provide an interface service, then the type of component to be used in the plug-in may be determined to be Activity.
The interface service provides a visual page for the user to operate, so that the interaction between the user and the application program is realized. Continuing the above example, when the plug-in is a video plug-in, when the use request is to perform fast forward operation on the video, the user can perform fast forward on the video based on the interface provided by the Activity component, at this time, it can be determined that the use request of the user needs to provide interface service, and then it is determined that the type of the component to be used in the plug-in is Activity.
In one embodiment of the present application, after determining the type of the component to be used in the plug-in based on the use request, the plug-in further determines the first component to be used in the plug-in based on the use request, because the plug-in may include multiple components of the same type.
In one embodiment, the step S11 may include: and determining a keyword according to the use request, and determining a first component to be used according to the corresponding relation between the keyword and the component.
In the embodiment of the application, the electronic device can extract the keyword from the use request. In one embodiment, all fields in the use request may be used as keys. In one embodiment, a keyword lexicon may be set in advance according to a possible use request, the use request is identified after the use request is received, and fuzzy matching is performed on the use request according to the keyword lexicon, so as to determine keywords. The components also have corresponding keywords, the keywords corresponding to the components are manually set fields, and developers can preset keywords for the components based on functions realized by the components. The keywords determined from the use request can indicate the requirements of the user for the functions implemented by the plug-in units, the keywords corresponding to the components are fields for representing the functions implemented by the components, and the keywords determined from the use request correspond to the keywords corresponding to the components, namely the keywords determined from the use request can be understood to have a corresponding relation with the components. The electronic equipment extracts keywords from the use request according to the use request, and further determines a first component to be used in the plug-in according to the corresponding relation between the keywords and the components.
For example, the plug-in determines that the type of the component to be used in the plug-in is ContentProvider based on the use request, two ContentProvider are packaged in the plug-in, the ContentProvider is ContentProvider1, contentProvider2, and ContentProvider1 stores user account data, and the function realized by the plug-in is to perform operations such as adding, deleting, checking and the like on the stored user account data, the keyword set for the ContentProvider1 is useridrovider (user account data provider), the ContentProvider2 stores play record data, and the function realized by the fact that the operation such as adding, deleting and the like is performed on the stored play record data is performed on the ContentProvider2 is the keyword set for the ContentProvider is PlayRecordprovider. The key of the ContentProvider may represent the data provided by this ContentProvider. When the use request is to search the video play record, determining that the keyword is to search the video play record based on the use request, wherein the keyword for searching the video play record corresponds to a keyword PlayRecordprovider corresponding to ContentProvider2, and further determining that a first component to be used in the plug-in is ContentProvider2 according to the corresponding relation between the keyword and the component.
Of course, when the type of component to be used in the plug-in is other types, for example BroadCastReceiver, service, activity, the method may also be used to determine the first component to be used in the plug-in. Since the methods are substantially similar, detailed descriptions thereof will be omitted.
S12, after the first component is identified as an unregistered component, acquiring a keyword corresponding to the first component; wherein the key is a field that characterizes the function implemented by the component.
In this embodiment, after determining the first component to be used in the plug-in, whether the first component is registered is identified. The component is registered, i.e., declared in a configuration file of the application, such as an android manifest file, and if the component is not registered, the application cannot identify and execute the component. If a claim for a component can be found in an android manifest. Xml file, it can be determined that the component is registered, and conversely, it can be determined that the component is unregistered. In addition, it should be noted that, in general, the components are registered by the application program, the plug-in cannot register the components inside the component, that is, the components encapsulated in the plug-in are not registered, and the components in the plug-in cannot be identified and executed.
In this embodiment of the present application, the keywords corresponding to the components are manually set fields, and the developer may preset the keywords for the components based on the functions implemented by the components. When the electronic equipment identifies that the first component in the plug-in is not registered, a keyword corresponding to the first component is acquired. In one implementation, a developer may store the component identifier and a keyword corresponding to the component in a database of the electronic device, and after determining a first component to be used in the plug-in, further determine the identifier of the first component, and further obtain, according to the identifier of the first component, the keyword corresponding to the first component from the database.
S13, determining a first proxy component corresponding to the first component based on the corresponding relation between the keywords and the proxy components, wherein the first proxy component is registered through the application program, and the keywords and the proxy components are corresponding through indexes.
In the embodiment of the present application, the proxy component is a component that has already been registered by the application (host). The application may declare the proxy component in a configuration file, such as an android management file, or may declare the proxy component in an android management file in advance when the plug-in begins running. Agent for agent
When an application registers with a proxy component, the component will be declared in the android manifest. The index of the proxy component is declared during the declaration process. The index is a unique identification of the component by which the application can identify the proxy component. The index consists of the package name of the application and the key corresponding to the proxy component. The first proxy component is a proxy component corresponding to the first component, the function realized by the first component to be used in the plug-in is the same as the function realized by the first proxy component, that is, the keyword corresponding to the first component is the same as the keyword corresponding to the first proxy component, and the keyword corresponding to the component in the plug-in corresponds to the proxy component through the index of the proxy component. And the electronic equipment determines the first proxy component corresponding to the first component according to the acquired keyword corresponding to the first component through the corresponding relation between the keyword of the component in the plug-in and the proxy component.
For example, the keyword corresponding to the first component obtained by the electronic device is useid provider, the application program has two proxy components, the index of the first proxy component is qiyi.
S14, obtaining a first operation request based on the use request, wherein the first operation request carries an operation to be executed by the first component.
In the embodiment of the application, the use request is a request sent by a user aiming at the requirement of the user, while the component is used for executing some logic operations of the bottom layer, such as adding, deleting and modifying the database, and cannot directly execute the use request. Therefore, the use request needs to be converted into an operation request which can be executed by the component, and the operation corresponding to the operation request is executed after the component receives the operation request based on the operation to be executed by the component carried in the first operation request obtained by the use request.
In one embodiment, the step S14 may include:
s141, determining a demand keyword of the use request.
In the embodiment of the application, the electronic device can determine the requirement keywords of the use request. In one embodiment, all fields in the use request may be used as demand keywords. In one embodiment, a keyword lexicon may be set in advance according to a possible use request, the use request is identified after the use request is received, and fuzzy matching is performed on the use request according to the keyword lexicon, so as to determine a required keyword.
S142, determining a first operation request corresponding to the use request based on the corresponding relation between the demand keywords and the operation request.
In this embodiment of the present application, a correspondence relationship between a requirement keyword and an operation request is preset. And in the subsequent execution process, the corresponding relation can be continuously perfected and modified. After the electronic equipment determines the requirement keywords of the use request, the first operation request corresponding to the use request is determined according to the corresponding relation between the requirement keywords and the operation request.
S15, a first operation request is sent to the first proxy component, and the first proxy component calls the first component so that the first component executes an operation corresponding to the first operation request in the plug-in.
In this embodiment of the present application, after determining a first proxy component of a first component to be used in a plug-in, the electronic device sends an operation request to the first proxy component.
In the embodiment of the present application, the operation request is not directly sent to the first component in the plug-in, because the first component in the plug-in is not registered, and therefore, the application cannot identify the first component in the plug-in. Therefore, the electronic device needs to send an operation request to the first proxy component corresponding to the first component, and the first proxy component can call back the operation instruction to the first component in the plug-in through the interface provided by the software service company, so that the first component executes the operation corresponding to the first operation request in the plug-in, and the operation on the data in the plug-in is completed.
In one embodiment, when the electronic device determines that the type of the component to be used in the plug-in is ContentProvider and the first component to be used is the first ContentProvider, and when the first operation request is to add data, the operation corresponding to the operation request is to add data to the first ContentProvider.
Taking a use request as a registration account as an example for explanation, when the use request is the registration account, the registration account adds new user data from a database storing user account data, namely the use request of the registration account is used for providing data service for users, the type of a component to be used in the plug-in unit can be determined to be a ContentProvider, keywords determined based on the use request of the registration account are accounts, and further, according to the corresponding relation between the keywords and the components, the first component to be used in the plug-in unit is determined to be the first ContentProvider for providing the user account data. And determining that the required keywords are registered from the use request of the registered account, further determining that a first operation request corresponding to the use request of the registered account is added data according to the corresponding relation between the required keywords and the operation request, and adding data to the first ContentProvider according to the operation corresponding to the operation request, namely adding the account data newly registered by the user to the first ContentProvider to finish the registration of the account.
In one embodiment, when the electronic device determines that the type of the component to be used in the plug-in is ContentProvider and the first component to be used is the first ContentProvider, and when the first operation request is to delete data, the operation corresponding to the operation request is to delete data from the first ContentProvider.
Taking the use request as the log-out account for example for description, when the use request is the log-out account for log-in, the log-out account for log-in deletes the appointed user data from the database storing the user account data, namely the log-out account for log-in is used for providing data service for the user, the type of the component to be used in the plug-in is determined to be ContentProvider, the keyword determined based on the log-out account for log-in is the account, and further, according to the corresponding relation between the keyword and the component, the first component to be used in the plug-in is determined to be the first ContentProvider for providing the user account data. And determining that the required keyword is logged out from the use request of the registered account, further determining that a first operation request corresponding to the use request of the registered account is deleting data according to the corresponding relation between the required keyword and the operation request, and deleting the data from the first ContentProvider according to the operation corresponding to the operation request, namely deleting the account data of the appointed user from the first ContentProvider, so as to finish logging out the account.
In one embodiment, when the electronic device determines that the type of the component to be used in the plug-in is ContentProvider and the first component to be used is the first ContentProvider, and when the first operation request is modification data, the operation corresponding to the operation request is modification data in the first ContentProvider.
Taking the use request as an example for modifying the account number password, when the use request is the modification account number password, the modification account number password modifies the appointed user account number data from a database for storing the user account number data, namely the use request for modifying the account number password is used for providing data service for users, the type of a component to be used in the plug-in unit can be determined to be ContentProvider, a keyword determined based on the use request for modifying the account number password is an account number, and further, according to the corresponding relation between the keyword and the component, the first component to be used in the plug-in unit is determined to be the first ContentProvider for providing the user account number data. And determining that the required keywords are modified from the use request of the registered account, further determining that the first operation request corresponding to the use request of modifying the account password is modified data according to the corresponding relation between the required keywords and the operation request, and modifying the data from the first ContentProvider according to the operation corresponding to the operation request, namely modifying the user account data appointed in the first ContentProvider, so as to complete the modification of the account password.
In one embodiment, when the electronic device determines that the type of the component to be used in the plug-in is ContentProvider and the first component to be used is the first ContentProvider, and when the first operation request is query data, the operation corresponding to the operation request is query data from the first ContentProvider.
Taking a use request as an example to query a video play record, when the use request is the query video play record, the query video play record queries a specified video play record from a database storing video play record data, that is, the use request of querying the video play record is to provide data service for a user, it can be determined that a component type to be used in the plug-in is a ContentProvider, a keyword determined based on the use request of querying the video play record is a play record, and then, according to a corresponding relation between the keyword and the component, it is determined that a first component to be used in the plug-in is a first ContentProvider providing user play record data. And determining that the required keywords are inquired from the use request of inquiring the video playing record, further determining that a first operation request corresponding to the use request of inquiring the video playing record is inquired data according to the corresponding relation between the required keywords and the operation request, and inquiring the designated user video playing record data from the first ContentProvider by the operation corresponding to the operation request to finish inquiring the video playing record.
In the technical scheme provided by the embodiment of the application, the components are packaged in the plug-in, the application program registers the proxy component, after receiving the use request of the user, the electronic equipment determines the type of the component to be used in the plug-in and the first component to be used based on the use request, and after recognizing that the first component is an unregistered component, the electronic equipment acquires the keyword corresponding to the first component, and further determines the first proxy component of the first component based on the correspondence between the keyword and the proxy component. After a first operation request is obtained based on the use request, the operation request is sent to the first proxy component, and then the first component in the plug-in is called through the first proxy component, so that the first component executes the operation corresponding to the first operation request in the plug-in. Because the first proxy component is registered, but the first component to be used in the plug-in is not registered, the application program can identify the first proxy component and can not identify the first component, so after obtaining the operation request based on the use request, the operation request is sent to the first proxy component, and then the operation request is returned to the first component by the first proxy component, the first component can execute the operation corresponding to the operation request in the plug-in, thereby completing the operation on the data in the plug-in.
Based on the embodiment shown in fig. 1, the embodiment of the present invention further provides a method for operating on data in a plug-in, as shown in fig. 2, where the method may include steps S21-S27, steps S21-S22 are the same as steps S11-S12, steps S26-S27 are the same as steps S14-S15, and steps S23-S25 are one implementation manner of step S13.
S23, obtaining an index list of the proxy component.
In the embodiment of the application, the proxy component is registered through the application program. When registering the proxy component, the component is declared in the android manifest. The index of the proxy component is declared during the declaration process. The index is a unique identification of the component by which the application can identify the component. The index typically consists of package names and keywords for the application. The application program declares the plurality of proxy components, puts the index of the plurality of proxy components in the list to obtain an index list of the proxy components, and the electronic device obtains the index list of the proxy components.
S24, acquiring the package name of the application program, and mapping index information of the first proxy component from the index list according to the keyword corresponding to the first component and the package name of the application program.
S25, determining a first proxy component corresponding to the first component based on index information of the first proxy component; the index information comprises package names of the application programs and keywords corresponding to the proxy components, and the keywords corresponding to the first component are identical to the keywords corresponding to the first proxy component.
In the embodiment of the application, the package name of the application is the identification of the application, and the package name of the application is unique. The application is installed on the electronic device, and therefore, the electronic device can acquire the package name of the application, where the acquired package name of the application is the package name of the application running the plug-in. The first component to be used in the plug-in is not registered, so that the index is not stated, but because the functions of the first component and the first proxy component are the same, the keywords corresponding to the first component are the same, and therefore, the electronic device maps the index information of the first proxy component from the index list of the proxy component according to the keywords corresponding to the first component and the package name of the application program, and further determines the first proxy component according to the index information of the first proxy component.
For example, the keyword of the first component acquired by the electronic device is useid provider, two proxy components are registered through the application program, the index 1 of the first proxy component is qiyi. The index list of the proxy component consists of index 1 and index 2. After the electronic device obtains the package name qiyi of the application program, according to the package name of the application program and the keyword corresponding to the first component, mapping first proxy component index information corresponding to the first component from the index list to be index 1, and further determining the first proxy component according to the index 1.
In the technical scheme provided by the embodiment of the application, the components are packaged in the plug-in, the application program registers the proxy component, after receiving the use request of the user, the electronic equipment determines the type of the component to be used in the plug-in and the first component to be used based on the use request, and after recognizing that the first component is an unregistered component, the electronic equipment acquires the keyword corresponding to the first component, and further determines the first proxy component of the first component based on the correspondence between the keyword and the proxy component. After obtaining a first operation request based on the use request, sending the first operation request to the first proxy component, and calling the first component in the plug-in through the first proxy component so that the first component executes an operation corresponding to the first operation request in the plug-in. Because the first proxy component is registered, but the first component to be used in the plug-in is not registered, the application program can identify the first proxy component and can not identify the first component, so after obtaining the operation request based on the use request, the operation request is sent to the first proxy component, and then the operation request is returned to the first component by the first proxy component, the first component can execute the operation corresponding to the operation request in the plug-in, thereby completing the operation on the data in the plug-in.
The technical solution provided in the embodiments of the present application is described below with reference to a signaling schematic diagram of a method for operating on data in a card shown in fig. 3.
In step S31, the plug-in sends an operation request to the first proxy component.
In this embodiment of the present application, after receiving a use request, a plug-in installed in an application program on an electronic device obtains the use request, and the plug-in determines, based on the use request, a component type to be used and a first component to be used in the plug-in. After the plug-in determines the first component to be used, acquiring a keyword corresponding to the first component, and determining a first proxy component corresponding to the first component based on the corresponding relation between the keyword and the proxy component. The plug-in turn obtains an operation request based on the use request, and sends the operation request to the first proxy component.
In step S32, the first proxy component calls back an operation request to the first component in the plug-in based on the external interface.
In the embodiment of the application, the external interface is provided by a service company, and the first proxy component calls back the operation request to the first component in the plug-in through the external interface.
In step S33, the first component in the plug-in executes the operation corresponding to the operation request in the plug-in.
In the embodiment of the application, after receiving the operation request sent by the first proxy component, the first component in the plug-in can execute the operation corresponding to the first operation request, so as to implement the operation on the data in the plug-in.
The process is the same as the method for operating the data in the plug-in unit in the above embodiment, so that the description thereof will not be repeated.
In order to facilitate understanding, the method for operating the data in the plug-in unit provided in the embodiment of the present application is described below with reference to a specific application scenario.
In the application scene of the internet of vehicles, various functions are realized by installing plug-ins on the vehicle-mounted equipment. For example, an alien plug-in may be installed on the in-vehicle device to play the video. Many basic databases of the curiosity are used at the bottom layer of the plugin, including databases for storing account data, databases for storing play records, and the like. The package internally encapsulates a component of the type ContentProvider, data in the databases can be shared to the application programs through the ContentProvider, and database operations such as adding, deleting, checking and the like can be provided for the data in the databases.
However, the plug-in cannot register the ContentProvider component, so that the registered ContentProvider cannot be found by database operations such as logging in an account number, querying a play record and the like. Therefore, in the embodiment of the application, the application program (host) for installing the plug-in declares a proxy component in the configuration file android management, and the index of the proxy component is composed of the package name of the application program and the key corresponding to the proxy component. After receiving the use request of the user, the plug-in unit can determine that the ContentProvider to be used in the plug-in unit is ContentProvider1 for providing the play record data based on the use request, and further determine the proxy component of ContentProvider1 according to the keyword of ContentProvider1 and the index of the proxy component. The database operation to be executed in the plug-in will call back in the proxy ContentProvider, which provides an interface through the odd technology, and the specific implementation method in the plug-in of the call back. For example, a method of adding a censoring to the database, thereby achieving the purpose that the database can be used in the plug-in.
The application scenario of the method for operating the data in the plug-in unit provided by the embodiment of the application is not limited to the application scenario of the internet of vehicles, and the method for operating the data in the plug-in unit provided by the embodiment of the application can be used as long as a software service company provides the plug-in unit to the outside of a third party company.
Based on the same inventive concept, according to the method for operating the data in the plug-in unit provided by the above embodiment of the present application, correspondingly, the embodiment of the present application provides a method and apparatus for operating the data in the plug-in unit, where the apparatus is applied to an electronic device of an Android system, and a plug-in unit is installed on an application program of the electronic device, and a schematic structural diagram of the apparatus is shown in fig. 4, and includes:
a first determining module 41, configured to receive a use request, and determine a type of a component to be used in the plug-in and a first component to be used based on the use request; wherein the plug-in is packaged with at least one type of component and at least one first component to be used;
the first obtaining module 42 is configured to obtain a keyword corresponding to the first component after identifying that the first component is an unregistered component; wherein the key words are fields for representing functions realized by the component;
A second determining module 43, configured to determine a first proxy component corresponding to the first component based on a correspondence between the keyword and the proxy component; the first proxy component registers through the application program, and the keywords correspond to the proxy components through indexes;
a second obtaining module 44, configured to obtain a first operation request based on the usage request, where the first operation request carries an operation to be performed by the first component;
the calling module 45 is configured to send a first operation request to the first proxy component, and the first proxy component calls the first component, so that the first component executes an operation corresponding to the first operation request in the plug-in.
Optionally, the first determining module 41 may be specifically configured to:
if the use request is based on providing the data service, determining the type of the component to be used as a content provider ContentProvider;
if the use request is for providing the broadcast service, determining that the type of the component to be used is BroadCastReceiver;
if the use request is for providing background Service, determining the type of the component to be used as Service;
if the use request is to provide an interface service, the type of the component to be used is determined to be Activity.
Optionally, the first determining module 41 may be further configured to:
and acquiring the keywords from the use request, and acquiring a first component to be used according to the corresponding relation between the keywords and the components.
Optionally, the second determining module 43 may be specifically configured to:
acquiring an index list of the proxy component;
acquiring the package name of an application program, and mapping index information of a first proxy component from the index list according to a keyword corresponding to the first component and the package name of the application program;
determining a first proxy component corresponding to the first component based on index information of the first proxy component;
the index information comprises package names of application programs and keywords corresponding to the proxy components, and the keywords corresponding to the first component are identical to the keywords corresponding to the first proxy component.
Optionally, the second determining module 43 may be specifically configured to:
acquiring an index list of the proxy component;
acquiring the package name of the application program, and mapping index information of the first proxy component from an index list according to the keyword corresponding to the first component and the package name of the application program;
determining a first proxy component corresponding to the first component based on index information of the first proxy component;
The index information comprises package names of the application programs and keywords corresponding to the proxy components, and the keywords corresponding to the first component are identical to the keywords corresponding to the first proxy component.
Optionally, the second obtaining module 44 is specifically configured to:
extracting a demand keyword of the use request;
and determining a first operation request corresponding to the use request based on the mapping relation between the demand keywords and the operation request.
Optionally, when it is determined that the component type to be used is a content provider ContentProvider and the first component to be used is a first ContentProvider;
the first operation request is to add data, and the operation corresponding to the operation request is to add data to the first ContentProvider;
the first operation request is deleting data, and the operation corresponding to the operation request is inquiring data from the first ContentProvider;
the first operation request is modification data, and the operation corresponding to the operation request is modification data from the first ContentProvider;
the first operation request is query data, and the operation corresponding to the operation request is query data in the first ContentProvider.
In the technical scheme provided by the embodiment of the application, the components are packaged in the plug-in, the application program registers the proxy component, after receiving the use request of the user, the electronic equipment determines the type of the component to be used in the plug-in and the first component to be used based on the use request, and after recognizing that the first component is an unregistered component, the electronic equipment acquires the keyword corresponding to the first component, and further determines the first proxy component of the first component based on the correspondence between the keyword and the proxy component. After obtaining a first operation request based on the use request, sending the first operation request to the first proxy component, and calling the first component in the plug-in through the first proxy component so that the first component executes an operation corresponding to the first operation request in the plug-in. Because the first proxy component is registered, but the first component to be used in the plug-in is not registered, the application program can identify the first proxy component and can not identify the first component, so after obtaining the operation request based on the use request, the operation request is sent to the first proxy component, and then the operation request is returned to the first component by the first proxy component, the first component can execute the operation corresponding to the operation request in the plug-in, thereby completing the operation on the data in the plug-in.
The embodiment of the application also provides an electronic device, as shown in fig. 5, which comprises a processor 51, a communication interface 52, a memory 53 and a communication bus 54, wherein the processor 51, the communication interface 52 and the memory 53 complete communication with each other through the communication bus 54,
a memory 53 for storing a computer program;
the processor 51 is configured to implement any of the above methods for operating on data in the plug-in unit when executing the program stored in the memory 53.
The communication bus mentioned by the above terminal may be a peripheral component interconnect standard (Peripheral Component Interconnect, abbreviated as PCI) bus or an extended industry standard architecture (Extended Industry Standard Architecture, abbreviated as EISA) bus, etc. The communication bus may be classified as an address bus, a data bus, a control bus, or the like. For ease of illustration, the figures are shown with only one bold line, but not with only one bus or one type of bus.
The communication interface is used for communication between the terminal and other devices.
The memory may include random access memory (Random Access Memory, RAM) or 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 aforementioned processor.
The processor may be a general-purpose processor, including a central processing unit (Central Processing Unit, CPU for short), a network processor (Network Processor, NP for short), etc.; but also digital signal processors (Digital Signal Processor, DSP for short), application specific integrated circuits (Application Specific Integrated Circuit, ASIC for short), field-programmable gate arrays (Field-Programmable Gate Array, FPGA for short) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components.
In yet another embodiment provided herein, there is further provided a computer readable storage medium having a computer program stored therein, which when executed by a processor, implements a method of operating on data within a plug-in as described in any of the above embodiments.
In yet another embodiment provided herein, there is also provided a computer program product containing instructions that, when run on a computer, cause the computer to perform the method of operating on data within a plug-in as described in any of the above embodiments.
In the above embodiments, it may be implemented in whole or in part 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. When loaded and executed on a computer, produces a flow or function in accordance with embodiments of the present application, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer instructions may be stored in or transmitted from one computer-readable storage medium to another, for example, by wired (e.g., coaxial cable, optical fiber, digital Subscriber Line (DSL)), or wireless (e.g., infrared, wireless, microwave, etc.). The computer readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that contains an integration of one or more 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)), etc.
It is noted that relational terms such as first and second, and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Moreover, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
In this specification, each embodiment is described in a related manner, and identical and similar parts of each embodiment are all referred to each other, and each embodiment mainly describes differences from other embodiments. In particular, for the apparatus embodiments, the electronic device embodiments, the computer-readable storage medium embodiments, and the computer program product embodiments, the description is relatively simple, as relevant to the description of the method embodiments in part, since they are substantially similar to the method embodiments.
The foregoing description is only of the preferred embodiments of the present application and is not intended to limit the scope of the present application. Any modifications, equivalent substitutions, improvements, etc. that are within the spirit and principles of the present application are intended to be included within the scope of the present application.

Claims (10)

1. The method for operating the data in the plug-in is characterized by being applied to the electronic equipment of the Android system, and the plug-in is installed on an application program of the electronic equipment, and comprises the following steps:
receiving a use request, and determining the type of a component to be used in the plug-in and a first component to be used based on the use request; wherein the package has at least one type of component and at least one first component to be used encapsulated therein;
after the first component is identified as an unregistered component, acquiring a keyword corresponding to the first component; wherein the key words are fields for representing functions realized by the component;
determining a first proxy component corresponding to the first component based on the corresponding relation between the keyword and the proxy component; the first proxy component registers through the application program, and the keywords correspond to the proxy components through indexes;
Acquiring a first operation request based on the use request, wherein the first operation request carries an operation to be executed by the first component;
and sending the first operation request to the first proxy component, and calling the first component by the first proxy component so that the first component executes the operation corresponding to the first operation request in the plug-in.
2. The method of claim 1, wherein the step of determining the type of component to be used based on the use request comprises:
if the use request is for providing a data service, determining the type of the component to be used as a content provider ContentProvider;
if the use request is for providing the broadcast service, determining the type of the component to be used as a broadcast receiver BroadCastReceiver;
if the use request is for providing background Service, determining the type of the component to be used as Service;
and if the use request is for providing interface service, determining the type of the component to be used as Activity.
3. The method of claim 1, wherein the step of determining the first component to be used based on the use request comprises:
And determining a keyword according to the use request, and determining a first component to be used according to the corresponding relation between the keyword and the component.
4. The method according to claim 1, wherein the step of obtaining a first proxy component corresponding to the first component based on the correspondence between keywords and proxy components comprises:
acquiring an index list of the proxy component;
acquiring the package name of an application program, and mapping index information of a first proxy component from the index list according to a keyword corresponding to the first component and the package name of the application program;
determining a first proxy component corresponding to the first component based on index information of the first proxy component;
the index information comprises package names of application programs and keywords corresponding to the proxy components, and the keywords corresponding to the first component are identical to the keywords corresponding to the first proxy component.
5. The method of claim 1, wherein the step of obtaining a first operation request based on the use request comprises:
determining a demand keyword of the use request;
and determining a first operation request corresponding to the use request based on the corresponding relation between the demand keywords and the operation request.
6. The method according to claim 1, wherein when it is determined that the component type to be used is a content provider ContentProvider and the first component to be used is a first ContentProvider;
the first operation request is to add data, and the operation corresponding to the operation request is to add data to the first ContentProvider;
the first operation request is deleting data, and the operation corresponding to the operation request is inquiring data from the first ContentProvider;
the first operation request is modification data, and the operation corresponding to the operation request is modification data from the first ContentProvider;
the first operation request is query data, and the operation corresponding to the operation request is query data from the first ContentProvider.
7. An apparatus for operating on data in a plug-in, which is applied to an electronic device of an Android system, wherein a plug-in is installed on an application program of the electronic device, the apparatus includes:
the first determining module is used for receiving a use request and determining the type of a component to be used in the plug-in and a first component to be used based on the use request; wherein the package has at least one type of component and at least one first component to be used encapsulated therein;
The first acquisition module is used for acquiring keywords corresponding to the first component after identifying that the first component is an unregistered component; wherein the key words are fields for representing functions realized by the component;
the second determining module is used for determining a first proxy component corresponding to the first component based on the corresponding relation between the keywords and the proxy components; the first proxy component registers through the application program, and the keywords correspond to the proxy components through indexes;
the second acquisition module is used for acquiring a first operation request based on the use request, wherein the first operation request carries an operation to be executed by the first component;
and the calling module is used for sending the first operation request to the first proxy component, and the first proxy component calls the first component so that the first component executes the operation corresponding to the first operation request in the plug-in.
8. The apparatus of claim 7, wherein the first determining module is specifically configured to:
if the use request is for providing a data service, determining the type of the component to be used as a content provider ContentProvider;
If the use request is for providing the broadcast service, determining the type of the component to be used as a broadcast receiver BroadCastReceiver;
if the use request is for providing background Service, determining the type of the component to be used as Service;
and if the use request is for providing interface service, determining the type of the component to be used as Activity.
9. The electronic equipment is characterized by comprising a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory are communicated with each other through the communication bus;
a memory for storing a computer program;
a processor for carrying out the method steps of any one of claims 1-6 when executing a program stored on a memory.
10. A computer-readable storage medium, characterized in that the computer-readable storage medium has stored therein a computer program which, when executed by a processor, implements the method steps of any of claims 1-6.
CN202211586685.3A 2022-12-09 2022-12-09 Method, device, equipment and medium for operating data in plug-in Pending CN116016676A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202211586685.3A CN116016676A (en) 2022-12-09 2022-12-09 Method, device, equipment and medium for operating data in plug-in

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202211586685.3A CN116016676A (en) 2022-12-09 2022-12-09 Method, device, equipment and medium for operating data in plug-in

Publications (1)

Publication Number Publication Date
CN116016676A true CN116016676A (en) 2023-04-25

Family

ID=86027745

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202211586685.3A Pending CN116016676A (en) 2022-12-09 2022-12-09 Method, device, equipment and medium for operating data in plug-in

Country Status (1)

Country Link
CN (1) CN116016676A (en)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105825066A (en) * 2016-03-25 2016-08-03 东华软件股份公司 Method and device for generating electronic case history
CN108664265A (en) * 2018-05-15 2018-10-16 玩咖欢聚文化传媒(北京)有限公司 The interpolation method and system of Android application program
CN110226156A (en) * 2017-01-30 2019-09-10 微软技术许可有限责任公司 Attribute value between client and server it is synchronous
CN110389791A (en) * 2019-05-22 2019-10-29 百度在线网络技术(北京)有限公司 Component dispatching method, device, equipment and storage medium
CN112068903A (en) * 2020-09-21 2020-12-11 深圳市欢太科技有限公司 Application loading method, application loading device, medium and equipment

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105825066A (en) * 2016-03-25 2016-08-03 东华软件股份公司 Method and device for generating electronic case history
CN110226156A (en) * 2017-01-30 2019-09-10 微软技术许可有限责任公司 Attribute value between client and server it is synchronous
CN108664265A (en) * 2018-05-15 2018-10-16 玩咖欢聚文化传媒(北京)有限公司 The interpolation method and system of Android application program
CN110389791A (en) * 2019-05-22 2019-10-29 百度在线网络技术(北京)有限公司 Component dispatching method, device, equipment and storage medium
CN112068903A (en) * 2020-09-21 2020-12-11 深圳市欢太科技有限公司 Application loading method, application loading device, medium and equipment

Similar Documents

Publication Publication Date Title
CN110209505B (en) Data request method and related equipment
CN111078504A (en) Distributed call chain tracking method and device, computer equipment and storage medium
CN105512044B (en) Update method and system for the library of object of keyword driving test
CN116204438A (en) Test case generation method, automatic test method and related device
CN112699034B (en) Virtual login user construction method, device, equipment and storage medium
WO2024109543A1 (en) Vehicle-to-cloud communication method based on service-oriented architecture, and storage medium
CN111443920B (en) Frame migration method and device
CN110798358B (en) Distributed service identification method and device, computer readable medium and electronic equipment
CN114640657A (en) Multi-registration center fusion method and device
CN108647139B (en) System test method, device, storage medium and electronic device
CN116016676A (en) Method, device, equipment and medium for operating data in plug-in
CN115858320A (en) Operation log recording method, apparatus, medium and product
CN109348053B (en) Telephone number mark processing method, server, terminal device and computer readable storage medium
CN112667949A (en) Data processing method and device for front-end gateway
CN109194734B (en) Message pushing method and device, server and readable storage medium
CN111225075A (en) Configuration method and device for Internet of things directional access service
CN113704320B (en) Data processing method, device, electronic equipment and storage medium
CN113342423B (en) Configuration file updating method and device
CN109285036B (en) Internet of things service processing method and device and storage medium
CN114363221B (en) Heartbeat detection method, storage medium, electronic equipment and system based on micro-service system
KR20130113788A (en) System and method for distinguishing service registration ip of pc-room
CN115766532A (en) Link monitoring method and device, storage medium and electronic device
CN114064313A (en) Attribute information acquisition method, attribute information acquisition device, attribute information acquisition equipment and attribute information acquisition medium
CN115687920A (en) Data processing method, device, server and computer readable storage medium
CN117950745A (en) Micro front end-based sub-application registration method, device, equipment and storage medium

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