Detailed Description
In order to make the objects, technical solutions and advantages of the present application more clearly understood, the present application is further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.
It is understood that the term "or/and" as used herein, describing an association relationship of associated objects, means that there may be three relationships, e.g., a or/and B, may mean: a exists alone, A and B exist simultaneously, and B exists alone. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship.
The data object identification generation method provided by the application can be applied to the application environment shown in fig. 1. The application environment includes a terminal 102, a network 104, and a server 106, and the terminal 102 and the server 106 can be communicatively connected via the network 104. The network system formed by the terminal 102, the network 104 and the server 106 may be based on the internet, may also be based on a local area network, and may also be based on a combination network of the internet and the local area network, which is not described herein again.
The terminal 102 may be, but is not limited to, a cellular phone 1022, a laptop 1024, a desktop 1026, etc.; in fact, it is obvious that the user can also use electronic devices of the type such as: tablet computers, laptop computers, personal Digital Assistants (PDAs), wearable devices (e.g., smart glasses, smart watches, etc.), etc., which are not limited in this application.
The operating system layer of the terminal 102 is installed with a web application, which may be a web application, a client application, an applet application, or the like. The web application may be a web browser; the client Application may refer to various APPs (applications), for example, a computer Application or a mobile Application, such as a social platform program, a shopping platform program, or an instant messaging program; the applet application refers to an application that can be used without downloading and installing, for example, a wechat applet that runs in a wechat environment, and a hundred applet that runs in a hundred degree environment.
The server 106 may be a device that stores code data required for the network application on the terminal 102 to run. For example, for a web browser, the server 106 may store business codes for all constituent web pages within the associated web site.
The network 104 is used to enable a network connection between the terminal 102 and the server 106 and may include various types of wired or wireless networks. The network 104 may include the internet, a local area network ("LAN"), a wide area network ("WAN"), an intranet, a mobile phone network, a Virtual Private Network (VPN), a cellular or other mobile communication network, bluetooth, NFC, or any combination thereof. The network 104 may also be based on a corresponding communication protocol when performing data transmission, for example, the web browser may be based on an HTTP communication protocol when receiving a service code corresponding to a web page, and the mobile application may be based on a Websocket communication protocol when receiving a service code.
In an embodiment, as shown in fig. 2, a service parameter collecting method is provided, which is described by taking the application of the method to the terminal in fig. 1 as an example, and includes the following steps:
step 202, obtaining a jump link of a page element.
Here, a page element generally refers to an element presented in a web application page, and the page element may include text, pictures, audio, animation, video, and the like.
Here, a jump link generally refers to a URL (Uniform Resource Locator) of a target page to which a page element is jumped to after being triggered (e.g., exposed or clicked).
Whether web applications, client applications, applet applications, etc., or other types of applications. When a page element is operated by a user, a data access request is generally sent to a server, and the data access request carries a jump link of the page element.
Specifically, the terminal may acquire the jump link of the page element when monitoring that the page element is exposed or when monitoring that the page element is clicked.
Step 204, acquiring a target link matching rule matched with the jump link according to the jump link;
here, the target link matching rule is a link matching rule that matches the jump link, which is screened from the plurality of link matching rules. The link matching rule is generally a regular expression, and the regular expression can be used for effectively matching links (or routing addresses) of various web applications, client applications or applet applications. The regular expression is a logical formula for operating on character strings, namely, a 'regular character string' is formed by using specific characters defined in advance and a combination of the specific characters. Because the jump link is a character string, if the character string of the jump link is matched with the character string according to the rule of the regular expression, the jump link is matched with the corresponding link matching rule, namely the jump link is in accordance with the filtering logic of the regular expression. The link matching rule may also be other specific rules, as desired.
Specifically, the terminal may screen out a target link matching rule matching the jump link from the plurality of link matching rules.
And step 206, analyzing the service parameters of the page elements from the jump links according to the parameter analysis rules corresponding to the target link matching rules.
In the embodiment of the application, it is considered that the jump link often includes information related to the service attribute of the page element, for example, after a commodity picture in the shopping platform is clicked, the jump link includes commodity information of a corresponding commodity, and the commodity information is a service parameter.
Specifically, after determining the target link matching rule, the terminal may search for a parameter of a corresponding position according to an analysis rule corresponding to the target link matching rule; and assigning the searched parameters to corresponding fields.
The parsing rules mainly include two types, one is for the URL, and the parameter at the corresponding position is intercepted and assigned to the corresponding field after being divided, and the other is for the URL? The latter key = value format parameter, according to analyzing the parameter value of the corresponding key, and assigning to the corresponding field. These two parameter resolution rules can effectively cover links (or routing addresses) of various websites, applications, and applets.
The business parameter acquisition method comprises the steps of acquiring a jump link of a page element, acquiring a target link matching rule matched with the jump link according to the jump link, and analyzing business parameters of the page element from the jump link according to a parameter analysis rule corresponding to the target link matching rule. By adopting the scheme of the embodiment, the page element service parameters can be acquired without burying points or few burying points and knowing the service parameters of the service logic of the peripheral system.
For the webpage application, as the webpage code of the webpage application is provided with the jump link, the jump link of the page element can be obtained from the webpage code without burying points. For small program application, the jump link of the page element needs to be written into the page code of the small program application through a small amount of embedded points, and for client application, the jump link needs to be transmitted to a collection plug-in or a software development toolkit through a parameter transmission mode. Although a small amount of buried points are needed for obtaining the jump link of the page element for the client application and the applet application, the number of buried points is much smaller than that needed for obtaining the service parameter by the traditional manual buried points, and the workload of buried points can be reduced.
Meanwhile, in the traditional service parameter acquisition mode, the service logic of the page to which the parameters belong is acquired from the peripheral system, and in order to acquire the service parameters in the click exposure log, the service codes are coupled with the statistical codes, which is not beneficial to code management of the front end and the client. In the scheme of the embodiment of the application, the acquisition of the service parameters does not need to depend on a peripheral system, and the condition that the statistical codes are coupled with the service codes can be avoided. In addition, the collection of the service parameters can be completed at the front end/client end, and no resource pressure is generated on a data cleaning layer.
In one embodiment, the obtaining of the target link matching rule matching the jumped link according to the jumped link may include: and screening out a target link matching rule matched with the jump link from the locally stored link matching rule set according to the jump link.
Here, the link matching rule set generally stores a plurality of link matching rules, and the link matching rule set may be configured locally, or may be obtained from the server after the server configures. The general better mode is that after the server configures the link matching rule set, the terminal acquires the link matching rule set from the server, so that each terminal does not need to configure the link matching rule set independently, when the number of the terminals is large, the configuration times can be obviously reduced, and the universal applicability of the scheme can be improved, namely, the service of different companies and the types of different terminals are all applicable. Here, local storage may also refer to caching.
In this embodiment, the target link matching rule is selected from the locally stored link matching rule set, and it is not necessary to request a service to query the target link matching rule each time a page element click event (a page element is clicked) or an exposure event (a page element exposure) is monitored, so that the number of interactions with the server can be reduced, and the matching efficiency of the link matching rule is improved.
In one embodiment, the obtaining of the target link matching rule matching the jumped link according to the jumped link may include: and requesting the server to acquire a target link matching rule matched with the jump link according to the jump link, and receiving the target link matching rule returned by the server.
And the server screens out a target link matching rule matched with the jump link from the link matching rule set according to the jump link. The set of link matching rules typically stores a plurality of link matching rules.
In the embodiment, the link matching rule set does not need to be stored locally in the terminal, so that the data storage space can be saved.
The above-mentioned method for obtaining the target link matching rule according to the jump link can be selected based on the needs of multiple aspects such as matching efficiency and storage space.
In an embodiment, the obtaining the jump link of the page element may include: and acquiring the jump link of the page element when the exposure of the page element is monitored or the page element is monitored to be clicked.
Here, the page element exposure means that the page element enters a screen and is presented to a user. As will be understood by those skilled in the art, when a page element is exposed, the jump link of the page element refers to a link path of a page to which the page element jumps after being clicked, and when the page element is clicked, the jump link of the page element also refers to a link path of a page to which the page element jumps after being clicked.
In an embodiment, as shown in fig. 3, a service parameter collecting method is provided, which is described by taking the application of the method to the terminal in fig. 1 as an example, and includes the following steps:
step 302, acquiring a link matching rule set from a server side and a parameter analysis rule corresponding to each link matching rule in the link matching rule set;
specifically, the terminal may obtain the link matching rule set and the parameter parsing rule corresponding to each link matching rule from the server side when the collection plug-in is loaded or when a Software Development Kit (SDK) is initialized.
Step 304, storing the acquired link matching rule set and each parameter analysis rule;
specifically, the terminal may write the obtained link matching rule set and each parameter parsing rule into a memory or locally, so as to cache the link matching rule set and each parameter parsing rule.
Step 306, acquiring a jump link of the page element;
specifically, the terminal may acquire the jump link of the page element when monitoring that the page element is exposed or when monitoring that the page element is clicked.
Step 308, screening out a target link matching rule matched with the jump link from the locally stored link matching rule set according to the jump link;
and 310, analyzing the service parameters of the page elements from the jump links according to the parameter analysis rule corresponding to the target link matching rule.
With respect to step 308 and step 310, reference may be made to the description of step 204 and step 206, which are not repeated herein.
In this embodiment, the acquisition of the service parameters can be realized without embedding points or only embedding a small number of points and without knowing the service logic of the peripheral system. Meanwhile, only the server side is required to obtain the link matching rule set, and each terminal is not required to be respectively configured with the link matching rule set, so that the universal applicability of the scheme is improved, namely, the service of different companies and the types of different terminals are applicable. And the acquired link matching rule set and each parameter analysis rule are stored, and the target link matching rule matched with the jump link is screened out from the locally stored link matching rule set according to the jump link, so that the interaction times and the interaction time with the server can be reduced, and the acquisition efficiency of the service parameters is improved.
In an embodiment, the service parameter collecting method of the present application may further include the steps of: and after the service parameters are bound with the element data of the page elements, adding the service parameters into a target log of the page elements. Generally, the terminal reports the target log, the reporting object is generally a server, and the reporting object corresponding to the target log and the server configured with the link matching rule and the parameter parsing rule may be the same server or different servers.
Here, the target log generally includes an exposure log or a click log. Here, the element data of the page element may be identification information of the page element, or other data capable of distinguishing different page elements.
Specifically, the terminal may bind the analyzed service parameter with element data of a corresponding page element, and join the service parameter into an exposure log or a click log of the page element to complete reporting. Generally, the service parameters collected by the exposure of the corresponding page elements are added into the exposure log, and the service parameters collected by clicking the corresponding page elements are added into the click log.
In one embodiment, the service parameter collecting method of the present application may further include the steps of: when the link matching rule set does not have a link matching rule matched with the jump link of the page element, prompt information is generated; and sending the prompt information to a server or a target terminal.
Here, the target terminal may be a manager terminal. The prompt information may be generated by filling the jump link or the related information of the jump link into a preset information template to obtain the prompt information. The information template can be set according to actual needs.
Specifically, the prompt information may be sent to the target terminal so that the administrator can obtain the prompt information in time, or the prompt information may be sent to the server so that the server can manage and process the prompt information in a unified manner.
Here, the presentation information may be recorded with a jump link or related information of the jump link. The jump link can be obtained through the associated information, or the associated information includes a partial character string of the jump link. The prompt information is used for prompting a manager that a new service scene, namely a new page jump link, appears, and for the new page jump link, no matched link matching rule exists in the link matching rule set, and a link matching rule and a parameter parsing rule are configured for the new page jump link.
In the scheme of the embodiment of the application, when a new service scene, namely a new page jump link, appears, the link matching rule and the parameter analysis rule configured in the background are updated, and the front-end version sending is not relied on. Meanwhile, when the link matching rule is concentrated and no link matching rule matched with the jump link exists, prompt information is generated and sent, and a manager can be reminded of updating the configuration in time.
In one embodiment, the terminal is installed with a web application, the web application includes a web application, a client application or/and an applet application, and the page element is an element in the web application, the client application or the applet application.
As can be seen from the above, for network applications, the service parameter acquisition of exposed elements or clicked elements of a page can be realized without front-end point burying, and the condition that a statistical code is coupled with a service code is avoided; for client application or applet application, only a very small amount of buried point work needs to be done by developers, and specific business logic of a peripheral system does not need to be concerned.
In an embodiment, the target link matching rule is a regular expression, and when the jump link matches the filter rule of the regular expression, the regular expression is determined to match the jump link. Links (or routing addresses) of various types of web applications, client applications, or applet applications may be efficiently matched using regular expressions.
In an embodiment, as shown in fig. 4, a service parameter collecting method is provided, which is described by taking the application of the method to the terminal in fig. 1 as an example, and includes the following steps:
step 402, acquiring a link matching rule set from a server side and a parameter analysis rule corresponding to each link matching rule in the link matching rule set;
step 404, storing the acquired link matching rule set and each parameter analysis rule;
step 406, acquiring a jump link of the page element;
step 402, step 404 and step 406 in this embodiment may refer to the descriptions in step 302, step 304 and step 306, which are not repeated herein.
Step 408, screening a link matching rule from a locally stored link matching rule set according to the jump link;
specifically, the link matching rules in the link matching rule set are regular expressions, whether the jump links meet the filtering rules of one or more regular expressions in the link matching rule set is detected, and if yes, the corresponding link matching rules are screened out as target link matching rules.
Step 410, detecting whether a target link matching rule matched with the jump link is screened, if so, entering step 412, otherwise, entering step 416;
and when the target link matching rule matched with the jump link is not screened, the service parameters are not analyzed.
Step 412, resolving the service parameters of the page elements from the jump links according to the parameter resolution rules corresponding to the target link matching rules;
table 1 below is a schematic correspondence relationship between a link matching rule (regular expression) and a parameter parsing rule (parameter configuration rule). The specific form of each regular expression can be set as required, and the specific form of the regular expression does not constitute a limitation on the scheme of the present invention. The parameter configuration rules are also not limited to the ones listed in table 1.
TABLE 1
Serial number
|
Regular expression
|
Electronic commerce collaboration (eletp) type
|
Rules for parameter configuration
|
1
|
Regular expression 1
|
Shop
|
Position one + shop mark
|
2
|
Regular expression 2
|
Shop
|
Shop with one positionIdentification
|
3
|
Regular expression 3
|
Coupon
|
Label + Activity identification
|
4
|
Regular expression 4
|
Coupon
|
Activity ID + Activity ID |
The terminal can analyze the service parameters of the page elements from the jump links according to the parameter analysis rules corresponding to the target link matching rules, for example, if the parameter configuration rule of the jump links is "tag + active identifier", the corresponding "tag" and "active identifier" can be analyzed as the service parameters of the page elements.
Step 414, after the service parameters are bound with the element data of the page elements, adding the bound service parameters into the target logs of the page elements.
Specifically, the terminal may bind the analyzed service parameter with element data of a corresponding page element, and join the service parameter into an exposure log or a click log of the page element to complete reporting.
Step 416, generating and sending a prompt message, in which the jump link or the related information of the jump link is recorded.
Here, the prompt information is used to prompt the user to modify the configuration.
Specifically, the terminal may generate the prompt information in which the jump link or the associated information of the jump link is recorded, and transmit the prompt information to the server or another terminal (e.g., a target terminal).
According to the scheme, the non-embedded point acquisition of the service parameters can be realized, meanwhile, due to the fact that parameter analysis rules are managed at the rear end, the universal applicability is achieved, namely the service of different companies and the service of different terminal types are applicable, when a new scene occurs, the modifiable configuration can take effect immediately, and the front end version sending is not depended on. It should be noted that fig. 4 is a schematic flow chart of a preferred embodiment of the service parameter collection method according to the present invention. According to different considerations, when the method for acquiring service parameters of the present invention is implemented, all the steps shown in fig. 4 may be included, or only a part of the steps shown in fig. 4 may be included.
It should be understood that although the various steps in the flow charts of fig. 2-4 are shown in order as indicated by the arrows, the steps are not necessarily performed in order as indicated by the arrows. The steps are not performed in the exact order shown and described, and may be performed in other orders, unless explicitly stated otherwise. Moreover, at least some of the steps in fig. 2-4 may include multiple sub-steps or multiple stages that are not necessarily performed at the same time, but may be performed at different times, and the order of performing the sub-steps or stages is not necessarily sequential, but may be performed alternately or alternatingly with other steps or at least some of the sub-steps or stages of other steps.
In one embodiment, as shown in fig. 5, a service parameter collecting apparatus is provided, which includes: a link acquisition module 502, a rule matching module 504, and a parameter acquisition module 506, wherein:
a link obtaining module 502 for obtaining the jump link of the page element;
a rule matching module 504, configured to obtain a target link matching rule matching the jump link according to the jump link;
and the parameter acquisition module 506 is configured to analyze the service parameters of the page elements from the jump links according to the parameter analysis rule corresponding to the target link matching rule.
In one embodiment, rule matching module 504 may filter out target link matching rules that match the jumped link from a locally stored set of link matching rules based on the jumped link.
In one embodiment, the rule matching module 504 may receive the target link matching rule returned by the server according to a request from the jump link to the server for obtaining the target link matching rule matching the jump link.
In one embodiment, the link obtaining module 502 may obtain the jump link of the page element when the exposure of the page element is monitored or when the page element is monitored to be clicked.
In an embodiment, the service parameter collecting apparatus may further include a rule obtaining module (not shown in the figure), where the rule obtaining module is configured to obtain, from the server side, a link matching rule set and a parameter parsing rule corresponding to each link matching rule in the link matching rule set; and storing the acquired link matching rule set and each parameter analysis rule.
In one embodiment, the rule obtaining module may obtain the link matching rule set and the parameter parsing rule corresponding to each link matching rule from the server side when the collection plug-in is loaded or when the software development kit is initialized.
In an embodiment, the service parameter collecting apparatus may further include a log processing module (not shown in the figure), and the log processing module is configured to bind the service parameter and the element data of the page element, and add the bound service parameter and the element data to a target log of the page element. Here, the target log may include an exposure log or a click log. In an embodiment, the log processing module may be further configured to report the target log.
In an embodiment, the service parameter collecting apparatus may further include a prompt module (not shown in the figure), where the prompt module is configured to generate a prompt message when there is no link matching rule matching the jump link in the link matching rule set; and sending the prompt information to a server or a target terminal. Generally, the hint information describes a jump link or information related to a jump link.
In one embodiment, the service parameter collecting device is applied to a terminal, a network application is installed on the terminal, the network application includes a web application, a client application or/and an applet application, and a page element is an element in the web application, the client application or the applet application.
In an embodiment, the target link matching rule is a regular expression, and when the jump link conforms to the filtering rule of the regular expression, it is determined that the regular expression matches the jump link.
For the specific definition of the service parameter collecting device, reference may be made to the above definition of the service parameter collecting method, which is not described herein again. The modules in the service parameter acquiring device may be implemented wholly or partially by software, hardware and a combination thereof. The modules can be embedded in a hardware form or independent of a processor in the computer device, and can also be stored in a memory in the computer device in a software form, so that the processor can call and execute operations corresponding to the modules.
In one embodiment, a computer device is provided, which may be a terminal, and its internal structure diagram may be as shown in fig. 6. The computer device comprises a processor, a memory, a network interface, a display screen and an input device which are connected through a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device comprises a nonvolatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of an operating system and computer programs in the non-volatile storage medium. The network interface of the computer device is used for communicating with an external terminal through a network connection. The computer program is executed by a processor to implement a business parameter acquisition method. The display screen of the computer equipment can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer equipment can be a touch layer covered on the display screen, a key, a track ball or a touch pad arranged on a shell of the computer equipment, an external keyboard, a touch pad or a mouse and the like.
Those skilled in the art will appreciate that the architecture shown in fig. 6 is merely a block diagram of some of the structures associated with the disclosed aspects and is not intended to limit the computing devices to which the disclosed aspects apply, as particular computing devices may include more or less components than those shown, or may combine certain components, or have a different arrangement of components.
In one embodiment, there is provided a computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the following steps when executing the computer program:
acquiring a jump link of a page element;
acquiring a target link matching rule matched with the jump link according to the jump link;
and resolving the service parameters of the page elements from the jump links according to the parameter resolution rules corresponding to the target link matching rules.
In one embodiment, when the processor executes the computer program to implement the above step of obtaining the target link matching rule matching with the jump link according to the jump link, the following steps are specifically implemented: and screening out a target link matching rule matched with the jump link from the locally stored link matching rule set according to the jump link.
In one embodiment, when the processor executes the computer program to implement the above step of obtaining the target link matching rule matching with the jump link according to the jump link, the following steps are specifically implemented: and requesting the server to acquire a target link matching rule matched with the jump link according to the jump link, and receiving the target link matching rule returned by the server.
In an embodiment, when the processor executes the computer program to implement the step of obtaining the jump link of the page element, the following steps are specifically implemented: and acquiring the jump link of the page element when the exposure of the page element is monitored or the page element is monitored to be clicked.
In one embodiment, the processor, when executing the computer program, further performs the steps of: acquiring a link matching rule set and a parameter analysis rule corresponding to each link matching rule in the link matching rule set from a server side; and storing the acquired link matching rule set and each parameter analysis rule.
In one embodiment, when a collection plug-in is loaded or a software development kit is initialized, a link matching rule set and parameter analysis rules corresponding to the link matching rules are obtained from a server side.
In one embodiment, the processor, when executing the computer program, further performs the steps of: and binding the service parameters with the element data of the page elements, and adding the bound service parameters into a target log of the page elements. Typically, the target log comprises an exposure log or a click log.
In one embodiment, the processor when executing the computer program further performs the steps of: when the link matching rule is concentrated and no link matching rule matched with the jump link exists, prompt information is generated; and sending the prompt information to a server or a target terminal. Generally, the hint information describes a jump link or information related to a jump link.
In one embodiment, the computer device is a terminal, a web application is installed on the terminal, the web application includes a web application, a client application or/and an applet application, and the page element is an element in the web application, the client application or the applet application.
In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored which, when executed by a processor, performs the steps of:
acquiring a jump link of a page element;
acquiring a target link matching rule matched with the jump link according to the jump link;
and resolving the service parameters of the page elements from the jump links according to the parameter resolution rules corresponding to the target link matching rules.
In one embodiment, when the computer program is executed by the processor to implement the above step of obtaining the target link matching rule matching with the jump link according to the jump link, the following steps are specifically implemented: and screening out a target link matching rule matched with the jump link from the locally stored link matching rule set according to the jump link.
In one embodiment, when the computer program is executed by the processor to implement the above step of obtaining the target link matching rule matching with the jump link according to the jump link, the following steps are specifically implemented: and requesting the server to acquire a target link matching rule matched with the jump link according to the jump link, and receiving the target link matching rule returned by the server.
In one embodiment, when the computer program is executed by the processor to implement the step of obtaining the jump link of the page element, the following steps are specifically implemented: and acquiring the jump link of the page element when the exposure of the page element is monitored or the click of the page element is monitored.
In one embodiment, the computer program when executed by the processor further performs the steps of: acquiring a link matching rule set and a parameter analysis rule corresponding to each link matching rule in the link matching rule set from a server side; and storing the acquired link matching rule set and each parameter analysis rule.
In one embodiment, when a collection plug-in is loaded or a software development kit is initialized, a link matching rule set and parameter analysis rules corresponding to the link matching rules are obtained from a server side.
In one embodiment, the computer program when executed by the processor further performs the steps of: and after the service parameters are bound with the element data of the page elements, adding the service parameters into a target log of the page elements. Typically, the target log includes an exposure log or a click log.
In one embodiment, the computer program when executed by the processor further performs the steps of: when the link matching rule is concentrated and no link matching rule matched with the jump link exists, prompt information is generated; and sending the prompt information to a server or a target terminal. Generally, the hint information describes a jump link or information related to a jump link.
In one embodiment, the computer device is a terminal, the terminal is provided with a web application, the web application includes a web application, a client application or/and an applet application, and the page element is an element in the web application, the client application or the applet application.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above may be implemented by hardware instructions of a computer program, which may be stored in a non-volatile computer-readable storage medium, and when executed, may include the processes of the embodiments of the methods described above. Any reference to memory, storage, database or other medium used in the embodiments provided herein can include non-volatile and/or volatile memory. Non-volatile memory can include read-only memory (ROM), programmable ROM (PROM), electrically Programmable ROM (EPROM), electrically Erasable Programmable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms such as Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double Data Rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous Link DRAM (SLDRAM), rambus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).
The technical features of the above embodiments can be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the above embodiments are not described, but should be considered as the scope of the present specification as long as there is no contradiction between the combinations of the technical features.
The above-mentioned embodiments only express several embodiments of the present application, and the description thereof is more specific and detailed, but not construed as limiting the scope of the invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the concept of the present application, which falls within the scope of protection of the present application. Therefore, the protection scope of the present patent application shall be subject to the appended claims.