CN113691610B - Data acquisition method and device, electronic equipment and storage medium - Google Patents
Data acquisition method and device, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN113691610B CN113691610B CN202110963350.8A CN202110963350A CN113691610B CN 113691610 B CN113691610 B CN 113691610B CN 202110963350 A CN202110963350 A CN 202110963350A CN 113691610 B CN113691610 B CN 113691610B
- Authority
- CN
- China
- Prior art keywords
- service data
- server
- service
- identifier
- client
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 88
- 230000008569 process Effects 0.000 abstract description 23
- 230000006870 function Effects 0.000 description 9
- 238000004891 communication Methods 0.000 description 8
- 238000012545 processing Methods 0.000 description 8
- 238000010586 diagram Methods 0.000 description 7
- 230000008859 change Effects 0.000 description 4
- 230000004044 response Effects 0.000 description 4
- 238000001514 detection method Methods 0.000 description 3
- 230000003044 adaptive effect Effects 0.000 description 1
- 238000013459 approach Methods 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 238000006243 chemical reaction Methods 0.000 description 1
- 238000004590 computer program Methods 0.000 description 1
- 230000008878 coupling Effects 0.000 description 1
- 238000010168 coupling process Methods 0.000 description 1
- 238000005859 coupling reaction Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000009877 rendering Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/14—Session management
- H04L67/146—Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The embodiment of the application discloses a data acquisition method, a data acquisition device, electronic equipment and a storage medium. The method comprises the following steps: the method comprises the steps that a client side establishes connection with a server side, a designated identifier is stored in the server side, the designated identifier is used for identifying first service data in the server side, and the first service data are fixed service data; if the first service data which are acquired from the server based on the specified identifier in advance are stored locally, acquiring the second service data from the server based on the specified identifier; and taking the second service data and the local first service data as the service data corresponding to the acquired service end. Therefore, the client can acquire the first service data in advance through the appointed identification stored in the server to be stored locally, and then in the process of acquiring the service data corresponding to the server every time later, the client can acquire the second service data only through the appointed identification corresponding to the server, so that the efficiency of acquiring the service data from the server is improved.
Description
Technical Field
The present disclosure relates to the field of communications technologies, and in particular, to a data acquisition method, apparatus, electronic device, and storage medium.
Background
In some scenarios, a client needs to acquire a service provided in a server before using the service provided in the server. For example, in communications based on the GATT (Generic Attribute Profile) protocol, the GATT client needs to initiate a service discovery procedure to the GATT server to discover service data in the GATT server. However, there is still a problem in the related service acquisition that efficiency is to be improved.
Disclosure of Invention
In view of the above, the present application proposes a data acquisition method, apparatus, electronic device, and storage medium, so as to achieve improvement of the above problem.
In a first aspect, the present application provides a data acquisition method, applied to a client, where the method includes: the client establishes connection with a server, and the server stores a designated identifier, wherein the designated identifier is used for identifying first service data in the server, and the first service data is fixed service data; if the first service data which are acquired from the service end based on the specified identification in advance are stored locally, acquiring second service data from the service end based on the specified identification, wherein the second service data are service data except the first service data in the service end; and taking the second service data and the local first service data as the acquired service data of the service end.
In a second aspect, the present application provides a data acquisition method, applied to a server, where the method includes: the method comprises the steps that a connection is established between a server and a client, a designated identifier is stored in the server, the designated identifier is used for identifying first service data in the server, and the first service data are fixed service data; the method comprises the steps that second service data are acquired from a server in response to an acquisition request which is sent by a client and corresponds to the specified identifier, wherein the acquisition request is sent after the client determines that first service data which are acquired from the server in advance based on the specified identifier are locally stored; and sending the second service data to the client, so that the client can take the second service data and the local first service data as the acquired service data of the server.
In a third aspect, the present application provides a data acquisition method, running on a client, where the apparatus includes: the connection management unit is used for establishing connection with a service end, wherein a specified identifier is stored in the service end and used for identifying first service data in the service end, and the first service data is fixed service data; the first data acquisition unit is used for acquiring second service data from the service end based on the specified identifier if the first service data which is acquired from the service end based on the specified identifier in advance is locally stored, wherein the second service data is the service data except the first service data in the service end; and the second data acquisition unit is used for taking the second service data and the local first service data as the acquired service data of the service end.
In a fourth aspect, the present application provides a data acquisition method, running on a server, where the apparatus includes: the connection management unit is used for establishing connection with the client, wherein the server stores a specified identifier, the specified identifier is used for identifying first service data in the server, and the first service data is fixed service data; the data searching unit is used for responding to an acquisition request which is sent by the client and corresponds to the specified identifier, acquiring second service data from the server, wherein the acquisition request is sent after the client determines that the first service data which is acquired from the server based on the specified identifier in advance is locally stored; and the data sending unit is used for sending the second service data to the client, so that the client can take the second service data and the local first service data as the acquired service data of the server.
In a fifth aspect, the present application provides an electronic device comprising one or more processors and a memory; one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs configured to perform the methods described above.
In a sixth aspect, the present application provides a computer readable storage medium having program code stored therein, wherein the method described above is performed when the program code is run.
After a connection is established between a client and a server, the client further determines whether first service data acquired from the server based on the specified identifier is stored in advance, if so, service data (second service data) except the first service data in the server are acquired from the server directly based on the specified identifier, so that the second service data and the local first service data are used as acquired service data of the server.
Therefore, under the condition that the service data are divided into the first service data and the second service data by the service end, the client can obtain the first service data from the service end in advance to be stored locally, then in the process of obtaining the service data corresponding to the service end every time later, the client can only obtain the second service data by using the appointed mark corresponding to the service end, and further the data quantity of data obtaining from the service end in the process of obtaining the service data every time is reduced, and the efficiency of obtaining the service data from the service end is improved.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are needed in the description of the embodiments will be briefly introduced below, it being obvious that the drawings in the following description are only some embodiments of the present application, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
Fig. 1 is a schematic diagram of an application scenario of a data acquisition method according to an embodiment of the present application;
fig. 2 is a schematic diagram of another application scenario of a data acquisition method according to an embodiment of the present application;
FIG. 3 is a flowchart of a data acquisition method according to an embodiment of the present application;
fig. 4 is a schematic diagram of service data stored by a service end in an embodiment of the present application;
FIG. 5 is a flow chart illustrating a method for data acquisition according to another embodiment of the present application;
FIG. 6 is a flowchart of a data acquisition method according to a further embodiment of the present application;
FIG. 7 is a flowchart of a data acquisition method according to yet another embodiment of the present application;
FIG. 8 is a flowchart of a data acquisition method according to yet another embodiment of the present application;
FIG. 9 is a flowchart of a data acquisition method according to yet another embodiment of the present application;
fig. 10 shows a block diagram of a data acquisition device according to an embodiment of the present application;
FIG. 11 is a block diagram showing a data acquisition apparatus according to still another embodiment of the present application;
FIG. 12 shows a block diagram of an electronic device as proposed herein;
fig. 13 is a storage unit for storing or carrying program code for implementing the data acquisition method according to the 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. All other embodiments, which can be made by one of ordinary skill in the art based on the embodiments herein without making any inventive effort, are intended to be within the scope of the present application.
In general, in order to provide services to another electronic device, a service terminal may be configured in the electronic device, and a client terminal that may establish a connection with the service terminal is established in the other electronic device. Before the client uses the service provided in the server, the client needs to acquire the service provided in the server. For example, in communications based on the GATT (Generic Attribute Profile) protocol, the GATT client needs to initiate a service discovery procedure to the GATT server to discover service data in the GATT server, so as to obtain services that can be provided by the GATT server.
However, the inventors have found in the study that there is still a problem in that efficiency is to be improved in the related service data acquisition manner. For example, the inventor finds that if the client detects that no trust relationship is established between the client and the server connected after the client establishes a connection with the server, the client initiates a service data discovery procedure to obtain all service data in the server. That is, under the condition that the trust relationship is not established, in each service data acquisition process, the client acquires all the service data in the service end once, so that the service data acquisition process consumes longer time, and further the efficiency is affected.
Therefore, in order to improve the above-mentioned problem, the inventor proposes a data acquisition method, a device, an electronic apparatus and a storage medium provided by the present application, by acquiring a first service data specified identifier in an identifier service terminal from a service terminal, further determining whether first service data acquired from the service terminal based on the specified identifier is already stored locally in advance, and if so, acquiring service data (second service data) of the service terminal other than the first service data from the service terminal directly based on the specified identifier, so as to use the second service data and the local first service data as acquired service data of the service terminal.
Therefore, under the condition that the service data are divided into the first service data and the second service data by the service end, the client can obtain the first service data from the service end in advance to be stored locally, then in the process of obtaining the service data corresponding to the service end every time later, the client can only obtain the second service data by using the appointed mark corresponding to the service end, and further the data quantity of data obtaining from the service end in the process of obtaining the service data every time is reduced, and the efficiency of obtaining the service data from the service end is improved.
An application scenario according to an embodiment of the present application will be described first.
As shown in fig. 1, an application scenario according to an embodiment of the present application includes an electronic device 100 and an electronic device 200. The electronic device 100 is provided with a server, and the electronic device 200 is provided with a client. The client in the electronic device 200 may be a GATT client, and the corresponding server in the electronic device 100 may be a GATT server.
Again, the types of first and second electronic devices shown in fig. 1 are merely exemplary. For example, as shown in fig. 2, the second electronic device may be a wireless headset 210 in addition to the smartphone shown in fig. 1. Furthermore, the first electronic device may be a tablet computer, a computer, or other devices besides the smart phone shown in fig. 1. The second electronic device may be a device such as a smart band or a smart watch, in addition to the devices shown in fig. 1 and 2.
Embodiments of the present application will be described in detail below with reference to the accompanying drawings.
Referring to fig. 3, a data acquisition method provided in an embodiment of the present application includes:
s110: the client establishes connection with the server, and the server stores a designated identifier, wherein the designated identifier is used for identifying first service data in the server, and the first service data is fixed service data.
After the service end starts to operate, the service end can start to send broadcast data. After receiving the broadcast data sent by the server, the client can establish connection with the server sending the broadcast data.
Furthermore, in the embodiment of the present application, in order to enable a client that establishes a connection with a server to acquire which service data is fixed in the server, a specific identifier for identifying the service data that is fixed (first service data) may be stored in the server.
Optionally, the client is a GATT client, the server is a GATT server, a database corresponding to the GATT server is provided with a specified feature, and a value of the specified feature is used for recording the specified identifier. Optionally, a separately established identifier storage file is provided in the server, where the identifier storage file is used to store the specified identifier.
Here, the service data in the service side may be understood as data related to a service provided by the service side, or may be understood as data for describing the provided service. Optionally, the service data may include a service (name of the service), a feature corresponding to the service, and a feature descriptor corresponding to the feature. Wherein, the feature can be used to describe the functions of the corresponding service, and the feature descriptor can be used to describe how the corresponding functions are used and whether the corresponding functions have extensibility, etc. The service, the feature and the feature descriptor included in the service data in the service end are respectively corresponding to the identification. For example, in the GATT server, the service, the feature, and the feature descriptor are each associated with a handle as their respective identities. In some cases, the identifiers corresponding to the services, features, and feature descriptors are arranged in a certain order. For example, as shown in fig. 4, the service end includes a service 1, a service 2, and a service 3. Wherein, service 1 corresponds to feature 1, and feature 1 corresponds to feature descriptor 1. Service 2 corresponds to feature 2, feature 2 corresponds to feature descriptor 2. Service 3 corresponds to feature 3 and feature 3 corresponds to feature descriptor 3. Service 1 corresponds to an identification of 0x0001, feature 1 corresponds to an identification of 0x0002, and feature descriptor 1 corresponds to an identification of 0x0003. Service 2 corresponds to an identifier of 0x0004, feature 2 corresponds to an identifier of 0x0005, and feature descriptor 2 corresponds to an identifier of 0x0006. Service 3 corresponds to an identification of 0x0007, feature 3 corresponds to an identification of 0x0008, and feature descriptor 3 corresponds to an identification of 0x0009.
It should be noted that the number of services included in the service side shown in fig. 4 is only exemplary, and fewer or more services than those shown in fig. 4 may be included in the service side. For example, only the service 1 and the service 2 may be included, and services other than the service 1, the service 2, and the service 3 may be included. Similarly, the number of features corresponding to each service may be not limited to only 1 shown in fig. 4, and for example, there may be a plurality of features corresponding to the service. Moreover, the patterns of the identifiers shown in fig. 4 are also merely exemplary, and other patterns are also possible for the identifiers of the embodiments of the present application. For example, the storage location of the service data on the server may be directly used as the corresponding identifier. It should be noted that, as a way, the storage addresses in the server are sequenced adjacently in sequence, and the service data can still be sequenced based on the storage addresses by using the storage addresses of the service data as the identifier.
Among the service data included in the service end, part of the service data may be fixed, and the fixed part of the service data may be divided based on the corresponding identifier. For example, the service data may be divided into the first service data and the second service data by the service data correspondence identification. The first service data represents the service data which is fixed and unchanged, and the second service data represents the service data which can possibly change.
Alternatively, the specified identifier may include a start identifier and an end identifier, where the start identifier is used to identify a start position of the first service data, and the end identifier is used to characterize an end position of the first service data. As shown in fig. 4, if the determined first service data includes service 2, feature descriptor 2, service 3, feature 3, and feature descriptor 3 based on the case shown in fig. 4, the corresponding specified identifier includes 0x0004 and 0x0009, where 0x0004 is a start identifier and 0x0009 is a stop identifier. Optionally, the first service data may be determined from the service data included in the service end and the service data with the front corresponding identifier is sequentially determined from the small identifier to the large identifier, until the service data that is not fixed is detected for the first time, and then the identifier of the previous service data that is not fixed is used as the specified identifier. For example, referring to fig. 4 again, the identifier 0x0001 corresponding to the service 1 is the identifier with the top ranking, and then the fixed service data is determined sequentially from the identifier 0x0001, and if the first detected service data is not the service 3, the first service data may be determined to include the service data corresponding to the identifiers 0x0001, 0x0002, 0x0003, 0x0004, 0x0005 and 0x 0006. Thus 0x0006 would be the designation.
Furthermore, it should be noted that the fixed service data shown in the embodiments of the present application may be understood as service data that does not change in a specified time period when the device where the server is located. The specified time period may be a life cycle of the device where the server is located, or may be a certain operation cycle of the device where the server is located. A lifecycle, among other things, is understood as the time that a device can be used. For example, a device may be used for two years, and the life cycle of the device is then two years. The operation cycle may be a cycle set by the user, for example, the user may set one week as one operation cycle, or may set one month as one operation cycle.
S120: and if the first service data which is acquired from the service end based on the specified identification in advance is stored locally, acquiring second service data from the service end based on the specified identification, wherein the second service data is the service data except the first service data in the service end.
It should be noted that, in this embodiment of the present application, after the client obtains the specified identifier from the server for the first time, it may be determined, according to the specified identifier, which service data is the first service data in the server, and then the first service data is stored locally in the client.
Correspondingly, after the client establishes connection with the server, the client can firstly acquire the designated identifier corresponding to the server, then determine whether the first service data identified by the acquired designated identifier is stored or not according to the acquired designated identifier, and if so, can acquire the second service data from the server directly based on the designated identifier.
As one way, after the client establishes a connection with the server, the method further includes: if the first service data acquired from the server based on the specified identifier is not stored locally, acquiring the service data corresponding to the server from the server; and storing the first service data in the service data corresponding to the service end locally.
S130: and taking the second service data and the local first service data as the acquired service data of the service end.
In this embodiment of the present application, after the client acquires the second service data returned by the server, the client may combine the second service data with the first service data, and then use the combined service data as the service data corresponding to the acquired server.
Wherein combining the second service data and the first service data is understood as ordering the second service data and the first service data in a unified and established order. It will be appreciated that all service data in the server is arranged in a certain order. However, in the embodiment of the present application, the client may store the first service data in the service data corresponding to the server separately, so that the first service data and the second service data may be acquired respectively, and then the second service data and the first service data may be uniformly ordered according to a predetermined order, so that the order of the service data finally acquired by the client and the original order in the server are consistent. The predetermined sequence is the arrangement sequence of the service data in the server.
As a way, after the client establishes a connection with the server, the method further includes: if the first service data acquired from the server based on the specified identifier is not stored locally, acquiring the service data corresponding to the server from the server; and storing the first service data in the service data corresponding to the service end locally.
It should be noted that, as a way, the client may discover the server through the broadcast data sent by the server, and establish a connection with the server. If the connection is established for the first time, the specified identifier can be obtained from the server after the connection is established, and the first service data can be obtained again based on the specified identifier. The broadcast data sent by the server may carry an equipment identifier of the equipment where the server is located. When the client stores the first service data of the server, the first service data and the equipment identifier can be stored correspondingly. After the client acquires the equipment identifier from the broadcast data sent by the server, the client determines whether the first service data acquired from the server based on the specified identifier (the specified identifier stored by the server in the equipment to which the equipment identifier belongs) is stored locally by querying whether the equipment identifier exists locally. And if the equipment identifier is inquired to be stored locally, determining that the first service data acquired from the server side based on the designated identifier is stored locally.
In the data acquisition method provided in this embodiment, after the client establishes a connection with the server, the client further determines whether the local first service data acquired from the server based on the specified identifier is already stored in advance, and if so, the service data (second service data) of the server except for the first service data is acquired from the server directly based on the specified identifier, so that the second service data and the local first service data are used as the acquired service data of the server.
Therefore, under the condition that the service data are divided into the first service data and the second service data by the service end, the client can obtain the first service data from the service end in advance to be stored locally, then in the process of obtaining the service data corresponding to the service end every time later, the client can only obtain the second service data by using the appointed mark corresponding to the service end, and further the data quantity of data obtaining from the service end in the process of obtaining the service data every time is reduced, and the efficiency of obtaining the service data from the service end is improved.
Referring to fig. 5, a data acquisition method provided in an embodiment of the present application includes:
S210: the client establishes connection with the server, and the server stores a designated identifier, wherein the designated identifier is used for identifying first service data in the server, and the first service data is fixed service data.
S220: and if the first service data which is acquired from the server side based on the specified identifier in advance is stored locally, the specified identifier is read from the local, wherein the local specified identifier is acquired from the server side when the first service data is acquired from the server side in advance.
It should be noted that, when the client obtains the specified identifier from the server for the first time and stores the first service data identified by the specified identifier locally, the obtained specified identifier may also be stored in correspondence with the first service data, so that the specified identifier is also stored locally on the client. After the client establishes connection with the server, if the client determines that the first service data acquired from the server based on the specified identifier is locally stored, the client directly reads the specified identifier from the local.
S230: and acquiring second service data from the service end based on the local reading of the specified identifier.
As one way, the obtaining the second service data from the server based on the local reading of the specified identifier includes: and if the local reading of the specified identifier is consistent with the specified identifier stored in the server, acquiring second service data from the server based on the local reading of the specified identifier.
It should be noted that, the fixed service data in the server may refer to service data that is not transformed in a certain period of time. After the current period time is over, the service data which is fixed and unchanged in the next period time may change, so that the client can adapt to the period change better, and the client can compare the locally stored specified identifier with the specified identifier stored in the server.
For example, if the locally read specific identifier is identifier 1 and the specific identifier stored in the server is also identifier 1, then the locally read specific identifier is consistent with the specific identifier stored in the server. If the locally read specific identifier is identifier 2 and the specific identifier stored in the server is identifier 1, the locally read specific identifier is not consistent with the specific identifier stored in the server.
Furthermore, it should be noted that the client may establish connection with multiple servers, and the specified identifiers corresponding to the different servers may be the same. In this way, the client may store the specified identifier and the device identifier (the device identifier of the device where the server is located) correspondingly, so as to distinguish the specified identifiers corresponding to the different servers. For example, the locally stored designation of the client may be as shown in the following table.
If the specified identifier read from the local is identifier 2, the device identifier is device 2, and the specified identifier acquired from the server is identifier 2, and the device identifier is identifier 2, the client determines that the specified identifier read from the local is consistent with the specified identifier stored in the server. If the specified identifier read from the local is identifier 2, the device identifier is device 2, and the specified identifier acquired from the server is identifier 2, and the device identifier is identifier 1, the client determines that the specified identifier read from the local is inconsistent with the specified identifier stored in the server. In this case, it may be further determined that the service end corresponding to the first service data in the device 2 has actually changed, so that the designated identifier for identifying the first service data also changes, and in the case that it is determined that the service end corresponding to the first service data has actually changed, the service data corresponding to the service end needs to be all retrieved from the service end.
S240: and taking the second service data and the local first service data as the acquired service data of the service end.
According to the data acquisition method, when the service end divides the service data into the first service data and the second service data, the client can acquire the first service data from the service end in advance to store the first service data locally, then the client can acquire the second service data only through the appointed identification corresponding to the service end in the subsequent process of acquiring the service data corresponding to the service end every time, and therefore the data quantity of data acquisition from the service end in the process of acquiring the service data every time is reduced, and the efficiency of acquiring the service data from the service end is improved. In addition, in this embodiment, the specified identifier is also stored locally correspondingly when the first service data is stored, so that when the second service data is acquired based on the specified identifier, the specified identifier can be directly acquired from the local, and further, the speed of searching the second service data by the triggering service end is improved.
Referring to fig. 6, a data acquisition method provided in an embodiment of the present application includes:
S310: the client establishes connection with a server, and the server stores a designated identifier, wherein the designated identifier is used for identifying first service data in the server, and the first service data is fixed service data;
s320: and if the first service data acquired from the server based on the specified identifier in advance is stored locally, determining a service data query range based on the specified identifier, wherein the service data query range is a range corresponding to the second service data.
As can be seen from the foregoing description of the embodiments, in the embodiments of the present application, the specific identifier may have various implementations. The corresponding determined data query ranges may also be different for the specified identifications of the different embodiments.
As a way, the specified identifier is a last identifier sequenced in a specified identifier section, a start identifier of the specified identifier section is a first identifier sequenced in the server, and the specified identifier section is a section where the identifier corresponding to the first service data is located; the determining a service data query range based on the specified identification includes: and taking the range of the identifiers sequenced after the specified identifier as the service data query range. That is, in the case where the first service data is counted from the first identifier, the last identifier is assigned among identifiers corresponding to the service data included in the first service data. And when the identifiers corresponding to the service data are all ordered from small to large, the designated identifier is the largest identifier among the identifiers corresponding to the service data included in the first service data. For example, referring back to FIG. 4, if the designation is 0x0006 in this manner, the determined service data query range is 0x0007 to the last designation.
Alternatively, the specified identifier may include a start identifier and an end identifier, and then the client may use the range from the first identifier in the server to the start identifier, and the range after the end identifier as the service data query range. For example, referring back to FIG. 4, if the start indicator is 0x0004 and the stop indicator is 0x0006 in this manner, the determined service data query range would include a range from 0x0001 (the first indicator of rank) to 0x0003 and after 0x 0007.
As a way, the specified identifier is a last identifier sequenced in a specified identifier section, a start identifier of the specified identifier section is a first identifier sequenced in the server, and the specified identifier section is a section where the identifier corresponding to the first service data is located; the determining a service data query range based on the specified identification includes: and taking the range of the identifiers sequenced after the specified identifier as the service data query range.
S330: triggering the service end to search service data based on the service data query range so as to acquire second searched service data, wherein the second service data is the service data except the first service data in the service end.
S340: and taking the second service data and the local first service data as the acquired service data of the service end.
According to the data acquisition method, when the service end divides the service data into the first service data and the second service data, the client can acquire the first service data from the service end in advance to store the first service data locally, then the client can acquire the second service data only through the appointed identification corresponding to the service end in the subsequent process of acquiring the service data corresponding to the service end every time, and therefore the data quantity of data acquisition from the service end in the process of acquiring the service data every time is reduced, and the efficiency of acquiring the service data from the service end is improved. In addition, in this embodiment, the client may further determine the service data query range according to the specified identifier, so that the server may directly acquire service data based on the service data query range determined by the client, thereby further improving the acquisition efficiency.
Referring to fig. 7, a data acquisition method provided in an embodiment of the present application includes:
S410: the client establishes connection with a server, and the server stores a designated identifier, wherein the designated identifier is used for identifying first service data in the server, and the first service data is fixed service data;
s420: and acquiring the equipment identifier of the equipment where the server is located.
Wherein the device identification is information for identifying the uniqueness of the device. In the embodiments of the present application, the device identifier may have various embodiments.
As one approach, device identification may be implemented by a network address to which the device corresponds. In this manner, the network address of the device may be used as the device identification of the device. For example, if the device at the server side sends wireless data by means of bluetooth communication. The wireless data sent based on the bluetooth communication mode carries the bluetooth address of the device, and the client can use the bluetooth address carried in the wireless data as the device identifier of the device. Where a bluetooth address is used as the device identification, the bluetooth address is a public type address so that the bluetooth address of the device is fixed.
Alternatively, the device identification may be a random number generated based on a specified protocol, and the random number generated each time may be different, so that the device identifications corresponding to different devices may be unique. The random number serving as the device identifier may be added to the transmitted wireless data each time the server transmits the wireless data, so that the client receiving the wireless data may know which server the current wireless data is transmitted from.
In the case that the device identifier may have various embodiments, the client may acquire the device identifier in a given manner.
Optionally, if the predetermined manner configured by the client is to obtain the network address carried in the wireless data as the device identifier, the client may directly extract the network address from the wireless data after obtaining the wireless data sent by the server, so as to be used as the device identifier of the device where the server is located. Optionally, if the predetermined manner configured by the client is to obtain the random number carried in the wireless data as the device identifier, the client may directly extract the random number from the wireless data after obtaining the wireless data sent by the server, so as to be used as the device identifier of the device where the server is located.
Furthermore, the client may also perform device identification acquisition in an adaptive manner. It should be noted that, when different service ends identify their own devices, the adopted identification modes may be different. For example, although the wireless data sent by the device may carry a network address, a random network address (random type network address) is adopted by some devices, so that the network addresses of different devices may be the same, and in this case, the network address has no good way to uniquely identify the devices.
As a way, the client may detect the type of the network address adopted in the wireless data during the process of obtaining the device identifier; if the network address is detected to be a fixed type network address, directly taking the acquired network address as the equipment identifier of the equipment for transmitting the wireless data; if the network address is detected to be a random type network address, further detecting whether the wireless data carries a random number generated based on a specified protocol; and if the random number generated based on the specified protocol is detected, the random number generated based on the specified protocol is used as the equipment identification of the equipment for transmitting the wireless data. If the random number generated based on the specified protocol is not detected, all the service data are directly obtained from the service end and are used as the service data corresponding to the service end.
It should be noted that, in the embodiment of the present application, after the client obtains the first service data from the server, the device identifier may be stored in correspondence with the first service data.
S430: and detecting whether service data corresponding to the equipment identifier is stored locally.
As described above, the client may store the device identifier corresponding to the first service data when storing the first service data. The client detects whether the service data corresponding to the device identifier is stored locally or not, and can be understood as that the client determines whether the service data is based on the first service data acquired from the server locally or not. And, the first service data is service data identified by a specified identification in the wireless data where the device identification is located.
S440: and if the service data corresponding to the equipment identifier is not stored locally, determining that the first service data acquired from the server side based on the specified identifier is not stored locally.
S450: and if the service data corresponding to the equipment identifier is stored locally, determining that the first service data acquired from the server side based on the specified identifier is stored locally.
S460: and if the first service data which is acquired from the service end based on the specified identification in advance is stored locally, acquiring second service data from the service end based on the specified identification, wherein the second service data is the service data except the first service data in the service end.
S470: and taking the second service data and the local first service data as the acquired service data of the service end.
According to the data acquisition method, when the service end divides the service data into the first service data and the second service data, the client can acquire the first service data from the service end in advance to store the first service data locally, then the client can acquire the second service data only through the appointed identification corresponding to the service end in the subsequent process of acquiring the service data corresponding to the service end every time, and therefore the data quantity of data acquisition from the service end in the process of acquiring the service data every time is reduced, and the efficiency of acquiring the service data from the service end is improved. In addition, in the process of storing the first service data in this embodiment, the first service data and the device identifier of the device where the server is located are correspondingly stored, so that the first service data stored in the server can be directly determined under the condition that the service data corresponding to the device identifier is determined to be stored.
Referring to fig. 8, a data acquisition method provided in an embodiment of the present application is applied to a server, and the method includes:
s510: the method comprises the steps that a service end is connected with a client end, a designated identifier is stored in the service end, the designated identifier is used for identifying first service data in the service end, and the first service data are fixed service data.
S520: and responding to an acquisition request which is sent by the client and corresponds to the specified identifier, acquiring second service data from the server, wherein the acquisition request is sent after the client determines that the first service data acquired from the server based on the specified identifier in advance is locally stored.
In one manner, the obtaining, in response to the obtaining request corresponding to the specified identifier sent by the client, second service data from the server includes:
and responding to an acquisition request corresponding to the specified identifier sent by the client, acquiring a service data query range from the acquisition request, and querying service data corresponding to the service data query range in the service terminal as second service data.
S530: and sending the second service data to the client, so that the client can take the second service data and the local first service data as the acquired service data of the server.
It should be noted that, in this embodiment of the present application, before the client obtains the specified identifier from the server, the client may first detect whether a trust relationship has been established with the server, and if the trust relationship has been established, may directly perform service acquisition in the server according to a service acquisition mode corresponding to the established trust relationship. If the trust relationship is not established, the subsequent acquisition of the specified identifier from the server can be executed. If a trust relationship is established between the client and the server, the identity authentication between the client and the server is represented.
The following describes, by way of an example, a flow of an actual scenario according to an embodiment of the present application. As shown in fig. 9, the flow shown in fig. 9 includes:
s610: and the GATT client acquires the broadcast data sent by the GATT server.
S620: and the GATT client establishes connection with the GATT server.
S630: the GATT client detects whether a connection is first established with the server.
The GATT client may detect whether to establish a connection with the server for the first time. For example, the detection may be performed by detecting whether the service data corresponding to the device identifier of the device where the GATT server is located is stored locally in the foregoing embodiment, and if the service data corresponding to the device identifier is stored locally, the connection is determined not to be the first connection, otherwise, if the service data corresponding to the device identifier is not stored locally, the connection is determined to be the first connection. For another example, the detection may be performed by detecting whether or not the specific identifier obtained from the broadcast data is identical to the specific identifier stored locally, and if it is detected that the specific identifier obtained from the broadcast data is identical to the specific identifier stored locally, the connection is determined not to be the first connection, whereas if it is detected that the specific identifier obtained from the broadcast data is identical to the specific identifier stored locally, or if the specific identifier is not stored locally, the connection is determined to be the first connection.
S640: if the connection is the first connection, the GATT client triggers the service search to start from the service data which is ranked at the forefront among all the service data of the service end.
The service data in the service end may be arranged according to a certain order. For example, as shown in fig. 4, the corresponding service data identified as 0x0001 is the service data ranked first among all the service data of the service end. Then, if the GATT client determines that the connection is established for the first time with the GATT server, the GATT client triggers to start searching for services from the service data identified as 0x0001 in the GATT server.
S641: and acquiring the specified identification from the specified characteristics in the database of the GATT server.
In this embodiment, the specific identifier may be stored in the form of a feature in the service data, and the feature in which the specific identifier is stored may be used as the specific feature.
S642: and the GATT client stores the first service data in the searched service data locally.
Under the condition that the GATT client determines that the connection with the GATT server is established for the first time, the GATT client searches all service data in the GATT server once, so that all service data in the GATT server are found. Then for convenience
S650: if not, the GATT client triggers the local reading of the first service data.
S651: the GATT client triggers the service searching from the first service data after the specified identification to obtain the second service data.
In the embodiment shown in fig. 9, the designation flag indicates a flag corresponding to the last service data in the manner of performing fixed data detection from the first service data. It is also understood that the designation identifier is the one of the fixed service data for which the corresponding identifier is the largest. Wherein the ordering of the service data is equivalent to the ordering of the identifications corresponding to the service data. For example, referring to fig. 4, if the fixed service data is determined from 0x0001, the determined fixed service data includes service 1, feature descriptor 1, service 2, feature 2, and feature descriptor 2. Then, in the determined unchanged fixed unchanged service data, the corresponding identifier with the largest identifier is 0x0006, and then the determined specified identifier is 0x0006. After the GATT client determines that a connection is first established with the GATT server, the first service data stored locally includes service 1, feature descriptor 1, service 2, feature 2, and feature descriptor 2. Then after a subsequent connection is not established for the first time, a search for service data is started from 0x 0007.
The processing manner after the first service data and the second service data are obtained can be referred to the content in the foregoing embodiment.
Referring to fig. 10, a data acquisition device 600 provided in an embodiment of the present application is operated at a client, where the device 600 includes:
the connection management unit 610 is configured to establish a connection with a server, where the server stores a specified identifier, where the specified identifier is used to identify first service data in the server, and the first service data is fixed service data.
And the first data obtaining unit 620 is configured to obtain, if first service data obtained from the service end based on the specified identifier in advance is stored locally, second service data from the service end based on the specified identifier, where the second service data is service data in the service end except for the first service data.
And a second data obtaining unit 630, configured to take the second service data and the local first service data as obtained service data of the server.
As one manner, the first data obtaining unit 620 is specifically configured to, if the first service data that is obtained from the server side in advance based on the specified identifier is stored locally, read the specified identifier locally, where the local specified identifier is obtained from the server side when the first service data is obtained from the server side in advance; and acquiring second service data from the service end based on the local reading of the specified identifier. Optionally, the first data obtaining unit is specifically configured to obtain, if the local read identifier is consistent with the specified identifier stored in the server, second service data from the server based on the local read specified identifier.
As one way, the first data obtaining unit 620 is specifically configured to determine, if the first service data obtained from the server based on the specified identifier in advance is stored locally, a service data query range based on the specified identifier, where the service data query range is a range corresponding to the second service data; triggering the service end to search the service data based on the service data query range so as to acquire the searched second service data. Optionally, the specified identifier is a last identifier sequenced in a specified identifier interval, a start identifier of the specified identifier interval is a first identifier sequenced in the server, and the specified identifier interval is an interval in which the identifier corresponding to the first service data is located; the first data obtaining unit 620 is specifically configured to use a range where the identifiers sequenced after the specified identifier are located as a service data query range.
As a way, the first data obtaining unit 620 is further specifically configured to obtain an equipment identifier of an equipment where the server is located; and if the service data corresponding to the equipment identifier is stored locally, determining that the first service data acquired from the server side based on the specified identifier is stored locally.
As one manner, the second data obtaining unit 630 is further configured to obtain, if the first service data obtained from the server based on the specified identifier is not stored locally, service data corresponding to the server from the server; and storing the first service data in the service data corresponding to the service end locally.
As a way, the client is a GATT client, the server is a GATT server, a database corresponding to the GATT server is provided with a specified feature, and a value of the specified feature is used for recording the specified identifier.
Referring to fig. 11, a data acquisition device 700 provided in an embodiment of the present application is operated at a client, where the device 700 includes:
the connection management unit 710 is configured to establish a connection with a client, where the server stores a specified identifier, where the specified identifier is used to identify first service data in the server, and the first service data is fixed service data.
The data searching unit 720 is configured to obtain, in response to an obtaining request sent by the client and corresponding to the specified identifier, second service data from the server, where the obtaining request is sent after determining that the first service data obtained from the server based on the specified identifier is stored locally by the client.
As one manner, the data searching unit 720 is specifically configured to, in response to an acquisition request corresponding to the specified identifier sent by the client, acquire a service data query range from the acquisition request, and query, in the server, service data corresponding to the service data query range as second service data.
And a data sending unit 730, configured to send the second service data to the client, so that the client uses the second service data and the local first service data as the acquired service data of the server.
In the data acquisition device provided in this embodiment, after the client establishes a connection with the server, the client further determines whether the local first service data acquired from the server based on the specified identifier is already stored in advance, and if so, the service data (second service data) of the server except for the first service data is acquired from the server directly based on the specified identifier, so as to use the second service data and the local first service data as the acquired service data of the server. Therefore, under the condition that the service data are divided into the first service data and the second service data by the service end, the client can obtain the first service data from the service end in advance to be stored locally, then in the process of obtaining the service data corresponding to the service end every time later, the client can only obtain the second service data by using the appointed mark corresponding to the service end, and further the data quantity of data obtaining from the service end in the process of obtaining the service data every time is reduced, and the efficiency of obtaining the service data from the service end is improved.
It should be noted that, for convenience and brevity, specific working procedures of the apparatus and units described above may refer to corresponding procedures in the foregoing method embodiments, and are not described herein again. In several embodiments provided herein, the coupling of the modules to each other may be electrical. In addition, each functional module in each embodiment of the present application may be integrated into one processing module, or each module may exist alone physically, or two or more modules may be integrated into one module. The integrated modules may be implemented in hardware or in software functional modules.
An electronic device provided in the present application will be described with reference to fig. 12.
Referring to fig. 12, based on the above-mentioned data acquisition method and apparatus, another electronic device 100 capable of executing the above-mentioned data acquisition method is further provided in the embodiments of the present application. The electronic device 100 includes one or more (only one shown) processors 102, memory 104, and a wireless module 106 coupled to one another. The memory 104 stores therein a program capable of executing the contents of the foregoing embodiments, and the processor 102 can execute the program stored in the memory 104.
Wherein the processor 102 may include one or more processing cores. The processor 102 utilizes various interfaces and lines to connect various portions of the overall electronic device 100, perform various functions of the electronic device 100, and process data by executing or executing instructions, programs, code sets, or instruction sets stored in the memory 104, and invoking data stored in the memory 104. Alternatively, the processor 102 may be implemented in hardware in at least one of digital signal processing (Digital Signal Processing, DSP), field programmable gate array (Field-Programmable Gate Array, FPGA), programmable logic array (Programmable Logic Array, PLA). The processor 102 may integrate one or a combination of several of a central processing unit (Central Processing Unit, CPU), an image processor (Graphics Processing Unit, GPU), and a modem, etc. The CPU mainly processes an operating system, a user interface, an application program and the like; the GPU is used for being responsible for rendering and drawing of display content; the modem is used to handle wireless communications. It will be appreciated that the modem may not be integrated into the processor 102 and may be implemented solely by a single communication chip.
The Memory 104 may include random access Memory (Random Access Memory, RAM) or Read-Only Memory (RAM). Memory 104 may be used to store instructions, programs, code sets, or instruction sets. The memory 104 may include a stored program area and a stored data area, wherein the stored program area may store instructions for implementing an operating system, instructions for implementing at least one function (e.g., a touch function, a sound playing function, an image playing function, etc.), instructions for implementing the various method embodiments described below, etc. The storage data area may also store data created by the terminal 100 in use (such as phonebook, audio-video data, chat-record data), etc.
The wireless module 106 is configured to receive and transmit electromagnetic waves, and to implement mutual conversion between the electromagnetic waves and the electrical signals, so as to communicate with a communication network or other devices, such as an audio playback device. The wireless module 106 may include various existing circuit elements for performing these functions, such as an antenna, a radio frequency transceiver, a digital signal processor, an encryption/decryption chip, a Subscriber Identity Module (SIM) card, memory, and the like. The wireless module 106 may communicate with various networks such as the internet, intranets, wireless networks, or other devices via wireless networks. The wireless network may include a cellular telephone network, a wireless local area network, or a metropolitan area network. For example, the wireless module 106 may interact with a base station.
Referring to fig. 13, a block diagram of a computer readable storage medium according to an embodiment of the present application is shown. The computer readable medium 1100 has stored therein program code that can be invoked by a processor to perform the methods described in the method embodiments above.
The computer readable storage medium 1100 may be an electronic memory such as a flash memory, an EEPROM (electrically erasable programmable read only memory), an EPROM, a hard disk, or a ROM. Optionally, computer readable storage medium 1100 includes non-volatile computer readable medium (non-transitory computer-readable storage medium). The computer readable storage medium 1100 has storage space for program code 1110 that performs any of the method steps described above. The program code can be read from or written to one or more computer program products. Program code 1110 may be compressed, for example, in a suitable form.
In summary, after the connection between the client and the server is established, the client further determines whether the first service data acquired from the server based on the specified identifier is stored in advance, if so, service data (second service data) of the server except the first service data is acquired from the server directly based on the specified identifier, so as to use the second service data and the local first service data as the acquired service data of the server.
Therefore, under the condition that the service data are divided into the first service data and the second service data by the service end, the client can obtain the first service data from the service end in advance to be stored locally, then in the process of obtaining the service data corresponding to the service end every time later, the client can only obtain the second service data by using the appointed mark corresponding to the service end, and further the data quantity of data obtaining from the service end in the process of obtaining the service data every time is reduced, and the efficiency of obtaining the service data from the service end is improved.
Finally, it should be noted that: the above embodiments are only for illustrating the technical solution of the present application, and are not limiting thereof; although the present application has been described in detail with reference to the foregoing embodiments, one of ordinary skill in the art will appreciate that: the technical scheme described in the foregoing embodiments can be modified or some technical features thereof can be replaced by equivalents; such modifications and substitutions do not drive the essence of the corresponding technical solutions to depart from the spirit and scope of the technical solutions of the embodiments of the present application.
Claims (11)
1. A method for obtaining data, applied to a client, the method comprising:
The client establishes connection with a server, and the server stores a designated identifier, wherein the designated identifier is used for identifying first service data in the server, and the first service data is fixed service data;
if the first service data acquired from the service end based on the specified identifier in advance is stored locally, determining a service data query range based on the specified identifier, wherein the service data query range is a range corresponding to the second service data;
triggering the service end to search service data based on the service data query range so as to acquire second searched service data, wherein the second service data is the service data except the first service data in the service end;
and taking the second service data and the local first service data as the acquired service data of the service end.
2. The method according to claim 1, wherein the method further comprises:
and if the first service data which is acquired from the server side based on the specified identifier in advance is stored locally, the specified identifier is read from the local, wherein the local specified identifier is acquired from the server side when the first service data is acquired from the server side in advance.
3. The method of claim 1, wherein the specified identifier is a last identifier in a specified identifier section, a start identifier of the specified identifier section is a first identifier in the service end in the sequence, and the specified identifier section is a section in which the identifier corresponding to the first service data is located; the determining a service data query range based on the specified identification includes:
and taking the range of the identifiers sequenced after the specified identifier as the service data query range.
4. The method of claim 1, wherein determining a service data query scope based on the specified identification, the service data query scope being preceded by a scope corresponding to second service data, further comprises:
acquiring an equipment identifier of equipment where a server is located;
and if the service data corresponding to the equipment identifier is stored locally, determining that the first service data acquired from the server side based on the specified identifier is stored locally.
5. The method according to any one of claims 1-4, wherein after the client establishes a connection with the server, further comprising:
if the first service data acquired from the server based on the specified identifier is not stored locally, acquiring the service data corresponding to the server from the server;
And storing the first service data in the service data corresponding to the service end locally.
6. The method according to any one of claims 1 to 4, wherein the client is a GATT client, the server is a GATT server, a database corresponding to the GATT server is provided with a specified feature, and a value of the specified feature is used for recording the specified identifier.
7. A data acquisition method, applied to a server, the method comprising:
the method comprises the steps that a connection is established between a server and a client, a designated identifier is stored in the server, the designated identifier is used for identifying first service data in the server, and the first service data are fixed service data;
responding to an acquisition request which is sent by a client and corresponds to the specified identifier, determining a service data query range based on the specified identifier, wherein the service data query range is a range corresponding to second service data, searching service data based on the service data query range to acquire the searched second service data, and sending the acquisition request after determining that the first service data which is acquired from the server based on the specified identifier in advance is locally stored in the client;
And sending the second service data to the client, so that the client can take the second service data and the local first service data as the acquired service data of the server.
8. A data acquisition device, operable on a client, the device comprising:
the connection management unit is used for establishing connection with a service end, wherein a specified identifier is stored in the service end and used for identifying first service data in the service end, and the first service data is fixed service data;
the first data acquisition unit is used for determining a service data query range based on the specified identifier if the first service data which is acquired from the service end based on the specified identifier in advance is locally stored, wherein the service data query range is a range corresponding to the second service data; triggering the service end to search service data based on the service data query range so as to acquire second searched service data, wherein the second service data is the service data except the first service data in the service end;
and the second data acquisition unit is used for taking the second service data and the local first service data as the acquired service data of the service end.
9. A data acquisition device, operable on a server, the device comprising:
the connection management unit is used for establishing connection with the client, wherein the server stores a specified identifier, the specified identifier is used for identifying first service data in the server, and the first service data is fixed service data;
the data searching unit is used for responding to an acquisition request which is sent by the client and corresponds to the specified identifier, determining a service data query range based on the specified identifier, wherein the service data query range is a range corresponding to second service data, searching the service data based on the service data query range to acquire the searched second service data, and sending the acquisition request after determining that the first service data which is acquired from the server based on the specified identifier in advance is locally stored by the client;
and the data sending unit is used for sending the second service data to the client, so that the client can take the second service data and the local first service data as the acquired service data of the server.
10. An electronic device comprising one or more processors and memory;
One or more programs stored in the memory and configured to be executed by the one or more processors, the one or more programs configured to perform the method of any of claims 1-6.
11. A computer readable storage medium, characterized in that the computer readable storage medium has stored therein a program code, wherein the program code, when being executed by a processor, performs the method of any of claims 1-6.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110963350.8A CN113691610B (en) | 2021-08-20 | 2021-08-20 | Data acquisition method and device, electronic equipment and storage medium |
| PCT/CN2022/106771 WO2023020187A1 (en) | 2021-08-20 | 2022-07-20 | Data obtaining methods and apparatuses, electronic device and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110963350.8A CN113691610B (en) | 2021-08-20 | 2021-08-20 | Data acquisition method and device, electronic equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113691610A CN113691610A (en) | 2021-11-23 |
| CN113691610B true CN113691610B (en) | 2024-04-09 |
Family
ID=78581099
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110963350.8A Active CN113691610B (en) | 2021-08-20 | 2021-08-20 | Data acquisition method and device, electronic equipment and storage medium |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN113691610B (en) |
| WO (1) | WO2023020187A1 (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113691609B (en) * | 2021-08-20 | 2024-04-09 | Oppo广东移动通信有限公司 | Data acquisition method and device, electronic equipment and storage medium |
| CN113691610B (en) * | 2021-08-20 | 2024-04-09 | Oppo广东移动通信有限公司 | Data acquisition method and device, electronic equipment and storage medium |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101350841A (en) * | 2007-07-17 | 2009-01-21 | 华为技术有限公司 | Method for establishing medium resource access relation as well as communication system and relevant equipment |
| CN105553954A (en) * | 2015-12-09 | 2016-05-04 | 百度在线网络技术（北京）有限公司 | Data processing method and system |
| CN105704252A (en) * | 2016-04-26 | 2016-06-22 | 青岛海信电器股份有限公司 | Low-power-consumption bluetooth equipment data transmission method and device |
| WO2016127693A1 (en) * | 2015-02-13 | 2016-08-18 | 华为技术有限公司 | Service data sending method and storage system |
| CN108170723A (en) * | 2017-12-07 | 2018-06-15 | 维沃移动通信有限公司 | A kind of web page resources acquisition methods, terminal device, server and system |
| CN109120851A (en) * | 2018-09-21 | 2019-01-01 | 维沃移动通信有限公司 | A kind of image processing method, device and electronic equipment |
| CN110049503A (en) * | 2018-01-15 | 2019-07-23 | 中国移动通信有限公司研究院 | A kind of method and apparatus obtaining data |
| CN110830538A (en) * | 2018-08-13 | 2020-02-21 | 华为技术有限公司 | Message transmission method, device and storage medium |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10558653B2 (en) * | 2017-06-07 | 2020-02-11 | Sap Se | Dynamic, variable-data attribute data service |
| CN112311720B (en) * | 2019-07-23 | 2022-10-14 | 腾讯科技（深圳）有限公司 | Data transmission method and device |
| CN112286896B (en) * | 2020-11-19 | 2024-02-06 | 北京百家科技集团有限公司 | Log file processing method and device, computer equipment and storage medium |
| CN113691610B (en) * | 2021-08-20 | 2024-04-09 | Oppo广东移动通信有限公司 | Data acquisition method and device, electronic equipment and storage medium |
| CN113691609B (en) * | 2021-08-20 | 2024-04-09 | Oppo广东移动通信有限公司 | Data acquisition method and device, electronic equipment and storage medium |
-
2021
- 2021-08-20 CN CN202110963350.8A patent/CN113691610B/en active Active
-
2022
- 2022-07-20 WO PCT/CN2022/106771 patent/WO2023020187A1/en active Application Filing
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101350841A (en) * | 2007-07-17 | 2009-01-21 | 华为技术有限公司 | Method for establishing medium resource access relation as well as communication system and relevant equipment |
| WO2016127693A1 (en) * | 2015-02-13 | 2016-08-18 | 华为技术有限公司 | Service data sending method and storage system |
| CN105553954A (en) * | 2015-12-09 | 2016-05-04 | 百度在线网络技术（北京）有限公司 | Data processing method and system |
| CN105704252A (en) * | 2016-04-26 | 2016-06-22 | 青岛海信电器股份有限公司 | Low-power-consumption bluetooth equipment data transmission method and device |
| CN108170723A (en) * | 2017-12-07 | 2018-06-15 | 维沃移动通信有限公司 | A kind of web page resources acquisition methods, terminal device, server and system |
| CN110049503A (en) * | 2018-01-15 | 2019-07-23 | 中国移动通信有限公司研究院 | A kind of method and apparatus obtaining data |
| CN110830538A (en) * | 2018-08-13 | 2020-02-21 | 华为技术有限公司 | Message transmission method, device and storage medium |
| CN109120851A (en) * | 2018-09-21 | 2019-01-01 | 维沃移动通信有限公司 | A kind of image processing method, device and electronic equipment |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113691610A (en) | 2021-11-23 |
| WO2023020187A1 (en) | 2023-02-23 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN113691610B (en) | Data acquisition method and device, electronic equipment and storage medium | |
| JP5990275B2 (en) | Method for transmitting data between terminals and terminal | |
| EP3413594B1 (en) | Methods for connecting communication devices, terminal device and server system | |
| CN113691609B (en) | Data acquisition method and device, electronic equipment and storage medium | |
| US10645001B2 (en) | Information transmission method and apparatus, device and storage medium | |
| CN108781473B (en) | Method and equipment for sharing files among different terminals | |
| CN113366815B (en) | Network resource request method, device, electronic equipment and storage medium | |
| CN109886670B (en) | Payment method, device, system, mobile terminal, payment machine and server | |
| CN109714716B (en) | Data packet forwarding method and device and mobile terminal | |
| CN105141789B (en) | Unknown phone number labeling method and device | |
| CN107645789B (en) | Network access method, device and system | |
| CN109725543B (en) | Equipment control code configuration method and device, cloud server and network system | |
| CN104023055A (en) | Video sharing method and system, and terminal device | |
| CN1852326B (en) | Method for obtaining mobile game for mobile terminal | |
| CN105430636A (en) | SIM card management method and system | |
| CN113132929A (en) | Equipment network access method, device, computer equipment and storage medium | |
| CN111757317B (en) | Request processing method, related device and system | |
| US11979819B2 (en) | Communication method and apparatus | |
| CN111511043B (en) | Network connection method, device, electronic equipment and storage medium | |
| CN114222284A (en) | Terminal equipment identification method and device and readable storage medium | |
| CN104969598B (en) | A kind of method and apparatus using white spectrum communication | |
| CN103763087B (en) | Information processing method and electronic equipment | |
| CN113055961A (en) | Wireless network connection method, device, router and storage medium | |
| CN111338710A (en) | Application program control method and device, electronic equipment and storage medium | |
| CN107370863B (en) | Connection information updating method and device based on Bluetooth connection |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |