CN107453946B - Field management method and device and electronic equipment - Google Patents
Field management method and device and electronic equipment Download PDFInfo
- Publication number
- CN107453946B CN107453946B CN201710595906.6A CN201710595906A CN107453946B CN 107453946 B CN107453946 B CN 107453946B CN 201710595906 A CN201710595906 A CN 201710595906A CN 107453946 B CN107453946 B CN 107453946B
- Authority
- CN
- China
- Prior art keywords
- field name
- field
- service user
- program
- service
- 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.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/12—Network monitoring probes
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/16—Threshold monitoring
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/535—Tracking the activity of the user
Abstract
The embodiment of the specification provides a field management method, a field management device and electronic equipment, wherein a point of a collection program is buried for a service user who obtains a service; thereby collecting field names used by the service user; when the target field name needs to be discarded, the target service user who uses the target field name is quickly and accurately determined according to the collected field names.
Description
Technical Field
The embodiment of the specification relates to the technical field of internet, in particular to a field management method and device and electronic equipment.
Background
In a business system, there is typically a service provider as well as a service consumer. The service provider typically provides services such as queries to the outside in the form of an interface. The service user can use the corresponding service through the interface; with the migration of traffic (e.g., service upgrades), it is possible that fields of some interfaces are no longer used, i.e., need to be taken offline, commonly referred to as field obsolescence. However, before the characters are discarded, all the service users using the field need to be found so as to inform the service users that the field needs to be discarded. Otherwise, the server may make errors that cause various problems (e.g., query errors, system crashes) if obsolete fields are still used. The service user seeking to use the obsolete field may generally be based on a static code scan, for example, when a field needs to be obsolete, first the codes of all service users are downloaded, and then based on these codes it is looked up whether any service user has used this field.
There is a need to provide a more efficient scheme for finding service consumers that use obsolete fields.
Disclosure of Invention
The field management method, the field management device and the electronic device provided by the embodiments of the present specification are used to provide a more efficient scheme for finding a service user using a discarded field.
According to a field management method provided by an embodiment of the present specification, the method includes:
the service provider carries out the embedded point of the acquisition program to the service user; the collecting program is used for collecting the field names used by the service users;
the service user records the used field name according to the collection program of the embedded point;
the service user uploads use information to the service provider, wherein the use information is associated with the field name recorded by the acquisition program;
the service provider receives the use information uploaded by the service user;
and the service provider determines a target service user from the use information according to the target field name to be discarded.
The field management method provided by the embodiment of the specification is applied to a service provider and comprises the following steps:
carrying out embedded point acquisition on a program to a service user; the collecting program is used for collecting the field names used by the service users;
receiving the use information uploaded by the service user; the use information is associated with the field name used by the service user recorded by the acquisition program;
and determining a target service user from the use information according to the target field name to be discarded.
According to the field management method provided by the embodiment of the specification, the field management method is applied to a service user side, and the method comprises the following steps:
recording the used field names according to the acquisition program of the buried points;
uploading the use information; the usage information is associated with a field name of the acquisition program record.
According to a field management device provided by an embodiment of the present specification, the field management device is applied to a service provider, and the field management device includes:
the embedded point unit is used for acquiring embedded points of programs from a service user; the collecting program is used for collecting the field names used by the service users;
a receiving unit that receives the usage information uploaded by the service user; the usage information is associated with a field name used by the service user;
and the determining unit is used for determining the target service user from the use information according to the target field name to be discarded.
According to a field management device provided by an embodiment of the present specification, the field management device is applied to a service user, and the field management device includes:
the collecting unit records the used field names according to the acquisition program of the buried points;
an upload unit that uploads the usage information; the usage information is associated with a field name of the acquisition program record.
According to this specification embodiment, provide an electronic equipment, include:
a processor;
a memory for storing processor-executable instructions;
wherein the processor is configured to:
carrying out embedded point acquisition on a program to a service user; the collecting program is used for collecting the field names used by the service users;
receiving the use information uploaded by the service user; the use information is associated with the field name used by the service user recorded by the acquisition program;
and determining a target service user from the use information according to the target field name to be discarded.
According to this specification embodiment, provide an electronic equipment, include:
a processor;
a memory for storing processor-executable instructions;
wherein the processor is configured to:
recording the used field names according to the acquisition program of the buried points;
uploading the use information; the usage information is associated with a field name of the acquisition program record.
In the embodiment of the present specification, the service provider performs embedding of a collection program for collecting field names used by a service user who acquires a service, to the service user. Thus, the service provider can determine the field names that have been used historically by the service consumer for each landfill. When a target field needs to be discarded, the service user using the target field can be quickly and accurately determined by inquiring the field names used by the service users in history.
Drawings
FIG. 1 is a diagram of a system architecture implementing field management provided by an embodiment of the present description;
FIG. 2 is a flow chart of a field management method provided by an embodiment of the present specification;
FIG. 3 is a flowchart of a field management method provided by an embodiment of the present specification;
FIG. 4 is a flowchart of a field management method provided by an embodiment of the present specification;
fig. 5 is a block diagram of a field management apparatus according to an embodiment of the present disclosure;
fig. 6 is a block diagram of a field management apparatus according to an embodiment of the present disclosure.
Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present specification. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the specification, as detailed in the appended claims.
The terminology used in the description herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the description. As used in this specification and the appended claims, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items.
It should be understood that although the terms first, second, third, etc. may be used herein to describe various information, these information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, the first information may also be referred to as second information, and similarly, the second information may also be referred to as first information, without departing from the scope of the present specification. The word "if" as used herein may be interpreted as "at … …" or "when … …" or "in response to a determination", depending on the context.
In this specification, the field (field) may be expressed as a variable associated with an interface. For example, the query interface may have associated therewith several specific fields. In general, a "column" of a database table may be referred to as a "field," each field containing information for a particular topic. For example, in a contact list, "name" and "contact" are attributes common to all rows in the data list, and these columns may be referred to as the "name" field and the "contact" field. Taking the query service as an example, assuming that a name needs to be queried, querying the name can be implemented by calling the "name" field associated with the query interface.
As previously mentioned, a service user seeking to use a discard field may generally be based on a static code scan, for example, when a field needs to be discarded, first downloading the codes of all service users, and then based on these codes, looking up whether any service user has used this field.
However, the method based on static code scanning has the following problems:
the code for all service users in the system needs to be maintained (updated, downloaded, etc.).
Then, the service user using the obsolete fields is also searched from all the codes, so that the searching efficiency is low. Furthermore, even if a service user using a discarded field is scanned, it may not be sufficient. For example, some unused codes exist but actually the traffic link cannot be covered, and if such codes exist, static code scanning cannot be found if a call discard field exists, thus resulting in omission.
Fig. 1 is a system architecture diagram for implementing field management provided in an embodiment of the present specification. In this embodiment, the system may be a distributed service system including a plurality of service consumers 11 and service providers 12.
The service provider 12 may provide services through exposed interfaces, typically one interface for each service, and may have associated fields. For example, the query interface of the address book is associated with a "name" field, a "contact phone" field, and the like.
The service user 11 may call the field associated with the interface to obtain the corresponding service.
The service consumer 11 and the service provider 12 may be different subsystems located in the same system; for example, the service user 11 is a service server that specifically executes a service, and the service provider 12 may be a central server that provides support for each service user.
Further, the service consumer 11 is an external system with respect to the service provider 12; for example, the service provider 12 is a cloud server that provides services to the outside, and each service consumer 11 is a client that accesses the cloud platform to obtain the services.
In this embodiment, the service provider 12 performs embedding of a collection program for collecting field names used by the service consumer 11 to acquire services to the service consumer 11. Thus, the service provider 12 can determine the field names that have been used historically by the service consumers 11 for each landfill. When a target field needs to be discarded, by referring to the field names that have been used by the service users 11, the service user using the target field can be quickly and accurately determined.
An embodiment of a method for implementing field management according to the present disclosure is described below with reference to an example shown in fig. 2, where the method may include the following steps:
step 210: the service provider carries out the embedded point of the acquisition program to the service user; the collecting program is used for collecting the field names used by the service users.
In this embodiment, the buried point is a commonly used data acquisition method. Typically, a lander (i.e., a service provider) may implant a harvesting procedure with a landed party (i.e., a service consumer). The collection procedure may typically be a piece of code that automatically collects relevant data (e.g., used fields) of the site party.
It should be noted that the relevant data may be set by the buried point side. It will be appreciated that the collection procedure can be preset to collect which data. In this embodiment, the collection program can automatically collect the field names used by the service users.
Step 220: and the service user records the used field names according to the collection program of the buried points.
From a code execution perspective, using a field is embodied as calling the field, typically a Get method. For example, assuming a Field is Field, when the collector monitors execution of getField (), the service user uses the Field to trigger collection of the Field. Generally, the collection program may record the collected field name in a non-persistent device such as a memory, or may record the collected field name in a persistent device such as a hard disk.
Step 230: and the service user uploads use information to the service provider, wherein the use information is associated with the field name recorded by the acquisition program.
In a specific embodiment, the uploading, by the service consumer, the usage information to the service provider may specifically include:
and the service user uploads the use information associated with the field name recorded by the acquisition program to the service provider at regular time.
In general, the collection program may output a usage information (e.g., log) collected to the field name at regular time (preset time duration, such as 1 hour, 1 day, which may be configured by the service provider or the service user). The service consumer then uploads the usage information to the service provider.
In a specific embodiment, the uploading, by the service consumer, the usage information to the service provider may specifically include:
and the service user uploads the use information associated with the field name recorded by the acquisition program to the service provider in a log mode.
Step 240: and the service provider receives the use information uploaded by the service user.
The service provider aggregates the used fields of the service users by burying points for the service users acquiring the service.
Step 250: and the service provider determines a target service user from the use information according to the target field name to be discarded.
When a field needs to be discarded, the field name may be set as the target field name. Then, the usage information of all service users is traversed to find the service user who has used the target field name.
Specifically, the step 250 may include:
the service provider acquires a target field name to be discarded;
the service provider inquiring whether there is usage information with the target field name;
when the service provider inquires that the use information with the target field name exists, the service provider determines the service user of the use information as the target service user.
For example, the usage information of the service user 1 associates a field name a, a field name B, and a field name C;
the field name a, the field name C and the field name D are associated with the use information of the service user 2;
the field name B and the field name E are associated with the use information of the service user 3;
assuming that the target field name to be discarded is C,
then, the service provider needs to sequentially determine whether the target field name C exists in the usage information:
for the service user 1, the field name A is different from the target field name C, and the next field name is continuously judged;
the field name B is different from the target field name C, and the next field name is continuously judged;
the field name C is the same as the target field name C, and the service user 1 can be determined to be the target service user;
for the service user 2, the field name A is different from the target field name C, and the next field name is continuously judged;
the field name C is the same as the target field name C, and the service user 2 can be determined to be the target service user;
for the service user 3, the field name B is different from the target field name C, and the next field name is continuously judged;
the field name E is different from the target field name C, and the next field name is not available, and the process is finished;
thus, the service user 1, 2 can be finally determined as the target service user; and then the target service user can be informed of the need of service upgrade, and the target field is replaced.
In this embodiment, the service provider performs a collection procedure for collecting field names used by the service consumers to obtain the service, by performing a collection procedure on the embedded points of the field names. Thus, the service provider can determine the field names that have been used historically by the service consumer for each landfill. When a target field needs to be discarded, the service user using the target field can be quickly and accurately determined by inquiring the field names used by the service users in history.
In an actual business scenario, a service provider may need to manage and control field usage of a service user in addition to searching for a service user using discarded fields. For example, the query service provided by a certain service provider is charged, and assuming that 10 query times can be obtained after payment, the service provider needs to manage and control the service user and determine whether the query times exceed the limit.
On the basis of the embodiment shown in fig. 2, in another embodiment, the buried point further includes a statistical program and a management and control program;
in this embodiment, the statistical program is configured to count the number of times of using the field name used by the service consumer.
For the service user, the number of times of using the used field name may be counted according to a statistical procedure of the buried point. For example, every time any field name is used 1 time, the number of times the field name is used is increased by 1.
For example, assuming a Field is Field, after the collector monitors the execution of getField (), the statistical program may trigger a statistic, and add 1 to the number of statistics of the Field. The statistical program may also record the statistical number of field names to a non-persistent device or a persistent device, in a similar manner as the acquisition program records.
In this embodiment, the management and control program is configured to manage and control the field name used by the service user.
For a service user, the field name used may be managed according to a management program of the buried point.
In this embodiment, the regulation may be performed based on rules, and the regulated rules may be configured by the service provider:
for example, the managing the field name used by the service user may include:
when the number of uses of a field name reaches a threshold value, the field name is prohibited from being used.
The threshold may be an empirical value set manually, and the thresholds for different field names may be different.
Or a threshold (such as an upper usage limit) determined according to the payment condition of the service user.
It will be appreciated that the service provider may be configured with the threshold in a landed administration program.
As shown in table 1 below:
TABLE 1
| Charging/payment | Upper limit of use/time |
| 100 | 10 |
| 200 | 20 |
| 300 | 30 |
| …… | …… |
The table is only an example, and in practical applications, the corresponding relationship between the payment and the usage upper limit may be more complicated, such as multiple payment and additional delivery of the usage upper limit, month and year packages, and the like.
Generally, if the service provider confirms the payment of the service user, the service provider statistical program may issue the zero clearing statistical times and the instruction of updating the threshold. The updated threshold is the upper limit of the service provider corresponding to the payment amount.
For example, the threshold value for the field a configured in the control configuration is 10 times.
When the number of times of use of the field a (counted by the statistical program) reaches 10 times, it indicates that the number of times of calling the field a by the service user has reached the upper limit, and the field a cannot be called by prohibiting the service user from using the field name a.
In addition, the managing and controlling the field name used by the service user may include:
in the case where the field name does not belong to the access-permitted field name, the field is prohibited from being used.
Typically, service providers do not open all services, and therefore, some fields are not available to the service consumer.
It can be understood that, when the service provider is in a site management program, a configuration file may be configured in the management program;
in one implementation, the configuration file records whether all field names are allowed to be used.
Thus, after the collecting program monitors that a service user uses a field name, the management and control program can query the configuration file to determine whether the field name is allowed to be used;
if the field name is allowed to be used, the service user can call the field normally so as to obtain the corresponding service;
if the field name is not allowed to be used, the service user can not call the field, and can not obtain the corresponding service.
In another implementation, the configuration file only records the fields that are allowed to be used.
Similarly, after the collecting program monitors that a field name is used by a service user, the management and control program may query whether the field name exists in the configuration file;
if the field name exists in the configuration file, which indicates that the field name is allowed to be used, the service user can normally call the field, so as to obtain the corresponding service;
if the field name does not exist in the configuration file, which indicates that the field name is not allowed to be used, the service user cannot call the field, and thus cannot acquire the corresponding service.
In yet another implementation, the configuration file only records fields that are not allowed to be used.
Similarly, after the collecting program monitors that a field name is used by a service user, the management and control program may query whether the field name exists in the configuration file;
if the field name does not exist in the configuration file, the field name is allowed to be used, and then the service user can normally call the field so as to obtain corresponding service;
if the field name exists in the configuration file, which indicates that the field name is not allowed to be used, the service user cannot call the field, and thus cannot acquire the corresponding service.
Similar to the previous embodiment, the service provider may develop the field name after the service consumer pays for the particular field name.
The charging condition of each field name can be set according to the service.
For example, suppose that a service user needs to use a certain service, but the field name a corresponding to the service is not allowed to be used; when the service provider is paid for the field name a, if the service provider confirms that the service user successfully pays for the field name a, a new configuration file can be issued to the service user for updating the original configuration file in the service user management and control program;
corresponding to the above configuration files:
if the configuration file records whether all the field names are allowed to be used, the field name A in the new configuration file is changed from the non-allowed use to the allowed use;
if the configuration file only records the fields allowed to be used, the field name A is newly added in the new configuration file;
if the configuration file only records fields that are not allowed to be used, then the field name a has been deleted in this new configuration file.
It should be noted that the collecting program, the statistical program and the management and control program may be integrated into one program.
An embodiment of the method for the service provider to perform the present specification is described below with reference to fig. 3, and the embodiment may be implemented with respect to fig. 2:
step 310: carrying out embedded point acquisition on a program to a service user; the collecting program is used for collecting the field names used by the service users.
Step 320: receiving the use information uploaded by the service user; the use information is associated with the field name used by the service user recorded by the acquisition program;
step 330: and determining a target service user from the use information according to the target field name to be discarded.
The specific steps in this embodiment may refer to the content of the description in fig. 2, which is not described herein again.
In an embodiment, the step 330 may specifically include:
acquiring a target field name to be discarded;
inquiring whether the use information with the target field name exists;
if it is found that the usage information having the target field name exists, the service user using the usage information is determined as the target service user.
In one embodiment, the buried point further comprises a statistical program and a management and control program;
the statistical program is used for counting the use times of the field names used by the service user;
the management and control program is used for managing and controlling the field names used by the service users.
In an embodiment, the managing and controlling the field name used by the service user specifically includes:
prohibiting use of the field name in a case where the number of uses of the field name reaches a threshold;
and/or the presence of a gas in the gas,
in the case where the field name does not belong to the access-permitted field name, the field name is prohibited from being used.
An embodiment of the method for executing the subject by the service user in the present specification is described below with reference to fig. 4, and the embodiment may be implemented with reference to fig. 2:
step 410: and recording the used field names according to the collection program of the buried points.
Step 420: uploading the use information; the usage information is associated with a field name of the acquisition program record.
In one embodiment, the uploading the usage information specifically includes:
and uploading the use information of the field names related to the acquisition program records at regular time.
In one embodiment, the uploading the usage information specifically includes:
and uploading the use information of the field name associated with the acquisition program record in a log mode.
In one embodiment, the method further comprises:
counting the use times of the used field names according to a statistical program of the buried points;
and managing and controlling the used field names according to the management and control program of the embedded points.
In an embodiment, the counting, according to the statistical procedure of the buried points, the number of times of using the used field name includes:
every time any field name is used 1 time, the number of times the field name is used is increased by 1.
In one embodiment, the managing and controlling the used field name according to the management and control program of the embedded point specifically includes:
prohibiting use of the field name in a case where the number of uses of the field name reaches a threshold;
and/or the presence of a gas in the gas,
in the case where the field name does not belong to the access-permitted field name, the field name is prohibited from being used.
Corresponding to the field management method embodiment described in the foregoing fig. 3, the present specification also provides an embodiment of a field management apparatus. The device embodiments may be implemented by software, or by hardware, or by a combination of hardware and software. The software implementation is taken as an example, and is formed by reading corresponding computer program instructions in the nonvolatile memory into the memory for operation through the processor of the device where the software implementation is located as a logical means. In terms of hardware, a hardware structure of the apparatus in which the field management device in this specification is located may include a processor, a network interface, a memory, and a nonvolatile memory, and the apparatus in the embodiment generally manages an actual function according to the field and may also include other hardware, which is not described in detail herein.
Referring to fig. 5, a block diagram of a field management apparatus provided for an embodiment of the present specification, applied to a service provider, includes:
the embedded point unit is used for acquiring embedded points of programs from a service user; the collecting program is used for collecting the field names used by the service users;
a receiving unit that receives the usage information uploaded by the service user; the usage information is associated with a field name used by the service user;
and the determining unit is used for determining the target service user from the use information according to the target field name to be discarded.
In an alternative embodiment:
the determining unit specifically includes:
the acquisition subunit acquires a target field name to be discarded;
a query subunit configured to query whether or not there is usage information having the target field name;
and a determining subunit, configured to determine, when it is found that the usage information having the target field name exists, a service user using the usage information as a target service user.
In an alternative embodiment:
the embedded point also comprises a statistical program and a control program;
the statistical program is used for counting the use times of the field names used by the service user;
the management and control program is used for managing and controlling the field names used by the service users.
In an alternative embodiment:
the management and control program is specifically configured to:
prohibiting use of the field name in a case where the number of uses of the field name reaches a threshold;
and/or the presence of a gas in the gas,
in the case where the field name does not belong to the access-permitted field name, the field name is prohibited from being used.
Corresponding to the field management method embodiment described in the foregoing fig. 4, the present specification also provides an embodiment of a field management apparatus. The device embodiments may be implemented by software, or by hardware, or by a combination of hardware and software. The software implementation is taken as an example, and is formed by reading corresponding computer program instructions in the nonvolatile memory into the memory for operation through the processor of the device where the software implementation is located as a logical means. In terms of hardware, a hardware structure of the apparatus in which the field management device in this specification is located may include a processor, a network interface, a memory, and a nonvolatile memory, and the apparatus in the embodiment generally manages an actual function according to the field and may also include other hardware, which is not described in detail herein.
Referring to fig. 6, a block diagram of a field management apparatus provided for an embodiment of the present specification, applied to a service user, includes:
the collecting unit records the used field names according to the acquisition program of the buried points;
an upload unit that uploads the usage information; the usage information is associated with a field name of the acquisition program record.
In an alternative embodiment:
the uploading unit specifically comprises:
and uploading the use information of the field names related to the acquisition program records at regular time.
In an alternative embodiment:
the uploading unit specifically comprises:
and uploading the use information of the field name associated with the acquisition program record in a log mode.
In an alternative embodiment:
the device further comprises:
a statistic unit for counting the number of times of use of the used field name according to a statistic program of the buried point;
and the control unit controls the used field names according to the control program of the embedded points.
In an alternative embodiment:
the statistical unit specifically comprises:
every time any field name is used 1 time, the number of times the field name is used is increased by 1.
In an alternative embodiment:
the management and control unit specifically comprises:
a first management and control subunit which prohibits the use of the field name when the number of uses of the field name reaches a threshold value;
and/or the presence of a gas in the gas,
and a second administration subunit which prohibits use of the field name in the case where the field name does not belong to the access permitted field name.
The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. A typical implementation device is a computer, which may take the form of a personal computer, laptop computer, cellular telephone, camera phone, smart phone, personal digital assistant, media player, navigation device, email messaging device, game console, tablet computer, wearable device, or a combination of any of these devices.
The implementation process of the functions and actions of each unit in the above device is specifically described in the implementation process of the corresponding step in the above method, and is not described herein again.
For the device embodiments, since they substantially correspond to the method embodiments, reference may be made to the partial description of the method embodiments for relevant points. The above-described embodiments of the apparatus are merely illustrative, and the units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the solution in the specification. One of ordinary skill in the art can understand and implement it without inventive effort.
Fig. 5 above describes the internal functional modules and the structural schematic of the field management apparatus, and the substantial execution subject may be an electronic device, including:
a processor;
a memory for storing processor-executable instructions;
wherein the processor is configured to:
carrying out embedded point acquisition on a program to a service user; the collecting program is used for collecting the field names used by the service users;
receiving the use information uploaded by the service user; the use information is associated with the field name used by the service user recorded by the acquisition program;
and determining a target service user from the use information according to the target field name to be discarded.
Preferably, the determining a target service user from the usage information according to the target field name to be discarded specifically includes:
acquiring a target field name to be discarded;
inquiring whether the use information with the target field name exists;
if it is found that the usage information having the target field name exists, the service user using the usage information is determined as the target service user.
Preferably, the buried point further comprises a statistical program and a management and control program;
the statistical program is used for counting the use times of the field names used by the service user;
the management and control program is used for managing and controlling the field names used by the service users.
Preferably, the managing and controlling the field name used by the service user specifically includes:
prohibiting use of the field name in a case where the number of uses of the field name reaches a threshold;
and/or the presence of a gas in the gas,
in the case where the field name does not belong to the access-permitted field name, the field name is prohibited from being used.
Fig. 6 above describes the internal functional modules and the structural schematic of the field management apparatus, and the substantial execution subject may be an electronic device, including:
a processor;
a memory for storing processor-executable instructions;
wherein the processor is configured to:
recording the used field names according to the acquisition program of the buried points;
uploading the use information; the usage information is associated with a field name of the acquisition program record.
Preferably, the uploading of the usage information specifically includes:
and uploading the use information of the field names related to the acquisition program records at regular time.
Preferably, the uploading of the usage information specifically includes:
and uploading the use information of the field name associated with the acquisition program record in a log mode.
Preferably, the method further comprises:
counting the use times of the used field names according to a statistical program of the buried points;
and managing and controlling the used field names according to the management and control program of the embedded points.
Preferably, the counting the number of times of using the used field name according to the statistical procedure of the buried point specifically includes:
every time any field name is used 1 time, the number of times the field name is used is increased by 1.
Preferably, the managing and controlling program according to the embedded point manages and controls the used field name, and specifically includes:
prohibiting use of the field name in a case where the number of uses of the field name reaches a threshold;
and/or the presence of a gas in the gas,
in the case where the field name does not belong to the access-permitted field name, the field name is prohibited from being used.
In the above embodiments of the electronic device, it should be understood that the Processor may be a Central Processing Unit (CPU), other general-purpose processors, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), etc. The general-purpose processor may be a microprocessor, or the processor may be any conventional processor, and the aforementioned memory may be a read-only memory (ROM), a Random Access Memory (RAM), a flash memory, a hard disk, or a solid state disk. The steps of a method disclosed in connection with the embodiments of the present invention may be directly implemented by a hardware processor, or may be implemented by a combination of hardware and software modules in the processor.
The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the embodiment of the electronic device, since it is substantially similar to the embodiment of the method, the description is simple, and for the relevant points, reference may be made to part of the description of the embodiment of the method.
Other embodiments of the present disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This specification is intended to cover any variations, uses, or adaptations of the specification following, in general, the principles of the specification and including such departures from the present disclosure as come within known or customary practice within the art to which the specification pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the specification being indicated by the following claims.
It will be understood that the present description is not limited to the precise arrangements described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present description is limited only by the appended claims.
Claims (23)
1. A method of field management, the method comprising:
the service provider carries out the embedded point of the acquisition program to the service user; the collecting program is used for collecting the field names used by the service users;
the service user records the used field name according to the collection program of the embedded point;
the service user uploads use information to the service provider, wherein the use information is associated with the field name recorded by the acquisition program;
the service provider receives the use information uploaded by the service user;
and the service provider determines a target service user from the use information according to the target field name to be discarded.
2. A field management method applied to a service provider comprises the following steps:
carrying out embedded point acquisition on a program to a service user; the collecting program is used for collecting the field names used by the service users;
receiving the use information uploaded by the service user; the use information is associated with the field name used by the service user recorded by the acquisition program;
and determining a target service user from the use information according to the target field name to be discarded.
3. The method according to claim 2, wherein the determining the target service user from the usage information according to the target field name to be discarded specifically comprises:
acquiring a target field name to be discarded;
inquiring whether the use information with the target field name exists;
if it is found that the usage information having the target field name exists, the service user using the usage information is determined as the target service user.
4. The method of claim 2, the site further comprising a statistical program and a management program;
the statistical program is used for counting the use times of the field names used by the service user;
the management and control program is used for managing and controlling the field names used by the service users.
5. The method according to claim 4, wherein the managing a field name used by the service consumer specifically includes:
prohibiting use of the field name in a case where the number of uses of the field name reaches a threshold;
and/or the presence of a gas in the gas,
in the case where the field name does not belong to the access-permitted field name, the field name is prohibited from being used.
6. A field management method applied to a service user, the method comprising:
recording the used field name according to the acquisition program of the service provider buried point;
uploading usage information to the service provider; the use information is associated with the field name recorded by the acquisition program; and the service provider inquires whether the use information with the target field name exists or not according to the target field name to be discarded, and determines the service user of the use information as the target service user when the use information with the target field name exists.
7. The method according to claim 6, wherein the uploading of the usage information specifically comprises:
and uploading the use information of the field names related to the acquisition program records at regular time.
8. The method according to claim 6, wherein the uploading of the usage information specifically comprises:
and uploading the use information of the field name associated with the acquisition program record in a log mode.
9. The method of claim 6, further comprising:
counting the use times of the used field names according to a statistical program of the buried points;
and managing and controlling the used field names according to the management and control program of the embedded points.
10. The method according to claim 9, wherein the counting the number of times of using the used field name according to the statistical procedure of the buried point comprises:
every time any field name is used 1 time, the number of times the field name is used is increased by 1.
11. The method according to claim 9, wherein the controlling the field names according to the control program of the embedded point specifically includes:
prohibiting use of the field name in a case where the number of uses of the field name reaches a threshold;
and/or the presence of a gas in the gas,
in the case where the field name does not belong to the access-permitted field name, the field name is prohibited from being used.
12. A field management apparatus applied to a service provider, the apparatus comprising:
the embedded point unit is used for acquiring embedded points of programs from a service user; the collecting program is used for collecting the field names used by the service users;
a receiving unit that receives the usage information uploaded by the service user; the usage information is associated with a field name used by the service user;
and the determining unit is used for determining the target service user from the use information according to the target field name to be discarded.
13. The apparatus according to claim 12, wherein the determining unit specifically includes:
the acquisition subunit acquires a target field name to be discarded;
a query subunit configured to query whether or not there is usage information having the target field name;
and a determining subunit, configured to determine, when it is found that the usage information having the target field name exists, a service user using the usage information as a target service user.
14. The apparatus of claim 12, the landfill further comprising a statistical program and a management program;
the statistical program is used for counting the use times of the field names used by the service user;
the management and control program is used for managing and controlling the field names used by the service users.
15. The apparatus according to claim 14, wherein the hypervisor is specifically configured to:
prohibiting use of the field name in a case where the number of uses of the field name reaches a threshold;
and/or the presence of a gas in the gas,
in the case where the field name does not belong to the access-permitted field name, the field name is prohibited from being used.
16. A field management apparatus applied to a service user, the apparatus comprising:
the collection unit records the used field names according to the collection program of the service provider buried points;
an upload unit that uploads usage information to the service provider; the use information is associated with the field name recorded by the acquisition program; and the service provider inquires whether the use information with the target field name exists or not according to the target field name to be discarded, and determines the service user of the use information as the target service user when the use information with the target field name exists.
17. The apparatus according to claim 16, wherein the uploading unit specifically includes:
and uploading the use information of the field names related to the acquisition program records at regular time.
18. The apparatus according to claim 16, wherein the uploading unit specifically includes:
and uploading the use information of the field name associated with the acquisition program record in a log mode.
19. The apparatus of claim 16, the apparatus further comprising:
a statistic unit for counting the number of times of use of the used field name according to a statistic program of the buried point;
and the control unit controls the used field names according to the control program of the embedded points.
20. The apparatus according to claim 19, wherein the statistical unit specifically includes:
every time any field name is used 1 time, the number of times the field name is used is increased by 1.
21. The apparatus according to claim 19, wherein the management unit specifically includes:
a first management and control subunit which prohibits the use of the field name when the number of uses of the field name reaches a threshold value;
and/or the presence of a gas in the gas,
and a second administration subunit which prohibits use of the field name in the case where the field name does not belong to the access permitted field name.
22. An electronic device, comprising:
a processor;
a memory for storing processor-executable instructions;
wherein the processor is configured to:
carrying out embedded point acquisition on a program to a service user; the collecting program is used for collecting the field names used by the service users;
receiving the use information uploaded by the service user; the use information is associated with the field name used by the service user recorded by the acquisition program;
and determining a target service user from the use information according to the target field name to be discarded.
23. An electronic device, comprising:
a processor;
a memory for storing processor-executable instructions;
wherein the processor is configured to:
recording the used field name according to the acquisition program of the service provider buried point;
uploading usage information to the service provider; the use information is associated with the field name recorded by the acquisition program; and the service provider inquires whether the use information with the target field name exists or not according to the target field name to be discarded, and determines the service user of the use information as the target service user when the use information with the target field name exists.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710595906.6A CN107453946B (en) | 2017-07-20 | 2017-07-20 | Field management method and device and electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710595906.6A CN107453946B (en) | 2017-07-20 | 2017-07-20 | Field management method and device and electronic equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107453946A CN107453946A (en) | 2017-12-08 |
| CN107453946B true CN107453946B (en) | 2020-07-17 |
Family
ID=60488817
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710595906.6A Active CN107453946B (en) | 2017-07-20 | 2017-07-20 | Field management method and device and electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107453946B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113676547B (en) * | 2021-09-01 | 2023-04-07 | 北京字跳网络技术有限公司 | Data processing method, data processing device, storage medium and electronic equipment |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102254283A (en) * | 2011-07-26 | 2011-11-23 | 华为技术有限公司 | System, method and device for managing application programs |
| CN102904820A (en) * | 2012-09-25 | 2013-01-30 | 上海证券交易所 | Extensible traffic control data interaction method and system |
| CN103731298A (en) * | 2013-11-15 | 2014-04-16 | 中国航天科工集团第二研究院七〇六所 | Large-scale distributed network safety data acquisition method and system |
| CN103793749A (en) * | 2014-02-27 | 2014-05-14 | 四川物联恒安安全技术研究有限公司 | Safety production comprehensive supervisory platform data transmission method |
| CN105843867A (en) * | 2016-03-17 | 2016-08-10 | 畅捷通信息技术股份有限公司 | Metadata model-based search method and search device based on metadata model |
| CN106126569A (en) * | 2016-06-17 | 2016-11-16 | 南京乐运乐科技有限公司 | A kind of rapid data method of servicing and system |
| CN106157114A (en) * | 2016-07-06 | 2016-11-23 | 商宴通（上海）网络科技有限公司 | Have dinner based on user the homepage proposed algorithm of behavior modeling |
| CN106230561A (en) * | 2016-07-22 | 2016-12-14 | 努比亚技术有限公司 | Method of data capture, Apparatus and system |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10969931B2 (en) * | 2014-07-21 | 2021-04-06 | Tibco Software Inc. | Data mapping service |
-
2017
- 2017-07-20 CN CN201710595906.6A patent/CN107453946B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102254283A (en) * | 2011-07-26 | 2011-11-23 | 华为技术有限公司 | System, method and device for managing application programs |
| CN102904820A (en) * | 2012-09-25 | 2013-01-30 | 上海证券交易所 | Extensible traffic control data interaction method and system |
| CN103731298A (en) * | 2013-11-15 | 2014-04-16 | 中国航天科工集团第二研究院七〇六所 | Large-scale distributed network safety data acquisition method and system |
| CN103793749A (en) * | 2014-02-27 | 2014-05-14 | 四川物联恒安安全技术研究有限公司 | Safety production comprehensive supervisory platform data transmission method |
| CN105843867A (en) * | 2016-03-17 | 2016-08-10 | 畅捷通信息技术股份有限公司 | Metadata model-based search method and search device based on metadata model |
| CN106126569A (en) * | 2016-06-17 | 2016-11-16 | 南京乐运乐科技有限公司 | A kind of rapid data method of servicing and system |
| CN106157114A (en) * | 2016-07-06 | 2016-11-23 | 商宴通（上海）网络科技有限公司 | Have dinner based on user the homepage proposed algorithm of behavior modeling |
| CN106230561A (en) * | 2016-07-22 | 2016-12-14 | 努比亚技术有限公司 | Method of data capture, Apparatus and system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107453946A (en) | 2017-12-08 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107343047B (en) | Application promotion system and method | |
| KR101894226B1 (en) | Method, apparatus, and system for determining a location corresponding to an ip address | |
| CN109740089A (en) | Collecting method, device, system, readable storage medium storing program for executing and electronic equipment | |
| CN110781372B (en) | Method and device for optimizing website, computer equipment and storage medium | |
| CN112100204A (en) | Virtual resource regulation and control method and device, computer equipment and storage medium | |
| CN109688094B (en) | Suspicious IP configuration method, device, equipment and storage medium based on network security | |
| CN110704677A (en) | Program recommendation method and device, readable storage medium and terminal equipment | |
| CN110851339A (en) | Method and device for reporting buried point data, storage medium and terminal equipment | |
| CN110191097B (en) | Method, system, equipment and storage medium for detecting security of login page | |
| CN107453946B (en) | Field management method and device and electronic equipment | |
| CN110795026B (en) | Hot spot data identification method, device, equipment and storage medium | |
| CN106156122B (en) | Transaction information acquisition method and device | |
| CN111672128A (en) | Game mall game recommendation method and system based on local reserved time identification | |
| CN108399031B (en) | Method and device for determining interface layout mode | |
| US20180020075A1 (en) | Apparatus and method for providing data based on cloud service | |
| CN113703993A (en) | Service message processing method, device and equipment | |
| CN109242643B (en) | Game recommendation method and device applied to live broadcast platform and storage medium | |
| CN108629610B (en) | Method and device for determining popularization information exposure | |
| CN111143377A (en) | Automatic driving simulation data collection method, device and system | |
| CN109002491A (en) | User interest acquisition method, device, computer installation and computer readable storage medium | |
| JP7088972B2 (en) | Information providing equipment, information providing method, and program | |
| CN109508318B (en) | Memory space counting method and device, electronic equipment and readable storage medium | |
| CN110418020B (en) | List state information processing method and device, electronic terminal and storage medium | |
| CN115361358B (en) | IP extraction method and device, storage medium and electronic device | |
| EP2639714A1 (en) | Information collection device, system, method, and program |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| TR01 | Transfer of patent right | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20200923 Address after: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman Islands Patentee after: Innovative advanced technology Co.,Ltd. Address before: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman Islands Patentee before: Advanced innovation technology Co.,Ltd. Effective date of registration: 20200923 Address after: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman Islands Patentee after: Advanced innovation technology Co.,Ltd. Address before: A four-storey 847 mailbox in Grand Cayman Capital Building, British Cayman Islands Patentee before: Alibaba Group Holding Ltd. |