WO2019095861A1 - 数据处理方法和装置、终端设备、服务器 - Google Patents

数据处理方法和装置、终端设备、服务器 Download PDF

Info

Publication number
WO2019095861A1
WO2019095861A1 PCT/CN2018/107522 CN2018107522W WO2019095861A1 WO 2019095861 A1 WO2019095861 A1 WO 2019095861A1 CN 2018107522 W CN2018107522 W CN 2018107522W WO 2019095861 A1 WO2019095861 A1 WO 2019095861A1
Authority
WO
WIPO (PCT)
Prior art keywords
identifier
interface
permission
application
terminal device
Prior art date
Application number
PCT/CN2018/107522
Other languages
English (en)
French (fr)
Inventor
李记锋
Original Assignee
阿里巴巴集团控股有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 阿里巴巴集团控股有限公司 filed Critical 阿里巴巴集团控股有限公司
Publication of WO2019095861A1 publication Critical patent/WO2019095861A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/2866—Architectures; Arrangements
    • H04L67/30—Profiles
    • H04L67/303—Terminal profiles
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M1/00—Substation equipment, e.g. for use by subscribers
    • H04M1/72—Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
    • H04M1/724—User interfaces specially adapted for cordless or mobile telephones
    • H04M1/72403—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality
    • H04M1/72406—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality by software upgrading or downloading

Definitions

  • the embodiments of the present disclosure relate to the field of computer technologies, and in particular, to a data processing method and apparatus, a terminal device, and a server.
  • operating system-based terminal devices have been rapidly developed. Through the operating system, users can install their favorite applications on the terminal device to achieve more functions.
  • the application When a function needs to be performed, the application usually needs to obtain the corresponding permissions in the operating system to perform the function. For example, when you need to perform a sweep, the application usually needs to obtain the camera permissions in the operating system to perform the sweep function.
  • the operating system can provide an application permission setting interface, and the user can perform authorization operation or deauthorization operation on one or more rights of the application in the permission setting interface.
  • a user can cancel one or more permissions for an application.
  • the application usually pops up a prompt message to prompt the user to open the canceled right.
  • the user needs to enter the permission setting interface of the application through one or more operations, and the canceled permission is opened in the permission setting interface, so that the operation of the entire permission opening process is cumbersome and the user experience is not high.
  • different terminal devices may run different operating systems, and paths to enter the application permission setting interface in different operating systems are different. In the case that the user is not familiar with the terminal device, the user may need to perform a larger number of operations or take a longer time to enter the application permission setting interface.
  • the purpose of the embodiments of the present specification is to provide a data processing method and device, a terminal device, and a server, so as to implement a permission setting interface that the terminal device can jump to the application itself, simplify user operations, and improve user experience.
  • an embodiment of the present disclosure provides a data processing method, including: acquiring a scene identifier corresponding to the control in response to a triggering instruction for a control in a service interface; wherein the scene identifier includes a permission identifier; and detecting an application Whether the program has the authority identified by the permission identifier; if not, the device information is sent to the server.
  • an embodiment of the present disclosure provides a terminal device, including: a display component, configured to provide a service interface, and a processor, configured to acquire a scenario identifier corresponding to the control, in response to a triggering instruction for a control in a service interface.
  • the scenario identifier includes a permission identifier; detecting whether the application has the authority identified by the permission identifier; and the communication component is configured to send the device information to the server.
  • an embodiment of the present disclosure provides a data processing apparatus, including: an obtaining unit, configured to acquire a scene identifier corresponding to the control, in response to a triggering instruction for a control in a service interface; wherein the scene identifier includes The privilege identifier is configured to detect whether the application has the privilege identified by the privilege identifier, and the sending unit is configured to send the device information to the server.
  • the embodiment of the present disclosure provides a data processing method, including: receiving an interface identifier sent by a server; wherein the interface identifier is used to identify a permission setting interface of an application; and displaying the generated based on the interface identifier a guiding interface; entering the permission setting interface in response to the triggering permission to enable the opening permission; opening the target permission of the application in response to the triggering instruction of the opening the target permission; executing the triggering instruction of the application in the foreground, executing The functionality of the controls in the application.
  • an embodiment of the present disclosure provides a terminal device, including: a communication component, configured to receive an interface identifier sent by a server; wherein the interface identifier is used to identify a permission setting interface of an application; Demonstrating a boot interface generated based on the interface identifier; displaying the permission setting interface; the processor, configured to control the display component to display the permission setting interface in response to the triggering instruction for allowing the permission to be opened; and triggering in response to the opening of the target permission And an instruction to open a target authority of the application; and execute a function of the control in the application in response to a trigger instruction of the application running in the foreground.
  • an embodiment of the present disclosure provides a data processing apparatus, including: a receiving unit, configured to receive an interface identifier sent by a server; wherein the interface identifier is used to identify a permission setting interface of an application; And the entry unit is configured to enter the permission setting interface in response to the triggering instruction for allowing the permission to be opened; and the opening unit is configured to open the location in response to the triggering instruction of opening the target permission An object authority of the application; an execution unit, configured to execute a function of the control in the application in response to a trigger instruction of the application running in the foreground.
  • the embodiment of the present disclosure provides a data processing method, including: providing a correspondence between device information and an interface identifier; wherein the interface identifier is used to identify a permission setting interface of the application; and the receiving terminal device sends the The device information is obtained by acquiring the interface identifier corresponding to the received device information based on the correspondence between the device information and the interface identifier, and sending the acquired interface identifier to the terminal device.
  • an embodiment of the present disclosure provides a server, including: a communication component, configured to receive device information sent by a terminal device; and send the acquired interface identifier to the terminal device.
  • a processor configured to provide a correspondence between the device information and the interface identifier, where the interface identifier is used to identify a permission setting interface of the application; and the interface identifier corresponding to the received device information is obtained based on the correspondence between the device information and the interface identifier .
  • the embodiment of the present disclosure provides a data processing apparatus, including: a providing unit, configured to provide a correspondence between device information and an interface identifier; wherein the interface identifier is used to identify a permission setting interface of the application; a unit, configured to receive the device information sent by the terminal device, and the acquiring unit, configured to acquire an interface identifier corresponding to the received device information, based on the correspondence between the device information and the interface identifier, and the sending unit, configured to send the acquired interface to the terminal device Logo.
  • the server can provide the corresponding relationship between the device information and the interface identifier; and can receive the device information sent by the terminal device; and can be based on the correspondence between the device information and the interface identifier. Acquiring the interface identifier corresponding to the received device information; the acquired interface identifier may be sent to the terminal device.
  • the server can send an interface identifier suitable for the terminal device to the terminal device according to the device information sent by the terminal device, so that the terminal device can jump to the permission setting interface identified by the interface identifier, so that the user can conveniently set the interface in the permission setting interface.
  • the ability to open applications simplifies user operations and improves the user experience.
  • FIG. 1 is a flow chart of a data processing method according to an embodiment of the present specification
  • FIG. 2 is a schematic diagram of a service interface according to an embodiment of the present specification
  • FIG. 3 is a schematic diagram of a guiding interface according to an embodiment of the present specification.
  • FIG. 4 is a schematic diagram of a prompt information according to an embodiment of the present specification.
  • FIG. 5 is a schematic diagram of a permission setting interface according to an embodiment of the present specification.
  • FIG. 6 is a schematic diagram of a user opening a target authority in a permission setting interface according to an embodiment of the present disclosure
  • FIG. 7 is a schematic diagram of an operation of a user returning an application to a foreground operation according to an embodiment of the present disclosure
  • FIG. 8 is a schematic diagram of performing a sweep function according to an embodiment of the present specification.
  • FIG. 9 is a flowchart of a data processing method according to an embodiment of the present specification.
  • FIG. 10 is a flowchart of a data processing method according to an embodiment of the present specification.
  • FIG. 11 is a flowchart of a data processing method according to an embodiment of the present specification.
  • FIG. 12 is a schematic diagram showing the functional structure of a data processing apparatus according to an embodiment of the present disclosure.
  • FIG. 13 is a schematic diagram showing the functional structure of a data processing apparatus according to an embodiment of the present disclosure.
  • FIG. 14 is a schematic diagram showing the functional structure of a data processing apparatus according to an embodiment of the present specification.
  • FIG. 15 is a schematic structural diagram of a terminal device according to an embodiment of the present disclosure.
  • FIG. 16 is a schematic diagram showing the functional structure of a server according to an embodiment of the present specification.
  • FIG. 1 Please refer to FIG. 1, FIG. 2, FIG. 3, FIG. 4, FIG. 5, FIG. 6, FIG. 7, and FIG. Embodiments of the present specification provide a data processing system.
  • the data processing system may include a terminal device.
  • the terminal device may have a display function.
  • the terminal device may include a smart phone, a tablet electronic device, a network set top box, a portable computer, a desktop computer, a personal digital assistant (PDA), an in-vehicle device, a smart wearable device, and the like.
  • the smart wearable device may include smart glasses, a smart watch, a smart bracelet, and the like.
  • the terminal device can be running an operating system (OS).
  • the operating system can be a computer program that controls and manages hardware and software resources.
  • the operating system may include an Android operating system (an operating system developed by Google Inc.), an IOS operating system (an operating system developed by Apple Inc.), and a Windows operating system (an operating system developed by Microsoft Corporation).
  • the operating system may further include an operating system that is further optimized and customized based on the operating system described above.
  • the MIUI operating system the mobile phone operating system developed by Huawei based on the Android operating system
  • the EMUI operating system the mobile operating system developed by Huawei based on the Android operating system.
  • An application can be run in the operating system.
  • the operating system can manage the permissions of the application.
  • Application permissions can include Normal Permissions and Dangerous Permissions. Common permissions may include, for example, vibration, access to a network, and the like.
  • Normal permissions usually do not involve user privacy. Normal permissions are authorized when the application is installed and usually do not require user authorization.
  • Sensitive permissions may include, for example, invoking a camera, reading location information, allowing message notifications, and the like. Sensitive permissions usually involve user privacy. Sensitive permissions usually require authorization from the user.
  • the operating system may provide an permission setting interface of the application, and the user may perform an authorization operation or a deauthorization operation on the one or more sensitive permissions of the application in the permission setting interface.
  • the permissions setting interface provided by the operating system can be the same or different for different applications.
  • the developer may develop a software development kit that has been developed with certain functions ( The Software Development Kit (SDK) is embedded in the application, so that the application in the operating system can be embedded with a software development kit.
  • SDK Software Development Kit
  • the data processing system may further include a server.
  • the server may be a server or a server cluster including multiple servers.
  • the server may include, for example, an Alipay server, a WeChat server, an ant wealth server, a Jingdong server, and the like.
  • the server can communicate with the terminal device.
  • the server and the terminal device can communicate using any suitable network protocol, including network protocols that have not been developed at the filing date of this document.
  • the network protocol may include, for example, a TCP/IP protocol, a UDP/IP protocol, an HTTP protocol, an HTTPS protocol, and the like.
  • the network protocol may further include, for example, an RPC protocol (Remote Procedure Call Protocol), a REST protocol (Representational State Transfer), and the like used on the foregoing protocol.
  • the terminal device can run an application in an operating system to provide a service interface.
  • the application may include, for example, Alipay, WeChat, Ant Fortune, Jingdong Mobile Client, and the like.
  • the service interface may be provided by default.
  • the service interface may be provided in response to a first triggering instruction that provides a service interface.
  • the first triggering command may be generated when any combination of one or more of the keys is detected, pressed, clicked, double-clicked, or swiped.
  • the keys may include physical keys, controls, and the like.
  • the business interface can be used to present business data, which can include, for example, order data, payment data, merchandise data, and the like.
  • the business interface may have one or more controls, and the controls may include button controls, image controls, text box controls, input box controls, and the like.
  • Some or all of the controls in the service interface may have a scenario identifier, and the scenario identifier may be used to identify a service scenario.
  • the scenario identifier may specifically include a service identifier and a permission identifier.
  • the service identifier can be used to identify the service involved in the service scenario.
  • the permission identifier can be used to identify the permission that the service scenario needs to use.
  • the rights identified by the rights identifier may be ordinary rights or sensitive rights.
  • the scenario identifier may be obtained by splicing the service identifier and the permission identifier.
  • the scene identifier can also be obtained based on other methods.
  • the service identifier and the rights identifier may be encoded to obtain the scene identifier.
  • the business interface can have a swipe button control.
  • the scan button control may be associated with a scene identifier Pay_Camera, and the scene identifier Pay_Camera may be used to identify a sweeping service scene.
  • the scenario identifier Pay_Camera may include a service identifier Pay and a permission identifier Camera, where the service identifier Pay may be used to identify a scan code payment service, and the permission identifier Camera may be used to identify a call camera permission that is required to be used in the sweeping service scenario. .
  • the business interface can have an activity reminder button control.
  • the activity reminder button control may be corresponding to a scene identifier Push_Notifaction, and the scene identifier Push_Notifaction may be used to identify an activity reminding service scenario.
  • the scenario identifier Push_Notifaction may include a service identifier Push and a permission identifier Notifaction, and the service identifier Push may be used to identify a message push service, and the permission identifier Notifaction may be used to identify an allow message notification permission that needs to be used in the active reminder service scenario.
  • the terminal device may detect whether the control in the service interface is clicked, double-clicked, pressed for more than a predetermined time (or called a long press), or swiped to generate a second trigger instruction;
  • the second triggering instruction is for the scene identifier corresponding to the control;
  • the acquired scene identifier can be parsed to obtain the permission identifier;
  • the application can be detected whether the application has the authority identified by the permission identifier; if not, the device information can be sent to the server.
  • the application here can be the aforementioned application for providing a business interface.
  • the application may generate a second triggering instruction; the second triggering instruction may be obtained for the scene identifier corresponding to the control; the obtained scene identifier may be parsed to obtain the permission identifier; and the application identifier and the permission identifier may be used to invoke the operating system.
  • the permission detection method is configured to detect whether the user has the authority identified by the permission identifier; if not, the device information acquisition method in the operating system may be invoked to obtain the device information of the terminal device; and the acquired device information may be sent to the server. among them,
  • the application identifier may be used to identify an application, such as a package name (PackageName) of the application.
  • the authority detection method may include a rights detection function.
  • the operating system may be an Android operating system, and the permission detecting function in the Android operating system may be AppOpsManager.checkOpThrow. After AppOpsManager.checkOpThrow is called, the Android operating system can query whether the application identified by the application identifier has the permission identified by the permission identifier from its own application rights manager; if so, it can return AppOpsManager.Mode_Allowed to the application; if not, You can return AppOpsManager.Mode_Ignore to your application.
  • the device information may include one or more of a vendor identifier, a device model identifier, and an operating system version identifier.
  • the vendor identifier may be used to identify the manufacturer of the terminal device, and may include, for example, HW (Huawei), MI (Millet), Apple (Apple), and the like.
  • the device model identifier may be used to identify the model of the terminal device, and may include, for example, PE_TL10 (a model of a mobile phone manufactured by Huawei).
  • the operating system version identifier may be used to identify a version of the operating system, and may include, for example, MIUI 9.0 (a version of Huawei's development operating system), EMUI 3.0 (a version of Huawei's development operating system), and the like.
  • the device information may also include other data, which is not specifically limited in this embodiment.
  • the device information acquisition method may include a device information acquisition function.
  • the operating system may be an Android operating system
  • the device information obtaining function may include a vendor identification acquiring function getDeviceBrand, a device model identification acquiring function getSystemModel, an operating system version obtaining function getSystemVersion, and the like.
  • the operating systems running on different terminal devices may be different, and the paths of the rights setting interfaces of the applications in different operating systems may be different.
  • the server may provide a corresponding relationship between the device information and the interface identifier, in order to facilitate the interface identifier to be redirected to the rights setting interface.
  • the interface identifier can be used to identify a permission setting interface of the application.
  • the interface identifier may be a link address implemented based on a URL Scheme protocol.
  • the correspondence between the device information and the interface identifier may include a combination of one or more of a vendor identifier, a device model identifier, and an operating system version identifier, and a corresponding relationship of the interface identifier.
  • the server may provide a correspondence between the HW, the PE_TL 10, and the EMUI 3.0 and the interface identifier IDA.
  • the correspondence between the MI, the NOTE 3, and the MIUI 9.0 and the interface identifier IDB may be provided.
  • the server may receive the device information sent by the terminal device; the interface identifier corresponding to the received device information may be obtained based on the correspondence between the device information and the interface identifier; and the acquired interface identifier may be sent to the terminal device.
  • the terminal device may receive an interface identifier sent by the server; may display a guiding interface generated based on the received interface identifier; and may enter the third triggering command that is allowed to be opened in the guiding interface.
  • the interface identifies the permission setting interface identified by the interface.
  • a unified boot template can be embedded in the application.
  • the application can receive the interface identifier sent by the server; the boot template can be obtained locally; the interface identifier can be embedded in the boot template obtained locally to obtain the boot interface; and the boot interface can be displayed.
  • the application here can be the aforementioned application for providing a business interface. In this way, the boot template does not have to be transmitted between the terminal device and the server, so that the amount of communication data between the terminal device and the server can be reduced.
  • the guiding interface may have a first control
  • the first control may be a button control or an image control or the like.
  • the first control may correspond to an interface identifier for generating a third triggering instruction that allows the opening permission.
  • the application may detect whether the first control is clicked, double-clicked, pressed for more than a predetermined time, or swiped to generate a third triggering instruction; in response to the third triggering instruction, the interface identifier corresponding to the first control may be acquired; Go to the permission setting interface identified by the interface identifier.
  • the application here can be the aforementioned application for providing a business interface.
  • the application may also generate the third triggering instruction in other manners, which is not specifically limited in this embodiment.
  • the terminal device may activate the target permission of the application in response to the fifth triggering instruction of the provisioning target authority received in the permission setting interface; and execute the application in response to the foreground received in the permission setting interface.
  • the sixth trigger instruction can execute the function corresponding to the control.
  • the target authority here may be the authority identified by the rights identifier in the foregoing scenario identifier; the application here may be the foregoing application for providing a service interface.
  • the permission setting interface can be provided by an operating system in the terminal device.
  • the permission setting interface can have one or more controls, and each control can correspond to one permission.
  • the operating system can detect whether the control in the permission setting interface is clicked, double-clicked, pressed for more than a predetermined time, or swiped to generate a trigger instruction for opening the permission corresponding to the control.
  • the operating system may also use other methods to generate the triggering permission of the opening permission, which is not specifically limited in this embodiment.
  • one or more gestures may be preset in the operating system, and each gesture may correspond to a permission in the permission setting interface. When the operating system recognizes the gesture, the operating system may generate a trigger instruction for opening the permission corresponding to the gesture.
  • Applications can run in the foreground or in the background.
  • the interface of the application can be displayed in the display screen of the terminal device.
  • the interface of the application is usually not displayed in the display screen of the terminal device; at this time, the application usually runs in the resource manager of the operating system and occupies system resources.
  • the permission setting interface is usually provided by the operating system, after the terminal device enters the permission setting interface by the guiding interface, the application usually changes to run in the background in the foreground. After the user opens the target permission in the permission setting interface, the trigger operation can be triggered to make the application run in the background to run in the foreground.
  • the permission setting interface may include a return control
  • the return control may be a button control or an image control.
  • the operating system can detect whether the return control is clicked, double clicked, pressed for more than a predetermined time, or swiped to generate a sixth triggering command to run the application in the foreground.
  • the operating system can also generate the sixth triggering instruction in other manners, which is not specifically limited in this embodiment.
  • the terminal device when detecting that the application program has the authority identified by the authority identifier, the terminal device may further execute a function corresponding to the control by the second trigger instruction.
  • the functions of the second triggering instruction for the control may include, for example, a sweep function, a push activity information function, and the like.
  • the application may generate a second triggering instruction; the second triggering instruction may be obtained for the scene identifier corresponding to the control; the obtained scene identifier may be parsed to obtain the permission identifier; and the application identifier and the permission identifier may be used to invoke the operating system.
  • the permission detection method is configured to detect whether the user has the authority identified by the permission identifier; if yes, the second trigger instruction may be executed for the function corresponding to the control.
  • the server may further provide a correspondence between the service identifier and the guiding template.
  • Each boot template may correspond to one or more service identifiers, and each service identifier may correspond to one boot template.
  • the guiding template may have prompt information for prompting the user to open the permission, and the prompt information may be text, sound, image, video, or any combination thereof.
  • the boot template can be used to generate a boot interface.
  • the boot interface can be used to guide the user to open the application.
  • the terminal device when detecting that the application does not have the authority identified by the authority identifier, the terminal device may further send the scene identifier to the server.
  • the scene identifier may be the scene identifier corresponding to the control by the foregoing second trigger instruction.
  • the server may receive the scenario identifier sent by the terminal device; the received scenario identifier may be parsed to obtain the service identifier; and the mapping template corresponding to the service identifier may be obtained according to the correspondence between the service identifier and the guiding template; and the obtained template may be sent to the terminal device. Guide template.
  • the terminal device may receive a boot template sent by the server; the interface identifier may be embedded in a boot template from the server to obtain a boot interface; and the boot interface may be displayed.
  • the terminal device can display different guiding interfaces according to different service scenarios, thereby improving the user experience.
  • the application can receive the boot template sent by the server; the interface identifier can be embedded in the boot template from the server to obtain a boot interface; and the boot interface can be displayed.
  • the terminal device may further display the prompt information in response to the fourth triggering instruction of the refusal to open permission received at the guiding interface.
  • the guiding interface may further have a second control.
  • the second control may be a button control or an image control or the like.
  • the second control may be configured to generate a fourth trigger instruction that refuses to open the right.
  • the application can also detect whether the second control is clicked, double-clicked, pressed for more than a predetermined time, or swiped to generate a fourth triggering instruction; in response to the fourth triggering instruction, the prompting information can be displayed, and the prompting information can be text and sound. , image, video or any combination thereof, etc., the prompt information can be, for example, the text message "Detecting that you refuse to turn on the camera permission. You cannot use the sweep function."
  • FIG. 1, FIG. 2, FIG. 3, FIG. 4, FIG. 5, FIG. 6, FIG. 7, and FIG. An example of a scenario of an embodiment of the present specification is described below.
  • the terminal device may be a smart phone.
  • the smartphone can run the EMUI 3.0 operating system.
  • An ant wealth application can be run in the EMUI 3.0 operating system.
  • the server can be an ant wealth server.
  • the smartphone can run an ant wealth application to provide a business interface.
  • the business interface can have a swipe button control.
  • the scan button control may be associated with a scene identifier Pay_Camera, and the scene identifier Pay_Camera may be used to identify a sweeping service scene.
  • the scenario identifier Pay_Camera may include a service identifier Pay and a permission identifier Camera, where the service identifier Pay may be used to identify a scan code payment service, and the permission identifier Camera may be used to identify a call camera permission that is required to be used in the sweeping service scenario. .
  • the smart phone may generate a trigger command after detecting that the swipe button control is clicked, double-clicked, pressed for more than a predetermined time, or swiped; in response to the trigger command, the scan may be acquired.
  • Sweep button control corresponding scene identifier Pay_Camera; can analyze the scene identifier Pay_Camera, get the permission identification Camera; can detect whether the ant wealth application has the permission to call the camera; if yes, can perform the sweep scan button control corresponding to the sweep function;
  • the operating system version identifier EMUI3.0 and the scene identifier Pay_Camera may be sent to the ant wealth server to guide the user to activate the calling camera permission of the ant wealth application.
  • the ant wealth server may provide a correspondence between the operating system version identifier EMUI3.0 and the interface identifier IDA; and the corresponding relationship between the service identifier Pay and the boot template TA may be provided.
  • the ant wealth server can receive the operating system version identifier EMUI3.0 and the scene identifier Pay_Camera sent by the smart phone; the interface identifier IDA corresponding to the operating system version identifier EMUI3.0 can be obtained; the scene identifier Pay_Camera can be parsed to obtain the service identifier Pay; The boot template TA corresponding to the service identifier Pay may be obtained; the interface identifier IDA and the boot template TA may be returned to the smart phone.
  • the smart phone may receive the interface identifier IDA and the boot template TA sent by the ant wealth server; may display a boot interface generated based on the interface identifier IDA and the boot template TA; in response to the permission to be opened at the boot interface
  • the triggering command of the permission may enter the permission setting interface identified by the interface identifier IDA; or, in response to the triggering instruction of the rejection opening permission received at the guiding interface, the text prompt message may be displayed, “Your camera function does not seem to be open ⁇ ".
  • the smart phone can activate the calling camera permission of the ant wealth application in response to the triggering instruction for invoking the camera permission received in the permission setting interface; and the ant wealth application is executed in response to the foreground received in the permission setting interface.
  • the trigger command of the program can execute the sweep function corresponding to the sweep button control.
  • the embodiment of the present specification provides a data processing method.
  • the data processing method uses the terminal device as an execution subject, and may include the following steps.
  • Step S10 Acquire a scene identifier corresponding to the control in response to a triggering instruction for a control in the service interface.
  • the service interface may be provided by an application in the terminal device for displaying service data.
  • the business data may include, for example, order data, payment data, merchandise data, and the like.
  • the business interface may have one or more controls, and the controls may include button controls, image controls, text box controls, input box controls, and the like.
  • Some or all of the controls in the service interface may be associated with a scenario identifier, and the scenario identifier may be used to identify a service scenario.
  • the scenario identifier may specifically include a service identifier and a permission identifier.
  • the service identifier can be used to identify the service involved in the service scenario.
  • the permission identifier can be used to identify the permission that the service scenario needs to use.
  • the application in the terminal device may detect whether a control in the service interface is clicked, double-clicked, pressed for more than a predetermined time, or swiped to generate a trigger instruction; in response to the trigger instruction, Obtaining the trigger instruction for the scene identifier corresponding to the control.
  • Step S12 Detect whether the application has the authority identified by the permission identifier.
  • the application in the terminal device can parse the scene identifier to obtain the permission identifier; and can detect whether the user has the authority identified by the authority identifier.
  • the application here can be the aforementioned application for providing a business interface.
  • Step S14 If no, the device information is sent to the server.
  • the application in the terminal device may acquire device information of the terminal device; the device information may be sent to the server.
  • the device information includes one or more of a vendor identifier, a model identifier, and an operating system version identifier.
  • the application in the terminal device may further send the scenario identifier to the server.
  • the application in the terminal device can also perform a function corresponding to the control.
  • the control here can be the control for the aforementioned trigger instruction.
  • the terminal device may obtain a scenario identifier corresponding to the control, where the scenario identifier may include a permission identifier, and may detect whether the application has the permission identifier. The identified permission; if not, the device information can be sent to the server. In this way, when detecting that the application does not have the permission required by the current service scenario, the terminal device may send its own device information to the server, so as to be able to receive the interface identifier for jumping to the permission setting interface, thereby guiding the user. The permissions required to open the current business scenario.
  • the embodiment of the present specification also provides another data processing method.
  • the data processing method uses the terminal device as an execution subject, and may include the following steps.
  • Step S20 Receive an interface identifier sent by the server.
  • the interface identifier may be used to identify a permission setting interface of the application.
  • the interface identifier may be a link address implemented based on a URL Scheme protocol.
  • the application program in the terminal device may send device information to the server, and may receive an interface identifier corresponding to the device information sent by the server.
  • Step S22 Display a boot interface generated based on the interface identifier.
  • the application in the terminal device may acquire a boot template; the boot interface may be generated based on the boot template and the interface identifier; and the boot interface may be displayed.
  • the guiding template may have prompt information for prompting the user to open the permission, and the prompt information may be text, sound, image, video, or any combination thereof.
  • the boot template can be used to generate a boot interface.
  • the boot interface can be used to guide the user to open the application.
  • the application in the terminal device may be embedded with a unified boot template. In this way, the application in the terminal device can obtain the boot template locally. In this way, the boot template does not have to be transmitted between the terminal device and the server, so that the amount of communication data between the terminal device and the server can be reduced.
  • the application in the terminal device may send a scenario identifier to the server; and may receive a boot template corresponding to the service identifier in the scenario identifier sent by the server.
  • the terminal device can display different guiding interfaces according to different service scenarios, thereby improving the user experience.
  • Step S24 Enter the permission setting interface in response to the trigger instruction that allows the permission to be opened.
  • the guiding interface may have a first control.
  • the first control may correspond to the interface identifier, and is used to generate a trigger instruction that allows the permission to be opened.
  • the application in the terminal device can detect whether the first control is clicked, double-clicked, pressed for more than a predetermined time, or swiped to generate a trigger instruction that allows the permission to be opened; in response to the trigger instruction that allows the permission to be opened; Enter the permission setting interface identified by the interface identifier.
  • Step S26 Turn on the target authority of the application in response to the triggering instruction of the target permission.
  • the target authority may be the authority identified by the rights identifier in the scene identifier.
  • the terminal device may be running an operating system.
  • the permission setting interface may be provided by the operating system.
  • the permission setting interface can have one or more controls, and each control can correspond to one permission.
  • the operating system may detect whether the control in the permission setting interface is clicked, double-clicked, pressed for more than a predetermined time, or swiped to generate a trigger instruction for opening the permission corresponding to the control.
  • the operating system may also generate triggering commands for the opening permission in other manners, which is not specifically limited in this embodiment.
  • one or more gestures may be preset in the operating system, and each gesture may correspond to one of the rights setting interfaces. When the operating system recognizes the gesture, the operating system may generate a trigger instruction for opening the permission corresponding to the gesture.
  • Step S28 The function of the control in the application is executed in response to the triggering instruction of the application running in the foreground.
  • the application in the terminal device may run in the foreground or in the background.
  • the interface of the application can be displayed in the display screen of the terminal device.
  • the interface of the application is usually not displayed in the display screen of the terminal device; at this time, the application usually runs in the resource manager of the operating system and occupies system resources.
  • the permission setting interface is usually provided by the operating system, after the terminal device enters the permission setting interface by the guiding interface, the application program is changed to run in the background in the foreground. After the user opens the target permission in the permission setting interface, the user can trigger the operation to make the application run in the background to run in the foreground.
  • the permission setting interface may include a return control
  • the return control may be a button control or an image control.
  • the operating system can detect whether the return control is clicked, double-clicked, pressed for more than a predetermined time, or swiped to generate a trigger instruction for running the application in the foreground.
  • the operating system may also generate triggering instructions for running the application in the foreground in other manners, which is not specifically limited in this embodiment.
  • the guiding interface may further have a second control.
  • the second control can be used to generate a trigger instruction that refuses to open the right.
  • the application program in the terminal device may detect whether the second control is clicked, double-clicked, pressed for more than a predetermined time, or scrolled to generate a trigger instruction for rejecting the open permission; in response to the trigger instruction for rejecting the open permission, You can display a message.
  • the prompt information may be text, sound, image, video, or any combination thereof, and the prompt information may be, for example, a text message "Detecting that you refuse to turn on the camera permission. You cannot use the sweep function."
  • the terminal device may receive an interface identifier sent by the server; may display a boot interface generated based on the interface identifier; and may respond to the triggering instruction that allows the permission to be opened, may enter the permission setting interface;
  • the triggering instruction of the permission may open the target authority of the application; in response to the triggering instruction of the application running in the foreground, the function of the control in the application may be executed.
  • the terminal device can receive the interface identifier sent by the server; the user can jump to the permission setting interface based on the interface identifier; facilitate the user to open the application permission in the permission setting interface, thereby simplifying the user operation and improving the user experience.
  • the embodiment of the present specification also provides another data processing method.
  • the data processing method takes the server as the execution subject, and may include the following steps.
  • Step S30 Provide a correspondence between the device information and the interface identifier.
  • the device information may include one or more of a vendor identifier, a device model identifier, and an operating system version identifier.
  • the interface identifier can be used to identify a permission setting interface of the application.
  • the interface identifier may be a link address implemented based on a URL Scheme protocol.
  • the correspondence between the device information and the interface identifier may include a combination of one or more of a vendor identifier, a device model identifier, and an operating system version identifier, and a corresponding relationship of the interface identifier.
  • the device information may also include other data, which is not specifically limited in this embodiment.
  • the developer may collect the interface identifier of the application in one or more terminal devices; the correspondence between the device information of the terminal device and the interface identifier of the application device in the terminal device may be set in the server. .
  • Step S32 Receive device information sent by the terminal device.
  • the terminal device may send its own device information to the server, and the server may receive device information sent by the terminal device.
  • Step S34 Acquire an interface identifier corresponding to the received device information based on the correspondence between the device information and the interface identifier.
  • Step S36 Send the acquired interface identifier to the terminal device.
  • the server may further provide a default interface identifier.
  • the default interface identifier can be used to identify an application setting interface of an application in a common majority terminal device. In this manner, the server may determine that the default interface identifier has a corresponding relationship with the receiving device information when the interface identifier corresponding to the receiving device information is not obtained; the default interface identifier may be obtained; and the default may be sent to the terminal device. Interface identifier.
  • the server may further provide a correspondence between the service identifier and the boot template.
  • the service identifier can be used to identify the service involved in the service scenario.
  • the guiding template may have prompt information for prompting the user to open the permission, and the prompt information may be text, sound, image, video, or any combination thereof.
  • the boot template can be used to generate a boot interface.
  • the boot interface can be used to guide the user to open the application.
  • the server may receive the scenario identifier sent by the terminal device, and may obtain the boot template corresponding to the received service identifier based on the correspondence between the service identifier and the boot template; and the obtained boot template may be sent to the terminal device.
  • the server may provide a corresponding relationship between the device information and the interface identifier; and may receive the device information sent by the terminal device; and obtain the interface identifier corresponding to the received device information based on the correspondence between the device information and the interface identifier.
  • the acquired interface identifier can be sent to the terminal device.
  • the server can send an interface identifier suitable for the terminal device to the terminal device according to the device information sent by the terminal device, so that the terminal device can jump to the permission setting interface identified by the interface identifier, so that the user can conveniently set the interface in the permission setting interface.
  • the ability to open applications simplifies user operations and improves the user experience.
  • the embodiment of the present specification further provides a data processing apparatus, which may include an obtaining unit 40, a detecting unit 42, and a transmitting unit 44. among them,
  • the obtaining unit 40 is configured to obtain, according to a triggering instruction for the control in the service interface, a scenario identifier corresponding to the control, where the scenario identifier includes a permission identifier;
  • the detecting unit 42 is configured to detect whether the application has the authority identified by the permission identifier
  • the sending unit 44 is configured to send device information to the server if not.
  • the embodiment of the present specification further provides another data processing apparatus, which may include a receiving unit 50, a display unit 52, an entry unit 54, an opening unit 56, and an execution unit 58. among them,
  • the receiving unit 50 is configured to receive an interface identifier sent by the server, where the interface identifier is used to identify a permission setting interface of the application;
  • a display unit 52 configured to display a boot interface generated based on the interface identifier
  • the entering unit 54 is configured to enter the permission setting interface in response to the triggering instruction for allowing the permission to be opened;
  • the opening unit 56 is configured to enable the target authority of the application in response to the triggering instruction for opening the target authority;
  • the executing unit 58 is configured to execute a function of the control in the application in response to a trigger instruction of the application running in the foreground.
  • the embodiment of the present specification further provides another data processing apparatus, which may include a providing unit 60, a receiving unit 62, an obtaining unit 64, and a transmitting unit 66. among them,
  • the providing unit 60 is configured to provide a correspondence between the device information and the interface identifier, where the interface identifier is used to identify a permission setting interface of the application;
  • the receiving unit 62 is configured to receive device information sent by the terminal device
  • the obtaining unit 64 is configured to acquire, according to the correspondence between the device information and the interface identifier, an interface identifier corresponding to the received device information.
  • the sending unit 66 is configured to send the acquired interface identifier to the terminal device.
  • the embodiment of the present specification further provides a terminal device.
  • the terminal device may include a display component, a processor, and a communication component.
  • the display component includes, but is not limited to, a liquid crystal display (LCD) display, a cathode ray tube (CRT) display, and a light emitting diode (LED) display.
  • the display component can be used to provide a business interface.
  • the processor can be implemented in any suitable manner.
  • a processor can employ, for example, a microprocessor or processor and a computer readable medium, logic gate, switch, or application-specific integrated circuit (such as software or firmware) that can be executed by the (micro)processor.
  • ASIC Application Specific Integrated Circuit
  • the processor may be configured to obtain, according to a triggering instruction for a control in a service interface, a scenario identifier corresponding to the control, where the scenario identifier includes a permission identifier, and detecting whether the application has the permission identifier The identified permissions.
  • the communication component includes but is not limited to a wired network card, a wireless network card, a Bluetooth module, an infrared transceiver module, an ultra-wideband communication module, and a Zigbee protocol communication module.
  • the communication component can be used to send device information to the server if not.
  • the embodiment of the present specification further provides another terminal device.
  • the terminal device may include a display component, a processor, and a communication component.
  • the communication component includes but is not limited to a wired network card, a wireless network card, a Bluetooth module, an infrared transceiver module, an ultra-wideband communication module, and a Zigbee protocol communication module.
  • the communication component may be configured to receive an interface identifier sent by the server; wherein the interface identifier is used to identify a permission setting interface of the application.
  • the display component includes, but is not limited to, a liquid crystal display (LCD) display, a cathode ray tube (CRT) display, and a light emitting diode (LED) display.
  • the display component may be configured to display a boot interface generated based on the interface identifier; and display the rights setting interface.
  • the processor can be implemented in any suitable manner.
  • a processor can employ, for example, a microprocessor or processor and a computer readable medium, logic gate, switch, or application-specific integrated circuit (such as software or firmware) that can be executed by the (micro)processor.
  • ASIC Application Specific Integrated Circuit
  • the processor may be configured to: in response to the triggering instruction that allows the permission to be opened, control the display component to display the permission setting interface; in response to the triggering instruction of the opening the target permission, open the target permission of the application; in response to the foreground Running a trigger instruction of the application to perform the function of the control in the application.
  • the embodiment of the present specification further provides a server.
  • the server can include a communication component and a processor.
  • the communication component includes but is not limited to a wired network card, a wireless network card, a Bluetooth module, an infrared transceiver module, an ultra-wideband communication module, and a Zigbee protocol communication module.
  • the communication component may be configured to receive device information sent by the terminal device, and send the acquired interface identifier to the terminal device.
  • the processor can be implemented in any suitable manner.
  • a processor can employ, for example, a microprocessor or processor and a computer readable medium, logic gate, switch, or application-specific integrated circuit (such as software or firmware) that can be executed by the (micro)processor.
  • ASIC Application Specific Integrated Circuit
  • the processor may be configured to provide a correspondence between the device information and the interface identifier, where the interface identifier is used to identify a permission setting interface of the application; and the device is acquired based on the correspondence between the device information and the interface identifier.
  • the interface identifier corresponding to the information.
  • PLD Programmable Logic Device
  • FPGA Field Programmable Gate Array
  • HDL Hardware Description Language
  • the system, device, module or unit illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product having a certain function.
  • the system, device, module or unit illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product having a certain function.
  • a typical implementation device is a computer.
  • the computer can be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or A combination of any of these devices.
  • the present specification can be implemented by means of software plus a necessary general hardware platform. Based on such understanding, the technical solution of the present specification may be embodied in the form of a software product in essence or in the form of a software product, which may be stored in a storage medium such as a ROM/RAM or a disk. , an optical disk, etc., includes instructions for causing a computer device (which may be a personal computer, server, or network device, etc.) to perform the methods described in various embodiments of the present specification or portions of the embodiments.
  • a computer device which may be a personal computer, server, or network device, etc.
  • This description can be used in a variety of general purpose or special purpose computer system environments or configurations.
  • program modules include routines, programs, objects, components, data structures, and the like that perform particular tasks or implement particular abstract data types.
  • the present specification can also be practiced in distributed computing environments where tasks are performed by remote processing devices that are connected through a communication network.
  • program modules can be located in both local and remote computer storage media including storage devices.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Human Computer Interaction (AREA)
  • Information Transfer Between Computers (AREA)
  • Telephonic Communication Services (AREA)
  • Stored Programmes (AREA)

Abstract

本说明书实施例提供一种数据处理方法和装置、终端设备、服务器。所述方法包括：提供设备信息和界面标识的对应关系；其中，所述界面标识用于标识应用程序的权限设置界面；接收终端设备发来的设备信息；基于设备信息和界面标识的对应关系，获取接收的设备信息对应的界面标识；向终端设备发送获取的界面标识。

Description

数据处理方法和装置、终端设备、服务器 技术领域
本说明书实施例涉及计算机技术领域，特别涉及一种数据处理方法和装置、终端设备、服务器。
背景技术
目前，基于操作系统的终端设备得到了快速的发展。通过操作系统，用户可以在终端设备上安装自己喜欢的应用程序来实现更多的功能。在需要执行功能时，应用程序通常需要获得操作系统内相应的权限才可执行所述功能。例如，在需要执行扫一扫功能时，应用程序通常需要获得操作系统内的摄像头权限才可执行扫一扫功能。
操作系统可以提供应用程序的权限设置界面，用户可以在权限设置界面对应用程序的一个或多个权限进行授权操作或取消授权操作。在一些情况下，用户有可能取消了应用程序的一个或多个权限。这样，在需要执行与被取消权限相关的一些功能时，应用程序通常会弹出提示信息，以提示用户需要开通被取消权限。用户需要通过一次或多次操作，进入应用程序的权限设置界面，并在权限设置界面开通被取消权限，使得整个权限开通过程操作繁琐，用户体验不高。尤其地，不同终端设备有可能运行不同的操作系统，不同操作系统中进入应用程序权限设置界面的路径不同。在用户不熟悉终端设备的情况下，用户有可能需要进行较多次数的操作或花费较长的时间，才能够进入应用程序的权限设置界面。
发明内容
本说明书实施例的目的是提供一种数据处理方法和装置、终端设备、服务器，以实现终端设备能够自行跳转到应用程序的权限设置界面，简化用户操作，提高用户体验。
为实现上述目的，本说明书实施例提供一种数据处理方法，包括：响应于针对业务界面中控件的触发指令，获取所述控件对应的场景标识；其中，所述场景标识包括权限标识；检测应用程序是否具备所述权限标识所标识的权限；若否，向服务器发送设备信息。
为实现上述目的，本说明书实施例提供一种终端设备，包括：显示组件，用于提供 业务界面；处理器，用于响应于针对业务界面中控件的触发指令，获取所述控件对应的场景标识；其中，所述场景标识包括权限标识；检测应用程序是否具备所述权限标识所标识的权限；通信组件，用于若否，向服务器发送设备信息。
为实现上述目的，本说明书实施例提供一种数据处理装置，包括：获取单元，用于响应于针对业务界面中控件的触发指令，获取所述控件对应的场景标识；其中，所述场景标识包括权限标识；检测单元，用于检测应用程序是否具备所述权限标识所标识的权限；发送单元，用于若否，向服务器发送设备信息。
为实现上述目的，本说明书实施例提供一种数据处理方法，包括：接收服务器发来的界面标识；其中，所述界面标识用于标识应用程序的权限设置界面；展示基于所述界面标识生成的引导界面；响应于允许开通权限的触发指令，进入所述权限设置界面；响应于开通目标权限的触发指令，开通所述应用程序的目标权限；响应于前台运行所述应用程序的触发指令，执行所述应用程序中控件的功能。
为实现上述目的，本说明书实施例提供一种终端设备，包括：通信组件，用于接收服务器发来的界面标识；其中，所述界面标识用于标识应用程序的权限设置界面；显示组件，用于展示基于所述界面标识生成的引导界面；展示所述权限设置界面；处理器，用于响应于允许开通权限的触发指令，控制显示组件展示所述权限设置界面；响应于开通目标权限的触发指令，开通所述应用程序的目标权限；响应于前台运行所述应用程序的触发指令，执行所述应用程序中控件的功能。
为实现上述目的，本说明书实施例提供一种数据处理装置，包括：接收单元，用于接收服务器发来的界面标识；其中，所述界面标识用于标识应用程序的权限设置界面；展示单元，用于展示基于所述界面标识生成的引导界面；进入单元，用于响应于允许开通权限的触发指令，进入所述权限设置界面；开通单元，用于响应于开通目标权限的触发指令，开通所述应用程序的目标权限；执行单元，用于响应于前台运行所述应用程序的触发指令，执行所述应用程序中控件的功能。
为实现上述目的，本说明书实施例提供一种数据处理方法，包括：提供设备信息和界面标识的对应关系；其中，所述界面标识用于标识应用程序的权限设置界面；接收终端设备发来的设备信息；基于设备信息和界面标识的对应关系，获取接收的设备信息对应的界面标识；向终端设备发送获取的界面标识。
为实现上述目的，本说明书实施例提供一种服务器，包括：通信组件，用于接收终 端设备发来的设备信息；向终端设备发送获取的界面标识。处理器，用于提供设备信息和界面标识的对应关系；其中，所述界面标识用于标识应用程序的权限设置界面；基于设备信息和界面标识的对应关系，获取接收的设备信息对应的界面标识。
为实现上述目的，本说明书实施例提供一种数据处理装置，包括：提供单元，用于提供设备信息和界面标识的对应关系；其中，所述界面标识用于标识应用程序的权限设置界面；接收单元，用于接收终端设备发来的设备信息；获取单元，用于基于设备信息和界面标识的对应关系，获取接收的设备信息对应的界面标识；发送单元，用于向终端设备发送获取的界面标识。
由以上本说明书实施例提供的技术方案可见，本说明书实施例中服务器可以提供设备信息和界面标识的对应关系；可以接收终端设备发来的设备信息；可以基于设备信息和界面标识的对应关系，获取接收的设备信息对应的界面标识；可以向终端设备发送获取的界面标识。这样，服务器可以根据终端设备发来的设备信息，向终端设备下发适合于该终端设备的界面标识，使得终端设备可以自行跳转到界面标识所标识的权限设置界面，便于用户在权限设置界面开通应用程序的权限，从而简化了用户操作，提高了用户体验。
附图说明
为了更清楚地说明本说明书实施例或现有技术中的技术方案，下面将对实施例或现有技术描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本说明书中记载的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动性的前提下，还可以根据这些附图获得其他的附图。
图1为本说明书实施例一种数据处理方法的流程图；
图2为本说明书实施例一种业务界面的示意图；
图3为本说明书实施例一种引导界面的示意图；
图4为本说明书实施例一种提示信息的示意图；
图5为本说明书实施例一种权限设置界面的示意图；
图6为本说明书实施例一种用户在权限设置界面开通目标权限的示意图；
图7为本说明书实施例一种用户进行应用程序返回前台运行的操作的示意图；
图8为本说明书实施例一种执行扫一扫功能的示意图；
图9为本说明书实施例一种数据处理方法的流程图；
图10为本说明书实施例一种数据处理方法的流程图；
图11为本说明书实施例一种数据处理方法的流程图；
图12为本说明书实施例一种数据处理装置的功能结构示意图；
图13为本说明书实施例一种数据处理装置的功能结构示意图；
图14为本说明书实施例一种数据处理装置的功能结构示意图；
图15为本说明书实施例一种终端设备的功能结构示意图；
图16为本说明书实施例一种服务器的功能结构示意图。
具体实施方式
下面将结合本说明书实施例中的附图，对本说明书实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅仅是本说明书一部分实施例，而不是全部的实施例。基于本说明书中的实施例，本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例，都应当属于本说明书保护的范围。
请一并参阅图1、图2、图3、图4、图5、图6、图7和图8。本说明书实施例提供一种数据处理系统。
在本实施例中，所述数据处理系统可以包括终端设备。所述终端设备可以具有显示功能。具体地，所述终端设备可以包括智能手机、平板电子设备、网络机顶盒、便携式计算机、台式电脑、个人数字助理(PDA)、车载设备、智能穿戴设备等。其中，所述智能穿戴设备可以包括智能眼镜、智能手表、智能手环等。
所述终端设备可以运行有操作系统(Operating System，OS)。所述操作系统可以为控制和管理硬件和软件资源的计算机程序。具体地，所述操作系统可以包括安卓操作系统(谷歌公司开发的操作系统)、IOS操作系统(苹果公司开发的操作系统)、Windows操作系统(微软公司开发的操作系统)。当然，所述操作系统还可以包括基于上述操作系统进一步优化、定制处理的操作系统。例如，MIUI操作系统(小米公司基于安卓操作系统开发的手机操作系统)、EMUI操作系统(华为公司基于安卓操作系统开发的手机操作系统)等。
所述操作系统中可以运行有应用程序。所述操作系统可以对应用程序的权限进行管理。应用程序的权限可以包括普通权限(Normal Permissions)和敏感权限(Dangerous Permissions)。普通权限例如可以包括震动、访问网络等。普通权限通常不涉及用户隐私。普通权限在应用程序安装时获得授权，通常不需要用户进行授权。敏感权限例如可以包括调用摄像头、读取位置信息、允许消息通知等。敏感权限通常涉及用户隐私。敏感权限通常需要用户进行授权。具体地，操作系统可以提供应用程序的权限设置界面，用户可以在权限设置界面对应用程序的一个或多个敏感权限进行授权操作或取消授权操作。针对不同的应用程序，操作系统提供的权限设置界面可以相同或不同。在本实施例的一个实施方式中，在一些情况下，在开发应用程序的过程中，为了缩短开发时间、简化开发流程，开发人员可以将已经开发好的具有某种功能的软件开发工具包(Software Development Kit，SDK)，嵌入到应用程序中，如此，所述操作系统中的应用程序可以嵌入有软件开发工具包。
在本实施例中，所述数据处理系统还可以包括服务器。所述服务器可以为一个服务器，还可以为包括多个服务器的服务器集群。所述服务器例如可以包括支付宝服务器、微信服务器、蚂蚁财富服务器、京东服务器等。
所述服务器可以与所述终端设备进行通信。所述服务器与所述终端设备之间可以使用任何合适的网络协议进行通信，包括在本文件提交日尚未开发出的网络协议。所述网络协议例如可以包括TCP/IP协议、UDP/IP协议、HTTP协议、HTTPS协议等。当然，所述网络协议例如还可以包括在上述协议之上使用的RPC协议(Remote Procedure Call Protocol，远程过程调用协议)、REST协议(Representational State Transfer，表述性状态转移协议)等。
在本实施例中，所述终端设备可以运行操作系统中的应用程序进而提供业务界面。所述应用程序例如可以包括支付宝、微信、蚂蚁财富、京东手机客户端等。具体地，操作系统中的应用程序在运行后，可以默认提供所述业务界面。或者，操作系统中的应用程序在运行后，响应于提供业务界面的第一触发指令，可以提供所述业务界面。所述第一触发指令可以是在检测到一个或多个按键的任意组合，被按下、点击、双击、或划过时产生的。所述按键可以包括物理按键和控件等。
所述业务界面可以用于展示业务数据，所述业务数据例如可以包括订单数据、支付数据、商品数据等。所述业务界面可以具有一个或多个控件，所述控件可以包括按钮控件、图像控件、文本框控件、输入框控件等。所述业务界面中的部分或全部控件可以对 应有场景标识，所述场景标识可以用于标识业务场景。所述场景标识具体可以包括业务标识和权限标识。所述业务标识可以用于标识业务场景涉及到的业务。所述权限标识可以用于标识业务场景需要使用到的权限。所述权限标识所标识的权限可以为普通权限或敏感权限。其中，所述场景标识可以由业务标识和权限标识拼接得到。当然，所述场景标识还可以基于其它方式得到。例如，可以将业务标识和权限标识进行编码进而得到所述场景标识。
例如，所述业务界面可以具有扫一扫按钮控件。所述扫一扫按钮控件可以对应有场景标识Pay_Camera，所述场景标识Pay_Camera可以用于标识扫一扫业务场景。所述场景标识Pay_Camera可以包括业务标识Pay和权限标识Camera，所述业务标识Pay可以用于标识扫码支付业务，所述权限标识Camera可以用于标识扫一扫业务场景需要使用到的调用摄像头权限。
另举一例，所述业务界面可以具有活动提醒按钮控件。所述活动提醒按钮控件可以对应有场景标识Push_Notifaction，所述场景标识Push_Notifaction可以用于标识活动提醒业务场景。所述场景标识Push_Notifaction可以包括业务标识Push和权限标识Notifaction，所述业务标识Push可以用于标识消息推送业务，所述权限标识Notifaction可以用于标识活动提醒业务场景需要使用到的允许消息通知权限。
在本实施例中，所述终端设备可以检测业务界面中的控件是否被单击、双击、按下超过预定时间(或称为长按)、或划过进而产生第二触发指令；可以获取第二触发指令针对控件对应的场景标识；可以解析获取的场景标识，得到权限标识；可以检测应用程序是否具备权限标识所标识的权限；若否，可以向服务器发送自身的设备信息。其中，这里的应用程序可以为前述用于提供业务界面的应用程序。
具体地，应用程序可以产生第二触发指令；可以获取第二触发指令针对控件对应的场景标识；可以解析获取的场景标识，得到权限标识；可以使用自身的应用标识和权限标识，调用操作系统中的权限检测方法，以检测自身是否具备权限标识所标识的权限；若否，可以调用操作系统中的设备信息获取方法，获取终端设备的设备信息；可以向服务器发送获取的设备信息。其中，
所述应用标识可以用于标识应用程序，例如可以为应用程序的包名(PackageName)等。
所述权限检测方法可以包括权限检测函数。例如，所述操作系统可以为安卓操作系 统，安卓操作系统中的权限检测函数可以为AppOpsManager.checkOpThrow。AppOpsManager.checkOpThrow被调用以后，安卓操作系统可以从自身的应用权限管理器中查询应用标识所标识的应用程序是否具备权限标识所标识的权限；若是，可以向应用程序返回AppOpsManager.Mode_Allowed；若否，可以向应用程序返回AppOpsManager.Mode_Ignore。
所述设备信息可以包括厂商标识、设备型号标识和操作系统版本标识中的一个或多个。所述厂商标识可以用于标识终端设备的生产厂商，例如可以包括HW(华为厂商)、MI(小米厂商)、Apple(苹果厂商)等。所述设备型号标识可以用于标识终端设备的型号，例如可以包括PE_TL10(华为公司生产的一款手机的型号)等。所述操作系统版本标识可以用于标识操作系统的版本，例如可以包括MIUI9.0(小米公司开发操作系统的一个版本)、EMUI3.0(华为公司开发操作系统的一个版本)等。当然，所述设备信息还可以包括其它的数据，本实施例对此并不做具体限定。
所述设备信息获取方法可以包括设备信息获取函数。例如，所述操作系统可以为安卓操作系统，所述设备信息获取函数可以包括厂商标识获取函数getDeviceBrand、设备型号标识获取函数getSystemModel、操作系统版本获取函数getSystemVersion等。
在本实施例中，不同终端设备上运行的操作系统可能不同，不同操作系统中应用程序的权限设置界面的路径可能不同。例如，蚂蚁财富在华为智能手机和小米智能手机上权限设置界面的路径是不同的。为了便于根据设备信息，向终端设备下发合适的用于跳转到权限设置界面的界面标识，所述服务器可以提供设备信息和界面标识的对应关系。其中，所述界面标识可以用于标识应用程序的权限设置界面。具体地，例如，所述界面标识可以为基于URL Scheme协议实现的链接地址。例如，设备信息和界面标识的对应关系可以包括厂商标识、设备型号标识和操作系统版本标识中的一个或多个的组合，和界面标识的对应关系。例如，所述服务器可以提供HW、PE_TL10、EMUI3.0共同与界面标识IDA的对应关系；可以提供MI、NOTE3、MIUI9.0共同与界面标识IDB的对应关系。
如此，所述服务器可以接收终端设备发来的设备信息；可以基于设备信息和界面标识的对应关系，获取接收的设备信息对应的界面标识；可以向终端设备发送获取的界面标识。
在本实施例中，所述终端设备可以接收服务器发来的界面标识；可以展示基于接收的界面标识生成的引导界面；响应于在引导界面接收到的允许开通权限的第三触发指 令，可以进入界面标识所标识的权限设置界面。
具体地，应用程序中可以嵌入有统一的引导模板。如此，应用程序可以接收服务器发来的界面标识；可以从本地获取引导模板；可以将界面标识嵌入从本地获取的引导模板内，得到引导界面；可以展示引导界面。其中，这里的应用程序可以为前述用于提供业务界面的应用程序。这样，终端设备与服务器之间可以不必传输引导模板，从而可以减少终端设备与服务器之间的通信数据量。
具体地，所述引导界面可以具有第一控件，所述第一控件可以为按钮控件或图像控件等。所述第一控件可以对应有界面标识，用于产生允许开通权限的第三触发指令。应用程序可以检测第一控件是否被单击、双击、按下超过预定时间、或划过进而产生第三触发指令；响应于第三触发指令，可以获取第一控件对应的界面标识；可以跳转到界面标识所标识的权限设置界面。其中，这里的应用程序可以为前述用于提供业务界面的应用程序。当然，应用程序还可以采用其它的方式产生第三触发指令，本实施例对此并不做具体限定。
在本实施例中，所述终端设备响应于在权限设置界面接收到的开通目标权限的第五触发指令，可以开通应用程序的目标权限；响应于在权限设置界面接收到的前台运行应用程序的第六触发指令，可以执行控件对应的功能。其中，这里的目标权限可以为前述场景标识中的权限标识所标识的权限；这里的应用程序可以为前述用于提供业务界面的应用程序。
权限设置界面可以是终端设备中的操作系统提供的。权限设置界面可以具有一个或多个控件，每个控件可以对应一个权限。操作系统可以检测权限设置界面中的控件是否被单击、双击、按下超过预定时间、或划过进而产生开通该控件所对应权限的触发指令。当然，操作系统还可以采用其它的方式产生开通权限的触发指令，本实施例对此并不做具体限定。例如，操作系统中可以预置一个或多个手势，每个手势可以对应权限设置界面中的一个权限。操作系统在识别到手势时，可以产生开通该手势所对应权限的触发指令。
应用程序可以在前台运行，也可以在后台运行。应用程序在前台运行时，终端设备的显示屏幕内可以显示有应用程序的界面。应用程序在后台运行时，终端设备的显示屏幕内通常不显示应用程序的界面；此时，应用程序通常在操作系统的资源管理器内运行，并占用系统资源。在本实施例中，鉴于权限设置界面通常是操作系统提供的，终端设备在由引导界面进入权限设置界面以后，应用程序通常在前台运行更改为在后台运行。用 户在权限设置界面开通目标权限以后，可以进行触发操作以使应用程序在后台运行更改为在前台运行。具体地，权限设置界面可以包括返回控件，返回控件可以为按钮控件或图像控件等。操作系统可以检测返回控件是否被单击、双击、按下超过预定时间、或划过进而产生前台运行应用程序的第六触发指令。当然，操作系统还可以采用其它的方式产生第六触发指令，本实施例对此并不做具体限定。
在本实施例的一个实施方式中，所述终端设备在检测到应用程序具备权限标识所标识的权限时，还可以执行第二触发指令针对控件对应的功能。第二触发指令针对控件对应的功能例如可以包括扫一扫功能、允许推送活动信息功能等。
具体地，应用程序可以产生第二触发指令；可以获取第二触发指令针对控件对应的场景标识；可以解析获取的场景标识，得到权限标识；可以使用自身的应用标识和权限标识，调用操作系统中的权限检测方法，以检测自身是否具备权限标识所标识的权限；若是，可以执行第二触发指令针对控件对应的功能。
在本实施例的一个实施方式中，为了使终端设备能够基于不同的业务场景展示不同的引导界面，以提高用户体验，所述服务器还可以提供业务标识和引导模板的对应关系。每个引导模板可以对应一个或多个业务标识，每个业务标识可以对应一个引导模板。所述引导模板可以具有用于提示用户所需要开通权限的提示信息，提示信息可以为文字、声音、图像、视频或其任意组合等。所述引导模板可以用于生成引导界面。所述引导界面可以用于引导用户开通应用程序的权限。
在本实施方式中，所述终端设备在检测到应用程序不具备权限标识所标识的权限时，还可以向服务器发送场景标识。其中，这里的场景标识可以为前述第二触发指令针对控件对应的场景标识。
所述服务器可以接收终端设备发来的场景标识；可以解析接收的场景标识，得到业务标识；可以基于业务标识和引导模板的对应关系，获取业务标识对应的引导模板；可以向终端设备发送获取的引导模板。
所述终端设备可以接收服务器发来的引导模板；可以将界面标识嵌入来自服务器的引导模板内，得到引导界面；可以展示引导界面。这样，终端设备能够根据基于不同的业务场景展示不同的引导界面，提高用户体验。具体地，应用程序可以接收服务器发来的引导模板；可以将界面标识嵌入来自服务器的引导模板内，得到引导界面；可以展示引导界面。
在本实施例的一个实施方式中，所述终端设备响应于在引导界面接收到的拒绝开通权限的第四触发指令，还可以展示提示信息。具体地，所述引导界面还可以具有第二控件。所述第二控件可以为按钮控件或图像控件等。所述第二控件可以用于产生拒绝开通权限的第四触发指令。应用程序还可以检测第二控件是否被单击、双击、按下超过预定时间、或划过进而产生第四触发指令；响应于第四触发指令，可以展示提示信息，提示信息可以为文字、声音、图像、视频或其任意组合等，提示信息例如可以为文字信息“检测到您拒绝开通摄像头权限。您无法使用扫一扫功能”。
请一并参阅图1、图2、图3、图4、图5、图6、图7和图8。以下介绍本说明书实施例的一个场景示例。
在本场景示例中，所述终端设备可以为智能手机。所述智能手机可以运行有EMUI3.0操作系统。所述EMUI3.0操作系统中可以运行有蚂蚁财富应用程序。所述服务器可以为蚂蚁财富服务器。
在本场景示例中，所述智能手机可以运行蚂蚁财富应用程序进而提供业务界面。所述业务界面可以具有扫一扫按钮控件。所述扫一扫按钮控件可以对应有场景标识Pay_Camera，所述场景标识Pay_Camera可以用于标识扫一扫业务场景。所述场景标识Pay_Camera可以包括业务标识Pay和权限标识Camera，所述业务标识Pay可以用于标识扫码支付业务，所述权限标识Camera可以用于标识扫一扫业务场景需要使用到的调用摄像头权限。
在本场景示例中，所述智能手机在检测到扫一扫按钮控件被单击、双击、按下超过预定时间、或划过以后，可以产生触发指令；响应于该触发指令，可以获取扫一扫按钮控件对应的场景标识Pay_Camera；可以解析场景标识Pay_Camera，得到权限标识Camera；可以检测蚂蚁财富应用程序是否具备调用摄像头权限；若是，可以执行扫一扫按钮控件对应的扫一扫功能；若否，可以向蚂蚁财富服务器发送操作系统版本标识EMUI3.0和场景标识Pay_Camera，以便于引导用户开通蚂蚁财富应用程序的调用摄像头权限。
在本场景示例中，蚂蚁财富服务器可以提供操作系统版本标识EMUI3.0和界面标识IDA的对应关系；可以提供业务标识Pay和引导模板TA的对应关系。如此，蚂蚁财富服务器可以接收智能手机发来的操作系统版本标识EMUI3.0和场景标识Pay_Camera；可以获取操作系统版本标识EMUI3.0对应的界面标识IDA；可以解析场景标识Pay_Camera，得到业务标识Pay；可以获取业务标识Pay对应的引导模板TA；可以向 智能手机返回界面标识IDA和引导模板TA。
在本场景示例中，智能手机可以接收蚂蚁财富服务器发来的界面标识IDA和引导模板TA；可以展示基于界面标识IDA和引导模板TA生成的引导界面；响应于在该引导界面接收到的允许开通权限的触发指令，可以进入界面标识IDA所标识的权限设置界面；或者，响应于在该引导界面接收到的拒绝开通权限的触发指令，可以展示文字提示信息“您的相机功能好像没有打开哦～”。
在本场景示例中，智能手机响应于在权限设置界面接收到的开通调用摄像头权限的触发指令，可以开通蚂蚁财富应用程序的调用摄像头权限；响应于在权限设置界面接收到的前台运行蚂蚁财富应用程序的触发指令，可以执行扫一扫按钮控件对应的扫一扫功能。
请参阅图9。本说明书实施例提供一种数据处理方法。所述数据处理方法以终端设备为执行主体，可以包括以下步骤。
步骤S10：响应于针对业务界面中控件的触发指令，获取所述控件对应的场景标识。
在本实施例中，所述业务界面可以是所述终端设备中的应用程序提供的，以用于展示业务数据。所述业务数据例如可以包括订单数据、支付数据、商品数据等。所述业务界面可以具有一个或多个控件，所述控件可以包括按钮控件、图像控件、文本框控件、输入框控件等。所述业务界面中的部分或全部控件可以对应有场景标识，所述场景标识可以用于标识业务场景。所述场景标识具体可以包括业务标识和权限标识。所述业务标识可以用于标识业务场景涉及到的业务。所述权限标识可以用于标识业务场景需要使用到的权限。
在本实施例中，所述终端设备中的应用程序可以检测业务界面中的控件是否被单击、双击、按下超过预定时间、或划过进而产生触发指令；响应于所述触发指令，可以获取所述触发指令针对控件对应的场景标识。
步骤S12：检测应用程序是否具备所述权限标识所标识的权限。
在本实施例中，所述终端设备中的应用程序可以解析场景标识，得到权限标识；可以检测自身是否具备权限标识所标识的权限。其中，这里的应用程序可以为前述用于提供业务界面的应用程序。
步骤S14：若否，向服务器发送设备信息。
在本实施例中，若否，所述终端设备中的应用程序可以获取所述终端设备的设备信息；可以向服务器发送所述设备信息。所述设备信息包括厂商标识、型号标识和操作系统版本标识中的一个或多个。在本实施例的一个实施方式中，若否，所述终端设备中的应用程序还可以向服务器发送所述场景标识。
在本实施例的一个实施方式中，若是，所述终端设备中的应用程序还可以执行控件对应的功能。其中，这里的控件可以为前述触发指令针对的控件。
在本实施例中，所述终端设备响应于针对业务界面中控件的触发指令，可以获取所述控件对应的场景标识，所述场景标识可以包括权限标识；可以检测应用程序是否具备所述权限标识所标识的权限；若否，可以向服务器发送设备信息。这样，所述终端设备在检测到应用程序不具备当前业务场景所需的权限时，可以向服务器发送自身的设备信息，以便于能够接收用于跳转到权限设置界面的界面标识，从而引导用户开通当前业务场景所需的权限。
请参阅图10。本说明书实施例还提供另一种数据处理方法。所述数据处理方法以终端设备为执行主体，可以包括以下步骤。
步骤S20：接收服务器发来的界面标识。
在本实施例中，所述界面标识可以用于标识应用程序的权限设置界面。具体地，例如，所述界面标识可以为基于URL Scheme协议实现的链接地址。
在本实施例中，所述终端设备中的应用程序可以向服务器发送设备信息，可以接收服务器发来的与所述设备信息对应的界面标识。
步骤S22：展示基于所述界面标识生成的引导界面。
在本实施例中，所述终端设备中的应用程序可以获取引导模板；可以基于所述引导模板和所述界面标识生成引导界面；可以展示引导界面。所述引导模板可以具有用于提示用户所需要开通权限的提示信息，提示信息可以为文字、声音、图像、视频或其任意组合等。所述引导模板可以用于生成引导界面。所述引导界面可以用于引导用户开通应用程序的权限。
在本实施例的一个实施方式中，所述终端设备中的应用程序可以嵌入有统一的引导模板。如此，所述终端设备中的应用程序可以从本地获取引导模板。这样，终端设备与服务器之间可以不必传输引导模板，从而可以减少终端设备与服务器之间的通信数据量。
在本实施例的另一个实施方式中，所述终端设备中的应用程序可以向服务器发送场景标识；可以接收服务器发来的与场景标识中业务标识相对应的引导模板。这样，终端设备能够根据基于不同的业务场景展示不同的引导界面，提高用户体验。关于场景标识的详细介绍可以参见前述实施例，在此不再赘述。
步骤S24：响应于允许开通权限的触发指令，进入权限设置界面。
在本实施例中，所述引导界面可以具有第一控件。所述第一控件可以对应有所述界面标识，用于产生允许开通权限的触发指令。如此，所述终端设备中的应用程序可以检测第一控件是否被单击、双击、按下超过预定时间、或划过进而产生允许开通权限的触发指令；响应于允许开通权限的触发指令；可以进入所述界面标识所标识的权限设置界面。
步骤S26：响应于开通目标权限的触发指令，开通所述应用的目标权限。
在本实施例中，所述目标权限可以为场景标识中的权限标识所标识的权限。
在本实施例中，所述终端设备可以运行有操作系统。权限设置界面可以是所述操作系统提供的。权限设置界面可以具有一个或多个控件，每个控件可以对应一个权限。所述操作系统可以检测权限设置界面中的控件是否被单击、双击、按下超过预定时间、或划过进而产生开通该控件所对应权限的触发指令。当然，所述操作系统还可以采用其它的方式产生开通权限的触发指令，本实施例对此并不做具体限定。例如，所述操作系统中可以预置一个或多个手势，每个手势可以对应权限设置界面中的一个权限。所述操作系统在识别到手势时，可以产生开通该手势所对应权限的触发指令。
步骤S28：响应于前台运行所述应用程序的触发指令，执行所述应用程序中控件的功能。
在本实施例中，所述终端设备中的应用程序可以在前台运行，也可以在后台运行。应用程序在前台运行时，终端设备的显示屏幕内可以显示有应用程序的界面。应用程序在后台运行时，终端设备的显示屏幕内通常不显示应用程序的界面；此时，应用程序通常在操作系统的资源管理器内运行，并占用系统资源。在本实施例中，鉴于权限设置界面通常是操作系统提供的，终端设备在由引导界面进入权限设置界面以后，应用程序在前台运行更改为在后台运行。用户在权限设置界面开通目标权限以后，可以进行触发操作以使应用程序在后台运行更改为在前台运行。具体地，权限设置界面可以包括返回控件，返回控件可以为按钮控件或图像控件等。操作系统可以检测返回控件是否被单击、 双击、按下超过预定时间、或划过进而产生前台运行应用程序的触发指令。当然，操作系统还可以采用其它的方式产生前台运行应用程序的触发指令，本实施例对此并不做具体限定。
在本实施例的一个实施方式中，所述引导界面还可以具有第二控件。所述第二控件可以用于产生拒绝开通权限的触发指令。具体地，所述终端设备中的应用程序可以检测第二控件是否被单击、双击、按下超过预定时间、或划过进而产生拒绝开通权限的触发指令；响应于拒绝开通权限的触发指令，可以展示提示信息。提示信息可以为文字、声音、图像、视频或其任意组合等，提示信息例如可以为文字信息“检测到您拒绝开通摄像头权限。您无法使用扫一扫功能”。
在本实施例中，所述终端设备可以接收服务器发来的界面标识；可以展示基于所述界面标识生成的引导界面；响应于允许开通权限的触发指令，可以进入权限设置界面；响应于开通目标权限的触发指令，可以开通所述应用的目标权限；响应于前台运行所述应用程序的触发指令，可以执行所述应用程序中控件的功能。这样，所述终端设备可以接收服务器发来的界面标识；可以基于界面标识自行跳转至权限设置界面；便于用户在权限设置界面开通应用程序的权限，从而简化了用户操作，提高了用户体验。
请参阅图11。本说明书实施例还提供另一种数据处理方法。所述数据处理方法以服务器为执行主体，可以包括以下步骤。
步骤S30：提供设备信息和界面标识的对应关系。
在本实施例中，所述设备信息可以包括厂商标识、设备型号标识和操作系统版本标识中的一个或多个。所述界面标识可以用于标识应用程序的权限设置界面。具体地，例如，所述界面标识可以为基于URL Scheme协议实现的链接地址。例如，所述设备信息和界面标识的对应关系可以包括厂商标识、设备型号标识和操作系统版本标识中的一个或多个的组合，和界面标识的对应关系。当然，所述设备信息还可以包括其它的数据，本实施例对此并不做具体限定。
在本实施例中，开发人员可以采集应用程序在一个或多个终端设备的界面标识；可以在服务器设定终端设备的设备信息与所述应用程序在该终端设备的界面标识之间的对应关系。
步骤S32：接收终端设备发来的设备信息。
在本实施例中，所述终端设备可以向服务器发送自身的设备信息，所述服务器 可以接收终端设备发来的设备信息。
步骤S34：基于设备信息和界面标识的对应关系，获取接收的设备信息对应的界面标识。
步骤S36：向终端设备发送获取的界面标识。
在本实施例的一个实施方式中，所述服务器还可以提供默认界面标识。所述默认界面标识可以用于标识应用程序在普通多数终端设备中的权限设置界面。如此，所述服务器可以在没有获取到接收设备信息对应的界面标识时，可以认为所述默认界面标识与接收设备信息具有对应关系；可以获取所述默认界面标识；可以向终端设备发送所述默认界面标识。
在本实施例的一个实施方式中，所述服务器还可以提供业务标识和引导模板的对应关系。所述业务标识可以用于标识业务场景涉及到的业务。所述引导模板可以具有用于提示用户所需要开通权限的提示信息，提示信息可以为文字、声音、图像、视频或其任意组合等。所述引导模板可以用于生成引导界面。所述引导界面可以用于引导用户开通应用程序的权限。如此，所述服务器可以接收终端设备发来的场景标识；可以基于业务标识和引导模板的对应关系，获取接收的业务标识对应的引导模板；可以向终端设备发送获取的引导模板。
在本实施例中，所述服务器可以提供设备信息和界面标识的对应关系；可以接收终端设备发来的设备信息；可以基于设备信息和界面标识的对应关系，获取接收的设备信息对应的界面标识；可以向终端设备发送获取的界面标识。这样，服务器可以根据终端设备发来的设备信息，向终端设备下发适合于该终端设备的界面标识，使得终端设备可以自行跳转到界面标识所标识的权限设置界面，便于用户在权限设置界面开通应用程序的权限，从而简化了用户操作，提高了用户体验。
请参阅图12。本说明书实施例还提供一种数据处理装置，所述数据处理装置可以包括获取单元40、检测单元42和发送单元44。其中，
获取单元40，用于响应于针对业务界面中控件的触发指令，获取所述控件对应的场景标识；其中，所述场景标识包括权限标识；
检测单元42，用于检测应用程序是否具备所述权限标识所标识的权限；
发送单元44，用于若否，向服务器发送设备信息。
请参阅图13。本说明书实施例还提供另一种数据处理装置，所述数据处理装置可以包括接收单元50、展示单元52、进入单元54、开通单元56和执行单元58。其中，
接收单元50，用于接收服务器发来的界面标识；其中，所述界面标识用于标识应用程序的权限设置界面；
展示单元52，用于展示基于所述界面标识生成的引导界面；
进入单元54，用于响应于允许开通权限的触发指令，进入所述权限设置界面；
开通单元56，用于响应于开通目标权限的触发指令，开通所述应用程序的目标权限；
执行单元58，用于响应于前台运行所述应用程序的触发指令，执行所述应用程序中控件的功能。
请参阅图14。本说明书实施例还提供另一种数据处理装置，所述数据处理装置可以包括提供单元60、接收单元62、获取单元64和发送单元66。其中，
提供单元60，用于提供设备信息和界面标识的对应关系；其中，所述界面标识用于标识应用程序的权限设置界面；
接收单元62，用于接收终端设备发来的设备信息；
获取单元64，用于基于设备信息和界面标识的对应关系，获取接收的设备信息对应的界面标识；
发送单元66，用于向终端设备发送获取的界面标识。
请参阅图15。本说明书实施例还提供一种终端设备。所述终端设备可以包括显示组件、处理器和通信组件。
在本实施例中，所述显示组件包括但不限于液晶(Liquid Crystal Display，LCD)显示器、阴极射线管(Cathode Ray Tube，CRT)显示器、和发光二极管(Light Emitting Diode，LED)显示器等。具体地，所述显示组件可以用于提供业务界面。
在本实施例中，所述处理器可以按任何适当的方式实现。例如，处理器可以采取例如微处理器或处理器以及存储可由该(微)处理器执行的计算机可读程序代码(例如软件或固件)的计算机可读介质、逻辑门、开关、专用集成电路(Application Specific Integrated Circuit，ASIC)、可编程逻辑控制器和嵌入微控制器的形式等等。具体地，所述处理器，可以用于响应于针对业务界面中控件的触发指令，获取所述控件对应的场 景标识；其中，所述场景标识包括权限标识；检测应用程序是否具备所述权限标识所标识的权限。
在本实施例中，所述通信组件包括但不限于有线网卡、无线网卡、蓝牙模块、红外收发模块、超宽带通信模块、以及紫蜂协议通信模块等。具体地，所述通信组件可以用于若否，向服务器发送设备信息。
请参阅图15。本说明书实施例还提供另一种终端设备。所述终端设备可以包括显示组件、处理器和通信组件。
在本实施例中，所述通信组件包括但不限于有线网卡、无线网卡、蓝牙模块、红外收发模块、超宽带通信模块、以及紫蜂协议通信模块等。具体地，所述通信组件可以用于接收服务器发来的界面标识；其中，所述界面标识用于标识应用程序的权限设置界面。
在本实施例中，所述显示组件包括但不限于液晶(Liquid Crystal Display，LCD)显示器、阴极射线管(Cathode Ray Tube，CRT)显示器、和发光二极管(Light Emitting Diode，LED)显示器等。具体地，所述显示组件可以用于展示基于所述界面标识生成的引导界面；展示所述权限设置界面。
在本实施例中，所述处理器可以按任何适当的方式实现。例如，处理器可以采取例如微处理器或处理器以及存储可由该(微)处理器执行的计算机可读程序代码(例如软件或固件)的计算机可读介质、逻辑门、开关、专用集成电路(Application Specific Integrated Circuit，ASIC)、可编程逻辑控制器和嵌入微控制器的形式等等。具体地，所述处理器可以用于响应于允许开通权限的触发指令，控制显示组件展示所述权限设置界面；响应于开通目标权限的触发指令，开通所述应用程序的目标权限；响应于前台运行所述应用程序的触发指令，执行所述应用程序中控件的功能。
请参阅图16。本说明书实施例还提供一种服务器。所述服务器可以包括通信组件和处理器。
在本实施例中，所述通信组件包括但不限于有线网卡、无线网卡、蓝牙模块、红外收发模块、超宽带通信模块、以及紫蜂协议通信模块等。具体地，所述通信组件可以用于接收终端设备发来的设备信息；向终端设备发送获取的界面标识。
在本实施例中，所述处理器可以按任何适当的方式实现。例如，处理器可以采取例如微处理器或处理器以及存储可由该(微)处理器执行的计算机可读程序代码(例 如软件或固件)的计算机可读介质、逻辑门、开关、专用集成电路(Application Specific Integrated Circuit，ASIC)、可编程逻辑控制器和嵌入微控制器的形式等等。具体地，所述处理器可以用于提供设备信息和界面标识的对应关系；其中，所述界面标识用于标识应用程序的权限设置界面；基于设备信息和界面标识的对应关系，获取接收的设备信息对应的界面标识。
需要说明的是，本说明书中的各个实施例均采用递进的方式描述，各个实施例之间相同/相似的部分互相参见即可，每个实施例重点说明的都是与其它实施例的不同之处。尤其，对于数据处理装置实施例、终端设备实施例和服务器实施例而言，由于其基本相似于数据处理方法实施例，所以描述的比较简单，相关之处参见数据处理方法实施例的部分说明即可。
另外，可以理解的是，所属领域技术人员在阅读本说明书文件之后，可以无需创造性劳动想到本说明书文件中列举的部分或全部实施例之间可以组合，这些组合也在本说明书公开和保护的范围内。
在20世纪90年代，对于一个技术的改进可以很明显地区分是硬件上的改进(例如，对二极管、晶体管、开关等电路结构的改进)还是软件上的改进(对于方法流程的改进)。然而，随着技术的发展，当今的很多方法流程的改进已经可以视为硬件电路结构的直接改进。设计人员几乎都通过将改进的方法流程编程到硬件电路中来得到相应的硬件电路结构。因此，不能说一个方法流程的改进就不能用硬件实体模块来实现。例如，可编程逻辑器件(Programmable Logic Device,PLD)(例如现场可编程门阵列(Field Programmable Gate Array，FPGA))就是这样一种集成电路，其逻辑功能由用户对器件编程来确定。由设计人员自行编程来把一个数字系统“集成”在一片PLD上，而不需要请芯片制造厂商来设计和制作专用的集成电路芯片2。而且，如今，取代手工地制作集成电路芯片，这种编程也多半改用“逻辑编译器(logic compiler)”软件来实现，它与程序开发撰写时所用的软件编译器相类似，而要编译之前的原始代码也得用特定的编程语言来撰写，此称之为硬件描述语言(Hardware Description Language，HDL)，而HDL也并非仅有一种，而是有许多种，如ABEL(Advanced Boolean Expression Language)、AHDL(Altera Hardware Description Language)、Confluence、CUPL(Cornell University Programming Language)、HDCal、JHDL(Java Hardware Description Language)、Lava、Lola、MyHDL、PALASM、RHDL(Ruby Hardware Description Language)等，目前最普遍使用的是VHDL(Very-High-Speed Integrated Circuit Hardware Description  Language)与Verilog2。本领域技术人员也应该清楚，只需要将方法流程用上述几种硬件描述语言稍作逻辑编程并编程到集成电路中，就可以很容易得到实现该逻辑方法流程的硬件电路。
上述实施例阐明的系统、装置、模块或单元，具体可以由计算机芯片或实体实现，或者由具有某种功能的产品来实现。
上述实施例阐明的系统、装置、模块或单元，具体可以由计算机芯片或实体实现，或者由具有某种功能的产品来实现。一种典型的实现设备为计算机。具体的，计算机例如可以为个人计算机、膝上型计算机、蜂窝电话、相机电话、智能电话、个人数字助理、媒体播放器、导航设备、电子邮件设备、游戏控制台、平板计算机、可穿戴设备或者这些设备中的任何设备的组合。
通过以上的实施方式的描述可知，本领域的技术人员可以清楚地了解到本说明书可借助软件加必需的通用硬件平台的方式来实现。基于这样的理解，本说明书的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品可以存储在存储介质中，如ROM/RAM、磁碟、光盘等，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本说明书各个实施例或者实施例的某些部分所述的方法。
本说明书可用于众多通用或专用的计算机系统环境或配置中。例如：个人计算机、服务器计算机、手持设备或便携式设备、平板型设备、多处理器系统、基于微处理器的系统、置顶盒、可编程的消费电子设备、网络PC、小型计算机、大型计算机、包括以上任何系统或设备的分布式计算环境等等。
本说明书可以在由计算机执行的计算机可执行指令的一般上下文中描述，例如程序模块。一般地，程序模块包括执行特定任务或实现特定抽象数据类型的例程、程序、对象、组件、数据结构等等。也可以在分布式计算环境中实践本说明书，在这些分布式计算环境中，由通过通信网络而被连接的远程处理设备来执行任务。在分布式计算环境中，程序模块可以位于包括存储设备在内的本地和远程计算机存储介质中。
虽然通过实施例描绘了本说明书，本领域普通技术人员知道，本说明书有许多变形和变化而不脱离本说明书的精神，希望所附的权利要求包括这些变形和变化而不脱离本说明书的精神。

Claims (19)

  1. 一种数据处理方法，包括：
    响应于针对业务界面中控件的触发指令，获取所述控件对应的场景标识；其中，所述场景标识包括权限标识；
    检测应用程序是否具备所述权限标识所标识的权限；
    若否，向服务器发送设备信息。
  2. 如权利要求1所述的方法，所述场景标识还包括业务标识。
  3. 如权利要求1所述的方法，所述设备信息包括厂商标识、型号标识和操作系统版本标识中的一个或多个。
  4. 如权利要求1所述的方法，若否，所述方法还包括：向服务器发送所述场景标识。
  5. 如权利要求1所述的方法，所述方法还包括：若是，执行所述控件对应的功能。
  6. 一种终端设备，包括：
    显示组件，用于提供业务界面；
    处理器，用于响应于针对业务界面中控件的触发指令，获取所述控件对应的场景标识；其中，所述场景标识包括权限标识；检测应用程序是否具备所述权限标识所标识的权限；
    通信组件，用于若否，向服务器发送设备信息。
  7. 一种数据处理装置，包括：
    获取单元，用于响应于针对业务界面中控件的触发指令，获取所述控件对应的场景标识；其中，所述场景标识包括权限标识；
    检测单元，用于检测应用程序是否具备所述权限标识所标识的权限；
    发送单元，用于若否，向服务器发送设备信息。
  8. 一种数据处理方法，包括：
    接收服务器发来的界面标识；其中，所述界面标识用于标识应用程序的权限设置界面；
    展示基于所述界面标识生成的引导界面；
    响应于允许开通权限的触发指令，进入所述权限设置界面；
    响应于开通目标权限的触发指令，开通所述应用程序的目标权限；
    响应于前台运行所述应用程序的触发指令，执行所述应用程序中控件的功能。
  9. 如权利要求8所述的方法，在展示基于所述界面标识生成的引导界面之前，所 述方法还包括：
    获取引导模板；
    相应地，所述展示基于所述界面标识生成的引导界面，包括：
    展示基于所述界面标识和所述引导模板生成的引导界面。
  10. 如权利要求9所述的方法，所述获取引导模板，包括：
    从本地获取引导模板；
    或者，接收服务器发来的引导模板。
  11. 如权利要求8所述的方法，所述方法还包括：
    响应于拒绝开通权限的触发指令，展示提示信息。
  12. 如权利要求8所述的方法，所述控件对应有场景标识；所述场景标识包括用于标识所述目标权限的权限标识。
  13. 一种终端设备，包括：
    通信组件，用于接收服务器发来的界面标识；其中，所述界面标识用于标识应用程序的权限设置界面；
    显示组件，用于展示基于所述界面标识生成的引导界面；展示所述权限设置界面；
    处理器，用于响应于允许开通权限的触发指令，控制显示组件展示所述权限设置界面；响应于开通目标权限的触发指令，开通所述应用程序的目标权限；响应于前台运行所述应用程序的触发指令，执行所述应用程序中控件的功能。
  14. 一种数据处理装置，包括：
    接收单元，用于接收服务器发来的界面标识；其中，所述界面标识用于标识应用程序的权限设置界面；
    展示单元，用于展示基于所述界面标识生成的引导界面；
    进入单元，用于响应于允许开通权限的触发指令，进入所述权限设置界面；
    开通单元，用于响应于开通目标权限的触发指令，开通所述应用程序的目标权限；
    执行单元，用于响应于前台运行所述应用程序的触发指令，执行所述应用程序中控件的功能。
  15. 一种数据处理方法，包括：
    提供设备信息和界面标识的对应关系；其中，所述界面标识用于标识应用程序的权限设置界面；
    接收终端设备发来的设备信息；
    基于设备信息和界面标识的对应关系，获取接收的设备信息对应的界面标识；
    向终端设备发送获取的界面标识。
  16. 如权利要求15所述的方法，所述设备信息包括厂商标识、型号标识和操作系统版本标识中的一个或多个。
  17. 如权利要求15所述的方法，所述方法还包括：
    提供业务标识和引导模板的对应关系；
    接收终端设备发来的场景标识；其中，所述场景标识包括业务标识；
    基于业务标识和引导模板的对应关系，获取接收的业务标识对应的引导模板；
    向终端设备发送获取的引导模板。
  18. 一种服务器，包括：
    通信组件，用于接收终端设备发来的设备信息；向终端设备发送获取的界面标识；
    处理器，用于提供设备信息和界面标识的对应关系；其中，所述界面标识用于标识应用程序的权限设置界面；基于设备信息和界面标识的对应关系，获取接收的设备信息对应的界面标识。
  19. 一种数据处理装置，包括：
    提供单元，用于提供设备信息和界面标识的对应关系；其中，所述界面标识用于标识应用程序的权限设置界面；
    接收单元，用于接收终端设备发来的设备信息；
    获取单元，用于基于设备信息和界面标识的对应关系，获取接收的设备信息对应的界面标识；
    发送单元，用于向终端设备发送获取的界面标识。
PCT/CN2018/107522 2017-11-17 2018-09-26 数据处理方法和装置、终端设备、服务器 WO2019095861A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201711143482.6A CN108011930A (zh) 2017-11-17 2017-11-17 数据处理方法和装置、终端设备、服务器
CN201711143482.6 2017-11-17

Publications (1)

Publication Number Publication Date
WO2019095861A1 true WO2019095861A1 (zh) 2019-05-23

Family

ID=62052735

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/107522 WO2019095861A1 (zh) 2017-11-17 2018-09-26 数据处理方法和装置、终端设备、服务器

Country Status (3)

Country Link
CN (1) CN108011930A (zh)
TW (1) TWI709070B (zh)
WO (1) WO2019095861A1 (zh)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112667367A (zh) * 2020-12-22 2021-04-16 北京有竹居网络技术有限公司 一种多租户应用的跳转方法、装置、电子设备及存储介质
CN112965711A (zh) * 2021-03-04 2021-06-15 北京金山云网络技术有限公司 作业测试方法和装置、电子设备和存储介质
CN114281459A (zh) * 2021-12-22 2022-04-05 南京欧珀软件科技有限公司 资源获取方法及相关产品
CN114416265A (zh) * 2022-01-26 2022-04-29 北京得间科技有限公司 界面权限显示方法、电子设备及存储介质

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108011930A (zh) * 2017-11-17 2018-05-08 阿里巴巴集团控股有限公司 数据处理方法和装置、终端设备、服务器
CN109829122B (zh) * 2018-12-20 2021-03-09 浙江口碑网络技术有限公司 获取业务入口的方法及装置、存储介质、电子装置
US20220101305A1 (en) * 2020-09-29 2022-03-31 Ncr Corporation Mobile navigational control of terminal user interface

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106055988A (zh) * 2016-05-25 2016-10-26 东方网力科技股份有限公司 针对控件的权限控制方法及装置
JP6024109B2 (ja) * 2012-01-20 2016-11-09 株式会社リコー 情報処理システム及びジョブ実行方法
CN106886692A (zh) * 2017-03-23 2017-06-23 北京金山安全软件有限公司 应用程序的使用方法、装置及电子设备
CN108011930A (zh) * 2017-11-17 2018-05-08 阿里巴巴集团控股有限公司 数据处理方法和装置、终端设备、服务器

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
TWI488114B (zh) * 2009-07-22 2015-06-11 Mitake Information Corp 提供一行動裝置下載一相容軟體之裝置與方法
US8621571B2 (en) * 2010-03-03 2013-12-31 Htc Corporation Online service providing system, method, server and mobile device thereof, and computer program product
CN106055968B (zh) * 2016-05-31 2019-09-17 北京金山安全软件有限公司 一种权限设置方法、装置及电子设备

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP6024109B2 (ja) * 2012-01-20 2016-11-09 株式会社リコー 情報処理システム及びジョブ実行方法
CN106055988A (zh) * 2016-05-25 2016-10-26 东方网力科技股份有限公司 针对控件的权限控制方法及装置
CN106886692A (zh) * 2017-03-23 2017-06-23 北京金山安全软件有限公司 应用程序的使用方法、装置及电子设备
CN108011930A (zh) * 2017-11-17 2018-05-08 阿里巴巴集团控股有限公司 数据处理方法和装置、终端设备、服务器

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112667367A (zh) * 2020-12-22 2021-04-16 北京有竹居网络技术有限公司 一种多租户应用的跳转方法、装置、电子设备及存储介质
CN112965711A (zh) * 2021-03-04 2021-06-15 北京金山云网络技术有限公司 作业测试方法和装置、电子设备和存储介质
CN114281459A (zh) * 2021-12-22 2022-04-05 南京欧珀软件科技有限公司 资源获取方法及相关产品
CN114281459B (zh) * 2021-12-22 2024-04-16 南京欧珀软件科技有限公司 资源获取方法及相关产品
CN114416265A (zh) * 2022-01-26 2022-04-29 北京得间科技有限公司 界面权限显示方法、电子设备及存储介质

Also Published As

Publication number Publication date
TWI709070B (zh) 2020-11-01
TW201923543A (zh) 2019-06-16
CN108011930A (zh) 2018-05-08

Similar Documents

Publication Publication Date Title
WO2019095861A1 (zh) 数据处理方法和装置、终端设备、服务器
JP6698646B2 (ja) Ｊｓｏｎスタイルシート言語変換
US11204681B2 (en) Program orchestration method and electronic device
US10884767B2 (en) Service processing methods and devices
US20170289338A1 (en) Enabling stateful dynamic links in mobile applications
US10637804B2 (en) User terminal apparatus, communication system, and method of controlling user terminal apparatus which support a messenger service with additional functionality
CN109074278B (zh) 验证移动应用中的有状态动态链接
US20200125624A1 (en) Method and system for starting application
US10698700B2 (en) Method and system for starting application
KR20210134675A (ko) 사용자 시연을 통하여 명령들을 학습하고 실행 가능하게 하기 위한 방법 및 시스템
US9524089B1 (en) Common web component
AU2017320170B2 (en) Electronic device and method for call back notification service
EP3416054B1 (en) Method and device for page display, and storage medium
US10802674B2 (en) Method and apparatus for displaying function interface
US8907927B2 (en) Camera based hover detection for touch-based mobile devices
US9888340B2 (en) Non-intrusive proximity based advertising and message delivery
EP3416070A1 (en) Page display method and device and storage medium
CN114741292A (zh) 测试脚本管理方法及装置、电子设备和存储介质
CN107861666B (zh) 桌面应用安装方法及装置
KR102106484B1 (ko) 정보 표시 방법, 단말 및 서버
CN110868640A (zh) 资源转移方法、装置、设备及存储介质
US9706013B2 (en) Mobile runtime conditional sections for surveys
US20230111874A1 (en) Device emulations in a notebook session
CN115525382A (zh) 一种远程协助方法、装置及终端设备

Legal Events

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

Ref document number: 18879353

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18879353

Country of ref document: EP

Kind code of ref document: A1