CN113810857A

CN113810857A - Beacon message processing method and system

Info

Publication number: CN113810857A
Application number: CN202010544418.4A
Authority: CN
Inventors: 郑凯; 拉胡尔·阿尔温德·贾达夫; 李柏潮; 李�杰
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2020-06-15
Filing date: 2020-06-15
Publication date: 2021-12-17
Anticipated expiration: 2040-06-15
Also published as: CN113810857B

Abstract

The embodiment of the application discloses a system, includes: receiving, by a mobile device, a beacon message from a beacon device, the beacon message including the target beacon identification; acquiring beacon data based on the beacon message; transmitting the target beacon identification and the beacon data to the server; and if the server determines that the beacon data meets the preset conditions, calling a corresponding third-party service based on the target beacon identification. The configuration of the preset condition can be carried out on the server, and since the behavior of judging whether the preset condition is met is not executed by the mobile equipment side, the APP of the mobile equipment does not need to sense the preset condition and needs to modify the preset condition, when the preset condition needs to be modified, the server is only needed to carry out corresponding modification, and the time consumption of the whole process is greatly reduced.

Description

Beacon message processing method and system

Technical Field

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

Background

A beacon device is a device that periodically broadcasts beacon messages to a nearby area, where the transmitted beacon messages are made available to a smart phone or other bluetooth enabled mobile device. Beacon devices are typically battery powered, deployed indoors, and used to broadcast beacon messages to surrounding mobile devices. The range of the broadcast is determined by the hardware capabilities of the beacon device, typically within 100 meters. The mobile device equipped with the capability of reading the beacon message takes corresponding action according to the received beacon message, and provides corresponding service for the owner of the mobile device.

In one scenario, when the mobile device acquires a beacon message of a peripheral beacon broadcast, the mobile device may report the beacon identifier scanned by the mobile device to the cloud server, and the cloud server may return a corresponding message attachment. However, the mobile device needs to make a call to the third-party service after receiving the message attachment, which causes a certain service delay.

Disclosure of Invention

In a first aspect, the present application provides a system comprising:

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

In this embodiment, the mobile device may periodically perform a scan to discover beacon messages from beacon devices in proximity to the mobile device location, the beacon messages including a target beacon identification. As used herein, "proximity" refers to the 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 the mobile device may initiate a short range scan for RF signals, such as BLE RF signals, near field communication RF signals, and ultrasound signals.

Obtaining beacon data based on the beacon message, wherein the beacon data comprises at least one of: a distance between the mobile device and the beacon device, and a time at which the mobile device receives the beacon message;

specifically, the mobile device may obtain distance information between the mobile device and the beacon device based on a signal strength value of the received beacon message, where the distance information may include at least one of the following: a distance value between the mobile device and the beacon device, a change in 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 a trend of change of the distance value between the mobile device and the beacon device, such as far to near, near to far, and the like.

Specifically, the time information may include at least one of the following: a time at which the beacon message is received by the mobile device, a time at which the mobile device is within a signal coverage area of the beacon device. The time information may include, among other things, the time at which the App user scanned the beacon device, the time the App user stayed around the beacon device, and so on.

Transmitting the target beacon identification and the beacon data to the server; and the number of the first and second groups,

the server is configured to invoke a corresponding third-party service based on the target beacon identifier if it is determined that the beacon data meets a preset condition.

When an application on a mobile device scans nearby beacon devices, a request for obtaining a beacon message attachment may be sent to a server (a beacon cloud service platform), where the request may carry a target beacon identifier and beacon data. The server may invoke a corresponding third-party service based on the target beacon identifier when the beacon data satisfies a preset condition.

In one implementation, the mobile device may receive the beacon message from the beacon device based on a system service of the mobile device, and in this case, the third-party service may refer to a service provided by a third-party Application (APP). For example, one or more applications may be supported in a mobile device, some of which may be applications provided by a third party (not the producer of the mobile device). The third party application may not be pre-installed in the terminal but may require the mobile device to be downloaded from the network side. When the mobile device runs the applications, the mobile device can communicate with a third-party server corresponding to the applications, and the third-party server can provide third-party services. Taking the fact that the producer of the mobile device is Hua and the Tencent of the provider of the WeChat as an example, after the WeChat is installed in the mobile device, when the mobile device runs the WeChat, the mobile device can communicate with a server (namely a third party server) corresponding to the WeChat.

It should be noted that in some implementations, based on an agreement between the manufacturer of the mobile device and the developer of some applications, the applications may be pre-installed in the terminal, in which case the service provided by invoking the applications may still be understood as the third party service being invoked by the server.

In one implementation, the service related to beacon data processing on the server side may be provided by a certain manufacturer, and in this case, a service not provided by the manufacturer may be understood as a third-party service.

In one implementation, a mobile device may receive a beacon message from a beacon device based on a second application, the third party service being a service provided by a first application, the first application and the second application being different, i.e., the application receiving the beacon message and the application providing the third party service are different applications.

In the embodiment of the application, in the process of triggering and invoking the third-party service, a preset condition of triggering is added to the server, including but not limited to that the distance between the mobile device and the beacon device, or the time when the mobile device receives the beacon message and the like satisfies a preset condition. When the application program of the mobile device scans a specific beacon message, the relevant beacon data is sent to the server, the server can perform rule judgment based on the beacon data, and the third-party service is called only if preset conditions are met. The method has the advantages that the server instead of the mobile device judges whether to trigger the calling of the third-party service, processing steps of the mobile device can be reduced, the preset conditions can be configured and modified on the server, the APP does not need to sense how the preset conditions need to be modified because the behavior of judging whether the preset conditions are met is not executed on the mobile device side, and when the preset conditions need to be modified, only the server needs to correspondingly modify, so that the time consumption of the whole process is greatly reduced. When an application APP developer needs to modify the preset conditions and needs to modify, the business logic of the App does not need to be modified, the App does not need to be released on the application market again, the App does not need to be updated by a user, the preset conditions can be directly modified on the server side, and the time consumption of the whole process is greatly reduced.

In an alternative 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 a second application; or, the third party service is a service provided by the first application, and the mobile device is configured to receive a beacon message from a beacon device based on its own service process.

In an optional implementation, the server is configured to determine, based on a preconfigured mapping relationship, a third-party service corresponding to the target beacon identifier; the mapping relation comprises a plurality of beacon identifications and third-party services corresponding to each beacon identification.

In this embodiment of the application, the server may determine, based on a preconfigured mapping relationship, a third-party service corresponding to the target beacon identifier; the mapping relation comprises a plurality of beacon identifications and a third party service corresponding to each beacon identification. The mapping relationship may be configured on the server in advance by the application developer.

In an alternative implementation, the beacon data includes information indicating a distance between the mobile device and the beacon device, and 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 big to small; and the combination of (a) and (b),

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

In an alternative implementation, the beacon data includes information indicating a time at which the mobile device received the beacon message;

the preset condition at least comprises one of the following conditions:

the time when the mobile device receives the beacon message is within a preset range; and the combination of (a) and (b),

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

In an alternative implementation, the server is configured to send a target message to an address where the third-party service is located, for example, the third-party service may be a mailbox address, the mailbox address is related to the third-party service, the third-party service may provide a corresponding third-party service based on the received target message, the target message is generated based on the target beacon identifier and/or the beacon data, the target message is related to the third-party service to be invoked, and specifically, the target message is data required for invoking the third-party service.

In an optional implementation, the server is configured to call a 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, and then, the server may call the application programming interface API corresponding to the third-party service. For example, the API may be a RESTful API, and the server may call a third party service using a RESTful address pre-configured by the developer. The third-party service may be deployed in a server otherwise deployed by a developer, or may 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 in an a server, and a serverless function implementing another server is deployed on the a server at the same time, in this case, the server side calls the service corresponding to the serverless function, which may also be understood as calling a third-party service.

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

In an alternative implementation, the server is configured to determine a corresponding third party service based on the target beacon identification; based on the beacon data, invoking the third party service.

In one implementation, the server may pass these beacon data as input parameters to a third party service. In one implementation, the server may process (e.g., mathematically statistically or otherwise process) the beacon data and pass the processing results as input parameters to a third party service, and so on.

In an alternative implementation, the server is configured to receive reply data from the third party service; sending the reply data to the mobile device; correspondingly, the mobile device is configured to trigger the corresponding presentation of the reply data.

In an alternative implementation, the mobile device is configured to receive reply data from the third party service; and triggering the corresponding presentation of the reply data.

In the embodiment of the application, if the server determines that the beacon data meets the preset condition, the server calls the corresponding third-party service based on the target beacon identifier. Optionally, the third-party service may send the reply data back to the server, and the server may receive the reply data from the third-party service and send the reply data to the mobile device; accordingly, the mobile device may trigger a corresponding presentation of the reply data.

Optionally, the third-party service may send the reply data directly to the mobile device; accordingly, the mobile device may trigger a corresponding presentation of the reply data. The manner in which the data is presented may not be limited to having the data displayed on the screen of the mobile device. In some implementations, presenting the message data can include providing one or more notifications. Presentation of the message data may include force feedback (e.g., a vibration indication), an audio output (e.g., beep, music, etc.), a visual output (e.g., a flashing light), or a combination thereof. In some implementations, the message data can include any content including, but not limited to, text, graphics, digital images, audio, video, and animation. The message data may be presented on the mobile device in the form of an audio output to cooperate with the mobile device without display capability. In some implementations, presenting the message data can include retrieving content corresponding to one or more values included in the message data; and causing the content to be displayed on a screen.

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

In a second aspect, the present application provides a system comprising: 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 call the corresponding third-party service based on the target beacon identification.

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

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 service process of the mobile device.

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

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

In an alternative implementation, the mobile device is configured to receive a beacon message from a beacon device, the beacon message including the target beacon identification; obtaining beacon data based on the beacon message, wherein the beacon data comprises at least one of:

a distance between the mobile device and the beacon device, and a time at which the mobile device receives the beacon message, or an identity of the mobile device;

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

accordingly, the server is configured to invoke a corresponding third party service based on the target beacon identification and the beacon data.

In an optional implementation, the method further comprises receiving condition modification information, the 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 third aspect, the present application provides a beacon message processing method, where the method is applied to a server, and the method includes:

receiving a target beacon identification from a mobile device; and the number of the first and second groups,

and calling the corresponding third-party service based on the target beacon identification.

In an optional implementation, the server, 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.

In an alternative implementation, the preset condition includes at least one of the following:

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

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

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

and sending a target message to the address of the third-party service, wherein the target message is generated based on the beacon identification.

and calling an Application Programming Interface (API) corresponding to the third-party service.

and initiating a remote procedure call protocol (RPC) based call to the address of the third-party service.

In an optional implementation, the method further comprises:

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

and calling a corresponding third-party service based on the target beacon identification and the beacon data.

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

determining a corresponding third party service based on the target beacon identification; invoking the third party service based on the beacon data.

In an optional implementation, 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 presentation corresponding to the reply data.

In an optional implementation, the method further comprises: receiving condition modification information, wherein the condition modification information indicates that the preset condition is modified into a new condition; modifying the preset condition based on the condition modification information.

In a fourth aspect, the present application provides a beacon message processing method, including:

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 the beacon device, and a time at which the mobile device receives the beacon message, or an identity of the mobile device; and the number of the first and second groups,

and if the beacon data is determined to meet the preset conditions, calling corresponding third-party service based on the target beacon identification.

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

a distance value between the mobile device and the beacon device, a change in distance value between the mobile device and the beacon device.

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

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

In an optional implementation, the method further comprises:

receiving reply data from the third party service;

In a fifth aspect, the present application provides a beacon message processing apparatus, including:

a receiving module, configured to receive a target beacon identifier from a mobile device.

And the calling module is used for calling the corresponding third-party service based on the target beacon identification.

In an alternative implementation, the apparatus further comprises:

the determining module is used for 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.

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

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

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

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

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

In an optional implementation, the invoking module is configured to determine, based on the target beacon identifier, a corresponding third party service; based on the beacon data, invoking the third party service.

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

and the sending module is used for sending the reply data to the mobile equipment so that the mobile equipment triggers the presentation corresponding to the reply data.

In a sixth aspect, the present application provides a beacon message processing apparatus, including:

a receiving module configured to receive 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 the beacon device, and a time at which the mobile device receives the beacon message, or an identity of the mobile device; and the number of the first and second groups,

and the calling module is used for calling the corresponding third-party service based on the target beacon identifier if the beacon data meets the preset condition.

In an alternative implementation, the apparatus further comprises:

the determining module is used for determining a third-party service corresponding to the target beacon identifier based on a preset mapping relation; the mapping relationship comprises a plurality of beacon identifications and third-party services corresponding to each beacon identification.

In an optional implementation, the receiving module is further configured to: receiving condition modification information, wherein the condition modification information indicates that the preset condition is modified into a new condition; the device further comprises:

and the state modification module is used for modifying the preset condition based on the condition modification information.

In a seventh aspect, the present application provides a beacon message processing apparatus, which may include a processor, a memory, and a communication interface, the processor and the memory being coupled, the communication interface being configured to perform the steps related to the receiving and sending actions in the possible implementations of the third aspect or the fourth aspect, and the memory storing program instructions, which when executed by the processor, are configured to process data received by the communication interface, as the steps related to the processing in the possible implementations of the third aspect or the fourth aspect. For steps performed in each possible implementation manner of the third aspect or the fourth aspect, the processor may specifically refer to the third aspect or the fourth aspect, and details are not described here.

In an eighth aspect, the present application provides a computer-readable storage medium having stored thereon a computer program which, when run on a computer, causes the computer to perform the method of any of the above third or fourth aspects.

In a ninth aspect, the present application provides circuitry comprising processing circuitry configured to perform the method of any of the third or fourth aspects above.

In a tenth aspect, the present application provides a computer program which, when run on a computer, causes the computer to perform the method of any of the third or fourth aspects above.

In an eleventh aspect, the present application provides a chip system, where the chip system includes a processor, and the processor is configured to enable a server or a threshold value obtaining apparatus to implement the functions recited in the above aspects, for example, to transmit or process data and/or information recited in the above methods. In one possible design, the system-on-chip further includes a memory for storing program instructions and data necessary for the server or the communication device. The chip system may be formed by a chip, or may include a chip and other discrete devices.

Drawings

FIG. 1 is a plan view of an exemplary application scenario;

FIG. 2 is a plan view of an exemplary application scenario;

fig. 3 is a flowchart illustrating a beacon information processing method according to an embodiment of the present application;

fig. 4 is a flowchart illustrating a beacon information processing method according to an embodiment of the present application;

fig. 5 is a flowchart illustrating a beacon information processing method according to an embodiment of the present application;

FIG. 6 is an illustration of a configuration interface provided by an embodiment of the present application;

fig. 7 is a flowchart illustrating a beacon information processing method according to an embodiment of the present application;

fig. 8 is a flowchart illustrating a beacon information processing method according to an embodiment of the present application;

fig. 9 is a flowchart illustrating a beacon information processing method according to an embodiment of the present application;

fig. 10 is a flowchart illustrating a beacon information processing method according to an embodiment of the present application;

fig. 11 is a schematic diagram of a beacon information processing apparatus according to an embodiment of the present application;

fig. 12 is an illustration of a mobile device provided by an embodiment of the present application;

fig. 13 is a schematic software architecture of a mobile device according to an embodiment of the present application;

fig. 14 is an illustration of a server provided in an embodiment of the present application.

Detailed Description

Embodiments of the present application will now be described with reference to the accompanying drawings, and it is to be understood that the described embodiments are merely illustrative of some, but not all, embodiments of the present application. As can be appreciated by those skilled in the art, with the development of technology and the emergence of new scenes, the technical solutions provided in the embodiments of the present application are equally applicable to similar technical problems.

The terms "first," "second," and the like in the description and in the claims of the present application and in the above-described drawings are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It will be appreciated that the data so used may be interchanged under appropriate circumstances such that the embodiments described herein may be practiced otherwise than as specifically illustrated or described herein. Moreover, the terms "comprises," "comprising," and any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or modules is not necessarily limited to those steps or modules explicitly listed, but may include other steps or modules not expressly listed or inherent to such process, method, article, or apparatus. The naming or numbering of the steps appearing in the present application does not mean that the steps in the method flow have to be executed in the chronological/logical order indicated by the naming or numbering, and the named or numbered process steps may be executed in a modified order depending on the technical purpose to be achieved, as long as the same or similar technical effects are achieved.

In addition, in the description of the present invention, "a plurality" means two or more unless otherwise specified. The term "and/or" or the character "/" in this application is merely an association describing associated objects, meaning that there may be three relationships, e.g., a and/or B, or a/B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone.

First, an application scenario illustration of the present application is described.

Fig. 1 is a plan view of an exemplary application scenario 100. In the illustrated embodiment, the application scenario 100 includes a beacon device 110 a. The beacon device 110a may broadcast a beacon message, which may be, for example, an Eddystone-based beacon communication format, to the mobile devices (102a and 102b) using a short-range communication link, which is primarily used to assist developers in using Beacons hardware and providing location-based smartphone communication transmissions. Applications running on the mobile devices (102a and 102b) (or services deployed in the mobile devices (102a and 102 b)) can be correspondingly presented to the user on the mobile devices (102a and 102b) based on the beacon messages, such as displaying messages and the like. The application scenario 100 may include, among other things, retail stores, museums, stadiums, restaurants, etc. as applicable to any beacon-equipped environment.

Beacon device 110a and mobile devices (102a and 102b) may broadcast and/or receive beacon messages using short-range radio technologies, such as bluetooth or Near Field Communication (NFC) technologies. In some implementations, beacon device 110a can use a particular type of Bluetooth^TMKnown as Bluetooth Low Energy (BLE). The wireless communication range of beacon device 110a may be between 10 meters and 30 meters. Other ranges are also possible. In the event that a mobile device (102a and 102b) is within wireless communication range of beacon device 110a, the mobile device may receive a corresponding beacon message.

Various embodiments of the mobile devices (102a and 102b) include a smartphone, a tablet, a laptop, or a wearable computer. In some implementations, the mobile devices (102a and 102b) can include wireless receivers or transceivers that can scan the environment 100 for beacon messages from other devices in the environment 100, such as beacon devices. For example, the mobile devices (102a and 102b) may include a BLE receiver that scans for beacon messages. The mobile devices (102a and 102b) may communicate with the server using a base station of a wireless network, such as a Long Term Evolution (LTE) or Code Division Multiple Access (CDMA) (e.g., CDMA2000 and wideband CDMA (wcdma)) based wireless network. Other types of wireless networks are also possible.

Fig. 2 shows an illustration of a system for processing beacon messages. The mobile devices (202a and 202b) may communicate, for example, via one or more wireless networks. For example, a base station 203 of a wireless network (e.g., 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. The mobile devices (202a and 202b) can communicate with one or more servers (207, 208), e.g., via base station 203, access point 204, or a combination thereof. The server (207, 208) may include a network interface configured to communicate with devices, such as device mobile devices (202a and 202 b). The server (207, 208) may include processor electronics configured to communicate with devices, such as device mobile devices (202a and 202b), via a network interface using a protocol, such as Transmission Control Protocol (TCP) or User Datagram Protocol (UDP).

The mobile devices (202a and 202b) may also receive beacon messages from the beacon devices (201a, 201b, and 201c) via the short-range communication link. 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, the mobile devices (202a and 202b) can be configured to continuously scan for beacon messages. In some implementations, the mobile devices (202a and 202b) can be configured to scan for beacon messages based on an application calling 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) can establish communication with one or more servers (207, 208) via long-range communication links associated with base stations 203 that provide cellular data services.

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, an application developer may pre-configure a mapping relationship between a beacon identifier and a beacon accessory, after a corresponding application on a mobile device scans and acquires a beacon message, the beacon identifier may be sent to the server 208, the server 208 may determine the beacon accessory corresponding to the beacon identifier based on the pre-configured mapping relationship between the beacon identifier and the beacon accessory, and send the beacon accessory to the corresponding application on the mobile device (102a and 102b), and the application may trigger presentation corresponding to the beacon accessory.

It should be noted that the application may be configured with a mapping between beacon attachments and corresponding message data, and after obtaining the beacon attachments, the application may trigger a presentation corresponding to the message data on the mobile device.

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

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

In some existing scenarios, after receiving the message attachment, the mobile device needs to further invoke a third-party service (the third-party service may be deployed on the server 208 or the server 207), so as to obtain necessary data relied on by message data presentation based on invoking the third-party service, or so that the third-party service can obtain relevant information of the mobile device, thereby implementing a corresponding service.

In the following, a shop marketing scenario is taken as an example to explain how mobile devices, beacon devices and servers can interact with each other, and in other scenarios, the interaction processes of the three devices are similar, and the differences are mainly reflected in the interaction content. For example: the application configures a marketing message "the customer who first registered the membership card can obtain the coupon full of 100 minus 50, and the old customer checks in to obtain the coupon 100 minus 30". The marketing message may be triggered to be displayed on the mobile device when the mobile device is at some location, such as a store, these sites may be deployed with beacon devices that periodically transmit a certain beacon identification (carried on beacon information), the server side may be configured with a beacon accessory corresponding to the beacon identification, the beacon accessory may trigger the mobile device to display the marketing message, such that, when the mobile device moves into the range of the beacon devices, the beacon information including the beacon identifier can be received, the beacon identifier is forwarded to the server side, the server can issue the beacon attachment corresponding to the beacon identifier to the mobile device, and after the application program corresponding to the mobile device obtains the beacon attachment, whether the user of the current application program has registered the membership card needs to be inquired. If the user of the application does not register a loyalty card, a prompt is made to "the customer that first registered the loyalty card can obtain a coupon full of 100 minus 50". If the user of the application has registered a membership card, a prompt is made to "old customer check-in available 100 minus 30 coupon. In this case, after the corresponding application on the mobile device obtains the beacon attachment, it needs to cache the beacon attachment, issue another network request, query the third-party service for additional information (e.g., whether the user has registered a member), and finally determine what action should be taken (e.g., pop-up to prompt for offer information for new customers or offer information for old members).

The above process has the disadvantage that the action of judging whether to call the third-party service is performed on the mobile equipment side, and when the preset condition needs to be modified, the business logic of the App on the mobile equipment side needs to be modified correspondingly, so that the time consumption of the whole process is greatly increased. Further, the beacon attachments provided by the server 208 are static (returning only a string based on the beacon identification) and cannot be linked to the existing services of subsequent applications (e.g., querying membership status). This results in that the mobile device may need to interact with different third-party services many times, the service delay is large, and the experience of the user of the corresponding application on the mobile device is affected. And if the business logic needs to be modified, for example, if the old client is modified to prompt the old client that the client who registers the membership card for the first time can obtain the coupon of 100 minus 50 and the old client checks in to obtain the coupon of 100 minus 30, so as to attract the old client to guide the member who registers the same party (new client), the business logic of the corresponding application program on the mobile device needs to be modified, the application program needs to be released again on the application market, and the application program needs to be upgraded by the user. The whole process is long in time consumption and difficult to quickly achieve marketing targets. Moreover, when the corresponding application program on the mobile device communicates with the server 208, identity verification is performed once, and subsequent communication between the corresponding application program on the mobile device and the three-party cloud service needs to be performed again in an identity verification process, so that the attack surface of network attack is increased in multiple identity verification processes, and the security is reduced.

In order to solve the above problem, an embodiment of the present application provides a system, and referring to fig. 3, fig. 3 is a flowchart illustrating a system and executing steps thereof provided by the embodiment of the present application, as shown in fig. 3, the system provided by the embodiment of the present application 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 a target beacon identification 301 from a beacon device.

In some implementations, the mobile device periodically performs a scan to discover beacon messages from beacon devices in proximity to the mobile device location, the beacon messages including a target beacon identification. As used herein, "proximity" refers to the 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 for RF signals, such as BLE RF signals, Near Field Communication (NFC) RF signals, and ultrasound signals.

In some implementations, a mobile device, after receiving a beacon message from a beacon device, can obtain beacon data based on the beacon message, wherein the beacon data includes at least one of: a distance between the mobile device and the beacon device, and a time at which the mobile device receives the beacon message, or an identity of the mobile device.

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

In some implementations, the mobile device can calculate an average RSSI value based on a Received Signal Strength Indication (RSSI) value of the beacon message and perform an average of the RSSI values. In some implementations, the RSSI may be mathematically defined as being about the ratio of the power of the received signal to a reference received power (e.g., 1mW), where the higher (or less negative) the RSSI value, the stronger the signal. In some implementations, the RSSI value may be expressed in dBm. Based on a predetermined transmission power for transmitting beacon messages, a range estimate may be calculated based on the RSSI values. Determining the distance estimate may include using channel quality information such as a Bit Error Rate (BER) or Packet Error Rate (PER) derived from the received beacon message.

The change information of the distance value between the mobile device and the beacon device may include a trend of change of the distance value between the mobile device and the beacon device, such as far to near, near to far, and the like.

In this embodiment, the time information may include at least one of the following: a time at which the beacon message is received by the mobile device, a time at which the mobile device is within a signal coverage area of the beacon device. The time information may include the time when the App user scans the beacon device, the dwell time of the App user around the beacon device, and the like.

For example, the beacon message may be an Eddystone-based beacon communications format that is used primarily to help developers use Beacons hardware and provide location-based smartphone communications transmissions. In one implementation, the beacon message may include a beacon identifier and an activity parameter. The beacon identifier may include a text string such as "com. Other types of identifiers are also possible. In some implementations, the activity parameter can include an action value or a string of characters. In some implementations, the activity parameter can include a message value or a message string. 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. Thus, the 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 the present application may include the beacon identifier in the above-described embodiment.

The beacon message may also include an application identifier and a user message. The application identifier may identify an application running on the mobile device for processing beacon messages after receipt by the mobile device. For example, an operating system running on the mobile device may use the application identifier to forward the beacon message to the application corresponding to the application identifier. In some implementations, if an application is not already installed on the mobile device, a browser can be launched on the mobile device and the user directed (e.g., using a Uniform Resource Locator (URL)) to a website where the user can download and install the application corresponding to the application identifier.

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

According to the embodiment of the application, after receiving the target beacon identification from the beacon device, the mobile device can send the target beacon identification to the server. Wherein an application on the mobile device or an underlying service may send the target beacon identification to the server after receiving the target beacon identification from the beacon device.

Specifically, when an application on the mobile device scans a nearby beacon device, a request for obtaining an attachment of a beacon message may be sent to a server (beacon cloud service platform), where the request may carry the target beacon identifier 302. The server may invoke the corresponding third party service 303 based on the target beacon identification.

In the embodiments of the present application, a service is an executable program that implements a specific function or provides specific content. For example, the service may be a Web page accessible through a Web browser developed using a programming Language such as HyperText Markup Language (HTML), Cascading Style Sheets (CSS), or java script (JavaScript, JS), or a small program, Web application, or other type of application developed using JS that can be used without installation. The functions or contents provided by the service are related to the type of service.

The third-party service according to the embodiment of the present application may be a service for providing a third-party Application (APP). For example, one or more applications may be supported in the mobile device, wherein some of the applications may be applications downloaded by the mobile device from the network side and provided by a third party (not the producer of the mobile device). When the mobile device runs the applications, the mobile device can communicate with a third-party server corresponding to the applications, and the third-party server can provide third-party services. Taking the fact that the producer of the mobile device is Hua and the Tencent of the provider of the WeChat as an example, after the WeChat is installed in the mobile device, when the mobile device runs the WeChat, the mobile device can communicate with a server (namely a third party server) corresponding to the WeChat.

In this embodiment of the application, the server may determine, based on a preconfigured mapping relationship, a third-party service corresponding to the target beacon identifier; the mapping relation comprises a plurality of beacon identifications and a third party service corresponding to each beacon identification. The mapping relationship may be configured on the server in advance by the application developer. In one implementation, the third party service in the mapping relationship may be an address where the third party service is located, and the server may send a target message to the address where the third party service is located, where the target message is generated based on the beacon identifier. In one implementation, the third-party service in the mapping relationship may be an application programming interface API, and then, the server may call the application programming interface API corresponding to the third-party service. For example, the API may be a RESTful API, and the server may call a third party service using a RESTful address pre-configured by the developer. The three-party service can be deployed in a server which is additionally deployed by a developer, and can also be a deployed serverless function. In one implementation, the third-party service in the mapping relationship may be an address where the third-party service is located, and the server may initiate a remote procedure call protocol (RPC) -based call 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, the beacon message including the target beacon identification; obtaining beacon data based on the beacon message, wherein the beacon data comprises at least one of: 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 sending the target beacon identity and the beacon data to the server; accordingly, the server is configured to invoke a corresponding third party service based on the target beacon identification and the beacon data. Specifically, the server is configured to determine a corresponding third-party service based on the target beacon identifier, and invoke the third-party service based on the beacon data.

In this embodiment, the server may determine what third-party service should be invoked based on the target beacon identifier, for example, which RESTful address should be invoked, or a destination address of the transmitted information, etc. based on the target beacon identifier. At this point, the server may invoke the third party service based on the beacon data.

In one embodiment, the server further determines whether the request meets a trigger condition configured by the developer, and invokes a third-party service if the trigger condition is met. That is, if the server determines that the beacon data meets the preset condition, the server invokes the corresponding third-party service based on the target beacon identifier. In the embodiment of the application, after the server receives the request sent by the mobile device, the server may trigger the rule to generate an Applet rule instance, where the rule instance may include multiple states, and use a state machine model commonly used in the industry. When the state machine reaches the end state, a call may be initiated to an address of a third-party service that is configured in advance by the developer, and the specific manner includes but is not limited to sending a message, initiating an RPC call, and the like.

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

Then, the trigger rule may be a combination of one or more of the following: the distance value between the mobile device and the beacon device meets a preset condition, the change information of the distance value between the mobile device and the beacon device meets the preset condition, the time of receiving the beacon message by the mobile device meets the preset condition, and the time of the mobile device in the signal coverage area of the beacon device meets the preset condition.

In the embodiment of the application, in the process of triggering and invoking the third-party service, a preset condition of triggering is added to the server, including but not limited to that the distance between the mobile device and the beacon device, or the time when the mobile device receives the beacon message and the like satisfies a preset condition. When the application program of the mobile device scans a specific beacon message, the relevant beacon data is sent to the server, the server can perform rule judgment based on the beacon data, and the third-party service is called only if preset conditions are met. This has the advantage that the configuration and modification of the preset conditions can be performed on the server, and in particular, the server can receive condition modification information indicating that the preset conditions are modified to new conditions; modifying the preset condition based on the condition modification information. Because the action of judging whether to satisfy the preset condition is not executed by the mobile equipment side, the APP does not need to sense how the preset condition needs to be modified, and when the preset condition needs to be modified, only the server needs to perform corresponding modification, so that the time consumption of the whole process is greatly reduced. When an application APP developer needs to modify the preset conditions and needs to modify, the business logic of the App does not need to be modified, the App does not need to be released on the application market again, the App does not need to be updated by a user, the preset conditions are directly modified on the server side, and the time consumption of the whole process is greatly reduced.

An illustration of a preconfigured mapping relationship is given below:

wherein the beacon identification corresponds to the beacon accessory, the trigger target, and the trigger condition. The trigger target includes, but is not limited to, a RESTful address of a three-party cloud service (RPC, Remote Procedure Call, or other manners), and the trigger condition includes, but is not limited to, a time when the application user scans to the beacon device, a staying time of the application user around the beacon device, a distance between the application user and the beacon device, a trend of the distance, and the like.

Referring to fig. 4, fig. 4 is a schematic flow of beacon data processing provided in this embodiment of the present application, as shown in fig. 4, a beacon device 401 sends a beacon message to a mobile device 402, the mobile device sends a request carrying a target beacon identifier to a server 403 (cloud platform), and the server may determine, based on a mapping relationship, a beacon accessory corresponding to the target beacon identifier, determine, when beacon data meets a preset condition, a third-party service corresponding to the target beacon identifier, return the beacon accessory to the mobile device 402, and invoke the corresponding third-party service 404.

Referring to fig. 5, fig. 5 is a system schematic provided by an embodiment of the present application, and as shown in fig. 5, a server may include a rule/trigger configuration engine 501, a beacon attachment pushing engine 502, a third party service triggering engine 503, a rule/trigger application engine 504, and a memory 505; among other things, an application developer (e.g., application developer 1 or application developer 2 shown in fig. 5) may configure a rule/trigger configuration based on the rule/trigger configuration engine 501, so that the rule/trigger configuration is stored in the memory 505, where the rule/trigger configuration may be a mapping relationship between the target beacon identifier and a third-party service, and trigger a preset condition that the third-party service needs to meet. Applications (e.g., application 1 and application 2 shown in fig. 5) may send the beacon message to the server, the rule/trigger application engine 504 may determine, based on the rule/trigger configuration in the memory 505, that the target beacon in the beacon message identifies the corresponding beacon accessory, and determine whether beacon data carried by the beacon message satisfies a preset condition, and return the beacon accessory to the corresponding application (e.g., application 1 or application 2 shown in fig. 5) based on the beacon accessory push engine 502, and the rule/trigger application engine 503 triggers invocation of the corresponding third-party service when the rule/trigger application engine 504 determines whether the beacon data carried by the beacon message satisfies the preset condition.

In more detail, in the embodiment of the present application, the server may provide a platform for configuring rules for an application developer, where the rules include a plurality of states, and jump relationships and jump conditions between the states. For example, the beacon cloud platform provides several rule templates while allowing developers to customize the rule logic. The beacon cloud platform stores the message rules by using a database and other technologies. Optionally, the beacon cloud platform may provide a RESTful interface (instead of a Web interface) for the developer to configure beacon IDs, beacon attachment messages, rule trigger conditions, rule trigger behaviors, and the like.

Referring to fig. 6, fig. 6 is an administrator interface schematic of a rule/trigger configuration provided in an embodiment of the present application, and as shown in fig. 6, some embodiments of the administrator interface may be a web-based Graphical User Interface (GUI) designed to interact with an administrator (e.g., an application developer, etc.) to implement configuration of a rule/trigger. In some embodiments, the GUI may be presented to the administrator by a browser application on the computing device. Specifically, the rule/trigger configured interface may include a configuration interface 601 for triggering a rule, for example, as shown in fig. 6, a "rule name" and a "rule condition" may be configured on the rule/trigger configured interface, where the "rule condition" may include, for example, configurations of "within a specific time" and "scan to beacon", and a trigger condition related to time may be input in an input box corresponding to the "within the specific time", for example, the time when a beacon message is received is weekend, morning, and the like, and a corresponding beacon identifier may be input in an input box corresponding to the "scan to beacon". Further, the rule/trigger configured interface may include a configuration interface 602 for triggering content, for example, a third party service that triggers invocation when the above rule is satisfied (a rule corresponding to "within a specific time" and "scan to beacon") may be input within an input box corresponding to "execute after satisfy" shown in fig. 6, the third party service may be an address where the third party service is located, an application programming interface API, or the like.

It should be noted that the control setting and arrangement of the GUI in fig. 6 are only illustrative and do not constitute a limitation of the present application.

Fig. 7 shows more details than fig. 3, specifically, when a mobile device approaches a beacon device 701, an application (or an underlying service) thereon may scan a beacon signal, acquire a beacon message carrying a target beacon identifier 702, generate corresponding beacon data, forward the beacon message carrying the target beacon identifier and the beacon data to a server 703, and if it is determined that the beacon data meets a preset condition, invoke a corresponding third-party service 704 based on the target beacon identifier, may receive reply data 705 returned by the third-party service, and send the reply data 705 to a mobile device 706, or the mobile device may directly receive reply data 707 returned by the third-party service, and then the mobile device may perform corresponding presentation 708 based on the reply data 707.

Specifically, the embodiment of the present application finds that, a mobile device is configured to receive a beacon message from a beacon device, where the beacon message includes the target beacon identifier; obtaining beacon data based on the beacon message, wherein the beacon data comprises at least one of: a distance between the mobile device and the beacon device, and a time at which the mobile device receives the beacon message, or an identity of the mobile device; transmitting the target beacon identification and the beacon data to the server; and the server is configured to call a corresponding third-party service based on the target beacon identifier if the beacon data is determined to meet the preset condition.

An embodiment of the present application provides a system, including: 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 call the corresponding third-party service based on the target beacon identification. The server side executes the calling of the third-party service, instead of the mobile equipment calling the third-party service after the mobile equipment needs to receive the message attachment, so that the service delay is reduced.

Taking two specific scenes as illustrations, describing the beacon message processing method provided by the embodiment of the application, taking a scene of a shopping mall as an example, a cash register is provided with a plurality of channels, a beacon device is deployed in each channel, a consumer acquires marketing information when queuing in the cash register channel, for example, "pay for wallet and enjoy 9 discount", and meanwhile, a background server of the beacon device counts the number of people at the cash register, and if the number of people in the cash register channel is too many, the beacon device notifies an administrator, coordinates more cash registers, opens more cash register channels, and reduces the queuing time of the consumer.

The developer deploys the rules on the server (beacon cloud platform): when the application user scans the beacon signal (i.e., the mobile device reports a beacon message), which represents that there is a client entering the checkout lane, the count is incremented by one. The application user counts down by one from near to far from the beacon device (on behalf of the customer leaving the checkout lane). If the count exceeds 200, a RESTful address is called to realize the function of sending the notice to the market manager.

The optional implementation scheme of the beacon cloud platform is as follows: a Web interface is provided for developers to configure the beacon's corresponding functionality. The developer logs into the Web interface. The beacon cloud platform provides a configuration interface for developers to fill in beacon identification, beacon message attachments and rule logic for triggering third-party service calling. In the rule logic interface, the beacon cloud platform may provide a condition defined by intervention, for example, "number of people who scanned the beacon," after the developer selects the condition, the developer may set the target to "200," set the message action as "send mail," and input the mailbox address.

The beacon cloud platform records the content input by the developer through a database. The beacon cloud platform provides SDKs to developers for developing applications. When the consumer uses the application program, the beacon SDK automatically and periodically scans nearby beacon devices, and when a specific beacon is scanned, the beacon SDK sends a message to the beacon cloud platform. And when receiving the request message, the beacon cloud platform inquires the message attachment corresponding to the beacon identifier from the database, constructs a response data packet and sends the response data packet to the mobile phone application program. Meanwhile, the beacon cloud platform inquires the message rule corresponding to the beacon from the database, updates the number count of people near the beacon, judges whether the count exceeds a threshold value preset by a developer, and sends the mail to the designated mailbox address.

In another scenario, the Beacon scan function may be implemented by a three-party program other than the App (e.g., a resident process provided by the underlying service). Therefore, a mobile phone user does not need to install a target App, and a developer of the target App deploys code logic of the target App as an Applet of the Beacon cloud platform to realize a specific function.

Specifically, when a nearby Beacon is scanned, a corresponding message can be reported to the Beacon cloud platform, which indicates that the mobile phone meets a certain Beacon. App developers configure rule logic corresponding to Beacon owned by the App developers on the Beacon cloud platform. The specific configuration method may use the scheme provided in the above embodiments. The implementation may be as shown in fig. 8, for example, a Beacon deployed in a brand of furniture store, but without the brand App installed on the consumer's cell phone. Peripheral Beacon is scanned, and the Beacon is sent to a Beacon cloud platform for analysis, the cloud platform inquires the message rule corresponding to the scanned Beacon, and the Beacon scanning event is distributed to the back-end server of the brand. The back-end server of the brand can perform processing such as pedestrian flow statistics and user shopping behavior analysis.

Referring to fig. 9, fig. 9 is a flowchart illustrating a beacon message processing method according to an embodiment of the present application, where as shown in fig. 9, the method is applied to a server, and the beacon message processing method according to the embodiment of the present application includes:

901. a target beacon identification is received from the mobile device.

902. And calling the corresponding third-party service based on the target beacon identification.

In an alternative implementation, the third-party service corresponding to the target beacon identifier may be determined based on a preconfigured mapping relationship; the mapping relation comprises a plurality of beacon identifications and third-party services corresponding to each beacon identification.

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

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

In an alternative implementation, a remote procedure call protocol, RPC, based call may be initiated to the address where the third party service is located.

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

In an alternative implementation, a corresponding third party service may be determined based on the target beacon identification; invoking the third party service based on the beacon data.

In an alternative implementation, reply data from the third party service may be received; and sending the reply data to the mobile equipment so that the mobile equipment triggers the presentation corresponding to the reply data.

The description of step 901 and step 902 may refer to the description related to fig. 3 to fig. 8 in the above embodiments, and is not repeated here.

Referring to fig. 10, fig. 10 is a flowchart illustrating a beacon message processing method according to an embodiment of the present application, where as shown in fig. 10, the method is applied to a server, and the beacon message processing method according to the embodiment of the present application includes:

1001. 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 the beacon device, and a time at which the mobile device receives the beacon message, or an identity of the mobile device.

1002. And calling a corresponding third-party service based on the target beacon identification under the condition that the beacon data meet the preset condition.

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

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

The description of step 1001 and step 1002 may refer to fig. 3 to fig. 8 and the related description in the above embodiments, and are not repeated here.

Referring to fig. 11, fig. 11 is a schematic diagram of a beacon message processing apparatus according to an embodiment of the present application, and as shown in fig. 11, a beacon message processing apparatus 1100 according to an embodiment of the present application includes:

a receiving module 1101, configured to receive a target beacon identifier from a mobile device.

And the invoking module 1102 is configured to invoke a corresponding third-party service based on the target beacon identifier.

In an alternative implementation, the apparatus further comprises:

a determining module 1103, configured to determine, based on a preconfigured mapping relationship, a third-party service corresponding to the target beacon identifier; the mapping relation comprises a plurality of beacon identifications and third-party services corresponding to each beacon identification.

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

In an optional implementation, the invoking module 1102 is configured to invoke an application programming interface API corresponding to the third party service.

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

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

In an alternative implementation, the invoking module 1102 is configured to determine a corresponding third-party service based on the target beacon identifier; based on the beacon data, invoking the third party service.

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

The beacon message processing apparatus provided in the embodiment of the present application may further include:

a receiving module 1101 configured to receive 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 the beacon device, and a time at which the mobile device receives the beacon message, or an identity of the mobile device; and the number of the first and second groups,

a calling module 1102, configured to, if it is determined that the beacon data meets a preset condition, call a corresponding third-party service based on the target beacon identifier.

In an alternative implementation, the apparatus further comprises:

In an optional implementation, the receiving module 1101 is configured to receive condition modification information, where the condition modification information indicates that the preset condition is modified to a new condition; modifying the preset condition based on the condition modification information.

The type of the mobile device is not specifically limited in the present application, and the mobile device may be a portable mobile device such as a mobile phone, a tablet computer, a Personal Digital Assistant (PDA), a wearable device, and a laptop computer (laptop). Exemplary embodiments of portable mobile devices include, but are not limited to, portable mobile devices that carry an iOS, android, microsoft, or other operating system. The portable mobile device may also be other portable mobile devices such as a laptop computer (laptop) with a touch sensitive surface (e.g., a touch panel), etc. It should also be understood that in other embodiments of the present application, the mobile device may not be a portable mobile device, but may be a desktop computer with a touch-sensitive surface (e.g., a trackpad).

Referring to fig. 12, fig. 12 is a schematic structural diagram of an electronic device 100 provided in 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, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a microphone 170B, a microphone 170C, an earphone interface 170D, a sensor module 180, a key 190, a motor 191, an indicator 192, a camera 193, a display screen 194, a Subscriber Identification Module (SIM) card interface 195, and the like. The sensor module 180 may include a pressure sensor 180A, a gyroscope sensor 180B, a pneumatic 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, an ambient light sensor 180L, a bone conduction sensor 180M, and the like.

It is to be understood that the illustrated structure of the embodiment of the present application does not specifically limit the electronic device 100. In other embodiments of the present application, electronic device 100 may include more or fewer components than shown, or some components may be combined, some components may be split, or a different arrangement of components. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

Processor 110 may include one or more processing units, such as: the processor 110 may include an Application Processor (AP), a modem processor, a Graphics Processing Unit (GPU), an Image Signal Processor (ISP), a controller, a video codec, a Digital Signal Processor (DSP), a baseband processor, and/or a neural-Network Processing Unit (NPU), etc. The different processing units may be separate devices or may be integrated into one or more processors.

The controller can generate an operation control signal according to the instruction operation code and the timing signal to complete the control of instruction fetching and instruction execution.

A memory may also be provided in processor 110 for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. The memory may hold instructions or data that have just been used or recycled by the processor 110. If the processor 110 needs to reuse the instruction or data, it can be called directly from the memory. Avoiding repeated accesses reduces the latency of the processor 110, thereby increasing the efficiency of the system.

In some embodiments, processor 110 may include one or more interfaces. The interface may include an integrated circuit (I2C) interface, an integrated circuit built-in audio (I2S) interface, a Pulse Code Modulation (PCM) interface, a universal asynchronous receiver/transmitter (UART) interface, a Mobile Industry Processor Interface (MIPI), a general-purpose input/output (GPIO) interface, a Subscriber Identity Module (SIM) interface, and/or a Universal Serial Bus (USB) interface, etc.

The software system of the electronic device 100 may employ a layered architecture, an event-driven architecture, a micro-core architecture, a micro-service architecture, or a cloud architecture. The embodiment of the present application takes an Android system with a layered architecture as an example, and exemplarily illustrates a software structure of the electronic device 100.

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

The layered architecture divides the software into several layers, each layer having a clear role and division of labor. The layers communicate with each other through a software interface. In some embodiments, the Android system is divided into four layers, an application layer, an application framework layer, an Android runtime (Android runtime) and system library, and a kernel layer from top to bottom.

The application layer may include a series of application packages.

As shown in fig. 13, the application package may include camera, gallery, calendar, phone call, map, navigation, WLAN, bluetooth, music, video, short message, etc. applications.

The application framework layer provides an Application Programming Interface (API) and a programming framework for the application program of the application layer. The application framework layer includes a number of predefined functions.

As shown in FIG. 13, the application framework layers may include a window manager, content provider, view system, phone manager, resource manager, notification manager, and the like.

The window manager is used for managing window programs. The window manager can obtain the size of the display screen, judge whether a status bar exists, lock the screen, intercept the screen and the like. In this embodiment, the window manager may obtain the sizes of the two display screens provided by the electronic device 100, and uniformly manage the contents displayed by the two display screens.

The content provider is used to store and retrieve data and make it accessible to applications. The data may include video, images, audio, calls made and received, browsing history and bookmarks, phone books, etc.

The view system includes visual controls such as controls to display text, controls to display pictures, and the like. The view system may be used to build applications. The display interface may be composed of one or more views. For example, the display interface including the short 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. Such as management of call status (including on, off, etc.).

The resource manager provides various resources for the application, such as localized strings, icons, pictures, layout files, video files, and the like.

The notification manager enables the application to display notification information in the status bar, can be used to convey notification-type messages, can disappear automatically after a short dwell, and does not require user interaction. Such as a notification manager used to inform download completion, message reminders, etc. The notification manager may also be a notification that appears in the form of a chart or scroll bar text at the top status bar of the system, such as a notification of a background running application, or a notification that appears on the screen in the form of a dialog window. For example, prompting text information in the status bar, sounding a prompt tone, vibrating the mobile device, flashing an indicator light, etc.

The Android Runtime comprises a core library and a virtual machine. The Android runtime is responsible for scheduling and managing an Android system.

The core library comprises two parts: one part is a function which needs to be called by java language, and the other part is a core library of android.

The application layer and the application framework layer run in a virtual machine. The virtual machine executes java files of the application layer and the application framework layer as binary files. The virtual machine is used for performing the functions of object life cycle management, stack management, thread management, safety and exception management, garbage collection and the like.

The system library may include a plurality of functional modules. For example: surface managers (surface managers), Media Libraries (Media Libraries), three-dimensional graphics processing Libraries (e.g., OpenGL ES), 2D graphics engines (e.g., SGL), and the like.

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

The media library supports a variety of commonly used audio, video format playback and recording, and still image files, among others. The media library may support a variety of audio-video encoding formats, such as MPEG4, h.264, MP3, AAC, AMR, JPG, PNG, and the like.

The three-dimensional graphic processing library is used for realizing three-dimensional graphic drawing, image rendering, synthesis, layer processing and the like.

The 2D graphics engine is a drawing engine for 2D drawing.

The kernel layer is a layer between hardware and software. The inner core layer at least comprises a display driver, a camera driver, an audio driver and a sensor driver.

Fig. 14 shows a schematic structure of a server 1400. The server 14 may implement the functionality of the server referred to above. The server 1400 may include a memory 1401, a processor 1402, and a transceiver 1403. Wherein the memory 1401, the processor 1402, and the transceiver 1403 are connected by a bus. The memory 1401 is used to store computer instructions that, when executed by the processor 1402, the processor 1402 may perform the steps performed in the embodiments shown in fig. 9 and 10. The processor 1402 may further execute instructions stored in the memory 1401 to trigger the transceiver 1403 to perform operations for establishing a communication connection with another device.

The transceiver 1403 may be used for transceiving data transmitted by other devices. Such as transceiver 1403 may include a receiver and a transmitter. Among other things, 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 for supporting the techniques described herein. All relevant contents of each step related to the above method embodiment may be referred to the functional description of the corresponding functional module, and are not described herein again.

In the software architecture corresponding to the embodiment of the present application, the server may also be understood as a cloud platform that provides beacon data and related processing functions, where the cloud platform has a function for a developer to configure a message attachment corresponding to a beacon identifier, a triggered third-party service, and a corresponding trigger rule, where the configuration mode may be through a Web interface, or through a RESTful programming interface, or the like. The cloud platform has a function of receiving beacon identification and beacon data sent by the mobile device, and can judge whether a rule for triggering third-party services on the cloud platform is met or not based on the received beacon data, and if the rule is met, the third-party services are called. Specifically, reference may be made to the execution steps related to the server in fig. 3 to fig. 10 in the foregoing embodiments, and the cloud platform may be deployed in a server or a server cluster, which is not limited herein.

It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, a division of a unit is merely a logical division, and an actual implementation may have another division, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.

The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application may be substantially implemented or contributed to by the prior art, or all or part of the technical solution may be embodied in a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or other network devices) to execute all or part of the steps of the method according to the embodiment of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a read-only memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.

The above embodiments are only used for illustrating the technical solutions of the present application, and not for limiting the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; such modifications or substitutions do not depart from the scope of the embodiments of the present application.

Claims

1. A system, characterized in that the system comprises:

a mobile device configured to receive a beacon message from a beacon device, the beacon message including the target beacon identification; based on the beacon message, obtaining beacon data, wherein the beacon data comprises 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 mobile device receives the beacon message;

the server is configured to call a corresponding third-party service based on the target beacon identifier when the beacon data meet a preset condition.

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

a distance value between the mobile device and the beacon device, a change in 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:

4. A system according to any one of claims 1 to 3, wherein the third party service is a service provided by a first application, the mobile device is configured to receive beacon messages from beacon devices based on a second application, the first application and the second application being different; or the like, or, alternatively,

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 includes information indicating a distance between the mobile device and the beacon device, and the preset condition includes at least one of:

6. A system according to claim 1 or 3, wherein the beacon data includes information indicative of the time at which the mobile device received the beacon message;

the preset condition at least comprises one of the following conditions:

7. The system according to any one of claims 1 to 6, wherein the server is configured to determine a third-party service corresponding to the target beacon identifier based on a pre-configured mapping relationship; the mapping relation comprises a plurality of beacon identifications and third-party services corresponding to each beacon identification.

8. The system of any of claims 1 to 7, wherein the server is configured to receive reply data from the third party service; sending the reply data to the mobile device; correspondingly, the mobile device is configured to trigger the corresponding presentation of the reply data; or the like, or, alternatively,

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

9. The system according to any one of claims 1 to 8, wherein the server is configured to receive condition modification information indicating that the preset condition is modified to a new condition; modifying the preset condition based on the condition modification information.

10. A method for processing a beacon message, the method comprising:

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 the beacon device, and a time at which the mobile device receives the beacon message; and the number of the first and second groups,

and calling a corresponding third-party service based on the target beacon identification under the condition that the beacon data meet the preset condition.

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

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

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

14. The method of claim 10 or 12, wherein the beacon data comprises information indicating a time at which the mobile device received the beacon message;

the preset condition at least comprises one of the following conditions:

15. The method of any of claims 10 to 14, further comprising:

16. The method of any of claims 10 to 15, further comprising:

receiving reply data from the third party service;

17. The method of any of claims 10 to 16, further comprising:

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

18. An apparatus for processing a beacon message, the apparatus comprising:

a communication interface to receive 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 the beacon device, and a time at which the mobile device receives the beacon message; and the number of the first and second groups,

and the processing circuit is used for calling the corresponding third-party service based on the target beacon identification 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:

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

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

22. The apparatus of claim 18 or 20, wherein the beacon data comprises information indicating a time at which the mobile device received the beacon message;

the preset condition at least comprises one of the following conditions:

23. The apparatus according to any one of claims 18 to 22, wherein the processing circuit is further configured to determine, based on a preconfigured mapping relationship, a third party service corresponding to the target beacon identifier; the mapping relation comprises a plurality of beacon identifications and third-party services corresponding to each beacon identification.

24. The apparatus according to any one of claims 18 to 23, wherein the communication interface is further configured to receive reply data from the third party service;

25. The apparatus according to any of claims 18 to 24, wherein the communication interface is further configured to receive condition modification information, the condition modification information indicating that the preset condition is modified to a new condition; the device 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, which when executed by one or more processors, are operable to perform the method of any one of claims 10-17.

27. A computer product comprising instructions for execution by a computer to implement the method of any one of claims 10-17.