Nothing Special   »   [go: up one dir, main page]

CN105704178B - Task platform access method and device - Google Patents

Task platform access method and device Download PDF

Info

Publication number
CN105704178B
CN105704178B CN201410693085.6A CN201410693085A CN105704178B CN 105704178 B CN105704178 B CN 105704178B CN 201410693085 A CN201410693085 A CN 201410693085A CN 105704178 B CN105704178 B CN 105704178B
Authority
CN
China
Prior art keywords
task
party application
platform
interface
request
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN201410693085.6A
Other languages
Chinese (zh)
Other versions
CN105704178A (en
Inventor
张延巍
吴蒿
周超凡
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Tencent Technology Shenzhen Co Ltd
Original Assignee
Tencent Technology Shenzhen Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Tencent Technology Shenzhen Co Ltd filed Critical Tencent Technology Shenzhen Co Ltd
Priority to CN201410693085.6A priority Critical patent/CN105704178B/en
Publication of CN105704178A publication Critical patent/CN105704178A/en
Application granted granted Critical
Publication of CN105704178B publication Critical patent/CN105704178B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Landscapes

  • Information Transfer Between Computers (AREA)

Abstract

the invention discloses an access method of a task platform, which comprises the following steps: receiving a login request sent by a third-party application accessor; after the login request is verified, allowing the third-party application accessor to log in; receiving a task creation request of a third-party application accessor, wherein the task creation request comprises an interface for the platform server to access; and generating a task of the third-party application according to the task creation request so as to be displayed on the task platform. The invention also discloses an access device of the task platform. The invention provides a task platform for third-party application access, when the third-party application is accessed, the task of the third-party application can be displayed on the task platform only by setting corresponding task information and an interface, and the platform server can also carry out data communication with the third-party application server through the interface.

Description

task platform access method and device
Technical Field
The invention relates to the technical field of internet, in particular to an access method and device of a task platform.
background
with the rapid development of networks, network platforms have also been rapidly developed. The network platform is used for displaying by a third-party application developer, and a user can access various applications through the network platform.
However, in the existing network platform, when a user interacts with the network platform, the network platform can only obtain the standardized data of the user on the network platform, and cannot obtain the data of the user accessing the third-party application through the network platform. Moreover, the user accesses the data of the third-party application on the network platform, and the third-party application cannot know the data due to confidentiality of user information. The third-party application can only acquire the data condition of the user in the third-party application. Therefore, the existing network platform has limitations in data interaction.
disclosure of Invention
The embodiment of the invention mainly aims to solve the technical problem that the existing network platform for displaying the third-party application has limitation in data interaction.
In order to achieve the above object, an embodiment of the present invention provides an access method for a task platform, which is applied to a platform server, where the platform server provides a task platform to display a task of a third-party application, and the access method for the task platform includes the following steps:
Receiving a login request sent by a third-party application accessor;
after the login request is verified, allowing the third-party application accessor to log in;
receiving a task creation request of a third-party application accessor, wherein the task creation request comprises an interface for the platform server to access;
And generating a task of a third-party application according to the task creation request so as to be displayed on the task platform.
in addition, to achieve the above object, an embodiment of the present invention further provides an access device for a task platform, including:
the request receiving module is used for receiving a login request sent by a third-party application accessor; the platform server is also used for receiving a task creating request of a third-party application accessor, wherein the task creating request comprises an interface for the platform server to access;
the login authentication module is used for allowing the third-party application accessor to log in after the login request is authenticated;
And the task generating module is used for generating a task of a third-party application according to the task creating request so as to display the task on the task platform.
The embodiment of the invention provides a task platform for the access of the third-party application through the platform server, and when the third-party application is accessed, the task of the third-party application can be displayed on the task platform only by setting corresponding task information and an interface, and the platform server can also carry out data communication with the third-party application server through the interface, thereby solving the problem of interaction limitation between the platform server and the third-party application server.
drawings
FIG. 1 is a schematic diagram of interaction among a PC terminal, a third-party application server and a platform server in a task centralized interaction system according to the present invention;
FIG. 2 is a diagram of a hardware architecture of the platform server of FIG. 1;
FIG. 3 is a functional block diagram of a first embodiment of an access device of a task platform according to the present invention;
FIG. 4 is a schematic diagram of detailed functional modules of a task generation module in an access device of a task platform according to the present invention;
FIG. 5 is an exemplary diagram of an interface of a task corresponding to a third-party application in an access device of a task platform according to the present invention;
FIG. 6 is an exemplary diagram of an interface for setting task information during task creation in an access device of a task platform according to the present invention;
FIG. 7 is a schematic diagram of a detailed functional module of an interface test module in the access device of the task platform according to the present invention;
FIG. 8 is a functional block diagram of a third embodiment of an access device of a task platform according to the present invention;
FIG. 9 is a functional block diagram of a third embodiment of an access device of a task platform according to the present invention;
FIG. 10 is a flowchart illustrating a first embodiment of an access method of a task platform according to the present invention;
FIG. 11 is a detailed flowchart of a task of generating a third-party application in the access method of the task platform according to the present invention;
FIG. 12 is a schematic diagram illustrating a detailed flow of joint debugging test performed on an interface in the access method of the task platform according to the present invention;
FIG. 13 is a flowchart illustrating a second embodiment of an access method of a task platform according to the present invention;
Fig. 14 is a flowchart illustrating a task platform access method according to a third embodiment of the present invention.
the implementation, functional features and advantages of the objects of the present invention will be further explained with reference to the accompanying drawings.
Detailed Description
the technical scheme of the invention is further explained by combining the drawings and the specific embodiments in the specification. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
The invention provides a task centralized interaction system, which comprises: terminal 100, platform server 200, third party application server 300. The platform server 200 is used for providing a task platform for a developer of a third-party application to provide a task corresponding to the third-party application. A developer of the third-party application may create a task corresponding to the third-party application in the platform server 200 and set a subtask corresponding to the task. If the task only comprises one subtask, the data packet corresponding to the task can be obtained after the subtask is executed. If the task comprises a plurality of subtasks, each subtask is completed, and then a data packet corresponding to the subtask can be obtained. It should be noted that, if the task corresponding to the third-party application is a plurality of subtasks, the task described in the following embodiment refers to a subtask of the task. The platform server 200 generates a task corresponding to the third-party application according to the creation requirement, and displays the generated task on a task display interface of the platform server 200. The user using the terminal 100 requests to log in the task platform of the platform server 200 through the task display interface, obtains a task corresponding to the third-party application, and executes the task in the third-party application server 300, so as to obtain a corresponding data packet after the task is executed. The third party application server 300 can also be accessed by the terminal 100 to execute the task corresponding to the third party application.
therefore, if a developer of a third-party application needs to expose a task of its third-party application on the task platform, the platform server 200 must be accessed first to obtain permission for task exposure. In view of this, the present invention provides a platform server 200 for accessing the third-party application, and displaying the task of the third-party application after the access is successful. As shown in fig. 2, the platform server 200 may be an independent server or a server group consisting of a plurality of servers. Which may include a processor 201, memory 202, a communication module 203, and a communication bus 204. The communication bus 204 is used for communication between the respective constituent elements in the platform server 200. The communication module 203 is used for enabling the platform server 200 to communicate with external devices such as PC terminals and other servers, and the communication module 203 may include an RS232 module, a radio frequency module, a WIFI module, and the like. Memory 202 may include one or more computer-readable storage media, and includes not only internal memory, but also external memory. The memory 202 has stored therein an operating system, platform access means, and the like. The processor 201 calls the platform access device and other components in the memory 202 to realize the functions of accessing the third-party application, displaying the task of the third-party application and the like.
as shown in fig. 3, the structure of the first embodiment of the access device of the task platform of the present invention is shown. The access device of the task platform of the embodiment can comprise:
a request receiving module 310, configured to receive a login request sent by a third-party application accessor; the platform server is also used for receiving a task creating request of a third-party application accessor, wherein the task creating request comprises an interface for the platform server to access;
the login verification module 320 is configured to allow the third-party application accessor to log in after the login request is verified;
And the task generating module 330 is configured to generate a task of a third-party application according to the task creating request, so as to be displayed on the task platform.
the third party application accessor accesses the task platform provided by the platform server 200 by using the terminal 100, if the third party application accessor accesses the task platform for the first time, registration is required to be performed first, and login is performed after the registration is successful. If the third party application access person has a login account, directly inputting the account and the password for login. The terminal 100 generates a login request according to an account and a password input by a third-party application accessor on a user interaction interface of the task platform, and sends the login request to the platform server 200. The request receiving module 310 of the platform server 200 receives the login request through the communication module 203, and then the login authentication module 320 authenticates the account and the password, and allows the third-party application accessor to log in after the authentication is successful.
after the third-party application accessor logs in the task platform, the task can be created on the task platform, for example, necessary information for creating the task such as the third-party application to be accessed and the task information of the third-party application is set. The task generating module 330 generates a task of the third-party application according to the information set by the third-party application accessor. The generated task of the third-party application is displayed on the task platform.
After the task displayed by the platform server 200 is received by the terminal user, the platform server 200 jumps to the third-party application server 300 to execute the task, and the completion condition of the task by the terminal 100 is recorded in the third-party application server 300, so that after receiving the data packet acquisition request of the terminal 100, the platform server 200 needs to perform data interaction with the third-party application server 300, and when the third-party application accessor accesses the third-party application, the platform server 200 needs to provide an interface for accessing the third-party application server 300 corresponding to the third-party application. The method specifically comprises the following steps: when the accessor of the third party application creates the task on the platform server 200, the address information of the interface is set, and meanwhile, the data interaction rule is also set in the third party application server 300.
the embodiment of the invention provides a task platform through the platform server 200 for the access of the third-party application, and when the third-party application is accessed, the task of the third-party application can be displayed on the task platform only by setting corresponding task information and an interface, and the platform server 200 can also perform data communication with the third-party application server 300 through the interface, track the application condition of the user in the third-party application server 300 in time, and solve the problem of interaction limitation between the platform server 200 and the third-party application server 300.
further, as shown in fig. 4, the task generating module 330 includes:
An interface providing unit 331, configured to provide a task setting interface according to the task creation request;
An input unit 332, configured to receive task condition information input by the third-party application accessor on the task setting interface, where the task condition information includes third-party application information, task information of the third-party application, and interface information of an application server corresponding to the third-party application;
the task identifier allocating unit 333 is configured to generate a task identifier corresponding to the task information of the third-party application according to a preset configuration rule or randomly;
and a task generating unit 334, configured to generate a task of the third-party application according to the task condition information and the task identifier.
And after the third-party application accessor logs in the task platform, the task interface corresponding to the third-party application accessor is accessed. And in the task interface, the third party application accessed by the third party application accessor on the task platform and the display condition of the task thereof are displayed. As shown in fig. 5, in the task interface corresponding to the accessor a, the checking and management of the task, the setting of the scheduling lead amount of the task, and the checking of the data report of the task operation can be realized. In the task viewing interface, all third-party applications accessed by the accessor a and information of tasks corresponding to the accessed third-party applications, such as app names, task identifications, task names, mart types, creation time, task states and the like, can be obtained. The mart type is the type of the user exposed by the task of the third-party application, such as a PC terminal user and a mobile terminal user. In addition, the task viewing interface also includes a "create task" control S1 and an "operate" control S2. The control S1 can be used for the accessor to create a new task; the control S2 allows the accessor to manage tasks of the accessed third party application, such as launch, delete, logoff, edit, pause, and so on.
When the accessor triggers control S1, a task creation request will be triggered. The interface providing unit 331 provides a task setting interface for the accessor to set information required for task creation according to the task creation request. As shown in fig. 6, in the task setting interface, the accessor is prompted to set corresponding information, such as the setting of each subtask of the task, interface information, and the like. It should be noted that each task may correspond to a plurality of subtasks, and the content of the subtasks may be set according to actual needs. For example, the task may include at least one first subtask preset by the task platform and at least one second subtask that is editable. Taking the game network platform as an example, when the third-party application is zhu xian application, the task is divided into four subtasks: the first subtask is to enter or install the zhu xian application, the second subtask is to have a role level up to 11 (which can be set by the user), the third subtask is to have a role level up to 40 (which can be set by the user), and the fourth subtask is to log in the application for 5 consecutive days. In addition, in this embodiment, the third-party application accessor further provides a task interface to the task platform according to an interface protocol agreed with the task platform, so that the task platform can call back the interface to perform data communication according to the agreed protocol.
When the task setting interface detects the information input by the user in the interface and detects the trigger of the confirmation event, the input unit 332 acquires the information input in the interface. Then, the task identifier allocating unit 333 generates a task identifier corresponding to the task according to a preset configuration rule or randomly. In this embodiment, each task corresponds to a task identifier, and after the task is created, the task and the corresponding task identifier are stored in a preset table; the task platform can acquire all configuration contents of one task through the unique task identifier. The task identifier can be configured by the task platform according to a preset configuration rule, and can also be randomly allocated by the task platform. After the game developer fills corresponding information in a task setting interface of the task platform, the task platform generates a task identifier corresponding to a task of a third-party application according to the third-party application and the task information. Finally, the task generating unit 334 generates the task of the third-party application according to the third-party application information, the task information of the third-party application, the task identifier, and the interface information of the application server.
Further, as shown in fig. 7, the access device of the task platform further includes an interface testing module 340, where the interface testing module 340 includes:
An interface obtaining unit 341, configured to obtain an interface for the platform server to access, where the interface is set in the task creation request;
a test request generating unit 342, configured to generate a test request according to a preset interface protocol;
A request sending unit 343, configured to send the test request to the third-party application server through the interface;
a test determining unit 344, configured to determine that the joint debugging test is successful when a response to the test request returned by the third-party application server meets a response rule in the interface protocol, and allow the task of the third-party application to be displayed on the task platform; and when the response returned by the third-party application server is not received or the response returned by the third-party application server to the test request does not conform to the response rule in the interface protocol, judging that the joint debugging test fails, and refusing the task of the third-party application to be displayed on the task platform.
In this embodiment, the preset interface protocol is a communication protocol agreed in advance between the platform server 200 and the third-party application server 300, and the interface protocol specifies parameters to be transmitted when the platform server 200 communicates with the third-party application server 300, such as a user identifier, a task identifier, and a command word cmd. The parameter cmd sets a corresponding command word by the platform server 200 according to a preset configuration rule to control the third party application server 300 to perform a corresponding operation. For example: check _ served instructs the third-party application server 300 to query whether the corresponding subtask of the task is completed, and if so, directly sends the data packet and returns whether the sending is successful; and the aware instructs the third-party application server 300 to directly send the data packet and returns whether the sending is successful or not. In addition, the interface protocol will also specify the protocol return packet returned by the third party application server 300. For example, in this embodiment, the protocol return packet of the interface protocol specification may include the following parameters: ret-return code, of the "integer" type; msg-error information, encoded in utf8, or other parameters that need to be included. Wherein the return code may include a standard return code and a custom return code. The value range of the standard return code can be 0-200, and is set by the platform server 200. The specific settings may be as follows: 0-step completed or reward issued successfully; 1-the user cannot be found; 2-the user has not completed the subtask; 3-the reward for the subtask has been released; 100-token has expired; 101-token is absent; 102-reward issuance failure; 103-request parameter error. The value range of the self-defined return code can be 200-10000, and the self-defined return code can be flexibly set by the third-party application server 300 according to specific application conditions.
after the task generating module 330 generates the task of the third-party application according to the task creating request, the interface acquiring unit 341 acquires the interface which is set by the third-party application accessor when initiating the task creating request and is accessible to the platform server. The test request generating unit 342 generates a test request according to a preset interface protocol. The method specifically comprises the following steps: and acquiring parameters, such as user identification, task identification, command words and the like, required by the test request in the test scene according to the interface protocol. Then, the request sending unit 343 accesses the above-mentioned interface through the communication module 203, and sends the parameters of the test request to the third party application server 300. After receiving the test request, the third-party application server 300 executes corresponding processing according to the parameters in the test request, and returns a processing result after the processing. After receiving the processing result returned by the third-party application server 300, the test determining unit 344 analyzes the processing result to determine whether the processing result meets the requirement defined by the interface protocol packet specified by the interface protocol. If yes, judging that the joint debugging test is successful; if not, the joint debugging test is judged to fail. Of course, when the test determining unit 345 does not receive the processing result returned by the third-party application server 300, it determines that the joint debugging test fails.
in another embodiment, the task platform may further include an interface joint debugging test interface, when the task platform generates the preset task, the task platform automatically jumps to the interface joint debugging test interface, and the access person clicks a preset test button on the interface joint debugging test interface to enter the joint debugging test of the interface. When the preset test button is pressed, an interface test request is generated, and joint debugging test is carried out according to the interface test request.
Further, as shown in fig. 8, the access device of the task platform may further include:
and the task auditing module 350 is configured to audit the generated task of the third-party application, so that the task of the third-party application is displayed on the task platform after the audit is passed.
After the joint debugging test is successful, the platform server 200 sends the generated task to the task auditing module 350, so that the task auditing module 350 audits the task generated by the third-party application, and the task of the third-party application is allowed to be displayed on the task platform after the audit is passed. The auditing process specifically comprises the following steps: firstly, a corresponding task auditing rule can be set according to a specific scene, and after a task of a third-party application is generated, the generated task is audited according to the task auditing rule setting.
Further, as shown in fig. 9, the access device of the task platform may further include:
And the task display module 360 is configured to expose the task applied by the third party on the task platform according to a preset ordering rule.
In this embodiment, when the platform server 200 performs an audit on the generated task of the third-party application, and after the audit is passed, the task is exposed according to a preset ordering rule through a preset advertisement slot in various social networks. Specifically, the exposure of the task needs advertisement broad-coupling, for example, a game developer needs to upload advertisements in a task platform, and after the uploaded advertisements are approved, the task and the advertisements can be exposed according to a uniform ordering rule of an advertisement system. The preset ordering rules may include expected popularity of tasks according to the third party application, or exposure requirements set by the third party application accessor, etc.
Correspondingly, based on the platform server, the invention provides an access method of a task platform. Fig. 10 shows a first embodiment of an access method of a task platform according to the present invention. The access method of the task platform of the embodiment can comprise the following steps:
Step S110, receiving a login request sent by a third-party application accessor;
if the third-party application accessor accesses the task platform for the first time, registration is needed first, and login is carried out after the registration is successful. If the third party application access person has a login account, directly inputting the account and the password for login. The terminal 100 generates a login request according to an account and a password input by a third-party application accessor on a user interaction interface of the task platform, and sends the login request to the platform server 200.
step S120, after the login request is verified, allowing the third-party application accessor to log in;
step S130, receiving a task creating request of a third-party application accessor, wherein the task creating request comprises an interface for the platform server to access;
After the third-party application accessor logs in the task platform, the task can be created on the task platform, for example, necessary information for creating the task such as the third-party application to be accessed and the task information of the third-party application is set.
And step S140, generating a task of the third-party application according to the task creation request so as to be displayed on the task platform.
after the task displayed by the platform server 200 is received by the terminal user, the platform server 200 jumps to the third-party application server 300 to execute the task, and the completion condition of the task by the terminal 100 is recorded in the third-party application server 300, so that the platform server 200 needs to perform data interaction with the third-party application server after receiving the data packet acquisition request of the terminal, and the third-party application accessor needs to provide an interface for the platform server 200 to access the third-party application server 300 corresponding to the third-party application when accessing the third-party application. The method specifically comprises the following steps: when the accessor of the third party application creates the task on the platform server 200, the address information of the interface is set, and meanwhile, the data interaction rule is also set in the third party application server 300.
The embodiment of the invention provides a task platform through the platform server 200 for the access of the third-party application, and when the third-party application is accessed, the task of the third-party application can be displayed on the task platform only by setting corresponding task information and an interface, and the platform server 200 can also perform data communication with the third-party application server 300 through the interface, track the application condition of the user in the third-party application server 300 in time, and solve the problem of interaction limitation between the platform server and the third-party application server 300.
Further, as shown in fig. 11, the step S140 may include:
Step S141, providing a task setting interface according to the task creating request;
and after the third-party application accessor logs in the task platform, the task interface corresponding to the third-party application accessor is accessed. And in the task interface, the third party application accessed by the third party application accessor on the task platform and the display condition of the task thereof are displayed. When the third-party application accessor triggers a task creation request in the task interface, the platform server 200 provides a task setting interface according to the task creation request, so that the accessor sets information required by task creation.
Step S142, receiving task condition information input by the third party application accessor on the task setting interface, wherein the task condition information comprises third party application information, task information of the third party application and interface information of an application server corresponding to the third party application;
and when the task setting interface detects the information input by the access person in the interface and detects the trigger of the confirmation event, acquiring the information input in the interface.
step S143, generating a task identifier corresponding to the task information of the third party application according to a preset configuration rule or randomly;
the platform server 200 generates a task identifier corresponding to the task according to a preset configuration rule or randomly. In this embodiment, each task corresponds to a task identifier, and after the task is created, the task and the corresponding task identifier are stored in a preset table; the task platform can acquire all configuration contents of one task through the unique task identifier.
and step S144, generating a task of the third-party application according to the task condition information and the task identifier.
and after the task identifier is generated, generating a platform task according to the task identifier, the third-party application server interface, the third-party application information and the task information corresponding to the third-party application. When the user finishes any subtask of the platform task, the task platform can pick up the task reward corresponding to the subtask.
further, as shown in fig. 12, the step S140 may include:
And step S150, performing joint debugging test on the interface set in the task creation request, so as to allow the task of the third-party application to be displayed on the task platform after the test is successful.
wherein, the step S150 may specifically include:
Step S151, acquiring an interface which is set in the task creation request and is used for the platform server to access;
step S152, generating a test request according to a preset interface protocol;
step S153, sending the test request to the application server through the interface;
Step S154, when the response to the test request returned by the application server accords with the response rule in the interface protocol, the joint debugging test is judged to be successful;
step S155, when the response returned by the application server is not received, or when the response returned by the application server to the test request does not conform to the response rule in the interface protocol, it is determined that the joint debugging test fails.
in this embodiment, the preset interface protocol is a communication protocol agreed in advance between the platform server and the third-party application server, and the interface protocol specifies parameters to be transmitted when the platform server and the third-party application server communicate with each other, such as a user identifier, a task identifier, and a command word cmd. The parameter cmd sets a corresponding command word by the platform server 200 according to a preset configuration rule to control the third party application server 300 to perform a corresponding operation. For example: check _ served instructs the third-party application server 300 to query whether the corresponding subtask of the task is completed, and if so, directly sends the data packet and returns whether the sending is successful; and the aware instructs the third-party application server 300 to directly send the data packet and returns whether the sending is successful or not. In addition, the interface protocol also specifies a protocol return packet returned by the third-party application server. For example, in this embodiment, the protocol return packet of the interface protocol specification may include the following parameters: ret-return code, of the "integer" type; msg-error information, encoded in utf8, or other parameters that need to be included. Wherein the return code may include a standard return code and a custom return code. The value range of the standard return code can be 0-200, and is set by the platform server 200. The specific settings may be as follows: 0-step completed or reward issued successfully; 1-the user cannot be found; 2-the user has not completed the subtask; 3-the reward for the subtask has been released; 100-token has expired; 101-token is absent; 102-reward issuance failure; 103-request parameter error. The value range of the self-defined return code can be 200-10000, and the self-defined return code can be flexibly set by a third-party application server according to specific application conditions.
And generating a test request according to a preset interface protocol after generating a task of the third-party application according to the task creation request. The method specifically comprises the following steps: and acquiring parameters, such as user identification, task identification, command words and the like, required by the test request in the test scene according to the interface protocol. The platform server 200 then accesses the above interface and sends the parameters of the test request to the third party application server. And after receiving the test request, the third-party application server executes corresponding processing according to the parameters in the test request, and returns a processing result after the processing. After receiving the processing result returned by the third-party application server 300, the platform server 200 analyzes the processing result to determine whether the processing result meets the requirement defined by the interface protocol packet specified by the interface protocol. If yes, judging that the joint debugging test is successful; if not, the joint debugging test is judged to fail. Certainly, when the platform server 200 does not receive the processing result returned by the third-party application server, it is determined that the joint debugging test fails.
In another embodiment, the task platform may further include an interface joint debugging test interface, when the task platform generates the preset task, the task platform automatically jumps to the interface joint debugging test interface, and the access person clicks a preset test button on the interface joint debugging test interface to enter the joint debugging test of the interface. When the preset test button is pressed, an interface test request is generated, and joint debugging test is carried out according to the interface test request.
Further, as shown in fig. 13, after the step S140, the method further includes:
and step S160, after the joint debugging test is successful, auditing the task of the third-party application so as to allow the task of the third-party application to be displayed on the task platform after the auditing is passed.
and after the joint debugging test is successful, the platform server audits the generated task, and after the audit is passed, the task of the third-party application is allowed to be displayed on the task platform. The auditing process specifically comprises the following steps: firstly, a corresponding task auditing rule can be set according to a specific scene, and after a task of a third-party application is generated, the generated task is audited according to the task auditing rule setting.
further, as shown in fig. 14, the access method of the task platform further includes:
Step S170, exposing the task applied by the third party on the task platform according to a preset ordering rule.
in this embodiment, when the platform server performs an audit on the generated task of the third-party application, and after the audit is passed, the platform server performs exposure processing on the task according to a preset ordering rule through preset advertisement slots in various social networks. Specifically, the exposure of the task needs advertisement broad-coupling, for example, a game developer needs to upload advertisements in a task platform, and after the uploaded advertisements are approved, the task and the advertisements can be exposed according to a uniform ordering rule of an advertisement system. The preset ordering rules may include expected popularity of tasks according to the third party application, or exposure requirements set by the third party application accessor, etc.
The above description is only for the preferred embodiment of the present invention and is not intended to limit the scope of the present invention, and all modifications of equivalent structures and equivalent processes that can be directly or indirectly applied to other related technical fields using the contents of the present specification and the accompanying drawings are included in the scope of the present invention.

Claims (8)

1. an access method of a task platform is applied to a platform server, the platform server provides the task platform to display a task of a third party application, and the access method of the task platform comprises the following steps:
receiving a login request sent by a third-party application accessor;
After the login request is verified, allowing the third-party application accessor to log in;
receiving a task creation request of a third-party application accessor, wherein the task creation request comprises an interface for the platform server to access;
Generating a task of a third-party application according to the task creation request so as to be displayed on the task platform, wherein the task is taken by a terminal user and then jumps to a third-party application server to be executed;
Wherein, the generating the task of the third-party application according to the task creation request comprises:
Generating a task setting interface according to the task creating request;
receiving task condition information input by the third-party application accessor on the task setting interface, wherein the task condition information comprises third-party application information, task information of the third-party application and interface information of an application server corresponding to the third-party application;
Generating a task identifier corresponding to the task information of the third-party application according to a preset configuration rule or randomly;
and generating the task of the third-party application according to the task condition information and the task identifier.
2. the access method of the task platform according to claim 1, wherein the generating of the task of the third-party application according to the task creation request further comprises:
Acquiring an interface which is set in a task creating request and is used for the platform server to access;
generating a test request according to a preset interface protocol;
Sending the test request to the application server through the interface;
When the response to the test request returned by the application server conforms to the response rule in the interface protocol, judging that the test is successful, and allowing the task of the third-party application to be displayed on the task platform;
and when the response returned by the application server is not received or the response returned by the application server to the test request does not conform to the response rule in the interface protocol, judging that the test fails, and rejecting the task of the third-party application to be displayed on the task platform.
3. The access method of the task platform according to claim 1 or 2, wherein after generating the task of the third-party application according to the task creation request, the method further comprises:
and auditing the task of the third-party application so as to display the task of the third-party application on the task platform after the auditing is passed.
4. The task platform access method according to claim 1 or 2, wherein the task platform access method further comprises:
and exposing the task applied by the third party on the task platform according to a preset sequencing rule.
5. an access device of a task platform, the access device of the task platform comprising:
The request receiving module is used for receiving a login request sent by a third-party application accessor; the platform server is also used for receiving a task creating request of a third-party application accessor, wherein the task creating request comprises an interface for the platform server to access;
The login authentication module is used for allowing the third-party application accessor to log in after the login request is authenticated;
The task generation module is used for generating a task of a third-party application according to the task creation request so as to display the task on the task platform, and after the task is received by a terminal user, the task is skipped to a third-party application server to be executed;
Wherein the task generation module comprises:
The interface providing unit is used for generating a task setting interface according to the task creating request;
the input unit is used for receiving task condition information input by the third-party application accessor on the task setting interface, wherein the task condition information comprises third-party application information, task information of the third-party application and interface information of an application server corresponding to the third-party application;
The task identifier distribution unit is used for randomly generating a task identifier corresponding to the task information of the third-party application according to a preset configuration rule;
And the task generating unit is used for generating the task of the third-party application according to the task condition information and the task identifier.
6. The task platform access device of claim 5, further comprising an interface test module, wherein the interface test module comprises:
the interface acquisition unit is used for acquiring an interface which is set in the task creation request and is used for the platform server to access;
The test request generating unit is used for generating a test request according to a preset interface protocol;
a request sending unit, configured to send the test request to the application server through the interface;
the test judging unit is used for judging that the test is successful and allowing the task of the third-party application to be displayed on the task platform when the response to the test request returned by the application server conforms to the response rule in the interface protocol; and when the response returned by the application server is not received or the response returned by the application server to the test request does not conform to the response rule in the interface protocol, judging that the test fails, and rejecting the task of the third-party application to be displayed on the task platform.
7. an access device for a task platform according to claim 5 or 6, wherein the access device for a task platform further comprises:
and the task auditing module is used for auditing the tasks of the third-party application so as to display the tasks of the third-party application on the task platform after the auditing is passed.
8. an access device for a task platform according to claim 5 or 6, wherein the access device for a task platform further comprises:
And the task display module is used for exposing the tasks applied by the third party on the task platform according to a preset sequencing rule.
CN201410693085.6A 2014-11-26 2014-11-26 Task platform access method and device Active CN105704178B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201410693085.6A CN105704178B (en) 2014-11-26 2014-11-26 Task platform access method and device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201410693085.6A CN105704178B (en) 2014-11-26 2014-11-26 Task platform access method and device

Publications (2)

Publication Number Publication Date
CN105704178A CN105704178A (en) 2016-06-22
CN105704178B true CN105704178B (en) 2019-12-10

Family

ID=56295039

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201410693085.6A Active CN105704178B (en) 2014-11-26 2014-11-26 Task platform access method and device

Country Status (1)

Country Link
CN (1) CN105704178B (en)

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108121606B (en) * 2016-11-26 2021-02-19 深圳壹账通智能科技有限公司 Method and device for generating coded data based on joint debugging interface
CN108345639B (en) * 2018-01-10 2021-05-18 武汉天喻教育科技有限公司 Task management system and task management method
CN108563567B (en) * 2018-04-09 2023-07-14 绍兴君鸿智能科技有限公司 Automated testing method, apparatus, device and computer readable storage medium
CN108804320A (en) * 2018-05-30 2018-11-13 平安普惠企业管理有限公司 Automated testing method, device, computer equipment and storage medium
CN109248438B (en) * 2018-09-21 2022-07-15 Oppo广东移动通信有限公司 Task project management method, device, storage medium and mobile terminal
CN109559213A (en) * 2018-12-20 2019-04-02 航天信息股份有限公司 The processing method and processing device of taxation informatization
CN110851261A (en) * 2019-11-13 2020-02-28 深圳前海微众银行股份有限公司 Task processing method, system, device, equipment and computer readable storage medium
CN114205366B (en) * 2021-12-01 2024-07-30 广州方硅信息技术有限公司 Cross-platform data synchronization method and device, equipment, medium and product thereof

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102739708A (en) * 2011-04-07 2012-10-17 腾讯科技(深圳)有限公司 System and method for accessing third party application based on cloud platform
CN102821084A (en) * 2011-11-23 2012-12-12 腾讯科技(深圳)有限公司 Method for identifying open platform, open platform and open system
CN102929947A (en) * 2012-09-27 2013-02-13 腾讯科技(深圳)有限公司 Data processing method and device
CN103428166A (en) * 2012-05-16 2013-12-04 腾讯科技(深圳)有限公司 Multi-SNS platform unified access method and system applied by third party
CN103888451A (en) * 2014-03-10 2014-06-25 百度在线网络技术(北京)有限公司 Method, device and system for certification authorization

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102739708A (en) * 2011-04-07 2012-10-17 腾讯科技(深圳)有限公司 System and method for accessing third party application based on cloud platform
CN102821084A (en) * 2011-11-23 2012-12-12 腾讯科技(深圳)有限公司 Method for identifying open platform, open platform and open system
CN103428166A (en) * 2012-05-16 2013-12-04 腾讯科技(深圳)有限公司 Multi-SNS platform unified access method and system applied by third party
CN102929947A (en) * 2012-09-27 2013-02-13 腾讯科技(深圳)有限公司 Data processing method and device
CN103888451A (en) * 2014-03-10 2014-06-25 百度在线网络技术(北京)有限公司 Method, device and system for certification authorization

Also Published As

Publication number Publication date
CN105704178A (en) 2016-06-22

Similar Documents

Publication Publication Date Title
CN105704178B (en) Task platform access method and device
US9979712B2 (en) Synchronizing authentication sessions between applications
CN105677452B (en) Task processing method and device for task platform
CN110290049B (en) Message pushing method, server and computer readable storage medium
US9641575B2 (en) Method for sharing multimedia content between two users
US20150261554A1 (en) System and methods for remote maintenance in an electronic network with multiple clients
CN108712413B (en) Identity verification method and equipment
US8683226B2 (en) Automatic provisioning in mobile to mobile platforms
CN105389263B (en) Application software authority monitoring method, system and equipment
CN108228444B (en) Test method and device
CN111355723B (en) Single sign-on method, device, equipment and readable storage medium
CN110069909B (en) Method and device for login of third-party system without secret
CN105991614A (en) Open authorization, resource access method and device, and a server
US20220377556A1 (en) Internet-of-things device registration method and apparatus, device, and storage medium
CN111064708B (en) Authorization authentication method and device and electronic equipment
CN111861804A (en) Community management method, system, user terminal and management terminal
CN110231965B (en) Cloud device, application processing method and electronic device
CN104917794A (en) Data sharing method, device and system
CN114757634A (en) Portable high-integration mobile office platform as a service (PaaS)
CN114553608A (en) Method and device for accessing cloud platform
CN103067260B (en) Realize method and the device of instant messaging
CN112559352A (en) Interface test method, device, equipment and storage medium
CN106330899A (en) Private cloud device account management method and system, electronic device and server
CN115733666A (en) Password management method and device, electronic equipment and readable storage medium
US10742802B2 (en) Methods and devices for verifying a communication number

Legal Events

Date Code Title Description
C06 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant