CN112784132A - Data acquisition method and device and computer storage medium - Google Patents
Data acquisition method and device and computer storage medium Download PDFInfo
- Publication number
- CN112784132A CN112784132A CN201911097201.7A CN201911097201A CN112784132A CN 112784132 A CN112784132 A CN 112784132A CN 201911097201 A CN201911097201 A CN 201911097201A CN 112784132 A CN112784132 A CN 112784132A
- Authority
- CN
- China
- Prior art keywords
- view
- node
- application
- comment
- interface
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/951—Indexing; Web crawling techniques
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/953—Querying, e.g. by the use of web search engines
Landscapes
- Engineering & Computer Science (AREA)
- Databases & Information Systems (AREA)
- Theoretical Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- User Interface Of Digital Computer (AREA)
Abstract
The embodiment of the application discloses a data acquisition method, a data acquisition device and a computer readable storage medium, wherein the method comprises the following steps: obtaining comment query information, wherein the comment query information comprises first application information of a target application and second application information of an application to be queried; the target application comprises comment data corresponding to a plurality of functional applications respectively, and the functional applications comprise applications to be inquired; accessing a user comment interface corresponding to the application to be inquired based on the first application information and the second application information; traversing a plurality of view nodes associated with the user comment interface, and acquiring view resource identifiers of the view nodes; determining a view node with a target view resource identifier as a target view node in a plurality of view nodes, and extracting interface service data in the target view node; the interface business data is comment data associated with the comment user in the user comment interface. By the method and the device, the user comment data of the application can be efficiently acquired.
Description
Technical Field
The present application relates to the field of internet technologies, and in particular, to a data acquisition method and apparatus, and a computer-readable storage medium.
Background
The method has the advantages that the user comment data of the Application (APP) are very important to obtain, the appeal of the user can be accurately known through obtaining and analyzing the user comment data of the Application, the defects of the App and the public opinion information of the current App can be rapidly found, and therefore corresponding measures can be taken timely.
At present, a common method for acquiring user comment data of an application is a web crawler, but the web crawler is only suitable for crawling user comment data in an application web version, and for a native application version (non-web version), the web crawler cannot be used for acquiring the comment data of the user to the application, so that a large amount of manpower is required for acquiring the comment data of the user to a specific application, and low efficiency is caused.
Disclosure of Invention
The embodiment of the application provides a data acquisition method, a data acquisition device and a computer-readable storage medium, which can efficiently acquire user comment data of an application.
An embodiment of the present application provides a data obtaining method, including:
obtaining comment query information, wherein the comment query information comprises first application information of a target application and second application information of an application to be queried; the target application comprises comment data corresponding to a plurality of functional applications respectively, and the functional applications comprise the application to be inquired;
accessing a user comment interface corresponding to the application to be inquired based on the first application information and the second application information;
traversing a plurality of view nodes associated with the user comment interface, and acquiring view resource identifiers of the view nodes;
determining a view node with a target view resource identifier as a target view node in the plurality of view nodes, and extracting interface service data in the target view node; the interface service data is comment data which is associated with a comment user in the user comment interface.
Wherein, still include:
combining interface service data belonging to the same comment user to obtain comment data corresponding to the comment user in the user comment interface;
or combining the interface service data belonging to the same target view resource identifier to obtain the comment data associated with each target view resource identifier.
Accessing a user comment interface corresponding to the application to be queried based on the first application information and the second application information includes:
reading the first application information and the second application information through a starting function;
and calling the target application according to the first application information, and accessing the user comment interface corresponding to the application to be inquired in the target application according to the second application information.
Wherein traversing a plurality of view nodes associated with the user comment interface and obtaining view resource identifiers for the plurality of view nodes comprises:
acquiring detailed layout information corresponding to the user comment interface through a page layout scanning tool;
and traversing the view nodes in the detailed layout information to acquire the view resource identifiers corresponding to the view nodes.
Wherein the plurality of view nodes comprises a root view node and a plurality of child view nodes;
the traversing the view nodes in the detailed layout information to obtain the view resource identifiers corresponding to the view nodes includes:
acquiring the root view node in the detailed layout information;
acquiring a view resource identifier corresponding to the root view node;
calling a system auxiliary function interface to acquire the plurality of child view nodes associated with the root view node through the view resource identifier corresponding to the root view node;
and acquiring view resource identifiers corresponding to the multiple child view nodes respectively.
Wherein the step of calling a system auxiliary function interface to acquire the plurality of child view nodes associated with the root view node through the view resource identifier corresponding to the root view node comprises:
calling the system auxiliary function interface to acquire a first child view node associated with the root view node through the view resource identifier corresponding to the root view node; the first child view node corresponds to comment data displayed on a screen in the user comment interface;
calling a simulation operation auxiliary function interface, performing simulation sliding operation on the user comment interface in the root view node through the simulation operation auxiliary function interface, and displaying non-traversed comment data in the user comment interface after sliding in the screen;
calling the system auxiliary function interface to acquire a second child view node associated with the root view node; the second child view node corresponds to the non-traversed comment data in the user comment interface after sliding;
determining the first child view node and the second child view node as the plurality of child view nodes associated with the root view node.
Wherein, the determining a view node with a target view resource identifier in the plurality of view nodes as a target view node comprises:
inputting the target view resource identification;
respectively matching the target view resource identifier with the view resource identifier corresponding to each view node, and determining the view node with the target view resource identifier as the target view node according to the matching result;
wherein the view resource type corresponding to the target view resource identification comprises at least one of: user name, user model, review date, review content, and application rating.
Wherein the extracting interface service data in the target view node comprises:
acquiring a node data set corresponding to the target view node;
and extracting data with text key fields from the node data set, and determining the data with the text key fields as the interface service data.
An aspect of an embodiment of the present application provides a data obtaining apparatus, including:
the system comprises a first acquisition module, a second acquisition module and a query module, wherein the first acquisition module is used for acquiring comment query information which comprises first application information of a target application and second application information of an application to be queried; the target application comprises comment data corresponding to a plurality of functional applications respectively, and the functional applications comprise the application to be inquired;
the access module is used for accessing a user comment interface corresponding to the application to be inquired based on the first application information and the second application information;
the second obtaining module is used for traversing a plurality of view nodes associated with the user comment interface and obtaining view resource identifiers of the view nodes;
a determining module, configured to determine, as a target view node, a view node with a target view resource identifier in the plurality of view nodes;
the extraction module is used for extracting the interface service data in the target view node; the interface service data is comment data which is associated with a comment user in the user comment interface.
Wherein, still include:
the first combination module is used for combining interface service data belonging to the same comment user to obtain comment data corresponding to the comment user in the user comment interface; alternatively, the first and second electrodes may be,
and the second combination module is used for combining the interface service data belonging to the same target view resource identifier to obtain comment data associated with each target view resource identifier.
Wherein the access module comprises:
the reading unit is used for reading the first application information and the second application information through a starting function;
and the access unit is used for calling the target application according to the first application information and accessing the user comment interface corresponding to the application to be inquired in the target application according to the second application information.
Wherein the second obtaining module includes:
the information obtaining unit is used for obtaining detailed layout information corresponding to the user comment interface through a page layout scanning tool;
and the obtaining identification unit is used for traversing the view nodes in the detailed layout information and obtaining the view resource identifications corresponding to the view nodes.
Wherein the plurality of view nodes comprises a root view node and a plurality of child view nodes;
the acquiring identification unit comprises:
a first obtaining node subunit, configured to obtain the root view node in the detailed layout information;
the first obtaining identifier subunit is configured to obtain a view resource identifier corresponding to the root view node;
a second obtaining node subunit, configured to invoke a system auxiliary function interface to obtain the multiple sub-view nodes associated with the root view node through the view resource identifier corresponding to the root view node;
and the second acquiring identifier subunit is configured to acquire view resource identifiers corresponding to the multiple sub-view nodes, respectively.
Wherein the second obtaining node subunit includes:
the first acquiring child node subunit is configured to invoke the system auxiliary function interface to acquire a first child view node associated with the root view node through the view resource identifier corresponding to the root view node; the first child view node corresponds to comment data displayed on a screen in the user comment interface;
the simulation sliding subunit is used for calling a simulation operation auxiliary function interface, performing simulation sliding operation on the user comment interface in the root view node through the simulation operation auxiliary function interface, and displaying the non-traversed comment data in the user comment interface after sliding in the screen;
a second acquiring child node subunit, configured to invoke the system auxiliary function interface to acquire a second child view node associated with the root view node; the second child view node corresponds to the non-traversed comment data in the user comment interface after sliding;
a determining subunit, configured to determine the first child view node and the second child view node as the plurality of child view nodes associated with the root view node.
Wherein the determining module comprises:
the input unit is used for inputting the target view resource identifier;
a node determining unit, configured to match the target view resource identifier with a view resource identifier corresponding to each view node, and determine, according to a matching result, the view node having the target view resource identifier as the target view node;
wherein the view resource type corresponding to the target view resource identification comprises at least one of: user name, user model, review date, review content, and application rating.
Wherein, the extraction module comprises:
the acquisition set unit is used for acquiring a node data set corresponding to the target view node;
and the data determining unit is used for extracting data with text key fields from the node data set and determining the data with the text key fields as the interface service data.
An aspect of an embodiment of the present application provides a computer device, including: a processor and a memory; the processor is connected with the memory, wherein the memory is used for storing a computer program, and the processor is used for calling the computer program to execute the method in the embodiment of the application.
An aspect of the embodiments of the present application provides a computer-readable storage medium storing a computer program, the computer program comprising program instructions that, when executed by a processor, perform a method as in the embodiments of the present application.
Obtaining comment query information in the embodiment of the application, wherein the comment query information comprises first application information of a target application and second application information of an application to be queried; the target application comprises comment data corresponding to a plurality of functional applications respectively, and the functional applications comprise the application to be inquired; accessing a user comment interface corresponding to the application to be inquired based on the first application information and the second application information; traversing a plurality of view nodes associated with the user comment interface, and acquiring view resource identifiers of the view nodes; determining a view node with a target view resource identifier as a target view node in the plurality of view nodes, and extracting interface service data in the target view node; the interface service data is comment data which is associated with a comment user in the user comment interface. Therefore, the user comment interface corresponding to the application to be inquired can be accessed by receiving the first application information of the target application and the second application information of the application to be inquired, then view resource identifiers of the view nodes are obtained through the view nodes on the user comment interface, and after the target view resource identifiers are determined, interface service data in the target view nodes can be crawled in a full-automatic mode, so that the collection efficiency of the user comment data in the application can be improved.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
Fig. 1 is a schematic view of a data acquisition scenario provided in an embodiment of the present application;
fig. 2 is a schematic flowchart of a data acquisition method according to an embodiment of the present application;
FIG. 3 is a schematic flow chart diagram of another data acquisition method provided in the embodiments of the present application;
fig. 4 is a schematic view of another scenario of data acquisition provided in the embodiment of the present application;
FIG. 5 is a schematic view of a scene simulating a sliding screen according to an embodiment of the present application;
FIG. 6a is a schematic diagram of a method for combining comment data provided by an embodiment of the present application;
FIG. 6b is a schematic diagram of another method for combining comment data provided by an embodiment of the present application;
FIG. 7 is a schematic flow chart diagram illustrating another data acquisition method provided in an embodiment of the present application;
FIG. 8 is a schematic structural diagram of a computer apparatus device according to an embodiment of the present disclosure;
fig. 9 is a schematic structural diagram of an electronic device according to an embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
Please refer to fig. 1, which is a schematic view of a data acquisition scenario provided in an embodiment of the present application. As shown in fig. 1, the mobile terminal 10A may enter a user comment interface (such as the user comment interface 10B shown in fig. 1) of the application to be queried through a general interface, comment query information and a start function are input in the mobile terminal 10A, and through the start function, the start function may be a StartActivity code (the StartActivity code serves as to introduce the comment query information), and a current interface of the mobile terminal 10A in fig. 1 jumps to the user comment interface 10B shown in fig. 1; through a page layout scanning tool under a Software Development Kit (SDK) in a mobile terminal, such as a tool uiautomatoviewer under the SDK in an Android system (Android), to scan and analyze the user comment interface 10B, knowing a hierarchical relationship of the user comment interface 10B and attributes of each control (view node), detailed layout information corresponding to the user comment interface 10B may be obtained, where the detailed layout information may correspond to the node structure 10C in fig. 1, traverse view nodes in the node structure 10C, and obtain view resource identifiers (resource-ids) corresponding to each view node; when the administrator wants to query the user name and the comment score in the detailed layout information, the view resource identifier corresponding to the user name and the comment score may be determined as a target view resource identifier, the target view resource identifier is input into the mobile terminal 10A, the mobile terminal 10A matches the target view resource identifier with the view resource identifier corresponding to each view node, and according to a matching result, the view node having the target view resource identifier is determined as the target view node; the mobile terminal 10A will automatically acquire the interface service data in the target view node, and if only the data corresponding to the user name and the data corresponding to the comment score are acquired, taking the user comment interface 10B as an example, the data corresponding to the user name, which are 138 × 8742, 156 × 8482, and 137 × 0673, may be acquired, and the data corresponding to the comment score, which are 4 stars, 5 stars, and 3 stars, are acquired; and combining the interface service data into comment data of different forms according to the actual analysis requirements of the administrator.
The view area displayed in the user comment interface 10B corresponds to the view node in the node structure 10C in fig. 1 one to one, for example: a view area 10a in the user comment interface 10B corresponds to a view node 10 in the node structure 10C, a view area 101a in the user comment interface 10B corresponds to a view node 101 in the node structure 10C, a view area 102a in the user comment interface 10B corresponds to a view node 102 in the node structure 10C, and a view area 103a in the user comment interface 10B corresponds to a view node 103 in the node structure 10C; the view nodes comprise a root view node and a plurality of child view nodes, the view node 10 is the root view node, and the corresponding view interface is the integral interface of the user comment interface 10B; acquiring all child nodes of the root view node 10, namely view node 101, view node 102, view nodes 103 and …, view node 104, view node 105 and view node 106, wherein the view node 101 (namely view area 101a) contains detailed comment data of a user 138 × 8742, the view node 102 (namely view area 102a) contains detailed comment data of a user 156 × 8482, and the view node 103 (namely view area 103a) contains detailed comment data of a user 137 × 0673, as shown in the current screen of the user comment interface 10B; taking the user 138 × 8742 as an example, all child nodes in the view node 101, that is, the view node 1011, the view nodes 1012, …, and the view node 1013 are obtained, the view node 1011, the view nodes 1012, …, and the view node 1013 respectively store comment detailed data of the user, and the comment detailed data may include data such as a user avatar, a user name, a mobile terminal model, comment time, comment content, a comment score, an application version, and a communication situation with other users (including a comment value, text communication, and the like). After traversing the current screen of the user comment interface 10B, invoking an analog operation auxiliary function interface, such as invoking an action scroll forward auxiliary function interface (the function of which is to slide the node content downwards), automatically implementing an analog screen sliding operation downwards on the user comment interface 10B in the root view node 10, where the screen displays the non-traversed comment data in the user comment interface 10B after sliding.
The view resource identifier may be in the form of:
such as a user name, com # ##, id/detail _ comment _ user _ textview, where "#x" may represent the brand of the mobile terminal, "# # ###### # may represent an application market, an application store, or specific application software, etc.
The mobile terminal 10A may include a mobile phone, a tablet computer, a notebook computer, a palm computer, a Mobile Internet Device (MID), a Point Of Sale (POS) machine, a wearable device (e.g., a smart watch, a smart bracelet, etc.), or other terminal devices with application installation functions.
Please refer to fig. 2, which is a flowchart illustrating a data obtaining method according to an embodiment of the present application. As shown in fig. 2, the method may include the steps of:
step S101, obtaining comment inquiry information, wherein the comment inquiry information comprises first application information of a target application and second application information of an application to be inquired; the target application comprises comment data corresponding to a plurality of functional applications respectively, and the functional applications comprise the application to be inquired;
specifically, the mobile terminal 10A obtains first application information of a target application and second application information of an application to be queried, where the target application may include an application market, an application store, or specific application software, and the application to be queried may include an application in the application market or an applet in the specific application software; the first application information is a package name of the target application and is a unique identifier of the target application, namely one package name represents one target application, and the second application information is a package name of the application to be queried and is a unique identifier of the application to be queried.
Step S102, accessing a user comment interface corresponding to the application to be inquired based on the first application information and the second application information;
specifically, as can be seen from step S101, the first application information is a package name of the target application, and the package name of the application to be queried is obtained when the second application information is obtained, the specified package name is introduced by specifying the first application information and the second application information and using a start function, the target application is called according to the first application information, the user comment interface corresponding to the application to be queried is accessed in the target application according to the second application information, that is, the user comment interface corresponding to the specified package name is opened.
Step S103, traversing a plurality of view nodes associated with the user comment interface, and acquiring view resource identifiers of the view nodes;
specifically, the detailed layout information corresponding to the user comment interface is obtained through a page layout scanning tool in a software development kit in the mobile terminal, for example, a tool uiautomatorviewer in a software development kit in the android system, please refer to fig. 1 together, traverse all view nodes in the node structure 10C, and obtain view resource identifiers of all view nodes.
Step S104, determining a view node with a target view resource identifier in the plurality of view nodes as a target view node, and extracting interface service data in the target view node; the interface service data is comment data which is associated with a comment user in the user comment interface;
specifically, according to the actual analysis requirement of an administrator, determining a resource type corresponding to a target resource-id, assuming that a user name is the target resource type, first obtaining the resource-id of the user name, for example, in application market ABC, the resource-id corresponding to the user name is com.ABC.apparket, id/detail _ comment _ user _ client _ textview, respectively matching the resource-id corresponding to the user name with the resource-id corresponding to each view node, and according to the matching result, determining the view node having the user name resource identifier as the target view node; and acquiring a node data set corresponding to the target view node, extracting key field data corresponding to a user name from the node data set, and determining the data with the key field as the interface service data.
Obtaining comment query information in the embodiment of the application, wherein the comment query information comprises first application information of a target application and second application information of an application to be queried; the target application comprises comment data corresponding to a plurality of functional applications respectively, and the functional applications comprise the application to be inquired; accessing a user comment interface corresponding to the application to be inquired based on the first application information and the second application information; traversing a plurality of view nodes associated with the user comment interface, and acquiring view resource identifiers of the view nodes; determining a view node with a target view resource identifier as a target view node in the plurality of view nodes, and extracting interface service data in the target view node; the interface service data is comment data which is associated with a comment user in the user comment interface. Therefore, the user comment interface corresponding to the application to be inquired can be accessed by receiving the first application information of the target application and the second application information of the application to be inquired, then view resource identifiers of the view nodes are obtained through the view nodes on the user comment interface, and after the target view resource identifiers are determined, interface service data in the target view nodes can be crawled in a full-automatic mode, so that the collection efficiency of the user comment data in the application can be improved.
Please refer to fig. 3, which is a flowchart illustrating another data acquisition method according to an embodiment of the present application. As shown in fig. 3, the method may include the steps of:
s201, obtaining comment query information, wherein the comment query information comprises first application information of a target application and second application information of an application to be queried; the target application comprises comment data corresponding to a plurality of functional applications respectively, and the functional applications comprise the application to be inquired;
for a specific implementation process of step S201, reference may be made to the description of step S101 in the embodiment corresponding to fig. 2, which is not described herein again.
S202, reading the first application information and the second application information through a starting function;
specifically, the function of the start function is to transmit the first application information and the second application information, and convert the current interface of the mobile terminal into a user comment interface.
S203, the target application is called according to the first application information, and the user comment interface corresponding to the application to be inquired is accessed in the target application according to the second application information;
specifically, the first application information is a unique package name of the target application, and the second application information is a unique package name of the application to be queried, for example, a user comment interface of the application EF in the application market ABC is to be opened, and a user comment interface of the application market ABC accessing the application EF can be opened by specifying the package name of the application market ABC and the package name of the application EF.
S204, acquiring detailed layout information corresponding to the user comment interface through a page layout scanning tool;
specifically, the detailed data of the user comment can be clearly seen by the user comment interface obtained in step S203, but the administrator cannot directly obtain the target data, and needs to use a page layout scanning tool to scan and analyze the user comment interface to obtain corresponding detailed layout information, please refer to fig. 4 together, which is another scene schematic diagram for data acquisition provided in the embodiment of the present application. As shown in fig. 4, through the detailed layout information 20A corresponding to the user comment interface, the hierarchical relationship of the current page and the attribute of each control (view node) can be known.
S205, traversing the view nodes in the detailed layout information, and acquiring the view resource identifiers corresponding to the view nodes;
specifically, the view nodes include a root view node and a plurality of child view nodes; acquiring the root view node in the detailed layout information, acquiring a view resource identifier corresponding to the root view node, and calling the system auxiliary function interface to acquire a first sub-view node associated with the root view node through the view resource identifier corresponding to the root view node, wherein the first sub-view node corresponds to comment data displayed on a screen in the user comment interface; calling a simulation operation auxiliary function interface, performing simulation sliding operation on the user comment interface in the root view node through the simulation operation auxiliary function interface, and displaying non-traversed comment data in the user comment interface after sliding in the screen; calling the system auxiliary function interface to acquire a second child view node associated with the root view node; the second child view node corresponds to the non-traversed comment data in the user comment interface after sliding; and determining the first sub-view node and the second sub-view node as the plurality of sub-view nodes associated with the root view node, and acquiring view resource identifiers corresponding to the plurality of sub-view nodes respectively.
Referring to fig. 4 and fig. 5 together, fig. 5 is a schematic view of a scene of a simulated sliding screen according to an embodiment of the present application. The detailed layout information 20A in fig. 4 is consistent with the meaning represented by the node structure 10C in fig. 1, the view nodes may correspond to one another, and the detailed layout information 20A may correspond to the view area currently displayed on the screen of the user comment interface 10B in fig. 1; as shown in the detailed layout information 20A in fig. 4, the view node 10 is a root view node, the root view node 10 includes root view node 10 set data, the root view node 10 set data includes a child view node 101, a child view node 102, and a child view node 103, the child view node 101 includes view node 101 set data, similarly, the child view node 102 includes view node 102 set data, and the child view node 103 includes view node 103 set data; acquiring the view resource identifier of the root view node 10 in the detailed layout information 20A, calling a system auxiliary function Interface (such as an Application Programming Interface (API) Interface in an Android system) to acquire a first child view node associated with the view resource identifier of the root view node 10, that is, the child view node 101, the child view node 102, and the child view node 103; the first child view node corresponds to comment data displayed on the current screen in the user comment interface 10B; acquiring resource-id corresponding to the first sub-view node according to the first sub-view node; after traversing the detailed layout information 20A, calling a simulation operation auxiliary function interface, as shown in fig. 5, implementing a simulation downward screen sliding operation on the user comment interface 10B in the root view node 10, and automatically acquiring an undisplayed view area (unretraversed comment data) in the user comment interface 10B, for example, a view area 104a, a view area 105a, and a view area 106a in the user comment interface 10B after the screen sliding; obtaining detailed layout information 200A corresponding to a user comment interface 10B after the screen is slid through a page layout scanning tool, wherein a view area 104a in the user comment interface 10B after the screen is slid corresponds to a child view node 104 in the detailed layout information 200A, a view area 105a corresponds to a child view node 105 in the detailed layout information 200A, and a view area 106a corresponds to a child view node 106 in the detailed layout information 200A (that is, an undisplayed view area in the user comment interface 10B corresponds to a second child view node associated with the root view node 10); and acquiring resource-id corresponding to the second sub-view node according to the second sub-view node.
S206, inputting the target view resource identifier; respectively matching the target view resource identifier with the view resource identifier corresponding to each view node, and determining the view node with the target view resource identifier as the target view node according to the matching result; wherein the view resource type corresponding to the target view resource identification comprises at least one of: user name, user model, comment date, comment content and application score;
specifically, according to the actual analysis user comment data requirement of the administrator, a target resource-id is input, for example, a user name, a user model, a comment date and comment content in user comment data of an application EF are queried in an application market ABC, and then the resource-id corresponding to the target data is input, as follows:
user name: abc, app key id/detail _ comment _ user _ textview,
the user machine type: abc, app key id/detail _ comment _ user _ client _ textview,
date of review: abc, app key id/detail _ comment _ time _ textview,
and (4) comment content: abc, app key id/detail _ comment _ content _ textview.
S207, acquiring a node data set corresponding to the target view node; extracting data with text key fields from the node data set, and determining the data with the text key fields as the interface service data;
as can be seen from the detailed layout information 20A in fig. 4, the user comment detailed data is implemented in a tree node form or a list form, and by acquiring data of a root node in the list, data of all child nodes that are desired to be searched under the root node is searched, and content in the node is extracted.
Specifically, please refer to fig. 4, assuming that the user name is the target data, the child view node 10111 is the target child view node, and a node data set 201A corresponding to the target child view node 10111 is obtained; the node data set 201A may include an index of a current view node, a resource identifier resource-id, a text key field text, a class, a node range bound, and the like; interface business data, namely data 134 with text key fields, 6514 are extracted in node data set 201A.
In fig. 4, by expanding the sub-view node 101, the sub-view nodes 1011,. said.,. 1012 contained in the sub-view node 101 and the sub-view nodes contained in the sub-view node thereof can be clearly known, and the node data sets contained in the sub-view node 101 can also be clearly known, wherein the sub-view node 102 and the sub-view node 103 are not expanded in fig. 4, but the sub-view node 102 and the sub-view node 103 also contain the corresponding sub-view nodes and node data sets, which is not described herein again.
In summary, steps S201 to S207 are specific descriptions of steps S101 to S104 in the embodiment corresponding to fig. 2.
S208, combining the interface service data belonging to the same comment user to obtain comment data corresponding to the comment user in the user comment interface; or combining the interface service data belonging to the same target view resource identifier to obtain comment data associated with each target view resource identifier.
Specifically, please refer to fig. 6a together, which is a schematic diagram of a method for combining comment data according to an embodiment of the present application. When a technician wants to know detailed comment data of an application by a user, for example, when the technician wants to know the reason for giving a poor comment to a user, the interface service data of the same user can be combined in the mode of fig. 6a, so that the reason for poor user experience can be known, the appeal point of the user can be known by combing the comments of the user, and the requirements of the user can be met as much as possible.
Or please refer to fig. 6b together, which is a schematic diagram of another method for combining comment data provided in the embodiment of the present application. When a technician wants to know the detailed situation of certain interface service data, the specific interface service data of different users can be combined in the mode of fig. 6b, for example, when the application versions which are popular with a great number of users are to be analyzed, the application versions, comment contents and comment scores in the user comment detailed data can be independently obtained, and after the interface service data are combined for comprehensive analysis, the defects in the functions of the favorite application versions and part of the favorite application versions of the users can be known, so that a solution can be provided more quickly, and the defects can be converged.
Obtaining comment query information in the embodiment of the application, wherein the comment query information comprises first application information of a target application and second application information of an application to be queried; the target application comprises comment data corresponding to a plurality of functional applications respectively, and the functional applications comprise the application to be inquired; reading the first application information and the second application information through a starting function; calling the target application according to the first application information, and accessing the user comment interface corresponding to the application to be inquired in the target application according to the second application information; acquiring detailed layout information corresponding to the user comment interface through a page layout scanning tool; traversing the view nodes in the detailed layout information to acquire the view resource identifiers corresponding to the view nodes; inputting the target view resource identification; respectively matching the target view resource identifier with the view resource identifier corresponding to each view node, and determining the view node with the target view resource identifier as the target view node according to the matching result; wherein the view resource type corresponding to the target view resource identification comprises at least one of: user name, user model, comment date, comment content and application score; combining interface service data belonging to the same comment user to obtain comment data corresponding to the comment user in the user comment interface; or combining the interface service data belonging to the same target view resource identifier to obtain comment data associated with each target view resource identifier. Therefore, the user comment interface corresponding to the application to be inquired can be accessed by receiving the first application information of the target application and the second application information of the application to be inquired, then view resource identifiers of the view nodes are obtained through the view nodes on the user comment interface, and after the target view resource identifiers are determined, interface service data in the target view nodes can be crawled in a full-automatic mode, so that the collection efficiency of the user comment data in the application can be improved.
Please refer to fig. 7, which is a flowchart illustrating another data acquisition method according to an embodiment of the present application. As shown in fig. 7, a start function and comment query information are input in the mobile terminal, and the current interface of the mobile terminal jumps to a user comment interface; scanning and analyzing a user comment interface through a page layout scanning tool in the mobile terminal, acquiring detailed layout information corresponding to the user comment interface, traversing a plurality of view nodes in the detailed layout information, and acquiring view resource identifiers corresponding to the view nodes; calling an auxiliary function interface of a system to acquire a node data set on a corresponding view node through the view resource identifier of each view node, wherein the node data set comprises the view resource identifier of the current view node, an index in the whole layout, key field data and the like; inputting a target view resource identifier, respectively matching the target view resource identifier with a view resource identifier corresponding to each view node, and determining the view node with the target view resource identifier as the target view node according to a matching result; and acquiring a node data set corresponding to the target view node, extracting key field data corresponding to the target view resource identifier from the node data set, and determining the data with the key field as the interface service data. For a specific implementation process, reference may be made to the description of step S201 to step S207 in the embodiment corresponding to fig. 3, which is not described herein again.
Fig. 8 is a schematic structural diagram of a computer device according to an embodiment of the present application. As shown in fig. 8, the computer apparatus 1 may include: the system comprises a first acquisition module 11, an access module 12, a second acquisition module 13, a determination module 14 and an extraction module 15;
the first obtaining module 11 is configured to obtain comment query information, where the comment query information includes first application information of a target application and second application information of an application to be queried; the target application comprises comment data corresponding to a plurality of functional applications respectively, and the functional applications comprise the application to be inquired;
the access module 12 is configured to access a user comment interface corresponding to the application to be queried based on the first application information and the second application information;
the second obtaining module 13 is configured to traverse a plurality of view nodes associated with the user comment interface, and obtain view resource identifiers of the view nodes;
a determining module 14, configured to determine, as a target view node, a view node with a target view resource identifier in the multiple view nodes;
the extracting module 15 is configured to extract interface service data in the target view node; the interface service data is comment data which is associated with a comment user in the user comment interface;
for specific functional implementation manners of the first obtaining module 11, the accessing module 12, the second obtaining module 13, the determining module 14, and the extracting module 15, reference may be made to steps S101 to S104 in the corresponding embodiment of fig. 2, which is not described herein again.
Referring again to fig. 8, the computer apparatus 1 may further include: a first assembling module 16 and a second assembling module 17;
the first combination module 16 is configured to combine interface service data belonging to the same comment user to obtain comment data corresponding to the comment user in the user comment interface; alternatively, the first and second electrodes may be,
the second combination module 17 is configured to combine interface service data belonging to the same target view resource identifier to obtain comment data associated with each target view resource identifier;
for specific functional implementation of the first combination module 16 and the second combination module 17, reference may be made to step S208 in the embodiment corresponding to fig. 3, which is not described herein again.
Referring again to fig. 8, the access module 12 may include: a reading unit 121, an access unit 122;
a reading unit 121, configured to read the first application information and the second application information through a start function;
the access unit 122 is configured to invoke the target application according to the first application information, and access the user comment interface corresponding to the application to be queried in the target application according to the second application information;
for specific functional implementation manners of the reading unit 121 and the accessing unit 122, refer to step S202 to step S203 in the corresponding embodiment of fig. 3, which is not described herein again.
Referring again to fig. 8, the second obtaining module 13 may include: an acquisition information unit 131 and an acquisition identification unit 132;
an obtaining information unit 131, configured to obtain detailed layout information corresponding to the user comment interface through a page layout scanning tool;
an obtaining identification unit 132, configured to traverse the multiple view nodes in the detailed layout information, and obtain the view resource identifiers corresponding to the multiple view nodes;
the specific functional implementation manners of the information obtaining unit 131 and the identification obtaining unit 132 may refer to step S204 to step S205 in the corresponding embodiment of fig. 2, which is not described herein again.
Referring to fig. 8 again, the acquiring identification unit 132 may include: a first acquisition node subunit 1321, a first acquisition identifier subunit 1322, a second acquisition node subunit 1323, and a second acquisition identifier subunit 1324;
a first obtaining node subunit 1321, configured to obtain the root view node in the detailed layout information;
a first obtaining identifier subunit 1322, configured to obtain a view resource identifier corresponding to the root view node;
a second obtaining node subunit 1323, configured to invoke a system auxiliary function interface to obtain the multiple sub-view nodes associated with the root view node through the view resource identifier corresponding to the root view node;
a second obtaining identifier subunit 1324, configured to obtain view resource identifiers corresponding to the multiple sub-view nodes, respectively;
for specific implementation of functions of the first obtaining node subunit 1321, the first obtaining identifier subunit 1322, the second obtaining node subunit 1323, and the second obtaining identifier subunit 1324, reference may be made to step S205 in the embodiment corresponding to fig. 3, which is not described herein again.
Referring again to FIG. 8, the second acquisition node sub-unit 1323 may include a first acquisition sub-node sub-unit 13231, a simulated sliding sub-unit 13232, a second acquisition sub-node sub-unit 13233, and a determination sub-unit 13234.
A first obtaining child node subunit 13231, configured to invoke the system auxiliary function interface to obtain a first child view node associated with the root view node through the view resource identifier corresponding to the root view node; the first child view node corresponds to comment data displayed on a screen in the user comment interface;
the simulation sliding subunit 13232 is configured to invoke a simulation operation auxiliary function interface, perform a simulation sliding operation on the user comment interface in the root view node through the simulation operation auxiliary function interface, and display non-traversed comment data in the user comment interface after the sliding operation in the screen;
a second obtain child node subunit 13233, configured to invoke the system accessibility interface to obtain a second child view node associated with the root view node; the second child view node corresponds to the non-traversed comment data in the user comment interface after sliding;
a determining subunit 13234, configured to determine the first child view node and the second child view node as the plurality of child view nodes associated with the root view node.
The specific functional implementation manners of the first obtaining sub-node sub-unit 13231, the simulated sliding sub-unit 13232, the second obtaining sub-node sub-unit 13233, and the determining sub-unit 13234 may refer to step S205 in the embodiment corresponding to fig. 3, and are not described herein again.
Referring again to fig. 8, the determining module 14 may include: input unit 141, and determination node unit 142.
An input unit 141, configured to input the target view resource identifier;
a node determining unit 142, configured to match the target view resource identifier with the view resource identifier corresponding to each view node, and determine, according to a matching result, the view node having the target view resource identifier as the target view node;
wherein the view resource type corresponding to the target view resource identification comprises at least one of: user name, user model, review date, review content, and application rating.
The specific functional implementation manners of the input unit 141 and the node determining unit 142 may refer to step S206 in the embodiment corresponding to fig. 3, which is not described herein again.
Referring again to fig. 8, the extraction module 15 may include: an acquisition aggregation unit 151 and a determination data unit 152.
An acquiring set unit 151, configured to acquire a node data set corresponding to the target view node;
a determining data unit 152, configured to extract data with text key fields from the node data set, and determine the data with text key fields as the interface service data.
For specific functional implementation of the acquiring set unit 151 and the determining data unit 152, reference may be made to step S207 in the embodiment corresponding to fig. 3, which is not described herein again.
Obtaining comment query information in the embodiment of the application, wherein the comment query information comprises first application information of a target application and second application information of an application to be queried; the target application comprises comment data corresponding to a plurality of functional applications respectively, and the functional applications comprise the application to be inquired; accessing a user comment interface corresponding to the application to be inquired based on the first application information and the second application information; traversing a plurality of view nodes associated with the user comment interface, and acquiring view resource identifiers of the view nodes; determining a view node with a target view resource identifier as a target view node in the plurality of view nodes, and extracting interface service data in the target view node; the interface service data is comment data which is associated with a comment user in the user comment interface. Therefore, the user comment interface corresponding to the application to be inquired can be accessed by receiving the first application information of the target application and the second application information of the application to be inquired, then view resource identifiers of the view nodes are obtained through the view nodes on the user comment interface, and after the target view resource identifiers are determined, interface service data in the target view nodes can be crawled in a full-automatic mode, so that the collection efficiency of the user comment data in the application can be improved.
Fig. 9 is a schematic structural diagram of an electronic device according to an embodiment of the present application. As shown in fig. 9, the electronic device 1000 may include: the processor 1001, the network interface 1004, and the memory 1005, the electronic device 1000 may further include: a user interface 1003, and at least one communication bus 1002. Wherein a communication bus 1002 is used to enable connective communication between these components. The user interface 1003 may include a Display screen (Display) and a Keyboard (Keyboard), and the optional user interface 1003 may also include a standard wired interface and a standard wireless interface. The network interface 1004 may optionally include a standard wired interface, a wireless interface (e.g., WI-FI interface). The memory 1005 may be a high-speed RAM memory or a non-volatile memory (non-volatile memory), such as at least one disk memory. The memory 1005 may optionally be at least one memory device located remotely from the processor 1001. As shown in fig. 9, a memory 1005, which is a kind of computer-readable storage medium, may include therein an operating system, a network communication module, a user interface module, and a device control application program.
In the electronic device 1000 shown in fig. 9, the network interface 1004 may provide a network communication function; the user interface 1003 is an interface for providing a user with input; and the processor 1001 may be used to invoke a device control application stored in the memory 1005 to implement:
obtaining comment query information, wherein the comment query information comprises first application information of a target application and second application information of an application to be queried; the target application comprises comment data corresponding to a plurality of functional applications respectively, and the functional applications comprise the application to be inquired;
accessing a user comment interface corresponding to the application to be inquired based on the first application information and the second application information;
traversing a plurality of view nodes associated with the user comment interface, and acquiring view resource identifiers of the view nodes;
determining a view node with a target view resource identifier as a target view node in the plurality of view nodes, and extracting interface service data in the target view node; the interface service data is comment data which is associated with a comment user in the user comment interface.
In one embodiment, the processor 1001 further performs the following specific steps:
combining interface service data belonging to the same comment user to obtain comment data corresponding to the comment user in the user comment interface;
or combining the interface service data belonging to the same target view resource identifier to obtain the comment data associated with each target view resource identifier.
In an embodiment, when the processor 1001 accesses the user comment interface corresponding to the application to be queried based on the first application information and the second application information, the following steps are specifically performed:
reading the first application information and the second application information through a starting function;
and calling the target application according to the first application information, and accessing the user comment interface corresponding to the application to be inquired in the target application according to the second application information.
In an embodiment, when the processor 1001 executes traversal of a plurality of view nodes associated with the user comment interface and acquires view resource identifiers of the view nodes, the following steps are specifically executed:
acquiring detailed layout information corresponding to the user comment interface through a page layout scanning tool;
and traversing the view nodes in the detailed layout information to acquire the view resource identifiers corresponding to the view nodes.
In one embodiment, the plurality of view nodes comprises a root view node and a plurality of child view nodes;
when the processor 1001 executes traversal of the plurality of view nodes in the detailed layout information and acquires the view resource identifiers corresponding to the plurality of view nodes, the following steps are specifically executed:
acquiring the root view node in the detailed layout information;
acquiring a view resource identifier corresponding to the root view node;
calling a system auxiliary function interface to acquire the plurality of child view nodes associated with the root view node through the view resource identifier corresponding to the root view node;
and acquiring view resource identifiers corresponding to the multiple child view nodes respectively.
In an embodiment, when the processor 1001 executes the view resource identifier corresponding to the root view node and calls a system auxiliary function interface to obtain the multiple child view nodes associated with the root view node, the following steps are specifically executed:
calling the system auxiliary function interface to acquire a first child view node associated with the root view node through the view resource identifier corresponding to the root view node; the first child view node corresponds to comment data displayed on a screen in the user comment interface;
calling a simulation operation auxiliary function interface, performing simulation sliding operation on the user comment interface in the root view node through the simulation operation auxiliary function interface, and displaying non-traversed comment data in the user comment interface after sliding in the screen;
calling the system auxiliary function interface to acquire a second child view node associated with the root view node; the second child view node corresponds to the non-traversed comment data in the user comment interface after sliding;
determining the first child view node and the second child view node as the plurality of child view nodes associated with the root view node.
In an embodiment, when the processor 1001 determines, as a target view node, a view node having a target view resource identifier in the view nodes, specifically performs the following steps:
inputting the target view resource identification;
respectively matching the target view resource identifier with the view resource identifier corresponding to each view node, and determining the view node with the target view resource identifier as the target view node according to the matching result;
wherein the view resource type corresponding to the target view resource identification comprises at least one of: user name, user model, comment date, comment content, application score, and the like.
In an embodiment, when the processor 1001 extracts the interface service data in the target view node, the following steps are specifically performed:
acquiring a node data set corresponding to the target view node;
and extracting data with text key fields from the node data set, and determining the data with the text key fields as the interface service data.
Obtaining comment query information in the embodiment of the application, wherein the comment query information comprises first application information of a target application and second application information of an application to be queried; the target application comprises comment data corresponding to a plurality of functional applications respectively, and the functional applications comprise the application to be inquired; accessing a user comment interface corresponding to the application to be inquired based on the first application information and the second application information; traversing a plurality of view nodes associated with the user comment interface, and acquiring view resource identifiers of the view nodes; determining a view node with a target view resource identifier as a target view node in the plurality of view nodes, and extracting interface service data in the target view node; the interface service data is comment data which is associated with a comment user in the user comment interface. Therefore, the user comment interface corresponding to the application to be inquired can be accessed by receiving the first application information of the target application and the second application information of the application to be inquired, then view resource identifiers of the view nodes are obtained through the view nodes on the user comment interface, and after the target view resource identifiers are determined, interface service data in the target view nodes can be crawled in a full-automatic mode, so that the collection efficiency of the user comment data in the application can be improved.
It should be understood that the electronic device 1000 described in this embodiment of the application may perform the description of the data obtaining method in the embodiments corresponding to fig. 1 to fig. 7, and may also perform the description of the computer device 1 in the embodiment corresponding to fig. 8, which is not described herein again. In addition, the beneficial effects of the same method are not described in detail.
Further, here, it is to be noted that: an embodiment of the present application further provides a computer-readable storage medium, where a computer program executed by the aforementioned computer device 1 is stored in the computer-readable storage medium, and the computer program includes program instructions, and when the processor executes the program instructions, the description of the data acquisition method in the embodiment corresponding to fig. 1 to 7 can be executed, so that details are not repeated here. In addition, the beneficial effects of the same method are not described in detail. For technical details not disclosed in embodiments of the computer-readable storage medium referred to in the present application, reference is made to the description of embodiments of the method of the present 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 can be implemented by a computer program, which can be stored in a computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. The readable storage medium may be a magnetic disk, an optical disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), or the like.
The above disclosure is only for the purpose of illustrating the preferred embodiments of the present application and is not to be construed as limiting the scope of the present application, so that the present application is not limited thereto, and all equivalent variations and modifications can be made to the present application.
Claims (10)
1. A method of data acquisition, comprising:
obtaining comment query information, wherein the comment query information comprises first application information of a target application and second application information of an application to be queried; the target application comprises comment data corresponding to a plurality of functional applications respectively, and the functional applications comprise the application to be inquired;
accessing a user comment interface corresponding to the application to be inquired based on the first application information and the second application information;
traversing a plurality of view nodes associated with the user comment interface, and acquiring view resource identifiers of the view nodes;
determining a view node with a target view resource identifier as a target view node in the plurality of view nodes, and extracting interface service data in the target view node; the interface service data is comment data which is associated with a comment user in the user comment interface.
2. The method of claim 1, further comprising:
combining interface service data belonging to the same comment user to obtain comment data corresponding to the comment user in the user comment interface; alternatively, the first and second electrodes may be,
and combining the interface service data belonging to the same target view resource identifier to obtain comment data associated with each target view resource identifier.
3. The method of claim 1, wherein accessing a user comment interface corresponding to the application to be queried based on the first application information and the second application information comprises:
reading the first application information and the second application information through a starting function;
and calling the target application according to the first application information, and accessing the user comment interface corresponding to the application to be inquired in the target application according to the second application information.
4. The method of claim 1, wherein traversing a plurality of view nodes associated with the user comment interface, obtaining view resource identifications for the plurality of view nodes, comprises:
acquiring detailed layout information corresponding to the user comment interface through a page layout scanning tool;
and traversing the view nodes in the detailed layout information to acquire the view resource identifiers corresponding to the view nodes.
5. The method of claim 4, wherein the plurality of view nodes comprises a root view node and a plurality of child view nodes;
the traversing the view nodes in the detailed layout information to obtain the view resource identifiers corresponding to the view nodes includes:
acquiring the root view node in the detailed layout information;
acquiring a view resource identifier corresponding to the root view node;
calling a system auxiliary function interface to acquire the plurality of child view nodes associated with the root view node through the view resource identifier corresponding to the root view node;
and acquiring view resource identifiers corresponding to the multiple child view nodes respectively.
6. The method according to claim 5, wherein said invoking a system accessibility interface to obtain the plurality of child view nodes associated with the root view node via the view resource identifier corresponding to the root view node comprises:
calling the system auxiliary function interface to acquire a first child view node associated with the root view node through the view resource identifier corresponding to the root view node; the first child view node corresponds to comment data displayed on a screen in the user comment interface;
calling a simulation operation auxiliary function interface, performing simulation sliding operation on the user comment interface in the root view node through the simulation operation auxiliary function interface, and displaying non-traversed comment data in the user comment interface after sliding in the screen;
calling the system auxiliary function interface to acquire a second child view node associated with the root view node; the second child view node corresponds to the non-traversed comment data in the user comment interface after sliding;
determining the first child view node and the second child view node as the plurality of child view nodes associated with the root view node.
7. The method of claim 1, wherein determining a view node with a target view resource identifier among the plurality of view nodes as a target view node comprises:
inputting the target view resource identification;
respectively matching the target view resource identifier with the view resource identifier corresponding to each view node, and determining the view node with the target view resource identifier as the target view node according to the matching result;
wherein the view resource type corresponding to the target view resource identification comprises at least one of: user name, user model, review date, review content, and application rating.
8. The method of claim 1, wherein the extracting interface traffic data in the target view node comprises:
acquiring a node data set corresponding to the target view node;
and extracting data with text key fields from the node data set, and determining the data with the text key fields as the interface service data.
9. A computer device comprising a memory and a processor, the memory storing a computer program that, when executed by the processor, causes the processor to perform the steps of the method according to any one of claims 1 to 8.
10. A computer-readable storage medium, characterized in that the computer-readable storage medium stores a computer program comprising program instructions which, when executed by a processor, perform the steps of the method according to any one of claims 1 to 8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911097201.7A CN112784132A (en) | 2019-11-11 | 2019-11-11 | Data acquisition method and device and computer storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911097201.7A CN112784132A (en) | 2019-11-11 | 2019-11-11 | Data acquisition method and device and computer storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112784132A true CN112784132A (en) | 2021-05-11 |
Family
ID=75750066
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911097201.7A Pending CN112784132A (en) | 2019-11-11 | 2019-11-11 | Data acquisition method and device and computer storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112784132A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117707453A (en) * | 2023-08-15 | 2024-03-15 | 荣耀终端有限公司 | Method, equipment and storage medium for reading node information |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20120215798A1 (en) * | 2011-02-18 | 2012-08-23 | International Business Machines Corporation | System and Method for a Centralized URL Commenting Service Enabling Metadata Aggregation |
| CN102999610A (en) * | 2012-11-22 | 2013-03-27 | 用友软件股份有限公司 | Data access system and data access method |
| CN103150307A (en) * | 2011-12-06 | 2013-06-12 | 株式会社理光 | Method and equipment for searching name related to thematic word from network |
| CN104205086A (en) * | 2012-03-19 | 2014-12-10 | 阿尔卡特朗讯 | Method of modifying access control for WEB services using query languages |
| CN106407371A (en) * | 2016-09-09 | 2017-02-15 | 广州神马移动信息科技有限公司 | User comment data displaying method and system, server and client |
| US20170206065A1 (en) * | 2014-09-23 | 2017-07-20 | Quixey, Inc. | Entity-Based External Functionality for Software Developers |
| CN107833055A (en) * | 2017-10-19 | 2018-03-23 | 广东欧珀移动通信有限公司 | Comment processing method and equipment |
-
2019
- 2019-11-11 CN CN201911097201.7A patent/CN112784132A/en active Pending
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20120215798A1 (en) * | 2011-02-18 | 2012-08-23 | International Business Machines Corporation | System and Method for a Centralized URL Commenting Service Enabling Metadata Aggregation |
| CN103150307A (en) * | 2011-12-06 | 2013-06-12 | 株式会社理光 | Method and equipment for searching name related to thematic word from network |
| CN104205086A (en) * | 2012-03-19 | 2014-12-10 | 阿尔卡特朗讯 | Method of modifying access control for WEB services using query languages |
| CN102999610A (en) * | 2012-11-22 | 2013-03-27 | 用友软件股份有限公司 | Data access system and data access method |
| US20170206065A1 (en) * | 2014-09-23 | 2017-07-20 | Quixey, Inc. | Entity-Based External Functionality for Software Developers |
| CN106407371A (en) * | 2016-09-09 | 2017-02-15 | 广州神马移动信息科技有限公司 | User comment data displaying method and system, server and client |
| CN107833055A (en) * | 2017-10-19 | 2018-03-23 | 广东欧珀移动通信有限公司 | Comment processing method and equipment |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117707453A (en) * | 2023-08-15 | 2024-03-15 | 荣耀终端有限公司 | Method, equipment and storage medium for reading node information |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111045655B (en) | Page rendering method and device, rendering server and storage medium | |
| CN108399072B (en) | Application page updating method and device | |
| CN110798501B (en) | Data processing method and device and readable storage medium | |
| CN102930017B (en) | A kind of method and apparatus for providing Search Results on mobile terminals | |
| TWI798652B (en) | A method and system for automatically generating a data collection module | |
| CN109191158B (en) | Processing method and processing equipment for user portrait label data | |
| CN106470110B (en) | Method and device for sending messages to multiple users in user list in group mode | |
| CN111488186B (en) | Data processing method, device, electronic equipment and computer storage medium | |
| US20150081278A1 (en) | Electronic device, character conversion method, and storage medium | |
| CN110166499A (en) | A kind of method and server obtaining user's representation data | |
| CN112925520A (en) | Method and device for building visual page and computer equipment | |
| CN108664665A (en) | Data format method for transformation, device, equipment and readable storage medium storing program for executing | |
| CN110705226A (en) | Spreadsheet creating method and device and computer equipment | |
| CN111240669A (en) | Interface generation method and device, electronic equipment and computer storage medium | |
| CN111880813B (en) | Method for realizing android card UI (user interface) and storage medium | |
| CN112667120A (en) | Display method and device of interactive icon and electronic equipment | |
| CN109683760B (en) | Recent content display method, device, terminal and storage medium | |
| CN106682014B (en) | Game display data generation method and device | |
| CN112286486B (en) | Operation method of application program on intelligent terminal, intelligent terminal and storage medium | |
| CN112784132A (en) | Data acquisition method and device and computer storage medium | |
| CN109740074B (en) | Method, device and equipment for processing parameter configuration information | |
| JP2019101889A (en) | Test execution device and program | |
| CN113794930B (en) | Video generation method, device, equipment and storage medium | |
| CN107168687B (en) | Method and equipment for setting game instruction macro | |
| CN112001929B (en) | Picture asset processing method and device, storage medium and electronic device |
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 |