CN108037990B

CN108037990B - Task information processing method and device and server

Info

Publication number: CN108037990B
Application number: CN201711369145.9A
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: 2020-11-27
Anticipated expiration: 2037-12-18
Also published as: CN108037990A

Abstract

The embodiment of the application discloses a task information processing method, a task information processing device and a server. The method comprises the following steps: the method comprises the steps that a server receives a task state query request sent by an interactive component, wherein the task state query request carries an account number 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 and the server cannot be in direct communication; judging whether a task corresponding to the account number at the current stage is completed or not, wherein the task comprises subtasks at multiple stages; and when the subtask in the current stage is completed, returning task activation information to the interaction component, and indicating the interaction component to send the task activation information to the third-party client, wherein the task activation information is used for the third-party client to open a task interface. The method enables the third-party client to open the task interface based on the task activation information, and further achieves cross-platform task management between the third-party client and the server.

Description

Task information processing method and device and server

Technical Field

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

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 can give certain rewards to the user after the user performs some task operations, for example, certain points or coupons are distributed to the user. However, the server of the software downloading platform and a third-party client other than the client of the software downloading platform belong to different platforms, and a network link cannot be directly established for communication, so that the third-party client cannot realize cross-platform task management according to the server of the software downloading platform.

Disclosure of Invention

In view of the above problems, the present application provides a method, an apparatus, and a server for task information processing to implement cross-platform task management.

In a first aspect, the present application provides a task information processing method, applied to a server, the method including: the server receives a task state query request sent by an interactive component, wherein the task state query request carries an account bound by a third-party client; judging whether subtasks in the current stage included in the task corresponding to the account are completed or not, wherein the task comprises subtasks in multiple stages; and when the subtask in the current stage is completed, returning task activation information to the interaction component, and indicating the interaction component to send the task activation information to the third-party client, wherein the task activation information is used for the third-party client to open a task interface.

In a second aspect, the present application provides a task information processing apparatus, operating on a server, the apparatus comprising: the data receiving unit is used for receiving a task state query request sent by the interactive component, wherein the task state query request carries an account number bound by a third-party client; the task judging unit is used for judging whether subtasks in the current stage included in the task corresponding to the account are completed or not, wherein the task includes subtasks in multiple stages; and the task information processing unit is used for returning task activation information to the interaction component when the subtask in the current stage is completed, indicating the interaction component to send the task activation information to the third-party client, wherein the task activation information is used for the third-party client to open a task interface.

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 task information processing method, the device and the server, after a task state query request which is sent by an interaction component and carries an account number bound by a third-party client is received, whether a subtask in a current stage, which is included by a task corresponding to the account number, is completed is judged, when the subtask in the current stage is completed, task activation information is returned to the interaction component to indicate the interaction component to send the task activation information to the third-party client, so that the third-party client can open a task interface based on the task activation information, and cross-platform task management between the third-party client and the server is achieved.

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 illustrating a task information processing method proposed in the present application;

FIG. 5 is a schematic diagram of an interface in a task information processing method proposed in the present application;

FIG. 6 is a schematic diagram of another interface in a task information processing method proposed in the present application;

fig. 7 is a schematic diagram illustrating a task interface in a task information processing method according to the present application in a closed state;

FIG. 8 is a schematic diagram of another interface in a task information processing method proposed in the present application;

FIG. 9 is a flow chart illustrating another task information processing method proposed by the present application;

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 is a block diagram illustrating a mobile terminal for performing a task information processing 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 the data in the game center server, so that the third-party client cannot realize cross-platform task management between servers according to the software downloading platform.

Therefore, the inventor proposes a task information processing method, a device and a server for realizing cross-platform task management in the application.

The following first introduces a network environment in which the task information processing method and apparatus provided by the present application operate.

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. As one mode, the interactive component and the client communicate in an inter-process communication mode, or communicate through other api (application Programming interface) protocol interfaces.

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 a task state query request to the server 220 through the network 210, the server 220 starts to query the completion condition of the user task, and when the task corresponding to the account of the user is queried to be completed, the task activation information is returned to the interactive component through the network 210, and the interactive component is instructed to send the task activation information to the third-party client.

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

Referring to fig. 4, a task information processing method provided by the present application is applied to a server, and the method includes:

step S110: the server receives a task state query request sent by the interaction component, wherein the task state query request carries an account number bound by a third-party client.

As one way, the task state query request is sent when the interaction 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 specifically query the task information of a certain user, the task state query request carries an account number bound by a third-party client.

As a mode, the interactive component and the third-party client are both arranged on the same mobile terminal, and the third-party client and the server cannot directly communicate. The third-party client and the server cannot be directly communicated with each other, wherein one way 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.

Step S120: and judging whether the subtasks in the current stage included in the task corresponding to the account are completed or not, wherein the task includes subtasks in multiple stages.

The user can complete the corresponding task through the client corresponding to the server, and it can be understood that when the user executes the task in the client, the user logs in advance by using the account, and when the server stores the task completion state, the server correspondingly stores the account and the completion state of the task corresponding to the account.

The server may configure a task for the account in advance, for example, when the account is registered, a task corresponding to the account is generated correspondingly. And when the server detects that the user logs in the server by using the account, the task corresponding to the account is enabled to take effect. As one way, the server may detect whether the task corresponding to the user account is valid before step S120, and when the task is valid, detect the completion status of the valid task.

By one approach, the multi-phase tasks include 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.

It should be noted that, the specific number of the multiple stages and the specific task content of each stage are not specifically limited in this application, the several stage tasks are merely exemplary, and the number of the stages and the task content of each stage may be set according to actual situations.

Step S130: and when the subtask in the current stage is completed, returning task activation information to the interaction component, and indicating the interaction component to send the task activation information to the third-party client, wherein the task activation information is used for the third-party client to open a task interface.

Step S140: and when the subtask in the current stage is in an incomplete state, returning task incomplete information to the interaction component, and indicating the interaction component to send the task incomplete information to the third-party client, wherein the task incomplete information is used for the third-party client to open a subtask interface in the current stage.

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.

It should be noted that there are various ways to distinguish whether the task interface is opened in the third-party client. As one way, the interfaces in different states may be distinguished, for example, as shown in fig. 7, when the task interface is a button 131, when the button 131 representing the task interface is in the first state, the representing task interface is turned off, in this case, when the third client detects that the user touches the button 131, no response is made. And when the button 131 of the representation task interface is in the second state, as shown in fig. 8, the representation task interface is opened, and in this case, when the third client detects that the user touches the button 131, the browser in the mobile terminal is triggered to display the task interface, or the game center client corresponding to the server is triggered to start and display the task interface.

And when receiving the task activation information, the third client switches the task interface from the first state to the second state. Here, it is understood that the difference between the first state and the second state may be that the button 131 is different in color or may be different in shape. In addition, the task interface may be a button, and may also be text information, an icon, a picture, or the like, and the specific form is not limited in this application.

According to the task information processing method, after a task state query request which is sent by an interaction component and carries an account number bound by a third-party client is received, whether a subtask in the current stage, which is included by a task corresponding to the account number, is completed is judged, when the subtask in the current stage is completed, task activation information is returned to the interaction component to indicate the interaction component to send the task activation information to the third-party client, so that the third-party client can open a task interface based on the task activation information, and cross-platform task management between the third-party client and a server is achieved.

Referring to fig. 9, a task information processing method provided by the present application is applied to a server, and the method includes:

step S210: the server receives a task state query request sent by an interactive component, wherein the task state query request carries an account number 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 subtasks in the current stage included in the task corresponding to the account are completed or not, wherein the task includes subtasks in multiple stages.

Step S230: and when the subtask of the current stage is completed, judging whether a next-stage subtask exists.

For a task, the server may configure the relevance therein, for example, configure the subtask of the previous stage to be completed by the user, and then allow the user to execute the subtask of the next stage. Wherein the orderliness of the phases can be identified by the phase number.

As one mode, a task established in the server is associated with a certain game, and a certain game usually has a plurality of game users, and the tasks corresponding to different game users are different. Correspondingly, when the interactive component sends a task state query request to the server, the request carries the game account of the user bound by the third-party client, and the server correspondingly queries the completion state of the task corresponding to the task ID corresponding to the received game account.

When the established task is a multi-stage subtask, different stages can be distinguished by adding suffixes to task IDs. For example, when the task ID is 123456, the subtask of the first stage is 123456_1, while the subtask of the second stage is 123456_2, and so on for the task IDs of the following stages. For example, when the multi-stage task includes downloading and installing a specified application, completing a comment on the specified application, and completing posting in a specified forum block, and the ID of the task is a, the downloading and installing of the specified application is a subtask in the first stage, the task ID of the specified application is a _1, the completion of the comment on the specified application is a subtask in the second stage, the task ID of the specified application is a _2, and the completion of posting in the specified forum block is a subtask in the third stage, the task ID of the specified application is a _ 3.

As another way, the server may configure the order of the phase tasks in addition to the aforementioned determination of the phase order in terms of the number size of the phase tasks. For example, when the IDs of the plurality of stage tasks included in the task with the task ID a are a _1, a _2, and a _3, the server may configure a _3 as a sub task of the first stage, a _1 as a sub task of the second stage, and a _2 as a sub task of the third stage. Of course, this is only an exemplary sorting manner, and the server may preset a plurality of sorting manners, and the server may be freely selected according to needs.

Step S240: and when the subtask in the current stage is in an incomplete state, returning task incomplete information to the interaction component, and indicating the interaction component to send the task incomplete information to the third-party client, wherein the task incomplete information is used for the third-party client to open a subtask interface in the current stage.

Step S250: and when judging that the next-stage subtask exists, returning task activation information of the next-stage subtask to the interaction component.

Step S260: and when judging that the next-stage subtask does not exist, judging whether a new task exists or not.

Step S270: and when judging that a new task exists, returning task activation information of the new task to the interaction component.

And when judging that a new task exists, ending the process.

And when judging that no new task exists, ending the processing flow.

It should be noted that, when the task activation information is different, the interfaces to which the task interfaces are linked are different. For example, when the task activation information is task activation information of a task in a next stage, the interface linked with the task interface of the third client is an interface of the task in the next stage. And when the task activation information is the task activation information of the new task, the interface linked with the task interface of the third client is the interface of the new task.

According to the task information processing method, after a task state query request which is sent by an interaction component and carries an account number bound by a third-party client is received, whether a subtask in the current stage included by a task corresponding to the account number is completed or not is judged, when the subtask in the current stage is completed, whether a subtask in the next stage or a new task is sequentially judged, task activation information is returned to the interaction component according to a judgment result, the interaction component is instructed to send the task activation information to the third-party client, so that the third-party client can open a task interface based on the task activation information, and cross-platform task management between the third-party client and a server is achieved.

Referring to fig. 10, a task information processing apparatus 300 provided by the present application runs on a server, and the apparatus 300 includes: a data receiving unit 310, a task determining unit 320, and a task information processing unit 330.

The data receiving unit 310 is configured to receive a task state query request sent by an interaction component, where the task state query request carries an account bound to a third-party client, the interaction 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 task determining unit 320 is configured to determine whether a sub task at a current stage included in a task corresponding to the account is completed, where the task includes sub tasks at multiple stages.

And a task information processing unit 330, configured to, when the subtask in the current stage is completed, return task activation information to the interaction component, instruct the interaction component to send the task activation information to the third-party client, where the task activation information is used for the third-party client to open a task interface.

Referring to fig. 11, a task information processing apparatus 400 provided by the present application runs on a server, and the apparatus 400 includes: a data receiving unit 410, a task judging unit 420, and a task information processing unit 430.

The data receiving unit 410 is configured to receive a task state query request sent by an interactive component, where the task state 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.

A task determining unit 420, configured to determine whether a sub task at a current stage included in a task corresponding to the account is completed, where the task includes sub tasks at multiple stages.

And a task information processing unit 430, configured to, when the subtask in the current stage is completed, return task activation information to the interaction component, and instruct the interaction component to send the task activation information to the third-party client, where the task activation information is used by the third-party client to open a task interface.

As one mode, the task information processing unit 430 includes: a stage task determining subunit 431, configured to determine whether there is a next stage subtask when the subtask in the current stage is completed; and the task activation subunit 432 is configured to, when it is determined that there is a next-stage subtask, return task activation information of the next-stage subtask to the interaction component.

As one mode, the task information processing unit 430 further includes: a task change judgment subunit 433, configured to judge whether there is a new task; and when the task change judging subunit 433 judges that a new task exists, the task activating subunit 432 is configured to return task activation information of the new task to the interaction component.

To sum up, after receiving an account number sent by an interaction component and carrying a third-party client binding, a task state query request is sent by the interaction component, whether a subtask in the current stage, which is included by a task corresponding to the account number, is completed or not is judged, when the subtask in the current stage is completed, task activation information is returned to the interaction component to indicate the interaction component sends the task activation information to the third-party client, so that the third-party client can open a task interface based on the task activation information, and cross-platform task management between the third-party client and a server is realized.

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 task information processing method and apparatus, the embodiment of the present application further provides a mobile terminal 100 capable of executing the task information processing method, 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., Institute of Electrical and Electronics Engineers (IEEE) standard IEEE 802.10A, IEEE802.11 b, IEEE802.1 g, and/or IEEE802.1 n), Voice over internet protocol (VoIP), world wide mail Access (Microwave for Wireless communications, Wi-Max), and any other suitable protocols 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 task information processing method is applied to a server, and the method comprises the following steps:

the server receives a task state query request sent by an interactive component, wherein the task state query request carries an account number bound with a third-party client, and the third-party client cannot directly communicate with the server;

judging whether subtasks in the current stage included in the task corresponding to the account are completed or not, wherein the task comprises subtasks in multiple stages;

and when the subtask in the current stage is completed, returning task activation information to the interaction component, and indicating the interaction component to send the task activation information to the third-party client, wherein the task activation information is used for the third-party client to open a task interface.

2. The method of claim 1, wherein the step of returning task activation information to the interactive component when the subtasks of the current phase are completed comprises:

when the subtask of the current stage is completed, judging whether a next-stage subtask exists;

and when judging that the next-stage subtask exists, returning task activation information of the next-stage subtask to the interaction component.

3. The method of claim 2, wherein the step of returning task activation information to the interactive component when the subtasks of the current phase are completed further comprises:

when judging that no next-stage subtask exists, judging whether a new task exists;

and when judging that a new task exists, returning new task activation information to the interaction component.

4. The method according to claim 1, wherein the step of determining whether the subtasks in the current stage included in the task corresponding to the account are completed further includes:

judging whether the task corresponding to the account takes effect;

and when the sub tasks take effect, executing the judgment of whether the sub tasks in the current stage included in the tasks corresponding to the account are completed.

5. The method according to any of claims 1-4, wherein the plurality of phase tasks comprises 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.

6. The method according to any of claims 1-4, wherein the interactive component and the third-party client are both located on the same mobile terminal, and the interactive component is an SDK component.

7. A task information processing apparatus, operating on a server, the apparatus comprising:

the data receiving unit is used for receiving a task state query request sent by the interactive component, wherein the task state query request carries an account number bound with a third-party client, and the third-party client cannot directly communicate with the server;

the task judging unit is used for judging whether subtasks in the current stage included in the task corresponding to the account are completed or not, wherein the task includes subtasks in multiple stages;

and the task information processing unit is used for returning task activation information to the interaction component when the subtask in the current stage is completed, indicating the interaction component to send the task activation information to the third-party client, wherein the task activation information is used for the third-party client to open a task interface.

8. The apparatus according to claim 7, wherein the task information processing unit includes:

a stage task judging subunit, configured to judge whether a next stage subtask exists when the subtask in the current stage is completed;

and the task activation subunit is used for returning task activation information of the next-stage subtask to the interaction component when judging that the next-stage subtask exists.

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.