CN113920638B

CN113920638B - Queuing and calling method and device based on wearable equipment

Info

Publication number: CN113920638B
Application number: CN202010658186.5A
Authority: CN
Inventors: 黄励哲
Original assignee: Honor Device Co Ltd
Current assignee: Honor Device Co Ltd
Priority date: 2020-07-09
Filing date: 2020-07-09
Publication date: 2022-11-25
Anticipated expiration: 2040-07-09
Also published as: CN113920638A

Abstract

The embodiment of the application relates to a queuing and calling method and device based on wearable equipment, wherein the method comprises the following steps: the first terminal equipment acquires a queuing serial number distributed by the second terminal equipment, and binds the queuing serial number with the first terminal equipment; the method comprises the steps that a first terminal device sends a first message to a wearable device to obtain device information of the wearable device; in response to receiving the device information of the wearable device, the first terminal device sends a second message to the server; and responding to the received push message sent by the server, and sending a control instruction to the wearable device by the first terminal device. The method can utilize the wearable device to remind, so that the queuing reminding becomes more personalized and effective, and a user is given a proper reminding mode for queuing and calling, so that the user can know the queuing condition better.

Description

Queuing and calling method and device based on wearable equipment

Technical Field

The application relates to the field of wearable equipment, in particular to a queuing and calling method and device based on the wearable equipment.

Background

At present, in the process of dining in a restaurant or visiting a hospital, a user needs to queue according to a serial number distributed by the restaurant or the hospital, and when the number is in turn to the user, the user can go to the restaurant or visit the hospital. Due to the large number of queuing people, the users are prompted to turn to the queuing sequence through various ways. There are several situations in the current state of the art:

1. automatic rolling prompting number calling

The method is that in the process of queuing of users in public places (hereinafter collectively referred to as "merchants") such as restaurants, hospitals and government agencies, merchants send queuing number tickets to each user according to a sequence, wherein the current queuing sequence can be updated immediately in an operation system of the merchant, and when a certain number comes, a voice number calling system of the merchant prompts that the user asks for an XX number to eat, or a display screen of the merchant updates the user instantly to prompt that the user has arrived at the XX number, or the display screen of the merchant displays the queuing condition in an instant rolling manner.

2. Short-distance number calling tool

In the case of a large number of people in the queue, a merchant may distribute a signaler to one person of the users in the queue to realize one-to-one binding between the person and the number. When the number of the user is arranged, the merchant uses the signal transmitting host to transmit the radio frequency signal to the hand of the user, and after the annunciator of the user receives the signal, the annunciator of the user can generate functions of vibration, buzzing and the like to achieve the effect of reminding the user so as to achieve the function of calling the number.

3. Mobile phone short message or application message push number calling

The user can use the mobile phone number to register and arrange the number at a merchant to obtain a queuing number, and when the queuing sequence in the merchant system turns to a certain number user, the merchant can remind the user in a short message mode or prompt the user in an application message pushing mode.

The three modes have disadvantages, and for the method 1 and the method 2, the user needs to stay at the merchant site and cannot leave, so as to avoid missing the calling number or not receiving the calling number. For the method 3, the user needs to stare at the mobile phone at any time to avoid missing the queuing, and for a noisy shopping mall, the short message or message pushing mode is easy to be ignored, so that the queuing of the user is caused.

Disclosure of Invention

The embodiment of the application provides a queuing and calling method and device based on wearable equipment. The wearable device worn by the user can be utilized to give the user a proper reminding mode for queuing and calling, so that the user can better know the queuing condition.

In a first aspect, the application provides a queuing and calling method based on a wearable device, the method including:

acquiring a queuing serial number distributed by second terminal equipment, and binding the queuing serial number with first terminal equipment; sending a first message to wearable equipment to acquire equipment information of the wearable equipment; in response to receiving the device information of the wearable device, sending a second message to a server; and sending a control instruction to the wearable device in response to receiving the push message sent by the server.

In the first aspect, a first terminal device acquires a queuing number assigned by a second terminal device, and the first terminal device binds the queuing number with the first terminal device while or after acquiring the queuing number, and establishes a corresponding relationship; then the first terminal device sends a first message to the wearable device to acquire device information of the wearable device; after the wearable device sends the device information of the wearable device to the first terminal device, the first terminal device sends a second message to the server to indicate the server to generate a push ID; when the user queue number is up, the second terminal device sends a message to inform the server, and then the server sends a push message to the first terminal device. After receiving the push message sent by the server, the first terminal device sends a control instruction to the wearable device, so that the wearable device carries out corresponding reminding. The method can utilize the wearable device to remind, so that the queuing reminding becomes more personalized and effective, and a proper reminding mode for queuing and calling is given to the user, so that the user can better know the queuing condition.

Optionally, in a possible implementation manner of the first aspect, the obtaining, by the first terminal device, the queuing sequence number allocated by the second terminal device includes: the first terminal equipment can scan the two-dimensional code generated by the second terminal equipment through the camera to acquire a queuing number; or the first terminal equipment can read the RFID label of the second terminal equipment through the NFC module to acquire the queuing sequence number; or the second terminal device may scan the two-dimensional code generated by the first terminal device through the camera to obtain the queuing number. Through the implementation mode, the mode of acquiring the queuing number is diversified, and the user experience is improved.

Optionally, in a possible implementation manner of the first aspect, the obtaining, by the first terminal device, the queuing sequence number allocated by the second terminal device includes: the first terminal equipment comprises a queuing push application, and the second terminal equipment sends the queuing sequence number to the first terminal equipment in response to the operation of the queuing push application. Through the implementation mode, the mode of acquiring the queuing number is diversified, and the user experience is improved.

Optionally, in a possible implementation manner of the first aspect, the binding the queuing sequence number and the first terminal device includes: after acquiring a queuing serial number distributed by second terminal equipment, first terminal equipment correspondingly binds equipment information of the first terminal with the queuing serial number; or acquiring the queuing sequence number distributed by the second terminal equipment based on the equipment information of the first terminal. Through the implementation mode, the queuing sequence number and the terminal equipment are uniquely bound, and wrong reminding is avoided.

Optionally, in a possible implementation manner of the first aspect, the device information of the first terminal includes an SN number of the first terminal.

Optionally, in a possible implementation manner of the first aspect, the device information of the wearable device includes: the SN of the wearable device and/or the IMEI of the wearable device, and the device type of the wearable device.

Optionally, in a possible implementation manner of the first aspect, the sending the first message to the wearable device, and acquiring the device information of the wearable device includes: and periodically sending a first message to the wearable device at a preset time interval to acquire the device information of the wearable device. Through the implementation mode, the first terminal equipment can acquire the condition of the wearable equipment connected with the first terminal equipment in real time.

In a second aspect, the present application provides a wearable device-based queuing and calling apparatus, wherein the apparatus includes a processor, the processor is coupled with a memory, and the processor reads and executes instructions in the memory, so that the apparatus implements the method and steps of any one of the foregoing aspects.

In a second aspect, the present application provides a computer-readable storage medium having instructions stored thereon, which when executed on a terminal device, cause the terminal device to implement the method and steps of any of the preceding aspects.

Drawings

Fig. 1 is a diagram of a network architecture consisting of a terminal device, a wearable device and a server;

fig. 2 is a diagram illustrating a structure of a terminal device;

fig. 3 is a schematic flow chart of a queuing and calling method based on a wearable device;

4A-4C are display interfaces of a queuing push application;

fig. 5 is a schematic diagram of information interaction between the terminal device 12 and the wearable device 10;

fig. 6 is a mapping relationship table corresponding to device types and device alert types;

fig. 7 is a table of mapping relationships between push IDs and SNs of wearable devices, device types of wearable devices, and account IDs of terminal devices;

fig. 8 is a table of a mapping relationship between push IDs and queuing numbers.

Detailed Description

The technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application.

The technical scheme is mainly applied to giving reasonable prompts to the user when the user queues in a merchant and waits for numbers, so that the user is prevented from missing the number calling. For the user, the user can be freely deactivated without waiting at a merchant, so that unnecessary time waste is avoided; for the merchant, the merchant pays no additional cost, does not need to increase equipment or labor cost, and even does not need to provide paper-version queuing number tickets for users. Compared with the mobile phone short message or application message push calling in the prior art, the method and the device can also overcome the noisy situation of the position of the user, give various prompts to the user, and enable the user to avoid missing the calling. The invention aims to provide a queuing and calling method based on wearable equipment for realizing zero cost of merchants, which pushes a calling message to the wearable equipment of a user, such as a bracelet, an earphone, glasses, a watch and the like of the user, and when the calling message arrives, the perception of the user is enhanced through the forms of bracelet vibration, earphone ringing, characters appearing on the glasses and the like, so that a strong reminding effect is achieved.

The scheme related to the application is mainly applied to a network architecture formed by terminal equipment, wearable equipment and a server, wherein the terminal equipment can include any terminal equipment or portable terminal equipment such as a mobile phone, a tablet computer, a Personal Digital Assistant (PDA), a laptop computer (laptop), a mobile computer and the like. Exemplary embodiments of the portable terminal device include, but are not limited to, those that carry iOS, android, microsoft, or other operating systems. Wherein, the wearable device can include but is not limited to smart watch, bracelet, glasses, earphone, AR \ VR device and so on with wireless connection function. The embodiment of the application does not specifically limit the types of the terminal device and the wearable device.

Fig. 1 is a diagram of a network architecture composed of a terminal device, a wearable device, and a server according to an embodiment of the present disclosure, and referring to fig. 1, the network architecture includes a terminal device 12, a wearable device 10, a server 14, and a terminal device 16. The terminal device 12 and the server 14, and the server 14 and the terminal device 16 may be connected through a communication network, which may be a wireless communication network, for example, a wifi (wireless fidelity) network, a 3G network, or an LTE (Long Term Evolution) network, a mobile communication network such as 4g,5g, etc. In one possible implementation, the terminal device 12 and the server 14, and the server 14 and the terminal device 16 may be connected through a wired communication network. The embodiment of the present application may further include other types of networking modes, which is not limited in this respect.

Fig. 2 is a diagram of a structural example of a terminal device according to an embodiment of the present application, which can be regarded as a structural example diagram of the terminal device 12 and the terminal device 16. As shown in fig. 1. The terminal device may include a processor 110, an external memory interface 120, an internal memory 121, a Universal Serial Bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, a sensor module 180, a display screen 194, and the like. The sensor module 180 may include a pressure sensor 180A, a gyroscope sensor 180B, an air pressure sensor 180C, a magnetic sensor 180D, an acceleration sensor 180E, a distance sensor 180F, a proximity light sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, a bone conduction sensor 180M, and the like.

It is to be understood that the illustrated structure of the present embodiment does not constitute a specific limitation to the terminal device. In other embodiments, the terminal device may include more or fewer components than shown, or combine certain components, or split certain components, or a different arrangement of components. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

Processor 110 may include one or more processing units, such as: the processor 110 may include an Application Processor (AP), a modem processor, a Graphics Processing Unit (GPU), an Image Signal Processor (ISP), a controller, a video codec, a Digital Signal Processor (DSP), a baseband processor, and/or a neural-Network Processing Unit (NPU), etc. Wherein, the different processing units may be independent devices or may be integrated in one or more processors. For example, in the present application, the processor 110 may obtain current state information.

The controller can be a neural center and a command center of the terminal equipment. The controller can generate an operation control signal according to the instruction operation code and the time sequence signal to finish the control of instruction fetching and instruction execution.

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

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

The I2C interface is a bidirectional synchronous serial bus including a serial data line (SDA) and a Serial Clock Line (SCL). In some embodiments, the processor 110 may include multiple sets of I2C buses. The processor 110 may be coupled to the touch sensor 180K, the charger, etc., through different I2C bus interfaces, respectively. For example: the processor 110 may be coupled to the touch sensor 180K through an I2C interface, so that the processor 110 and the touch sensor 180K communicate through an I2C bus interface, thereby implementing a touch function of the terminal device.

The UART interface is a universal serial data bus used for asynchronous communications. The bus may be a bidirectional communication bus. It converts the data to be transmitted between serial communication and parallel communication. In some embodiments, a UART interface is generally used to connect the processor 110 with the wireless communication module 160. For example: the processor 110 communicates with a bluetooth module in the wireless communication module 160 through a UART interface to implement a bluetooth function.

A MIPI interface may be used to connect processor 110 with peripheral devices such as display screen 194. The MIPI interface includes a Camera Serial Interface (CSI), a Display Serial Interface (DSI), and the like. In some embodiments, processor 110 and display screen 194 communicate via a DSI interface to implement the display functionality of the terminal device.

The GPIO interface may be configured by software. The GPIO interface may be configured as a control signal and may also be configured as a data signal. In some embodiments, a GPIO interface may be used to connect the processor 110 with the display screen 194, the wireless communication module 160, the sensor module 180, and the like. The GPIO interface may also be configured as an I2C interface, I2S interface, UART interface, MIPI interface, and the like.

The USB interface 130 is an interface conforming to the USB standard specification, and may be a Mini USB interface, a Micro USB interface, a USB Type C interface, or the like. The USB interface 130 may be used to connect a charger to charge the terminal device, and may also be used to transmit data between the terminal device and the peripheral device. And the earphone can also be used for connecting an earphone and playing audio through the earphone. The interface may also be used to connect other electronic devices, such as AR devices and the like.

It should be understood that the interface connection relationship between the modules illustrated in this embodiment is only an exemplary illustration, and does not constitute a limitation on the structure of the terminal device. In other embodiments of the present application, the terminal device may also adopt different interface connection manners or a combination of multiple interface connection manners in the foregoing embodiments.

The charging management module 140 is configured to receive charging input from a charger. The charger may be a wireless charger or a wired charger. In some wired charging embodiments, the charging management module 140 may receive charging input from a wired charger via the USB interface 130. In some wireless charging embodiments, the charging management module 140 may receive a wireless charging input through a wireless charging coil of the terminal device. The charging management module 140 may also supply power to the terminal device through the power management module 141 while charging the battery 142.

The power management module 141 is used to connect the battery 142, the charging management module 140 and the processor 110. The power management module 141 receives input from the battery 142 and/or the charging management module 140, and supplies power to the processor 110, the internal memory 121, the display screen 194, the wireless communication module 160, and the like. The power management module 141 may also be used to monitor parameters such as battery capacity, battery cycle count, battery state of health (leakage, impedance), etc. In some other embodiments, the power management module 141 may also be disposed in the processor 110. In other embodiments, the power management module 141 and the charging management module 140 may be disposed in the same device.

The wireless communication function of the terminal device can be realized by the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, the modem processor, the baseband processor, and the like.

The antennas 1 and 2 are used for transmitting and receiving electromagnetic wave signals. Each antenna in a terminal device may be used to cover a single or multiple communication bands. Different antennas can also be multiplexed to improve the utilization of the antennas. For example: the antenna 1 may be multiplexed as a diversity antenna of a wireless local area network. In other embodiments, the antenna may be used in conjunction with a tuning switch.

The mobile communication module 150 may provide a solution including 2G/3G/4G/5G wireless communication applied on the terminal device. The mobile communication module 150 may include at least one filter, a switch, a power amplifier, a Low Noise Amplifier (LNA), and the like. The mobile communication module 150 may receive the electromagnetic wave from the antenna 1, filter, amplify, etc. the received electromagnetic wave, and transmit the electromagnetic wave to the modem processor for demodulation. The mobile communication module 150 may also amplify the signal modulated by the modem processor, and convert the signal into electromagnetic wave through the antenna 1 to radiate the electromagnetic wave. In some embodiments, at least some of the functional modules of the mobile communication module 150 may be disposed in the processor 110. In some embodiments, at least some of the functional modules of the mobile communication module 150 may be disposed in the same device as at least some of the modules of the processor 110.

The modem processor may include a modulator and a demodulator. The modulator is used for modulating a low-frequency baseband signal to be transmitted into a medium-high frequency signal. The demodulator is used for demodulating the received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then passes the demodulated low frequency baseband signal to a baseband processor for processing. The low frequency baseband signal is processed by the baseband processor and then transferred to the application processor. The application processor displays images or video via the display screen 194. In some embodiments, the modem processor may be a stand-alone device. In other embodiments, the modem processor may be provided in the same device as the mobile communication module 150 or other functional modules, independent of the processor 110.

The wireless communication module 160 may provide solutions for wireless communication applied to the terminal device, including Wireless Local Area Networks (WLANs) (such as wireless fidelity (Wi-Fi) networks), bluetooth (BT), global Navigation Satellite Systems (GNSS), frequency Modulation (FM), near Field Communication (NFC), infrared (IR), and the like. The wireless communication module 160 may be one or more devices integrating at least one communication processing unit. The wireless communication module 160 receives electromagnetic waves via the antenna 2, performs frequency modulation and filtering processing on electromagnetic wave signals, and transmits the processed signals to the processor 110. The wireless communication module 160 may also receive a signal to be transmitted from the processor 110, perform frequency modulation and amplification on the signal, and convert the signal into electromagnetic waves through the antenna 2 to radiate the electromagnetic waves.

In some embodiments, the terminal device's antenna 1 is coupled to the mobile communication module 150 and the antenna 2 is coupled to the wireless communication module 160 so that the terminal device can communicate with the network and other devices through wireless communication techniques.

The terminal device realizes the display function through the GPU, the display screen 194, and the application processor. The GPU is a microprocessor for image processing, and is connected to the display screen 194 and an application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. The processor 110 may include one or more GPUs that execute program instructions to generate or alter display information.

The display screen 194 is used to display images, video, and the like. The display screen 194 includes a display panel. The display panel may be a Liquid Crystal Display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (active-matrix organic light-emitting diode, AMOLED), a flexible light-emitting diode (FLED), a miniature, a Micro-OLED, a quantum dot light-emitting diode (QLED), or the like. In some embodiments, the terminal device may include 1 or N display screens 194, N being a positive integer greater than 1.

A series of Graphical User Interfaces (GUIs) may be displayed on the display screen 194 of the terminal device, and these GUIs are the main screens of the terminal device. Generally, the size of the display screen 194 of the terminal device is fixed, and only a limited number of controls can be displayed in the display screen 194 of the terminal device. A control is a GUI element, which is a software component contained in an application program and controls all data processed by the application program and interactive operations related to the data, and a user can interact with the control through direct manipulation (direct manipulation) to read or edit information related to the application program. Generally, a control may include a visual interface element such as an icon, button, menu, tab, text box, dialog box, status bar, navigation bar, widget, and the like. For example, in the present embodiment, the display screen 194 may display virtual keys (one-key arrangement, start arrangement, stop arrangement).

The external memory interface 120 may be used to connect an external memory card, such as a Micro SD card, to extend the storage capability of the terminal device. The external memory card communicates with the processor 110 through the external memory interface 120 to implement a data storage function. For example, files such as music, video, etc. are saved in an external memory card.

The internal memory 121 may be used to store computer-executable program code, which includes instructions. The processor 110 executes various functional applications of the terminal device and data processing by executing instructions stored in the internal memory 121. For example, in the present embodiment, the processor 110 may perform scene arrangement by executing instructions stored in the internal memory 121. The internal memory 121 may include a program storage area and a data storage area. The storage program area may store an operating system, an application program (such as a sound playing function, an image playing function, etc.) required by at least one function, and the like. The storage data area may store data (such as audio data, a phonebook, etc.) created during use of the terminal device, and the like. In addition, the internal memory 121 may include a high-speed random access memory, and may further include a nonvolatile memory, such as at least one magnetic disk storage device, a flash memory device, a universal flash memory (UFS), and the like. The processor 110 executes various functional applications of the terminal device and data processing by executing instructions stored in the internal memory 121 and/or instructions stored in a memory provided in the processor.

The pressure sensor 180A is used for sensing a pressure signal, and can convert the pressure signal into an electrical signal. In some embodiments, the pressure sensor 180A may be disposed on the display screen 194. The pressure sensor 180A can be of a wide variety, such as a resistive pressure sensor, an inductive pressure sensor, a capacitive pressure sensor, and the like. The capacitive pressure sensor may be a sensor comprising at least two parallel plates having an electrically conductive material. When a force acts on the pressure sensor 180A, the capacitance between the electrodes changes. The terminal device determines the intensity of the pressure from the change in capacitance. When a touch operation is applied to the display screen 194, the terminal device detects the intensity of the touch operation according to the pressure sensor 180A. The terminal device may also calculate the touched position from the detection signal of the pressure sensor 180A. In some embodiments, the touch operations that are applied to the same touch position but have different touch operation intensities may correspond to different operation instructions. For example: and when the touch operation with the touch operation intensity smaller than the first pressure threshold value acts on the short message application icon, executing an instruction for viewing the short message. And when the touch operation with the touch operation intensity larger than or equal to the first pressure threshold value acts on the short message application icon, executing an instruction of newly building the short message.

The gyro sensor 180B may be used to determine the motion attitude of the terminal device. In some embodiments, the angular velocity of the terminal device about three axes (i.e., x, y, and z axes) may be determined by the gyro sensor 180B. The gyro sensor 180B may be used for photographing anti-shake. Illustratively, when the shutter is pressed, the gyroscope sensor 180B detects the shake angle of the terminal device, calculates the distance to be compensated for by the lens module according to the shake angle, and enables the lens to counteract the shake of the terminal device through reverse movement, thereby achieving anti-shake. The gyroscope sensor 180B may also be used for navigation, somatosensory gaming scenes.

The air pressure sensor 180C is used to measure air pressure. In some embodiments, the terminal device calculates altitude, aiding positioning and navigation, from the barometric pressure measured by barometric pressure sensor 180C.

The magnetic sensor 180D includes a hall sensor. The terminal device can detect the opening and closing of the flip holster by using the magnetic sensor 180D. In some embodiments, when the terminal device is a flip, the terminal device may detect the opening and closing of the flip according to the magnetic sensor 180D. And then according to the detected opening and closing state of the leather sheath or the opening and closing state of the flip, the characteristics of automatic unlocking of the flip and the like are set.

The acceleration sensor 180E can detect the magnitude of acceleration of the terminal device in various directions (generally, three axes). When the terminal equipment is static, the size and the direction of gravity can be detected. The method can also be used for identifying the attitude of the terminal equipment, and is applied to horizontal and vertical screen switching, pedometers and other applications.

A distance sensor 180F for measuring a distance. The terminal device may measure the distance by infrared or laser. In some embodiments, the scene is photographed and the terminal device may range using the distance sensor 180F to achieve fast focus.

The proximity light sensor 180G may include, for example, a Light Emitting Diode (LED) and a light detector, such as a photodiode. The light emitting diode may be an infrared light emitting diode. The terminal device emits infrared light to the outside through the light emitting diode. The terminal device detects infrared reflected light from a nearby object using a photodiode. When sufficient reflected light is detected, it can be determined that there is an object near the terminal device. When insufficient reflected light is detected, the terminal device may determine that there is no object near the terminal device. The terminal device can detect that the user holds the terminal device by using the proximity light sensor 180G and calls by being close to ears, so that the screen is automatically extinguished to achieve the purpose of saving power. The proximity light sensor 180G may also be used in a holster mode, a pocket mode automatically unlocks and locks the screen.

The ambient light sensor 180L is used to sense the ambient light level. The terminal device may adaptively adjust the brightness of the display screen 194 according to the perceived ambient light level. The ambient light sensor 180L may also be used to automatically adjust the white balance when taking a picture. The ambient light sensor 180L may also cooperate with the proximity light sensor 180G to detect whether the terminal device is in a pocket, so as to prevent accidental touch.

The fingerprint sensor 180H is used to collect a fingerprint. The terminal equipment can utilize the collected fingerprint characteristics to realize fingerprint unlocking, access to an application lock, fingerprint photographing, fingerprint incoming call answering and the like.

The temperature sensor 180J is used to detect temperature. In some embodiments, the terminal device executes a temperature processing strategy using the temperature detected by the temperature sensor 180J. For example, when the temperature reported by the temperature sensor 180J exceeds the threshold, the terminal device performs a reduction in the performance of the processor located near the temperature sensor 180J, so as to reduce power consumption and implement thermal protection. In other embodiments, the terminal device heats the battery 142 when the temperature is below another threshold to avoid abnormal shutdown of the terminal device due to low temperatures. In other embodiments, the terminal device performs boosting of the output voltage of the battery 142 when the temperature is below a further threshold value to avoid abnormal shutdown due to low temperature.

The touch sensor 180K is also called a "touch device". The touch sensor 180K may be disposed on the display screen 194, and the touch sensor 180K and the display screen 194 form a touch screen, which is also called a "touch screen". The touch sensor 180K is used to detect a touch operation applied thereto or nearby. The touch sensor can communicate the detected touch operation to the application processor to determine the touch event type. Visual output associated with the touch operation may be provided through the display screen 194. In other embodiments, the touch sensor 180K may be disposed on the surface of the terminal device at a different position than the display screen 194.

The bone conduction sensor 180M may acquire a vibration signal. In some embodiments, the bone conduction sensor 180M may acquire a vibration signal of the human vocal part vibrating the bone mass. The bone conduction sensor 180M may also contact the human body pulse to receive the blood pressure pulsation signal. In some embodiments, the bone conduction sensor 180M may also be disposed in a headset, integrated into a bone conduction headset. The audio module 170 may analyze a voice signal based on the vibration signal of the bone mass vibrated by the sound part acquired by the bone conduction sensor 180M, so as to implement a voice function. The application processor can analyze heart rate information based on the blood pressure beating signal acquired by the bone conduction sensor 180M, so as to realize the heart rate detection function.

Fig. 3 is a schematic flowchart of a queuing and calling method based on a wearable device according to an embodiment of the present application, and according to the content described in fig. 3, a detailed scheme of an embodiment of a terminal device according to the present application is as follows:

s101, acquiring a queuing serial number distributed by the terminal equipment 16, and binding the queuing serial number with the terminal equipment 12.

In the embodiment of the present application, the terminal device 16 may be understood as a terminal device at a merchant, and there are various ways for the terminal device 12 to obtain the queuing number assigned by the terminal device at the merchant. In a possible implementation manner, the terminal device 12 may invoke a camera of the terminal device 12 through a queuing push application to scan a two-dimensional code generated by the terminal device 16 at the merchant, so as to obtain a queuing number at the current merchant; or the terminal device 12 may call the NFC module of the terminal device 12 to read the RFID tag of the terminal device 16 at the merchant through the queuing push application, so as to obtain the queuing number at the merchant; or the user two-dimensional code in the queuing push application of the terminal device 12 can be presented to the terminal device 16 at the merchant for scanning, so as to obtain the queuing serial number of the current merchant; or in response to the operation of the user on the queuing push application, the terminal device 12 may receive the queuing number sent by the terminal device 16 at the merchant, where the operation of the user on the queuing push application may be that the user searches for information of a corresponding merchant in the queuing push application, finds the corresponding merchant, and enters the queuing function module at the merchant, and the user triggers queuing through operations such as clicking, sliding, voice input, gesture input, and the like, so that the terminal device 16 at the merchant sends the queuing number to the terminal device 12. After the terminal device 12 obtains the queuing serial number, the terminal device 12 binds the queuing serial number with the terminal device 12, and sends the bound result to the merchant. Fig. 4A-4C are display interfaces of a queuing push application provided by an embodiment of the present application. In the queuing push application shown in fig. 4A, a user may enter a display interface of the queuing push application through operations such as clicking, sliding, voice input, gesture input, and the like for the queuing push application, and then a queuing button is provided on the interface shown in fig. 4B, and the user may trigger a queuing function through operations such as clicking, sliding, voice input, gesture input, and the like for the queuing button to obtain a queuing number.

In a possible implementation manner, the user may obtain a queuing number, for example, a specific number M, at the merchant, and after obtaining the queuing number M, the user may input the queuing number in a queuing push application in the terminal device 12, and the terminal device 12 obtains the queuing number. As shown in the interface of FIG. 4C, the user may enter the queuing number M assigned at the merchant in a blank entry box. After the terminal device 12 obtains the queuing serial number, the terminal device 12 binds the queuing serial number and the terminal device, and sends the bound result to a merchant.

In the embodiment of the present application, the merchant location may be understood as a terminal device 16 at the merchant location, where a queuing system is disposed in the terminal device 16 at the merchant location. The queuing system may generate a real-time queuing number, which the queuing system may send to the user's terminal device 12 through the terminal device 16 at the merchant. The specific implementation comprises the following steps: in response to the user queuing operation, the terminal device 16 at the merchant generates a queuing number M corresponding to the user, where the queuing number M may be generated based on the account ID of the user or based on the SN number of the terminal device.

In a possible implementation manner, the queuing number M may be sent to the server 14 by the terminal device 16 at the merchant, and then sent to the terminal device 12 by the server 14, so that the terminal device 12 obtains the queuing number M; in a possible implementation manner, the queuing number M may be directly sent to the terminal device 12 by the terminal device 16 at the merchant through wireless communication manners such as bluetooth, infrared, WIFI, NFC, and the like; or in a possible implementation manner, since the queuing system of the terminal device 16 at the merchant and the queuing push application in the user terminal device 12 use the same set of algorithm, the camera is called according to the queuing push application to scan the two-dimensional code at the merchant, the queuing push application calls the NFC module to read the RFID tag at the merchant and present the user two-dimensional code in the queuing application, and the two-dimensional code is provided to the merchant for scanning, so that the queuing serial number M consistent with that in the terminal device 16 system at the merchant is generated in the user terminal device 12. In this embodiment of the present application, the server 14 refers to an intermediate device that connects a user terminal device and a terminal device at a merchant, where the server 14 may include a terminal server, a cloud server, and the like, which is not limited in this embodiment of the present application.

In a possible implementation manner, the binding the queuing Number with the terminal device 12 includes that, after the terminal device 12 obtains the queuing Number M, the queuing Number M corresponds to a Serial Number (SN) of the terminal device one to one; or in a possible implementation manner, the terminal device 12 obtains the queuing sequence number M based on the SN when obtaining the queuing sequence number M, that is, the queuing system of the terminal device 16 at the merchant generates a queuing sequence number M corresponding to the terminal device according to the SN of the terminal device. That is, the two possible implementations described above can bind the queuing number M and the terminal device.

The various methods or implementations recited in the embodiments of the present application may be combined to obtain a preferred embodiment, which is not limited in this respect.

S102, sending a first message to the wearable device 10, and acquiring a SN of the wearable device 10 and/or an IMEI (International Mobile Equipment Identity) of the wearable device 10 and a device type of the wearable device 10.

In this embodiment, the wearable device 10 may include an electronic device, such as a smart watch, a bracelet, glasses, an earphone, an AR \ VR device, and the like, connected to the terminal device 12 in a wireless or wired connection manner. The embodiment of the present application does not specifically limit the type of the wearable device.

In this embodiment of the application, after the terminal device 12 obtains the queuing number at the current merchant, or while the terminal device 12 obtains the queuing number at the current merchant, the terminal device 12 sends a first message to the wearable device 10, so as to obtain the SN of the wearable device 10 and/or the IMEI of the wearable device 10 and the device type of the wearable device 10.

The sending, by the terminal device 12, the first message to the wearable device 10 to obtain the SN of the wearable device 10 and/or the IMEI of the wearable device 10 and the device type of the wearable device 10 specifically includes:

fig. 5 is a schematic diagram of information interaction between a terminal device 12 and a wearable device 10 according to an embodiment of the present application. Fig. 5 is only an example, and further modules may be added or related modules may be deleted according to an actual situation, which is not limited in this embodiment of the present application.

In one possible implementation, the queued push application in the terminal device 12 periodically sends a message to the terminal device management center application in the terminal device 12 at preset intervals to inform the terminal device management center application to query the connection status and type of the wearable device 10 connected to the terminal device 12. The terminal device management center application periodically sends a first message to the wearable device 10 through the terminal device 12 at preset intervals, where the first message is used to query the SN of the wearable device 10 currently connected to the terminal device 12 and/or the IMEI of the wearable device 10 and the device type of the wearable device 10, and then the wearable device 10 returns the relevant information to the terminal device 12. After acquiring the SN of the wearable device 10 and/or the IMEI of the wearable device 10 and the device type of the corresponding wearable device 10, the terminal device management center application sends the SN of the wearable device 10 and/or the IMEI of the wearable device 10 and the device type of the corresponding wearable device 10 to the queuing push application. Or in a possible implementation manner, after acquiring the SN of the wearable device 10 and/or the IMEI of the wearable device 10 and the device type of the corresponding wearable device 10, the terminal device management center application stores the SN of the wearable device 10 and/or the IMEI of the wearable device 10 and the device type of the corresponding wearable device 10 in a database of the terminal device management center application.

In a possible implementation manner, after the terminal device 12 acquires the queuing number at the current merchant, or while the terminal device 12 acquires the queuing number at the current merchant, the queuing push application in the terminal device 12 immediately sends a message to the terminal device management center application in the terminal device 12, the terminal device management center application sends a first message to the wearable device 10 through the terminal device 12, the first message is used for querying a SN of the wearable device 10 currently connected to the terminal device 12 and/or an IMEI of the wearable device 10 and a device type corresponding to the wearable device 10, and then the wearable device 10 returns the relevant information to the terminal device 12. After acquiring the SN of the wearable device 10 and/or the IMEI of the wearable device 10 and the device type of the corresponding wearable device 10, the terminal device management center application sends the SN of the wearable device 10 and/or the IMEI of the wearable device 10 and the device type of the corresponding wearable device 10 to the queuing push application. Or in a possible implementation manner, after acquiring the SN of the wearable device 10 and/or the IMEI of the wearable device 10 and the device type of the corresponding wearable device 10, the terminal device management center application stores the SN of the wearable device 10 and/or the IMEI of the wearable device 10 and the device type of the corresponding wearable device 10 in a database of the terminal device management center application.

In the embodiment of the present application, the device types of the wearable device 10 include, but are not limited to: bracelet, earphone, glasses, wrist-watch etc. according to the difference of wearable equipment type, the warning mode that lines up that corresponds is different. Fig. 6 is a mapping relationship table corresponding to device types and device alert types according to an embodiment of the present application. For example, if the wearable device 10 connected to the terminal device 12 is a bracelet, when the serial number of the queue is turned to M, the corresponding bracelet of the user may perform a vibration prompt to inform the user of the serial number of the queue, so that the user may go to a merchant for dining or treatment, etc.; for example, if the wearable device connected to the terminal device is a headset, when the serial number of the queue is up to M, the corresponding headset of the user will sound a ring alarm. In one possible implementation, a wearable device may prompt a user in a combination of alert types, such as a watch or bracelet that may audibly and/or vibrationally alert the user simultaneously and/or sequentially. Wherein in the present application A and/or B represent three cases, A, B and A and B.

In a possible implementation manner, since the wearable device 10 is in a disconnected state from the terminal device 12 or the wearable device 10 is not in a wearing state, the wearable device 10 does not return the SN of the wearable device 10 and/or the IMEI of the wearable device 10 and the device type of the corresponding wearable device 10 to the terminal device 12, wherein the terminal device management center application directly obtains the SN and/or the IMEI of the terminal device 12. The terminal device management center application sends the SN and/or the IMEI of the terminal device 12 to the queuing push application after acquiring the SN and/or the IMEI of the terminal device 12. Or in a possible implementation manner, after acquiring the SN and/or the IMEI of the terminal device 12, the application of the terminal device management center stores the SN and/or the IMEI of the terminal device 12 in a database applied by the terminal device management center. In a possible implementation manner, since no wearable device is connected to the terminal device 12, the corresponding number calling mode is executed in a terminal device message reminding manner. For example, the user queues up the serial number, but the wearable device of the user is disconnected from the terminal device at this time, and the terminal device informs the user of the arrival of the queuing serial number in the form of message push. The reminding mode of message pushing is consistent with the reminding mode of the terminal equipment.

S103, in response to receiving the SN of the wearable device 10 and/or the IMEI of the wearable device 10 and the device type of the wearable device 10, sending a second message to the server 14.

In the embodiment of the application, when the terminal device 12 sends a first message to the wearable device 10 to obtain the SN of the wearable device 10 and/or the IMEI of the wearable device 10 and the device type of the wearable device 10, the wearable device 10 sends the SN of the wearable device 10 and/or the IMEI of the wearable device 10 and the device type of the corresponding wearable device 10 to the terminal device.

In one possible implementation, the wearable device 10 periodically sends the SN of the wearable device 10 and/or the IMEI of the wearable device 10 and the device type of the wearable device 10 to the terminal device 12 at preset time intervals. Alternatively, in a possible implementation manner, the wearable device 10 sends the SN of the wearable device 10 and/or the IMEI of the wearable device 10 and the device type of the corresponding wearable device 10 to the terminal device 12 upon receiving the first message.

Simultaneously with or after the terminal device 12 receives the SN of the wearable device 10 and/or the IMEI of the wearable device 10 and the device type of the wearable device 10 sent by the wearable device 10, the terminal device 12 sends a second message to the server 14. In the embodiment of the present application, the server 14 refers to an intermediate device that connects the user terminal device 12 and the terminal device 16 at the merchant, where the server 14 may include a terminal server, a cloud server, and the like, which is not limited in this embodiment of the present application. Wherein the second message may include at least one of a SN of the wearable device 10 and/or an IMEI of the wearable device 10, a device type of the wearable device 10, and an account ID of the user terminal device 12. In one possible implementation, the second message may include a combination of the SN of the wearable device 10, the device type of the wearable device 10, and the account ID of the user terminal device 12. The account ID of the user terminal device 12 is an ID authenticated by the user when logging in the terminal device 12, such as an account ID and an Apple ID.

In this embodiment, after receiving the second message sent by the terminal device 12, the server 14 performs algorithm conversion on the content in the second message to generate a push ID. In one possible implementation manner, after receiving the SN of the wearable device 10, the device type of the wearable device 10, and the account ID of the user terminal device 12, the server 14 generates an 8-digit push ID by using the SHA256 algorithm. The SHA256 algorithm is only an example, and other types of algorithms may also be used in the embodiments of the present application, which is not limited thereto. Similarly, the 8-bit push ID is only an example in the embodiment of the present application, and other types of push IDs, such as a 4-bit push ID, may also be included, which is not limited herein. Wherein a list of mapping relationships between the push ID and the SN of the wearable device 10, the device type of the wearable device 10 and the account ID of the user terminal device 12 is generated simultaneously in the server 14. Fig. 7 is a mapping table between a push ID and an SN of a wearable device, a device type of the wearable device, and an account ID of a terminal device according to an embodiment of the present application. The push ID and the account ID are represented by letters, which is only one example in the embodiment of the present application, and may also be identified by other characters such as numbers, which is not limited in this respect.

In the embodiment of the present application, after the server 14 generates the push ID, the server 14 sends the push ID to the terminal device 16 at the merchant. In a possible implementation manner, for example, the wearable device SN connected to the terminal device 12 is M1, the device type is a bracelet, the account ID corresponding to the terminal device 12 is ABC, and at this time, the push ID is ABCAKJD. After receiving the push ID, the terminal device 16 at the merchant establishes a one-to-one correspondence between the queuing number M and the push ID, that is, ABCAKJD and M are corresponding mapping relationships. Fig. 8 is a table of a mapping relationship between push IDs and queuing numbers according to an embodiment of the present application. For example, in an embodiment of the present application, terminal device 16 at the merchant may query the M number to obtain ABCAKJD. In a scenario that may be implemented, when the queuing system in the terminal device 16 at the merchant arrives at the queuing number M, the terminal device 16 at the merchant queries the push ID (i.e., ABCAKJD) corresponding to the M number, and after obtaining ABCAKJD, the terminal device 16 at the merchant sends the push ID (i.e., ABCAKJD) to the server 14. After receiving the push ID, the server 14 obtains the SN of the corresponding wearable device 10, the device type of the wearable device 10, and the account ID of the user terminal device 12 by querying the mapping relationship table, and the server 14 sends a push message to the terminal device 12 corresponding to the account ID of the user terminal device. Wherein the push message includes push content and a device type of the wearable device.

In a possible implementation manner, after receiving the push ID, the server 14 obtains, by querying the mapping relationship table, the SN of the corresponding wearable device, the device type of the wearable device, and the account ID of the user terminal device, and the second electronic device sends a push message to the terminal device corresponding to the SN of the user terminal device. Wherein the push message comprises push content and a device type of the wearable device.

S104, receiving the push message sent by the server 14, and sending a control instruction to the wearable device 10.

In this embodiment, after the server 14 receives the push ID sent by the terminal device 16 at the merchant, the server 14 sends a push message to the corresponding terminal device 12 to remind the user that the corresponding queuing number of the user is reached. In particular, the terminal device 12 will receive a push message sent by the server 14, wherein the push message includes push content and a device type of the wearable device. The specific push message is received by the push application, and after the push application receives the push content and the device type of the wearable device, different control instructions are sent to the wearable device through the terminal device according to the device type of the wearable device to prompt that the queuing number of the user is up. The device type and the control command have a mapping relation, and the terminal device inquires a mapping relation table every time so as to determine which type of control command is sent to the wearable device.

The embodiment of the present application further provides a terminal device, where the terminal device includes a processor and a memory, the memory contains executable instructions, and when the processor reads and executes the instructions in the memory, the processor may enable the terminal to implement the methods and functions in S101 to S104 in the foregoing embodiments, and specific execution steps and contents are referred to in S101 to S104, and are not described herein again.

It will be further appreciated by those of ordinary skill in the art that the elements and algorithm steps of the examples described in connection with the embodiments disclosed herein may be embodied in electronic hardware, computer software, or combinations of both, and that the components and steps of the examples have been described in a functional general in the foregoing description for the purpose of illustrating clearly the interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

It will be understood by those skilled in the art that all or part of the steps in the method for implementing the above embodiments may be implemented by a program, and the program may be stored in a computer-readable storage medium, where the storage medium is a non-transitory medium, such as a random access memory, a read only memory, a flash memory, a hard disk, a solid state disk, a magnetic tape (magnetic tape), a floppy disk (floppy disk), an optical disk (optical disk), and any combination thereof.

The above description is only for the preferred embodiment of the present application, but the scope of the present application is not limited thereto, and any changes or substitutions that can be easily conceived by those skilled in the art within the technical scope of the present application should be covered within the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A queuing and calling method based on wearable equipment is applied to first terminal equipment, and is characterized in that the method comprises the following steps:

acquiring a queuing serial number distributed by second terminal equipment, and binding the queuing serial number with first terminal equipment;

after the queuing serial number is obtained or while the queuing serial number is obtained, sending a first message to wearable equipment to obtain equipment information of the wearable equipment; the first message is used for inquiring the SN of the wearable device currently connected with the first terminal device and/or the IMEI of the wearable device and the device type of the corresponding wearable device; responding to the received equipment information of the wearable equipment, sending a second message to a server, so that the server converts the content in the second message through an algorithm, generates a push ID and sends the push ID to the second terminal equipment; establishing a corresponding relation between the queuing sequence number and the push ID in the second terminal equipment; the second message comprises at least one of a SN, an IMEI, a device type of the wearable device and an account ID of the terminal device; the device types of different wearable devices correspond to different queuing reminding modes;

in response to receiving a push message sent by the server, sending a control instruction to the wearable device; the push message comprises push content and the type of the wearable device, when the queue serial number is reached, the second terminal device pushes the push ID corresponding to the queue serial number to the server, and the server sends the push ID after inquiring the mapping relation table.

2. The method according to claim 1, wherein the obtaining of the queuing number assigned by the second terminal device comprises:

the first terminal equipment can scan the two-dimensional code generated by the second terminal equipment through a camera to obtain the queuing number; or alternatively

The first terminal equipment can read the RFID label of the second terminal equipment through an NFC module so as to acquire the queuing sequence number; or alternatively

The second terminal device may scan the two-dimensional code generated by the first terminal device through a camera to obtain the queuing number.

3. The method according to claim 1, wherein the obtaining of the queuing number allocated by the second terminal device comprises:

the first terminal equipment comprises a queuing push application, and the second terminal equipment sends the queuing sequence number to the first terminal equipment in response to the operation of the queuing push application.

4. The method of claim 1, wherein binding the queued sequence number with the first terminal device comprises:

after a queuing serial number distributed by second terminal equipment is obtained, correspondingly binding equipment information of the first terminal equipment with the queuing serial number; or

And acquiring the queuing sequence number distributed by the second terminal equipment based on the equipment information of the first terminal equipment.

5. The method of claim 4, wherein the device information of the first terminal device comprises an SN number of the first terminal device.

6. The method of claim 1, wherein the device information of the wearable device comprises: the SN of the wearable device and/or the IMEI of the wearable device, and the device type of the wearable device.

7. The method of claim 1, wherein sending the first message to a wearable device, and wherein obtaining the device information of the wearable device comprises:

and periodically sending a first message to the wearable device at a preset time interval to acquire the device information of the wearable device.

8. A wearable device number queuing apparatus, wherein the apparatus comprises a processor, the processor is coupled with a memory, and the processor reads and executes instructions in the memory, so that the apparatus implements the method of any one of claims 1 to 7.

9. A computer-readable storage medium having instructions stored thereon, which, when run on a terminal device, cause the terminal device to perform the method of any one of claims 1-7.