CN111857928A

CN111857928A - Page task access method, device and system, electronic equipment and storage medium

Info

Publication number: CN111857928A
Application number: CN202010716757.6A
Authority: CN
Inventors: 殷勇
Original assignee: Beijing Dajia Internet Information Technology Co Ltd
Current assignee: Beijing Dajia Internet Information Technology Co Ltd
Priority date: 2020-07-23
Filing date: 2020-07-23
Publication date: 2020-10-30

Abstract

The disclosure relates to a page task access method, a device, a system, an electronic device and a storage medium. The method comprises the following steps: generating a corresponding task module according to a target task parameter corresponding to the obtained target task identifier; wherein, the target task identification corresponds to a target task; acquiring interaction information of a target service page through a task module, and generating a page task state corresponding to a target task; the target business page is a related page of a target task, and the page task state comprises a task completion state and a task progress corresponding to the interaction information; and transmitting the page task state to the task system, and responding to an instruction sent by the task system to update the target task. Therefore, excessive attention target tasks are not needed in the development process of the business page, unnecessary repetitive work is avoided, the business page can be quickly accessed into a project system, and the aim of quantitative production is fulfilled.

Description

Page task access method, device and system, electronic equipment and storage medium

Technical Field

The present disclosure relates to the field of web page data processing technologies, and in particular, to a method, an apparatus, a system, an electronic device, and a storage medium for accessing a page task.

Background

With the rapid development of internet technology, various network online technologies are mature more and more, and various online products are generated. Generally, in an operation system in the field of mobile internet, there is a task-based operation mode, that is, a user is guided to browse a plurality of different service pages, and is requested to execute different tasks on different service pages, for example, watching a video, sliding a page, executing praise, adding comments, and the like, and after the user finishes the task, the user is rewarded to a certain extent. In order to facilitate the user to track the execution state of the task at any moment, the task state information is usually maintained on the corresponding business page.

However, in a project, the number of service pages is usually huge, and different service pages are generally sourced from different development teams or different developers, and a method for maintaining task state information is performed on different service pages respectively, so that many repeated tasks are added to the development of the service pages, and the service pages cannot be quickly accessed into a project system.

Disclosure of Invention

The disclosure provides a page task access method, a device, a system, an electronic device and a storage medium, which are used for at least solving the problem that a business page cannot be quickly accessed to a project system in the related art. The technical scheme of the disclosure is as follows:

according to a first aspect of the embodiments of the present disclosure, a method for accessing a page task is provided, including:

generating a corresponding task module according to a target task parameter corresponding to the obtained target task identifier; the target task identification corresponds to a target task;

acquiring interaction information of a target service page through the task module, and generating a page task state corresponding to the target task; the target business page is a related page of the target task, and the page task state comprises a task completion state and a task progress corresponding to the interaction information;

and transmitting the page task state to a task system, and responding to an instruction sent by the task system to update the target task.

In an exemplary embodiment, the obtaining, by the task module, interaction information of a target business page and generating a page task state corresponding to the target task includes:

acquiring the target service page;

generating the page task state in response to an interaction instruction received from the target service page through the task module; and the interactive instruction is generated by interactive operation received by the target service page.

and acquiring the interaction information of a target service page transmitted by a file object of the browser through the task module, and generating a page task state corresponding to the target task.

In an exemplary embodiment, after the transmitting the page task status to a task system and updating the target task in response to an instruction issued by the task system, the method includes:

transmitting a communication result to the task system through a preset interface module, returning to execute the interaction information of the target service page transmitted by the file object of the browser acquired through the task module, and generating a page task state corresponding to the target task; and the communication result is a result of responding to an instruction sent by the task system and updating the target task.

In an exemplary embodiment, the transmitting the page task status to a task system and updating the target task in response to an instruction issued by the task system includes:

and detecting whether the page task state meets a preset condition, transmitting the page task state to the task system when the page task state meets the preset condition, and updating the target task in response to an instruction sent by the task system.

In an exemplary embodiment, when the page task status satisfies the preset condition, transmitting the page task status to the task system, and updating the target task in response to an instruction issued by the task system, includes:

detecting whether the time length of the target task in a preset state reaches a preset time length or not;

and if the time length of the target task in the preset state reaches the preset time length, transmitting the page task state to the task system through a preset interface module, and responding to an instruction sent by the task system to update the target task.

detecting whether the page task state is finished or not;

and if the page task state is finished, transmitting the page task state to the task system through a preset interface module, and responding to an instruction sent by the task system to update the target task.

and switching the target task, and returning to execute the target task parameters corresponding to the obtained target task identifier to generate a corresponding task module.

In an exemplary embodiment, before generating a corresponding task module according to a target task parameter corresponding to an obtained target task identifier, the method includes:

acquiring target task parameters corresponding to the target task identification through a preset interface module; the target task parameter is at least one of a task parameter stored according to a preset network address or a self-defined generated task parameter.

In an exemplary embodiment, the generating a corresponding task module according to the target task parameter corresponding to the obtained target task identifier includes:

acquiring rendering information; the rendering information obtaining method comprises the steps that the rendering information obtaining method comprises the display configuration information of the page task state on the page;

creating a pendant corresponding to the target task according to the rendering information; the pendant is a rendering format established according to the rendering information, and the rendering format comprises internal elements and a display format;

creating a root node, and mounting the pendant to the root node;

and setting target task parameters corresponding to the target task identification according to the pendant to obtain a corresponding task module.

In an exemplary embodiment, after the target task parameter corresponding to the target task identifier is set according to the pendant and the corresponding task module is obtained, the method includes:

and setting the pendant to a preset position, wherein the preset position can be configured.

and packaging the page task access method into a preset format to obtain a corresponding page task access object.

In an exemplary embodiment, the encapsulating the page task access method into a preset format to obtain a corresponding page task access object includes:

and packaging the page task access method into a JavaScript SDK format to obtain a corresponding page task access object.

According to a second aspect of the embodiments of the present disclosure, there is provided a page task access method, including:

acquiring a target task parameter corresponding to a target task identifier through a preset interface module; the target task identification corresponds to a target task;

acquiring rendering information, and creating a pendant corresponding to the target task according to the rendering information;

setting the target task parameters according to the pendants to obtain corresponding task modules;

According to a third aspect of the embodiments of the present disclosure, there is provided a page task access apparatus, including:

the task module generation unit is configured to execute target task parameters corresponding to the obtained target task identifiers and generate corresponding task modules; the target task identification corresponds to a target task;

the page task state generating unit is configured to execute the task module, acquire the interaction information of the target service page and generate a page task state corresponding to the target task; the target business page is a related page of the target task, and the page task state comprises a task completion state and a task progress corresponding to the interaction information;

and the target task updating unit is configured to transmit the page task state to a task system and update the target task in response to an instruction sent by the task system.

In an exemplary embodiment, the page task state generating unit is further configured to perform:

acquiring the target service page;

In an exemplary embodiment, the target task update unit is further configured to perform:

detecting whether the page task state is finished or not;

In an exemplary embodiment, the task module generating unit is further configured to perform:

creating a root node, and mounting the pendant to the root node;

According to a fourth aspect of the embodiments of the present disclosure, there is provided a page task access system, including:

the target task parameter acquisition unit is configured to execute the acquisition of target task parameters corresponding to the target task identifier through a preset interface module; the target task identification corresponds to a target task;

the pendant generating unit is configured to execute the steps of obtaining rendering information and creating a pendant corresponding to the target task according to the rendering information;

the task module generating unit is configured to execute the setting of the target task parameters according to the pendant to obtain a corresponding task module;

According to a fifth aspect of embodiments of the present disclosure, there is provided an electronic apparatus including:

a processor;

a memory for storing the processor-executable instructions;

wherein the processor is configured to execute the instructions to implement the page task access method in any embodiment of the first aspect or the second aspect.

According to a sixth aspect of the embodiments of the present disclosure, there is provided a storage medium, where instructions, when executed by a processor of an electronic device, enable the electronic device to perform the page task access method described in any one of the first aspect or the second aspect.

According to a seventh aspect of embodiments of the present disclosure, there is provided a computer program product, the program product comprising a computer program, the computer program being stored in a readable storage medium, from which at least one processor of a device reads and executes the computer program, so that the device performs the page task access method described in any of the above first or second aspects.

The technical scheme provided by the embodiment of the disclosure at least brings the following beneficial effects:

generating a corresponding task module according to a target task parameter corresponding to the acquired target task identifier, wherein the target task identifier corresponds to a target task, acquiring interaction information of a target service page through the task module, generating a page task state corresponding to the target task, wherein the page task state comprises a task completion state and a task progress corresponding to the interaction information, transmitting the page task state to a task system, receiving the page task state by the task system, and simultaneously controlling the page task state by the task system so that the page task state updates the target task according to an instruction sent by the task system, and service logics between the target task and the corresponding target service page are independent and do not influence each other, so that excessive attention to the target task is not needed in the development process of the service page, and unnecessary repetitive work is avoided, the business page can be quickly accessed into the project system, and the purpose of quantitative production is realized.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and, together with the description, serve to explain the principles of the disclosure and are not to be construed as limiting the disclosure.

Fig. 1 is a flowchart illustrating a page task access method according to an exemplary embodiment.

Fig. 2 is a flowchart illustrating one possible implementation of step S100 according to an exemplary embodiment.

Fig. 3 is a flowchart illustrating a page task access method according to an example embodiment.

FIG. 4 is a diagram illustrating a page task access framework in accordance with an exemplary embodiment.

FIG. 5 is a diagram illustrating a page task access framework in accordance with an exemplary embodiment.

FIG. 6 is a task module work diagram shown in accordance with an exemplary embodiment.

FIG. 7 is a diagram illustrating task pendant generation, according to a particular illustrative embodiment.

Fig. 8 is a block diagram illustrating a page task access device in accordance with an example embodiment.

Fig. 9 is a block diagram illustrating a page task access device, according to an example embodiment.

FIG. 10 is a block diagram illustrating an electronic device for page task access in accordance with an exemplary embodiment.

Detailed Description

In order to make the technical solutions of the present disclosure better understood by those of ordinary skill in the art, the technical solutions in the embodiments of the present disclosure will be clearly and completely described below with reference to the accompanying drawings.

It should be noted that the terms "first," "second," and the like in the description and claims of the present disclosure and in the above-described drawings are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the disclosure described herein are capable of operation in sequences other than those illustrated or otherwise described herein. The implementations described in the exemplary embodiments below are not intended to represent all implementations consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present disclosure, as detailed in the appended claims.

Fig. 1 is a flowchart illustrating a page task access method according to an exemplary embodiment, and as shown in fig. 1, the method includes the following steps:

in step S100, a corresponding task module is generated according to a target task parameter corresponding to the obtained target task identifier; the target task identifier corresponds to one target task.

In step S200, acquiring interaction information of a target service page by a task module, and generating a page task state corresponding to a target task; the target business page is a related page of the target task, and the page task state comprises a task completion state and a task progress corresponding to the interaction information.

In step S300, the page task status is transmitted to the task system, and the target task is updated in response to an instruction issued by the task system.

The target task refers to a task corresponding to a corresponding target service page according to specific requirements, and the target service page is a page displayed to a user. The target task identifier refers to an identifier for uniquely identifying the target task or a corresponding index address. Exemplarily, when the target service page is a page displayed for a user to browse pictures, in order to ensure that the user can completely understand the contents of the pictures in the target service page, the user needs to browse for at least 30 seconds, and at this time, browsing for at least 30 seconds is a target task corresponding to the target service page. The task module is a module for processing the relevant logic of the target task, and the relevant logic comprises the completion state of the task to be recorded and reported and the progress of the task. The task state refers to the state and progress of the user in executing the target task on the business page, for example, whether the user browses pictures, several pictures, the time for browsing pictures is 10 seconds, 20 seconds or 30 seconds, and the like. Optionally, the foregoing is merely an illustration of the target task, and the specific target task further includes a selection state or other operations of a certain target by a user, and the target task is not specifically limited herein.

Specifically, after identification information corresponding to the target task is acquired, the task module is generated according to the corresponding target task parameter. Illustratively, the target task is browsing 10 pictures on the target business page, and browsing is required for at least 30 seconds, then the task module may be used for monitoring the number of pictures browsed by the user and browsing time, so that different target tasks correspond to different task module functions.

After the task module is generated, the task module monitors the interaction behavior of the user, acquires a state corresponding to data needing to be monitored and counted in the task module from the target service page according to the interaction behavior of the user, and determines the state as a page task state. Illustratively, the user operates to enter the target business page at 0 min 0 s at 10 am, and then, at 10 min 0 s10 s, the user browses for 10 s at the target business page, and browsing for 10 s at the target business page is one of the states of the target task. Similarly, the page has 10 pictures, the user browses 3 pictures, and the state that the user browses 3 pictures is also one of the states of the target task.

And after the page task state is obtained, transmitting the page task state to a task system so that the task system correspondingly processes the target task or the target service page according to the corresponding page task state, and generating a corresponding task processing instruction according to a processing result so as to update the target task. Illustratively, if the time for the user to browse the target service page reaches the preset 30 seconds, or if the user browses the preset 3 pictures, it indicates that the user has completed the target task, and this state is reported for replacing the task or rewarding the task, where the rewarding operation may also be regarded as an updated task.

The page task access method comprises the steps of generating a corresponding task module according to a target task parameter corresponding to an acquired target task identifier, acquiring interaction information of a target service page through the task module, generating a page task state corresponding to the target task, wherein the page task state comprises a task completion state and a task progress corresponding to the interaction information, transmitting the page task state to a task system, receiving the page task state by the task system, controlling the page task state by the task system simultaneously, so that the page task state updates the target task according to an instruction sent by the task system, and service logics between the target task and the corresponding target service page are independent and do not influence each other, thereby avoiding excessive attention to the target task in the development process of the service page, unnecessary repetitive work is avoided, the service page can be quickly accessed into the project system, and the aim of quantitative production is fulfilled.

In an exemplary embodiment, one possible implementation of step S200 includes:

acquiring a target service page; generating a page task state in response to an interaction instruction received from a target service page through a task module; the interactive instruction is generated by interactive operation received by the target service page.

The interactive instruction refers to an instruction generated by a user operating on a target service page, for example, an interactive behavior such as clicking to enter the target service page, browsing on the target service page, sliding the page, executing praise, adding comments, and the like is performed.

Specifically, the execution state of the target task is judged according to the interaction instruction received by the target service page, and the page task state comprises a task completion state and a task progress corresponding to the interaction information. Illustratively, the user operates to enter the target business page at 0 min 0 s at 10 am, then, at 10 min 0 s10 s, the user browses for 10 s at the target business page, and the state of browsing for 10 s at the target business page is one of the states of the target task. Similarly, the page has 10 pictures, the user browses 3 pictures, and the state that the user browses 3 pictures is also one of the states of the target task. Or, the number of pictures browsed by the user on the target service page, etc. is also a state of the target task. The specific state statistics are not limited to the browsing time and the browsing number, and the specific page task state statistics are different according to the requirements of different target tasks.

In the above exemplary embodiment, a target service page is obtained; generating a page task state in response to an interaction instruction received from a target service page through a task module; the interactive instruction is generated by interactive operation received by the target service page. Therefore, the execution state of the target task on the target service page is counted by capturing the interaction behavior of the user, so that the page task state is separated from the service logic in the target service page, the page task state does not need to be concerned and maintained in the development process of the service page, unnecessary repeated line work is avoided, the service page can be quickly accessed into a project system, and the quantitative production of the service page can be carried out.

In an exemplary embodiment, one possible implementation of step S200 includes:

and acquiring the interaction information of the target service page transmitted by the file object of the browser through the task module, and generating a page task state corresponding to the target task.

Specifically, interaction information generated by a user performing an operation or the like on a markup service page may be acquired through a file object (document object) of the browser, and a page task state is determined according to the interaction information of the user.

Optionally, after step S300, the communication result is transmitted to the task system through a preset interface module, and step S200 is executed to implement real-time update of the target task. And the communication result is a result of responding to the instruction sent by the task system and updating the target task.

In the above exemplary embodiment, the task module obtains the interaction information of the target service page transmitted by the file object of the browser, generates the page task state corresponding to the target task, and transmits the communication result to the task system through the preset interface module. Therefore, the target task can be updated in real time, the target task is ensured to be updated synchronously on the target service page, and the consistency of background logic and target service page display is ensured.

In an exemplary embodiment, one possible implementation of step S300 includes:

and detecting whether the page task state meets a preset condition, transmitting the page task state to a task system when the page task state meets the preset condition, and updating the target task in response to an instruction sent by the task system.

Optionally, detecting whether the time length of the target task in the preset state reaches the preset time length or not; and if the time length of the target task in the preset state reaches the preset time length, transmitting the page task state to the task system through the preset interface module, and responding to an instruction sent by the task system to update the target task.

Optionally, detecting whether the page task state is completed; and if the page task state is finished, transmitting the page task state to the task system through a preset interface module, and responding to an instruction sent by the task system to update the target task.

Specifically, whether the duration that the target task is in the preset state reaches the preset duration or whether the page task state is completed is detected, if the duration that the target task is in the preset state reaches the preset duration or the page task state is completed, the page task state is transmitted to the task system through the preset interface module as soon as the target task is completed or the target task is completed in a stage mode, and the target task is updated in response to an instruction sent by the task system.

Optionally, after step S300, the method further includes: and switching the target task, and returning to execute the step of generating a corresponding task module according to the target task parameter corresponding to the obtained target task identifier.

Specifically, after a target task is completed, the target task is switched according to the task identifier, a corresponding task module is generated, and the switched target task is monitored and managed. And after the user finishes the corresponding target task, indicating a command for performing the next task, switching the target task, executing a step of generating a corresponding task module according to the task parameter corresponding to the obtained target task identifier, and performing a new round of task monitoring.

Optionally, acquiring a target task parameter corresponding to the target task identifier through a preset interface module; the target task parameter is at least one of a task parameter stored according to a preset network address or a self-defined generated task parameter.

Specifically, the target task parameter corresponding to the target task identifier is obtained through a preset interface module. And acquiring target task parameters according to task parameters stored by a preset network address through a preset interface module, or self-defining generated task parameters through the preset interface module.

Optionally, when a first instruction is received, timing is started to obtain a timing parameter; or, when receiving the first instruction, detecting the task progress in the target business page; and determining the timing parameters and/or the task progress as the page task state.

Specifically, a large part of the task types are timing tasks, and regarding the tasks of the type, the task module judges the task state according to a first instruction obtained by user operation. Or, directly detecting the task progress in the target service page, for example, browsing several pictures, then transmitting the detection result through the interface module, and determining the task state through the external electronic device.

Optionally, the task module can simply communicate with the target business page, so that communication and necessary non-repetitive logic interaction are required, and unnecessary repetitive work can be avoided, so that the target business page can be quickly accessed into the project system.

In the above exemplary embodiment, whether the page task state meets the preset condition is detected, when the page task state meets the preset condition, the page task state is transmitted to the task system, and the target task is updated in response to an instruction sent by the task system. Therefore, the target task can be updated in real time, the target task is ensured to be updated synchronously on the target service page, and the consistency of background logic and target service page display is ensured. After a target task is completed, the target task can be adjusted in time, so that the operation of a user is reduced, and the user experience can be improved to a certain extent.

Fig. 2 is a flowchart of an implementable manner of step S100 shown according to an exemplary embodiment, specifically including the following steps:

in step S110, rendering information is acquired; the rendering information obtaining method comprises the step of obtaining rendering information, wherein the rendering information comprises display configuration information of a page task state on a page.

In step S120, a pendant corresponding to the target task is created according to the rendering information; the pendant is a rendering format established according to the rendering information, and the rendering format comprises internal elements and a display format.

In step S130, a root node is created, and the pendant is mounted to the root node.

In step S140, a target task parameter corresponding to the target task identifier is set according to the pendant, and a corresponding task module is obtained.

The rendering information refers to information such as parameters of an image generated from a model or a display page, for example, description of a three-dimensional object, including geometric, viewpoint, texture, and lighting information.

Specifically, rendering information including display configuration information and the like of a page task state on a page is obtained, the pendant including internal elements and display formats is mounted according to the rendering information, target task parameters corresponding to target task identifiers are set according to the pendant, and a corresponding task module is obtained.

For example, in order to facilitate a user to grasp the progress of doing tasks in real time, a task state view may be generated according to a task state and a task module, and the task state view may be set on a target business page in a form of a pendant, so that the user can see the execution state of a target task and grasp the progress of doing tasks in real time.

Optionally, the pendant is set to a preset position, and the preset position is configurable.

Optionally, the page task access method is packaged in a preset format, and a corresponding page task access object is obtained.

Optionally, the method for accessing the page task is in a JavaScript SDK format, and a corresponding page task access object is obtained.

Specifically, the display position of the task pendant on the target service page can be dynamically adjusted, so that a user can adjust the display position of the pendant, the situation of shielding useful information is avoided, and the experience of the user is improved. And the whole page access method is encapsulated into a JavaScript SDK format and used as an access object of a page task to access the task system, so that the interference of external factors on the page access method is avoided, and the stability of page task access is improved.

In the above exemplary embodiments, the rendering information is acquired; the rendering information is obtained and comprises display configuration information of a page task state on a page; creating a pendant corresponding to the target task according to the rendering information; the pendant is a rendering format established according to the rendering information, and the rendering format comprises internal elements and a display format; creating a root node, and mounting a pendant to the root node; and setting target task parameters corresponding to the target task identification according to the pendant to obtain a corresponding task module. Therefore, the corresponding target task can be displayed on the target service page in a certain form according to the rendering information, and the user can perceive the visual target task pendant in real time and provide the user experience.

Fig. 3 is a flowchart illustrating a page task access method according to an exemplary embodiment, and as shown in fig. 3, the method includes the following steps:

in step S10, a target task parameter corresponding to the target task identifier is obtained through a preset interface module; the target task identifier corresponds to one target task.

In step S20, rendering information is acquired, and a pendant corresponding to the target task is created according to the rendering information.

In step S30, target task parameters are set according to the pendant, and a corresponding task module is obtained.

In step S40, acquiring interaction information of the target service page by the task module, and generating a page task state corresponding to the target task; the target business page is a related page of the target task, and the page task state comprises a task completion state and a task progress corresponding to the interaction information.

In step S50, the page task status is transmitted to the task system, and the target task is updated in response to an instruction issued by the task system.

The target task refers to a task corresponding to a corresponding target service page according to specific requirements, and the target service page is a page displayed to a user. The target task identifier refers to an identifier for uniquely identifying the target task or a corresponding index address. Exemplarily, when the target service page is a page displayed for a user to browse pictures, in order to ensure that the user can completely understand the contents of the pictures in the target service page, the user needs to browse for at least 30 seconds, and at this time, browsing for at least 30 seconds is a target task corresponding to the target service page. The task module is a module for processing the relevant logic of the target task, and the relevant logic comprises the completion state of the task to be recorded and reported and the progress of the task. The task state refers to the state and progress of the user in executing the target task on the business page, for example, whether the user browses pictures, several pictures, the time for browsing pictures is 10 seconds, 20 seconds or 30 seconds, and the like. Optionally, the foregoing is merely an illustration of the target task, and the specific target task further includes a selection state or other operations of a certain target by a user, and the target task is not specifically limited herein. Rendering information refers to information such as parameters of an image or display page generated from a model, for example, a description of a three-dimensional object, including geometry, viewpoint, texture, and lighting information.

Specifically, after a target task parameter corresponding to a target task identifier is obtained through a preset interface module, rendering information is obtained, a pendant corresponding to the target task is created according to the rendering information, the target task parameter is set according to the pendant, and a corresponding task module is obtained. Illustratively, the target task is browsing 10 pictures on the target business page, and browsing is required for at least 30 seconds, then the task module may be used for monitoring the number of pictures browsed by the user and browsing time, so that different target tasks correspond to different task module functions.

The page task access method comprises the steps of obtaining target task parameters corresponding to a target task identifier through a preset interface module, obtaining rendering information, creating a pendant corresponding to a target task according to the rendering information, setting the target task parameters according to the pendant to obtain a corresponding task module, obtaining interaction information of a target service page, generating a page task state corresponding to the target task, wherein the page task state comprises a task completion state and a task progress corresponding to the interaction information, transmitting the page task state to a task system, receiving the page task state by the task system, controlling the page task state by the task system at the same time, enabling the page task state to update the target task according to an instruction sent by the task system, enabling service logics between the target task and the corresponding target service page to be independent and not influenced mutually, and further enabling the development process of the service page to be free from excessive attention to the target task, unnecessary repetitive work is avoided, the service page can be quickly accessed into the project system, and the aim of quantitative production is fulfilled.

In a specific exemplary embodiment, as shown in fig. 4, the page task access framework diagram is shown according to an exemplary embodiment, and the page task access method may be divided into two parts, namely a "task directory" and a "task pendant", where the "task pendant" may be further divided into three parts, namely a "rendering module", a "task module", and an "interface module".

The task directory summarizes the identification and the address of each task and is used for distributing a task page URL to the user. In the process, the task system in the background directly splices the parameters of the task behind the URL as the parameters of the task page.

The page parameters may be: https:// example. com/? the task _ id is 6& task _ time is 5& task _ rewarded is 100.

Optionally, the parameter is not renamed with the predefined parameter of the original page and cannot be used by any role at the front end and the back end of the original page.

The task pendant is a set of SDKs running on the task page, usually written in JavaScript or related languages. Its responsibilities include exposing task status, tracking task progress, communicating with host business pages. As shown in fig. 5, a diagram illustrating a page task access framework is shown, according to an exemplary embodiment. Firstly, reading task parameters from a URL (uniform resource locator), creating a task module by using the parameters, capturing the interaction behavior of farmers according to the task module, reporting the captured interaction behavior to a task server, and triggering a task state view. The visible view part rendered by the task pendant is generally suspended at a fixed position of a screen and does not change position along with page scrolling, so that a user can observe the change of the task state in real time. In order to facilitate low-cost access of a plurality of task pages to the SDK, all logics are packaged into a JavaScript file with a fixed URL address, and then a line of script tags are embedded into the task pages: < script src ═ https:// fix-url/pendant. All parameters required by the initialization task pendant come from a URL parameter output by the background task system on the current target task page, and the task module does not need to manually write a code of the initialization pendant.

And the interface module in the task pendant is responsible for communication between the pendant SDK and the task page serving as the host. Generally, task pendants and business pages do not need to communicate due to the decoupling requirement. Some customized communication capabilities will also be provided in view of versatility. Optionally, reading the task initialization parameter, and besides reading from the URL, performing self-defined initialization parameter of the task page as a global variable read by the pendant SDK; after the task state is reported successfully, the task state is reported to a task page, so that the task page can execute additional logic, such as log record; interaction that the SDK can not track by oneself is facilitated, and the change of the task state is triggered. Therefore, the interface module of the pendant predefines a plurality of event names and corresponding event object structures to realize bidirectional communication with the task page. Of course, depending on the initialization parameters, some events may be invalid. In order to enable the two parties still not to care about the API of the other party, the global event is a relatively friendly mode, and the method belongs to the design category of data decoupling to a certain extent. The document object of the browser may be a good event handler, which may be used to send and receive events. Illustratively, for interaction changes that cannot be captured by a pendant SDK itself, the task page can be programmed to notify without regard to whether and how the task pendant exposes the interface object.

The task module in the task pendant is logic related to special processing tasks, and comprises recording and reporting task progress. For example, for timing tasks of the most predominant task types, the task module is responsible for judging the execution state of the tasks by itself. For other special task types, the interface module is responsible for informing the change of the task state. After the task periodic milestone is achieved, the module is responsible for reporting the task state, and directly initiates a request to a task server through an XMLHttpRequest API, so that the trouble of proxy request of a task page is avoided. FIG. 6 is a task module work diagram, shown in accordance with an exemplary embodiment. Because the uncertainty of cross-domain reporting is larger, once reporting failure occurs, the reporting is retried at least once. Whether the report is successful or failed, the result is notified to the interface module, and then an event is sent to the document to notify the task page of the current task state.

And the rendering module in the task pendant is a module for rendering the appearance of the task pendant. The task pendant appearance can be rendered to have a visual effect unified with a business page, so that the same set of operation activities has consistent task interaction experience.

Optionally, regarding the creation of the pendant elements, due to the diversity of the technical solutions of the task pages, the purpose that the front end outputs either real, Vue or other standardized modules cannot achieve compatibility with all task pages, and therefore, although it is troublesome, the creation of the pendant elements using the native DOM API and the assignment of the visual style are means for achieving comprehensive compatibility. FIG. 7 is a diagram illustrating task pendant generation according to an exemplary embodiment. First, file preparation (documentready) is performed, a root node is created, and a pendant root element is mounted under a < body > element of HTML and is arranged in any corner of a screen in a fixed position. Alternatively, it is possible to obscure key information of the task page no matter where it is placed, so the pendant element must also support draggable. Then create internal elements and styles and listen for interaction events. Optionally, for the safe access of the DOM node, generally, after document ready, that is, after other elements of the current page are rendered and important resources are loaded, the pendant is initialized. Based on the designed task pendant, the task logic and the rendering logic are completely packaged into a unified JavaScript SDK, the cost access of a task page 0 is realized, meanwhile, the task pendant further interacts with the task page, and the customization capability of the special task page is realized.

In the above exemplary embodiment, the task parameter passing through the page address parameter; a completely encapsulated task information presentation and synchronization mechanism; displaying task pendants in the technical scheme; an event-based page and pendant communication mechanism. The cost of accessing the service page into the operation task system is greatly reduced to be almost 0, and the task page is allowed to be produced in batch; and provides richer ability to customize a special task page for interaction with the task system.

It should be understood that although the various steps in the flow charts of fig. 1-7 are shown in order as indicated by the arrows, the steps are not necessarily performed in order as indicated by the arrows. The steps are not performed in the exact order shown and described, and may be performed in other orders, unless explicitly stated otherwise. Moreover, at least some of the steps in fig. 1-6 may include multiple steps or multiple stages, which are not necessarily performed at the same time, but may be performed at different times, which are not necessarily performed in sequence, but may be performed in turn or alternately with other steps or at least some of the other steps.

Fig. 8 is a block diagram illustrating a page task access device, according to an example embodiment. Referring to fig. 8, the apparatus includes a task module generating unit 801, a page task state generating unit 802, and a target task updating unit 803:

a task module generating unit 801 configured to execute a target task parameter corresponding to the obtained target task identifier and generate a corresponding task module; wherein, the target task identification corresponds to a target task;

a page task state generating unit 802, configured to execute the task module to obtain the interaction information of the target service page, and generate a page task state corresponding to the target task; the target business page is a related page of a target task, and the page task state comprises a task completion state and a task progress corresponding to the interaction information;

and a target task updating unit 803 configured to execute transmitting the page task state to the task system and update the target task in response to an instruction issued by the task system.

In an exemplary embodiment, the page task state generating unit 802 is further configured to perform: acquiring a target service page; generating a page task state in response to an interaction instruction received from a target service page through a task module; the interactive instruction is generated by interactive operation received by the target service page.

In an exemplary embodiment, the page task state generating unit 802 is further configured to perform: and acquiring the interaction information of the target service page transmitted by the file object of the browser through the task module, and generating a page task state corresponding to the target task.

In an exemplary embodiment, the target task update unit 803 is further configured to perform: transmitting the communication result to a task system through a preset interface module, returning to execute the interaction information of the target service page transmitted by the file object of the browser acquired through the task module, and generating a page task state corresponding to the target task; and the communication result is a result of responding to the instruction sent by the task system and updating the target task.

In an exemplary embodiment, the target task update unit 803 is further configured to perform: and detecting whether the page task state meets a preset condition, transmitting the page task state to a task system when the page task state meets the preset condition, and updating the target task in response to an instruction sent by the task system.

In an exemplary embodiment, the target task update unit 803 is further configured to perform: detecting whether the time length of the target task in a preset state reaches a preset time length or not; and if the time length of the target task in the preset state reaches the preset time length, transmitting the page task state to the task system through the preset interface module, and responding to an instruction sent by the task system to update the target task.

In an exemplary embodiment, the target task update unit 803 is further configured to perform: detecting whether the page task state is completed; and if the page task state is finished, transmitting the page task state to the task system through a preset interface module, and responding to an instruction sent by the task system to update the target task.

In an exemplary embodiment, the target task update unit 803 is further configured to perform: and switching the target task, and returning to execute the step of generating a corresponding task module according to the target task parameter corresponding to the obtained target task identifier.

In an exemplary embodiment, the task module generating unit 801 is further configured to perform: acquiring a target task parameter corresponding to a target task identifier through a preset interface module; the target task parameter is at least one of a task parameter stored according to a preset network address or a self-defined generated task parameter.

In an exemplary embodiment, the task module generating unit 801 is further configured to perform: acquiring rendering information; the rendering information is obtained and comprises display configuration information of a page task state on a page; creating a pendant corresponding to the target task according to the rendering information; the pendant is a rendering format established according to the rendering information, and the rendering format comprises internal elements and a display format; creating a root node, and mounting a pendant to the root node; and setting target task parameters corresponding to the target task identification according to the pendant to obtain a corresponding task module.

In an exemplary embodiment, the task module generating unit 801 is further configured to perform: and setting the pendant to a preset position, wherein the preset position can be configured.

In an exemplary embodiment, the target task update unit 803 is further configured to perform: and packaging the page task access method into a preset format to obtain a corresponding page task access object.

In an exemplary embodiment, the target task update unit 803 is further configured to perform: the access method of the encapsulated page task is in a JavaScript SDK format, and a corresponding page task access object is obtained.

FIG. 9 is a block diagram illustrating a page task access system in accordance with an exemplary embodiment. Referring to fig. 9, the apparatus includes a target task parameter acquiring unit 901, a pendant generating unit 902, a task module generating unit 903, a page task state generating unit 904, and a target task updating unit 905:

a target task parameter obtaining unit 901, configured to execute obtaining a target task parameter corresponding to a target task identifier through a preset interface module; wherein, the target task identification corresponds to a target task;

the pendant generating unit 902 is configured to execute obtaining rendering information and create a pendant corresponding to the target task according to the rendering information;

the task module generation unit 903 is configured to execute setting of target task parameters according to the pendant to obtain a corresponding task module;

a page task state generating unit 904 configured to execute the task module, acquire the interaction information of the target service page, and generate a page task state corresponding to the target task; the target business page is a related page of a target task, and the page task state comprises a task completion state and a task progress corresponding to the interaction information;

and the target task updating unit 905 is configured to execute the transmission of the page task state to the task system and update the target task in response to an instruction issued by the task system.

With regard to the apparatus in the above embodiments, the specific manner in which the respective modules perform operations has been described in detail in the embodiments related to the method or system, and will not be elaborated upon here.

FIG. 10 is a block diagram illustrating an electronic device 1000 for page task access in accordance with an exemplary embodiment. For example, the device 1000 may be a mobile phone, a computer, a digital broadcast terminal, a messaging device, a gaming console, a tablet device, a medical device, an exercise device, a personal digital assistant, and so forth.

Referring to fig. 10, device 1000 may include one or more of the following components: processing component 1002, memory 1004, power component 1006, multimedia component 1008, audio component 1010, interface to input/output (I/O) 1012, sensor component 1014, and communications component 1016.

The processing component 1002 generally controls the overall operation of the device 1000, such as operations associated with display, telephone calls, data communications, camera operations, and recording operations. The processing components 1002 may include one or more processors 1020 to execute instructions to perform all or a portion of the steps of the methods described above. Further, processing component 1002 may include one or more modules that facilitate interaction between processing component 1002 and other components. For example, the processing component 1002 may include a multimedia module to facilitate interaction between the multimedia component 1008 and the processing component 1002.

The memory 1004 is configured to store various types of data to support operation at the device 1000. Examples of such data include instructions for any application or method operating on device 1000, contact data, phonebook data, messages, pictures, videos, and so forth. The memory 1004 may be implemented by any type or combination of volatile or non-volatile storage devices, such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disks.

The power supply component 1006 provides power to the various components of the device 1000. The power components 1006 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power for the device 1000.

The multimedia component 1008 includes a screen that provides an output interface between the device 1000 and a user. In some embodiments, the screen may include a Liquid Crystal Display (LCD) and a Touch Panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive an input signal from a user. The touch panel includes one or more touch sensors to sense touch, slide, and gestures on the touch panel. The touch sensor may not only sense the boundary of a touch or slide action, but also detect the duration and pressure associated with the touch or slide operation. In some embodiments, the multimedia component 1008 includes a front facing camera and/or a rear facing camera. The front camera and/or the rear camera may receive external multimedia data when the device 1000 is in an operating mode, such as a shooting mode or a video mode. Each front camera and rear camera may be a fixed optical lens system or have a focal length and optical zoom capability.

The audio component 1010 is configured to output and/or input audio signals. For example, the audio component 1010 may include a Microphone (MIC) configured to receive external audio signals when the device 1000 is in an operational mode, such as a call mode, a recording mode, and a voice recognition mode. The received audio signal may further be stored in the memory 1004 or transmitted via the communication component 1016. In some embodiments, audio component 1010 also includes a speaker for outputting audio signals.

I/O interface 1012 provides an interface between processing component 1002 and peripheral interface modules, which may be keyboards, click wheels, buttons, etc. These buttons may include, but are not limited to: a home button, a volume button, a start button, and a lock button.

The sensor assembly 1014 includes one or more sensors for providing status assessment of various aspects of the device 1000. For example, sensor assembly 1014 may detect the open/closed status of device 1000, the relative positioning of components, such as a display and keypad of device 1000, the change in position of device 1000 or a component of device 1000, the presence or absence of user contact with device 1000, the orientation or acceleration/deceleration of device 1000, and the change in temperature of device 1000. The sensor assembly 1014 may include a proximity sensor configured to detect the presence of a nearby object without any physical contact. The sensor assembly 1014 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, the sensor assembly 1014 may also include an acceleration sensor, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.

Communications component 1016 is configured to facilitate communications between device 1000 and other devices in a wired or wireless manner. The device 1000 may access a wireless network based on a communication standard, such as WiFi, an operator network (such as 2G, 3G, 4G, or 5G), or a combination thereof. In an exemplary embodiment, the communication component 1016 receives a broadcast signal or broadcast related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communications component 1016 further includes a Near Field Communication (NFC) module to facilitate short-range communications.

In an exemplary embodiment, the device 1000 may be implemented by one or more Application Specific Integrated Circuits (ASICs), Digital Signal Processors (DSPs), Digital Signal Processing Devices (DSPDs), Programmable Logic Devices (PLDs), Field Programmable Gate Arrays (FPGAs), controllers, micro-controllers, microprocessors or other electronic components for performing the above-described methods.

In an exemplary embodiment, a non-transitory computer readable storage medium comprising instructions, such as the memory 1004 comprising instructions, executable by the processor 1020 of the device 1000 to perform the above-described method is also provided. For example, the non-transitory computer readable storage medium may be a ROM, a Random Access Memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, and the like.

Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This application is intended to cover any variations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.

It will be understood that the present disclosure is not limited to the precise arrangements described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.

Claims

1. A page task access method is characterized by comprising the following steps:

2. The page task access method according to claim 1, wherein the acquiring, by the task module, the interaction information of the target service page and generating the page task state corresponding to the target task comprises:

acquiring the target service page;

3. The page task access method according to claim 1, wherein the acquiring, by the task module, the interaction information of the target service page and generating the page task state corresponding to the target task comprises:

4. The page task access method according to claim 1, wherein before generating the corresponding task module according to the target task parameter corresponding to the obtained target task identifier, the method comprises:

5. The page task access method according to claim 1, wherein the generating a corresponding task module according to the target task parameter corresponding to the obtained target task identifier comprises:

creating a root node, and mounting the pendant to the root node;

6. A page task access method is characterized by comprising the following steps:

7. A page task access apparatus, comprising:

8. A page task access system, comprising:

9. An electronic device, comprising:

a processor;

a memory for storing the processor-executable instructions;

wherein the processor is configured to execute the instructions to implement the page task access method of any one of claims 1 to 5 or claim 6.

10. A storage medium, wherein instructions in the storage medium, when executed by a processor of an electronic device, enable the electronic device to perform a page task access method as claimed in any one of claims 1 to 5 or claim 6.