CN108038729B

CN108038729B - Reward issuing method, device and server

Info

Publication number: CN108038729B
Application number: CN201711369027.8A
Authority: CN
Inventors: 魏濛
Original assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Current assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date: 2017-12-18
Filing date: 2017-12-18
Publication date: 2022-01-11
Anticipated expiration: 2037-12-18
Also published as: CN108038729A

Abstract

The embodiment of the application discloses a reward issuing method, a reward issuing device and a server. The method comprises the steps that a server receives a reward event query request sent by an interactive component, the reward event query request carries an account bound by a third-party client, the interactive component and the third-party client are both arranged on the same mobile terminal, and the third-party client cannot directly communicate with the server; judging whether the account number meets the reward issuing condition or not; and when the account number meets the reward issuing condition, issuing a reward to the user corresponding to the account number through the interaction component. The method ensures that the server can still issue the reward to the account bound with the third client even under the condition that the communication between the third client and the server can not be directly established, thereby realizing the cross-platform reward issuing of the server.

Description

Reward issuing method, device and server

Technical Field

The present application relates to the field of computer technologies, and in particular, to a method, an apparatus, and a server for issuing rewards.

Background

With the development of mobile internet technology, software downloading platforms, such as software stores, software centers or game centers, provide more and more application software. In order to enrich the functions of the software downloading platform and improve the user experience, the software downloading platform gives certain rewards to the user after the user performs some operations, for example, certain points or coupons are distributed to the user. However, the software downloading platform and the client of the third party belong to different platforms, and communication cannot be directly established, so that the reward given to the user by the server of the software downloading platform cannot be issued to the account of the user at the client of the third party, and the server of the software downloading platform cannot realize cross-platform reward issuing.

Disclosure of Invention

In view of the above problems, the present application provides a method, an apparatus and a server for issuing rewards, so as to implement the server to issue rewards across platforms.

In a first aspect, the present application provides a reward issuing method, applied to a server, the method including: the server receives a reward event query request sent by an interactive component, wherein the reward event query request carries an account bound by a third-party client, the interactive component and the third-party client are both arranged on the same mobile terminal, and the third-party client cannot directly communicate with the server;

judging whether the account number meets the reward issuing condition or not; and when the account number meets the reward issuing condition, issuing a reward to the user corresponding to the account number through the interaction component.

In a second aspect, the present application provides a reward dispensing apparatus, operable on a server, the apparatus comprising: the system comprises a data receiving unit, a server and an interaction component, wherein the data receiving unit is used for receiving a reward event query request sent by the interaction component, the reward event query request carries an account bound by a third-party client, the interaction component and the third-party client are both arranged on the same mobile terminal, and the third-party client cannot directly communicate with the server; the reward judging unit is used for judging whether the account meets reward issuing conditions or not; and the reward issuing unit is used for issuing rewards to users corresponding to the account through the interactive component when the account meets the reward issuing conditions.

In a third aspect, the present application provides a server comprising one or more processors and a memory; one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs configured to perform the methods described above.

In a fourth aspect, the present application provides a computer-readable storage medium comprising a stored program, wherein the method described above is performed when the program is run.

According to the reward issuing method, the reward issuing device and the server, after the reward event inquiry request sent by the interactive component and carried with the account bound by the third-party client side is received, whether the account meets reward issuing conditions or not is judged, and when the account meets the reward issuing conditions, the reward is issued to the account through the interactive component, so that even under the condition that communication cannot be directly established between the third client side and the server, the server can still issue the reward to the account bound by the third client side, and therefore the server can issue the reward in a cross-platform mode.

These and other aspects of the present application will be more readily apparent from the following description of the embodiments.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.

FIG. 1 illustrates a schematic diagram of a network environment proposed in the present application;

FIG. 2 is a schematic diagram illustrating an interactive component arrangement proposed in the present application;

FIG. 3 is a schematic diagram of another interactive component arrangement proposed in the present application;

FIG. 4 is a flow chart of a method of reward distribution as set forth herein;

FIG. 5 illustrates an interface diagram of a reward distribution method set forth in the present application;

FIG. 6 is a schematic diagram of another interface in a reward distribution method proposed by the present application;

FIG. 7 is a flow chart of another method of reward distribution set forth herein;

FIG. 8 is a schematic view of an interface in another reward distribution method proposed by the present application;

FIG. 9 is a schematic view of another interface in another prize delivery method set forth herein;

fig. 10 is a block diagram showing a configuration of a content push apparatus proposed in the present application;

fig. 11 is a block diagram showing a structure of another content push apparatus proposed in the present application;

fig. 12 is a block diagram illustrating a structure of a server proposed in the present application;

fig. 13 is a schematic structural diagram of a mobile terminal proposed in the present application;

fig. 14 shows a block diagram of a mobile terminal of the present application for performing a bonus award delivery method according to an embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

The game center installed in the mobile terminal is generally a software download platform for a user to download or update a game client. In order to further enrich the user functions, reward tasks are arranged in the game center, and the users can obtain rewards given by the game center after completing the reward tasks. For example, the user may receive a corresponding reward when downloading and installing a specific application program in the game center, or when completing an evaluation of the application program once.

The game client downloaded by the user from the game center is a third party client relative to the game center. The server address configured in the game client is the address of the game server corresponding to the game client, so that the game client and the game center server cannot directly communicate before. Therefore, the game client as the third-party client generally cannot perform data interaction with data in the game center server, so that the reward given to the user by the server of the software downloading platform cannot be issued to the account of the user at the third-party client, and the server of the software downloading platform cannot realize cross-platform reward issuance.

Therefore, the inventor proposes a reward issuing method, a device and a server for realizing server cross-platform reward issuing in the application.

The network environment in which the reward distribution method and device provided by the present application operate is described first below.

As shown in fig. 1, the mobile terminal 200 and the server 220 are located in a wireless network or a wired network 210, and the mobile terminal 200 and the server 220 perform data interaction through the wireless network or the wired network 210. In the present application, the mobile terminal 200 may be a mobile phone, a tablet computer, or the like.

A client or other interactive components may be run in mobile terminal 200 and server 220 may run a server. The interactive components in the mobile terminal 200 are similar to the client and can independently communicate with the server. The interactive component may be provided in the mobile terminal separately from the client in the mobile terminal 200, as shown in fig. 2, or may be embedded in the client as shown in fig. 3. It will be appreciated that when the interactive component is embedded in the client, it is still running independently of the client.

For example, in the present application, the mobile terminal 200 runs therein an interactive component and a third party client with respect to the server 220, wherein the third party client cannot directly communicate with the server 220, and the interactive component can communicate with the server 220. A server corresponding to the game center runs in the server 220, and based on the network environment, the interaction component may perform data interaction with the server 220 through the network 210, so as to obtain data from the server 220, and transmit the data obtained from the server 220 to the client.

For example, the server 220 stores the progress of the game center user in completing the task and the completion condition. After the interactive component sends an update event query request to the server 220 through the network 210, the server 220 starts to query the completion condition of the user task, when the account number of the user meets the reward obtaining condition, the reward information corresponding to the reward is transmitted to the interactive component through the network 210, and the interactive component sends the reward information to the third client side or the server corresponding to the third client side, so that the reward is sent to the user corresponding to the account number.

Embodiments of the present application will be described in detail below with reference to the accompanying drawings.

Referring to fig. 4, the present application provides a method for issuing rewards, applied to a server, the method including:

step S110: the server receives a reward event query request sent by an interactive component, the reward event query request carries an account bound by a third-party client, the interactive component and the third-party client are both arranged on the same mobile terminal, and the third-party client cannot directly communicate with the server.

As one way, the reward event query request is sent when the interactive component detects that the third-party client is in a preset state. In the present application, the preset state includes one of the following states: when the third-party client is started; the third-party client-side is converted from background operation to foreground operation; and when the third party client receives the update instruction.

The third-party client is started when the mobile terminal is started for the first time after being started, and can also be restarted in the running process. The third-party client operates in the background, which means that the process of the third-party client still operates, but the mobile terminal does not currently display the operation interface of the third-party client, and correspondingly, the third-party client operates in the foreground, which means that the process of the third-party client not only operates, but also the mobile terminal currently displays the operation interface of the third-party client.

As one mode, the update instruction received by the third-party client may be an update instruction triggered manually by a user, for example, the user triggers the update instruction by touching a designated area in an interface of the third-party client, or as shown in fig. 5, slides the interface 111 of the third client along a direction indicated by an arrow in fig. 5, and when the interface 111 slides a preset distance h to a position shown in fig. 6, the update instruction is touched. As another mode, the update instruction received by the third-party client may be an update instruction triggered according to a preset period.

It should be noted that the mobile terminal may respond to a single-finger drag of the user, or may respond to a multi-finger drag to slide the interface 111. The sliding operation is only exemplary, and the present application is not limited to the specific operation, and the operation that the interface 111 can change between two positions is all within the protection scope of the present application.

In the application, in order to inquire the reward information of a certain user in a targeted manner, the reward event inquiry request carries an account bound by a third-party client.

Step S120: and judging whether the account number meets the reward issuing condition or not.

The user can complete the corresponding periodic task through the client corresponding to the server, and it can be understood that the user logs in by using the account in advance when executing the periodic task in the client, and the server correspondingly stores the account and the completion state of the periodic task corresponding to the account when storing the completion state of the periodic task. Based on the above manner, the server may determine whether the account satisfies the reward issuance condition by determining the state of the periodic task corresponding to the account of the user.

Step S130: and when the account number meets the reward issuing condition, issuing a reward to the user corresponding to the account number through the interaction component.

The periodic task may be a single-stage periodic task or a multi-stage periodic task. The periodic task includes at least one of the following tasks: downloading and installing a specified application program; completing the comment on the specified application program; and completing posting in the specified forum plate. When the periodic task is a single-stage periodic task, the user finishes downloading and installing the specified application program, finishes commenting on the specified application program and finishes one stage task in postings in the specified forum plate, and all contents representing the periodic task are finished.

And when the periodic task is a periodic task of a plurality of stages, downloading and installing a specified application program, completing comments on the specified application program and completing posting in a specified forum plate as different stages of the plurality of stages. In this case, the server detects that the previous stage task is completed and activates the next stage task. For example, when a specified application is downloaded and installed, comments to the specified application are completed, and periodic stage tasks posted as sequential ordering are completed in a specified forum block. After the server detects that the user executes the stage task of downloading and installing the specified application program, the user is allowed to execute the stage task of completing the comment of the specified application program, and the same is true for the subsequent period stage task.

As a mode, when the periodic task is a task in a single period, and when the server detects that the task in the single period is completed by the user, it is determined that the account of the user satisfies the reward issuance condition. And when the periodic task is a task in multiple stages, the server judges that the account of the user meets the reward issuing condition when detecting that the user completes the task in at least one stage.

Wherein, a communication link cannot be directly established between the third-party client and the server. The third-party client and the server cannot be directly communicated with each other, wherein one of the situations is that the server corresponding to the third-party client is different from the server corresponding to the interactive component, that is, the address of the server configured in the third-party client for requesting data is not the address of the server corresponding to the interactive component. For example, when the third-party client is a game client, the corresponding server is a game server, and when the third-party client is a client of the instant messaging software, the corresponding server is an instant messaging server. In addition, as another mode, the third-party client is the same as the server corresponding to the server, but the corresponding server is different. It will be appreciated that in this case, there are multiple servers running in the server.

The server may pre-select the category of the third client that determines the binding of the account when issuing the award to the account. As a mode, when it is determined that the third client bound to the account is a stand-alone client, that is, when the client is running, data support of the server may not be required, the reward is sent to the interaction component, and the interaction component is instructed to send the reward to the third client. And the interactive component and the third client can carry out information transmission in a mode of interprocess communication.

As another mode, when it is determined that the third client bound to the account is a networked client, that is, the client needs to perform data interaction with the server when running, the reward is sent to the server corresponding to the third client, and the server corresponding to the third client is instructed to update the reward information corresponding to the account.

It should be noted that, in the present application, the interaction component may be independent from the third-party client, or may be embedded in the third client. The specific type of the interactive component can also be set according to specific requirements. By one approach, it can be an SDK (software Development kit) component.

In the present application, the specific contents of the reward may be set according to actual needs, and the reward may be a point or a coupon.

According to the reward issuing method, after receiving the reward event inquiry request sent by the interaction assembly and carrying the account bound by the third-party client, whether the account meets the reward issuing condition is judged, and when the account meets the reward issuing condition, the reward is issued to the account through the interaction assembly, so that even under the condition that communication cannot be directly established between the third client and the server, the server can still issue the reward to the account bound by the third client, and therefore the server can issue the reward across-platform.

Referring to fig. 7, the present application provides a method for issuing rewards, applied to a server, the method including:

step S210: the server receives a reward event query request sent by an interactive component, the reward event query request carries an account bound by a third-party client, the interactive component and the third-party client are both arranged on the same mobile terminal, and the third-party client cannot directly communicate with the server.

Step S220: and judging whether the account number meets the reward issuing condition or not.

Step S230: and when the account number does not meet the reward issuing condition, returning a notice that the reward cannot be received to the interactive component.

Step S240: and when the account number meets the reward issuing condition, judging the type of the third client.

Step S250: and when the third client bound with the account is judged to be the stand-alone client, sending reward information to the interactive component, and indicating the interactive component to send the reward information to the third client, wherein the reward information is used for the third client to issue a reward corresponding to the reward information.

When the third client is a stand-alone client, the third client can be operated in a state of not accessing the internet, such as some stand-alone games. In this case, the third client displays the reward information transmitted from the interactive component in the interface of the third client to prompt the user to pick up the reward information, and when the user picking up is detected, the information stored locally is updated. For example, as shown in fig. 8, the current gold coin 100 and diamond 200 corresponding to the account bound by the third client are displayed on the interface 251, the gold coin for the present award 100 is displayed on the pop-up window 252, and the button 253 is provided as the user's picking-up interface. When detecting that the user clicks the button 253, as shown in fig. 9, the third client adds 100 to the locally stored gold coins, and synchronously updates the gold coin information in the display interface in the interface 251.

Step S260: and when the third client bound with the account is judged to be a networking client, transmitting reward information to the interaction component, and indicating the interaction component to transmit the reward information to a server corresponding to the third client, wherein the reward information is used for the server corresponding to the third client to issue a reward corresponding to the reward information.

When the third client is a networking client, as a way, data corresponding to the account bound by the third client is stored in the server corresponding to the third client. And when receiving the reward information, the interaction component directly transmits the reward information to a server corresponding to the third client, so that the server corresponding to the third client updates the account corresponding information. After the information of the user is updated, the server corresponding to the third client can send a notice that the reward is received to the third client.

The application provides a reward issue method, after receiving an account number and reward event inquiry request sent by an interactive component and carrying a third-party client binding, judging whether the account number meets reward issue conditions, when the account number meets the reward issue conditions, judging the type of a third client binding the account number, and then issuing the reward for the account number bound by the third client through the interactive component based on the judged type of the third client, so that even under the condition that communication cannot be directly established between the third client and a server, the server still can issue the reward for the account number bound by the third client, and therefore the server can issue the reward across-platform.

Referring to fig. 10, the present application provides a reward distribution apparatus 300 operating on a server, the apparatus 300 including: a data receiving unit 310, a bonus judging unit 320, and a bonus dispensing unit 330.

The data receiving unit 310 is configured to receive a reward event query request sent by an interactive component, where the reward event query request carries an account bound to a third-party client, the interactive component and the third-party client are both disposed in the same mobile terminal, and the third-party client and the server cannot directly communicate with each other.

The reward judging unit 320 is used for judging whether the account number meets the reward issuing condition.

By one approach, the reward issuance conditions include: and the periodic task corresponding to the account is in a finished state. The periodic task comprises a plurality of phase tasks, and the periodic task in a completion state comprises: the task of at least one stage of the plurality of stage tasks is in a completed state.

The plurality of phase tasks includes at least two of the following phase tasks: downloading and installing a specified application program; completing the comment on the specified application program; and completing posting in the specified forum plate.

The reward dispensing unit 330 is configured to dispense a reward to a user corresponding to the account through the interaction component when the account meets the reward dispensing condition.

By one approach, the reward issuance unit 330 includes:

the client determining subunit 331 is configured to determine a type of the third client.

The reward issuing execution subunit 332 is configured to, when the client determining subunit determines that the third client bound to the account is a stand-alone client, send reward information to the interaction component, instruct the interaction component to send the reward information to the third client, where the reward information is used by the third client to issue a reward corresponding to the reward information.

Referring to fig. 11, the present application provides a reward distribution apparatus 400 operating on a server, the apparatus 400 including: a data receiving unit 410, a bonus judging unit 420 and a bonus dispensing unit 430.

The data receiving unit 410 is configured to receive a reward event query request sent by an interactive component, where the reward event query request carries an account bound to a third-party client, the interactive component and the third-party client are both disposed in the same mobile terminal, and the third-party client and the server cannot directly communicate with each other.

The reward judging unit 420 is configured to judge whether the account number meets a reward issuing condition.

And the reward issuing unit 430 is configured to issue a reward to a user corresponding to the account through the interaction component when the account meets the reward issuing condition.

To sum up, the method, the device and the server for issuing the rewards provided by the application judge whether the account meets the reward issuing conditions after receiving the reward event query request sent by the interactive component and carrying the account bound by the third-party client, and when the account meets the reward issuing conditions, the reward is issued to the account through the interactive component, so that the server can still issue the rewards to the account bound by the third client even under the condition that the communication between the third client and the server cannot be directly established, and the server can issue the rewards across-platform rewards.

Referring to fig. 12, based on the content method and apparatus, the present application further provides a server 220 in the environment shown in fig. 1. The server 220 includes one or more processors 222 (only one of which is shown) and memory 224.

Those skilled in the art will appreciate that all other components are peripheral devices with respect to the processor 222, and the processor 222 is coupled to the peripheral devices through a plurality of peripheral interfaces 226. The peripheral interface 226 may be implemented based on the following standards: universal Asynchronous Receiver/Transmitter (UART), General Purpose Input/Output (GPIO), Serial Peripheral Interface (SPI), and Inter-Integrated Circuit (I2C), but the present invention is not limited to these standards. In some examples, the peripheral interface 226 may comprise only a bus. These controllers may also be separate from the peripheral interfaces 226 and integrated within the processor 222 or corresponding peripherals.

The memory 224 may be used to store software programs and modules, and the processor 222 executes various functional applications and data processing by executing the software programs and modules stored in the memory 224. The memory 224 may include high speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid state memory. In some examples, the memory 224 may further include memory that is remotely located from the processor 222.

A mobile terminal provided by the present application will be described with reference to fig. 13 and 14.

Referring to fig. 13, based on the method and the apparatus for issuing the rewards, an embodiment of the present invention further provides a mobile terminal 100 capable of executing the method for issuing the rewards, which includes an electronic body 10, where the electronic body 10 includes a housing 12 and a main display 120 disposed on the housing 12. The housing 12 may be made of metal, such as steel or aluminum alloy. In this embodiment, the main display 120 generally includes a display panel 111, and may also include a circuit or the like for responding to a touch operation performed on the display panel 111. The Display panel 111 may be a Liquid Crystal Display (LCD) panel, and in some embodiments, the Display panel 111 is a touch screen 109.

As shown in fig. 14, in an actual application scenario, the mobile terminal 100 may be used as a smartphone terminal, in which case the electronic body portion 10 generally further includes one or more processors 102 (only one is shown in the figure), a memory 104, an RF (Radio Frequency) module 106, an audio circuit 110, a sensor 114, an input module 118, and a power module 122. It will be understood by those skilled in the art that the present application is not intended to be limited to the configuration of the electronics body portion 10. For example, the electronics body section 10 may include more or fewer components than shown, or have a different configuration than shown.

Those skilled in the art will appreciate that all other components are peripheral devices with respect to the processor 102, and the processor 102 is coupled to the peripheral devices through a plurality of peripheral interfaces 124. The peripheral interface 124 may be implemented based on the following criteria: universal Asynchronous Receiver/Transmitter (UART), General Purpose Input/Output (GPIO), Serial Peripheral Interface (SPI), and Inter-Integrated Circuit (I2C), but the present invention is not limited to these standards. In some examples, the peripheral interface 124 may comprise only a bus; in other examples, the peripheral interface 124 may also include other elements, such as one or more controllers, for example, a display controller for interfacing with the display panel 111 or a memory controller for interfacing with a memory. These controllers may also be separate from the peripheral interface 124 and integrated within the processor 102 or a corresponding peripheral.

The memory 104 may be used to store software programs and modules, and the processor 102 executes various functional applications and data processing by executing the software programs and modules stored in the memory 104. The memory 104 may include high speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid state memory. In some examples, the memory 104 may further include memory located remotely from the processor 102, which may be connected to the electronic body portion 10 or the primary display 120 via a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.

The RF module 106 is configured to receive and transmit electromagnetic waves, and achieve interconversion between the electromagnetic waves and electrical signals, so as to communicate with a communication network or other devices. The RF module 106 may include various existing circuit elements for performing these functions, such as an antenna, a radio frequency transceiver, a digital signal processor, an encryption/decryption chip, a Subscriber Identity Module (SIM) card, memory, and so forth. The RF module 106 may communicate with various networks such as the internet, an intranet, a wireless network, or with other devices via a wireless network. The wireless network may comprise a cellular telephone network, a wireless local area network, or a metropolitan area network. The Wireless network may use various Communication standards, protocols, and technologies, including, but not limited to, Global System for Mobile Communication (GSM), Enhanced Mobile Communication (Enhanced Data GSM Environment, EDGE), wideband Code division multiple Access (W-CDMA), Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Wireless Fidelity (WiFi) (e.g., IEEE802.1 a, IEEE802.11 b, IEEE802.1 g, and/or IEEE802.11 n), Voice over internet protocol (VoIP), world wide mail Access (Microwave for Wireless communications, wimax), and any other suitable protocol for instant messaging, and may even include those protocols that have not yet been developed.

The audio circuitry 110, speaker 101, sound jack 103, microphone 105 collectively provide an audio interface between a user and the electronic body portion 10 or the main display 120. Specifically, the audio circuit 110 receives sound data from the processor 102, converts the sound data into an electrical signal, and transmits the electrical signal to the speaker 101. The speaker 101 converts an electric signal into a sound wave audible to the human ear. The audio circuitry 110 also receives electrical signals from the microphone 105, converts the electrical signals to sound data, and transmits the sound data to the processor 102 for further processing. Audio data may be retrieved from the memory 104 or through the RF module 106. In addition, audio data may also be stored in the memory 104 or transmitted through the RF module 106.

The sensor 114 is disposed in the electronic body portion 10 or the main display 120, examples of the sensor 114 include, but are not limited to: light sensors, operational sensors, pressure sensors, infrared heat sensors, distance sensors, gravitational acceleration sensors, and other sensors.

Specifically, the light sensors may include a light sensor 114F, a pressure sensor 114G. Among them, the pressure sensor 114G may detect a pressure generated by pressing on the mobile terminal 100. That is, the pressure sensor 114G detects pressure generated by contact or pressing between the user and the mobile terminal, for example, contact or pressing between the user's ear and the mobile terminal. Accordingly, the pressure sensor 114G may be used to determine whether contact or pressing has occurred between the user and the mobile terminal 100, as well as the magnitude of the pressure.

Referring to fig. 14 again, in the embodiment shown in fig. 14, the light sensor 114F and the pressure sensor 114G are disposed adjacent to the display panel 111. The light sensor 114F may turn off the display output when an object is near the main display 120, for example, when the electronic body portion 10 moves to the ear.

As one of the motion sensors, the gravity acceleration sensor can detect the magnitude of acceleration in various directions (generally three axes), detect the magnitude and direction of gravity when stationary, and can be used for applications (such as horizontal and vertical screen switching, related games, magnetometer attitude calibration), vibration recognition related functions (such as pedometer, tapping) and the like for recognizing the attitude of the mobile terminal 100. In addition, the electronic body 10 may also be configured with other sensors such as a gyroscope, a barometer, a hygrometer and a thermometer, which are not described herein,

in this embodiment, the input module 118 may include the touch screen 109 disposed on the main display 120, and the touch screen 109 may collect touch operations of the user (for example, operations of the user on or near the touch screen 109 using any suitable object or accessory such as a finger, a stylus, etc.) and drive the corresponding connection device according to a preset program. Optionally, the touch screen 109 may include a touch detection device and a touch controller. The touch detection device detects the touch direction of a user, detects a signal brought by touch operation and transmits the signal to the touch controller; the touch controller receives touch information from the touch detection device, converts the touch information into touch point coordinates, sends the touch point coordinates to the processor 102, and can receive and execute commands sent by the processor 102. In addition, the touch detection function of the touch screen 109 may be implemented by various types, such as resistive, capacitive, infrared, and surface acoustic wave. In addition to the touch screen 109, in other variations, the input module 118 may include other input devices, such as keys. The keys may include, for example, character keys for inputting characters, and control keys for triggering control functions. Examples of such control keys include a "back to home" key, a power on/off key, and the like.

The main display 120 is used to display information input by a user, information provided to the user, and various graphic user interfaces of the electronic body section 10, which may be composed of graphics, text, icons, numbers, video, and any combination thereof, and in one example, the touch screen 109 may be provided on the display panel 111 so as to be integrated with the display panel 111.

The power module 122 is used to provide power supply to the processor 102 and other components. Specifically, the power module 122 may include a power management system, one or more power sources (e.g., batteries or ac power), a charging circuit, a power failure detection circuit, an inverter, a power status indicator light, and any other components associated with the generation, management, and distribution of power within the electronic body portion 10 or the primary display 120.

The mobile terminal 100 further comprises a locator 119, the locator 119 being configured to determine an actual location of the mobile terminal 100. In this embodiment, the locator 119 implements the positioning of the mobile terminal 100 by using a positioning service, which is understood to be a technology or a service for obtaining the position information (e.g., longitude and latitude coordinates) of the mobile terminal 100 by using a specific positioning technology and marking the position of the positioned object on an electronic map.

It should be understood that the mobile terminal 100 described above is not limited to a smartphone terminal, but it should refer to a computer device that can be used in mobility. Specifically, the mobile terminal 100 refers to a mobile computer device equipped with an intelligent operating system, and the mobile terminal 100 includes, but is not limited to, a smart phone, a smart watch, a tablet computer, and the like.

In the description herein, reference to the description of the term "one embodiment," "some embodiments," "an example," "a specific example," or "some examples," etc., means that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the application. In this specification, the schematic representations of the terms used above are not necessarily intended to refer to the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples. Furthermore, various embodiments or examples and features of different embodiments or examples described in this specification can be combined and combined by one skilled in the art without contradiction.

Furthermore, the terms "first", "second" and "first" are used for descriptive purposes only and are not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one such feature. In the description of the present application, "plurality" means at least two, e.g., two, three, etc., unless specifically limited otherwise.

Any process or method descriptions in flow charts or otherwise described herein may be understood as representing modules, segments, or portions of code which include one or more executable instructions for implementing specific logical functions or steps of the process, and the scope of the preferred embodiments of the present application includes other implementations in which functions may be executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved, as would be understood by those reasonably skilled in the art of the present application.

The logic and/or steps represented in the flowcharts or otherwise described herein, e.g., an ordered listing of executable instructions that can be considered to implement logical functions, can be embodied in any computer-readable medium for use by or in connection with an instruction execution system, apparatus, or device, such as a computer-based system, processor-containing system, or other system that can fetch the instructions from the instruction execution system, apparatus, or device and execute the instructions. For the purposes of this description, a "computer-readable medium" can be any means that can contain, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device. More specific examples (a non-exhaustive list) of the computer-readable medium would include the following: an electrical connection (mobile terminal) having one or more wires, a portable computer diskette (magnetic device), a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber device, and a portable compact disc read-only memory (CDROM). Additionally, the computer-readable medium could even be paper or another suitable medium upon which the program is printed, as the program can be electronically captured, via for instance optical scanning of the paper or other medium, then compiled, interpreted or otherwise processed in a suitable manner if necessary, and then stored in a computer memory.

It should be understood that portions of the present application may be implemented in hardware, software, firmware, or a combination thereof. In the above embodiments, the various steps or methods may be implemented in software or firmware stored in memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, any one or combination of the following techniques, which are known in the art, may be used: a discrete logic circuit having a logic gate circuit for implementing a logic function on a data signal, an application specific integrated circuit having an appropriate combinational logic gate circuit, a Programmable Gate Array (PGA), a Field Programmable Gate Array (FPGA), or the like.

It will be understood by those skilled in the art that all or part of the steps carried by the method for implementing the above embodiments may be implemented by hardware related to instructions of a program, which may be stored in a computer readable storage medium, and when the program is executed, the program includes one or a combination of the steps of the method embodiments. In addition, functional units in the embodiments of the present application may be integrated into one processing module, or each unit may exist alone physically, or two or more units are integrated into one module. The integrated module can be realized in a hardware mode, and can also be realized in a software functional module mode. The integrated module, if implemented in the form of a software functional module and sold or used as a stand-alone product, may also be stored in a computer readable storage medium.

The storage medium mentioned above may be a read-only memory, a magnetic or optical disk, etc. Although embodiments of the present application have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting the present application, and that variations, modifications, substitutions and alterations may be made to the above embodiments by those of ordinary skill in the art within the scope of the present application.

Finally, it should be noted that: the above embodiments are only used to illustrate the technical solutions of the present application, and not to limit the same; although the present 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 solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; such modifications and substitutions do not necessarily depart from the spirit and scope of the corresponding technical solutions in the embodiments of the present application.

Claims

1. A reward issuing method applied to a server, the method comprising:

the server receives a reward event query request sent by an interactive component, wherein the reward event query request carries an account bound by a third-party client, the interactive component and the third-party client are both arranged on the same mobile terminal, and the third-party client cannot directly communicate with the server;

judging whether the account number meets the reward issuing condition or not;

and when the account meets the reward issuing condition, sending reward information to the third-party client or a server corresponding to the third-party client through the interaction component, wherein the reward information is used for issuing rewards to users corresponding to the account.

2. The method of claim 1, wherein the step of sending reward information to the third-party client via the interactive component, the reward information being used to issue a reward to the user corresponding to the account includes:

and when the third-party client bound with the account is judged to be the stand-alone client, sending reward information to the interaction component, and indicating the interaction component to send the reward information to the third-party client, wherein the reward information is used for the third-party client to issue a reward corresponding to the reward information.

3. The method of claim 1, wherein the step of sending reward information to a server corresponding to the third-party client through the interactive component, wherein the step of using the reward information to issue a reward to a user corresponding to the account comprises:

and when the third-party client bound with the account is judged to be a networking client, transmitting reward information to the interaction component, and indicating the interaction component to transmit the reward information to a server corresponding to the third-party client, wherein the reward information is used for the server corresponding to the third-party client to issue a reward corresponding to the reward information.

4. A method according to any one of claims 1 to 3, wherein the reward distribution conditions include:

and the periodic task corresponding to the account is in a finished state.

5. The method of claim 4, wherein the periodic task comprises a plurality of phase tasks, the periodic task being in a completed state comprising:

the task of at least one stage of the plurality of stage tasks is in a completed state.

6. The method of claim 5, wherein the plurality of phase tasks includes at least two of the following phase tasks:

downloading and installing a specified application program;

completing the comment on the specified application program; and

and completing posting in the designated forum plate.

7. A reward dispensing apparatus, operable on a server, the apparatus comprising:

the system comprises a data receiving unit, a server and an interaction component, wherein the data receiving unit is used for receiving a reward event query request sent by the interaction component, the reward event query request carries an account bound by a third-party client, the interaction component and the third-party client are both arranged on the same mobile terminal, and the third-party client cannot directly communicate with the server;

the reward judging unit is used for judging whether the account meets reward issuing conditions or not;

and the reward issuing unit is used for sending reward information to the third-party client side or a server corresponding to the third-party client side through the interaction component when the account meets the reward issuing condition, and the reward information is used for issuing rewards to users corresponding to the account.

8. The apparatus of claim 7, wherein the bonus award delivery unit comprises:

a client judging subunit, configured to judge a type of the third-party client,

and the reward issuing execution subunit is used for sending reward information to the interaction component when the client judging subunit judges that the third-party client bound with the account is the stand-alone client, indicating the interaction component to send the reward information to the third-party client, wherein the reward information is used for the third-party client to issue a reward corresponding to the reward information.

9. A server, comprising one or more processors and memory;

one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs configured to perform the method of any of claims 1-6.

10. A computer-readable storage medium, comprising a stored program, wherein the method of any of claims 1-6 is performed when the program is run.