CN113810857B - Beacon message processing method and system - Google Patents

Abstract

An embodiment of the present application discloses a system, which includes: a mobile device receives a beacon message from a beacon device, where the beacon message includes the target beacon identification; based on the beacon message, obtains beacon data; The server sends the target beacon identification and the beacon data; if the server determines that the beacon data meets the preset conditions, it calls the corresponding third-party service based on the target beacon identification. This application can configure the preset conditions on the server. Since the behavior of determining whether the preset conditions are met is not performed on the mobile device side, the APP of the mobile device does not need to sense how the preset conditions need to be modified. When the preset conditions are When the conditions need to be modified, the server only needs to make corresponding modifications, which greatly reduces the time-consuming of the entire process.

Description

A beacon message processing method and system

Technical field

The present application relates to the field of computers, and in particular, to a beacon message processing method and system.

Background technique

A beacon device is a device that periodically broadcasts beacon messages to nearby areas. The beacon messages it sends can be acquired by smartphones or other mobile devices that support Bluetooth. Beacon devices are generally battery-powered and deployed indoors to broadcast beacon messages to surrounding mobile devices. The broadcast range is determined by the hardware capabilities of the beacon device, and is generally within 100 meters. A mobile device installed with the ability to read beacon messages will take corresponding actions based on the beacon messages received to provide corresponding services to the owner of the mobile device.

In one scenario, when a mobile device obtains a beacon message broadcast by a surrounding beacon, it can report the beacon identification it scanned to the cloud server. The cloud service can return the corresponding message attachment, and the mobile device can according to the message Attachments and predefined program logic determine the next step, such as triggering the rendering of message attachments or calling third-party services. However, the mobile device needs to receive the message attachment before calling the third-party service, which will cause a certain business delay.

Contents of the invention

In a first aspect, this application provides a system, which includes:

The mobile device is configured to receive a beacon message from the beacon device, where the beacon message includes a target beacon identification.

In this embodiment, the mobile device may periodically perform scanning to discover beacon messages from beacon devices adjacent to the location of the mobile device, where the beacon messages include a target beacon identification. As used herein, "proximity" refers to a mobile device being physically close enough to a beacon device to receive a radio frequency (RF) signal transmitted by the beacon device. For example, a wireless transceiver on a mobile device may initiate a short-range scan to discover RF signals, such as BLE RF signals, near field communication RF signals, and ultrasonic signals.

Based on the beacon message, beacon data is obtained, wherein the beacon data includes at least one of the following: the distance between the mobile device and the beacon device, and the mobile device receiving the beacon the time of the message;

Specifically, the mobile device may obtain the distance information between the mobile device and the beacon device based on the signal strength value of the received beacon message, where the distance information may include at least one of the following: The distance value between the mobile device and the beacon device, and the change information of the distance value between the mobile device and the beacon device. The change information of the distance value between the mobile device and the beacon device may include the change information of the distance value between the mobile device and the beacon device. The change trend of the distance, for example, from far to near, from near to far, etc. wait.

Specifically, the time information may include at least one of the following: the time when the mobile device receives the beacon message, and the time when the mobile device is within the signal coverage area of the beacon device. The time information may include the time the App user scanned the beacon device, the time the App user stayed around the beacon device, etc.

Send the target beacon identification and the beacon data to the server; and,

The server is configured to call the corresponding third-party service based on the target beacon identification if it is determined that the beacon data satisfies the preset condition.

When the application on the mobile device scans a nearby beacon device, it can send a request to the server (beacon cloud service platform) to obtain the beacon message attachment. The request can carry the target beacon identification and beacon data. The server can call the corresponding third-party service based on the target beacon identification when the beacon data meets the preset conditions.

In one implementation, the mobile device can receive the beacon message from the beacon device based on the system service of the mobile device. At this time, the third-party service may refer to the service provided by a third-party application (application, APP). For example, a mobile device may support one or more applications, some of which may be applications provided by third parties (non-mobile device manufacturers). Third-party applications do not need to be pre-installed in the terminal, but need to be downloaded from the network side by the mobile device. When mobile devices run these applications, they can communicate with the third-party server corresponding to the application, and the third-party server can provide third-party services. Taking Huawei as the manufacturer of mobile devices and Tencent as the provider of WeChat as an example, after WeChat is installed on the mobile device, when the mobile device runs WeChat, it can communicate with the server corresponding to WeChat (that is, a third-party server).

It should be noted that in some implementations, an agreement is signed between mobile device producers and developers of certain applications. Such applications can be pre-installed in the terminal. In this case, calling the application provided by such applications The service can still be understood as the server calling a third-party service.

In one implementation, services related to beacon data processing on the server side can be provided by a certain manufacturer. At this time, services not provided by the manufacturer can be understood as third-party services.

In one implementation, the mobile device can receive a beacon message from a beacon device based on a second application, the third-party service is a service provided by a first application, and the first application and the second application are different, That is, the application that receives the beacon message and the application that provides third-party services are different applications.

In the embodiment of the present application, in the process of triggering the call of third-party services, preset conditions for triggering are added to the server, including but not limited to the distance between the mobile device and the beacon device, or the distance between the mobile device and the beacon device, or the distance between the mobile device and the beacon device. The time at which the mobile device receives the beacon message satisfies preset conditions. When the mobile device application scans a specific beacon message, it will send the relevant beacon data to the server. The server can make rule judgments based on the beacon data and only call third-party services if the preset conditions are met. The advantage of this is that the server rather than the mobile device performs the judgment action of whether to trigger the call of the third-party service, which can reduce the processing steps of the mobile device, and the preset conditions can be configured and modified on the server. Since it is judged whether the preset conditions are met, The behavior of setting conditions is not performed by the mobile device side. The APP does not need to sense how the preset conditions need to be modified. When the preset conditions need to be modified, the server only needs to make corresponding modifications, which greatly reduces the time required for the entire process. time consuming. When the application developer needs to modify the above preset conditions, there is no need to modify the business logic of the App, and there is no need to re-publish the App on the application market, and there is no need to let users upgrade the App. The preset conditions can be modified directly on the server side. That’s it, greatly reducing the time-consuming process of the entire process.

In an optional implementation, the third-party service is a service provided by a first application, and the mobile device is configured to receive a beacon message from a beacon device based on the second application; or, the third application The third-party service is a service provided by the first application. The mobile device is configured to receive beacon messages from the beacon device based on its own service process.

In an optional implementation, the server is configured to determine the third-party service corresponding to the target beacon identification based on a preconfigured mapping relationship; wherein the mapping relationship includes multiple beacon identifications and each A beacon identifies the corresponding third-party service.

In this embodiment of the present application, the server may determine the third-party service corresponding to the target beacon identification based on a pre-configured mapping relationship; wherein the mapping relationship includes multiple beacon identifications and a corresponding number corresponding to each beacon identification. Third Party Services. Among them, the mapping relationship can be pre-configured on the server by the application developer.

In an optional implementation, the beacon data includes information indicating the distance between the mobile device and the beacon device, and the preset condition includes at least one of the following:

The distance value between the mobile device and the beacon device is within a preset range;

The distance value between the mobile device and the beacon device changes from large to small; and,

The distance value between the mobile device and the beacon device changes from small to large.

In an optional implementation, the beacon data includes information indicating the time at which the mobile device receives the beacon message;

The preset conditions include at least one of the following:

The time when the mobile device receives the beacon message is within a preset range; and,

The time the mobile device is within the signal coverage area of the beacon device is within a preset range.

In an optional implementation, the server is configured to send the target message to the address where the third-party service is located. For example, the third-party service can be an email address, and the email address is related to the third-party service. The service may provide corresponding third-party services based on the received target message, which is generated based on the target beacon identification and/or beacon data, and the target message is related to the third-party service to be called, specifically , the target message is the data required to call the third-party service.

In an optional implementation, the server is configured to call the RESTful application programming interface API corresponding to the third-party service.

In one implementation, the third-party service in the mapping relationship may be an application programming interface API, then the server may call the application programming interface API corresponding to the third-party service. For example, the API can be a RESTful API, and the server can use the RESTful address pre-configured by the developer to call third-party services. The third-party service can be deployed on a server deployed separately by the developer, or it can be a deployed serverless function. For example, in one implementation, the beacon data processing service on the server side is provided by a certain manufacturer, and the beacon data processing service is located on server A. Server A is also deployed with a serverless function that implements another server. In this case, calling the service corresponding to the serverless function on the server side can also be understood as calling a third-party service.

In an optional implementation, the server is configured to initiate a call based on the remote procedure call protocol RPC to the address where the third-party service is located.

In an optional implementation, the server is configured to determine the corresponding third-party service based on the target beacon identification; and call the third-party service based on the beacon data.

In one implementation, the server can pass these beacon data as input parameters to the third-party service. In one implementation, the server can process the beacon data (such as mathematical statistics or other processing), and pass the processing results as input parameters to third-party services, etc.

In an optional implementation, the server is configured to receive reply data from the third-party service; send the reply data to the mobile device; correspondingly, the mobile device is configured to trigger The reply data is presented accordingly.

In an optional implementation, the mobile device is configured to receive reply data from the third-party service; and trigger presentation corresponding to the reply data.

In this embodiment of the present application, if the server determines that the beacon data meets the preset conditions, it calls the corresponding third-party service based on the target beacon identification. Optionally, the third-party service can send reply data to the server, and the server can receive the reply data from the third-party service and send the reply data to the mobile device; accordingly, the mobile device can Trigger the corresponding presentation of the reply data.

Optionally, the third-party service can directly send the reply data to the mobile device; accordingly, the mobile device can trigger the corresponding presentation of the reply data. The presentation of data may not be limited to having the data displayed on the screen of a mobile device. In some implementations, presenting message data may include providing one or more notifications. The presentation of message data may include force feedback (e.g., vibration indication), audio output (e.g., beeps, music, etc.), visual output (e.g., flash), or a combination thereof. In some implementations, message data may include any content, including but not limited to text, graphics, digital images, audio, video, and animation. Message data can be presented on the mobile device in the form of audio output to collaborate with mobile devices that do not have display capabilities. In some implementations, presenting the message data may include retrieving content corresponding to one or more values included in the message data; and causing the content to be displayed on the screen.

In an optional implementation, the server is configured to receive condition modification information indicating that the preset condition is modified to a new condition; the preset condition is modified based on the condition modification information. condition.

In a second aspect, the present application provides a system, which includes: a mobile device configured to receive a target beacon identification from a beacon device; sending the target beacon identification to a server; and, the server, Configured to call the corresponding third-party service based on the target beacon identification.

In an optional implementation, the server is configured to determine the third-party service corresponding to the target beacon identification based on a preconfigured mapping relationship; wherein the mapping relationship includes multiple beacon identifications and each A beacon identifies the corresponding third-party service.

In an optional implementation, the third-party service is a service provided by the first application, and the mobile device is configured to receive the target beacon identification from the beacon device based on the second application; or,

The third-party service is a service provided by the first application, and the mobile device is configured to receive the target beacon identification from the beacon device based on its own service process.

In an optional implementation, the server is configured to send a target message to the address where the third-party service is located, where the target message is generated based on the beacon identification.

In an optional implementation, the server is configured to call an application programming interface API corresponding to the third-party service.

In an optional implementation, the server is configured to initiate a call based on the remote procedure call protocol RPC to the address where the third-party service is located.

In an optional implementation, the mobile device is configured to receive a beacon message from a beacon device, where the beacon message includes the target beacon identification; based on the beacon message, obtain the beacon Data, wherein the beacon data includes at least one of the following:

The distance between the mobile device and the beacon device, the time when the mobile device receives the beacon message, or the identity of the mobile device;

Send the target beacon identification and the beacon data to the server;

Correspondingly, the server is configured to call the corresponding third-party service based on the target beacon identification and the beacon data.

In an optional implementation, the server is configured to determine the corresponding third-party service based on the target beacon identification; and call the third-party service based on the beacon data.

In an optional implementation, the server is configured to receive reply data from the third-party service; send the reply data to the mobile device; correspondingly, the mobile device is configured to trigger The reply data is presented accordingly.

In an optional implementation, the mobile device is configured to receive reply data from the third-party service; and trigger presentation corresponding to the reply data.

In an optional implementation, the method further includes receiving condition modification information, the condition modification information indicating modifying the preset condition to a new condition; modifying the preset condition based on the condition modification information.

In the third aspect, this application provides a beacon message processing method, the method is applied to the server, and the method includes:

receiving a target beacon identification from a mobile device; and,

Based on the target beacon identification, the corresponding third-party service is called.

In an optional implementation, the server and the method further include:

Based on the preconfigured mapping relationship, the third-party service corresponding to the target beacon identification is determined; wherein the mapping relationship includes multiple beacon identifications and the third-party service corresponding to each beacon identification.

In an optional implementation, the preset conditions include at least one of the following:

The distance value between the mobile device and the beacon device is within a preset range;

The distance value between the mobile device and the beacon device changes from large to small; and,

The distance value between the mobile device and the beacon device changes from small to large;

In an optional implementation, the preset conditions include at least one of the following:

The time at which the mobile device receives the beacon message is within a preset range; and

The time the mobile device is within the signal coverage area of the beacon device is within a preset range.

In an optional implementation, the corresponding third-party service call includes:

Send a target message to the address where the third-party service is located, where the target message is generated based on the beacon identification.

In an optional implementation, the corresponding third-party service call includes:

Call the application programming interface API corresponding to the third-party service.

In an optional implementation, the corresponding third-party service call includes:

Initiate a call based on the remote procedure call protocol RPC to the address where the third-party service is located.

In an optional implementation, the method further includes:

Receive beacon data from the mobile device, wherein the beacon data includes at least one of the following:

The distance between the mobile device and the beacon device, the time when the mobile device receives the beacon message, or the identity of the mobile device;

Based on the target beacon identification and the beacon data, the corresponding third-party service is called.

In an optional implementation, calling the corresponding third-party service based on the target beacon identification includes:

Based on the target beacon identification, the corresponding third-party service is determined; based on the beacon data, the third-party service is called.

In an optional implementation, the method further includes:

receive response data from said third-party services;

The reply data is sent to the mobile device so that the mobile device triggers presentation corresponding to the reply data.

In an optional implementation, the method further includes: receiving condition modification information indicating that the preset condition is modified to a new condition; modifying the preset condition based on the condition modification information .

In a fourth aspect, this application provides a beacon message processing method, which method includes:

Receive a target beacon identification and beacon data from a mobile device, wherein the beacon data includes at least one of the following: the distance between the mobile device and the beacon device, and the mobile device receiving the signal mark the time of the message, or the identity of the mobile device; and,

If it is determined that the beacon data meets the preset conditions, the corresponding third-party service is called based on the target beacon identification.

In an optional implementation, the distance information includes at least one of the following:

The distance value between the mobile device and the beacon device, and the change information of the distance value between the mobile device and the beacon device.

In an optional implementation, the time information includes at least one of the following:

The time when the mobile device receives the beacon message and the time when the mobile device is within the signal coverage area of the beacon device.

In an optional implementation, the method further includes:

Based on the preconfigured mapping relationship, the third-party service corresponding to the target beacon identification is determined; wherein the mapping relationship includes multiple beacon identifications and the third-party service corresponding to each beacon identification.

In an optional implementation, calling the corresponding third-party service based on the target beacon identification includes:

Based on the target beacon identification, the corresponding third-party service is determined; based on the beacon data, the third-party service is called.

In an optional implementation, the method further includes:

receive response data from said third-party services;

The reply data is sent to the mobile device so that the mobile device triggers presentation corresponding to the reply data.

In an optional implementation, the method further includes: receiving condition modification information indicating that the preset condition is modified to a new condition; modifying the preset condition based on the condition modification information .

In the fifth aspect, this application provides a beacon message processing device. The beacon message processing device includes:

The receiving module is used to receive the target beacon identification from the mobile device.

The calling module is used to call the corresponding third-party service based on the target beacon identification.

In an optional implementation, the device further includes:

A determining module, configured to determine a third-party service corresponding to the target beacon identification based on a preconfigured mapping relationship; wherein the mapping relationship includes multiple beacon identifications and a third-party service corresponding to each beacon identification.

In an optional implementation, the preset conditions include at least one of the following:

The distance value between the mobile device and the beacon device is within a preset range;

The distance value between the mobile device and the beacon device changes from large to small

The distance value between the mobile device and the beacon device changes from small to large;

The time at which the mobile device receives the beacon message is within a preset range; and

The time the mobile device is within the signal coverage area of the beacon device is within a preset range.

In an optional implementation, the calling module is configured to send a target message to the address where the third-party service is located, where the target message is generated based on the beacon identification.

In an optional implementation, the calling module is used to call an application programming interface API corresponding to the third-party service.

In an optional implementation, the calling module is configured to initiate a call based on the remote procedure call protocol RPC to the address where the third-party service is located.

In an optional implementation, the receiving module is configured to receive beacon data from the mobile device, where the beacon data includes at least one of the following:

The distance between the mobile device and the beacon device, the time when the mobile device receives the beacon message, or the identity of the mobile device;

Based on the target beacon identification and the beacon data, the corresponding third-party service is called.

In an optional implementation, the calling module is configured to determine the corresponding third-party service based on the target beacon identification; and call the third-party service based on the beacon data.

In an optional implementation, the receiving module is configured to receive reply data from the third-party service;

A sending module, configured to send the reply data to the mobile device, so that the mobile device triggers the corresponding presentation of the reply data.

In a sixth aspect, this application provides a beacon message processing device. The beacon message processing device includes:

A receiving module, configured to receive a target beacon identification and beacon data from a mobile device, where the beacon data includes at least one of the following: the distance between the mobile device and the beacon device, and the mobile device. The time when the device receives the beacon message, or the identity of the mobile device; and,

A calling module, configured to call the corresponding third-party service based on the target beacon identification if it is determined that the beacon data meets the preset conditions.

In an optional implementation, the distance information includes at least one of the following:

The distance value between the mobile device and the beacon device, and the change information of the distance value between the mobile device and the beacon device.

In an optional implementation, the time information includes at least one of the following:

The time when the mobile device receives the beacon message and the time when the mobile device is within the signal coverage area of the beacon device.

In an optional implementation, the device further includes:

The determination module determines the third-party service corresponding to the target beacon identification based on the pre-configured mapping relationship; wherein the mapping relationship includes multiple beacon identifications and the third-party service corresponding to each beacon identification.

In an optional implementation, the preset conditions include at least one of the following:

The distance value between the mobile device and the beacon device is within a preset range;

The distance value between the mobile device and the beacon device changes from large to small

The distance value between the mobile device and the beacon device changes from small to large;

The time at which the mobile device receives the beacon message is within a preset range; and

The time the mobile device is within the signal coverage area of the beacon device is within a preset range.

In an optional implementation, the calling module is configured to determine the corresponding third-party service based on the target beacon identification; and call the third-party service based on the beacon data.

In an optional implementation, the receiving module is configured to receive reply data from the third-party service;

A sending module, configured to send the reply data to the mobile device, so that the mobile device triggers the corresponding presentation of the reply data.

In an optional implementation, the receiving module is also configured to: receive condition modification information, the condition modification information indicating that the preset condition is modified to a new condition; the device also includes:

A status modification module, configured to modify the preset condition based on the condition modification information.

In the seventh aspect, the present application provides a beacon message processing device, which may include a processor, a memory and a communication interface. The processor and the memory are coupled, and the communication interface is used to perform each possible implementation of the third aspect or the fourth aspect. In the steps related to the receiving and sending actions, the memory stores program instructions, and when the program instructions stored in the memory are executed by the processor, they are used to process the data received by the communication interface, in the third aspect or the fourth aspect. Processing-related steps in each possible implementation. For the steps performed by the processor in each possible implementation manner of the third aspect or the fourth aspect, please refer to the third aspect or the fourth aspect for details, and will not be described again here.

In an eighth aspect, the present application provides a computer-readable storage medium that stores a computer program that, when run on a computer, causes the computer to execute any one of the above-mentioned third or fourth aspects. the method described.

In a ninth aspect, the present application provides a circuit system, which circuit system includes a processing circuit configured to perform the method described in any one of the above third or fourth aspects.

In a tenth aspect, the present application provides a computer program that, when run on a computer, causes the computer to execute the method described in any one of the above-mentioned third or fourth aspects.

In an eleventh aspect, the present application provides a chip system. The chip system includes a processor and is used to support a server or a threshold value acquisition device to implement the functions involved in the above aspects, for example, sending or processing the functions involved in the above methods. data and/or information. In a possible design, the chip system further includes a memory, and the memory is used to store necessary program instructions and data for the server or communication device. The chip system may be composed of chips, or may include chips and other discrete devices.

Description of the drawings

Figure 1 is a plan view of an exemplary application scenario;

Figure 2 is a plan view of an exemplary application scenario;

Figure 3 is a flowchart of the beacon information processing method provided by the embodiment of the present application;

Figure 4 is a flowchart of the beacon information processing method provided by the embodiment of the present application;

Figure 5 is a schematic flowchart of the beacon information processing method provided by the embodiment of the present application;

Figure 6 is a schematic diagram of the configuration interface provided by the embodiment of the present application;

Figure 7 is a flowchart of the beacon information processing method provided by the embodiment of the present application;

Figure 8 is a schematic flowchart of the beacon information processing method provided by the embodiment of the present application;

Figure 9 is a flowchart of the beacon information processing method provided by the embodiment of the present application;

Figure 10 is a schematic flowchart of the beacon information processing method provided by the embodiment of the present application;

Figure 11 is a schematic diagram of a beacon information processing device provided by an embodiment of the present application;

Figure 12 is a schematic diagram of a mobile device provided by an embodiment of the present application;

Figure 13 is a schematic diagram of the software architecture of a mobile device provided by an embodiment of the present application;

Figure 14 is a schematic diagram of a server provided by an embodiment of the present application.

Detailed ways

The embodiments of the present application will be described below in conjunction with the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present application, rather than all of the embodiments. Persons of ordinary skill in the art will know that with the development of technology and the emergence of new scenarios, the technical solutions provided by the embodiments of this application are also applicable to similar technical problems.

The terms "first", "second", etc. in the description and claims of this application and the above-mentioned drawings are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It is to be understood that the data so used are interchangeable under appropriate circumstances so that the embodiments described herein can be practiced in sequences other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or modules and need not be limited to those explicitly listed. Those steps or modules may instead include other steps or modules not expressly listed or inherent to the processes, methods, products or devices. The naming or numbering of steps in this application does not mean that the steps in the method flow must be executed in the time/logical sequence indicated by the naming or numbering. The process steps that have been named or numbered can be implemented according to the purpose to be achieved. The order of execution can be changed for technical purposes, as long as the same or similar technical effect can be achieved.

In addition, in the description of the present invention, unless otherwise specified, "plurality" means two or more. The term "and/or" or the character "/" in this application is just an association relationship describing associated objects, indicating that there can be three relationships, for example, A and/or B, or A/B, which can represent: A alone exists, A and B exist simultaneously, and B exists alone.

First, let’s describe the application scenarios of this application.

Figure 1 is a plan view of an exemplary application scenario 100. In the illustrated embodiment, the application scenario 100 includes a beacon device 110a. The beacon device 110a can use a short-range communication link to broadcast a beacon message to the mobile devices (102a and 102b). For example, the beacon message can be a beacon communication format based on Eddystone. This standard is mainly used to help developers use Beacons hardware and provide Location-based communication transmission for smartphones. Applications running on mobile devices (102a and 102b) (or services deployed in mobile devices (102a and 102b)) may perform corresponding presentations to users on mobile devices (102a and 102b) based on beacon messages, e.g. Display messages, etc. The application scenario 100 may include retail stores, museums, sports venues, restaurants, etc. and is applicable to any environment where beacons are configured.

Beacon device 110a and mobile devices (102a and 102b) may broadcast and/or receive beacon messages using short-range radio technology such as Bluetooth™ or near field communication (NFC) technology. In some implementations, beacon device 110a may use a specific type of Bluetooth ^™ , called Bluetooth low energy (BLE). The wireless communication range of the beacon device 110a may be between 10 meters and 30 meters. Other ranges are also possible. When mobile devices (102a and 102b) are within wireless communication range of beacon device 110a, the mobile devices may receive corresponding beacon messages.

Various embodiments of mobile devices (102a and 102b) include smartphones, tablets, laptops, or wearable computers. In some implementations, mobile devices (102a and 102b) may include wireless receivers or transceivers that may scan environment 100 for beacon messages from other devices in environment 100, such as beacon devices. For example, mobile devices (102a and 102b) may include a BLE receiver that scans for beacon messages. Mobile devices (102a and 102b) may communicate with the server utilizing base stations of wireless networks, such as those based on Long Term Evolution (LTE) or Code Division Multiple Access (CDMA) (eg, CDMA2000 and Wideband CDMA (WCDMA)). Other types of wireless networks are also possible.

Figure 2 shows an illustration of a system for processing beacon messages. Mobile devices (202a and 202b) may communicate via one or more wireless networks, for example. For example, a base station 203 of a wireless network (such as a cellular network) may communicate with a wide area network (WAN) 206 (such as the Internet) by utilizing a gateway 205. Likewise, an access point (AP) 204, such as a wireless access point based on the IEEE 802.11 family, may provide communication access to the wide area network 206. Mobile devices (202a and 202b) may communicate with one or more servers (207, 208), such as via base station 203, access point 204, or a combination thereof. Servers (207, 208) may include network interfaces configured to communicate with devices such as device mobile devices (202a and 202b). Servers (207, 208) may include devices configured to communicate with devices such as mobile devices (202a and 202b) via network interfaces using protocols such as transmission control protocol (TCP) or user datagram protocol (UDP). Processor electronics that communicate with a device.

Mobile devices (202a and 202b) may also receive beacon messages from beacon devices (201a, 201b and 201c) via short-range communication links. In some implementations, the short-range communication link may be based on Bluetooth wireless technology. In some implementations, the short-range communication link may be based on NFC wireless technology. In some implementations, mobile devices (202a and 202b) may be configured to continuously scan for beacon messages. In some implementations, mobile devices (202a and 202b) may be configured to scan for beacon messages based on applications that invoke a beacon scanning application programming interface (API).

In some implementations, based on receiving beacon messages from beacon devices (201a, 201b, and 201c) via short-range communication links, mobile devices (202a and 202b) may communicate via long-range communication with base station 203 that provides cellular data services. A distance communication link establishes communication with one or more servers (207, 208).

In more detail, beacon device 110a may be configured (locally or remotely via a network) to send a beacon message, which in some implementations may include a beacon identification. In the server 208 on the cloud side, the application developer can pre-configure the mapping relationship between the beacon identification and the beacon attachment. After the corresponding application on the mobile device scans and obtains the beacon message, it can send the beacon identification to the server. 208. The server 208 can determine the beacon attachment corresponding to the beacon identification based on the preconfigured mapping relationship between the beacon identification and the beacon attachment, and send the beacon attachment to the corresponding application on the mobile device (102a and 102b). , the application can trigger the rendering of the corresponding beacon attachment.

It should be noted that the application can be configured with a mapping between the beacon attachment and the corresponding message data. After obtaining the beacon attachment, the application can trigger the corresponding presentation of the message data on the mobile device.

It should be noted that the presentation method of the above message data may not be limited to displaying the data on the screen of the mobile device. In some implementations, presenting message data may include providing one or more notifications. The presentation of message data may include force feedback (e.g., vibration indication), audio output (e.g., beeps, music, etc.), visual output (e.g., flash), or a combination thereof. In some implementations, message data may include any content, including but not limited to text, graphics, digital images, audio, video, and animation. Message data can be presented on the mobile device in the form of audio output to collaborate with mobile devices that do not have display capabilities. In some implementations, presenting the message data may include retrieving content corresponding to one or more values included in the message data; and causing the content to be displayed on the screen.

Beacon devices (201a, 201b, and 201c) may include circuitry such as a processor, memory, and a transmitter for broadcasting beacon messages, and an interface for programming the beacon devices (201a, 201b, and 201c). It may be a USB interface or a two-way wireless interface such as a network interface based on LTE or IEEE 802.11. In some implementations, beacon devices (201a, 201b, and 201c) may be programmed to periodically update data within beacon messages. The beacon devices (201a, 201b, and 201c) may transmit different opcodes, such as different message values, at different times of the day.

In some existing scenarios, after receiving the message attachment, the mobile device needs to further call a third-party service (the third-party service can be deployed on the server 208 or the server 207). The purpose may be to obtain the message based on calling the third-party service. Necessary data on which data presentation depends, or so that third-party services can obtain relevant information of the mobile device and then implement corresponding services.

The following takes the store marketing scenario as an example to explain how mobile devices, beacon devices, and servers can interact. In other scenarios, the interaction process of these three devices is similar, and the difference is mainly reflected in the interactive content. For example: The application is configured with a marketing message "Customers who register for a membership card for the first time can get a coupon of 50 off 100 yuan, and old customers can get a coupon of 30 off 100 yuan by signing in." The marketing information can be triggered to be displayed on the mobile device when the mobile device is in certain places (such as stores). These places can be deployed with beacon devices that periodically send a certain beacon identification (carrying beacon information). , the server side can be configured with a beacon attachment corresponding to the beacon identification. The beacon attachment can trigger the mobile device to display the above marketing information. Then, when the mobile device moves within the range of these beacon devices, it can receive Include the beacon information of the above-mentioned beacon identification, and forward the beacon identification to the server side. The server can deliver the beacon attachment corresponding to the beacon identification to the mobile device, and the corresponding application on the mobile device obtains the information. After marking the attachment, you need to check whether the current application user has registered a membership card. If the user of the application has not registered a membership card, it will prompt "Customers who register for a membership card for the first time can receive a coupon of 50% off for purchases over 100 yuan". If the user of the application has registered a membership card, it will prompt "Old customers can get 100 off 30 coupons by signing in. In this case, after the corresponding application on the mobile device obtains the beacon attachment, it needs to cache it first Get up, initiate another network request, query the third-party service for additional information (such as whether the user has registered as a member), and finally decide what action should be taken (such as a pop-up window prompting new customer discount information or old member discount information).

The disadvantage of the above process is that the action of determining whether to call a third-party service is done on the mobile device side. When the preset conditions need to be modified, the business logic of the App on the mobile device side needs to be modified accordingly, which greatly increases the overall complexity. The time consuming process. Furthermore, the beacon attachment provided by the server 208 is static (only returns a string based on the beacon identification) and cannot be linked with subsequent existing services of the application (such as querying member status). As a result, the mobile device may need to interact with different third-party services multiple times, resulting in large business delays and affecting the user experience of the corresponding applications on the mobile device. And if the business logic needs to be modified, for example, it can be modified to prompt old customers that "Customers who register for a membership card for the first time can get a coupon of 50 off 100, and old customers can get a coupon of 30 off 100 when they sign in." To attract old customers to guide their peers. When a person (new customer) registers as a member, he needs to modify the business logic of the corresponding application on the mobile device, re-publish the application on the application market, and allow users to upgrade the application. The whole process takes a long time and it is difficult to achieve marketing goals quickly. Moreover, the corresponding application on the mobile device performs an identity verification once when communicating with the server 208. Subsequent communication between the corresponding application on the mobile device and the third-party cloud service requires another identity verification process. Multiple identity verification processes increase. This increases the attack surface of network attacks and reduces security.

In order to solve the above problems, an embodiment of the present application provides a system. Refer to Figure 3. Figure 3 is a flow diagram of a system and its execution steps provided by an embodiment of the present application. As shown in Figure 3, the present application The system provided by the embodiment includes:

A mobile device configured to receive a beacon message from a beacon device, the beacon message including the target beacon identification;

Wherein, the mobile device is configured to receive the target beacon identification 301 from the beacon device.

In some implementations, the mobile device periodically performs scanning to discover beacon messages from beacon devices adjacent to the location of the mobile device, the beacon messages including target beacon identifications. As used herein, "proximity" refers to a mobile device being physically close enough to a beacon device to receive radio frequency (RF) signals transmitted by the beacon device. For example, a wireless transceiver on a mobile device may initiate a short-range scan to discover RF signals, such as BLE RF signals, near field communication (NFC) RF signals, and ultrasonic signals.

In some specific implementations, after receiving a beacon message from a beacon device, the mobile device can obtain beacon data based on the beacon message, where the beacon data includes at least one of the following: the mobile device The distance to the beacon device, the time when the mobile device receives the beacon message, or the identity of the mobile device.

Specifically, the mobile device may obtain the distance information between the mobile device and the beacon device based on the signal strength value of the received beacon message, where the distance information may include at least one of the following: The distance value between the mobile device and the beacon device, and the change information of the distance value between the mobile device and the beacon device.

In some implementations, the mobile device may calculate an average RSSI value based on a received signal strength indication (RSSI) value of the beacon message and average the RSSI values. In some implementations, RSSI may be mathematically defined as approximately the ratio of the power of the received signal to a reference received power (e.g., 1 mW), where the higher the RSSI value (or the less negative the value), the stronger the signal. In some implementations, the RSSI value can be expressed in dBm. Based on the predetermined transmission power used to send the beacon message, the distance estimate may be calculated based on the RSSI value. Determining the range estimate may include using channel quality information such as bit error rate (BER) or packet error rate (PER) derived from received beacon messages.

The change information of the distance value between the mobile device and the beacon device may include the change information of the distance value between the mobile device and the beacon device. The change trend of the distance, for example, from far to near, from near to far, etc. wait.

In this embodiment of the present application, the time information may include at least one of the following: the time when the mobile device receives the beacon message, and the time when the mobile device is within the signal coverage area of the beacon device. The time information may include the time the App user scanned the beacon device, the time the App user stayed around the beacon device, etc.

For example, the beacon message can be a beacon communication format based on Eddystone, which is a standard mainly used to help developers use Beacons hardware and provide location-based smartphone communication transmission. In one implementation, the beacon message may include a beacon identifier and activity parameters. The beacon identifier may include a text string such as "com.company.retailstore_no_3954" or a hexadecimal value such as "0x0e33de54". Other types of identifiers are also possible. In some implementations, activity parameters may include action values or strings. In some implementations, activity parameters may include message values or message strings. Other types of activity parameters are also possible.

The beacon message may include a beacon universally unique identifier (UUID). Within a certain area, multiple beacon devices with the same beacon identifier may be included. However, such beacons may have different values for the beacon UUID. Therefore, a UUID can be used to distinguish beacon devices that share the same beacon identifier. In some implementations, the beacon identifier includes a beacon UUID. In some implementations, the UUID is a 128-bit value.

The target beacon identifier in the embodiment of this application may include the beacon identifier in the above embodiment.

Beacon messages can also include application identifiers and user messages. The application identifier may identify an application running on the mobile device that is used to process the beacon message after the mobile device receives it. For example, an operating system running on a mobile device may use the application identifier to forward a beacon message to an application corresponding to the application identifier. In some implementations, if the application is not yet installed on the mobile device, a browser may be launched on the mobile device and the user may be directed (e.g., using a uniform resource locator (URL)) to a location where the user may download and install the corresponding application. The website of the application based on the application identifier. In some implementations, the application may be automatically downloaded without user intervention in a manner transparent to the user (e.g., as a background process). In some implementations, if When an application is installed but not running on a mobile device, the application can be automatically launched by the operating system running on the mobile device to receive beacon messages.

The mobile device may send the target beacon identification 302 to the server.

In this embodiment of the present application, after receiving the target beacon identification from the beacon device, the mobile device may send the target beacon identification to the server. Wherein, after receiving the target beacon identification from the beacon device, the application program or the underlying service on the mobile device may send the target beacon identification to the server.

Specifically, when the application on the mobile device scans a nearby beacon device, it can send a request to obtain the beacon message attachment to the server (beacon cloud service platform), and the request can carry the target beacon identification 302. The server can call the corresponding third-party service 303 based on the target beacon identification.

In the embodiment of this application, a service is an executable program that implements specific functions or provides specific content. For example, a service may be a web page developed using a programming language such as HyperText Markup Language (HTML), cascading style sheets (CSS), or Java script (JavaScript, JS) that can be accessed through a web browser. , or small programs, web applications or other types of applications developed through JS that do not require installation and can be used. The functions or content provided by the service are related to the type of service.

The third-party services involved in the embodiments of this application may refer to services used to provide third-party applications (applications, APPs). For example, a mobile device may support one or more applications, some of which may be applications downloaded by the mobile device from the network and provided by a third party (non-mobile device manufacturer). When a mobile device runs these applications, it can communicate with the third-party server corresponding to the application, and the third-party server can provide third-party services. Taking Huawei as the manufacturer of mobile devices and Tencent as the provider of WeChat as an example, after WeChat is installed on the mobile device, when the mobile device runs WeChat, it can communicate with the server corresponding to WeChat (that is, a third-party server).

In this embodiment of the present application, the server may determine the third-party service corresponding to the target beacon identification based on a pre-configured mapping relationship; wherein the mapping relationship includes multiple beacon identifications and a corresponding number corresponding to each beacon identification. Third Party Services. Among them, the mapping relationship can be pre-configured on the server by the application developer. The mapping relationship may include multiple beacon identifiers and third-party services corresponding to each beacon identifier. In one implementation, the third-party service in the mapping relationship may be the address where the third-party service is located, and the server may send a request to the third-party service. The address where the third-party service is located sends a target message, and the target message is generated based on the beacon identification. In one implementation, the third-party service in the mapping relationship may be an application programming interface API, then the server may call the application programming interface API corresponding to the third-party service. For example, the API can be a RESTful API, and the server can use the RESTful address preconfigured by the developer to call third-party services. The third-party service can be deployed on a server deployed separately by the developer, or it can be a deployed serverless function. In one implementation, the third-party service in the mapping relationship may be the address where the third-party service is located, and the server may initiate a call based on the remote procedure call protocol RPC to the address where the third-party service is located.

In one embodiment, the mobile device is configured to receive a beacon message from a beacon device, where the beacon message includes the target beacon identification; and obtain beacon data based on the beacon message, The beacon data includes at least one of the following: the distance between the mobile device and the beacon device, the time when the mobile device receives the beacon message, or the identity of the mobile device. , and sends the target beacon identification and the beacon data to the server; accordingly, the server is configured to call the corresponding third-party service based on the target beacon identification and the beacon data. . Specifically, the server is configured to determine the corresponding third-party service based on the target beacon identification, and call the third-party service based on the beacon data.

In the embodiment of this application, the server can determine which third-party service to call based on the target beacon identification. For example, it can determine which RESTful address to call based on the target beacon identification, or the destination address to send information, etc. At this time, the server can call the third-party service based on the beacon data.

In one implementation, the server can pass these beacon data as input parameters to the third-party service. In one implementation, the server can process the beacon data (such as mathematical statistics or other processing), and pass the processing results as input parameters to third-party services, etc.

In one embodiment, the server also determines whether the request meets the trigger conditions configured by the developer. If the trigger conditions are met, the third-party service is called. That is, if the server determines that the beacon data satisfies the preset condition, it calls the corresponding third-party service based on the target beacon identification. In the embodiment of this application, when the server receives the request sent by the mobile device, it can trigger the rule and generate an Applet rule instance. This rule instance can contain multiple states and use a state machine model commonly used in the industry. When the state machine reaches the end state, it can initiate a call to the address of the third-party service pre-configured by the developer. The specific methods include but are not limited to sending messages, initiating RPC calls, etc.

Specifically, the beacon data may include at least one of the following: the distance between the mobile device and the beacon device, or the time when the mobile device receives the beacon message. The distance information includes at least one of the following: a distance value between the mobile device and the beacon device, and change information of the distance value between the mobile device and the beacon device. The time information includes at least one of the following: the time when the mobile device receives the beacon message, and the time when the mobile device is within the signal coverage area of the beacon device.

Then, the triggering rule may be one or a combination of the following: the distance value between the mobile device and the beacon device satisfies the preset condition, the distance between the mobile device and the beacon device The value change information satisfies the preset condition, the time when the mobile device receives the beacon message satisfies the preset condition, and the time when the mobile device is within the signal coverage area of the beacon device satisfies the preset condition.

In the embodiment of the present application, in the process of triggering the call of third-party services, preset conditions for triggering are added to the server, including but not limited to the distance between the mobile device and the beacon device, or the distance between the mobile device and the beacon device, or the distance between the mobile device and the beacon device. The time at which the mobile device receives the beacon message satisfies preset conditions. When the mobile device application scans a specific beacon message, it will send the relevant beacon data to the server. The server can make rule judgments based on the beacon data and only call third-party services if the preset conditions are met. The advantage of this is that the preset conditions can be configured and modified on the server. Specifically, the server can receive condition modification information indicating that the preset conditions are modified to new conditions; based on the The condition modification information modifies the preset condition. Since the behavior of determining whether the preset conditions are met is not performed by the mobile device, the APP does not need to sense how the preset conditions need to be modified. When the preset conditions need to be modified, the server only needs to make corresponding modifications, which greatly Reduces the time consumption of the entire process. When the application developer needs to modify the above preset conditions, there is no need to modify the business logic of the App, and there is no need to re-publish the App on the application market, and there is no need to let users upgrade the App. The preset conditions can be modified directly on the server side. That’s it, greatly reducing the time-consuming process of the entire process.

Next, a diagram of the preconfigured mapping relationship is given:

Among them, the beacon identification corresponds to the beacon attachment, trigger target and trigger condition. The trigger target includes but is not limited to the RESTful address of the third-party cloud service (it can also be RPC, Remote Procedure Call, remote procedure call and other methods), and the trigger condition includes but is not limited to the time when the application user scans the beacon device, the application The time the application user stays around the beacon device, the distance between the application user and the beacon device, the changing trend of the distance, etc.

Referring to Figure 4, Figure 4 is a schematic flow diagram of a beacon data processing provided by an embodiment of the present application. As shown in Figure 4, the beacon device 401 sends a beacon message to the mobile device 402, and the mobile device will carry the target The request for the beacon identification is sent to the server 403 (cloud platform). The server can determine the beacon attachment corresponding to the target beacon identification based on the mapping relationship and determine the beacon attachment corresponding to the target beacon identification when the beacon data meets the preset conditions. The third-party service returns the beacon attachment to the mobile device 402 and calls the corresponding third-party service 404.

In this embodiment of the present application, if the server determines that the beacon data meets the preset conditions, it calls the corresponding third-party service based on the target beacon identification. Optionally, the third-party service can send reply data to the server, and the server can receive the reply data from the third-party service and send the reply data to the mobile device; accordingly, the mobile device can Trigger the corresponding presentation of the reply data.

Optionally, the third-party service can directly send the reply data to the mobile device; accordingly, the mobile device can trigger the corresponding presentation of the reply data. The presentation of data may not be limited to having the data displayed on the screen of a mobile device. In some implementations, presenting message data may include providing one or more notifications. The presentation of message data may include force feedback (e.g., vibration indication), audio output (e.g., beeps, music, etc.), visual output (e.g., flash), or a combination thereof. In some implementations, message data may include any content, including but not limited to text, graphics, digital images, audio, video, and animation. Message data can be presented on the mobile device in the form of audio output to collaborate with mobile devices that do not have display capabilities. In some implementations, presenting the message data may include retrieving content corresponding to one or more values included in the message data; and causing the content to be displayed on the screen.

Referring to Figure 5, Figure 5 is a system diagram provided by an embodiment of the present application. As shown in Figure 5, the server can include a rule/trigger configuration engine 501, a beacon attachment push engine 502, and a third-party service trigger engine. 503. Rule/trigger application engine 504 and memory 505; wherein, application developers (such as application developer 1 or application developer 2 shown in Figure 5) can configure rules/triggers based on the rule/trigger configuration engine 501 Configuration, so that the rule/trigger configuration is stored in the memory 505, where the rule/trigger configuration can be the mapping relationship between the above-mentioned target beacon identifier and the third-party service, and the preset conditions that need to be met to trigger the third-party service. . Applications (such as Application 1 and Application 2 shown in Figure 5) can send beacon messages to the server, and the rule/trigger application engine 504 can determine the target information in the beacon message based on the rule/trigger configuration in the memory 505. The beacon attachment corresponding to the beacon identification, and determining whether the beacon data carried by the beacon message meets the preset conditions, and based on the beacon attachment push engine 502, returns the beacon attachment to the corresponding application (such as shown in Figure 5 Application 1 or Application 2), and when the rule/trigger application engine 504 determines whether the beacon data carried in the beacon message meets the preset conditions, the third-party service trigger engine 503 triggers the call to the corresponding third-party service.

In more detail, in this embodiment of the application, the server can provide a platform for application developers to configure rules. The rules include several states, as well as jump relationships and jump conditions between states. For example, the Beacon Cloud Platform provides several rule templates and allows developers to customize rule logic. The Beacon Cloud Platform uses database and other technologies to store message rules. Optionally, the beacon cloud platform can provide a RESTful interface (instead of a Web interface) for developers to configure beacon IDs, beacon attachment messages, rule triggering conditions, rule triggering behaviors, etc.

Referring to Figure 6, Figure 6 is a schematic diagram of an administrator interface for rule/trigger configuration provided by an embodiment of the present application. As shown in Figure 6, some embodiments of the administrator interface may be a web-based graphical user interface. Or graphical user interface (GUI), the GUI is designed to interact with administrators (such as application developers, etc.) to implement rule/trigger configuration. In some embodiments, the GUI may be presented to the administrator by a browser application on the computing device. Specifically, the rule/trigger configuration interface may include a trigger rule configuration interface 601. For example, as shown in Figure 6, the "rule name" and "rule conditions" can be configured on the rule/trigger configuration interface. , where "rule conditions" can include configurations such as "within a specific time" and "scanning for beacons". In the input box corresponding to "within a specific time", time-related trigger conditions can be entered, such as when a beacon message is received. The time is weekend morning, etc. The corresponding beacon ID can be entered in the input box corresponding to "Scan for beacon". In addition, the interface for rule/trigger configuration may include a configuration interface 602 for triggering content. For example, you may enter in the input box corresponding to "Execute after satisfaction" shown in Figure 6 when the above-mentioned rules ("within a specific time" and When the rules corresponding to "scanning for beacons") are met, the third-party service that is called is triggered. The third-party service can be the address of the third-party service, application programming interface API, etc.

It should be pointed out that the control settings and arrangement of the GUI in Figure 6 are only for illustration and do not constitute a limitation on the present application.

Figure 7 shows more details than Figure 3. Specifically, when a mobile device approaches the beacon device 701, the application program (or underlying service) on it can scan the beacon signal and obtain the target information carrying it. The beacon message carrying the target beacon identification 702 is generated, and the corresponding beacon data is generated, and the beacon message carrying the target beacon identification and beacon data is forwarded to the server 703. If it is determined that the beacon data meets the preset conditions, based on The target beacon identifier calls the corresponding third-party service 704, and can receive the reply data 705 returned by the third-party service, and send the reply data 705 to the mobile device 706, or the mobile device can directly receive the third-party service After returning the reply data 707, the mobile device can perform corresponding presentation 708 based on the reply data 707.

Specifically, the embodiment of this application finds that the mobile device is configured to receive a beacon message from a beacon device, where the beacon message includes the target beacon identification; based on the beacon message, the beacon data is obtained , wherein the beacon data includes at least one of the following: the distance between the mobile device and the beacon device, the time when the mobile device receives the beacon message, or the identity of the mobile device identification; sending the target beacon identification and the beacon data to the server; and, the server is configured to, if it is determined that the beacon data satisfies a preset condition, based on the target beacon identification, Call the corresponding third-party service.

In an optional implementation, the distance information includes at least one of the following:

The distance value between the mobile device and the beacon device, and the change information of the distance value between the mobile device and the beacon device.

In an optional implementation, the time information includes at least one of the following:

The time when the mobile device receives the beacon message and the time when the mobile device is within the signal coverage area of the beacon device.

In an optional implementation, the server is configured to determine the third-party service corresponding to the target beacon identification based on a preconfigured mapping relationship; wherein the mapping relationship includes multiple beacon identifications and each A beacon identifies the corresponding third-party service.

In an optional implementation, the server is configured to determine the corresponding third-party service based on the target beacon identification; and call the third-party service based on the beacon data.

In an optional implementation, the server is configured to receive reply data from the third-party service; send the reply data to the mobile device; correspondingly, the mobile device is configured to trigger The reply data is presented accordingly.

In an optional implementation, the mobile device is configured to receive reply data from the third-party service; and trigger presentation corresponding to the reply data.

Embodiments of the present application provide a system, which includes: a mobile device configured to receive a target beacon identification from a beacon device; sending the target beacon identification to a server; and the server is configured to In order to call the corresponding third-party service based on the target beacon identification. The server side performs the call to the third-party service instead of the mobile device needing to call the third-party service after receiving the message attachment, which reduces business latency.

Next, two specific scenarios are used as illustrations to describe the beacon message processing method provided by the embodiment of the present application. Taking the scene of a shopping mall as an example, the checkout counter has multiple channels, and a beacon device is deployed in each channel. When consumers queue up at the checkout channel, they receive marketing information, such as "Use Huawei Wallet to pay and enjoy a 10% discount." At the same time, the background server of the beacon device counts the number of people at the checkout counter. If there are too many people queuing up at the checkout channel, the administrator is notified. Coordinate more cashiers, open more cashier channels, and reduce consumers' queuing time.

The developer deploys rules on the server (beacon cloud platform): when the application user scans the beacon signal (that is, the mobile device reports the beacon message) (meaning that a customer enters the checkout channel), the count is increased by one. When the application user leaves the range of the beacon device from near to far (representing the customer leaving the checkout lane), the count is decremented by one. If the count exceeds 200, a RESTful address is called to implement the function of sending notifications to the mall administrator.

The optional implementation solution of the beacon cloud platform is to provide a web interface for developers to configure the corresponding functions of the beacon. Developers log in to the web interface. The beacon cloud platform provides a configuration interface for developers to fill in beacon identification, beacon message attachments, and rule logic that triggers third-party service calls. In the rule logic interface, the beacon cloud platform can provide some predefined conditions, such as "the number of people who scanned the beacon". After the developer selects the conditions, he can set the target as "200" and the message action as " Send Email" and enter your email address.

The Beacon Cloud Platform records the content input by developers through the database. The Beacon Cloud Platform provides developers with an SDK for developing applications. When consumers use the application, the beacon SDK automatically and periodically scans nearby beacon devices. When a specific beacon is scanned, the beacon SDK sends a message to the beacon cloud platform. When the beacon cloud platform receives the request message, it queries the message attachment corresponding to the beacon identifier from the database, and constructs a response data packet and sends it to the mobile application. At the same time, the beacon cloud platform queries the message rules corresponding to the beacon from the database, updates the count of people near the beacon, and determines whether the count exceeds the threshold preset by the developer, then sends an email to the specified email address.

In another scenario, the Beacon scanning function can be implemented by a third-party program other than the App (such as a resident process provided by the underlying service). As a result, mobile phone users do not need to install the target App. The developer of the target App deploys its code logic as an Applet on the Beacon cloud platform to implement specific functions.

Specifically, when a nearby Beacon is scanned, a corresponding message can be reported to the Beacon cloud platform, indicating that the mobile phone has encountered a certain Beacon. App developers configure the rule logic corresponding to the Beacon they own on the Beacon cloud platform. The specific configuration method may use the solutions provided in the above embodiments. The execution process can be shown in Figure 8. For example, Beacon is deployed in a certain brand of furniture store, but the brand's App is not installed on the consumer's mobile phone. Scan surrounding Beacons and send them to the Beacon cloud platform for analysis. The cloud platform queries the message rules corresponding to the scanned Beacons and distributes the Beacon scanning events to the back-end server of the brand. The brand's back-end server can perform processing such as people flow statistics and user shopping behavior analysis.

Referring to Figure 9, Figure 9 is a flow diagram of a beacon message processing method provided by an embodiment of the present application. As shown in Figure 9, the method is applied to a server. The beacon message processing method provided by an embodiment of the present application Methods include:

901. Receive the target beacon identification from the mobile device.

902. Based on the target beacon identification, call the corresponding third-party service.

In an optional implementation, the third-party service corresponding to the target beacon identification can be determined based on a preconfigured mapping relationship; wherein the mapping relationship includes multiple beacon identifications and a corresponding service corresponding to each beacon identification. Third Party Services.

In an optional implementation, a target message may be sent to the address where the third-party service is located, and the target message is generated based on the beacon identification.

In an optional implementation, the application programming interface API corresponding to the third-party service can be called.

In an optional implementation, a call based on the remote procedure call protocol RPC can be initiated to the address where the third-party service is located.

In an optional implementation, beacon data from the mobile device may be received, wherein the beacon data includes at least one of the following: a distance between the mobile device and the beacon device, and The time when the mobile device receives the beacon message, or the identity of the mobile device; based on the target beacon identity and the beacon data, call the corresponding third-party service.

In an optional implementation, the corresponding third-party service can be determined based on the target beacon identification; and the third-party service can be called based on the beacon data.

In an optional implementation, reply data from the third-party service may be received; and the reply data may be sent to the mobile device so that the mobile device triggers the corresponding presentation of the reply data.

The relevant descriptions of step 901 and step 902 may refer to the descriptions related to FIGS. 3 to 8 in the above embodiments, and will not be described again here.

Referring to Figure 10, Figure 10 is a flow diagram of a beacon message processing method provided by an embodiment of the present application. As shown in Figure 10, the method is applied to a server. The beacon message processing method provided by an embodiment of the present application Methods include:

1001. Receive a target beacon identification and beacon data from a mobile device, where the beacon data includes at least one of the following: the distance between the mobile device and the beacon device, and the distance received by the mobile device. The time of the beacon message or the identity of the mobile device.

1002. When the beacon data meets the preset conditions, call the corresponding third-party service based on the target beacon identification.

In an optional implementation, the distance information includes at least one of the following:

The distance value between the mobile device and the beacon device, and the change information of the distance value between the mobile device and the beacon device.

In an optional implementation, the time information includes at least one of the following:

The time when the mobile device receives the beacon message and the time when the mobile device is within the signal coverage area of the beacon device.

In an optional implementation, the third-party service corresponding to the target beacon identification can be determined based on a preconfigured mapping relationship; wherein the mapping relationship includes multiple beacon identifications and a corresponding service corresponding to each beacon identification. Third Party Services.

In an optional implementation, the corresponding third-party service can be determined based on the target beacon identification; and the third-party service can be called based on the beacon data.

In an optional implementation, reply data from the third-party service may be received;

The reply data is sent to the mobile device so that the mobile device triggers presentation corresponding to the reply data.

In an optional implementation, condition modification information may also be received, and the condition modification information indicates that the preset condition is modified to a new condition; and the preset condition is modified based on the condition modification information.

For relevant descriptions of step 1001 and step 1002, please refer to Figures 3 to 8 and related descriptions in the above embodiment, and will not be described again here.

Referring to Figure 11, Figure 11 is a schematic diagram of a beacon message processing device provided by an embodiment of the present application. As shown in Figure 11, a beacon message processing device 1100 provided by an embodiment of the present application includes:

The receiving module 1101 is used to receive the target beacon identification from the mobile device.

The calling module 1102 is used to call the corresponding third-party service based on the target beacon identification.

In an optional implementation, the device further includes:

The determination module 1103 is configured to determine the third-party service corresponding to the target beacon identification based on a preconfigured mapping relationship; wherein the mapping relationship includes multiple beacon identifications and the third-party service corresponding to each beacon identification.

In an optional implementation, the calling module 1102 is configured to send a target message to the address where the third-party service is located, where the target message is generated based on the beacon identification.

In an optional implementation, the calling module 1102 is used to call the application programming interface API corresponding to the third-party service.

In an optional implementation, the calling module 1102 is configured to initiate a call based on the remote procedure call protocol RPC to the address where the third-party service is located.

In an optional implementation, the receiving module 1101 is configured to receive beacon data from the mobile device, where the beacon data includes at least one of the following:

The distance between the mobile device and the beacon device, the time when the mobile device receives the beacon message, or the identity of the mobile device;

Based on the target beacon identification and the beacon data, the corresponding third-party service is called.

In an optional implementation, the calling module 1102 is configured to determine the corresponding third-party service based on the target beacon identification; and call the third-party service based on the beacon data.

In an optional implementation, the receiving module 1101 is configured to receive reply data from the third-party service;

A sending module, configured to send the reply data to the mobile device, so that the mobile device triggers the corresponding presentation of the reply data.

The beacon message processing device provided by the embodiment of the present application may also include:

Receiving module 1101, configured to receive a target beacon identification and beacon data from a mobile device, where the beacon data includes at least one of the following: the distance between the mobile device and the beacon device, and the The time when the mobile device receives the beacon message, or the identity of the mobile device; and,

The calling module 1102 is configured to call the corresponding third-party service based on the target beacon identification if it is determined that the beacon data meets the preset conditions.

In an optional implementation, the distance information includes at least one of the following:

The distance value between the mobile device and the beacon device, and the change information of the distance value between the mobile device and the beacon device.

In an optional implementation, the time information includes at least one of the following:

The time when the mobile device receives the beacon message and the time when the mobile device is within the signal coverage area of the beacon device.

In an optional implementation, the device further includes:

The determination module determines the third-party service corresponding to the target beacon identification based on the pre-configured mapping relationship; wherein the mapping relationship includes multiple beacon identifications and the third-party service corresponding to each beacon identification.

In an optional implementation, the calling module 1102 is configured to determine the corresponding third-party service based on the target beacon identification; and call the third-party service based on the beacon data.

In an optional implementation, the receiving module 1101 is configured to receive reply data from the third-party service;

A sending module, configured to send the reply data to the mobile device, so that the mobile device triggers the corresponding presentation of the reply data.

In an optional implementation, the receiving module 1101 is configured to receive condition modification information indicating that the preset condition is modified to a new condition; and the preset condition is modified based on the condition modification information. Set conditions.

This application does not specifically limit the type of mobile device mentioned. The mobile device can be a mobile phone, a tablet computer, a personal digital assistant (PDA), a wearable device, a laptop computer (laptop) and other portable mobile devices. . Exemplary embodiments of portable mobile devices include, but are not limited to, portable mobile devices running iOS, Android, Microsoft, or other operating systems. The above-mentioned portable mobile device may also be other portable mobile devices, such as a laptop computer (laptop) with a touch-sensitive surface (such as a touch panel). It should also be understood that in some other embodiments of the present application, the mobile device may not be a portable mobile device, but a desktop computer with a touch-sensitive surface (such as a touch panel).

Referring to Figure 12, Figure 12 shows a schematic structural diagram of an electronic device 100 provided by an embodiment of the present application.

The electronic device 100 may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, and an antenna 2. , mobile communication module 150, wireless communication module 160, audio module 170, speaker 170A, receiver 170B, microphone 170C, headphone interface 170D, sensor module 180, button 190, motor 191, indicator 192, camera 193, display screen 194, and Subscriber identification module (SIM) card interface 195, etc. The sensor module 180 may include a pressure sensor 180A, a gyro sensor 180B, an air pressure sensor 180C, a magnetic sensor 180D, an acceleration sensor 180E, a distance sensor 180F, a proximity light sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, and ambient light. Sensor 180L, bone conduction sensor 180M, etc.

It can be understood that the structure illustrated in the embodiment of the present application does not constitute a specific limitation on the electronic device 100 . In other embodiments of the present application, the electronic device 100 may include more or fewer components than shown in the figures, or some components may be combined, some components may be separated, or some components may be arranged differently. The components illustrated may be implemented in hardware, software, or a combination of software and hardware.

The processor 110 may include one or more processing units. For example, the processor 110 may include an application processor (application processor, AP), a modem processor, a graphics processing unit (GPU), an image signal processor ( image signal processor (ISP), controller, video codec, digital signal processor (digital signal processor, DSP), baseband processor, and/or neural network processing unit (NPU), etc. Among them, different processing units can be independent devices or integrated in one or more processors.

The controller can generate operation control signals based on the instruction operation code and timing signals to complete the control of fetching and executing instructions.

The processor 110 may also be provided with a memory for storing instructions and data. In some embodiments, the memory in processor 110 is cache memory. This memory may hold instructions or data that have been recently used or recycled by processor 110. If the processor 110 needs to use the instructions or data again, it can be called directly from the memory. Repeated accesses are avoided and the waiting time of the processor 110 is reduced, thus improving the efficiency of the system.

In some embodiments, processor 110 may include one or more interfaces. The interface may include an integrated circuit (inter-integrated circuit, I2C) interface, an integrated circuit built-in audio (inter-integrated circuitsound, I2S) interface, a pulse code modulation (PCM) interface, and a universal asynchronous receiver (universal asynchronous receiver) /transmitter, UART) interface, mobile industry processor interface (MIPI), general-purpose input/output (GPIO) interface, subscriber identity module (subscriber identity module, SIM) interface, and/or Universal serial bus (USB) interface, etc.

The software system of the electronic device 100 may adopt a layered architecture, an event-driven architecture, a microkernel architecture, a microservice architecture, or a cloud architecture. The embodiment of this application takes the Android system with a layered architecture as an example to illustrate the software structure of the electronic device 100 .

Figure 13 is a software structure block diagram of the electronic device 100 according to the embodiment of the present application.

The layered architecture divides the software into several layers, and each layer has clear roles and division of labor. The layers communicate through software interfaces. In some embodiments, the Android system is divided into four layers, from top to bottom: application layer, application framework layer, Android runtime (Android runtime) and system libraries, and kernel layer.

The application layer can include a series of application packages.

As shown in Figure 13, the application package can include applications such as camera, gallery, calendar, call, map, navigation, WLAN, Bluetooth, music, video, short message, etc.

The application framework layer provides an application programming interface (API) and programming framework for applications in the application layer. The application framework layer includes some predefined functions.

As shown in Figure 13, the application framework layer can include a window manager, content provider, view system, phone manager, resource manager, notification manager, etc.

A window manager is used to manage window programs. The window manager can obtain the display size, determine whether there is a status bar, lock the screen, capture the screen, etc. In this embodiment of the present application, the window manager can obtain the sizes of the two display screens provided by the electronic device 100, and uniformly manage the content displayed on the two display screens.

Content providers are used to store and retrieve data and make this data accessible to applications. Said data can include videos, images, audio, calls made and received, browsing history and bookmarks, phone books, etc.

The view system includes visual controls, such as controls that display text, controls that display pictures, etc. View systems can be used to build applications. The display interface can be composed of one or more views. For example, a display interface including a text message notification icon may include a view for displaying text and a view for displaying pictures.

The phone manager is used to provide communication functions of the electronic device 100 . For example, call status management (including connected, hung up, etc.).

The resource manager provides various resources to applications, such as localized strings, icons, pictures, layout files, video files, etc.

The notification manager allows applications to display notification information in the status bar, which can be used to convey notification-type messages and can automatically disappear after a short stay without user interaction. For example, the notification manager is used to notify download completion, message reminders, etc. The notification manager can also be notifications that appear in the status bar at the top of the system in the form of charts or scroll bar text, such as notifications for applications running in the background, or notifications that appear on the screen in the form of conversation windows. For example, text information is prompted in the status bar, a prompt sound is emitted, the mobile device vibrates, and the indicator light flashes, etc.

Android Runtime includes core libraries and virtual machines. The Android runtime is responsible for the scheduling and management of the Android system.

The core library contains two parts: one part is the functional functions that need to be called by the Java language, and the other part is the core library of Android.

The application layer and application framework layer run in virtual machines. The virtual machine executes the java files of the application layer and application framework layer as binary files. The virtual machine is used to perform object life cycle management, stack management, thread management, security and exception management, and garbage collection and other functions.

System libraries can include multiple functional modules. For example: surface manager (surface manager), media libraries (Media Libraries), 3D graphics processing library (for example: OpenGL ES), 2D graphics engine (for example: SGL), etc.

The surface manager is used to manage the display subsystem and provides the fusion of 2D and 3D layers for multiple applications.

The media library supports playback and recording of a variety of commonly used audio and video formats, as well as static image files, etc. The media library can support a variety of audio and video encoding formats, such as: MPEG4, H.264, MP3, AAC, AMR, JPG, PNG, etc.

The 3D graphics processing library is used to implement 3D graphics drawing, image rendering, composition, and layer processing.

2D Graphics Engine is a drawing engine for 2D drawing.

The kernel layer is the layer between hardware and software. The kernel layer includes at least display driver, camera driver, audio driver, and sensor driver.

Figure 14 shows a schematic structural diagram of a server 1400. The server 14 can implement the functions of the server mentioned above. The server 1400 may include a memory 1401, a processor 1402, and a transceiver 1403. Among them, the memory 1401, the processor 1402 and the transceiver 1403 are connected through a bus. The memory 1401 is used to store computer instructions. When the computer instructions are executed by the processor 1402, the processor 1402 can perform the execution steps in the embodiments shown in Figures 9 and 10. The processor 1402 can also execute instructions stored in the memory 1401 to trigger the transceiver 1403 to perform an operation of establishing a communication connection with other devices.

The transceiver 1403 can be used to send and receive data sent by other devices. For example, transceiver 1403 may include a receiver and a transmitter. The receiver may be used to perform 901 in the embodiment shown in FIG. 9, 1001 in the embodiment shown in FIG. 10, and/or other processes to support the technology described herein. All relevant content of each step involved in the above method embodiments can be quoted from the functional description of the corresponding functional module, and will not be described again here.

In the software architecture corresponding to the embodiments of this application, the server can also be understood as a cloud platform that provides beacon data and related processing functions. The cloud platform has message attachments, triggered third-party services and corresponding corresponding beacon identifiers for developers to configure. The function of triggering rules, in which the configuration method can be through the Web interface, or through the RESTful programming interface, etc. The cloud platform has the function of receiving beacon identification and beacon data sent by mobile devices. The cloud platform will determine whether the "rules for triggering third-party services" on the cloud platform are satisfied based on the received beacon data. If so, it will call the third party Serve. Specifically, reference can be made to the execution steps related to the server in Figures 3 to 10 in the above embodiments. The above cloud platform can be deployed in a server or a server cluster, which is not limited here.

Those skilled in the art can clearly understand that for the convenience and simplicity of description, the specific working processes of the above-described systems, devices and units can be referred to the corresponding processes in the foregoing method embodiments, and will not be described again here.

In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only illustrative. For example, the division of units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated. to another system, or some features can be ignored, or not implemented. On the other hand, the coupling or direct coupling or communication connection between each other shown or discussed may be through some interfaces, and the indirect coupling or communication connection of the devices or units may be in electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place, or they may be distributed to multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in various embodiments of the present application can be integrated into one processing unit, or each unit can exist physically alone, or two or more units can be integrated into one unit. The above integrated units can be implemented in the form of hardware or software functional units.

If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or contributes to the existing technology, or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium , including several instructions to cause a computer device (which may be a personal computer, a server, or other network device, etc.) to execute all or part of the steps of the method described in the embodiments of this application. The aforementioned storage media include: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), magnetic disk or optical disk and other media that can store program code. .

As mentioned above, the above embodiments are only used to illustrate the technical solution of the present application, but not to limit it. Although the present application has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that they can still make the foregoing technical solutions. The technical solutions described in each embodiment may be modified, or some of the technical features may be equivalently replaced; however, these modifications or substitutions do not cause the essence of the corresponding technical solutions to depart from the scope of the technical solutions in each embodiment of the present application.

Claims (26)

1. A system, the system comprising:

a mobile device configured to receive a beacon message from a beacon device, the beacon message including a target beacon identification; based on the beacon message, beacon data is acquired, wherein the beacon data includes information indicating at least one of the following parameters:

a distance between the mobile device and the beacon device, and a time at which the beacon message was received by the mobile device;

transmitting the target beacon identification and the beacon data to a server; the method comprises the steps of,

and the server is configured to call the corresponding third party service based on the target beacon identifier under the condition that the beacon data meets the preset condition.

2. The system of claim 1, wherein the distance information comprises at least one of:

and the distance value between the mobile device and the beacon device and the change information of the distance value between the mobile device and the beacon device.

3. The system of claim 1 or 2, wherein the time information comprises at least one of:

the time the beacon message is received by the mobile device, the time the mobile device is within the signal coverage area of the beacon device.

4. The system of claim 1 or 2, wherein the third party service is a service provided by a first application, the mobile device configured to receive a beacon message from a beacon device based on a second application, the first application and the second application being different; or alternatively, the first and second heat exchangers may be,

the third party service is a service provided by a first application, and the mobile device is configured to receive a beacon message from a beacon device based on a system service of the mobile device.

5. The system according to claim 1 or 2, wherein the beacon data comprises information indicating a distance between the mobile device and the beacon device, the preset condition comprising at least one of:

The distance value between the mobile device and the beacon device is within a preset range;

the distance value between the mobile device and the beacon device is changed from large to small; and, a step of, in the first embodiment,

the distance value between the mobile device and the beacon device is changed from small to large.

6. The system of claim 1, wherein the beacon data includes information indicating a time at which the beacon message was received by the mobile device;

the preset conditions at least comprise one of the following:

the time of the mobile device receiving the beacon message is within a preset range; and, a step of, in the first embodiment,

the time that the mobile device is within the signal coverage area of the beacon device is within a preset range.

7. The system according to claim 1 or 2, wherein the server is configured to determine, based on a pre-configured mapping relationship, a third party service to which the target beacon identification corresponds; the mapping relation comprises a plurality of beacon identifications and third party services corresponding to each beacon identification.

8. The system of claim 1 or 2, wherein the server is configured to receive reply data from the third party service; transmitting the reply data to the mobile device; correspondingly, the mobile device is configured to trigger presentation of the response data; or alternatively, the first and second heat exchangers may be,

The mobile device configured to receive reply data from the third party service; triggering the corresponding presentation of the reply data.

9. The system according to claim 1 or 2, wherein the server is configured to receive condition modification information indicating modification of the preset condition to a new condition; and modifying the preset condition based on the condition modification information.

10. A beacon message processing method, applied to a server, the method comprising:

receiving a target beacon identification and beacon data from a mobile device, wherein the beacon data includes at least one of: a distance between the mobile device and a beacon device, and a time at which the beacon message was received by the mobile device; the method comprises the steps of,

and under the condition that the beacon data meets the preset condition, calling a corresponding third party service based on the target beacon identifier.

11. The method of claim 10, wherein the distance information comprises at least one of:

and the distance value between the mobile device and the beacon device and the change information of the distance value between the mobile device and the beacon device.

12. The method according to claim 10 or 11, wherein the time information comprises at least one of:

the time the beacon message is received by the mobile device, the time the mobile device is within the signal coverage area of the beacon device.

13. The method according to claim 10 or 11, wherein the beacon data comprises information indicating a distance between the mobile device and the beacon device, the preset condition comprising at least one of:

the distance value between the mobile device and the beacon device is within a preset range;

the distance value between the mobile device and the beacon device is changed from large to small; and, a step of, in the first embodiment,

the distance value between the mobile device and the beacon device is changed from small to large.

14. The method of claim 10, wherein the beacon data includes information indicating a time at which the beacon message was received by the mobile device;

the preset conditions at least comprise one of the following:

the time of the mobile device receiving the beacon message is within a preset range; and, a step of, in the first embodiment,

the time that the mobile device is within the signal coverage area of the beacon device is within a preset range.

15. The method according to claim 10 or 11, characterized in that the method further comprises:

determining a third party service corresponding to the target beacon identifier based on a pre-configured mapping relation; the mapping relation comprises a plurality of beacon identifications and third party services corresponding to each beacon identification.

16. The method according to claim 10 or 11, characterized in that the method further comprises:

receiving reply data from the third party service;

and sending the reply data to the mobile equipment so that the mobile equipment triggers the corresponding presentation of the reply data.

17. The method according to claim 10 or 11, characterized in that the method further comprises:

receiving condition modification information, wherein the condition modification information indicates that the preset condition is modified to be a new condition; and modifying the preset condition based on the condition modification information.

18. A beacon message processing apparatus for use with a server, said apparatus comprising:

a communication interface for receiving a target beacon identification and beacon data from a mobile device, wherein the beacon data comprises at least one of: a distance between the mobile device and a beacon device, and a time at which the beacon message was received by the mobile device; the method comprises the steps of,

And the processing circuit is used for calling the corresponding third party service based on the target beacon identifier under the condition that the beacon data meets the preset condition.

19. The apparatus of claim 18, wherein the distance information comprises at least one of:

and the distance value between the mobile device and the beacon device and the change information of the distance value between the mobile device and the beacon device.

20. The apparatus of claim 18 or 19, wherein the time information comprises at least one of:

the time the beacon message is received by the mobile device, the time the mobile device is within the signal coverage area of the beacon device.

21. The apparatus of claim 18 or 19, wherein the beacon data includes information indicating a distance between the mobile device and the beacon device, and wherein the preset condition includes at least one of:

the distance value between the mobile device and the beacon device is within a preset range;

the distance value between the mobile device and the beacon device is changed from large to small; and, a step of, in the first embodiment,

the distance value between the mobile device and the beacon device is changed from small to large.

22. The apparatus of claim 18, wherein the beacon data includes information indicating a time at which the beacon message was received by the mobile device;

the preset conditions at least comprise one of the following:

the time of the mobile device receiving the beacon message is within a preset range; and, a step of, in the first embodiment,

the time that the mobile device is within the signal coverage area of the beacon device is within a preset range.

23. The apparatus of claim 18 or 19, wherein the processing circuit is further configured to determine, based on a pre-configured mapping relationship, a third party service to which the target beacon identifier corresponds; the mapping relation comprises a plurality of beacon identifications and third party services corresponding to each beacon identification.

24. The apparatus of claim 18 or 19, wherein the communication interface is further configured to receive reply data from the third party service;

and sending the reply data to the mobile equipment so that the mobile equipment triggers the corresponding presentation of the reply data.

25. The apparatus according to claim 18 or 19, wherein the communication interface is further configured to receive condition modification information, the condition modification information indicating modification of the preset condition to a new condition; the apparatus further comprises:

The processing circuit is used for modifying the preset condition based on the condition modification information.

26. A computer-readable medium comprising instructions that when executed by one or more processors are operable to perform the method of any of claims 10-17.