CN113535140A - Parameter packaging method, device, equipment and storage medium - Google Patents
Parameter packaging method, device, equipment and storage medium Download PDFInfo
- Publication number
- CN113535140A CN113535140A CN202010300090.1A CN202010300090A CN113535140A CN 113535140 A CN113535140 A CN 113535140A CN 202010300090 A CN202010300090 A CN 202010300090A CN 113535140 A CN113535140 A CN 113535140A
- Authority
- CN
- China
- Prior art keywords
- parameter
- channel
- data
- application
- constructed
- 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.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
Abstract
The embodiment of the invention discloses a parameter packaging method, a parameter packaging device, parameter packaging equipment and a storage medium. The method comprises the following steps: when a trigger event of the package parameters is monitored, acquiring the parameter of the access parameter corresponding to the trigger event; transferring the parameter to a pre-constructed parameter encapsulation function so that the parameter encapsulation function queries target data from a pre-constructed database according to the parameter, respectively filling each field data in the target data into corresponding fields of a pre-constructed entity class according to a pre-constructed field mapping relation, and outputting each field data in the entity class; and obtaining the packaged parameters according to the output result of the parameter packaging function. According to the technical scheme of the embodiment of the invention, the problems that errors are easy to occur and the efficiency of the operation flow is low due to the manual packaging process of the parameters are solved, the automatic packaging of the parameters in the Android subpackaging scheme is realized, the accuracy of the parameters is effectively ensured, and the packaging efficiency of the parameters is improved.
Description
Technical Field
The embodiment of the invention relates to the technical field of computers, in particular to a parameter packaging method, a parameter packaging device, parameter packaging equipment and a storage medium.
Background
The parameter encapsulation link in the Android packetization scheme is usually implemented by program developers writing corresponding packetization codes based on Integrated Development Environment (IDE), and a large number of codes need to be modified in the packetization process to implement packetization of different channels, but the manually implemented parameter encapsulation process is prone to errors and the operation flow efficiency is low.
Disclosure of Invention
The embodiment of the invention provides a parameter packaging method, device, equipment and storage medium, and aims to achieve the effect of automatically packaging parameters in an Android subpackaging scheme.
In a first aspect, an embodiment of the present invention provides a parameter encapsulation method, which may include:
when a trigger event of the package parameters is monitored, acquiring parameter access parameters corresponding to the trigger event, wherein the parameter access parameters comprise application identification parameters and channel identification parameters to be newly added;
transmitting the parameter of the input parameter to a parameter encapsulation function which is constructed in advance;
obtaining packaged parameters according to an output result of the parameter packaging function, wherein the packaged parameters comprise packaged application parameter information and channel parameter information;
the parameter encapsulation function can realize parameter encapsulation through the following steps:
inquiring target data from a pre-constructed database according to the parameter of the parameter;
and respectively filling each field data in the target data into corresponding fields of the entity class which is constructed in advance according to the mapping relation of the fields which are constructed in advance, and outputting each field data in the entity class.
Optionally, querying target data from a pre-constructed database according to the parameter of interest may include:
inquiring target application data corresponding to the application identification parameters from a pre-constructed application database;
correspondingly, according to the pre-constructed field mapping relationship, filling each field data in the target data into the corresponding field of the pre-constructed entity class, and outputting each field data in the entity class, including:
respectively filling each field data in the target application data into corresponding fields of a pre-constructed application entity class according to a pre-constructed application field mapping relation;
and outputting the data of each field in the application entity class.
Optionally, querying target application data corresponding to the application identification parameter from a pre-constructed application database may include:
checking the application identification parameters;
and if the application identification parameter is determined to be a legal parameter according to the verification result, inquiring target application data corresponding to the application identification parameter from a pre-constructed application database.
Optionally, querying target data from a pre-constructed database according to the parameter of interest may include:
inquiring channel data from a pre-constructed channel database, and splitting an absent channel identification parameter which does not exist in an inquiry result from a channel identification parameter;
inserting channel data corresponding to the channel identification parameters which do not exist into a channel database, and updating the channel database according to an insertion result;
taking each channel data in the channel database as target channel data;
correspondingly, according to the pre-constructed field mapping relationship, filling each field data in the target data into the corresponding field of the pre-constructed entity class, and outputting each field data in the entity class, including:
respectively filling each field data in the target channel data into corresponding fields of a channel entity class which is constructed in advance according to a channel field mapping relation which is constructed in advance;
and outputting the data of each field in the entity class of the channel.
Optionally, splitting the channel identification parameter that does not exist in the query result from the channel identification parameter may include:
filtering the non-existing channel identification parameters which do not exist in the query result from the channel identification parameters based on a preset filtering function;
existing channel identification parameters that do not exist in the non-existing channel identification parameters are filtered out from the channel identification parameters based on a preset filtering function.
Optionally, each piece of application data in the application database may include application identification information, an application name, a package name, and a platform type, and/or each piece of channel data in the channel database may include channel identification information, application identification information, a channel name, and a platform type.
Optionally, obtaining the encapsulated parameter according to the output result of the parameter encapsulation function may include:
obtaining filled parameters according to the output result of the parameter encapsulation function;
and encapsulating the filled parameters in a pre-constructed parameter encapsulation object, and obtaining encapsulated parameters based on the parameter encapsulation object.
In a second aspect, an embodiment of the present invention further provides a parameter packaging apparatus, where the apparatus may include:
the acquisition module is used for acquiring the parameter of the participating channel corresponding to the trigger event when the trigger event of the package parameter is monitored, wherein the parameter of the participating channel comprises an application identification parameter and a channel identification parameter to be newly added;
the transmission module is used for transmitting the parameter to a pre-constructed parameter encapsulation function so that the parameter encapsulation function queries target data from a pre-constructed database according to the parameter, respectively fills each field data in the target data into a corresponding field of a pre-constructed entity class according to a pre-constructed field mapping relation, and outputs each field data in the entity class;
and the encapsulation module is used for obtaining encapsulated parameters according to the output result of the parameter encapsulation function, wherein the encapsulated parameters comprise encapsulated application parameter information and channel parameter information.
In a third aspect, an embodiment of the present invention further provides an apparatus, where the apparatus may include:
one or more processors;
a memory for storing one or more programs;
when the one or more programs are executed by the one or more processors, the one or more processors are caused to implement the parameter encapsulation method provided by any embodiment of the invention.
In a fourth aspect, an embodiment of the present invention further provides a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements the parameter packaging method provided in any embodiment of the present invention.
According to the technical scheme of the embodiment of the invention, when the trigger event of the packaging parameter is monitored, the input parameter corresponding to the trigger event is obtained, and the input parameter is transmitted to the pre-constructed parameter packaging function, so that the packaged parameter can be obtained according to the output result of the parameter packaging function. According to the technical scheme, the problems that errors are easy to occur and the operation process efficiency is low due to the manual packaging process of the parameters are solved, the automatic packaging of the parameters in the Android subpackaging scheme is realized, the accuracy of the parameters is effectively guaranteed, and meanwhile, the packaging efficiency of the parameters can be greatly improved.
Drawings
FIG. 1 is a flowchart of a parameter packaging method according to an embodiment of the present invention;
FIG. 2 is a flowchart of a parameter packaging method according to a second embodiment of the present invention;
FIG. 3 is a flowchart of a parameter packaging method according to a third embodiment of the present invention;
FIG. 4 is a block diagram of a parameter packaging apparatus according to a fourth embodiment of the present invention;
fig. 5 is a schematic structural diagram of an apparatus in the fifth embodiment of the present invention.
Detailed Description
The present invention will be described in further detail with reference to the accompanying drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the invention and are not limiting of the invention. It should be further noted that, for the convenience of description, only some of the structures related to the present invention are shown in the drawings, not all of the structures.
Example one
Fig. 1 is a flowchart of a parameter packaging method according to an embodiment of the present invention. The embodiment can be suitable for the condition of automatically packaging the parameters in the Android subpackage scheme, and is particularly suitable for the condition of automatically packaging the parameters in the Android subpackage scheme based on the pre-constructed parameter packaging function. The method can be executed by a parameter encapsulation device provided by the embodiment of the invention, the device can be realized by software and/or hardware, and the device can be integrated on various user terminals or servers.
Referring to fig. 1, the method of the embodiment of the present invention specifically includes the following steps:
s110, when a trigger event of the package parameters is monitored, obtaining parameter access parameters corresponding to the trigger event, wherein the parameter access parameters comprise application identification parameters and channel identification parameters to be added newly.
In the program running process, the triggering event of the package parameter may be a calling event of a parameter package function, an obtaining event of a parameter, an input event of a parameter, or the like, which is not specifically limited herein. When a trigger event of the package parameter is monitored, a parameter corresponding to the trigger event may be obtained, where the parameter may include an application identification parameter and a channel identification parameter to be added, the application identification parameter may uniquely identify identification information (id) of an application, and the channel identification parameter may identify identification information of a channel to be added. It should be noted that the channel identification parameter setting means that there may be differences in sub-packages applied to different channels, for example, the sub-package applied to the same application in the a application market and the sub-package applied to the B application market are likely to be different sub-packages, and the a application market and the B application market are two channels.
S120, the parameter package function queries target data from a pre-constructed database according to the parameter, fills each field data in the target data into a corresponding field of a pre-constructed entity class according to a pre-constructed field mapping relation, and outputs each field data in the entity class.
The parameter encapsulation function may be configured to perform parameter encapsulation according to the parameter, for example, the parameter encapsulation function may query target data corresponding to the parameter from a pre-constructed database, and output the target data. For example, each piece of data in the database may include a plurality of fields, and an entity class corresponding to the database may be pre-constructed according to the field composition of each piece of data in the database, thereby implementing a one-to-one mapping relationship between each piece of field data in the database and each piece of field data in the entity class, where the mapping relationship may be stored in the pre-constructed field mapping relationship. Therefore, in the output process of the target data, the field data in the target data is filled into the corresponding field of the entity class according to the field mapping relationship, and the field data in the entity class can be used as the output result of the parameter encapsulation function.
It should be noted that, first, for different types of parameter entries, the parameter encapsulation function may implement parameter encapsulation through different implementation logics, which is not specifically limited herein. Secondly, the database can comprise an application database and a channel database, so that target application data can be inquired from the application database according to the application identification parameters, target channel data can be inquired from the channel database according to the channel identification information, and the target application data and the target channel data are jointly used as target data. Of course, each application data and each channel data may also be stored in one database, which is not specifically limited herein.
For example, taking the application identification parameter as an Integer type of parameter appId, and the channel identification parameter as a List < String > type of parameter addchaneldlist, the parameter encapsulation function may be as follows: ResultParam fetchParams (Integer appId, List < String > addChannelIdList), wherein fetchParams is the function name of the parameter encapsulation function, Integer appId is the first argument parameter appId with the type of Integer, List < String > addChannelIdList) is the second argument parameter addChannelIdList with the type of List < String >, and the return argument of the parameter encapsulation function is a ResultParam result argument with a custom type.
S130, obtaining packaged parameters according to the output result of the parameter packaging function, wherein the packaged parameters comprise packaged application parameter information and channel parameter information.
The packaged parameters can be obtained according to the output result of the parameter packaging function, for example, the output result of the parameter packaging function may be packaged parameters, and the packaged parameters may be result parameters for packaging the target data queried from the database into the objects of the corresponding type, thereby completely converting the contents that need to be manually filled in the existing scheme into automatic filling. For example, if the return parameter of the parameter wrapper function is a ResultParam result parameter of a custom type, the wrapped parameter may be a result parameter that stores the target data into ResultParam. After the packaged parameters are obtained, the packaged parameters can be transmitted to a calling party of the parameter packaging function, so that the subsequent link of Android subpackaging is realized.
For another example, the output result of the parameter encapsulation function may be a filled parameter, and the filled parameter may be a result parameter obtained by filling the target data queried in the database into the object of the corresponding type, and then encapsulating the result parameter (i.e., the filled parameter) in the pre-constructed parameter encapsulation object, which is equivalent to wrapping the output result of the parameter encapsulation function by one layer again. In practical applications, taking the example that the parameter encapsulation object is a baseResult object and the ResultParam result parameter includes app and allchannellst, an empty baseResult object is constructed by calling baseResult ═ new baseResult (), then corresponding app field data in the baseResult object is filled by calling baseresult.setapp, and corresponding channel field data in the baseResult object is filled by calling baseresult.setapp, and finally all encapsulated parameters are returned to the calling party of the parameter encapsulation function by returning the baseResult, thereby implementing automatic encapsulation of the parameters.
According to the technical scheme of the embodiment of the invention, when the trigger event of the packaging parameter is monitored, the input parameter corresponding to the trigger event is obtained, and the input parameter is transmitted to the pre-constructed parameter packaging function, so that the packaged parameter can be obtained according to the output result of the parameter packaging function. According to the technical scheme, the problems that errors are easy to occur and the operation process efficiency is low due to the manual packaging process of the parameters are solved, the automatic packaging of the parameters in the Android subpackaging scheme is realized, the accuracy of the parameters is effectively guaranteed, and meanwhile, the packaging efficiency of the parameters can be greatly improved.
Example two
Fig. 2 is a flowchart of a parameter packaging method according to a second embodiment of the present invention. The present embodiment is optimized based on the above technical solutions. In this embodiment, optionally, if the parameter entry parameter is an application identifier parameter, the parameter encapsulation function may implement parameter encapsulation by the following steps: inquiring target application data corresponding to the application identification parameters from a pre-constructed application database; respectively filling each field data in the target application data into corresponding fields of a pre-constructed application entity class according to a pre-constructed application field mapping relation; and outputting the data of each field in the application entity class.
The same or corresponding terms as those in the above embodiments are not explained in detail herein.
Referring to fig. 2, the method of the present embodiment may specifically include the following steps:
s210, when a trigger event of the package parameters is monitored, obtaining parameter access parameters corresponding to the trigger event, wherein the parameter access parameters comprise application identification parameters and channel identification parameters to be added newly.
S220, transmitting the application identification parameters to a pre-constructed parameter encapsulation function so that the parameter encapsulation function queries target application data corresponding to the application identification parameters from a pre-constructed application database; and respectively filling each field data in the target application data into corresponding fields of the application entity class which is constructed in advance according to the mapping relation of the application fields which are constructed in advance.
The application database can be a set of pre-constructed multi-client compatible data structure, and the application database is matched with the parameter encapsulation function and can be used for realizing the multi-client compatible parameter encapsulation function. Each piece of application data in the application database may include fields such as application identification information, application name, package name, platform type, etc., which may be used to represent specific client-related information. Further, according to the field composition of each piece of application data in the application database, an application entity class corresponding to the application database can be constructed in advance, so that the one-to-one mapping relation between each piece of field data in the application database and each piece of field data in the application entity class is realized. The mapping relation can be stored in a pre-constructed application field mapping relation, each field data in the target application data can be filled into a corresponding field of an application entity class according to the application field mapping relation, and each field data in the application entity class can be part of the content in the output result of the parameter encapsulation function.
Therefore, according to the application identification parameters, corresponding target application data can be queried from the application database, each piece of target application data can comprise fields such as application identification information, an application name, a package name, a platform type and the like, and the step can be that the application data with the application identification information consistent with the application identification parameters is used as the target application data; further, according to the mapping relationship of the application fields, the field data in the target application data may be respectively filled into the corresponding fields of the application entity class, for example, the data of the application identification information in the target application data is filled into the application identification information of the application entity class.
On the basis, optionally, before the target application data is queried from the application database, the application identification parameter can be checked, and if the application identification parameter is determined to be a legal parameter according to the check result, the target application data is queried from the application database; otherwise, the parameter encapsulation function can be directly skipped. For example, taking the application identification parameter appId as an example, if the if (appId < ═ 0) is established by calling, this indicates that appId is an illegal parameter, because the application identification information in the target application data must be greater than 0, an Exception may be thrown by using a throw Exception ("appId parameter Exception"), thereby ending the whole function flow; if the if is called (appId < ═ 0) does not hold, which indicates that appId is a legal parameter, the corresponding target application data can be queried from the application database.
And S230, obtaining packaged parameters according to the field data in the application entity class output by the parameter packaging function, wherein the packaged parameters comprise packaged application parameter information and channel parameter information.
According to the technical scheme of the embodiment of the invention, the parameter encapsulation function queries the target application data corresponding to the application identification parameter from the pre-constructed application database, so that each field data in the target application data can be respectively filled into the corresponding field of the application entity class according to the mapping relation of the application field, and the effect of automatically encapsulating the application parameter information corresponding to the application identification parameter is realized.
In order to better understand the specific implementation process of the above steps, the parameter encapsulation method of the present embodiment is exemplarily described below with reference to specific examples. Illustratively, taking the application database as an application table structure as an example, the application table structure (i.e., app table structure) may be pre-constructed in the following manner:
the primary key id is application identification information, each client normally has a unique code, and a field "package name _ name" is set to indicate the unique code of each client. Meanwhile, which platform type each application app corresponds to can be quickly distinguished through the field "platform type platform". It should be noted that the uniqueness of the primary key id can only guarantee the uniqueness of each piece of data, but it cannot guarantee the uniqueness of the data content of each piece of data, for example, the id of a piece of data is 1 and the data content is 3 pieces 555, the id of a piece of data is 2 and the data content is 555, and these 2 pieces of data have different ids but the same data content, so that the possibility of application duplication may occur. Theoretically, a sub-package can be uniquely determined according to the package _ name, but the speed of directly searching through the package _ name is low, id is equivalent to an index, a certain piece of data can be quickly searched through id, and the uniqueness of the data content of the piece of data is further ensured through the package _ name.
Further, for the result parameter of the return parameter ResultParam of the parameter encapsulation function, the specific structure of the entity class is related to the application table structure, so that the application entity class of the application app can be constructed before the ResultParam entity class is constructed. In order to implement a one-to-one mapping relationship between an application entity class and an application table structure, where the mapping relationship includes a package name and a type, the application entity class may be as follows: data Class App (val title: String;, val packageName: String;, val platform: Int: 0), wherein the application entity Class is a Class of Data Class, the Class name is App, which has 3 parameters, respectively, application name title, package name packageName, and platform type platform, and the 3 parameters correspond to the application table structure one by one. Similarly, a channel entity class corresponding to the channel table structure may also be pre-constructed, for example, a Data class Channle (val appId; Int ═ 0, val name: String ═ and val platform: Int ═ 0), and the specific meaning of the channel entity class is similar to that of the application entity class, and is not described herein again.
Thus, the pre-constructed ResultParam entity class may be as follows: data Class ResultParam { val App: App? Null, val channelList: List < channel >? Null, which has 2 parameters, respectively App of App type and channellst of List < channel > type, which 2 parameters can be initialized to null in the build phase. The data structure of the ResultParam entity class determines the data structure of the return parameters of the parameter encapsulation function.
On this basis, the application field mapping relationship can be as follows:
further, the query of the target application data may be implemented by:
the code defines a findAllById function, the return types of the findAllById function are consistent with the mapping relation of the application fields and are data of a BaseResultMap type, and the obtained target application data can be encapsulated into an application entity class. Specifically, target application data in the form of (id, title, package _ name, platform) is queried according to id through a select (id, title, package _ name, platform) from app where id [ #{ id, jdbcctype ═ INTEGER } statement, and the target application data is encapsulated into an application entity class by taking an application field mapping relationship BaseResultMap as a bridge. First, the query efficiency of a select (id, title, package _ name, platform) is higher than that of a select. Secondly, id is a main key with uniqueness, so that the inquired target application data is definitely a piece of data, but the ORM framework inquires a data set through a select statement, because the number of data in the inquiry result cannot be known, the inquiry result is directly packaged in the data set and returned, even if only one piece of data exists in the inquiry result. To avoid extracting data from the data set again, the data set may be limited in number by limit1, and the ORM framework extracts a piece of data from the data set and returns the piece of data, where the target application data is a piece of data, and the target application data may be marked as an app.
EXAMPLE III
Fig. 3 is a flowchart of a parameter packaging method provided in the third embodiment of the present invention. The present embodiment is optimized based on the above technical solutions. In this embodiment, optionally, if the parameter entry parameter is a channel identifier parameter, the parameter encapsulation function may implement parameter encapsulation by the following steps: inquiring channel data from a pre-constructed channel database, and splitting an absent channel identification parameter which does not exist in an inquiry result from a channel identification parameter; inserting channel data corresponding to the channel identification parameters which do not exist into a channel database, and updating the channel database according to an insertion result; taking each channel data in the channel database as target channel data, and respectively filling each field data in the target channel data into corresponding fields of a channel entity class which is constructed in advance according to a channel field mapping relation which is constructed in advance; and outputting the data of each field in the entity class of the channel. The same or corresponding terms as those in the above embodiments are not explained in detail herein.
Referring to fig. 3, the method of this embodiment may specifically include the following steps:
s310, when a trigger event of the package parameters is monitored, obtaining parameter access parameters corresponding to the trigger event, wherein the parameter access parameters comprise application identification parameters and channel identification parameters to be added newly.
S320, transmitting the channel identification parameters to a pre-constructed parameter encapsulation function so that the parameter encapsulation function queries each channel data from a pre-constructed channel database and splits the channel identification parameters which do not exist in the query result; inserting channel data corresponding to the channel identification parameters which do not exist into a channel database, and updating the channel database according to an insertion result; taking each channel data in the channel database as target channel data, and respectively filling each field data in the target channel data into corresponding fields of a channel entity class which is constructed in advance according to a channel field mapping relation which is constructed in advance; and outputting the data of each field in the entity class of the channel.
The Android subpackage realizes the subpackage function aiming at different channels, and a channel database which has a mapping relation with the application database can be set. Each piece of channel data in the channel database can comprise fields such as channel identification information, application identification information, channel names and platform types, one-to-one correspondence between the application databases and the channel database is achieved through the application identification information in the channel data and the application identification information in the application data, and compared with a conventional foreign key setting mode, the scheme can not cause a strong dependency relationship between the two databases, so that the problem that data structures cannot be decoupled can not occur.
On the basis, the channel identification parameter can identify the identification information of the channel to be newly added, namely the channel set information to be added, and the channel set information can not be verified. Moreover, because the channel identification parameter is transmitted by a calling party calling the parameter encapsulation function, whether channel data corresponding to the channel identification parameter exists in the channel database cannot be determined, so that the channel identification parameter can be split into an existing channel identification parameter existing in the channel database and an absent channel identification parameter not existing in the channel database, and the channel data corresponding to the absent channel identification parameter is inserted into the channel database, thereby realizing the synchronization function of the channel information in the parameter filling process.
Specifically, all channel data are queried from the channel database, so that the channel identification parameters which do not exist in the query result can be split from the channel identification parameters, namely the channel data corresponding to the channel identification parameters which do not exist in the channel database, the channel data can be inserted into the channel database, and the channel database is updated according to the insertion result; and outputting the data of each channel in the channel database. Of course, each channel data in the output channel database may be presented in various forms, for example, referring to the output mode of the target application data in the second embodiment of the present invention, each channel data in the channel database is used as the target channel data, and each field data in the target channel data may be respectively filled into a corresponding field of a channel entity class constructed in advance according to a mapping relationship of channel fields constructed in advance, for example, data of channel identification information in the target channel data is filled into channel identification information of the channel entity class, and the channel entity class may be used as an output result of the parameter encapsulation function.
On this basis, optionally, splitting an absent channel identification parameter that is not present in the query result from the channel identification parameter may include: filtering the non-existing channel identification parameters which do not exist in the query result from the channel identification parameters based on a preset filtering function; the existing channel identification parameters which do not exist in the non-existing channel identification parameters are filtered out from the channel identification parameters based on the preset filtering function, so that the accurate splitting of the non-existing channel identification parameters is realized, and the existing channel identification parameters are key factors of subsequent channel data synchronization.
S330, obtaining packaged parameters according to the channel data in the channel database output by the parameter packaging function, wherein the packaged parameters comprise packaged application parameter information and channel parameter information.
According to the technical scheme of the embodiment of the invention, the parameter encapsulation function queries each channel data from a channel database which is constructed in advance so as to split the channel identification parameters which do not exist in the query result from the channel identification parameters; therefore, the channel data corresponding to the channel identification parameters can be inserted into the channel database, and the channel database is updated according to the insertion result, so that the synchronization function of the channel information is realized; and then, outputting each channel data in the channel database, thereby realizing filling and packaging of the parameters.
In order to better understand the specific implementation process of the above steps, the parameter encapsulation method of the present embodiment is exemplarily described below with reference to specific examples. Illustratively, taking the channel database as a channel table structure as an example, in order to construct a channel table structure having a mapping relationship with the application table structure, the channel table structure may be pre-constructed in the following manner:
wherein, the application identification information corresponding to the piece of channel data can be determined through a field "application id app _ id" in the channel table structure. Meanwhile, which platform type each channel corresponds to can be quickly distinguished through the field "platform type platform", which can improve the acquisition efficiency of the platform types.
Further, for the result parameter of the return parameter ResultParam of the parameter encapsulation function, the specific structure of the entity class is related to the channel table structure, so that the channel entity class of the channel can be constructed before the ResultParam entity class is constructed. Moreover, in order to implement the one-to-one mapping relationship between the channel entity classes and the channel table structure, the channel entity classes can be constructed according to the field composition of each channel data in the channel database, and the specific form can be as follows: data Class Channle (val appId; Int is 0, val name: String, and val platform: Int is 0), wherein the channel entity Class is a Class of Data Class, the Class name is Channle, and the channel entity Class has 3 parameters, namely application id appId, channel name and platform type, and the 3 parameters correspond to the channel table structure one by one.
Thus, the pre-constructed ResultParam entity class may be as follows: data Class ResultParam { val App: App? Null, val channelList: List < channel >? Null, which has 2 parameters, respectively App of App type and channellst of List < channel > type, which 2 parameters can be initialized to null in the build phase. The data structure of the ResultParam entity class determines the data structure of the return parameters of the parameter encapsulation function.
On the basis, the channel field mapping relation can be constructed in the following way, so that the channel data inquired from the channel table structure is packaged into the channel entity class based on the channel field mapping relation:
further, the query of each channel data in the channel database can be realized through the following codes:
and querying all Channel data in a Channel table structure by calling a select function, representing all Channel data in a query Channel database by a constant true where value condition, and marking a query result as List < Channel > dbChannelList.
Further, the element information that the element in addchaneldlist (second parameter of fetchParams function) is included in dbChannelList may be filtered out, and the data dbChannelList existing in the channel table structure may be split from addchaneldlist, or in other words, an element common to both addchaneldlist and dbChannelList may be found. The specific filtration mode is as follows:
filter (channel- > { return | (b) channellst. contacts) }, wherein the filter function (preset filter function) in the addchanellist is called to realize the one-by-one filtering of each piece of data in the addchanellist, and each piece of data is called as a channel, namely, the function parameter in each round training process is a channel; and then, judging whether the dbChannelList contains a channel by calling the dbChannelList, if so, returning true, otherwise, returning false, wherein the return result of the filter function is filtered object information which is not contained through a negation operation (!), and marking the return result as a tmp1List, namely the object information in the tmp1List is different channel data in the addChannelIdList and the dbChannelList, the channel data is channel data corresponding to the channel identification parameter which does not exist, and the tmp1List is a subset of the addChannelIdList. And further, filtering the number of elements which do not contain tme1List in the addChannelIdList by using an addChannelIdList filter (channel- > { return! tme1List. contacts) }, marking the filtered result as tme2List, wherein the object information in the tmp2List is the channel data corresponding to the existing channel identification parameter.
Aiming at channel data which does not have channel identification parameters and corresponds to the channel data, automatic insertion operation can be executed on the channel data, and the specific operation scheme is as follows:
the method comprises the steps of performing insertion processing on Channel data which does not exist in a Channel database through an < insert > tag, wherein the inserted parameter type is a Channel type, and then assigning values to the inserted data by calling insert inter Channel (title, package _ name, platform) values, (# { title, jdbcc type ═ String }, # { packageName, jdbcc type ═ String }, # { platform, jdbcc type ═ Integer }) indicates that corresponding field data are sequentially extracted from the parameter Channel and filled into corresponding fields of the inserted data. Thus, the individual pieces of channel data in the tmp1List may be inserted into the channel database.
Addall (tmp2List) gets all channel data in the channel database by calling dbchannellst and marks it as allchannellst ═ dbchannellst. Therefore, each field data in the channel data can be filled into the corresponding field of the channel entity class according to the mapping relation of the channel field, and each field data in the channel entity class can be part of the content in the output result of the parameter encapsulation function.
Example four
Fig. 4 is a block diagram of a parameter packaging apparatus according to a fourth embodiment of the present invention, which is configured to execute the parameter packaging method according to any of the embodiments. The device and the parameter packaging method of each embodiment belong to the same inventive concept, and details which are not described in detail in the embodiment of the parameter packaging device can refer to the embodiment of the parameter packaging method. Referring to fig. 4, the apparatus may specifically include: an acquisition module 410, a delivery module 420, and an encapsulation module 430.
The obtaining module 410 is configured to obtain a parameter to be entered corresponding to a trigger event when the trigger event of the package parameter is monitored, where the parameter to be entered includes an application identification parameter and a channel identification parameter to be newly added;
a transfer module 420, configured to transfer the parameter to a pre-constructed parameter encapsulation function, so that the parameter encapsulation function queries target data from a pre-constructed database according to the parameter, fills each field data in the target data into a corresponding field of a pre-constructed entity class according to a pre-constructed field mapping relationship, and outputs each field data in the entity class;
the encapsulating module 430 is configured to obtain an encapsulated parameter according to an output result of the parameter encapsulating function, where the encapsulated parameter includes encapsulated application parameter information and channel parameter information.
Optionally, the transmission module 420 may specifically include:
the first transmission unit is used for transmitting the parameter of the input parameter to a pre-constructed parameter encapsulation function so that the parameter encapsulation function queries target application data corresponding to the application identification parameter from a pre-constructed application database; respectively filling each field data in the target application data into corresponding fields of a pre-constructed application entity class according to a pre-constructed application field mapping relation; and outputting the data of each field in the application entity class.
Optionally, the first transmission unit may specifically include:
the verifying subunit is used for verifying the application identification parameters;
and the query subunit is used for querying the target application data corresponding to the application identification parameter from a pre-constructed application database if the application identification parameter is determined to be a legal parameter according to the verification result.
Optionally, the transmission module 420 may specifically include:
the second transfer unit is used for transferring the parameter of the input parameter to a pre-constructed parameter encapsulation function so that the parameter encapsulation function queries each channel data from a pre-constructed channel database and splits the channel identification parameters which do not exist in the query result; inserting channel data corresponding to the channel identification parameters which do not exist into a channel database, and updating the channel database according to an insertion result; taking each channel data in the channel database as target channel data, and respectively filling each field data in the target channel data into corresponding fields of a channel entity class which is constructed in advance according to a channel field mapping relation which is constructed in advance; and outputting the data of each field in the entity class of the channel.
Optionally, the second transmission unit may specifically include:
the device comprises a channel identification parameter filter subunit, a query result filter subunit and a channel identification parameter filtering subunit, wherein the channel identification parameter filter subunit is used for filtering the channel identification parameters which do not exist in the query result based on a preset filter function;
and the existing channel identification parameter filtering subunit is used for filtering the existing channel identification parameters which do not exist in the non-existing channel identification parameters from the channel identification parameters based on a preset filtering function.
Optionally, each piece of application data in the application database may include application identification information, an application name, a package name, and a platform type, and/or each piece of channel data in the channel database may include channel identification information, application identification information, a channel name, and a platform type.
Optionally, the encapsulation module 430 may specifically include:
the filling unit is used for obtaining filled parameters according to the output result of the parameter encapsulation function;
and the packaging unit is used for packaging the filled parameters in the pre-constructed parameter packaging object and obtaining the packaged parameters based on the parameter packaging object.
In the parameter encapsulation device provided by the fourth embodiment of the present invention, when a trigger event of an encapsulation parameter is monitored, the acquisition module, the transfer module and the encapsulation module are matched with each other, so as to acquire an entry parameter corresponding to the trigger event, and transfer the entry parameter to a pre-constructed parameter encapsulation function, thereby obtaining the encapsulated parameter according to an output result of the parameter encapsulation function. The device solves the problems of easy error and low operation process efficiency caused by the manual packaging process of the parameters, realizes the automatic packaging of the parameters in the Android subpackage scheme, and can greatly improve the packaging efficiency of the parameters while effectively ensuring the accuracy of the parameters.
The parameter packaging device provided by the embodiment of the invention can execute the parameter packaging method provided by any embodiment of the invention, and has corresponding functional modules and beneficial effects of the execution method.
It should be noted that, in the embodiment of the parameter packaging apparatus, the included units and modules are merely divided according to functional logic, but are not limited to the above division as long as the corresponding functions can be implemented; in addition, specific names of the functional units are only for convenience of distinguishing from each other, and are not used for limiting the protection scope of the present invention.
EXAMPLE five
Fig. 5 is a schematic structural diagram of an apparatus according to a fifth embodiment of the present invention, as shown in fig. 5, the apparatus includes a memory 510, a processor 520, an input device 530, and an output device 540. The number of processors 520 in the device may be one or more, and one processor 520 is taken as an example in fig. 5; the memory 510, processor 520, input device 530, and output device 540 in the apparatus may be connected by a bus or other means, such as by bus 550 in fig. 5.
The memory 510 is used as a computer-readable storage medium for storing software programs, computer-executable programs, and modules, such as program instructions/modules corresponding to the parameter encapsulation method in the embodiment of the present invention (for example, the obtaining module 410, the delivering module 420, and the encapsulating module 430 in the parameter encapsulation apparatus). The processor 520 implements the parameter encapsulation method described above by executing software programs, instructions, and modules stored in the memory 510 to perform various functional applications of the device and data processing.
The memory 510 may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required for at least one function; the storage data area may store data created according to use of the device, and the like. Further, the memory 510 may include high speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other non-volatile solid state storage device. In some examples, memory 510 may further include memory located remotely from processor 520, which may be connected to devices through a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
The input device 530 may be used to receive input numeric or character information and generate key signal inputs related to user settings and function control of the device. The output device 540 may include a display device such as a display screen.
EXAMPLE six
An embodiment of the present invention provides a storage medium containing computer-executable instructions, which when executed by a computer processor, are configured to perform a parameter packing method, where the method includes:
when a trigger event of the package parameters is monitored, acquiring parameter access parameters corresponding to the trigger event, wherein the parameter access parameters comprise application identification parameters and channel identification parameters to be newly added;
transmitting the parameter of the input parameter to a parameter encapsulation function which is constructed in advance;
obtaining packaged parameters according to an output result of the parameter packaging function, wherein the packaged parameters comprise packaged application parameter information and channel parameter information;
the parameter encapsulation function can realize parameter encapsulation through the following steps:
inquiring target data from a pre-constructed database according to the parameter of the parameter;
and respectively filling each field data in the target data into corresponding fields of the entity class which is constructed in advance according to the mapping relation of the fields which are constructed in advance, and outputting each field data in the entity class.
Of course, the storage medium provided by the embodiment of the present invention contains computer-executable instructions, and the computer-executable instructions are not limited to the operations of the method described above, and may also perform related operations in the parameter encapsulation method provided by any embodiment of the present invention.
From the above description of the embodiments, it is obvious for those skilled in the art that the present invention can be implemented by software and necessary general hardware, and certainly, can also be implemented by hardware, but the former is a better embodiment in many cases. With this understanding, the technical solutions of the present invention may be embodied in the form of a software product, which can be stored in a computer-readable storage medium, such as a floppy disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a FLASH Memory (FLASH), a hard disk or an optical disk of a computer, and includes instructions for enabling a computer device (which may be a personal computer, a server, or a network device) to execute the methods according to the embodiments of the present invention.
It is to be noted that the foregoing is only illustrative of the preferred embodiments of the present invention and the technical principles employed. It will be understood by those skilled in the art that the present invention is not limited to the particular embodiments described herein, but is capable of various obvious changes, rearrangements and substitutions as will now become apparent to those skilled in the art without departing from the scope of the invention. Therefore, although the present invention has been described in greater detail by the above embodiments, the present invention is not limited to the above embodiments, and may include other equivalent embodiments without departing from the spirit of the present invention, and the scope of the present invention is determined by the scope of the appended claims.
Claims (10)
1. A method for parameter encapsulation, comprising:
when a trigger event of an encapsulation parameter is monitored, acquiring a parameter of participation corresponding to the trigger event, wherein the parameter of participation comprises an application identification parameter and a channel identification parameter to be newly added;
transmitting the parameter of the input parameter to a parameter encapsulation function which is constructed in advance;
obtaining packaged parameters according to an output result of the parameter packaging function, wherein the packaged parameters comprise packaged application parameter information and channel parameter information;
the parameter encapsulation function realizes parameter encapsulation through the following steps:
inquiring target data from a pre-constructed database according to the parameter of the target;
and respectively filling each field data in the target data into a corresponding field of a pre-constructed entity class according to a pre-constructed field mapping relation, and outputting each field data in the entity class.
2. The method of claim 1, wherein the querying target data from a pre-constructed database according to the parameter of interest comprises:
inquiring target application data corresponding to the application identification parameters from a pre-constructed application database;
the filling, according to a pre-constructed field mapping relationship, each field data in the target data into a corresponding field of a pre-constructed entity class, and outputting each field data in the entity class includes:
according to the mapping relation of the application fields which are constructed in advance, filling the field data in the target application data into the corresponding fields of the application entity class which is constructed in advance;
and outputting the data of each field in the application entity class.
3. The method of claim 2, wherein the querying target application data corresponding to the application identification parameter from a pre-built application database comprises:
checking the application identification parameters;
and if the application identification parameter is determined to be a legal parameter according to the verification result, inquiring target application data corresponding to the application identification parameter from a pre-constructed application database.
4. The method of claim 1, wherein the querying target data from a pre-constructed database according to the parameter of interest comprises:
inquiring channel data from a pre-constructed channel database, and splitting an absent channel identification parameter which does not exist in an inquiry result from the channel identification parameter;
inserting the channel data corresponding to the non-existing channel identification parameters into the channel database, and updating the channel database according to the insertion result;
taking each channel data in the channel database as target channel data;
the filling, according to a pre-constructed field mapping relationship, each field data in the target data into a corresponding field of a pre-constructed entity class, and outputting each field data in the entity class includes:
respectively filling each field data in the target channel data into corresponding fields of a pre-constructed channel entity class according to a pre-constructed channel field mapping relation;
and outputting the data of each field in the channel entity class.
5. The method of claim 4, wherein the splitting of the non-existing channel identification parameter from the channel identification parameter that is not present in the query result comprises:
filtering the non-existing channel identification parameters which do not exist in the query result from the channel identification parameters based on a preset filtering function;
and filtering existing channel identification parameters which do not exist in the non-existing channel identification parameters from the channel identification parameters based on the preset filtering function.
6. The method of any of claims 2-5, wherein each piece of application data in the application database includes application identification information, an application name, a package name, and a platform type; and/or the presence of a gas in the gas,
each piece of channel data in the channel database includes channel identification information, the application identification information, a channel name, and the platform type.
7. The method of claim 1, wherein the obtaining the packed parameters according to the output result of the parameter packing function comprises:
obtaining filled parameters according to the output result of the parameter encapsulation function;
and encapsulating the filled parameters in a pre-constructed parameter encapsulation object, and obtaining encapsulated parameters based on the parameter encapsulation object.
8. A parametric package device, comprising:
the acquisition module is used for acquiring the parameter of the participating channel corresponding to the trigger event when the trigger event of the package parameter is monitored, wherein the parameter of the participating channel comprises an application identification parameter and a channel identification parameter to be newly added;
the transfer module is used for transferring the parameter to a pre-constructed parameter encapsulation function so that the parameter encapsulation function queries target data from a pre-constructed database according to the parameter, respectively fills each field data in the target data into a corresponding field of a pre-constructed entity class according to a pre-constructed field mapping relation, and outputs each field data in the entity class;
and the encapsulation module is used for obtaining encapsulated parameters according to the output result of the parameter encapsulation function, wherein the encapsulated parameters comprise encapsulated application parameter information and channel parameter information.
9. An apparatus, characterized in that the apparatus comprises:
one or more processors;
a memory for storing one or more programs;
when executed by the one or more processors, cause the one or more processors to implement the parameter encapsulation method of any one of claims 1-7.
10. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the parameter encapsulation method according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010300090.1A CN113535140B (en) | 2020-04-16 | 2020-04-16 | Parameter packaging method, device, equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010300090.1A CN113535140B (en) | 2020-04-16 | 2020-04-16 | Parameter packaging method, device, equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113535140A true CN113535140A (en) | 2021-10-22 |
| CN113535140B CN113535140B (en) | 2022-11-11 |
Family
ID=78088443
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010300090.1A Active CN113535140B (en) | 2020-04-16 | 2020-04-16 | Parameter packaging method, device, equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113535140B (en) |
Citations (15)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6460057B1 (en) * | 1997-05-06 | 2002-10-01 | International Business Machines Corporation | Data object management system |
| CN102036227A (en) * | 2009-09-27 | 2011-04-27 | 中国移动通信集团公司 | Method, system and device for acquiring user identifier of data service |
| US7950017B1 (en) * | 1999-04-23 | 2011-05-24 | Avaya Inc. | Apparatus and method for forwarding messages between two applications |
| CN104267988A (en) * | 2014-09-26 | 2015-01-07 | 北京飞流九天科技有限公司 | System and method for packing mobile applications |
| CN104317964A (en) * | 2014-11-14 | 2015-01-28 | 中国建设银行股份有限公司 | Object-relational mapping method and system based on iBatis |
| CN104503745A (en) * | 2014-12-09 | 2015-04-08 | 北京奇虎科技有限公司 | Method and device for generating application channel package |
| CN104899225A (en) * | 2014-03-07 | 2015-09-09 | 北京四达时代软件技术股份有限公司 | Object relational mapping method and device as well as processor |
| US20150310517A1 (en) * | 2014-04-29 | 2015-10-29 | Nhn Entertainment Corporation | Method and system for tracking marketing channel of application |
| CN107592202A (en) * | 2017-09-20 | 2018-01-16 | 广州阿里巴巴文学信息技术有限公司 | Application signature method, apparatus, system, computing device and storage medium |
| CN107797808A (en) * | 2016-08-31 | 2018-03-13 | 腾讯科技（深圳）有限公司 | Application installation package processing method and processing device |
| CN109116828A (en) * | 2017-06-22 | 2019-01-01 | 中兴通讯股份有限公司 | Model code configuration method and device in a kind of controller |
| CN109271403A (en) * | 2018-09-28 | 2019-01-25 | 北京京东金融科技控股有限公司 | A kind of operating method of data query, device, medium and electronic equipment |
| CN109739872A (en) * | 2018-12-27 | 2019-05-10 | 苏州思必驰信息科技有限公司 | A kind of implementation method, system and the operating method of SQL statement processing |
| CN110363572A (en) * | 2019-06-25 | 2019-10-22 | 上海淇馥信息技术有限公司 | A kind of program channel promotion method, apparatus that closing ecological terminal, electronic equipment |
| CN111008254A (en) * | 2019-12-03 | 2020-04-14 | 北京锐安科技有限公司 | Object creating method and device, computer equipment and storage medium |
-
2020
- 2020-04-16 CN CN202010300090.1A patent/CN113535140B/en active Active
Patent Citations (15)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6460057B1 (en) * | 1997-05-06 | 2002-10-01 | International Business Machines Corporation | Data object management system |
| US7950017B1 (en) * | 1999-04-23 | 2011-05-24 | Avaya Inc. | Apparatus and method for forwarding messages between two applications |
| CN102036227A (en) * | 2009-09-27 | 2011-04-27 | 中国移动通信集团公司 | Method, system and device for acquiring user identifier of data service |
| CN104899225A (en) * | 2014-03-07 | 2015-09-09 | 北京四达时代软件技术股份有限公司 | Object relational mapping method and device as well as processor |
| US20150310517A1 (en) * | 2014-04-29 | 2015-10-29 | Nhn Entertainment Corporation | Method and system for tracking marketing channel of application |
| CN104267988A (en) * | 2014-09-26 | 2015-01-07 | 北京飞流九天科技有限公司 | System and method for packing mobile applications |
| CN104317964A (en) * | 2014-11-14 | 2015-01-28 | 中国建设银行股份有限公司 | Object-relational mapping method and system based on iBatis |
| CN104503745A (en) * | 2014-12-09 | 2015-04-08 | 北京奇虎科技有限公司 | Method and device for generating application channel package |
| CN107797808A (en) * | 2016-08-31 | 2018-03-13 | 腾讯科技（深圳）有限公司 | Application installation package processing method and processing device |
| CN109116828A (en) * | 2017-06-22 | 2019-01-01 | 中兴通讯股份有限公司 | Model code configuration method and device in a kind of controller |
| CN107592202A (en) * | 2017-09-20 | 2018-01-16 | 广州阿里巴巴文学信息技术有限公司 | Application signature method, apparatus, system, computing device and storage medium |
| CN109271403A (en) * | 2018-09-28 | 2019-01-25 | 北京京东金融科技控股有限公司 | A kind of operating method of data query, device, medium and electronic equipment |
| CN109739872A (en) * | 2018-12-27 | 2019-05-10 | 苏州思必驰信息科技有限公司 | A kind of implementation method, system and the operating method of SQL statement processing |
| CN110363572A (en) * | 2019-06-25 | 2019-10-22 | 上海淇馥信息技术有限公司 | A kind of program channel promotion method, apparatus that closing ecological terminal, electronic equipment |
| CN111008254A (en) * | 2019-12-03 | 2020-04-14 | 北京锐安科技有限公司 | Object creating method and device, computer equipment and storage medium |
Non-Patent Citations (3)
| Title |
|---|
| 余俊新等: "J2EE中对象关系映射的研究与实现", 《计算机技术与发展》 * |
| 李宁: "《Android深度探索(卷2)：系统应用源代码分析与ROM定制》", 31 January 2015, 人民邮电出版社 * |
| 黄强等: "一个基于类型元数据的轻量级ORM框架设计", 《计算机工程》 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113535140B (en) | 2022-11-11 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109345388B (en) | Block chain intelligent contract verification method and device and storage medium | |
| CA3091405A1 (en) | Model training system and method, and storage medium | |
| CN107277086B (en) | Service processing system, service processing method and service updating method | |
| US10924281B2 (en) | Method and apparatus for inter-blockchain transmission of authenticable message | |
| CN105187258B (en) | A kind of configurable Trap warning analysis processing methods | |
| CN111414407A (en) | Data query method and device of database, computer equipment and storage medium | |
| CN114500690B (en) | Interface data processing method and device, electronic equipment and storage medium | |
| CN108572986B (en) | Data updating method and node equipment | |
| CN111399756A (en) | Data storage method, data downloading method and device | |
| CN109067732A (en) | Internet of things equipment and data insertion system, method and computer readable storage medium | |
| CN104320312A (en) | Network application safety test tool and fuzz test case generation method and system | |
| CN109670081A (en) | The method and device of service request processing | |
| CN111651468A (en) | Data updating method and device based on SQL analysis, electronic equipment and storage medium | |
| CN109343983B (en) | Information interaction method, device, equipment and storage medium between function modules | |
| CN113495765A (en) | Business data filling method and device, storage medium and electronic device | |
| CN113535140B (en) | Parameter packaging method, device, equipment and storage medium | |
| CN109815202B (en) | Log editing method and related device | |
| CN112114871B (en) | Code sharing method, device, server, terminal and medium | |
| CN104378393A (en) | Resource sharing method and corresponding device | |
| CN114218256B (en) | Access statement processing method, device, equipment and storage medium | |
| CN113608746B (en) | Code conversion processing method, device, computer equipment and storage medium | |
| CN111399864B (en) | Android system application program foundation package generation method and generation device | |
| CN113704120A (en) | Data transmission method, device, equipment and storage medium | |
| CN109543024A (en) | A kind of text handling method and device | |
| CN112800194A (en) | Interface change identification 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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| EE01 | Entry into force of recordation of patent licensing contract | ||
| EE01 | Entry into force of recordation of patent licensing contract |
Application publication date: 20211022 Assignee: Yidu Lehuo Network Technology Co.,Ltd. Assignor: WUHAN DOUYU NETWORK TECHNOLOGY Co.,Ltd. Contract record no.: X2023980041384 Denomination of invention: A parameter encapsulation method, device, device, and storage medium Granted publication date: 20221111 License type: Common License Record date: 20230908 |