Function jump method, system and function recording, playback method, device and equipment
By recording and simulating the operation steps and execution sequence on the user terminal, the problem of uncontrollable target function jumps caused by manual user operation is solved, and efficient and controllable automatic function jumps are achieved.
Patent Information
- Application Number
- CN201810414053.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2018-05-03
- Publication Date
- 2024-11-22
- Estimated Expiration
- 2039-05-08
AI Technical Summary
In existing technologies, users need to manually perform operation steps when jumping to the target function in the application, which results in high operation costs and uncontrollability, and is prone to delays or failures.
By recording and generating the operation steps and execution sequence on the user terminal, and simulating user operation using view element identifiers and operation mode information, the system automatically jumps to the target function.
It achieves efficient and controllable switching of target functions, reduces manual operations, and improves the ease of use and reliability of user terminals.
Smart Images

Figure CN110442401B_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of computer application technology, and in particular to a method and system for realizing automatic function jump, and a method, device and machine equipment for function recording and playback. Background Art
[0002] With the rapid development of computer application technology, each application has rich functions, and users need to perform various operations according to a certain operation path to enter the required functions.
[0003] When users need to access a certain function in an app but do not know how to operate the app to jump to this function, they often check the help information or ask others for help on how to access this function. For example, for the function of setting the font size in an app, the answer obtained may be a description of the operation path like "enter the main interface->click the avatar->settings->accessibility->font size", or screenshots of the operation process.
[0004] The answer obtained is obtained by manually recording the process of operating the application according to the function that needs to be jumped to. Correspondingly, the questioner needs to operate again according to the answer obtained, and can jump to the function required for help only after successfully operating once.
[0005] Of course, users can also obtain instructions for using various functions in the application's help information, and thus obtain content similar to the above answers.
[0006] In addition, when the app is opened for the first time or a function is released, a prompt message will be displayed to provide users with instructions for jumping into the function.
[0007] However, no matter which method is used, there is only a weak correlation for the implementation of function jump entry in the application, and it is inevitable that the user needs to manually execute step by step according to the obtained operation steps.
[0008] In the manual execution process, it often takes a very high operation cost due to many reasons such as different understandings of certain expressions, which delays the jump to the function or even causes the failure of the function jump. In other words, no matter what method is used to guide users to jump to the required function, there are uncontrollable limitations. Summary of the invention
[0009] In order to solve the technical problem in the related art that the implementation of guiding users to jump to the required functions is uncontrollable, the present invention provides a method and system for implementing automatic function jump, as well as a method, device and machine equipment for function recording and playback.
[0010] A method for realizing automatic function jump, the method comprising:
[0011] Recording and generating a jump execution sequence of operation steps for entering a designated function by the user according to the operation performed on the first user terminal;
[0012] The user terminal acquires an operation step jump execution sequence corresponding to a target function, the user terminal includes a first user terminal, and the target function includes the designated function;
[0013] Jumping to execute the view element identifiers and the operation mode information corresponding to the view element identifiers sequentially in the sequence according to the operation steps, and sequentially executing the operations indicated by the corresponding operation mode information on the user terminal;
[0014] When the corresponding operations are executed in the jump execution sequence corresponding to the operation steps, the user terminal simulates user manipulation to jump into the target function.
[0015] In an exemplary embodiment, the step of recording and generating a jump execution sequence of operation steps for entering a specified function by a user according to the operation performed at the first user terminal includes:
[0016] Receiving a process recording selection corresponding to entering a designated function in a first user terminal;
[0017] The process recording selection triggers the view element jump in the first user terminal and the operation performed on the view element, and sequentially records the corresponding view element identifier and the operation mode information corresponding to the view element identifier until the first user terminal enters the designated function;
[0018] The sequentially recorded view element identifiers and the operation mode information corresponding to the view element identifiers are spliced together to obtain an operation step jump execution sequence for entering the specified function.
[0019] In an exemplary embodiment, the jumping to execute the view element identifier and the operation mode information corresponding to the view element identifier in the sequence according to the operation steps, and sequentially executing the operations indicated by the corresponding operation mode information on the user terminal, includes:
[0020] Parsing the jump execution sequence of the operation steps, and detecting whether the view element identifiers obtained by sequential parsing have corresponding view elements in the user terminal;
[0021] If the view element identifier obtained by the sequential parsing has a corresponding view element in the user terminal, operating the view element according to the operation mode information corresponding to the view element identifier;
[0022] The operation steps are sequentially parsed to jump to the next view element identifier in the execution sequence, and the view element is detected and the detected view element is operated accordingly.
[0023] In an exemplary embodiment, the jumping to execute the view element identifier and the operation mode information corresponding to the view element identifier in the sequence according to the operation steps, and sequentially executing the operations indicated by the corresponding operation mode information on the user terminal, includes:
[0024] If the view element identifier obtained by the sequential parsing does not have a corresponding view element in the user terminal, detecting whether the terminal version of the operation step jump execution sequence is the same as that of the user terminal;
[0025] When it is detected that the terminal version of the operation step jump execution sequence is different from that of the user terminal, converting the view element identifier into a view element update identifier suitable for the user terminal;
[0026] According to the view element update identifier and the operation mode information corresponding to the view element identifier, the corresponding view element is operated on the user terminal.
[0027] In an exemplary embodiment, converting the view element identifier into a view element update identifier applicable to the user terminal includes:
[0028] According to the operation steps, the mapping of view elements between the terminal version where the execution sequence is located and the user terminal is jumped, the view element identifier is converted into a view element identifier corresponding to the mapped view element, and a view element update identifier suitable for the user terminal is obtained.
[0029] In an exemplary embodiment, the view element identifiers and the operation mode information corresponding to the view element identifiers sequentially existing in the jump execution sequence according to the operation steps, before the user terminal sequentially searches for the view element corresponding to each view element identifier and performs the operation indicated by the corresponding operation mode information on the view element, the method further includes:
[0030] According to the mapping of view elements between the published terminal version and the old version, a mapping relationship between the view element identifier in the published terminal version and the view element identifier in the old terminal version is constructed and stored.
[0031] A method for function recording, the method comprising:
[0032] Receiving a process recording selection corresponding to entering a designated function in a first user terminal;
[0033] The process recording selection trigger is sequentially recorded according to the operation performed in the first user terminal until the first user terminal enters the specified function;
[0034] The operations recorded in sequence are spliced together to obtain an operation step jump execution sequence for entering the specified function, and the operation step jump execution sequence is used to simulate user manipulation on the user terminal so that the user terminal automatically jumps to the specified function.
[0035] A function playback method, the method comprising:
[0036] According to the playback selection corresponding to the target function entry process in the user terminal, an operation step jump execution sequence is obtained;
[0037] Jumping to execute the view element identifiers and the operation mode information corresponding to the view element identifiers sequentially in the sequence according to the operation steps, and sequentially executing the operations indicated by the corresponding operation mode information on the user terminal;
[0038] When the corresponding operations are executed in the jump execution sequence corresponding to the operation steps, the user terminal jumps to the target function.
[0039] A system for realizing an automatic jump entry function, the system comprising:
[0040] An operation recording module is used to record and generate an operation step jump execution sequence of the user's manipulation to enter a specified function according to the operation performed on the first user terminal;
[0041] An execution sequence acquisition module, used for a user terminal to acquire an operation step jump execution sequence corresponding to a target function, the user terminal includes a first user terminal, and the target function includes the specified function;
[0042] an automatic jump execution module, configured to jump to the view element identifiers and the operation mode information corresponding to the view element identifiers in sequence in the execution sequence according to the operation steps, and sequentially execute the operations indicated by the corresponding operation mode information in the user terminal;
[0043] The function entry module is used for simulating user manipulation to jump into the target function when the corresponding operation is executed in the jump execution sequence corresponding to the operation step.
[0044] In an exemplary embodiment, the operation recording module includes:
[0045] A recording selection receiving unit, configured to receive a recording selection corresponding to a process of entering a designated function in a first user terminal;
[0046] a recording execution unit, configured to record the process selection trigger according to the jump of the view element in the first user terminal and the operation performed on the view element, and sequentially record the corresponding view element identifier and the operation mode information corresponding to the view element identifier until the first user terminal enters the specified function;
[0047] The splicing unit is used to splice the sequentially recorded view element identifiers and the operation mode information corresponding to the view element identifiers together to obtain an operation step jump execution sequence for entering the specified function.
[0048] In an exemplary embodiment, the automatic jump execution module includes:
[0049] A parsing unit, configured to parse the jump execution sequence of the operation steps, and detect whether the view element identifiers obtained by sequential parsing have corresponding view elements in the user terminal;
[0050] an element operation unit, configured to operate the view element according to the operation mode information corresponding to the view element identifier if a corresponding view element exists in the user terminal;
[0051] The parsing control unit is used to sequentially parse the next view element identifier in the jump execution sequence of the operation step, and detect the view element and operate the detected view element accordingly.
[0052] In an exemplary embodiment, the automatic jump execution module includes:
[0053] a version detection unit, configured to detect whether the terminal version of the operation step jump execution sequence is the same as that of the user terminal if the view element identifier obtained by the sequential parsing does not have a corresponding view element in the user terminal;
[0054] a sequence conversion unit, configured to convert the view element identifier into a view element update identifier applicable to the user terminal when detecting that the terminal version of the operation step jump execution sequence is different from that of the user terminal;
[0055] The conversion sequence execution unit is used to operate the corresponding view element in the user terminal according to the view element update identifier and the operation mode information corresponding to the view element identifier.
[0056] In an exemplary embodiment, the sequence conversion unit is further used to jump to the mapping of view elements between the terminal version where the execution sequence is located and the user terminal according to the operation steps, convert the view element identifier into a view element identifier corresponding to the mapped view element, and obtain a view element update identifier suitable for the user terminal.
[0057] In an exemplary embodiment, the system further comprises:
[0058] The element mapping module is used to construct and store the mapping relationship between the view element identifier in the published terminal version and the view element identifier in the old terminal version according to the mapping of view elements between the published terminal version and the old version.
[0059] A device for recording functions, comprising:
[0060] A recording initiating module, configured to receive a recording selection corresponding to a process of entering a designated function in a first user terminal;
[0061] A recording execution module, configured to record the process selection trigger according to the operation performed in the first user terminal, and record sequentially until the first user terminal enters the specified function;
[0062] The splicing module is used to splice the operations recorded in sequence together to obtain an operation step jump execution sequence for entering the specified function, and the operation step jump execution sequence is used to simulate user control on the user terminal so that the user terminal automatically jumps to the specified function.
[0063] A function playback device, comprising:
[0064] A playback initiation module, used to obtain an operation step jump execution sequence according to a playback selection corresponding to a target function entry process in a user terminal;
[0065] a jump execution module, configured to jump to the view element identifiers and the operation mode information corresponding to the view element identifiers in sequence in the sequence according to the operation steps, and sequentially execute the operations indicated by the corresponding operation mode information in the user terminal;
[0066] The target function entry module is used to jump the user terminal to the target function when the corresponding operation is executed in the jump execution sequence corresponding to the operation step.
[0067] A machine device, comprising:
[0068] Processor; and
[0069] A memory having computer-readable instructions stored therein, wherein the computer-readable instructions implement the above method when executed by the processor.
[0070] The technical solution provided by the embodiments of the present invention may have the following beneficial effects:
[0071] For a specified function, a first user terminal records and generates an operation step jump execution sequence for the user to enter the specified function according to the operation performed. For any user terminal, the operation step jump execution sequence corresponding to the target function can be obtained. The user terminals include the first user terminal, and the target function includes the specified function. At this time, the view element identifiers and the operation mode information corresponding to the view element identifiers that exist in sequence in the operation step jump execution sequence are recorded in the user terminal, and the user terminal executes the operations indicated by the corresponding operation mode information in sequence. Finally, when all the view elements corresponding to the operation step jump execution sequence execute the corresponding operations, the user terminal jumps to the target function. It can be seen that the guidance of the jump entry to the target function is strongly related to the jump entry to the target function, and does not require manual intervention. The operation cost is extremely low, and delays or even failures in the jump entry to the target function can be avoided. The realization of guiding the user to jump to the required function has a very high controllability.
[0072] It is to be understood that the foregoing general description and the following detailed description are exemplary only and are not restrictive of the invention. BRIEF DESCRIPTION OF THE DRAWINGS
[0073] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the invention and, together with the description, serve to explain the principles of the invention.
[0074] Figure 1 is a simplified diagram of an implementation environment of the present invention according to an exemplary embodiment;
[0075] Figure 2 is a block diagram of a device according to an exemplary embodiment;
[0076] Figure 3 is a flow chart of a method for implementing automatic function jump according to an exemplary embodiment;
[0077] Figure 4 is based on Figure 3 A flowchart describing the details of step 310 is shown in the corresponding embodiment;
[0078] Figure 5 is based on Figure 3 A flowchart describing the details of step 350 is shown in the corresponding embodiment;
[0079] Figure 6 is based on Figure 5 The details of step 350 are described in a flowchart in another exemplary embodiment shown in the corresponding embodiment;
[0080] Figure 7 is a flow chart of a method for function recording according to an exemplary embodiment;
[0081] Figure 8 is a flow chart of a method for function playback according to an exemplary embodiment;
[0082] Fig. 9 is a schematic diagram of an interface for prompting and guiding a new function according to an exemplary embodiment;
[0083] Fig.10 is a schematic diagram of an interface of a function movement prompt according to an exemplary embodiment;
[0084] Fig.11 is a schematic diagram of mode conversion in an application according to an exemplary embodiment;
[0085] Fig.12 is a schematic diagram of a page of the application in recording mode according to an exemplary embodiment;
[0086] Fig.13 is based on Fig.12 A schematic diagram of the page where Maill is located shown in the corresponding embodiment;
[0087] Fig.14 is based on Fig.12 A schematic diagram of a payment page shown in the corresponding embodiment;
[0088] Fig.15 is a schematic diagram showing an implementation of selecting to share after stopping recording according to an exemplary embodiment;
[0089] Fig.16 is based on Fig.13 A playback schematic diagram corresponding to the corresponding embodiment;
[0090] Fig.17 is based on Fig.14 A playback schematic diagram corresponding to the corresponding embodiment;
[0091] Fig.18 is a flowchart of implementing a recording mode and a playback mode in an application according to an exemplary embodiment;
[0092] Fig.19 is a flowchart of creating and updating all ID lists L, deleted ID lists D, and new and old ID mutual mapping tables M according to an exemplary embodiment;
[0093] Fig. 20 is based on Fig.19 The flowchart of converting the server ID shown in the corresponding embodiment;
[0094] Fig.21 is a block diagram of a system for implementing an automatic jump entry function according to an exemplary embodiment;
[0095] Fig. 22 is based on Fig. 20 A block diagram describing the details of the operation recording module shown in the corresponding embodiment;
[0096] Fig.23 is based on Fig. 20 A block diagram describing the details of the automatic jump execution module shown in the corresponding embodiment;
[0097] Fig.24 is based on Fig. 22 A block diagram describing details of an automatic jump module in another embodiment shown in a corresponding embodiment;
[0098] Fig.25 is a block diagram of a function recording device according to an exemplary embodiment;
[0099] Fig.26 The invention is a block diagram of a device for function playback according to an exemplary embodiment. DETAILED DESCRIPTION
[0100] Here, exemplary embodiments will be described in detail, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present invention. Instead, they are merely examples of devices and methods consistent with some aspects of the present invention as detailed in the appended claims.
[0101] Figure 1 FIG. 1 is a schematic diagram of an implementation environment of the present invention according to an exemplary embodiment. In an exemplary embodiment, Figure 1 As shown, the implementation environment involved in the present invention includes a first user terminal 110 and a second user terminal 130 .
[0102] The first user terminal 110 corresponds to the answerer, and the second user terminal 130 corresponds to the questioner. The operation step jump execution sequence is obtained through implementation on the first user terminal 110 and distributed.
[0103] The second user terminal 130 obtains the operation step jump execution sequence distributed by the first user terminal 110, operates various view elements under the action of the operation step jump execution sequence, and then completes the automatic jump entry of the function.
[0104] It should be understood that the second user terminal 130 may also be the first user terminal 110 itself, which is not limited here.
[0105] It should be understood here that the operation step jump execution sequence performed by the first user terminal is performed for one or several applications running on the first user terminal, that is, the operation step recording performed is at the application level or system level. It is possible to record the operations involved in user manipulation in an application running on the first user terminal to obtain the operation step jump execution sequence, and it is also possible to record the operations involved in user manipulation of functions implemented by the cooperation of several applications across applications, which is not limited here.
[0106] Correspondingly, the user terminal simulates the operation performed by the user by jumping the execution sequence through the obtained operation steps, and this operation will also be performed for one or several applications.
[0107] Figure 2 2 is a block diagram of a device according to an exemplary embodiment. For example, the device 200 may be a terminal device in the aforementioned implementation environment. For example, the terminal device may be a smart phone, a tablet computer, a desktop computer, a laptop computer, etc.
[0108] Reference Figure 2 , the device 200 may include one or more of the following components: a processing component 202 , a memory 204 , a power component 206 , a multimedia component 208 , an audio component 210 , a sensor component 214 , and a communication component 216 .
[0109] The processing component 202 generally controls the overall operation of the device 200, such as operations associated with display, phone calls, data communications, camera operations, and recording operations. The processing component 202 may include one or more processors 218 to execute instructions to complete all or part of the steps of the method described below. In addition, the processing component 202 may include one or more modules to facilitate the interaction between the processing component 202 and other components. For example, the processing component 202 may include a multimedia module to facilitate the interaction between the multimedia component 208 and the processing component 202.
[0110] The memory 204 is configured to store various types of data to support operations on the device 200. Examples of such data include instructions for any application or method operating on the device 200. The memory 204 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable red-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk. The memory 204 also stores one or more modules, which are configured to be executed by the one or more processors 218 to complete the following: Figure 3 , Figure 4 , Figure 5 , Figure 6 , Figure 7 and Figure 8 All or part of the steps in any of the methods shown.
[0111] The power supply component 206 provides power to the various components of the device 200. The power supply component 206 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power for the device 200.
[0112] The multimedia component 208 includes a screen that provides an output interface between the device 200 and the user. In some embodiments, the screen may include a liquid crystal display (LCD) and a touch panel. If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touch, slide, and gestures on the touch panel. The touch sensor may not only sense the boundaries of a touch or slide action, but also detect the duration and pressure associated with the touch or slide operation. The screen may also include an organic light emitting display (OLED).
[0113] The audio component 210 is configured to output and / or input audio signals. For example, the audio component 210 includes a microphone (MIC), which is configured to receive external audio signals when the device 200 is in an operation mode, such as a call mode, a recording mode, and a speech recognition mode. The received audio signal can be further stored in the memory 204 or sent via the communication component 216. In some embodiments, the audio component 210 also includes a speaker for outputting audio signals.
[0114] The sensor assembly 214 includes one or more sensors for providing various aspects of status evaluation for the device 200. For example, the sensor assembly 214 can detect the open / closed state of the device 200, the relative positioning of the components, and the sensor assembly 214 can also detect the position change of the device 200 or a component of the device 200 and the temperature change of the device 200. In some embodiments, the sensor assembly 214 can also include a magnetic sensor, a pressure sensor or a temperature sensor.
[0115] The communication component 216 is configured to facilitate wired or wireless communication between the device 200 and other devices. The device 200 can access a wireless network based on a communication standard, such as WiFi (WIreless-Fidelity). In an exemplary embodiment, the communication component 216 receives a broadcast signal or broadcast-related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component 216 also includes a near field communication (NFC) module to facilitate short-range communication. For example, the NFC module can be based on Radio Frequency Identification (RFID) technology, Infrared Data Association (IrDA) technology, Ultra Wideband (UWB) technology, Bluetooth technology and other technologies.
[0116] In an exemplary embodiment, the device 200 can be implemented by one or more application-specific integrated circuits (ASICs), digital signal processors, digital signal processing devices, programmable logic devices, field programmable gate arrays, controllers, microcontrollers, microprocessors or other electronic components to perform the following method.
[0117] Figure 3FIG. 1 is a flow chart of a method for implementing automatic function jump according to an exemplary embodiment. The method for implementing automatic function jump is applicable to the implementation environment shown above. Figure 3 As shown, the method for implementing the automatic jump of the function includes at least the following steps.
[0118] In step 310, the first user terminal records and generates a jump execution sequence of operation steps for the user to enter a designated function according to the executed operation.
[0119] The first user terminal can be the form in which the application exists in any terminal device, that is, the application exists in the form of a user terminal in the terminal device, and the first user terminal is any user terminal. The operation performed on the first user terminal is a user operation triggered under user control, and each operation performed corresponds to an operation step. Therefore, recording this can generate an operation step jump execution sequence for the user to enter the specified function.
[0120] The operation performed on the first user terminal is performed under user control and is therefore directed to one or several applications related to a specified function. The execution of this operation involves the triggering and jumping of view elements on one or several applications.
[0121] View elements exist in the user terminal and are a series of elements in the user terminal interface that enable user interaction. No matter which interface the user terminal jumps to during operation, there are often view elements in this interface. View elements can be various buttons, drag components, function icons, etc.
[0122] Any view element will perform this operation by operating this view element. Bind the manipulation process on the view element. For example, initiate a jump to the interface. The operation refers to the operation on the view element, which is related to the type of view element. For example, the operation may include a click operation, a long press operation, a left slide operation, a right slide operation, etc.
[0123] In the operation of the first user terminal by the user, in order to jump into the designated function, a series of jumps between view elements will be performed, and the process of operating the view elements is accompanied. Correspondingly, in the process of the user operating the view elements in the first user terminal and then jumping into the designated function, the jump of the view elements is recorded, and the operation performed on the recorded view elements is recorded for the recorded view elements until the designated function is jumped into, and the jump execution sequence of the operation steps leading to the designated function in the user terminal is obtained.
[0124] It can be seen that the obtained operation step jump execution sequence corresponds to the operation path of jumping into the specified function. According to the performed view element jump and the performed operation view element, the operation step jump execution sequence generated by the record records the view elements according to the jump order between the view elements, and records the operation for the recorded view elements.
[0125] In an exemplary embodiment, the view element record is implemented through the view element identifier, and the operation record is implemented through the corresponding operation mode information. Thus, a jump execution sequence of operation steps formed by several groups of view element identifiers and operation mode information is obtained, and each group of view element identifiers and operation mode information corresponds to an operation step and will be used for the automatic execution of this operation step.
[0126] In an exemplary embodiment, the view element identifier is globally unique in the application, thereby facilitating the recording of view elements related to any page in the application. In addition, the view element identifier can also be composed of a tuple such as a page identifier and an element identifier relative to this page to uniquely identify a view element. The tuple method will help avoid identifier conflicts while implementing functional guidance.
[0127] It should be supplemented that the jump between view elements is based on the jump of the page. The operation of the view element causes the first user terminal to jump from the current page to the next page, and the operation performed is located on a view element on the next page. For the operation sequence to achieve the specified function, the page jump is actually focused on the jump of the view element. By executing the operation, it switches to a different view element, and finally achieves the specified function.
[0128] It should be understood that the first user terminal operates the view element for the specified function, thereby realizing the view element jump. After the view element jumps and the view element to which the jump is made is operated, the specified function is jumped to. The record of this process is essentially the recording of the specified function guidance, which records each operation step performed so as to provide it to the user terminal that needs to jump to this specified function.
[0129] The recording of the designated function guidance implemented in this exemplary embodiment ensures the accuracy and completeness of the function guidance through the recording process performed. In addition, it is also strongly related to the execution of the function jump entry, that is, under the control process corresponding to the operation step jump execution sequence, the user terminal that obtains the operation step jump execution sequence can automatically jump to the designated function.
[0130] In step 330, the user terminal obtains an operation step jump execution sequence corresponding to a target function, the user terminal includes a first user terminal, and the target function includes a designated function.
[0131] The user terminal may be the first user terminal or another user terminal different from the first user terminal. The target function is any function deployed by the user terminal, including the designated function mentioned above and other functions different from the designated function, which are not limited here.
[0132] The recorded function guide is obtained through the operation step jump execution sequence generated in the aforementioned step 310. Specifically, on the one hand, when the user terminal referred to in step 330 is the first user terminal, the operation step jump execution sequence obtained will automatically and quickly jump to the specified function; on the other hand, when the user terminal referred to in step 330 is different from the first user terminal, the operation step jump execution sequence issued by the first user terminal to the user terminal enables the user terminal to obtain the operation step jump execution sequence.
[0133] In an exemplary embodiment, the operation step jump execution sequence is stored in the form of a message or barcode information such as a QR code, and the user terminal obtains the carried operation step jump execution sequence through the obtained message or barcode information.
[0134] The first user terminal and the user terminal are relative in different scenarios. That is, the user terminal corresponds to the questioner who asks how to enter the target function, and the first user terminal corresponds to the answerer who answers how to enter the target function. At this time, although the first user terminal is different from the user terminal, the target function is the designated function referred to above.
[0135] In step 350, the view element identifiers and the operation mode information corresponding to the view element identifiers are sequentially present in the execution sequence according to the operation step jump, and the operations indicated by the corresponding operation mode information are sequentially executed on the user terminal.
[0136] As mentioned above, the sequentially existing view element identifiers constitute a group with the corresponding operation mode information, and so on, several groups of view element identifiers and operation mode information form an operation step jump execution sequence.
[0137] Corresponding to the record made by the first user terminal, the operation step jump execution sequence obtained by the user terminal to enter the target function records the operation steps that need to be executed sequentially to simulate user manipulation. This operation step has a view element identifier corresponding to the view element that needs to be triggered and the operation that needs to be triggered on this view element, that is, indicated by the operation mode information. The target function can be entered by sequentially executing the operation steps indicated by the operation step jump execution sequence.
[0138] In a specific implementation of an exemplary embodiment, for several groups of view element identifiers and operation mode information that exist sequentially in the operation step execution sequence, they are searched on the user terminal in turn to locate the view element of the user terminal, and the located view element is operated according to the operation mode information, and so on, to complete the execution of operations on all view element identifiers.
[0139] In an exemplary embodiment, the operation step jump execution sequence is in the form of a network address (Uniform ResoureLocator, referred to as URL), and then the data interaction between the first user terminal and the user terminal is realized through the form of the network address.
[0140] The operation steps in the form of network addresses jump to the execution sequence, and the slash " / " is used to connect the groups, that is, the string consisting of the view element identifier and the operation mode information is connected with " / ".
[0141] Furthermore, the network address corresponding to the operation step jump execution sequence also carries the supported protocol characters and version number, so as to accurately and reliably implement the function jump entry in the user terminal.
[0142] For example, the network address corresponding to the operation step jump execution sequence is: mqq: / / steprecord / v621 / profile.click / setting.longclick / more.leftslide.
[0143] Among them, mqq is the supported protocol character, v621 indicates that the supported terminal version is 6.2.1, profile, setting and more are view element identifiers for sequential jumps, click is a click operation applied to the view element identified by the view element identifier of profile, longclick is a long press operation applied to the view element identified by the view element identifier of setting, and leftslide is a left slide operation applied to the view element identified by more.
[0144] That is, a set of character strings formed by the view element identifier and the operation mode information is in the form of id.op, where id is the view element identifier and op is the operation mode information.
[0145] In step 370, when all view elements corresponding to the operation step jump execution sequence have executed the corresponding operations, the user terminal simulates user manipulation to jump into the target function.
[0146] Among them, after the user terminal realizes the corresponding jump through the operation corresponding to the recorded operation mode information, all the operation steps for entering the target function are executed, and the user terminal automatically jumps to the target function under the action of the acquired operation step jump execution sequence. After the user of the user terminal obtains the guidance required to enter the target function, that is, the operation step jump execution sequence, it is no longer necessary to manually follow each operation step step by step, and it is no longer necessary, which also avoids the situation where both the questioner and the answerer are time-consuming and laborious.
[0147] Through the exemplary embodiments described above, the recording and playback of the process of entering a specified function is implemented for the user terminal, so that the user terminal's guidance of the function is strongly related to the actual function entry process, for example, how to find the entrance to a certain function, and automated control is implemented for this purpose, which will help to enhance the usage threshold and ease of use of the user terminal.
[0148] Figure 4 is based on Figure 3 The flowchart of the corresponding embodiment shows the details of step 310. In an exemplary embodiment, as Figure 4 As shown, step 310 includes at least the following steps.
[0149] In step 311, a process recording selection corresponding to entering a designated function is received in a first user terminal.
[0150] The recording of the process of entering the designated function is to record the page jump that occurs when the first user terminal is controlled to enter the designated function, as well as the view elements operated in the page.
[0151] The process recording selection is initiated in the first user terminal as the user operates. In an exemplary embodiment, a "start recording" button is configured on the interface of the first user terminal. The user clicks the "start recording" button to initiate the process recording selection. The first user terminal that receives the process recording selection will enter the recording of the specified function as the user operates.
[0152] It should be noted here that the recorded designated function is the function performed by the user operating the first user terminal after the recording starts, and it can correspond to any function of the first user terminal according to the user's operation.
[0153] In step 313, the process recording selection trigger is based on the progress of the view element jump in the first user terminal and the operation performed on the view element, and the corresponding view element identifier and the operation mode information of the corresponding view element identifier are sequentially recorded until the first user terminal enters the specified function.
[0154] Among them, with the reception of the selection of entering the designated function process recording, the operation and the view element affected by the operation will be recorded. Specifically, after receiving the selection of entering the designated function process recording, the corresponding view element identification and operation mode information of the view element first operated by the user are recorded, and the corresponding view element identification and operation mode information of the view element operated subsequently are continuously recorded until jumping to the designated function entrance, at which time the continuous recording can be ended to realize the process recording of how to enter the designated function entrance.
[0155] Of course, it should be understood that the first user terminal referred to as entering the designated function may be the entrance to the designated function or the implementation of the designated function, which is not limited here and will be determined according to the actual corresponding designated function.
[0156] As mentioned above, the recording of the jumped view elements and operations is achieved by recording the view element identifiers and operation mode information. For each operation step, there is a view element that implements the operation and function corresponding to this operation step. Therefore, the recorded view element identifiers and operation mode information also correspond to the operation steps.
[0157] In step 315, the sequentially recorded view element identifiers and the operation mode information corresponding to the view element identifiers are spliced together to obtain an operation step jump execution sequence for entering a designated function.
[0158] Among them, as mentioned above, several groups of view element identifiers and operation mode information are obtained corresponding to the operation step records. At this time, according to the jump order between view elements, or the order corresponding to the operations, each group of view element identifiers and operation mode information are spliced together to obtain the operation step jump execution sequence.
[0159] In an exemplary embodiment, each set of view element identification and operation mode information in the operation step jump execution sequence exists in the form of a character string, so the operation step jump execution sequence is a character string sequence.
[0160] In other words, the execution and control of each operation step is realized in the form of a string, and the parsability and explainability are enhanced.
[0161] It can be understood that the operation step jump execution sequence corresponds to two sequences, one is the view element sequence, which corresponds to the view elements that are sequentially jumped, and the other is the operation sequence, which corresponds to the operations that are sequentially executed. The two sequences are combined to accurately locate the operated view elements and the operations applied, thereby ensuring the controllability of the operation step jump execution for the automatic jump entry of the function.
[0162] Figure 5 is based on Figure 3 The flowchart of the corresponding embodiment shows the details of step 350. The step 350, such as Figure 5 As shown, at least the following steps are included.
[0163] In step 351, the operation step jump execution sequence is parsed to detect whether the view element identifiers obtained by sequential parsing have corresponding view elements in the user terminal.
[0164] Among them, as mentioned above, the operation step jump execution sequence indicates the operation corresponding to each operation step and the view element acted upon by this operation through each group of view element identifiers and operation mode information. It is necessary to parse this operation step jump execution sequence to obtain the operation that needs to be performed and the view element acted upon for each operation step.
[0165] Therefore, the operation step jump execution sequence is parsed, and for each set of view element identification and operation mode information obtained by the analysis, a detection is performed to determine whether the corresponding view element exists in the running user terminal, so as to accurately locate the view element that needs to be triggered under the current corresponding operation step, and then the operation can be accurately triggered according to the operation mode information, and the corresponding operation step can be accurately executed.
[0166] Specifically, the parsing of the operation step jump execution sequence is a process of parsing each group of view element identifiers and operation mode information one by one according to the first and last order of the characters in the sequence. In this process, as each group of view element identifiers and operation mode information is obtained through parsing, a detection is performed on whether a corresponding view element exists in the running user terminal for this view element identifier.
[0167] It should be understood that for the user terminal, no matter what form the view element identifier exists in, it uniquely identifies the corresponding view element. Therefore, in an exemplary embodiment, whether the user terminal has a view element corresponding to the parsed view element identifier is to determine whether there is a view element whose view element identifier is consistent with the parsed view element identifier among the many view elements existing in the user terminal. The view element that is consistent with the parsed view element identifier is the view element that the user terminal needs to operate under the current operation step.
[0168] In step 353, if the view element identifier obtained by sequential parsing has a corresponding view element in the user terminal, the view element is operated according to the operation mode information corresponding to the view element identifier.
[0169] Among them, for the view element identifier currently parsed, the view element corresponding to this view element identifier is located by detecting the corresponding view element in the user terminal, so that the located view element can be operated according to the operation mode information corresponding to this view element identifier.
[0170] In step 355, the sequential parsing operation step jumps to the next view element identifier in the execution sequence, and accordingly performs view element detection and operates the detected view element.
[0171] Among them, as mentioned above, a set of view element identifiers and operation mode information are obtained by sequentially parsing the operation step jump execution sequence. After completing the operation of the corresponding view element, the sequential parsing of the operation step jump execution sequence is continued to obtain the next set of view element identifiers and operation mode information, and then the operation of the view element in the user terminal is continued.
[0172] This process is repeated in this way until the sequential parsing of the operation step jump execution sequence is completed and all view element identifiers and operation mode information have been parsed out.
[0173] Through this exemplary embodiment, effective control is achieved for the automatic jump entry of the function implemented in the user terminal for the operation step jump execution sequence, while ensuring the controllability and reliability of the execution, it also ensures the accuracy of the user terminal's automatic execution of the specified operation steps.
[0174] Figure 6 is based on Figure 5 The details of step 350 are described in another exemplary embodiment. In another exemplary embodiment, Figure 6 As shown, step 350 also includes the following steps.
[0175] In step 357, if the view element identifier obtained by sequential parsing does not have a corresponding view element in the user terminal, it is detected that the terminal version of the jump execution sequence of the operation step is the same as the user terminal.
[0176] Among them, Figure 5 In the corresponding embodiment, through the execution of step 351, it is confirmed that the view element identifier obtained by parsing the current sequence does not have a corresponding view element in the user terminal, that is, for the operation step, the user terminal does not have a view element that can be operated by the current operation step. Here, it is explained that the operation step jump execution sequence is not applicable to the user terminal, and this needs to be processed to ensure the successful jump entry of the target function in the user terminal.
[0177] In the case where the parsed view element identifier does not correspond to the user terminal, the first user terminal that generates the operation step jump execution sequence is not the currently running user terminal, so there is version incompatibility and the operation step jump execution sequence needs to be processed.
[0178] Specifically, the terminal version where the execution sequence is jumped according to the operation steps is checked for version consistency with the user terminal to confirm whether the two are user terminals of the same version.
[0179] As mentioned above, the operation step jump execution sequence carries the terminal version, that is, the version number. At this time, the version number will be parsed from the operation step jump execution sequence, and accordingly, the version number of the user terminal will also be obtained. By comparing the two, it can be detected whether the terminal version where the operation step jump execution sequence is located is consistent with the user terminal.
[0180] In step 358, when the terminal version where the jump execution sequence of the detection operation step is located is different from the user terminal, the view element identifier is converted into a view element update identifier suitable for the user terminal.
[0181] Among them, if it is detected that the terminal version of the operation step jump execution sequence is inconsistent with the user terminal, it is necessary to convert the operation step jump execution sequence. It should be understood that in the case of inconsistent versions, the inapplicability of the operation step jump execution sequence to the user terminal is reflected in the inability to find the corresponding view element in the user terminal, that is, as the version iteration proceeds, the view elements of each page in the interface may have changed, for example, the view element has been deleted, added or renamed. At this time, the changed view element corresponds to the view element identifier in the operation step jump execution sequence, so the view element identifier needs to be converted.
[0182] By converting the view element identifier, the view element identifier that is not applicable to the running user terminal in the operation step jump execution sequence is converted into a view element identifier that is applicable to the running user terminal, that is, a view element update identifier relative to the original view element identifier.
[0183] In an exemplary embodiment, converting a view element identifier into a view element update identifier suitable for a user terminal includes: performing a mapping of view elements between a terminal version where an execution sequence is located and a user terminal according to an operation step, converting the view element identifier into a view element identifier corresponding to the mapped view element, and obtaining a view element update identifier suitable for the user terminal.
[0184] It should be understood that the version iterations have resulted in differences in view elements between user terminals of different versions, such as changes such as deletion, addition, and modification of view elements. Correspondingly, the differences in view elements between versions are mapped to view element identifiers between different versions, i.e., changes such as deletion, addition, and renaming of view element identifiers. Regardless of the changes, for view element identifiers stored in different versions, the renaming will result in a mapping relationship between view elements of different versions, i.e., due to the change of view elements, the corresponding view element identifiers are changed, thereby generating a mapping relationship. At this time, the view element identifier conversion can be realized according to this mapping relationship.
[0185] In step 359, the view element identifiers and the operation mode information corresponding to the view element identifiers that exist sequentially in the execution conversion sequence are jumped according to the operation steps, and the corresponding view elements are operated on the user terminal.
[0186] Among them, after the view element update identifier is converted, the corresponding view element is found in the running user terminal, so that the operation can be performed according to the operation mode information, the found view element is operated, and then the operation steps of the originally recorded view element identifier that is not applicable to the current version are completed on the user terminal.
[0187] Through this exemplary embodiment, automatic jump entry to the target function is achieved in different versions. The achieved automatic jump entry to the target function has very strong versatility and version compatibility, and will not be affected by version iterations or different versions used by users.
[0188] After the conversion of the view element identifier obtained by the current analysis is completed, if the analysis has not yet ended, the operation step of jumping the execution sequence is continued, that is, 355 is executed.
[0189] In an exemplary embodiment, before step 350, the method for implementing the automatic jump of the function further includes:
[0190] According to the mapping of view elements between the published terminal version and the old version, a mapping relationship between the view element identifier in the published terminal version and the view element identifier in the old terminal version is constructed and stored.
[0191] Among them, as mentioned above, the view elements between different versions of user terminals differ. When the view elements are changed, that is, the view elements of the old terminal version are transformed on the user terminal of the released terminal version, but still correspond to the same operation and execution logic. At this time, a mapping relationship between the two will be constructed and stored.
[0192] The changes in view elements between the two terminal versions, including changes in view element styles, are still used to implement the same operation steps. Therefore, a mapping relationship can be constructed for this, and the data foundation and basis for the identification conversion of the subsequently generated operation step jump execution sequence can be provided.
[0193] In a specific implementation of an exemplary embodiment, the mapping relationship between the view element identifier in the released terminal version and the view element identifier in the old terminal version is constructed, including:
[0194] (1) For each terminal version release, all identification lists L are initialized, the deleted identification list D, and the new and old identification mutual mapping table M are empty.
[0195] Among them, the list of all identifiers L is configured to record all view element identifiers of the released terminal version; the deleted identifier list D is configured to record the view element identifiers corresponding to the view elements deleted relative to the old terminal version; the new and old identifier mutual mapping table M is configured to record the view element identifiers corresponding to the view elements that have been changed relative to the old terminal version.
[0196] (2) When the first version is released, all view element identifiers are added to the list of all identifiers L.
[0197] (3) For the iteration from the old terminal version to the released terminal version, the view element identifier will be processed according to the following three situations, specifically:
[0198] When a view element of an old terminal version is deleted relative to the published terminal version, the corresponding view element identifier is deleted from the list of all identifiers L and added to the list of deleted identifiers D;
[0199] If the released terminal version adds a new view element relative to the old terminal version, the corresponding view element identifier is added to the list of all identifiers L, and the newly added view element identifier cannot be the same as the view element identifier existing in the deleted identifier list D;
[0200] When a view element identifier is renamed, that is, from id to id', id is deleted from all identifier lists L and added to the deleted identifier list D. Id' is added to all identifier lists L, and id' is different from id. A corresponding mapping item is established in the new and old identifier mapping table M, that is, a bidirectional mapping relationship of id.v1<->id'.v2, to indicate the view elements that are mapped between version V1 and version V2.
[0201] At this point, when the view element identifier needs to be converted, the existing mapping item is obtained in the new and old identifier mutual mapping table M according to the terminal version of the parsed view element identifier, the terminal version of the running user terminal, and the view element identifier itself, and the conversion is performed according to the mapping of the view element identifier in this mapping item.
[0202] With the continuous version iteration, the identification list L, the deleted identification list D, and the new and old identification mapping table M are also constantly updated to ensure the accuracy of the stored identifications, thereby ensuring the smooth implementation of automatic function jump entry in different user terminals.
[0203] Figure 7 FIG. 1 is a flow chart of a method for recording a function according to an exemplary embodiment. In an exemplary embodiment, Figure 7 As shown, the method for recording the function includes at least the following steps:
[0204] In step 510, a process recording selection corresponding to entering a designated function is received in a first user terminal.
[0205] In step 530, the process recording selection trigger is recorded sequentially according to the operation performed in the first user terminal until the first user terminal enters the designated function.
[0206] In step 550, the operations recorded in sequence are spliced together to obtain an operation step jump execution sequence for entering a specified function. The operation step jump execution sequence is used to simulate user manipulation on the user terminal so that the user terminal automatically jumps to the specified function.
[0207] Through this exemplary embodiment, the operation process of entering a specified function is recorded for the user terminal. The recorded content is not static text content, nor dynamic video content, but step-by-step operations related to entering the specified function, for example, the operations performed and the content related to the operated view elements, which will be played back later by reading this content.
[0208] Of course, correspondingly, the playback referred to is not the static text content playback, nor the dynamic video content playback, but is strongly related to the actual control to enter the specified function, that is, through the playback, the operation is executed step by step, the operation steps involved in the operation playback, and then the user terminal is controlled to enter the specified function.
[0209] Figure 8 FIG. 1 is a flow chart of a method for function playback according to an exemplary embodiment. In an exemplary embodiment, Figure 8 As shown, the method for function playback includes at least the following steps.
[0210] In step 710, an operation step jump execution sequence is obtained according to the playback selection corresponding to the target function entry process in the user terminal.
[0211] In step 730, the view element identifiers and the operation mode information corresponding to the view element identifiers are sequentially executed in the sequence according to the operation step jump, and the operations indicated by the corresponding operation mode information are sequentially executed on the user terminal.
[0212] In step 750, when the corresponding operations are executed in the jump execution sequence corresponding to the operation steps, the user terminal jumps to the target function.
[0213] Under this exemplary effect, the user only needs to obtain the jump execution sequence of the operation steps of the target function, and the user terminal can automatically jump to the target function under the control of this operation step jump execution sequence, so that the function guidance performed is not virtual, but truly implemented in the control of the user terminal.
[0214] Taking an application as an example, the process implemented by the above exemplary embodiment is described in combination with this application. Here, the first user terminal and the user terminal are both this application.
[0215] In an app, when a user opens an installed app for the first time, or when a function is moved to another location in the app, guidance about the new function or the modified location is provided. Specifically, Fig. 9 8 is a schematic diagram of an interface for prompting and guiding a new function according to an exemplary embodiment. In this interface, a prompt message 810 is used to implement a prompt for a new function.
[0216] Fig.10 8 is a schematic diagram of an interface for showing a function moving prompt according to an exemplary embodiment. In the interface, the content shown on page 830 is used to guide the function whose position is modified.
[0217] For users and subsequent access to this function, the prompts are relatively weak. Specifically, users do not pay attention to these prompts at all, and still cannot find the entrance to this function when they want to use it. If you ask others for help, the other party needs to operate on the application, and then tell you the operation steps through text or video messages, and ask questions and perform them manually again, which is time-consuming and laborious for both parties.
[0218] Furthermore, if the operation steps are answers obtained in a chat application, it is necessary to switch back and forth between the chat application and this application to ensure that the operation is correct.
[0219] What is even more troublesome is that when the answerer's description of a certain step is different from the questioner's understanding, this process needs to be confirmed back and forth between the questioner and the answerer. In particular, when the questioner and the answerer are using different versions of the application, the page where the same function is located may be completely different, resulting in the questioner not being able to get the answer they want.
[0220] Through the implementation of the present invention, the network address is used to accurately describe how to locate any function in the application, and the user can directly obtain the required function through the network address without any ambiguity. The network address mentioned here is the existence form of the aforementioned operation step jump execution sequence.
[0221] The network address can be shared by other users or recorded by the user himself during the operation of the application. The network address is a pure string or converted into a QR code for easy dissemination among users.
[0222] Fig.11 1 is a schematic diagram of mode conversion in an application according to an exemplary embodiment. In the application, the normal use state is the normal mode. After clicking the "Start Recording" button resident in the application interface, it enters the recording mode. Clicking the "Stop Recording" button in the recording mode returns to the normal mode.
[0223] In normal mode, you can enter playback mode by clicking on the network address, and return to normal mode after playback ends.
[0224] At this point, the conversion between normal, recording and playback modes is realized.
[0225] The following is a detailed description of the recording mode and playback mode.
[0226] (1) Recording mode;
[0227] In recording mode, users can still use the application normally, but all operations will be recorded.
[0228] Fig.12 FIG. 1 is a schematic diagram of a page of the application in recording mode according to an exemplary embodiment. Fig.12 In the page shown, by clicking the "Start Recording" button 850, the recording mode is entered. Fig.12 After clicking the "Mail" tab on the page shown, you will be redirected to the page where Maill is located. Fig.13 shown. Fig.13 is based on Fig.12 A schematic diagram of the page where Maill is located shown in the corresponding embodiment.
[0229] Fig.14 is based on Fig.12 The payment page diagram shown in the corresponding embodiment. Fig.12 After clicking the "Pay" tab in the interface shown, switch to Fig.14 The payment page shown.
[0230] regardless Fig.13 ,still Fig.14 The page shown has a "Stop Recording" button 870 in the upper right corner. Clicking the button ends the recording and a network address is generated. The network address can be shared with other users via QR code, clipboard, etc. It can also be shared to other third-party applications, such as social applications.
[0231] Fig.15 This is a schematic diagram of implementing the selection of sharing after stopping recording according to an exemplary embodiment. After the network address is generated by stopping recording, the network address can be shared by selecting a sharing method.
[0232] Through sharing, the user himself or other users can obtain the network address, and then enter the playback mode by clicking on the network address.
[0233] (2) Playback mode;
[0234] Fig.16 is based on Fig.13 A playback schematic diagram corresponding to the corresponding embodiment; Fig.17 is based on Fig.14 A playback schematic diagram corresponding to the corresponding embodiment.
[0235] After the user opens the above network address in the application, the application will enter the playback mode and automatically complete all the operation steps indicated by the network address. In the playback mode, the user cannot operate the application, and a prompt 910 of "playing back" is displayed in the upper right corner.
[0236] It should be understood that the aforementioned implementation of opening the network address may be by scanning a QR code, reading text from a clipboard, or inputting a network address.
[0237] Further explanation, for the implementation of the recording mode in this application, such as Fig.19 The left process of the flowchart shown. Fig.18 The present invention is a flowchart of implementing a recording mode and a playback mode in an application according to an exemplary embodiment.
[0238] like Fig.18 As shown, use this application (App) normally, it is in normal mode at this time, click the "Start Recording" button and jump to step 1010.
[0239] In step 1010, the recording mode is entered, and the network address is initialized to scheme: / / host / version, where scheme and host are specified by the application itself, scheme indicates the protocol supported by the application, and version is the version number of the application during recording.
[0240] In the repeated execution of step 1030 to step 1050, the user uses the application normally. When the user operates a view element identified as id, a string " / id.op" is concatenated after the network address, where op refers to the operation mode information.
[0241] If the user clicks the "Stop Recording" button, the process proceeds to step 1090. At this point, a dialog box will pop up to inform the user that the user can share the steps just recorded via a QR code, clipboard, or third-party application. After the user selects a sharing method, the application returns to normal mode.
[0242] like Fig.18 The right process of the flowchart shown is to play back the application through the shared URL, that is, the network address.
[0243] Still starting with the user using the application normally, after opening a recorded URL, the process goes to step 1110, that is, parsing to obtain the version number Va of the App and the version number Vu corresponding to the URL, and then removing the scheme: / / host / version in front of the URL.
[0244] Execute all the operation steps between the " / " in the rest of the URL string in sequence. For example, "mqq: / / steprecord / profile.click / setting.longclick / more.leftslide" means "click profile->long press setting->slide left more" in sequence. After the playback is successful, it returns to the normal mode.
[0245] If a certain view element cannot be found in the application during playback, if Va and Vu are the same, execute step 1150, otherwise proceed to step 1170.
[0246] During the execution of step 1150, the App sends the URL and its own version number to the server. If the operation steps of the URL can be converted to the current version, the server returns the converted characters. At this time, the operation steps can still be executed intermittently.
[0247] The conversion performed by the server is realized through the obtained new and old id mutual mapping table M under the action of all id lists L and deleted id lists D. According to the uploaded App version number and URL version number, the corresponding mapping item is found in the new and old id mutual mapping table M, and the id conversion can be performed according to the mapping item.
[0248] Fig.19 It is a flowchart of creating and updating all ID lists L, deleted ID lists D and new and old ID mutual mapping tables M according to an exemplary embodiment.
[0249] Specifically, through the initial state shown in step 1210, the construction of all id lists L released in the first version in step 1230, and the implementation of steps 1270 to 1290 in the version iteration update, the creation and update of all id lists L, deleted id lists D and new and old id mapping tables M are completed.
[0250] At this point, you can Fig. 20 The process shown implements the conversion. Fig. 20 is based on Fig.19 The flowchart of converting the server ID is shown in the corresponding embodiment.
[0251] It should be understood that after an id is parsed from the URL, if it exists in L, no conversion is required even if the versions are different, as shown in steps 1310 to 1360.
[0252] However, if id does not exist in L, it is necessary to search for the corresponding mapping entry in M, as shown in step 1370, and then perform the conversion according to the found mapping entry.
[0253] Through this implementation, the effects of similar inquiries and responses to "Where is the xx function" scenarios will be greatly improved, saving time and having very high timeliness.
[0254] The following is an embodiment of the device of the present invention, which can be used to execute the above method embodiment of the present invention. For details not disclosed in the embodiment of the device of the present invention, please refer to the method embodiment of the present invention.
[0255] Fig.21 is a block diagram of a system for implementing an automatic jump entry function according to an exemplary embodiment. The system for implementing the automatic jump entry function, such as Fig.21 As shown, it at least includes but is not limited to: an operation recording module 1510, an execution sequence acquisition module 1530, an automatic jump execution module 1550 and a function entry module 1570.
[0256] An operation recording module 1510 is used to record and generate an operation step jump execution sequence of a user's manipulation to enter a specified function according to the operation performed at the first user terminal;
[0257] An execution sequence acquisition module 1530, configured for a user terminal to acquire an operation step jump execution sequence corresponding to a target function, wherein the user terminal includes a first user terminal, and the target function includes the specified function;
[0258] An automatic jump execution module 1550 is used to jump to the view element identifiers and the operation mode information corresponding to the view element identifiers in sequence in the sequence according to the operation steps, and sequentially execute the operations indicated by the corresponding operation mode information in the user terminal;
[0259] The function entry module 1570 is used for simulating user manipulation to jump into the target function when all view elements corresponding to the operation step jump execution sequence have executed the corresponding operation.
[0260] Fig. 22 is based on Fig.21 The block diagram of the corresponding embodiment shows the details of the operation recording module. In an exemplary embodiment, as Fig. 22 As shown, the operation recording module 1510 at least includes but is not limited to: a recording selection receiving unit 1511, a recording execution unit 1513 and a splicing unit 1515.
[0261] The recording selection receiving unit 1511 is used to receive a recording selection corresponding to a process of entering a specified function in the first user terminal;
[0262] The recording execution unit 1513 is configured to record the process selection trigger according to the jump of the view element in the first user terminal and the operation performed on the view element, and sequentially record the corresponding view element identifier and the operation mode information corresponding to the view element identifier until the first user terminal enters the specified function;
[0263] The splicing unit 1515 is used to splice the sequentially recorded view element identifiers and the operation mode information corresponding to the view element identifiers together to obtain an operation step jump execution sequence for entering the specified function.
[0264] Fig.23 is based on Fig.21 The block diagram of the corresponding embodiment shows the details of the automatic jump execution module. In an exemplary embodiment, as Fig.23 As shown, the automatic jump execution module 1550 at least includes: a parsing unit 1551, an element operation unit 1553 and a parsing control unit 1555.
[0265] A parsing unit 1551 is used to parse the jump execution sequence of the operation steps, and detect whether the view element identifiers obtained by sequential parsing have corresponding view elements in the user terminal;
[0266] An element operation unit 1553 is configured to operate the view element according to the operation mode information corresponding to the view element identifier if a corresponding view element exists in the user terminal.
[0267] The parsing control unit 1555 is used to sequentially parse the next view element identifier in the operation step jump execution sequence, and detect the view element and operate the detected view element accordingly.
[0268] Fig.24 is based on Fig.21 The block diagram of the automatic jump module in another embodiment is described in detail in the corresponding embodiment. In an exemplary embodiment, Fig.24 As shown, the automatic jump execution module 1550 further includes: a version detection unit 1556 , a sequence conversion unit 1557 and a conversion sequence execution unit 1558 .
[0269] A version detection unit 1556 is configured to detect whether the terminal version of the operation step jump execution sequence is the same as that of the user terminal if the view element identifier obtained by the sequential parsing does not have a corresponding view element in the user terminal;
[0270] A sequence conversion unit 1557, configured to convert the view element identifier into a view element update identifier applicable to the user terminal when detecting that the terminal version of the operation step jump execution sequence is different from that of the user terminal;
[0271] The conversion sequence execution unit 1558 is used to operate the corresponding view element in the user terminal according to the view element update identifier and the operation mode information corresponding to the view element identifier.
[0272] In another exemplary embodiment, the sequence conversion unit 1557 is further used to jump to the mapping of view elements between the terminal version where the execution sequence is located and the user terminal according to the operation steps, convert the view element identifier into a view element identifier corresponding to the mapped view element, and obtain a view element update identifier suitable for the user terminal.
[0273] In another exemplary embodiment, the system for implementing the automatic jump entry function further includes: an element mapping module. The element mapping module is used to construct and store a mapping relationship between a view element identifier in the published terminal version and a view element identifier in the old terminal version according to the mapping of view elements between the published terminal version and the old version.
[0274] Fig.25 is a block diagram of a function recording device according to an exemplary embodiment. In an exemplary embodiment, the function recording device, such as Fig.25 As shown, it at least includes: a recording initiating module 1610, a recording executing module 1630 and a splicing module 1650.
[0275] The recording initiating module 1610 is used to receive a process recording selection corresponding to entering a specified function in the first user terminal;
[0276] The recording execution module 1630 is used to select and trigger the recording of the process according to the operation performed on the first user terminal, and record in sequence until the first user terminal enters the specified function;
[0277] The splicing module 1650 is used to splice the operations recorded in sequence together to obtain an operation step jump execution sequence for entering the specified function, and the operation step jump execution sequence is used to simulate user control on the user terminal so that the user terminal automatically jumps to the specified function.
[0278] Fig.26 is a block diagram of a device for function playback according to an exemplary embodiment. In an exemplary embodiment, Fig.26 As shown, the function playback device at least includes: a playback initiating module 1710, a jump execution module 1730 and a target function entry module 1750.
[0279] The playback initiation module 1710 is used to obtain the operation step jump execution sequence according to the playback selection corresponding to the target function entry process in the user terminal;
[0280] A jump execution module 1730, configured to jump to the view element identifiers and the operation mode information corresponding to the view element identifiers in sequence in the sequence according to the operation steps, and sequentially execute the operations indicated by the corresponding operation mode information in the user terminal;
[0281] The target function entry module 1750 is used to jump the user terminal to the target function when the corresponding operation is executed in the jump execution sequence corresponding to the operation step.
[0282] Optionally, the present invention further provides a machine device, which can be used in the aforementioned implementation environment to execute Figure 3 , Figure 4 , Figure 5 , Figure 6 , Figure 7 and Figure 8 All or part of the steps of any of the methods shown. The device comprises:
[0283] processor;
[0284] a memory for storing processor-executable instructions;
[0285] When the computer-readable instructions are executed by the processor, the aforementioned method is implemented.
[0286] The specific manner in which the processor of the device in this embodiment performs operations has been described in detail in the embodiment of the method, and will not be elaborated here.
[0287] In an exemplary embodiment, a storage medium is also provided, which is a computer-readable storage medium, such as a temporary and non-temporary computer-readable storage medium including instructions. The storage medium, for example, includes a memory 204 of instructions, and the instructions can be executed by the processor 218 of the device 200 to perform the above method.
[0288] It should be understood that the present invention is not limited to the exact construction that has been described above and shown in the drawings and that various modifications and changes may be performed without departing from its scope. The scope of the present invention is limited only by the appended claims.
Claims
1. A method for realizing automatic function jump, characterized in that: The method comprises: When the first user terminal enters the recording mode, the user uses the application normally, records the operation and the view elements affected by the operation, and jumps to the designated function entrance, and concatenates the view element identifiers recorded in sequence and the operation mode information corresponding to the view element identifiers to obtain the operation step jump execution sequence for entering the designated function; The user terminal acquires an operation step jump execution sequence corresponding to a target function, the user terminal includes a first user terminal, and the target function includes the specified function, the operation step jump execution sequence includes a plurality of groups of view element identifiers and operation mode information corresponding to an operation path for jumping into the target function, each group of view element identifiers and operation mode information corresponds to an operation step and is used for automatic execution of the operation step; According to the view element identifiers and the operation mode information corresponding to the view element identifiers that exist sequentially in the operation step jump execution sequence, the operations indicated by the corresponding operation mode information are sequentially executed on the user terminal, and if the view element acted upon by the operation cannot be found in the application, the operation is continued to be executed after the view element identifier corresponding to the operation in the operation step jump execution sequence is converted, and the view element includes a button, a drag component and a function icon on the user terminal interface; When the corresponding operations are executed in the jump execution sequence corresponding to the operation steps, the user terminal automatically jumps to the target function.
2. The method according to claim 1, characterized in that The user enters the recording mode at the first user terminal and uses the application normally, records the operation and the view element affected by the operation until jumping to the designated function entrance, and concatenates the view element identifiers recorded in sequence and the operation mode information corresponding to the view element identifiers to obtain the operation step jump execution sequence for entering the designated function, including: Receiving a process recording selection corresponding to entering a designated function in a first user terminal; The process recording selection triggers the view element jump in the first user terminal and the operation performed on the view element, and sequentially records the corresponding view element identifier and the operation mode information corresponding to the view element identifier until the first user terminal enters the designated function; The sequentially recorded view element identifiers and the operation mode information corresponding to the view element identifiers are spliced together to obtain an operation step jump execution sequence for entering the specified function.
3. The method according to claim 1, characterized in that The step of jumping to execute the view element identifier and the operation mode information corresponding to the view element identifier in the sequence according to the operation steps, and sequentially executing the operations indicated by the corresponding operation mode information on the user terminal, includes: Parsing the jump execution sequence of the operation steps, and detecting whether the view element identifiers obtained by sequential parsing have corresponding view elements in the user terminal; If the view element identifier obtained by the sequential parsing has a corresponding view element in the user terminal, operating the view element according to the operation mode information corresponding to the view element identifier; The operation steps are sequentially parsed to jump to the next view element identifier in the execution sequence, and the view element is detected and the detected view element is operated accordingly.
4. The method according to claim 3, characterized in that If the view element affected by the operation cannot be found in the application, the operation is continued after the view element identifier corresponding to the operation in the operation step jump execution sequence is converted, including: If the view element identifier obtained by the sequential parsing does not have a corresponding view element in the user terminal, detecting whether the terminal version of the operation step jump execution sequence is the same as that of the user terminal; When it is detected that the terminal version of the operation step jump execution sequence is different from that of the user terminal, converting the view element identifier into a view element update identifier suitable for the user terminal; According to the view element update identifier and the operation mode information corresponding to the view element identifier, the corresponding view element is operated in the user terminal.
5. The method according to claim 4, characterized in that The converting the view element identifier into a view element update identifier suitable for the user terminal includes: According to the operation steps, the mapping of view elements between the terminal version where the execution sequence is located and the user terminal is jumped, the view element identifier is converted into a view element identifier corresponding to the mapped view element, and a view element update identifier suitable for the user terminal is obtained.
6. The method according to claim 5, characterized in that The method further comprises: before the view element identifiers and the operation mode information corresponding to the view element identifiers sequentially existing in the jump execution sequence according to the operation steps, and before the user terminal sequentially searches for the view element corresponding to each view element identifier and performs the operation indicated by the corresponding operation mode information on the view element: According to the mapping of view elements between the published terminal version and the old version, a mapping relationship between the view element identifier in the published terminal version and the view element identifier in the old terminal version is constructed and stored.
7. A method for function recording, characterized in that: The method comprises: Receiving a process recording selection corresponding to entering a designated function in a first user terminal; The process recording selection trigger is sequentially recorded according to the operation performed in the first user terminal until the first user terminal enters the specified function and ends, the operation performed by the first user terminal is oriented to the application related to the specified function, and the execution of the operation involves the triggering and jumping of the view element on the application; The operations recorded in sequence are spliced together to obtain an operation step jump execution sequence for entering the specified function. The operation step jump execution sequence is used to simulate user control on the user terminal so that the user terminal automatically jumps to the specified function. The operation step jump execution sequence includes several groups of view element identifiers and operation mode information corresponding to the operation path for jumping into the target function. Each group of view element identifiers and operation mode information corresponds to an operation step and will be used for the automatic execution of the operation step. The view elements include buttons, drag components and function icons on the user terminal interface.
8. A method for function playback, characterized in that: The method comprises: According to the playback selection corresponding to the target function entry process in the user terminal, an operation step jump execution sequence is obtained, wherein the operation step jump execution sequence includes a plurality of groups of view element identifiers and operation mode information corresponding to the operation path of jumping into the target function, each group of view element identifiers and operation mode information corresponds to an operation step and is used for automatic execution of the operation step; According to the view element identifiers and the operation mode information corresponding to the view element identifiers that exist sequentially in the operation step jump execution sequence, the operations indicated by the corresponding operation mode information are sequentially executed on the user terminal, and if the view element acted upon by the operation cannot be found in the application, the operation is continued to be executed after the view element identifier corresponding to the operation in the operation step jump execution sequence is converted, and the view element includes a button, a drag component and a function icon on the user terminal interface; When the corresponding operations are executed in the jump execution sequence corresponding to the operation steps, the user terminal automatically jumps to the target function.
9. A system for realizing an automatic jump entry function, characterized in that: The system comprises: an operation recording module, configured to record and generate an operation step jump execution sequence of a user controlling to enter a specified function according to an operation performed at a first user terminal, wherein the operation performed by the first user terminal is oriented to an application related to the specified function, and the execution of the operation involves triggering and jumping of a view element on the application; an execution sequence acquisition module, configured for a user terminal to acquire an operation step jump execution sequence corresponding to a target function, wherein the user terminal includes a first user terminal, and the target function includes the specified function, and the operation step jump execution sequence includes a plurality of groups of view element identifiers and operation mode information corresponding to an operation path for jumping into the target function, each group of view element identifiers and operation mode information corresponds to an operation step and is used for automatic execution of the operation step; An automatic jump execution module, configured to sequentially execute the operations indicated by the corresponding operation mode information on the user terminal according to the view element identifiers and the operation mode information corresponding to the view element identifiers in the order in the operation step jump execution sequence, and if the view element acted upon by the operation cannot be found in the application, then continue to execute the operation after converting the view element identifier corresponding to the operation in the operation step jump execution sequence, wherein the view element includes a button, a drag component, and a function icon on the user terminal interface; The function entry module is used for automatically jumping the user terminal into the target function when the corresponding operation is executed in the jump execution sequence corresponding to the operation step.
10. The system according to claim 9, characterized in that The operation recording module includes: A recording selection receiving unit, configured to receive a recording selection corresponding to a process of entering a designated function in a first user terminal; a recording execution unit, configured to record the process selection trigger according to the progress of the view element jump in the first user terminal and the operation performed on the view element, sequentially record the corresponding view element identifier and the operation mode information corresponding to the view element identifier until the first user terminal enters the specified function and ends, the operation performed by the first user terminal is oriented to the application related to the specified function, and the execution of the operation involves the triggering and jumping of the view element on the application; A splicing unit is used to splice the sequentially recorded view element identifiers and the operation mode information corresponding to the view element identifiers together to obtain an operation step jump execution sequence for entering the specified function, wherein the operation step jump execution sequence includes several groups of view element identifiers and operation mode information corresponding to the operation path for jumping into the target function, each group of view element identifiers and operation mode information corresponds to an operation step and will be used for the automatic execution of the operation step, and the view elements include buttons, drag components and function icons on the user terminal interface.
11. The system according to claim 9, characterized in that The automatic jump execution module comprises: A parsing unit, configured to parse the jump execution sequence of the operation steps, and detect whether the view element identifiers obtained by sequential parsing have corresponding view elements in the user terminal; an element operation unit, configured to operate the view element according to the operation mode information corresponding to the view element identifier if a corresponding view element exists in the user terminal; The parsing control unit is used to sequentially parse the next view element identifier in the jump execution sequence of the operation step, and detect the view element and operate the detected view element accordingly.
12. The system according to claim 11, characterized in that The automatic jump execution module comprises: a version detection unit, configured to detect whether the terminal version of the operation step jump execution sequence is the same as that of the user terminal if the view element identifier obtained by the sequential parsing does not have a corresponding view element in the user terminal; a sequence conversion unit, configured to convert the view element identifier into a view element update identifier applicable to the user terminal when detecting that the terminal version of the operation step jump execution sequence is different from that of the user terminal; The conversion sequence execution unit is used to operate the corresponding view element in the user terminal according to the view element update identifier and the operation mode information corresponding to the view element identifier.
13. A function recording device, characterized in that: The device comprises: A recording initiating module, configured to receive a recording selection corresponding to a process of entering a designated function in a first user terminal; a recording execution module, configured to record the process selection trigger according to the operation performed in the first user terminal, and record sequentially until the first user terminal enters the specified function and ends, wherein the operation performed by the first user terminal is oriented to the application related to the specified function, and the execution of the operation involves the triggering and jumping of the view element on the application; A splicing module is used to splice the operations recorded in sequence together to obtain an operation step jump execution sequence for entering the specified function. The operation step jump execution sequence is used to simulate user control on a user terminal so that the user terminal automatically jumps into the specified function. The operation step jump execution sequence includes several groups of view element identifiers and operation mode information corresponding to the operation path for jumping into the target function. Each group of view element identifiers and operation mode information corresponds to an operation step and will be used for the automatic execution of the operation step. The view elements include buttons, drag components and function icons on the user terminal interface.
14. A function playback device, characterized in that: The device comprises: A playback initiation module, configured to obtain an operation step jump execution sequence according to a playback selection corresponding to a target function entry process in a user terminal, wherein the operation step jump execution sequence includes a plurality of groups of view element identifiers and operation mode information corresponding to an operation path for jumping into the target function, each group of view element identifiers and operation mode information corresponding to an operation step, and used for automatic execution of the operation step; A jump execution module, configured to sequentially execute the operations indicated by the corresponding operation mode information on the user terminal according to the view element identifiers and the operation mode information corresponding to the view element identifiers in the order of the operation step jump execution sequence, and if the view element acted upon by the operation cannot be found in the application, then continue to execute the operation after converting the view element identifier corresponding to the operation in the operation step jump execution sequence, wherein the view element includes a button, a drag component, and a function icon on the user terminal interface; The target function entry module is used to automatically jump to the target function when the corresponding operation is executed in the jump execution sequence corresponding to the operation step.
15. A machine device, characterized in that: include: processor; as well as A memory having computer-readable instructions stored thereon, wherein the computer-readable instructions, when executed by the processor, implement the method according to any one of claims 1 to 8.
