WO2018006453A1 - 一种移动终端的协助方法及移动终端 - Google Patents

一种移动终端的协助方法及移动终端 Download PDF

Info

Publication number
WO2018006453A1
WO2018006453A1 PCT/CN2016/092362 CN2016092362W WO2018006453A1 WO 2018006453 A1 WO2018006453 A1 WO 2018006453A1 CN 2016092362 W CN2016092362 W CN 2016092362W WO 2018006453 A1 WO2018006453 A1 WO 2018006453A1
Authority
WO
WIPO (PCT)
Prior art keywords
help
information
requesting
request
requesting end
Prior art date
Application number
PCT/CN2016/092362
Other languages
English (en)
French (fr)
Inventor
梁晓辉
Original Assignee
中兴通讯股份有限公司
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 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2018006453A1 publication Critical patent/WO2018006453A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/40—Network security protocols

Definitions

  • the present application relates to, but is not limited to, the field of communications technologies, and in particular, to a method for assisting a mobile terminal and a mobile terminal.
  • An object of the present invention is to provide a method for assisting a mobile terminal and a mobile terminal, which solves the problem that the remote assistance has a time limit on both parties and restricts operation of other applications on the mobile terminals of the two parties.
  • a method for assisting a mobile terminal includes:
  • the requesting side creates a request session and generates form information.
  • the requesting end sends the form information to the responding end, so that the responding end generates the help form by using the form information.
  • the requesting end receives the help information sent by the responding end, where the help information includes a parameter obtained by the responding end to parameterize the operation event.
  • the requesting end executes the parameter included in the help information.
  • a method for assisting a mobile terminal includes:
  • the response terminal receives the form information sent by the requesting end, wherein the form information is form information generated by the requesting end creation requesting session.
  • the response end generates the help form using the form information.
  • the response end receives an operation event input by the user in the help form, and parameterizes the operation event to obtain a parameter.
  • the responding end sends the help information including the parameter to the requesting end, so that the requesting end executes the parameter included in the help information in the request form.
  • a mobile terminal includes: a form information generating module, a form information sending module, a help information receiving module, and a help information executing module.
  • the form information generation module is set to create a request session in the request form to generate form information.
  • the form information sending module is configured to send the form information to the responding end, so that the responding end generates the help form by using the form information.
  • the help information receiving module is configured to receive the help information sent by the responding end, wherein the help information includes a parameter obtained by the response end parameterizing the operation event, where the action event is that the responding end is in the An operation event that receives user input in the intermediate form.
  • the help information execution module is configured to execute the parameter included in the help information by the requesting end.
  • a mobile terminal includes: a form information receiving module, a help form generating module, a parameterized processing module, and a help information sending module.
  • the form information receiving module is configured to receive the form information sent by the requesting end, wherein the form information is form information generated by the requesting end creation requesting session.
  • the help form generation module is set to generate a help form using the form information.
  • the parameterization processing module is configured to receive an operation event input by the user in the help form, and parameterize the operation event to obtain a parameter.
  • the help information sending module is configured to send, to the requesting end, help information including the parameter to the requesting end, so that the requesting end executes the parameter included in the help information in the request form number.
  • a computer storage medium having stored therein one or more programs executable by a computer, the one or more programs being executed by the computer to cause the computer to perform a mobile terminal as provided above The method of assistance.
  • the method provides a request session, so as to implement the asynchronous assistance of the requesting end and the responding end, in the asynchronous assisting process, both time And other application operations on both mobile terminals are not limited.
  • FIG. 1 is a schematic flowchart of a method for assisting a mobile terminal according to an embodiment of the present invention
  • FIG. 2 is a schematic flowchart of another method for assisting a mobile terminal according to an embodiment of the present invention
  • FIG. 3 is a schematic flowchart diagram of another method for assisting a mobile terminal according to an embodiment of the present disclosure
  • FIG. 4 is a schematic flowchart diagram of another method for assisting a mobile terminal according to an embodiment of the present disclosure
  • FIG. 5 is a schematic structural diagram of a device for assisting a mobile terminal according to an embodiment of the present disclosure
  • FIG. 6 is a schematic structural diagram of another apparatus for assisting a mobile terminal according to an embodiment of the present disclosure.
  • FIG. 7 is a schematic structural diagram of another apparatus for assisting a mobile terminal according to an embodiment of the present disclosure.
  • FIG. 8 is a schematic structural diagram of another apparatus for assisting a mobile terminal according to an embodiment of the present disclosure.
  • FIG. 9 is a schematic structural diagram of another apparatus for assisting a mobile terminal according to an embodiment of the present disclosure.
  • FIG. 10 is a schematic structural diagram of another apparatus for assisting a mobile terminal according to an embodiment of the present disclosure.
  • FIG. 11 is a schematic structural diagram of another apparatus for assisting a mobile terminal according to an embodiment of the present invention.
  • FIG. 1 is a schematic flowchart of a method for assisting a mobile terminal according to an embodiment of the present invention. As shown in FIG. 1, the method includes the following steps S101-S104:
  • the request end creates a request session, and generates form information.
  • the requesting end can create a request session requesting help in the current form in the power-on state to obtain assistance from others. If a request session is created on the current form, the current form becomes a request form. When the requesting side creates a request session on the request form, the requesting side generates the form information of the request form.
  • the process of creating a request session may be implemented by using an interface for creating a request session provided by the requesting end, and the interface may be displayed at the uppermost layer of the requesting end interface, so that the user can enable the interface at any time; and the priority of the interface may also be Set to the highest, not affected by other operations or other services on the request side.
  • the requesting end can freely select the request object, that is, freely select the responding end.
  • the process of selecting the responding end may be performed when the requesting end creates the requesting session, that is, when the requesting end creates the requesting session, the requesting end submits the telephone number of the responding end, triggers the connection server, and obtains information such as its own user ID and digital certificate, and Obtain information such as the user ID and digital certificate corresponding to the phone number.
  • the two ID information splicing strings are used as the ID of the requesting session created by the requesting end.
  • the above connection server may be a server built by each operator and stored with a user ID or a user's telephone number or digital certificate.
  • the server has the function of registering and transmitting the requesting key and useful information between the requesting end and the responding end according to a certain standard format, and the key useful information is not limited to including the user ID, the terminal identification number, and the digital certificate at the time of registration.
  • the process of generating the form information of the request form may be: when the request session is created, the request form is encapsulated to generate the form information.
  • the request form is encapsulated to generate the form information.
  • the currently operated application name, version information, and current application interface are packaged together.
  • the above form information may include, but is not limited to, an application interface, an application name, an application version, and the like.
  • the requesting end sends the form information to the responding end, so that the responding end generates the help form by using the form information.
  • the current request form may be set to an inoperable state to wait for the help information fed back by the responding end. It should be noted that although the current request form is in an inoperable state, the user performs other application operations on the request side without limitation.
  • the requester only needs to adjust the current request form to run in the background, and is not affected or restricted by the request session creation event.
  • the requesting end can call the display function module to pop up a prompt for the user, for example, a pop-up prompt "The creation request has been sent, and the user can perform other application operations on the current terminal, but the current application interface that issues the request needs to wait for the help reply before proceeding.”
  • the requesting end receives the help information sent by the responding end, where the help information includes a parameter obtained by the responding end to parameterize the operation event.
  • the help information sent by the requesting end from the responding end may be encapsulated help information, and the requesting end needs to parse the encapsulated help information.
  • the requesting end executes the parameter included in the help information.
  • the requesting end may execute the received help information on the request form.
  • the help process for the request form is complete.
  • the application operation of the request form will jump to the next form and accept the user's free operation. The user can operate freely or create a request session again in the current form.
  • the foregoing method can be applied to mobile terminals such as mobile phones, tablets, and notebook computers, that is, the devices can implement the foregoing methods.
  • the purpose of the requesting session is to achieve the purpose of asynchronous assistance of the requesting end and the responding end.
  • the time of the two parties and other application operations on the mobile terminals of both parties are not limited.
  • the requesting by the requesting end, the parameter included in the help information in the request form, including:
  • the requesting end switches the request form to the foreground display.
  • the requesting end reads the parameter included in the help information and assigns the parameter to the request form.
  • the requester Since the requester can switch the request form to the background for other application operations after the request session is created, the requester may not be able to receive the help information sent by the responder. Request form. When the current form of the requester is not the request form, the requester will request the form to switch from the background to the foreground display. After the request side switches the request form to the foreground, the requester reads the parameters contained in the help information and assigns the parameter to the request form. At this point, the help process for the request form is complete.
  • the requesting end by switching the request form in the background and the foreground, the requesting end can better ensure that the operation of the mobile terminal is not restricted during the asynchronous assistance process when the asynchronous assistance is performed.
  • the requesting end switches the request form to the foreground display, including:
  • the requesting end If the requesting end does not receive the delay processing instruction, the requesting end switches the request form to the foreground display.
  • the requesting end If the requesting end receives the delay processing instruction, the requesting end switches the request form to the foreground display after a preset delay processing time.
  • the requesting end can automatically switch the request form to the foreground display, or can notify the user, and the user decides whether to agree to switch the current application interface to the request form. For example, the requester pops up a prompt message: "The created request session has received help information, please select whether to apply the help information.”
  • the requesting end can provide the user with three selection interfaces:
  • the requesting end When the user selects "Yes", the requesting end immediately switches the request form to the foreground display.
  • the requesting end When the user selects “delay processing”, the requesting end starts the warning timing. When the timing time reaches the preset delay processing time, the requesting end may switch the request form to the foreground display, or may pop up a prompt message: “The help information has been Delay processing, whether to run the received help information immediately, otherwise the help information will be invalid.”. For the latter, the user can select "Yes”, the requester immediately switches the request form to the foreground display; the user can also select "No", the requester continues to display the current form, and ends the asynchronous assistance of the request form. .
  • the user is free to decide whether to agree to switch the current application interface.
  • Running the help information can increase the dominance of the requester in asynchronous assistance.
  • FIG. 2 is a schematic flowchart of a method for assisting a mobile terminal according to an embodiment of the present invention. As shown in FIG. 2, the method includes the following steps S201-S206:
  • the requesting end determines whether the number of requesting sessions that have been created and placed in the background of the requesting end is less than a preset threshold number of requesting sessions.
  • the requesting end may preset a threshold of the number of requesting sessions that can be placed in the background, and is used to control the number of requesting sessions that can be created by the requesting end within a certain period of time.
  • the requesting end receives the requesting session and needs to be created, it first detects whether the number of requesting sessions that the requesting end has created is less than a preset threshold number of requesting sessions.
  • the requesting end creates a requesting session in the request form.
  • the requester can create a request session in the current request form. If the requesting end detects that the number of requested sessions in the requester's background is greater than or equal to the preset number of requested sessions, the requesting end may refuse to create a new requesting session.
  • the requesting end encrypts the request form, and generates encrypted form information of the request form.
  • the requesting end may encrypt the request form to generate encrypted form information of the request form.
  • the requesting end sends the form information to the responding end, so that the responding end uses the form information to generate a help form that is the same as the request form.
  • the requesting end receives the help information sent by the responding end, where the help information includes a parameter obtained by parameterizing the operation event by the responding end, where the operating event is that the responding end is in the Receives user-entered operational events in the intermediate form.
  • the requesting end executes the parameter included in the help information in the request form.
  • FIG. 3 is a schematic flowchart of a method for assisting a mobile terminal according to an embodiment of the present invention. As shown in FIG. 3, the method includes the following steps S301-S304:
  • the response end receives the form information sent by the requesting end, where the form information is form information generated by the requesting end creation requesting session.
  • the response end when the response end receives the form information sent by the requesting end, the response end may obtain key useful information of the form information according to the connected server, and use the key useful information to parse the form information. If the form information is encrypted, the response terminal can also decrypt the form information by using the key useful information.
  • the response end generates the help form by using the form information.
  • the response end uses the parsing, it may also be the parsed and decrypted form information, and the same help form is generated on the responding end as the request form.
  • the response end receives an operation event input by the user in the help window, and performs parameterization processing on the operation event to obtain a parameter.
  • the responding end has a function of recording a user operation.
  • the responding end parameterizes the operation event input by the user, and obtains help information including the parameter.
  • the action event can contain the control information and input information that the user enters in the help form.
  • the responding end sends the help information including the parameter to the requesting end, and the requesting end executes the parameter included in the help information in the request form.
  • the responding end obtains the key useful information of the responding end and the requesting end according to the connected server.
  • the responding end sends the encapsulated request to the requesting end according to the requesting session identifier sent by the previous requesting end.
  • Help information After receiving the help information sent by the responding end, the requesting end needs to parse the help information and execute the parameters included in the help information.
  • the asynchronous operation of the requesting end and the responding end is implemented.
  • the time of the two parties and other application operations on the mobile terminals of both parties are not limited.
  • the responding end parses the form information sent by the requesting end to generate Into the same help form as the request form.
  • the responder places a new help form generated in the background of the responder.
  • the responding end when the response end parses the form information, the responding end may be processing other request sessions sent by the requesting end in the previous period. Therefore, it is necessary to determine whether the current responding end is entering the help information, that is, determining the response. Whether the number of help forms generated by the terminal is greater than 1. If the current response terminal is entering the help information, the help form generated by the new resolution is placed in the background of the responder. When the responding end runs multiple help forms in the background, the responding end invokes the help form running in the background one by one and displays it in the foreground according to the order in which the request session is received.
  • the responding end may send a notification to inform the user that the help form generated by the new parsing may be placed in the foreground display of the responding end and the help information is entered.
  • asynchronously processing a plurality of different request sessions by receiving a plurality of request sessions improves the user experience.
  • the responding end sends the help information including the parameter to the requesting end, including:
  • the response end encrypts the help information including the parameter to generate encrypted help information.
  • the responder sends the encrypted help information including the parameter to the requesting end.
  • the response end may encrypt the help information to improve security performance.
  • the requesting side needs to decrypt the help information and execute the parameters contained in the help information.
  • FIG. 4 is a schematic flowchart of a method for assisting a mobile terminal. As shown in FIG. 4, the method includes the following steps S401-S414:
  • the requesting end submits an instruction to create a request session in the request form, and detects the number of background requesting sessions.
  • the instruction for creating the request session is submitted through the interface of the requesting session provided by the requesting end.
  • the interface can be displayed on the top layer of the request side interface.
  • the priority of the interface can be set to the highest, and is not affected by other operations and other services on the request side.
  • the requesting end detects that the user initiates a create request session for the current application interface operation, the number of active request sessions recorded by the requester is read.
  • S402. Determine whether the number of background request sessions exceeds a preset threshold.
  • S403 is performed; if the number of background request sessions does not exceed the preset threshold, S404 is performed.
  • the requesting end refuses to create a requesting session.
  • the requesting end can also pop up a prompt box: "The number of currently requested sessions reaches the maximum, please complete another request session and then initiate a new request session.”
  • S404 The requesting end creates a request session, and encapsulates the form information of the current request form, and sends the form information to the response end.
  • the user may pop up a prompt, for example, "The created request has been sent, and the user may perform some other application operations on the current terminal, but issue The requested current application interface needs to wait for help to reply before proceeding.”
  • the requesting side can adjust the request form to run in the background, and the user can perform other application operations on the current requesting end without any influence and limitation of the request initiation event.
  • the response end receives and parses the form information sent by the requesting end to generate a help form.
  • the response end When the response end detects that the encapsulated form information is sent, it parses the form information sent by the requester to generate a help form.
  • the real-time detection process can be started to detect whether the submitted request form will change.
  • the requesting end reminds the user that the request form is changed, causing the issued request to be interrupted, and ending the current requesting session process.
  • the requesting end When the requesting end detects that the current request form has changed, the requesting end pops up a prompt message for notification. Some of the current operations performed by the user have caused the request form to change, causing the request to be interrupted.
  • the requesting end sends the status of the requesting interrupt to the responding end, and the responding end may terminate the input of the help information.
  • the response end enters the help information on the help form, and parameterizes the help information, and then sends the package to the requesting end.
  • the user enters the help information and the related control operations on the help form displayed in the foreground of the response end.
  • the response terminal parameterizes the operation sequence of the user on the help form, each control operation and attribute information, and saves Help information entered on the help form.
  • the response end detects that the help information is entered, the help information is encapsulated and sent to the requesting end.
  • the requesting end receives the help information sent by the responding end, and notifies the user whether the calling request form is placed in the foreground to run the help information.
  • the requesting party may pop up a prompt message to the user: "The created requesting session has received the help information, and the user is requested to select whether to preview and apply the help information.”
  • the requesting end provides three selection interfaces.
  • S413 is executed.
  • the requesting end switches the current service, and the calling request form is placed in the foreground to run the help information.
  • the requester automatically runs each parameter in the read help information on the request form.
  • S414 The requesting end continues the current service, and the current requesting session process enters a waiting state; when the waiting for the warning time arrives, the system gives a prompt to determine whether to invoke.
  • the requesting end starts the system warning timing process and keeps the display priority of the current operation application to the highest; when the waiting warning time arrives, the requesting party pops up a prompt message: "The help information has been delayed, and the received help information is immediately run. Otherwise the request information will be invalid.”
  • S413 is performed; when the user selects “No”, the request session is ended, and the current application interface is continuously displayed in the foreground of the requesting end.
  • FIG. 5 is a schematic structural diagram of a mobile terminal.
  • the mobile terminal 500 includes: a form information generating module 501, a form information sending module 502, and help information receiving. Module 503 and help information execution module 504.
  • the form information generating module 501 is configured to create a request session and generate form information.
  • the form information sending module 502 is configured to send the form information to the responding end, so that the responding end generates the help form by using the form information.
  • the help information receiving module 503 is configured to receive, by the requesting end, the help information sent by the responding end, where the help information includes a parameter obtained by parameterizing the operation event by the responding end, where the operating event is
  • the response end receives an operation event input by the user in the intermediate form.
  • the help information execution module 505 is configured to execute the parameters included in the help information.
  • the form information generating module 501 includes:
  • the first determining unit 5011 is configured to determine, by the requesting end, whether the number of requesting sessions that have been created and placed in the background of the requesting end is less than a preset threshold number of requesting sessions.
  • the creating unit 5012 is configured to create a request session in the request form if the number of request sessions that have been created and placed in the background of the requesting end is less than a preset number of requesting sessions.
  • the generating unit 5013 is configured to encrypt the request form to generate encrypted form information of the request form.
  • the help information execution module 505 includes: a second determining unit, a switching unit, and a reading unit.
  • the parameter that the help information execution module executes to execute the help information includes:
  • the second determining unit 5051 is configured to determine whether the current form of the requesting end is the request form.
  • the first switching unit 5052 is configured to switch the request form to the foreground display if the current form of the requesting end is not the request form;
  • the reading unit 5053 is configured to read the parameter included in the help information and assign the parameter to the request form.
  • the first switching unit 5052 includes: a determining subunit, a first switching subunit, and a second switching subunit.
  • the switching unit switching the request form to the foreground display includes:
  • the determining subunit 50521 is configured to determine whether the requesting end receives the delay processing instruction.
  • the first switching subunit 50522 is configured to switch the request form to the foreground display if the requesting end does not receive the delay processing instruction.
  • the second switching subunit 50523 is configured to, if the requesting end receives the delay processing instruction, switch the request form to the foreground display after a preset delay processing time.
  • the mobile terminal 500 can implement the method provided in the embodiment shown in FIG. 1 to FIG. 2, that is, the methods provided in the embodiments shown in FIG. 1 to FIG. 2 can be implemented by the mobile terminal 500, and can also be implemented. The same technical effect is achieved and will not be described here.
  • FIG. 9 is a schematic structural diagram of a mobile terminal.
  • the mobile terminal 900 includes: a form information receiving module, a help form generating module, a parameterization processing module, and a help information sending module.
  • the form information receiving module 901 is configured to receive the form information sent by the requesting end, wherein the form information is form information generated by the requesting end creation requesting session.
  • the help form generation module 902 is configured to generate a help form using the form information.
  • the parameterization processing module 903 is configured to receive an operation event input by the user in the help form, and parameterize the operation event to obtain a parameter.
  • the help information sending module 904 is configured to send the help information including the parameter to the requesting end, and enable the requesting end to execute the parameter included in the help information in the request form.
  • the help form generating module 902 includes: a generating unit, a third determining unit, and a switching unit.
  • the generating unit 9021 is configured to parse the form information sent by the requesting end to generate a help form identical to the request form.
  • the third determining unit 9022 is configured to determine whether the number of help forms generated by the responding end is greater than 1.
  • the second switching unit 9023 is configured to place the generated new help form in the background of the responding end if the number of help forms that the responder has generated is greater than one.
  • the help information sending module 904 includes: an encryption unit and a sending unit.
  • the help information sending module sends the help information including the parameter to the requesting end, including:
  • the encryption unit 9041 is configured to encrypt the help information including the parameter to generate encrypted help information.
  • the sending unit 9042 is configured to send the encrypted help information including the parameter to the requesting end.
  • the mobile terminal 900 can implement the method provided in the embodiment shown in FIG. 3, that is, the method provided in the embodiment shown in FIG. 3 can be implemented by the mobile terminal 900, and the same technical effect can be achieved. I will not repeat them here.
  • the disclosed method and apparatus may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • there may be another division manner for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.
  • the requesting side creates a request session and generates form information.
  • the requesting end sends the form information to the responding end, so that the responding end generates the help form by using the form information.
  • the requesting end receives the help information sent by the responding end, where the help information includes a parameter obtained by the responding end to parameterize the operation event.
  • the requesting end executes the parameter included in the help information.
  • the requesting end creates a request session in the request form, and generates a window of the request form.
  • Body information includes:
  • the requesting end determines whether the number of requesting sessions that have been created and placed in the background of the requesting end is less than a preset threshold number of requesting sessions.
  • the requesting end creates a requesting session on the request form.
  • the requesting end encrypts the request form to generate encrypted form information of the request form.
  • the executing, by the requesting end, the parameter included in the help information in the request form includes:
  • the requesting end switches the request form to the foreground display.
  • the requesting end reads the parameter included in the help information and assigns the parameter to the request form.
  • the requesting end of the requesting form to switch the request form to the foreground display includes:
  • the requesting end If the requesting end does not receive the delay processing instruction, the requesting end switches the request form to the foreground display.
  • the requesting end If the requesting end receives the delay processing instruction, the requesting end switches the request form to the foreground display after a preset delay processing time.
  • the response terminal receives the form information sent by the requesting end, wherein the form information is form information generated by the requesting end creation requesting session.
  • the response end generates the help form using the form information.
  • the response end receives an operation event input by the user in the help form, and parameterizes the operation event to obtain a parameter.
  • the operation event is an operation event that the response end receives a user input in the help form.
  • the responding end generates the help form by using the form information, including:
  • the response end parses the form information sent by the requesting end to generate a help form.
  • the responder places a new help form generated in the background of the responder.
  • the sending, by the responding end, the help information that includes the parameter to the requesting end includes:
  • the response end encrypts the help information including the parameter to generate encrypted help information.
  • the responder sends the encrypted help information including the parameter to the requesting end.
  • the storage medium is, for example, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.
  • the solution of the embodiment of the present invention is to achieve the purpose of asynchronously assisting the requesting end and the responding end by means of creating a requesting session.
  • asynchronous assisting process both the time of the two parties and other application operations on the mobile terminals of the two parties are not restricted.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Telephone Function (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请提供了一种移动终端的协助方法及移动终端，该方法包括：请求端创建请求会话，生成窗体信息；所述请求端向响应端发送所述窗体信息，令响应端使用所述窗体信息生成帮助窗体；所述请求端接收所述响应端发送的帮助信息，其中，所述帮助信息包含所述响应端将操作事件进行参数化处理得到的参数；所述请求端执行所述帮助信息包含的所述参数。

Description

一种移动终端的协助方法及移动终端 技术领域
本申请涉及但不限于通信技术领域，尤其涉及一种移动终端的协助方法及移动终端。
背景技术
随着移动终端技术的快速更新，其搭载的功能越来越丰富，逐渐成为不同领域、不同年龄段人群不可或缺的通讯或娱乐工具。然而，对于老人或者对移动终端操作不够熟悉的人群来说，移动终端的很多新功能不知道如何使用，对于想学习使用新功能的人群来说，经常面临缺乏当面指导对象的困扰。目前，为了解决这一问题，存在对移动终端实施远程协助的方法。然而，在实施远程协助时，被协助方与协助方需要同步进行，且双方移动终端上的其它应用操作均需要停止。可见，远程协助存在对双方时间限制且对双方移动终端上其它应用操作限制的问题。
发明内容
以下是对本文详细描述的主题的概述。本概述并非是为了限制权利要求的保护范围。
本发明实施例的目的在于提供一种移动终端的协助方法及移动终端，解决了远程协助存在对双方时间限制且对双方移动终端上其它应用操作限制的问题。
一种移动终端的协助方法，包括：
请求端创建请求会话，生成窗体信息。
所述请求端向响应端发送所述窗体信息，令响应端使用所述窗体信息生成帮助窗体。
所述请求端接收所述响应端发送的帮助信息，其中，所述帮助信息包含所述响应端将操作事件进行参数化处理得到的参数。
所述请求端执行所述帮助信息包含的所述参数。
一种移动终端的协助方法，包括：
响应端接收请求端发送的窗体信息，其中，所述窗体信息是所述请求端创建请求会话生成的窗体信息。
所述响应端使用所述窗体信息生成帮助窗体。
所述响应端在所述帮助窗体中接收用户输入的操作事件，并将所述操作事件进行参数化处理得到参数。
所述响应端向所述请求端发送包含所述参数的帮助信息，令所述请求端在所述请求窗体执行所述帮助信息包含的所述参数。
一种移动终端，包括：窗体信息生成模块、窗体信息发送模块、帮助信息接收模块和帮助信息执行模块。
窗体信息生成模块，设置为在请求窗体创建请求会话，生成窗体信息。
窗体信息发送模块，设置为向响应端发送所述窗体信息，令响应端使用所述窗体信息生成帮助窗体。
帮助信息接收模块，设置为接收所述响应端发送的帮助信息，其中，所述帮助信息包含所述响应端将操作事件进行参数化处理得到的参数，所述操作事件是所述响应端在所述中间窗体中接收用户输入的操作事件。
帮助信息执行模块，设置为所述请求端执行所述帮助信息包含的所述参数。
一种移动终端，包括：窗体信息接收模块、帮助窗体生成模块、参数化处理模块和帮助信息发送模块。
窗体信息接收模块，设置为接收请求端发送的窗体信息，其中，所述窗体信息是所述请求端创建请求会话生成的窗体信息。
帮助窗体生成模块，设置为使用所述窗体信息生成帮助窗体。
参数化处理模块，设置为在所述帮助窗体中接收用户输入的操作事件，并将所述操作事件进行参数化处理得到参数。
帮助信息发送模块，设置为所述响应端向所述请求端发送包含所述参数的帮助信息，令所述请求端在所述请求窗体执行所述帮助信息包含的所述参 数。
一种计算机储存介质，所述计算机储存介质中储存有计算机可执行的一个或多个程序，所述一个或多个程序被所述计算机执行时使所述计算机执行如上述提供的一种移动终端的协助方法。
上述技术方案中的一个技术方案具有如下优点或有益效果：本发明实施例中，上述方法通过创建请求会话的方式，以实现请求端和响应端异步协助的目的，在异步协助过程中，双方时间及双方移动终端上其它应用操作均可不受限制。
附图概述
图1为本发明实施例提供的一种移动终端的协助方法的流程示意图；
图2为本发明实施例提供的另一种移动终端的协助方法的流程示意图；
图3为本发明实施例提供的另一种移动终端的协助方法的流程示意图；
图4为本发明实施例提供的另一种移动终端的协助方法的流程示意图；
图5为本发明实施例提供的一种移动终端的协助装置的结构示意图；
图6为本发明实施例提供的另一种移动终端的协助装置的结构示意图；
图7为本发明实施例提供的另一种移动终端的协助装置的结构示意图；
图8为本发明实施例提供的另一种移动终端的协助装置的结构示意图；
图9为本发明实施例提供的另一种移动终端的协助装置的结构示意图；
图10为本发明实施例提供的另一种移动终端的协助装置的结构示意图；
图11为本发明实施例提供的另一种移动终端的协助装置的结构示意图。
本发明的实施方式
下文中将结合附图对本发明的实施例进行详细说明。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互任意组合。
请参阅图1，图1是本发明实施例提供的一种移动终端的协助方法的流程示意图，如图1所示，包括以下步骤S101-S104：
S101、请求端创建请求会话，生成窗体信息。
在该步骤中，上述请求端在开机状态下，均可以在当前窗体创建请求帮助的请求会话，以获取他人的协助。如果在当前窗体创建了请求会话，则当前窗体则成为一个请求窗体。当请求端在请求窗体创建了请求会话，请求端会生成该请求窗体的窗体信息。
其中，创建请求会话的过程可以通过请求端提供的创建请求会话的接口来实现，可以将该接口显示在请求端界面的最上层，以便于用户随时启用该接口；还可以将该接口的优先级设置为最高，不受请求端上的其它操作或其它服务所影响。
此外，创建请求会话时，上述请求端可以自由选择请求对象，即自由选择响应端。其中，选择响应端的过程可以在请求端创建请求会话时进行，即请求端创建请求会话时，在请求端中提交响应端的电话号码，触发连接服务器，获取自身的用户ID和数字证书等信息，并获取与该电话号码相对应的用户ID和数字证书等信息。当请求端获取到自身的用户ID和响应端的用户ID时，将这两个ID信息拼接字符串作为请求端创建的请求会话的ID。
上述连接服务器可以是每个运营商搭建的存储有用户ID或用户电话号码或数字证书的服务器。该服务器具有注册和传递请求端和响应端之间按照一定规范格式提交关键有用信息的功能，该关键有用信息不限于包括注册时的用户ID、终端标识号及数字证书等。
其中，生成该请求窗体的窗体信息的过程，可以是在请求会话创建时，将该请求窗体进行封装，以生成上述窗体信息。例如，将当前所操作的应用名称、版本信息及当前应用界面一同进行封装。上述窗体信息可以包括但不限于应用界面、应用名称和应用版本等。
S102、所述请求端向响应端发送所述窗体信息，令响应端使用所述窗体信息生成帮助窗体。
在该步骤中，上述请求端向响应端发送窗体信息后，当前的请求窗体可以设置为不可操作状态，以等待响应端反馈的帮助信息。需要说明的是，当前的请求窗体虽然为不可操作状态，但是用户在请求端进行其他应用操作并不受限制。
如果用户在请求端需要进行其他应用操作时，请求端只需将当前的请求窗体调至后台运行即可，不受请求会话创建事件的任何影响和限制。
请求端可以调用显示功能模块给用户弹出提示，例如弹出提示“创建请求已发送，用户可以在当前终端上进行其他应用操作，但发出请求的当前应用界面需要等待帮助回复后再进行操作”。
S103、所述请求端接收所述响应端发送的帮助信息，其中，所述帮助信息包含所述响应端将操作事件进行参数化处理得到的参数。
在该步骤中，上述请求端接收到的从响应端发送过来的帮助信息可以是经过封装的帮助信息，上述请求端需要对封装的帮助信息进行解析。
S104、所述请求端执行所述帮助信息包含的所述参数。
在该步骤中，上述请求端可以将接收到的帮助信息执行于请求窗体上。至此，对于该请求窗体的帮助过程即完成。该请求窗体获得帮助后，该请求窗体所在的应用操作会跳转到下一个窗体，并可接受用户的自由操作。用户可以进行自由操作，也可以在当前的窗体再次创建请求会话。
本发明实施例中，上述方法可以应用于手机、平板、笔记本电脑等移动终端中，即这些装置可以实现上述方法。
本发明实施例中，通过创建请求会话的方式，以实现请求端和响应端异步协助的目的，在异步协助过程中，双方时间及双方移动终端上其它应用操作均可不受限制。
可选地，所述请求端在所述请求窗体执行所述帮助信息包含的所述参数，包括：
判断所述请求端的当前窗体是否为所述请求窗体。
如果所述请求端的当前窗体不为所述请求窗体，则所述请求端将所述请求窗体切换到前台显示。
所述请求端读取所述帮助信息包含的所述参数，并将所述参数赋值于所述请求窗体。
由于请求端在创建请求会话之后，可以将请求窗体切换到后台来进行其他应用操作，因此请求端在接收到响应端发送的帮助信息时，很有可能不是 请求窗体。当请求端的当前窗体不是请求窗体时，则请求端将请求窗体从后台切换到前台显示。在请求端将请求窗体切换到前台后，请求端读取帮助信息中包含的参数，将该参数赋值于该请求窗体。至此，对于该请求窗体的帮助过程即完成。
本发明实施方式中，通过将请求窗体在后台和前台的切换，可以使请求端在进行异步协助时，更好的确保异步协助过程中移动终端操作不受限制的目的。
可选地，所述请求端将所述请求窗体切换到前台显示，包括：
判断所述请求端是否接收到延迟处理指令。
如果所述请求端未接收到延迟处理指令，则所述请求端将所述请求窗体切换到前台显示。
如果所述请求端接收到所述延迟处理指令，则经预设的延迟处理时间后，所述请求端将所述请求窗体切换到前台显示。
当请求端的当前窗体不是请求窗体时，请求端可以自动将请求窗体切换到前台显示，也可以向用户发出通知，由用户决定是否同意切换当前应用界面到请求窗体。例如，请求端弹出提示消息：“创建的请求会话已收到帮助信息，请用户选择是否应用该帮助信息”。
例如，请求端可以向用户提供三种选择界面：
当用户选择“是”，则请求端立即将请求窗体切换到前台显示。
当用户选择“否”，则请求端继续显示当前窗体，并结束该请求窗体的异步协助。
当用户选择“延迟处理”，则请求端启动预警计时，当计时时间达到预设的延迟处理时间时，请求端可以将请求窗体切换到前台显示，也可以弹出提示消息：“该帮助信息已作延迟处理，是否立即运行所接收的帮助信息，否则该帮助信息将失效。”。对于后者，用户可以选择“是”，则请求端立即将请求窗体切换到前台显示；用户也可以选择“否”，则请求端继续显示当前窗体，并结束该请求窗体的异步协助。
本发明实施方式中，通过由用户自由决定是否同意切换当前应用界面来 运行帮助信息，可以提高请求端在异步协助中的主导地位。
请参阅图2，图2是本发明实施例提供的一种移动终端的协助方法的流程示意图，如图2所示，包括以下步骤S201-S206：
S201、所述请求端判断已创建并置于所述请求端后台中的请求会话的数量是否小于预先设置的请求会话数量阈值。
在该步骤中，上述请求端可以预先设置可置于后台的请求会话数量阈值，用于控制上述请求端在一定时间段内所能够创建的请求会话的数量。当请求端接收到有请求会话需要创建时，首先检测该请求端已创建的请求会话数量是否小于预设的请求会话数量阈值。
S202、如果已创建并置于所述请求端后台中的请求会话的数量小于预先设置的请求会话数量阈值，则所述请求端在所述请求窗体创建请求会话。
在该步骤中，如果请求端检测到已创建的在请求端后台中的请求会话数量小于预设的请求会话数量阈值，则该请求端在当前请求窗体中可以创建请求会话。如果请求端检测到已创建的在请求端后台中的请求会话数量大于或者等于预设的请求会话数量阈值，则该请求端可以拒绝创建新的请求会话。
S203、所述请求端对所述请求窗体进行加密，生成所述请求窗体的加密的窗体信息。
在该步骤中，上述请求端可以对请求窗体进行加密，以生成该请求窗体的加密的窗体信息。
S204、所述请求端向响应端发送所述窗体信息，令响应端使用所述窗体信息生成与所述请求窗体相同的帮助窗体。
S205、所述请求端接收所述响应端发送的帮助信息，其中，所述帮助信息包含所述响应端将操作事件进行参数化处理得到的参数，所述操作事件是所述响应端在所述中间窗体中接收用户输入的操作事件。
S206、所述请求端在所述请求窗体执行所述帮助信息包含的所述参数。
本发明实施例中，通过对请求窗体进行加密，为窗体信息提供安全机制，实现了发送请求会话的安全性；并通过创建多个请求会话实现异步处理多个不同的请求会话，提高了用户体验。
请参阅图3，图3是本发明实施例提供的一种移动终端的协助方法的流程示意图，如图3所示，包括以下步骤S301-S304：
S301、响应端接收请求端发送的窗体信息，其中，所述窗体信息是所述请求端创建请求会话生成的窗体信息。
在该步骤中，上述响应端接收到请求端发送的窗体信息时，可以根据所连接服务器获取该窗体信息的关键有用信息，利用该关键有用信息可以对该窗体信息进行解析。如果该窗体信息做了加密，则响应端还可以利用该关键有用信息对该窗体信息进行解密。
S302、所述响应端使用所述窗体信息生成帮助窗体。
在该步骤中，上述响应端使用解析后，也可能是解析并解密后的窗体信息，在该响应端生成与请求窗体相同的帮助窗体。
S303、所述响应端在所述帮助窗体中接收用户输入的操作事件，并将所述操作事件进行参数化处理得到参数。
在该步骤中，该响应端具有录制用户操作的功能，当用户在上述帮助窗体中输入操作事件时，响应端将用户输入的操作事件进行参数化处理，并得到包含参数的帮助信息。操作事件可以包含用户在帮助窗体中输入的控件信息及输入信息。
S304、所述响应端向所述请求端发送包含所述参数的帮助信息，令所述请求端在所述请求窗体执行所述帮助信息包含的所述参数。
在该步骤中，上述响应端根据所连接服务器，获取到响应端及请求端的关键有用信息，对帮助信息进行封装后，响应端按照之前请求端发送来的请求会话标识，向请求端发送封装好的帮助信息。请求端在接收到响应端发送来的帮助信息后，请求端需要对帮助信息进行解析并执行帮助信息中包含的参数。
本发明实施例中，通过接收请求会话的方式，以实现请求端和响应端异步协助的目的，在异步协助过程中，双方时间及双方移动终端上其它应用操作均可不受限制。
可选地，所述响应端对所述请求端发送的所述窗体信息进行解析，以生 成与所述请求窗体相同的帮助窗体。
判断所述响应端已生成的帮助窗体的数量是否大于1。
如果所述响应端已生成的帮助窗体的数量大于1，则所述响应端将生成的新的帮助窗体置于所述响应端的后台。
本发明实施方式中，响应端对窗体信息进行解析时，响应端有可能正在处理请求端在前期发送的其它请求会话，因此，需要判断当前响应端前台是否正在录入帮助信息，即判断该响应端已生成的帮助窗体的数量是否大于1。如果当前响应端前台正在录入帮助信息时，则将新解析生成的帮助窗体置于响应端的后台运行。当响应端后台运行多个帮助窗体时，响应端按照请求会话的接收顺序，将后台运行的帮助窗体进行逐个调用并在前台显示。
如果当前响应端前台未进行帮助信息录入时，响应端可以发出通知，告知用户可将新解析生成的帮助窗体置于响应端的前台显示并进行帮助信息的录入。
本发明实施方式中，通过接收多个请求会话实现异步处理多个不同的请求会话，提高了用户体验。
可选地，所述响应端向所述请求端发送包含所述参数的帮助信息，包括：
所述响应端对包含所述参数的帮助信息进行加密，生成加密的帮助信息。
所述响应端向所述请求端发送包含所述参数的所述加密的帮助信息。
本发明实施例中，响应端可以对帮助信息进行加密，以提高安全性能。请求端需要对帮助信息进行解密并执行帮助信息中包含的参数。
请参阅图4，图4是一种移动终端的协助方法的流程示意图，如图4所示，包括以下步骤S401-S414：
S401、请求端在请求窗体提交创建请求会话的指令,并检测后台请求会话的数量。
请求端开机进程结束后，通过请求端提供的创建请求会话的接口提交创建请求会话的指令。该接口可以显示在请求端界面的最上层，该接口的优先级可以设置为最高，不受请求端上的其他操作和其他服务所影响。
当请求端检测到用户对当前应用界面操作发起创建请求会话时，读取其记录的活跃请求会话数量。
S402、判断后台请求会话的数量是否超出预设的阈值。
如果后台请求会话的数量超出预设的阈值，则执行S403；如果后台请求会话的数量未超出预设的阈值，执行S404。
S403、请求端拒绝创建请求会话。
请求端还可以弹出提示框：“当前请求会话的数量达到最大，请完成其他请求会话后再发起新的请求会话。”。
S404、请求端创建请求会话，并封装当前请求窗体的窗体信息，进而发送给响应端。
当请求端将请求窗体的窗体信息进行封装并发送给响应端的同时，可以向用户弹出提示，例如，“创建的请求已发送，请用户可以在当前终端上进行一些其他应用操作，但发出请求的当前应用界面需要等待帮助回复后再进行操作。”。
请求端可以将请求窗体调至后台运行，用户可以在当前请求端上进行其他应用操作，不受请求发起事件的任何影响和限制。
S405、响应端接收并解析请求端发送的窗体信息，生成帮助窗体。
响应端检测到有封装的窗体信息发来时，解析请求端发送的窗体信息，生成帮助窗体。
S406、在整个请求会话过程中，请求端实时检测当前请求窗体变化情况。
请求端在请求会话发送时，即可以开启实时检测进程，检测所提交的请求窗体是否会发生改变。
S407、判断当前请求窗体是否发生改变，如果当前请求窗体发生改变，则执行S408；如果当前请求窗体未发生改变，则执行S410。
S408、请求端提醒用户请求窗体发生改变，导致所发出的请求中断，并结束当前请求会话进程。
请求端检测到当前请求窗体发生改变时，请求端弹出提示信息，通知用 户因进行的当前一些操作，已使请求窗体发生改变，导致所发出的请求中断。
S409、请求端将请求中断的状态发送给响应端，响应端可终止帮助信息的录入。
S410、响应端在帮助窗体上录入帮助信息，并将帮助信息参数化后进行封装发送给请求端。
用户在响应端前台显示的帮助窗体上，进行帮助信息的录入及相关控件操作，同时，响应端将用户在帮助窗体上的操作顺序、每个控件操作及属性信息进行参数化，并保存帮助窗体上输入的帮助信息。响应端检测到帮助信息录入完毕时，将帮助信息进行封装后发送给请求端。
S411、请求端接收到响应端发送的帮助信息，并通知用户是否调用请求窗体置于前台运行帮助信息。
请求端接收到响应端发送的帮助信息时，可以向用户弹出提示信息：“创建的请求会话已收到帮助信息，请用户选择是否预览和应用该帮助信息。”。
S412、判断是否调用。
请求端提供3种选择界面，当用户选择“是”，则执行S413。
当用户选择“延迟处理”，则执行S414。
S413、请求端切换当前业务，调用请求窗体置于前台运行帮助信息。
请求端将所读取的帮助信息中的各参数在请求窗体上进行自动化运行。
S414、请求端继续进行当前业务，当前请求会话进程进入等待状态；当等待预警时间到达时，系统给出提示，判断是否调用。
请求端启动系统预警计时进程，并将当前操作应用的显示优先级保持最高；当等待预警时间到达时，请求端弹出提示信息：“该帮助信息已作延迟处理，是否立即运行所接收的帮助信息，否则该请求信息将失效。”。当用户选择“是”，则执行S413；当用户选择“否”，则结束该请求会话，且在请求端前台继续显示当前应用界面。
请参阅图5，图5是一种移动终端的结构示意图，如图5所示，移动终端500包括：窗体信息生成模块501、窗体信息发送模块502、帮助信息接收 模块503和帮助信息执行模块504。
窗体信息生成模块501，设置为创建请求会话，生成窗体信息。
窗体信息发送模块502，设置为向响应端发送所述窗体信息，令响应端使用所述窗体信息生成帮助窗体。
帮助信息接收模块503，设置为所述请求端接收所述响应端发送的帮助信息，其中，所述帮助信息包含所述响应端将操作事件进行参数化处理得到的参数，所述操作事件是所述响应端在所述中间窗体中接收用户输入的操作事件。
帮助信息执行模块505，设置为执行所述帮助信息包含的所述参数。
可选地，如图6所示，窗体信息生成模块501包括：
第一判断单元5011，设置为所述请求端判断已创建并置于所述请求端后台中的请求会话的数量是否小于预先设置的请求会话数量阈值。
创建单元5012，设置为如果已创建并置于所述请求端后台中的请求会话的数量小于预先设置的请求会话数量阈值，则在所述请求窗体创建请求会话。
生成单元5013，设置为对所述请求窗体进行加密，生成所述请求窗体的加密的窗体信息。
可选地，如图7所示，帮助信息执行模块505包括：第二判断单元、切换单元和读取单元。
所述帮助信息执行模块执行所述帮助信息包含的所述参数包括：
第二判断单元5051，设置为判断所述请求端的当前窗体是否为所述请求窗体。
第一切换单元5052，设置为如果所述请求端的当前窗体不为所述请求窗体，则将所述请求窗体切换到前台显示；
读取单元5053，设置为读取所述帮助信息包含的所述参数，并将所述参数赋值于所述请求窗体。
可选地，如图8所示，第一切换单元5052，包括：判断子单元、第一切换子单元和第二切换子单元。
所述切换单元将所述请求窗体切换到前台显示包括：
判断子单元50521，设置为判断所述请求端是否接收到延迟处理指令。
第一切换子单元50522，设置为如果所述请求端未接收到延迟处理指令，则将所述请求窗体切换到前台显示。
第二切换子单元50523，设置为如果所述请求端接收到所述延迟处理指令，则经预设的延迟处理时间后，将所述请求窗体切换到前台显示。
本实施例中，移动终端500可以为实现图1-图2所示的实施例中提供的方法，即图1-图2所示的实施例中提供的方法都可以移动终端500实现，也能达到相同的技术效果，在此不再赘述。
请参阅图9，图9是一种移动终端的结构示意图，如图9所示，移动终端900包括：窗体信息接收模块、帮助窗体生成模块、参数化处理模块和帮助信息发送模块。
窗体信息接收模块901，设置为接收请求端发送的窗体信息，其中，所述窗体信息是所述请求端创建请求会话生成的窗体信息。
帮助窗体生成模块902，设置为使用所述窗体信息生成帮助窗体。
参数化处理模块903，设置为在所述帮助窗体中接收用户输入的操作事件，并将所述操作事件进行参数化处理得到参数。
帮助信息发送模块904，设置为向所述请求端发送包含所述参数的帮助信息，令所述请求端在所述请求窗体执行所述帮助信息包含的所述参数。
可选地，如图10所示，帮助窗体生成模块902包括：生成单元、第三判断单元和切换单元。
生成单元9021，设置为对所述请求端发送的所述窗体信息进行解析，生成与所述请求窗体相同的帮助窗体。
第三判断单元9022，设置为判断所述响应端已生成的帮助窗体的数量是否大于1。
第二切换单元9023，设置为如果所述响应端已生成的帮助窗体的数量大于1，则将生成的新的帮助窗体置于所述响应端的后台。
可选地，如图11所示，帮助信息发送模块904包括：加密单元和发送单元。
所述帮助信息发送模块向所述请求端发送包含所述参数的帮助信息包括：
加密单元9041，设置为对包含所述参数的帮助信息进行加密，生成加密的帮助信息。
发送单元9042，设置为向所述请求端发送包含所述参数的所述加密的帮助信息。
本实施例中，移动终端900可以为实现图3所示的实施例中提供的方法，即图3所示的实施例中提供的方法都可以移动终端900实现，也能达到相同的技术效果，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露方法和装置，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
本领域普通技术人员可以理解实现上述实施例方法的全部或者部分步骤是可以通过程序指令相关的硬件来完成，所述的程序可以储存于一计算机可读取介质中，该程序在执行时，包括以下步骤：
请求端创建请求会话，生成窗体信息。
所述请求端向响应端发送所述窗体信息，令响应端使用所述窗体信息生成帮助窗体。
所述请求端接收所述响应端发送的帮助信息，其中，所述帮助信息包含所述响应端将操作事件进行参数化处理得到的参数。
所述请求端执行所述帮助信息包含的所述参数。
可选地，所述请求端在请求窗体创建请求会话，生成所述请求窗体的窗 体信息包括：
所述请求端判断已创建并置于所述请求端后台中的请求会话的数量是否小于预先设置的请求会话数量阈值。
如果已创建并置于所述请求端后台中的请求会话的数量小于预先设置的请求会话数量阈值，则所述请求端在所述请求窗体创建请求会话。
所述请求端对所述请求窗体进行加密，以生成所述请求窗体的加密的窗体信息。
可选地，所述请求端在所述请求窗体执行所述帮助信息包含的所述参数包括：
判断所述请求端的当前窗体是否为所述请求窗体。
如果所述请求端的当前窗体不为所述请求窗体，则所述请求端将所述请求窗体切换到前台显示。
所述请求端读取所述帮助信息包含的所述参数，并将所述参数赋值于所述请求窗体。
可选地，所述则所述请求端将所述请求窗体切换到前台显示包括：
判断所述请求端是否接收到延迟处理指令。
如果所述请求端未接收到延迟处理指令，则所述请求端将所述请求窗体切换到前台显示。
如果所述请求端接收到所述延迟处理指令，则经预设的延迟处理时间后，所述请求端将所述请求窗体切换到前台显示。
该程序在执行时，还可以包括以下步骤：
响应端接收请求端发送的窗体信息，其中，所述窗体信息是所述请求端创建请求会话生成的窗体信息。
所述响应端使用所述窗体信息生成帮助窗体。
所述响应端在所述帮助窗体中接收用户输入的操作事件，并将所述操作事件进行参数化处理得到参数。
所述响应端向所述请求端发送包含所述参数的帮助信息，令所述请求端 在所述请求窗体执行所述帮助信息包含的所述参数。
可选地，所述操作事件是所述响应端在所述帮助窗体中接收用户输入的操作事件。
可选地，所述响应端使用所述窗体信息生成帮助窗体包括：
所述响应端对所述请求端发送的所述窗体信息进行解析，生成帮助窗体。
判断所述响应端已生成的帮助窗体的数量是否大于1。
如果所述响应端已生成的帮助窗体的数量大于1，则所述响应端将生成的新的帮助窗体置于所述响应端的后台。
可选地，所述响应端向所述请求端发送包含所述参数的帮助信息包括：
所述响应端对包含所述参数的帮助信息进行加密，生成加密的帮助信息。
所述响应端向所述请求端发送包含所述参数的所述加密的帮助信息。
所述的储存介质，如只读储存器(Read-Only Memory，简称ROM)、随机存取储存器(Random Access Memory，简称RAM)、磁碟或者光盘等。
以上所述，仅为本发明实施例的实施方式，但本发明实施例的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本发明实施例揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本发明实施例的保护范围之内。因此，本发明实施例的保护范围应以权利要求的保护范围为准。
工业实用性
本发明实施例方案通过创建请求会话的方式，以实现请求端和响应端异步协助的目的，在异步协助过程中，双方时间及双方移动终端上其它应用操作均可不受限制。

Claims (16)

  1. 一种移动终端的协助方法，包括：
    请求端创建请求会话，生成窗体信息；
    所述请求端向响应端发送所述窗体信息，令响应端使用所述窗体信息生成帮助窗体；
    所述请求端接收所述响应端发送的帮助信息，其中，所述帮助信息包含所述响应端将操作事件进行参数化处理得到的参数；
    所述请求端执行所述帮助信息包含的所述参数。
  2. 如权利要求1所述的移动终端的协助方法，其中，所述请求端创建请求会话，生成窗体信息包括：
    所述请求端判断已创建并置于所述请求端后台中的请求会话的数量是否小于预先设置的请求会话数量阈值；
    如果已创建并置于所述请求端后台中的请求会话的数量小于预先设置的请求会话数量阈值，则所述请求端在所述请求窗体创建请求会话；
    所述请求端对所述请求窗体进行加密，生成所述请求窗体的加密的窗体信息。
  3. 如权利要求2所述的移动终端的协助方法，其中，所述请求端执行所述帮助信息包含的所述参数包括：
    判断所述请求端的当前窗体是否为所述请求窗体；
    如果所述请求端的当前窗体不为所述请求窗体，则所述请求端将所述请求窗体切换到前台显示；
    所述请求端读取所述帮助信息包含的所述参数，并将所述参数赋值于所述请求窗体。
  4. 如权利要求3所述的移动终端的协助方法，其中，所述请求端将所述请求窗体切换到前台显示包括：
    判断所述请求端是否接收到延迟处理指令；
    如果所述请求端未接收到延迟处理指令，则所述请求端将所述请求窗体 切换到前台显示；
    如果所述请求端接收到所述延迟处理指令，则经预设的延迟处理时间后，所述请求端将所述请求窗体切换到前台显示。
  5. 一种移动终端的协助方法，包括：
    响应端接收请求端发送的窗体信息，其中，所述窗体信息是所述请求端创建请求会话生成的窗体信息；
    所述响应端使用所述窗体信息生成帮助窗体；
    所述响应端在所述帮助窗体中接收用户输入的操作事件，并将所述操作事件进行参数化处理得到参数；
    所述响应端向所述请求端发送包含所述参数的帮助信息，令所述请求端在所述请求窗体执行所述帮助信息包含的所述参数。
  6. 如权利要求5所述的移动终端的协助方法，其中，所述操作事件是所述响应端在所述帮助窗体中接收用户输入的操作事件。
  7. 如权利要求5或6所述的移动终端的协助方法，其中，所述响应端使用所述窗体信息生成帮助窗体包括：
    所述响应端对所述请求端发送的所述窗体信息进行解析，生成帮助窗体；
    判断所述响应端已生成的帮助窗体的数量是否大于1；
    如果所述响应端已生成的帮助窗体的数量大于1，则所述响应端将生成的新的帮助窗体置于所述响应端的后台。
  8. 如权利要求5或6所述的移动终端的协助方法，其中，所述响应端向所述请求端发送包含所述参数的帮助信息包括：
    所述响应端对包含所述参数的帮助信息进行加密，生成加密的帮助信息；
    所述响应端向所述请求端发送包含所述参数的所述加密的帮助信息。
  9. 一种移动终端，包括：窗体信息生成模块、窗体信息发送模块、帮助信息接收模块和帮助信息执行模块；
    所述窗体信息生成模块，设置为创建请求会话，生成窗体信息；
    所述窗体信息发送模块，设置为向响应端发送所述窗体信息，令响应端 使用所述窗体信息生成帮助窗体；
    所述帮助信息接收模块，设置为接收所述响应端发送的帮助信息，其中，所述帮助信息包含所述响应端将操作事件进行参数化处理得到的参数；
    所述帮助信息执行模块，设置为执行所述帮助信息包含的所述参数。
  10. 如权利要求9所述的移动终端，其中，所述窗体信息生成模块包括：第一判断单元、创建单元和生成单元；
    所述窗体信息生成模块创建请求会话，生成窗体信息包括：
    所述第一判断单元，设置为判断已创建并置于所述请求端后台中的请求会话的数量是否小于预先设置的请求会话数量阈值；
    所述创建单元，设置为如果已创建并置于所述请求端后台中的请求会话的数量小于预先设置的请求会话数量阈值，则在所述请求窗体创建请求会话；
    所述生成单元，设置为对所述请求窗体进行加密，生成所述请求窗体的加密的窗体信息。
  11. 如权利要求9或10所述的移动终端，其特征在于，所述帮助信息执行模块包括：第二判断单元、切换单元和读取单元；
    所述帮助信息执行模块执行所述帮助信息包含的所述参数包括：
    所述第二判断单元，设置为判断所述请求端的当前窗体是否为所述请求窗体；
    所述切换单元，设置为如果所述请求端的当前窗体不为所述请求窗体，则将所述请求窗体切换到前台显示；
    所述读取单元，设置为读取所述帮助信息包含的所述参数，并将所述参数赋值于所述请求窗体。
  12. 如权利要求11所述的移动终端，其特征在于，所述切换单元包括：判断子单元、第一切换子单元和第二切换子单元；
    所述切换单元将所述请求窗体切换到前台显示包括：
    所述判断子单元，设置为判断所述请求端是否接收到延迟处理指令；
    所述第一切换子单元，设置为如果所述请求端未接收到延迟处理指令， 则将所述请求窗体切换到前台显示；
    所述第二切换子单元，设置为如果所述请求端接收到所述延迟处理指令，则经预设的延迟处理时间后，将所述请求窗体切换到前台显示。
  13. 一种移动终端，包括：窗体信息接收模块、帮助窗体生成模块、参数化处理模块和帮助信息发送模块；
    所述窗体信息接收模块，设置为接收请求端发送的窗体信息，其中，所述窗体信息是所述请求端创建请求会话生成的窗体信息；
    所述帮助窗体生成模块，设置为使用所述窗体信息生成帮助窗体；
    所述参数化处理模块，设置为在所述帮助窗体中接收用户输入的操作事件，并将所述操作事件进行参数化处理得到参数；
    所述帮助信息发送模块，设置为向所述请求端发送包含所述参数的帮助信息，令所述请求端在所述请求窗体执行所述帮助信息包含的所述参数。
  14. 如权利要求13所述的移动终端，其中，所述操作事件是所述响应端在所述帮助窗体中接收用户输入的操作事件。
  15. 如权利要求13或14所述的移动终端，其中，所述帮助窗体生成模块包括：生成单元、第三判断单元和切换单元；
    所述帮助窗体生成模块使用所述窗体信息生成帮助窗体包括：
    所述生成单元，设置为对所述请求端发送的所述窗体信息进行解析，生成帮助窗体；
    第三判断单元，设置为判断所述响应端已生成的帮助窗体的数量是否大于1；
    切换单元，设置为如果所述响应端已生成的帮助窗体的数量大于1，则将生成的新的帮助窗体置于所述响应端的后台。
  16. 如权利要求13或14所述的移动终端，其特征在于，所述帮助信息发送模块，包括：加密单元和发送单元；
    所述帮助信息发送模块向所述请求端发送包含所述参数的帮助信息包括：
    所述加密单元，设置为对包含所述参数的帮助信息进行加密，生成加密的帮助信息；
    所述发送单元，设置为向所述请求端发送包含所述参数的所述加密的帮助信息。
PCT/CN2016/092362 2016-07-06 2016-07-29 一种移动终端的协助方法及移动终端 WO2018006453A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610527694.3A CN107592283B (zh) 2016-07-06 2016-07-06 一种移动终端的协助方法及移动终端
CN201610527694.3 2016-07-06

Publications (1)

Publication Number Publication Date
WO2018006453A1 true WO2018006453A1 (zh) 2018-01-11

Family

ID=60901361

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/092362 WO2018006453A1 (zh) 2016-07-06 2016-07-29 一种移动终端的协助方法及移动终端

Country Status (2)

Country Link
CN (1) CN107592283B (zh)
WO (1) WO2018006453A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113726878A (zh) * 2021-08-30 2021-11-30 深圳追一科技有限公司 在集群环境下的会话处理方法、系统、设备和存储介质

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101163347A (zh) * 2007-11-21 2008-04-16 深圳华为通信技术有限公司 远程控制移动终端的方法及设备
CN102662618A (zh) * 2012-03-29 2012-09-12 北京奇虎科技有限公司 远程协助过程中的图像处理方法及装置
CN103294523A (zh) * 2012-02-22 2013-09-11 腾讯科技（深圳）有限公司 一种远程协助方法和系统
CN104394191A (zh) * 2014-10-22 2015-03-04 腾讯科技（深圳）有限公司 远程控制移动终端的方法、控制终端及系统
CN104506718A (zh) * 2014-12-12 2015-04-08 上海斐讯数据通信技术有限公司 一种智能手机间远程协助的系统及其方法
WO2015117367A1 (zh) * 2014-08-21 2015-08-13 中兴通讯股份有限公司 远程协助的控制方法及装置

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102521027B (zh) * 2011-12-02 2013-10-30 华中科技大学 虚拟桌面系统中的窗口界面传输方法

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101163347A (zh) * 2007-11-21 2008-04-16 深圳华为通信技术有限公司 远程控制移动终端的方法及设备
CN103294523A (zh) * 2012-02-22 2013-09-11 腾讯科技（深圳）有限公司 一种远程协助方法和系统
CN102662618A (zh) * 2012-03-29 2012-09-12 北京奇虎科技有限公司 远程协助过程中的图像处理方法及装置
WO2015117367A1 (zh) * 2014-08-21 2015-08-13 中兴通讯股份有限公司 远程协助的控制方法及装置
CN104394191A (zh) * 2014-10-22 2015-03-04 腾讯科技（深圳）有限公司 远程控制移动终端的方法、控制终端及系统
CN104506718A (zh) * 2014-12-12 2015-04-08 上海斐讯数据通信技术有限公司 一种智能手机间远程协助的系统及其方法

Also Published As

Publication number Publication date
CN107592283A (zh) 2018-01-16
CN107592283B (zh) 2021-06-29

Similar Documents

Publication Publication Date Title
WO2022062623A1 (zh) 远程控制方法、装置、设备、存储介质及系统
WO2018014723A1 (zh) 密钥管理方法、装置、设备及系统
WO2021208743A1 (zh) 应用程序的账户绑定
US20190334840A1 (en) Anonymized Identifiers for Secure Communication Systems
US20160197897A1 (en) Cross-client communication method
CN114584613B (zh) 一种推送消息的方法、消息推送系统及电子设备
EP4206919A1 (en) Proxy service-based device calling method, electronic device, and readable storage medium
EP4099690A1 (en) Enhanced video call method and system, and electronic device
WO2015176352A1 (zh) 一种基于安卓系统的应用间信息交互方法及装置
WO2017161724A1 (zh) 一种语音处理的方法、装置以及终端
WO2011137871A2 (zh) 一种通信终端的输入方法及通信终端
CN106126377B (zh) 系统启动的方法及装置
CN110336665B (zh) 一种大数据消息加密方法、装置
WO2018006453A1 (zh) 一种移动终端的协助方法及移动终端
CN114217989A (zh) 设备间的服务调用方法、装置、设备、介质及计算机程序
JPWO2017094774A1 (ja) 制御システム、通信制御方法、及びプログラム
WO2023241613A1 (zh) 通话建立方法、装置、终端、系统及可读存储介质
WO2019071927A1 (zh) 授权信息获取方法、装置、电子设备及可读存储介质
JP2015162040A (ja) 電子機器
US9819725B1 (en) System, method, and computer program for remotely controlling mobile web applications installed on a mobile device
JP2017069936A (ja) 通信端末、通信システム、出力方法、及びプログラム
CN106685931B (zh) 智能卡应用管理方法和系统、终端和智能卡
CN113542231B (zh) 通信方法、电子设备及存储介质
CN113076362B (zh) 业务执行方法及装置
CN109933960B (zh) 服务调用控制方法、服务调用方法、装置及终端

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 16907957

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16907957

Country of ref document: EP

Kind code of ref document: A1