CN113810857B

CN113810857B - Beacon message processing method and system

Info

Publication number: CN113810857B
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: 2023-10-24
Anticipated expiration: 2040-06-15
Also published as: CN113810857A

Abstract

The embodiment of the application discloses a system, which comprises: the mobile device receives 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 condition, calling a corresponding third party service based on the target beacon identifier. The application can carry out configuration of the preset condition on the server, and because the action of judging whether the preset condition is met or not is not carried out by the mobile equipment side, the APP of the mobile equipment does not need to perceive what modification is needed by the preset condition, and when the preset condition needs to be modified, the server only needs to carry out corresponding modification, thereby greatly reducing the time consumption of the whole process.

Description

Beacon message processing method and system

Technical Field

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

Background

A beacon device is a device that periodically broadcasts beacon messages to the vicinity, and the beacon messages it transmits are acquired by a smart phone or other bluetooth enabled mobile device. Beacon devices are typically battery powered and deployed indoors for broadcasting 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 with the capability of reading the beacon message can take corresponding action according to the received beacon message, and provide corresponding service for the owner of the mobile device.

In one scenario, when a mobile device acquires a beacon message broadcast by a surrounding beacon, it may report the scanned beacon identifier to a cloud server, which may return a corresponding message attachment, and the mobile device may decide on the next action, such as triggering the presentation of the message attachment correspondence, or invoking a third party service, according to the message attachment and predefined program logic. However, the mobile device needs to make a call to the third party service after receiving the message attachment, which may cause 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 at locations proximate to the mobile device, the beacon messages including the target beacon identification. As used herein, "proximate" refers to a mobile device being physically close enough to a beacon device to receive Radio Frequency (RF) signals transmitted by the beacon device. For example, a wireless transceiver on a mobile device may initiate a short range scan to find RF signals, such as BLE RF signals, near field communication RF signals, and ultrasound signals.

Based on the beacon message, beacon data is acquired, wherein the beacon data comprises at least one of the following: a distance between the mobile device and the beacon device, and a time at which the beacon message was received by 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: and the distance value between the mobile device and the beacon device and the change information of the distance value between the mobile device and the beacon device. The change information of the distance value between the mobile device and the beacon device may comprise a trend of change of the distance of the change information of the distance value between the mobile device and the beacon device, such as from far to near, from near to far, etc.

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

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

and the server is configured to call the corresponding third party service based on the target beacon identifier if the beacon data is determined to meet the preset condition.

When an application on a mobile device scans for nearby beacon devices, a request to obtain a beacon message attachment may be sent to a server (beacon cloud service platform), which may carry a target beacon identification and beacon data. And the server can call the corresponding third party service based on the target beacon identifier under the condition that the beacon data meets the preset condition.

In one implementation, a mobile device may receive beacon messages from a beacon device based on a system service of the mobile device, at which point a 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, where some of the applications may be applications provided by a third party (not the manufacturer of the mobile device). The third party application may not be preloaded in the terminal but may require the mobile device to download from the network side. The mobile device, when running the applications, may communicate with a third party server corresponding to the application, which may provide third party services. Taking the fact that the producer of the mobile device is a messenger of a 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 corresponding to the WeChat (namely, a third party server).

It should be noted that, in some implementations, based on a protocol between the producer of the mobile device and the developer of some applications, the applications may be preloaded in the terminal, in which case, invoking the service provided by the applications may still be interpreted as the server invoking the third party service.

In one implementation, the service related to the beacon data processing on the server side may be provided by a manufacturer, where services not provided by the manufacturer may be understood as third party services.

In one implementation, the mobile device may receive the beacon message from the 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 being different applications.

In the embodiment of the application, in the process of triggering and calling the third party service, a preset condition for triggering is added on a server, including but not limited to the distance between the mobile equipment and the beacon equipment, or the preset condition is met with the time of the mobile equipment receiving the beacon message, and the like. When the application program of the mobile device scans a specific beacon message, relevant beacon data is sent to the server, the server can conduct rule judgment based on the beacon data, and the third party service is invoked only if preset conditions are met. The method has the advantages that the server, rather than the mobile device, judges whether to trigger the calling of the third-party service, the processing steps of the mobile device can be reduced, the configuration and the modification of the preset condition can be carried out on the server, and the APP does not need to perceive what modification is needed for the preset condition because the act of judging whether to meet the preset condition is not carried out on the mobile device side, and when the preset condition needs to be modified, only the server needs to carry out corresponding modification, so that the time consumption of the whole process is greatly reduced. When the application APP developer needs to modify the preset conditions, the application APP developer does not need to modify the service logic of the application APP, and does not need to issue the application App on the application market again, and the user does not need to upgrade the application App, and only needs to modify the preset conditions directly on the server side, so that 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, the mobile device being 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 the beacon message from the beacon device based on its own service process.

In an optional implementation, the server is configured to determine, based on a pre-configured 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 the embodiment of the application, the server can determine the 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 a third party service corresponding to each beacon identification. The mapping relationship may be configured on the server in advance for 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 large to small; and, a step of, in the first embodiment,

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

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

the preset conditions at least comprise one of the following:

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

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

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, where the mailbox address is related to the third party service, and the third party service may provide a corresponding third party service based on the received target message, where the target message is generated based on the target beacon identifier and/or the beacon data, and the target message is related to the third party service to be invoked, and in particular, the target message is data required for invoking the third party service.

In an alternative 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 can be deployed on a server which is additionally deployed by a developer, and can also be a deployed server function. For example, in one implementation, the beacon data processing service on the server side is provided by a manufacturer, and the beacon data processing service is located in an a server, where a server function implementing another server is deployed at the same time, in which case, the server side calls the server function corresponding service 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; and calling the third party service based on the beacon data.

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) the beacon data and pass the result of the process as an input parameter to a third party service, or the like.

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

In an alternative implementation, the mobile device is configured to receive reply data from the third party service; 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 corresponding third party service is called based on the target beacon identifier. Optionally, the third party service may send reply data to a server, and the server may receive reply data from the third party service and send the reply data to the mobile device; accordingly, the mobile device may trigger presentation of the reply data.

Alternatively, a third party service may send the reply data directly to the mobile device; accordingly, the mobile device may trigger presentation of the reply data. The manner of presentation of the data 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. The presentation of the message data may include force feedback (e.g., vibration indication), audio output (e.g., beep, music, etc.), visual output (e.g., 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. Message data may be presented on the mobile device in the form of audio output to cooperate with mobile devices that do 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.

In an alternative implementation, the server is configured to receive condition modification information, the condition modification information indicating modification of the preset condition to a new condition; and 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; transmitting the target beacon identification to a server; and the server is configured to call a 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, the mobile device being configured to receive a target beacon identification from a beacon device based on a second application; or alternatively, the first and second heat exchangers may be,

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

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

In an alternative 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; based on the beacon message, beacon data is acquired, wherein the beacon data comprises at least one of the following:

the distance between the mobile device and the beacon device, the time when the beacon message is received by the mobile device, or the 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 alternative implementation, the method further includes receiving condition modification information indicating modification of the preset condition to a new condition; and modifying the preset condition based on the condition modification information.

In a third aspect, the present application provides a beacon message processing method, the method being applied to a server, the method comprising:

receiving a target beacon identification from a mobile device; the method comprises the steps of,

and calling a corresponding third party service based on the target beacon identifier.

In an alternative implementation, the server, the method further includes:

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 a third party service corresponding to each beacon identification.

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

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

the time of the mobile device receiving the beacon message is within a preset range; and

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

and sending a target message to an address where the third party service is located, 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 call based on a remote procedure call protocol (RPC) to an address where the third party service is located.

In an alternative 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 identifier and the beacon data.

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

determining a corresponding third party service based on the target beacon identifier; and calling the third party service based on the beacon data.

In an alternative 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 corresponding presentation of the reply data.

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

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

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

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

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

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

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

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

In an alternative 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, the beacon message processing apparatus comprising:

and the receiving module is used for receiving the target beacon identification from the mobile device.

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

In an alternative implementation, the apparatus further includes:

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 large to small

In an alternative implementation, the calling 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 alternative implementation, the calling module is configured to initiate a call based on a remote procedure call protocol RPC 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 alternative implementation, the calling module is configured to determine, based on the target beacon identifier, a corresponding third party service; and calling the third party service based on the beacon data.

In an alternative 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, the beacon message processing apparatus comprising:

a receiving module for receiving a target beacon identification and beacon data from a mobile device, wherein the beacon data includes at least one of: the distance between the mobile device and the beacon device, the time when the beacon message is received by the mobile device, or the identity of the mobile device; the method comprises the steps of,

And the calling module is used for calling the corresponding third party service based on the target beacon identifier if the beacon data is determined to meet the preset condition.

In an alternative implementation, the apparatus further includes:

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 a third party service corresponding to each beacon identification.

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

and the state modification module is used for modifying the preset conditions 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 steps associated with receiving and sending actions in each of the possible implementations of the third aspect or the fourth aspect, the memory storing program instructions, the program instructions stored in the memory being configured to process data received by the communication interface when executed by the processor, and the steps associated with processing in each of the possible implementations of the third aspect or the fourth aspect. For the steps executed by the processor in each possible implementation manner of the third aspect or the fourth aspect, reference may be made to the third aspect or the fourth aspect specifically, which is not described herein.

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

In a ninth aspect, the present application provides a circuitry comprising processing circuitry configured to perform the method of any of the third or fourth aspects described 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 comprising a processor for supporting a server or threshold value acquisition means to perform the functions involved in the above aspects, e.g. to send or process data and/or information involved in the above methods. In one possible design, the chip system further includes a memory for holding program instructions and data necessary for the server or the communication device. The chip system can be composed of chips, and can also comprise chips 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 of a beacon information processing method according to an embodiment of the present application;

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

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

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

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

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

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

fig. 10 is a flowchart of 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 provided by an embodiment of the present application;

FIG. 12 is a schematic 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 a schematic illustration of a server according to an embodiment of the present application.

Detailed Description

Embodiments of the present application will now be described with reference to the accompanying drawings, in which it is evident that the embodiments described are only some, but not all embodiments of the present application. As one of ordinary skill in the art can know, with the development of technology and the appearance of new scenes, the technical scheme provided by the embodiment of the application is also applicable to similar technical problems.

The terms first, second and the like in the description and in the claims and in the above-described figures, are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that the embodiments described herein may be implemented in other sequences than those illustrated or otherwise described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations 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 that are expressly listed or inherent to such process, method, article, or apparatus. The naming or numbering of the steps in the present application does not mean that the steps in the method flow must be executed according to the time/logic sequence indicated by the naming or numbering, and the execution sequence of the steps in the flow that are named or numbered may be changed according to the technical purpose to be achieved, so long as the same or similar technical effects can be achieved.

In addition, in the description of the present application, unless otherwise indicated, the meaning of "a plurality" is two or more. The term "and/or" or the character "/" in this application is merely an association relation describing the association object, and indicates that three relations may exist, for example, a and/or B, or a/B may indicate: a exists alone, A and B exist together, and B exists alone.

First, an application scenario of the present application will be 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 (beacon device) 110a. Beacon device 110a may broadcast beacon messages to mobile devices (102 a and 102 b) using a short-range communication link, e.g., the beacon messages may be in an Eddystone-based beacon communication format that is primarily used to assist developers in using Beacons hardware and to provide location-based smart phone communication transmissions. Applications running on the mobile devices (102 a and 102 b) (or services deployed in the mobile devices (102 a and 102 b)) may be presented to the user on the mobile devices (102 a and 102 b) based on the beacon message accordingly, such as for display of a message, etc. The application scenario 100 may include, among other things, retail stores, museums, sports arenas, restaurants, etc. suitable for use in any environment configured with beacons.

The beacon device 110a and the mobile devices (102 a and 102 b) may broadcast and/or receive beacon messages using short range radio technologies such as bluetooth (tm) or near field communication (near field communication, NFC) technologies. In some embodimentsIn implementations, beacon device 110a may use a particular type of Bluetooth ^TM Known as bluetooth low energy (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. Where a mobile device (102 a and 102 b) is within wireless communication range of beacon device 110a, the mobile device may receive a corresponding beacon message.

Various embodiments of the mobile devices (102 a and 102 b) include smart phones, tablets, notebooks, or wearable computers. In some implementations, the mobile devices (102 a and 102 b) may include wireless receivers or transceivers that may scan the environment 100 for beacon messages from other devices in the environment 100, such as beacon devices. For example, the mobile devices (102 a and 102 b) may include BLE receivers that scan for beacon messages. The mobile devices (102 a and 102 b) may communicate with a server using base stations 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 one illustration of a system for processing beacon messages. The mobile devices (202 a and 202 b) 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 an IEEE 802.11 series-based wireless access point, may provide communication access to a wide area network 206. The mobile devices (202 a and 202 b) may communicate with one or more servers (207, 208), for example, via a base station 203, an 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 (202 a and 202 b). The server (207, 208) may include processor electronics configured to communicate with devices such as device mobile devices (202 a and 202 b) via a network interface using a protocol such as transmission control protocol (transmission control protocol, TCP) or user datagram protocol (user datagram protocol, UDP).

The mobile devices (202 a and 202 b) may also receive beacon messages from the beacon devices (201 a, 201b, and 201 c) via short-range communication links. In some implementations, the short-range communication link may be based on bluetooth wireless technology. In some implementations, the short-range communication link may be based on NFC wireless technology. In some implementations, the mobile devices (202 a and 202 b) may be configured to continually scan for beacon messages. In some implementations, the mobile devices (202 a and 202 b) can be configured to scan for beacon messages based on an application calling a beacon scanning application program interface (application programming interface, API).

In some implementations, based on receiving beacon messages from beacon devices (201 a, 201b, and 201 c) via short-range communication links, mobile devices (202 a and 202 b) can establish communication with one or more servers (207, 208) via long-range communication links associated with base station 203 providing cellular data services.

More specifically, the beacon device 110a may be configured (locally or remotely via a network) to transmit a beacon message, which in some implementations may include a beacon identification. In the cloud-side server 208, the application program developer may pre-configure the mapping relationship between the beacon identifier and the beacon accessory, after the corresponding application program on the mobile device scans and obtains the 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 program on the mobile device (102 a and 102 b), and the application program may trigger the presentation corresponding to the beacon accessory.

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

Note that, the manner of presenting 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. The presentation of the message data may include force feedback (e.g., vibration indication), audio output (e.g., beep, music, etc.), visual output (e.g., 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. Message data may be presented on the mobile device in the form of audio output to cooperate with mobile devices that do 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 (201 a, 201b, and 201 c) may include circuitry such as a processor, memory, transmitter for broadcasting beacon messages, and an interface for programming the beacon devices (201 a, 201b, and 201 c), which may be a USB interface or a bi-directional wireless interface such as an LTE or IEEE 802.11 based network interface. In some implementations, the beacon devices (201 a, 201b, and 201 c) can be programmed to periodically update data within the beacon message. The beacon devices (201 a, 201b, and 201 c) may transmit different opcodes, e.g., different message values, at different times of the day.

In some existing scenarios, after receiving the message attachment, the mobile device needs to further call a third party service (the third party service may be deployed on the server 208 or the server 207), so as to obtain necessary data on which the message data is presented based on calling the third party service, or may be so as to enable the third party service to 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 the mobile device, the beacon device and the server can interact, and in other scenarios, the interaction process of the three devices is similar, and the difference is mainly reflected in the interaction content. For example: the application configures a marketing message "a customer first registered with a membership card may obtain a coupon of 100 minus 50, and an old customer checks in to obtain a coupon of 100 minus 30. The marketing information can be triggered and displayed on the mobile device when the mobile device is located in certain places (such as shops), the places can be deployed with beacon devices which periodically send a certain beacon identifier (bearing beacon information), the server side can be configured with beacon accessories corresponding to the beacon identifier, the beacon accessories can trigger the mobile device to display the marketing information, when the mobile device moves to the range of the beacon devices, the mobile device can receive the beacon information comprising the beacon identifier and forward the beacon identifier to the server side, the server can send the beacon accessories corresponding to the beacon identifier to the mobile device, and after the application programs corresponding to the mobile device acquire the beacon accessories, a user needing to inquire whether the current application program has registered a membership card or not. If the user of the application program has not registered the membership card, a prompt is made to "the customer who first registered the membership card can obtain a coupon of 100 minus 50. If the user of the application has registered a membership card, a prompt is made to "old customer check-in may obtain a 100 minus 30 coupon. In this case, after the corresponding application program on the mobile device acquires the beacon attachment, it needs to buffer the beacon attachment first, then initiate another network request, query the third party service for additional information (such as whether the user has registered a member), and finally determine what action should be performed (such as popup window prompting new customer preference information or old member preference information).

The above process has the disadvantage that the action of judging whether to perform the third party service call is performed on the mobile device side, and when the preset condition needs to be modified, the service logic of the App on the mobile device side needs to be modified correspondingly, so that the time consumption of the whole process is greatly increased. Further, the beacon attachment provided by the server 208 is static (only returns a string based on the beacon identification) and cannot be linked with subsequent existing services (e.g., querying member status) of the application. This results in the mobile device potentially needing to interact with different third party services multiple times, with significant traffic delays, and the experience of the user of the corresponding application on the mobile device being impacted. And if the business logic needs to be modified, for example, the business logic needs to be modified to prompt the old customer that the customer who registers the membership card for the first time can obtain the coupon with the total of 100 minus 50, the old customer signs in to obtain the coupon with the total of 100 minus 30, and the old customer attracts the old customer to guide the personnel (new customer) of the same party to register the membership, the business logic of the corresponding application program on the mobile equipment needs to be modified, the application program is released again in the application market, and the user is enabled to upgrade the application program. The whole process is time-consuming and difficult to reach marketing targets quickly. And, once identity verification is performed when the corresponding application program on the mobile device communicates with the server 208, the subsequent communication between the corresponding application program on the mobile device and the three-party cloud service needs to perform the identity verification process again, and the multiple identity verification processes increase the attack surface of the network attack and reduce the security.

In order to solve the above-mentioned problems, an embodiment of the present application provides a system, referring to fig. 3, fig. 3 is a flowchart illustrating a system and execution steps thereof provided in the embodiment of the present application, and as shown in fig. 3, the system provided in 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 the beacon device.

In some implementations, the mobile device periodically performs a scan to discover beacon messages from beacon devices at locations proximate to the mobile device, the beacon messages including a target beacon identification. As used herein, "proximity" refers to a mobile device being physically close enough to a beacon device to receive Radio Frequency (RF) signals transmitted by the beacon device. For example, a wireless transceiver on a mobile device may initiate a short range scan to discover RF signals, such as BLE RF signals, near field communication (near field communication, NFC) RF signals, and ultrasound signals.

In some implementations, the mobile device, upon receiving a beacon message from the beacon device, may obtain beacon data based on the beacon message, wherein the beacon data includes at least one of: the distance between the mobile device and the beacon device, the time the beacon message is received by the mobile device, or the 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: and the distance value between the mobile device and the beacon device and the change information of the distance value between the mobile device and the beacon device.

In some implementations, the mobile device may indicate the value (received signal strength indication, RSSI) based on the received signal strength of the beacon message and perform an average on the RSSI values to calculate an average RSSI value. In some implementations, RSSI may be defined mathematically as being approximately the ratio of the power of the received signal to a reference received power (e.g., 1 mW), where the higher the RSSI value (or less negative), the stronger the signal. In some implementations, the RSSI value may be expressed in dBm. Based on a predetermined transmission power for transmitting the beacon message, a range estimate may be calculated based on the RSSI value. Determining the distance estimate may include using channel quality information such as 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 comprise a trend of change of the change information distance of the distance value between the mobile device and the beacon device, such as from far to near, from near to far, etc.

In the embodiment of the present application, the time information may include at least one of the following: the time the beacon message is received by the mobile device, the time the mobile device is within the signal coverage area of the beacon device. The time information may include, among other things, the time the App user scanned the beacon device, the residence time of the App user around the beacon device, etc.

For example, the beacon message may be in an Eddystone-based beacon communication format, which is primarily used to assist developers in using Beacons hardware and to provide location-based smart phone communication 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.company. Retailstore_no_3954" or a hexadecimal value such as "0x0e33de54". Other types of identifiers are also possible. In some implementations, the activity parameter can include an action value or a string. 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 universal unique identifier (universally unique identifier, UUID). Within a region, multiple beacon devices with the same beacon identifier may be included. However, such beacons may have different values for the beacon UUID. Thus, UUIDs can be used to distinguish beacon devices sharing 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 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 the beacon message after receipt by the mobile device. For example, an operating system running on a mobile device may use an application identifier to forward a beacon message to an application corresponding to the application identifier. In some implementations, the application can be automatically downloaded without user intervention in a manner transparent to the user (e.g., as a background process).

The mobile device may send the target beacon identification 302 to a 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 or underlying service on the mobile device, after receiving the target beacon identification from the beaconing device, may send the target beacon identification to the server.

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

In the embodiment of the present application, a service is an executable program that realizes a specific function or provides specific contents. For example, the service may be a Web page accessible through a Web browser developed using a programming language such as hypertext markup language (HyperText Markup Language, HTML), cascading style sheets (cascading style sheets, CSS), or java script (JavaScript, JS), or an applet developed through JS or the like that is ready to use without installation, a Web application, or other type of application. The function or content provided by a service is related to the type of service.

The third party service according to the embodiment of the present application may refer to a service for providing a third party Application (APP). For example, one or more applications may be supported in the mobile device, where some of the applications may be applications that the mobile device downloads from the network side and that are provided by a third party (not the manufacturer of the mobile device). When the mobile device runs the applications, the mobile device may communicate with a third party server corresponding to the applications, which may provide third party services. Taking the fact that the producer of the mobile device is a messenger of a 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 corresponding to the WeChat (namely, a third party server).

In the embodiment of the application, the server can determine the 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 a third party service corresponding to each beacon identification. The mapping relationship may be configured on the server in advance for the application developer. The mapping relationship may include a plurality of beacon identifiers and a third party service corresponding to each beacon identifier, and 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 identifiers. 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 on a server which is additionally deployed by a developer, and can also be a deployed server 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 call based on the remote procedure call protocol RPC to the address where the third party service is located.

In one embodiment, the mobile device is configured to receive a beacon message from a beacon device, the beacon message including the target beacon identification; based on the beacon message, beacon data is acquired, wherein the beacon data comprises at least one of the following: the distance between the mobile device and the beacon device, the time when the beacon message is received by the mobile device, or the identity of the mobile device, and sending the target beacon identifier 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 call the third party service based on the beacon data.

In the embodiment of the application, the server can determine what third party service is called based on the target beacon identification, for example, which RESTful address is called or the destination address for sending information can be determined based on the target beacon identification. At this time, the server may call the third party service based on the beacon data.

In one embodiment, the server also determines whether the request meets a trigger condition configured by the developer, and if so, invokes a third party service. 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 rule can be triggered to generate an Applet rule instance, and the rule instance can comprise a plurality of states and uses 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 the third party service that is preconfigured by the developer, including, but not limited to, sending a message, initiating an RPC call, and the like.

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

The triggering rule may then be a combination of one or more of the following: the distance value between the mobile device and the beacon device meets the preset condition, the change information of the distance value between the mobile device and the beacon device meets the preset condition, the time of the mobile device receiving the beacon message 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 calling the third party service, a preset condition for triggering is added on a server, including but not limited to the distance between the mobile equipment and the beacon equipment, or the preset condition is met with the time of the mobile equipment receiving the beacon message, and the like. When the application program of the mobile device scans a specific beacon message, relevant beacon data is sent to the server, the server can conduct rule judgment based on the beacon data, and the third party service is invoked 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, in particular the server can receive condition modification information indicating that the preset conditions are modified to new conditions; and modifying the preset condition based on the condition modification information. Because the act of judging whether the preset condition is met is not executed on the mobile equipment side, the APP does not need to sense what modification is needed for the preset condition, and when the preset condition needs to be modified, only the server needs to carry out 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, the application APP developer does not need to modify the business logic of the application APP, and does not need to issue the application App on the application market again, and the user does not need to upgrade the application App, and only needs to modify the preset conditions directly on the server side, so that 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 a beacon accessory, a trigger target, and a trigger condition. Wherein the trigger targets include, but are not limited to, RESTful addresses (also RPC, remote Procedure Call, remote procedure call, etc.) of the three-party cloud service, and the trigger conditions include, but are not limited to, time when the application user scans to the beacon device, residence time of the application user around the beacon device, distance of the application user from the beacon device, trend of change in distance, etc.

Referring to fig. 4, fig. 4 illustrates a flow chart of processing beacon data provided by an 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 attachment corresponding to the target beacon identifier, and when the beacon data meets a preset condition, determine a third party service corresponding to the target beacon identifier, and return the beacon attachment to the mobile device 402, and call a 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, the server may include a rule/trigger configuration engine 501, a beacon attachment push engine 502, a third party service trigger engine 503, a rule/trigger application engine 504, and a memory 505; wherein 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 such that the rule/trigger configuration is stored in the memory 505, wherein the rule/trigger configuration may be a mapping relationship between the target beacon identifier and the third party service and a preset condition that needs to be satisfied by the triggering third party service. An application (e.g., application 1 and application 2 shown in fig. 5) may send a beacon message to a server, a rule/trigger application engine 504 may determine, based on a rule/trigger configuration in a memory 505, a beacon attachment corresponding to a target beacon identification in the beacon message, and determine whether beacon data carried by the beacon message meets a preset condition, and based on a beacon attachment push engine 502, return the beacon attachment to a corresponding application (e.g., application 1 or application 2 shown in fig. 5), and the rule/trigger application engine 504 triggers a call to a corresponding third party service when determining whether the beacon data carried by the beacon message meets the preset condition.

More specifically, 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 a skip relation and a skip condition between the states. For example, the beacon cloud platform provides several rule templates while allowing the developer to customize rule logic. The beacon cloud platform stores the message rules using techniques such as databases. Alternatively, the beacon cloud platform may provide a RESTful interface (rather than a Web interface) for the developer to configure beacon IDs, beacon attachment messages, rule triggering conditions, rule triggering behavior, and the like.

Referring to fig. 6, fig. 6 is an administrator interface schematic for one rule/trigger configuration provided by embodiments of the present application, some embodiments of which may be web-based graphical user interfaces or graphical user interfaces (graphical user interface, abbreviated GUIs) designed to interact with an administrator (e.g., application developer, etc.) to implement the rule/trigger configuration, as shown in fig. 6. In some embodiments, the GUI may be presented to the administrator by a browser application on the computing device. Specifically, the interface of the rule/trigger configuration may include a configuration interface 601 for triggering a rule, for example, as shown in fig. 6, where the configuration of "rule name" and "rule condition" may be performed on the interface of the rule/trigger configuration, where "rule condition" may include, for example, a configuration of "within a specific time" and "scan to beacon", a trigger condition related to time may be input in an input box corresponding to "within a specific time", for example, a time of receiving a beacon message is the morning on the weekend, etc., and a corresponding beacon identifier may be input in an input box corresponding to "scan to beacon". In addition, the interface of rule/trigger configuration may include a configuration interface 602 that triggers content, for example, a third party service that triggers invocation when the above-described rule (the rule corresponding to "scan to beacon" for a specific time) is satisfied may be entered in an input box corresponding to "execute after satisfaction" shown in fig. 6, the third party service may be an address where the third party service is located, an application programming interface API, and so on.

It should be noted that the control settings and arrangements of the GUI in fig. 6 are only illustrative and not limiting.

Fig. 7 shows more details than fig. 3, specifically, when the mobile device approaches to the beacon device 701, an application program (or an underlying service) thereon may scan for a beacon signal, acquire a beacon message carrying a target beacon identifier 702, generate corresponding beacon data, forward a beacon message carrying the target beacon identifier and the beacon data to the server 703, if it is determined that the beacon data meets a preset condition, call a corresponding third party service 704 based on the target beacon identifier, and may receive reply data 705 returned by the third party service, and send the reply data 705 to the 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 application finds that, the mobile device is configured to receive a beacon message from the beacon device, and the beacon message comprises the target beacon identifier; based on the beacon message, beacon data is acquired, wherein the beacon data comprises at least one of the following: the distance between the mobile device and the beacon device, the time when the beacon message is received by the mobile device, or the 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 a 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; transmitting the target beacon identification to a server; and the server is configured to call a corresponding third party service based on the target beacon identification. The server side executes the call of the third party service instead of the mobile device after the mobile device receives the message attachment, thereby reducing the service delay.

The beacon message processing method provided by the embodiment of the application is described by taking two specific scenes as an illustration, taking the 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 obtains marketing information when queuing in a cash register channel, for example, a 'using Hua to pay for a wallet to share 9-fold preferential', meanwhile, a background server of the beacon device counts the number of people in the cash register, if the number of people in the cash register channel is too large, a manager is notified, more cashiers are coordinated, more cash register channels are opened, and the queuing time of the consumer is reduced.

The developer deploys rules on the server (beacon cloud platform): when the application user scans for a beacon signal (i.e., the mobile device reports a beacon message), the count is incremented by one on behalf of a customer entering the cashier's channel. The application user decrements the count by one when going from near to far from the beaconing device (leaving the cashier's channel on behalf of the customer). If the count exceeds 200, a RESTful address is called to realize the function of sending a notification to a mall manager.

The alternative implementation scheme of the beacon cloud platform is as follows: a Web interface is provided for the developer to configure the corresponding functionality of the beacon. The developer logs in to the Web interface. The beacon cloud platform provides a configuration interface for a developer to fill in a beacon identifier, a beacon message attachment and rule logic for triggering third party service call. In the rule logic interface, the beacon cloud platform may provide a defined condition if the intervention is performed, for example, "the number of people scanning the beacon", and after the developer selects the condition, the developer may set the target to "200", set the message action to "send mail", and input the mailbox address.

The beacon cloud platform records the content input by the developer through the database. The beacon cloud platform provides the SDK to the developer for developing the application. When the customer 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 the beacon cloud platform receives the request message, inquiring a message attachment corresponding to the beacon identifier from a database, constructing a response data packet and sending the response data packet to the mobile phone application program. Meanwhile, the beacon cloud platform queries a message rule corresponding to the beacon from the database, updates the count of the number of people nearby the beacon, judges whether the count exceeds a threshold preset by a developer, and sends a mail to a designated mailbox address.

In another scenario, the Beacon scanning function may be implemented by a three-party program other than 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 the code logic of the target App into an Applet of the Beacon cloud platform, so that specific functions can be realized.

Specifically, when a nearby Beacon is scanned, a corresponding message can be reported to the Beacon cloud platform, which indicates that the mobile phone encounters a certain Beacon. App developers configure the rules logic corresponding to the beacons they own on the Beacon cloud platform. The specific configuration method may use the scheme provided in the above embodiment. Execution may be as shown in fig. 8, for example, where Beacon is deployed in a certain brand furniture store, but no App of that brand is installed on the consumer's cell phone. And scanning peripheral Beacon, sending the Beacon to a Beacon cloud platform for analysis, inquiring a message rule corresponding to the scanned Beacon by the cloud platform, and distributing the Beacon scanning event to a back-end server of the brand. The backend server of the brand can perform processes such as people stream statistics, user shopping behavior analysis and the like.

Referring to fig. 9, fig. 9 is a flowchart of a beacon message processing method provided by 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 provided by the embodiment of the present application includes:

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

902. And calling a corresponding third party service based on the target beacon identifier.

In an alternative implementation, the third party service corresponding to the target beacon identifier may be determined 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.

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

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

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 from the mobile device may be received, wherein the beacon data includes at least one of: the distance between the mobile device and the beacon device, the time when the beacon message is received by the mobile device, or the identity of the mobile device; and calling a corresponding third party service based on the target beacon identifier and the beacon data.

In an alternative implementation, a corresponding third party service may be determined based on the target beacon identification; and calling 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 corresponding presentation of the reply data.

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

Referring to fig. 10, fig. 10 is a flowchart of a beacon message processing method provided by 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 provided by the embodiment of the present application includes:

1001. receiving a target beacon identification and beacon data from a mobile device, wherein the beacon data includes at least one of: the distance between the mobile device and the beacon device, the time the beacon message is received by the mobile device, or the identity of the mobile device.

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

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

In an alternative implementation, condition modification information may also be received, the condition modification information indicating modification of the preset condition to a new condition; and modifying the preset condition based on the condition modification information.

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

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

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

And a calling module 1102, configured to call a corresponding third party service based on the target beacon identifier.

In an alternative implementation, the apparatus further includes:

a determining module 1103, configured to determine, based on a pre-configured 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 calling 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 calling module 1102 is configured to call an application programming interface API corresponding to the third party service.

In an optional implementation, the calling module 1102 is configured to initiate a call based on a remote procedure call protocol RPC 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 optional implementation, the calling module 1102 is configured to determine, based on the target beacon identifier, a corresponding third party service; and calling the third party service based on the beacon data.

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

The beacon message processing device provided by the embodiment of the application can further comprise:

a receiving module 1101 for receiving a target beacon identification and beacon data from a mobile device, wherein the beacon data comprises at least one of: the distance between the mobile device and the beacon device, the time when the beacon message is received by the mobile device, or the identity of the mobile device; the method comprises the steps of,

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

In an alternative implementation, the apparatus further includes:

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; and modifying the preset condition based on the condition modification information.

The present application is not particularly limited as to the type of mobile device mentioned, and the mobile device may be a portable mobile device such as a mobile phone, a tablet computer, a personal digital assistant (personal digital assistant, PDA), a wearable device, a laptop computer (laptop), etc. Exemplary embodiments of portable mobile devices include, but are not limited to, portable mobile devices that carry iOS, android, microsoft or other operating systems. The portable mobile device described above may also be other portable mobile devices such as a laptop computer (laptop) or the like having a touch sensitive surface (e.g., a touch panel). It should also be appreciated that in other embodiments of the application, the mobile device may not be a portable mobile device, but rather a desktop computer having a touch-sensitive surface (e.g., a touch pad).

Referring to fig. 12, fig. 12 shows a schematic structural diagram of an electronic device 100 according to 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 (universal serial bus, USB) interface 130, a charge 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, keys 190, a motor 191, an indicator 192, a camera 193, a display 194, and a user identification module (subscriber identification module, SIM) card interface 195, etc. The sensor module 180 may include a pressure sensor 180A, a gyro sensor 180B, an air pressure sensor 180C, a magnetic sensor 180D, an acceleration sensor 180E, a distance sensor 180F, a proximity 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 should be understood that the illustrated structure of the embodiment of the present application does not constitute a specific limitation on the electronic device 100. In other embodiments of the present application, electronic device 100 may include more or fewer components than shown, or certain components may be combined, certain components may be separated, or different arrangements of components. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

The processor 110 may include one or more processing units, such as: the processor 110 may include an application processor (application processor, AP), a modem processor, a graphics processor (graphics processing unit, GPU), an image signal processor (image signal processor, ISP), a controller, a video codec, a digital signal processor (digital signal processor, DSP), a baseband processor, and/or a neural network processor (neural-network processing unit, NPU), etc. Wherein the different processing units may be separate devices or may be integrated in one or more processors.

The controller can generate operation control signals according to the instruction operation codes and the time sequence signals to finish the control of instruction fetching and instruction execution.

A memory may also be provided in the 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 the processor 110 has just used or recycled. If the processor 110 needs to reuse the instruction or data, it can be called directly from the memory. Repeated accesses are avoided and the latency of the processor 110 is reduced, thereby improving the efficiency of the system.

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

The software system of the electronic device 100 may employ a layered architecture, an event driven architecture, a microkernel architecture, a microservice architecture, or a cloud architecture. In the embodiment of the application, taking an Android system with a layered architecture as an example, a software structure of the electronic device 100 is illustrated.

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

The layered architecture divides the software into several layers, each with distinct roles and branches. The layers communicate with each other through a software interface. In some embodiments, the Android system is divided into four layers, from top to bottom, an application layer, an application framework layer, an Zhuoyun row (Android run) and system libraries, and a kernel layer, respectively.

The application layer may include a series of application packages.

As shown in fig. 13, the application package may include applications for cameras, gallery, calendar, phone calls, maps, navigation, WLAN, bluetooth, music, video, short messages, etc.

The application framework layer provides an application programming interface (application programming interface, API) and programming framework for application programs of the application layer. The application framework layer includes a number of predefined functions.

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

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

The content provider is used to store and retrieve data and make such data accessible to applications. The data may include video, images, audio, calls made and received, browsing history and bookmarks, phonebooks, 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, a display interface including a text message notification icon may include a view displaying text and a view displaying a picture.

The telephony manager is used to provide the communication functions of the electronic device 100. Such as the management of call status (including on, hung-up, etc.).

The resource manager provides various resources for the application program, such as localization 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 communicate notification type of consumption, can automatically disappear after a short dwell, and does not require user interaction. Such as notification manager is used to inform that the download is complete, a message reminder, etc. The notification manager may also be a notification of status bars appearing on top of the system in the form of a chart or scroll bar text, such as a notification of a background running application, or a notification appearing on the screen in the form of a dialog window. For example, a text message is prompted in a status bar, a prompt tone is emitted, the mobile device vibrates, and an indicator light blinks, etc.

Android run time includes a core library and virtual machines. Android run time is responsible for scheduling and management of the Android system.

The core library consists of 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 program layer and the application program framework layer as binary files. The virtual machine is used for executing the functions of object life cycle management, stack management, thread management, security and exception management, garbage collection and the like.

The system library may include a plurality of functional modules. For example: surface manager (surface manager), media Libraries (Media Libraries), three-dimensional graphics processing Libraries (e.g., openGL ES), 2D graphics engines (e.g., SGL), etc.

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

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

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 diagram of a server 1400. The server 14 may implement the functions of the servers 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, and trigger the transceiver 1403 to perform an operation of establishing a communication connection with other devices.

The transceiver 1403 may be used to transmit and receive data transmitted by other devices. For example, transceiver 1403 may include a receiver and a transmitter. Wherein 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 cited to the functional description of the corresponding functional module, which is not described herein.

In the software architecture corresponding to the embodiment of the present application, the server may also be understood as providing the beacon data and the relevant processing function cloud platform, where the cloud platform has a function for a developer to configure the message attachment, the triggered third party service and the corresponding triggering rule corresponding to the beacon identifier, where the configuration mode may be through a Web interface, or through a RESTful programming interface, etc. The cloud platform has the function of receiving the beacon identification and the beacon data sent by the mobile device, and can judge whether a rule triggering the third party service on the cloud platform is met or not based on the received beacon data, and if so, the third party service is called. In particular, reference may be made to the steps performed in connection with the servers in fig. 3 to 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 will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described system, apparatus and unit may refer to corresponding procedures in the foregoing method embodiments, and are not repeated herein.

In the several embodiments provided herein, it should be understood that the disclosed systems, devices, and methods may be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of elements is merely a logical functional division, and there may be additional divisions of actual implementation, e.g., multiple elements or components may be combined or integrated into another system, or some features may be omitted, or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection via interfaces, devices or units, which may be in electrical, mechanical or other forms.

The units described as separate units may or may not be physically separate, and units shown 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 may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

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

The integrated units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application may be embodied in essence or a part contributing to the prior art or all or part of the technical solution in the form of a software product stored in a storage medium, including several instructions for causing a computer device (which may be a personal computer, a server, or other network device, etc.) to perform all or part of the steps of the method according to the embodiment of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a read-only memory (ROM), a random access memory (random access memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.

The above embodiments are only for illustrating the technical solution of the present application, and not for limiting the same; although the application has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit of the application.

Claims

1. A system, the system comprising:

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

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

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

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

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

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

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

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

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

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

the preset conditions at least comprise one of the following:

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

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

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

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

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

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

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

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

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

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

the preset conditions at least comprise one of the following:

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

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

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

receiving reply data from the third party service;

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

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

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

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

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

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

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

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

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

the preset conditions at least comprise one of the following:

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

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

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

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

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