WO2014166227A1 - 一种在通讯录中添加插件的方法、装置和设备 - Google Patents

一种在通讯录中添加插件的方法、装置和设备 Download PDF

Info

Publication number
WO2014166227A1
WO2014166227A1 PCT/CN2013/085883 CN2013085883W WO2014166227A1 WO 2014166227 A1 WO2014166227 A1 WO 2014166227A1 CN 2013085883 W CN2013085883 W CN 2013085883W WO 2014166227 A1 WO2014166227 A1 WO 2014166227A1
Authority
WO
WIPO (PCT)
Prior art keywords
plug
request
function
address book
user
Prior art date
Application number
PCT/CN2013/085883
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 小米科技有限责任公司
Priority to RU2015125631A priority Critical patent/RU2630553C2/ru
Priority to KR1020157014010A priority patent/KR101726526B1/ko
Priority to JP2015543270A priority patent/JP6074516B2/ja
Priority to EP13881497.5A priority patent/EP2985701A4/en
Priority to MX2015008271A priority patent/MX346616B/es
Priority to BR112015016505A priority patent/BR112015016505A2/pt
Priority to US14/156,756 priority patent/US20140310606A1/en
Publication of WO2014166227A1 publication Critical patent/WO2014166227A1/zh

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44Arrangements for executing specific programs
    • G06F9/445Program loading or initiating
    • G06F9/44521Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading
    • G06F9/44526Plug-ins; Add-ons

Definitions

  • the embodiments of the present disclosure relate to the technical field of mobile devices, and in particular, to a method for adding a plug-in in an address book, an apparatus for adding a plug-in in an address book, and a device. Background technique
  • the address book can store contact information, such as contact name, phone number, home address, email address, contact's birthday, etc.
  • the mobile phone usually sets some common functions for the address book. For example, the user can select to directly dial a contact phone or send a message in the address book.
  • the address book actually fully expresses the social relationship network of users (such as mobile phone owners).
  • users such as mobile phone owners.
  • network communication technology people are more and more personalized for the application scenarios based on social network. Demand, and, some requirements may only be applicable in a small range.
  • the current address book only provides basic common functions, which can not meet these niche needs.
  • the current address book is a closed platform. If all users' personalized needs are all attached to the address book, the address book can only be redesigned. The engineering volume is large, the rate of return is low, and too much program data will reduce the stability and response speed of mobile devices. For ordinary users, the redundant address book function is also a problem, which will greatly reduce users. The experience of using.
  • the technical problem to be solved by the embodiments of the present disclosure is to provide a method for adding a plug-in in an address book, by importing an interface of a mobile device address book, importing a plug-in of a third-party application from the interface, so that the user can communicate from the plug-in through the plug-in.
  • the recording platform directly calls related functions of third-party applications, which reduces the occupation of system resources and storage space.
  • an embodiment of the present disclosure further provides an apparatus and a device for adding a plug-in in an address book to ensure implementation and application of the foregoing method.
  • an embodiment of the present disclosure discloses a method for adding a plug-in in an address book, the address book having an open interface, and the plug-in is a third-party application generated according to a specification defined by the interface.
  • Program plug-in; the method includes:
  • the plugin is added in the address book
  • the specifications defined by the interface include a user interface UI specification and a predefined permission specification.
  • the step of receiving the installation request of the plugin, and authenticating the plugin according to the request includes: receiving an installation request of the plugin, and determining, according to the request, whether the plugin adopts a user interface ⁇ the specification and compliance with the predefined permission specifications;
  • the plug-in adopts a user interface UI specification and conforms to the predefined permission specification, the authentication is passed;
  • the plug-in does not adopt the user interface UI specification or does not conform to the predefined permission specification, generating prompt information for prompting the user to determine whether to continue the installation.
  • the step of adding a plug-in to the address book includes:
  • the method before the step of receiving a request by the user to invoke the plug-in function, the method further includes:
  • a prompt message is generated for prompting the user whether to enable the plugin function.
  • the step of receiving a request by the user to invoke the plug-in function, and invoking a corresponding function of the plug-in according to the user request includes:
  • the data of the address book is transmitted to the third party application through the portal, and the corresponding function is executed in the third party application.
  • the address book includes contact information of an account bound by the user.
  • an embodiment of the present disclosure further discloses an apparatus for adding a plug-in in an address book, where the address book has an open interface, and the plug-in is a third-party application plug-in generated according to a specification defined by the interface;
  • the device includes: a request receiving module, configured to receive an installation request of the plugin; An authentication module, configured to authenticate the plugin according to the request;
  • the calling module is configured to receive a request by the user to invoke the plug-in function, and invoke a corresponding function of the plug-in according to the user request.
  • the specifications defined by the interface include a user interface specification and a predefined permission specification.
  • the authentication module includes: a rights specification determining sub-module, configured to determine, according to the request, whether the plug-in adopts a user interface UI specification and whether the predefined permission specification is met;
  • the authentication is invoked through the sub-module, and if the plug-in does not adopt the user interface specification or does not conform to the predefined permission specification, Calling the first prompt submodule;
  • Authentication is passed through a sub-module for determining the authentication pass
  • the first prompt sub-module is configured to generate prompt information for prompting the user to determine whether to continue the installation.
  • the adding module includes:
  • the submodule is installed to install the function data package carried by the plugin.
  • the device further includes:
  • the judging module is configured to determine whether the function of enabling the plug-in is set in the address book; if the function of enabling the plug-in is set in the address book, the execution sub-module is invoked; if the enabler is not set in the address book For the function of the plugin, the second prompt submodule is called.
  • An execution submodule configured to execute the request that the receiving user invokes the plugin function
  • the second prompt sub-module is configured to generate prompt information for prompting the user whether to enable the plug-in function.
  • the calling module includes:
  • An entry-opening sub-module configured to receive a request for the user to invoke the plug-in function, open a function data packet carried by the plug-in, and open a corresponding entry of the associated third-party application by using the function data packet;
  • a data transmission submodule configured to transmit data of the address book to the third party application through the portal, and perform corresponding functions in the third party application.
  • an embodiment of the disclosure further discloses an apparatus, including:
  • One or more processors are One or more processors;
  • One or more modules the one or more modules being stored in the memory and configured to be executed by the one or more processors, wherein the one or more modules have the function of receiving the The installation request of the plugin, the plugin is authenticated according to the request;
  • the plugin is added in the address book; Receiving a request by the user to invoke the plug-in function, and calling a corresponding function of the plug-in according to the user request.
  • the embodiment of the present disclosure introduces a plug-in of a third-party application from the interface by opening an interface of the mobile device address book, so that the user can directly call a related function of the third-party application from the address book platform through the plug-in, thereby reducing cumbersome operation steps. It makes the operation more convenient and faster, and improves the operability of the mobile device address book.
  • the system resources occupied by running the plug-in are far lower than the system resources occupied by the running application.
  • the address book can integrate different plug-ins to meet different user requirements, so that the functions of the address book are diversified, and at the same time, the mobile device is maintained well. Stability and response speed.
  • the address book system of other platforms is embedded in the address book, which is convenient for user management.
  • FIG. 1 is a schematic flowchart of Embodiment 1 of a method for adding a plug-in in an address book according to an embodiment of the present disclosure
  • FIGS. 2a-2g are schematic diagrams showing the display position of an open plug-in in an address book platform as a specific application example of an embodiment of the present disclosure
  • FIG. 3 is a schematic diagram showing an example of an application scenario in which a plug-in related function is invoked by applying an embodiment of the present disclosure
  • FIG. 4 is a schematic diagram showing an example of an application scenario in which a plug-in related function is applied to an embodiment of the present disclosure
  • FIG. 6 is a schematic diagram showing an example of an application scenario in which a plug-in related function is invoked by applying an embodiment of the present disclosure
  • FIG. 7 illustrates an application of the present disclosure.
  • FIG. 8 is a schematic diagram showing an example of an application scenario in which a plug-in related function is invoked by applying an embodiment of the present disclosure
  • FIG. 8 is a schematic diagram showing an example of an application scenario in which a plug-in related function is invoked by applying an embodiment of the present disclosure
  • FIG. 8 is a schematic diagram showing an example of an application scenario in which a plug-in related function is invoked by applying an embodiment of the
  • FIG. 9 illustrates a call plugin applied to an embodiment of the present disclosure.
  • a schematic diagram of an application scenario example of a related function FIG. 10 is a schematic diagram showing an example of an application scenario in which a plug-in related function is invoked by applying an embodiment of the present disclosure.
  • FIG. 11 is a diagram showing a function of calling a plug-in related to an embodiment of the present disclosure.
  • Schematic diagram of an application scenario example FIG. 12 illustrates the application of a plug-in phase to an embodiment of the present disclosure.
  • FIG. 13 is a schematic diagram showing an example of an application scenario in which a plug-in related function is invoked by applying an embodiment of the present disclosure;
  • FIG. 14 is a diagram showing an embodiment of the present disclosure in an address book.
  • FIG. 15 is a block diagram showing an exemplary structure of an apparatus for adding a plug-in in an address book according to an embodiment of the present disclosure.
  • the embodiments of the present disclosure have been shown by the above-described drawings, which will be described in more detail later.
  • the drawings and the text are not intended to limit the scope of the present disclosure in any way, and the description of the present disclosure will be described by those skilled in the art by reference to the specific embodiments. detailed description
  • One of the core concepts of the embodiments of the present disclosure is to import a plug-in of a third-party application from the interface by opening an interface of the mobile device address book, so that the user can directly call a related function of the third-party application from the address book platform through the plug-in.
  • FIG. 1 a flow chart of a method for adding a plug-in in an address book according to an embodiment of the present disclosure is shown.
  • the address book has an open interface
  • the plug-in is The third-party application plug-in generated according to the specification defined by the interface; the embodiment may specifically include the following steps:
  • Step 101 Receive an installation request of the plug-in, and perform authentication on the plug-in according to the request.
  • Step 102 After the authentication is passed, add the plug-in to the address book.
  • Step 103 Receive a request by the user to invoke the plug-in function, and invoke a corresponding function of the plug-in according to the user request.
  • the "address book” or “address book platform” refers to an address book application installed or configured in the mobile device. Such as the address book function in the phone.
  • the mobile device may be a variety of mobile devices, such as a tablet computer, a personal digital assistant, and a mobile phone.
  • the contact in the address book may include contact information stored in the mobile device, for example, the name, phone number, home address, email address, contact birthday, etc. of the contact entered by the user in the mobile phone address book.
  • the contacts in the address book may also include contact information in the cloud storage, such as contact information submitted by the user stored in the cloud server.
  • the address book may further include contact information of the account bound by the user.
  • the contacts in the address book may also include all the contacts in the SNS/IM account, and the account bound by the user may also be It is a game platform account, which can be an account of an online voice/video call service, which can be a network disk account, an account of a terminal interconnection service, and the like, and an account related to the user's social network behavior.
  • the temporary account authorization mode may be used, that is, the other account and its password are verified through the address book, and the account management authority is obtained. Thereby obtaining information about the relevant account contacts.
  • the open interface of the address book may be an API interface (application program interface) based on a mobile device operating system, which may include, but is not limited to, an operating system UI, a common control, data (contact data), and functions (such as merging duplicate contacts), and the rules corresponding to the above items, such as the processing method of multi-tone words, contact sorting and grouping basis.
  • the plug-in may be understood as a third-party application plug-in generated according to a specification defined by an open interface of the address book.
  • the specification of the interface definition may include a UI specification and a predefined permission specification.
  • the UI specification may include an encoding design specification and a control design specification.
  • the coding design specification can be understood as the coding of the plug-in is to comply with the coding requirements of the operating system of the mobile device and the API interface of the address book; the control design specification can be understood as the specific location of the address book and the specific display. The way to show the plugin.
  • FIG. 2 there is shown a schematic diagram showing a display position of an open plug-in in an address book platform as a specific application example of an embodiment of the present disclosure.
  • the TAB, group field and operation bar are opened to provide a plug-in for displaying the corresponding function; as shown in FIG. 2b, in the main interface of the address book.
  • the function plug-in is displayed; as shown in Figure 2f, in the account management interface of the address book, the account bar is opened to provide the plug-in for the corresponding function.
  • the uninstall management of the plug-in can be defined in the plug-in management interface of the address book, or it can be defined elsewhere.
  • the predefined permission specification may include, but is not limited to, a read and/or write permission of the address book data, and a read and/or write permission of the associated third party application data.
  • the data processing permissions of the plugin may include, but is not limited to, a read and/or write permission of the address book data, and a read and/or write permission of the associated third party application data.
  • the plug-in generated by the specification can save more system resources of the mobile device than the stand-alone APP. storage.
  • the plug-in when the address book platform of the mobile terminal receives the installation request of the plug-in, the plug-in is first authenticated.
  • the so-called authentication that is, the legality of the plug-in is analyzed to ensure the safe operation of the address book, for example, to prevent the wrong installation from damaging the address book, to prevent the plug-in from illegally stealing user data, illegally sending service instructions and other rogue applications.
  • composition of the plug-in permission may be in the following two ways: One way, the plug-in developer manually agrees with the address book developer in advance to fix the ID or the cloud verification key. authenticating;
  • Another way is to manually authorize the user. After the plug-in issues an installation request, the address book will display the permission switch of the plug-in application in the address book, and the user can manually turn it on or off.
  • the former method can be used in step 101 to perform quick authentication, verify the validity of the plug-in, and do not need to analyze the legality of the plug-in to facilitate installation and provide legality guarantee; the latter method is suitable for plug-in management, in communication Record After installing multiple plug-ins, not all plug-ins are applicable to different contacts. By controlling the plug-in permissions, the contact information interface is clean and the address book running load is reduced.
  • the step 101 may specifically include the following sub-steps:
  • Sub-step S1 l receiving an installation request of the plug-in, determining, according to the request, whether the plug-in adopts a user interface UI specification and whether the predefined permission specification is met; if yes, performing sub-step S12; Then performing sub-step S13;
  • Sub-step S12 determining that the authentication is passed
  • Sub-step S13 generating prompt information for prompting the user to judge whether to continue the installation.
  • the method in which the plug-in developer manually approves the authorization with the address book developer in advance and performs verification by means of the fixed ID or the cloud verification key may also be applied in the sub-step S11; when the permission of the plug-in exceeds the specification range defined by the interface At this time, the user needs to judge the legality of the plug-in according to the prompt information, and determine whether to continue the installation.
  • the above-mentioned judging processing method is only an example.
  • other judging processing methods may be set according to actual conditions, and the embodiment of the present disclosure does not limit this.
  • those skilled in the art may actually need to adopt other judging processing methods, and the embodiments of the present disclosure do not limit this.
  • the plug-in can be added in the address book platform of the mobile terminal.
  • the step 102 may specifically include the following sub-steps:
  • Sub-step S21 displaying the plug-in in a corresponding position of the address book in a specified manner according to the specification defined by the interface;
  • Sub-step S22 installing the function data packet carried by the plug-in.
  • the function data package is the physical content of the plug-in, and the plug-in can read and/or write data of the address book and the third-party application according to the function data package, or can be a simple application thereof.
  • a plugin with a birthday reminder can be imported into the address book platform to remind the user of the birthday of the contact in the address book.
  • the address book data can be understood as a contact and its birthday.
  • the plug-in generates a birthday reminder function button on the contact information interface, and according to the user's selection, determines the target contact, the reminder period, the reminder manner, etc., and then invokes the plug-in execution. The corresponding reminder function.
  • the step 103 may specifically include the following sub-steps:
  • Sub-step S31 receiving a request for the user to invoke the plug-in function, opening a function data packet carried by the plug-in, and opening a corresponding entry of the associated third-party application by using the function data packet;
  • Sub-step S32 the data of the address book is transmitted to the third-party application through the portal, and the corresponding function is executed in the third-party application.
  • the step 103 is further illustrated by an example of several application scenarios:
  • FIG. 3 a schematic diagram of an application scenario example of a plug-in for transferring a payment to a target contact according to an embodiment of the present disclosure is shown.
  • the plug-in of the address book includes a transfer payment plug-in, and the address book receives a request from the user to invoke the plug-in function, and the steps of calling the corresponding function of the plug-in according to the user request include:
  • the data of the target contact and the current user is transmitted to the third party application through the portal, and the corresponding transfer payment function is executed in the third party application.
  • FIG. 4 a schematic diagram of an application scenario example of a plug-in for delivering a courier to a target contact in accordance with an embodiment of the present disclosure is shown.
  • the plug-in of the address book includes a courier plug-in, and the address book receives a request from the user to invoke the plug-in function, and the steps of calling the corresponding function of the plug-in according to the user request include:
  • the data of the target contact and the current user is transmitted to the third party application through the portal, and the third party application sends the information of the user and the target contact to the courier company.
  • FIG. 5 a schematic diagram of an application scenario example of a plug-in for adding personal information to a target contact according to an embodiment of the present disclosure is shown.
  • the plug-in of the address book includes a personal plug-in, and the address book receives the request of the user to call the plug-in function, and the steps of calling the corresponding function of the plug-in according to the user request include:
  • Receiving a request submitted by the user to add a personal relationship to the target contact performing, according to the user request, writing the personal relationship data of the target contact, and opening a corresponding entry of the third-party application associated with the personal plug-in;
  • the data fed back in the third-party application is written into the target contact information through the portal;
  • the personal plug-in writes the personal relationship data into the contact information associated with the personal relationship.
  • FIG. 6 a schematic diagram of an application scenario example of a plug-in for querying a geographic location of a target contact according to an embodiment of the present disclosure is shown.
  • the plug-in of the address book includes a location query plug-in, and the address book receives a request from the user to invoke the plug-in function, and the steps of calling the corresponding function of the plug-in according to the user request include:
  • the data replied to by the current user and the target contact is transmitted to the third party application through the portal, and the corresponding location query function is executed in the third party application.
  • FIG. 7 a schematic diagram of an application scenario example of a plug-in for querying a target contact card of an embodiment of the present disclosure is shown. Figure.
  • the plug-in of the address book includes a business card plug-in, and the address book receives a request for the user to call the plug-in function, and the steps of calling the corresponding function of the plug-in according to the user request include:
  • the data of the target contact is transmitted to the third-party application through the portal, and the corresponding query business card function is executed in the third-party application.
  • FIG. 8 a schematic diagram of an application scenario example of a plug-in of an entertainment application according to an embodiment of the present disclosure is shown.
  • the plug-in of the address book includes a fortune-telling plug-in, and the address book receives a request from the user to invoke the function of the plug-in, and the steps of calling the corresponding function of the plug-in according to the user request include:
  • the data of the target contact and the current user is transmitted to the third-party application through the portal, and the corresponding fortune-telling function is executed in the third-party application.
  • FIG. 9 a schematic diagram of an application scenario example of a plug-in for playing a game with a target contact according to an embodiment of the present disclosure is shown.
  • the plug-in of the address book includes a game center plug-in, and the user has written the account information of the game center corresponding to the target contact into the target contact information of the address book through the plug-in, and the address book receives the request of the user to invoke the plug-in function, according to the
  • the steps for the user to request the corresponding function of the plugin include:
  • the data of the target contact and the current user is transmitted to the third party application through the portal, and the corresponding game comparison function is executed in the third party application.
  • FIG. 10 a schematic diagram of an application scenario example of a plug-in for an online voice/video call with a target contact in accordance with an embodiment of the present disclosure is shown.
  • the plug-in of the address book includes an online voice/video call plug-in, through which the user has written the account information of the online voice/video call service of the target contact into the target contact information of the address book, and judges whether the other party is determined by the online condition of the terminal device.
  • the address book receives a request by the user to invoke the plug-in function, and the step of calling the corresponding function of the plug-in according to the user request includes:
  • FIG. 11 there is shown a schematic diagram of an application scenario example of a plug-in that chats with a target contact in an embodiment of the present disclosure.
  • the plug-in of the address book includes a live chat plug-in, and the user has written the contact information of the target contact instant chat service account to the target contact information of the address book through the plug-in, and judges whether the other party is online through the online condition of the terminal device, and the address book Receiving a request by the user to invoke the plug-in function, and the step of calling the corresponding function of the plug-in according to the user request includes:
  • the data of the target contact and the current user is transmitted to the third party application through the portal, and the corresponding live chat function is executed in the third party application.
  • FIG. 12 there is shown a schematic diagram of an application scenario example of a plug-in for sharing a file with a target contact in an embodiment of the present disclosure.
  • the plug-in of the address book includes a network disk sharing plug-in, and the user has written the network account account information of the target contact into the target contact information of the address book through the plug-in, and the address book receives the request of the user to invoke the plug-in function, according to the user.
  • the steps to request the corresponding function of the plugin are:
  • the data of the target contact and the current user is transmitted to the third-party application through the portal, and the corresponding shared file function is executed in the third-party application.
  • FIG. 13 there is shown a schematic diagram of an application scenario example of a plug-in that is online with a target contact according to an embodiment of the present disclosure.
  • the plug-in of the address book includes a dual-machine interconnection plug-in, and the user has written the account information of the online service corresponding to the target contact into the target contact information of the address book through the plug-in, and the address book receives the request of the user to invoke the plug-in function, according to the user.
  • the steps to request the corresponding function of the plugin are:
  • the data of the target contact and the current user is transmitted to the third party application through the portal, and the corresponding online function is executed in the third party application.
  • FIG. 14 is a flow chart showing the steps of a method for adding a plug-in in an address book according to an embodiment of the present disclosure, which may specifically include the following steps:
  • Step 201 Receive an installation request of the plugin, and perform authentication on the plugin according to the request.
  • Step 202 after the authentication is passed, adding the plug-in to the address book;
  • Step 203 it is determined whether the function of enabling the plug-in is set in the address book; if yes, step 204 is performed; if not, step 205 is performed;
  • Step 204 Receive a request for a user to invoke the plug-in function, and invoke a corresponding function of the plug-in according to the user request;
  • Step 205 Generate prompt information for prompting the user whether to enable the plug-in function.
  • the plug-in before receiving the request of the user to invoke the plug-in function, it is detected that the function of enabling the plug-in is set in the address book. Due to the different design concepts of the plug-in, the plug-in can be turned on by default after installation, or it can be turned off by default, or the user can re-enable it after closing the plug-in according to requirements, or the plug-in is closed in other situations. With this scheme, it can be detected first.
  • the plugin is enabled in the address book, allowing the user to select it, turn it on when needed, and turn it off when not needed, which can save resources and enhance the user experience.
  • a structural block diagram of an apparatus for adding a plug-in in an address book which is a third-party application plug-in generated according to a specification defined by the interface, may specifically include the following modules:
  • a request receiving module 301 configured to receive an installation request of the plugin
  • the authentication module 302 is configured to authenticate the plugin according to the request
  • the installation module 303 is configured to add the plug-in to the address book after the authentication is passed;
  • the calling module 304 is configured to receive a request by the user to invoke the plug-in function, and invoke a corresponding function of the plug-in according to the user request.
  • the address book may include contact information of an account bound by the user.
  • the specification of the interface definition may specifically include a user interface UI specification and a predefined permission specification.
  • the authentication module may specifically include:
  • a judging sub-module configured to determine, according to the request, whether the plug-in adopts a user interface UI specification and whether the predefined permission specification is met; if the plug-in adopts a user interface UI specification and conforms to the predefined permission The specification, the authentication is invoked through the sub-module, and if the plug-in does not adopt the user interface UI specification or does not conform to the predefined permission specification, the first prompt sub-module is invoked;
  • Authentication is passed through a sub-module for determining the authentication pass
  • the first prompt sub-module is configured to generate prompt information for prompting the user to determine whether to continue the installation.
  • the adding module may specifically include:
  • a presentation submodule configured to display the plugin in a corresponding position of the address book in a specified manner according to a specification defined by the interface;
  • the submodule is installed to install the function data package carried by the plugin.
  • the calling module may specifically include:
  • the portal opens a sub-module, receives a request for the user to invoke the plug-in function, opens a function data package carried by the plug-in, and opens a corresponding entry of the associated third-party application by using the function data packet;
  • a data transfer sub-module that transmits data of the address book to the third-party application through the portal, and performs a corresponding function in the third-party application.
  • the apparatus may further include:
  • a judging module configured to determine whether a function for enabling the plug-in is set in the address book; if a function for enabling the plug-in is set in the address book, the execution sub-module is called; if the function of enabling the plug-in is not set in the address book , the second prompt sub-module is called.
  • An execution submodule configured to execute the request that the receiving user invokes the plugin function
  • the second prompt sub-module is configured to generate prompt information for prompting the user whether to enable the plug-in function.
  • the description is relatively simple, and the relevant part can be referred to the description of the method embodiment of adding the plug-in in the address book.
  • the embodiment of the present disclosure further provides an apparatus, where the apparatus may include:
  • One or more modules the one or more modules being stored in the memory and configured to be executed by the one or more processors, wherein the one or more modules have the function of receiving the The installation request of the plugin, the plugin is authenticated according to the request;
  • the plugin is added in the address book
  • the specification of the interface definition may include a user interface UI specification and a predefined permission specification.
  • the one or more modules may have the following functions: receiving an installation request of the plug-in, determining, according to the request, whether the plug-in adopts a user interface specification and whether the predefined permission specification is met;
  • the plug-in adopts a user interface specification and conforms to the predefined permission specification, the authentication is passed;
  • the plug-in does not adopt the user interface UI specification or does not conform to the predefined permission specification, generating prompt information for prompting the user to determine whether to continue the installation.
  • the one or more modules may have the function of: displaying the plug-in in a corresponding position of the address book in a specified manner according to the specification defined by the interface; installing a function data packet carried by the plug-in.
  • the one or more modules may have the following functions - determining whether a function for enabling the plug-in is set in the address book; If the function of enabling the plugin is set in the address book, executing the request for receiving the function of calling the plugin by the user;
  • a prompt message is generated to prompt the user whether to enable the plugin function.
  • the one or more modules may have the following functions: receiving a request for the user to invoke the plug-in function, opening a function data package carried by the plug-in, and opening the associated third-party application by using the function data package Corresponding entry;
  • the data of the address book is transmitted to the third party application through the portal, and the corresponding function is executed in the third party application.
  • the address book may include contact information of an account bound by the user.
  • the embodiment further provides a non-volatile readable storage medium, wherein the storage medium stores one or more programs, and when the one or more modules are applied to a device with an address book, The device performs the following steps (instructions):
  • the plugin is added in the address book
  • the specification of the interface definition may include a user interface UI specification and a predefined permission specification.
  • the one or more modules may have the following functions: receiving an installation request of the plug-in, determining, according to the request, whether the plug-in adopts a user interface UI specification and whether the predefined permission specification is met;
  • the plug-in adopts a user interface UI specification and conforms to the predefined permission specification, the authentication is passed;
  • the plug-in does not adopt the user interface UI specification or does not conform to the predefined permission specification, generating prompt information for prompting the user to determine whether to continue the installation.
  • the one or more modules may have the function of: displaying the plug-in in a corresponding position of the address book in a specified manner according to the specification defined by the interface; installing a function data packet carried by the plug-in.
  • the one or more modules may have the following functions - determining whether a function for enabling the plug-in is set in the address book;
  • a prompt message is generated to prompt the user whether to enable the plugin function.
  • the one or more modules may have the function of: receiving a request by the user to invoke the plug-in function, opening a function data packet carried by the plug-in, by using the function The packet opens into the corresponding entry of the associated third-party application;
  • the data of the address book is transmitted to the third party application through the portal, and the corresponding function is executed in the third party application.
  • the address book may include contact information of an account bound by the user.
  • the description is relatively simple, and the relevant part can be referred to the description of the method embodiment of adding the plug-in in the address book.
  • embodiments of the disclosed embodiments can be provided as a method, apparatus, or computer program product.
  • embodiments of the present disclosure can take the form of an entirely hardware embodiment, an entirely software embodiment, or a combination of software and hardware.
  • embodiments of the present disclosure can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) including computer usable program code.
  • Embodiments of the present disclosure are described with reference to flowcharts and/or block diagrams of methods, terminal devices (systems), and computer program products according to embodiments of the present disclosure. It will be understood that each flow and/or block of the flowcharts and/or block diagrams, and combinations of flow and / or blocks in the flowcharts and / or block diagrams can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general purpose computer, special purpose computer, embedded processor or other programmable data processing terminal device to produce a machine such that instructions are executed by a processor of a computer or other programmable data processing terminal device Means are provided for implementing the functions specified in one or more of the flow or in one or more blocks of the flow chart.
  • the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing terminal device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
  • the instruction device implements the functions specified in one or more flows of the flowchart and one or more blocks of the I or block diagram.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Stored Programmes (AREA)
  • Telephone Function (AREA)
  • Human Computer Interaction (AREA)
  • Telephonic Communication Services (AREA)

Abstract

本公开实施例提供了一种在通讯录中添加插件的方法、装置和设备,其中,所述通讯录具有开放的接口,所述插件为按所述接口定义的规范生成的第三方应用程序插件;所述的方法包括:接收所述插件的安装请求,依据所述请求对所述插件进行鉴权;当鉴权通过后,在通讯录中添加所述插件;接收用户调用所述插件功能的请求,依据所述用户请求调用所述插件的对应功能。本公开实施例使通讯录的功能多样化,减少繁琐的操作步骤,使得操作更加方便快捷,同时在运行移动设备时保持良好的稳定性和响应速度。

Description

一种在通讯录中添加插件的方法、 装置和设备 本申请基于申请号为 201310125562.4、申请日为 2013年 4月 11日的中国专利申请提 出, 并要求该中国专利申请的优先权, 该中国专利申请的全部内容在此引入本申请作为参 考。 技术领域
本公开实施例涉及移动设备的技术领域, 特别是涉及一种在通讯录中添加插件的方 法、 一种在通讯录中添加插件的装置和一种设备。 背景技术
曰常生活中,通讯录是移动设备(如手机,平板电脑等)中使用频率最高的应用程序。 一般而言, 通讯录可以存储联系人信息, 例如联系人姓名、 电话、 家庭地址、 电邮地址、 联系人的生日等, 为便于用户使用, 在移动设备中通常还会对通讯录设置一些常用功能, 例如, 用户可以在通讯录中选择直接拨打联系人电话或者发送信息等。
可以理解的是, 通讯录实际上充分表达了用户 (如手机机主) 的社会关系网络, 随着 网络通讯技术的日益发展,人们对于基于社会关系网络的应用场景有着越来越多的个性化 需求, 而且, 某些需求可能只是小范围适用的。
但是目前的通讯录只提供基本的常用功能, 完全无法满足这些小众需求, 目前的通讯 录是一个封闭的平台, 如果所有用户的个性化需求全部附加在通讯录上, 只能重新设计通 讯录, 工程量浩大, 回报率低, 而且过多的程序数据也会降低移动设备运行的稳定性和响 应速度, 对普通用户来讲, 沉冗的通讯录功能也是一种困扰, 会极大地降低用户的使用体 验。
目前的另一种解决方案是, 单独开发一个新的应用程序 (APP) 来满足用户的个性化 需求, 显然, 开发一个应用程序需要大量的人力与物力来设计 UI, 搭建 APP的架构和推 广, 难度和成本都非常高; 再者, 即使用户能接受新开发的应用程序, 但对于用户而言, 下载过多的应用程序也会占用过多的移动设备资源, 也会极大地降低用户的使用体验。 发明内容
本公开实施例所要解决的技术问题是提供一种在通讯录中添加插件的方法,通过开放 移动设备通讯录的接口, 从所述接口导入第三方应用程序的插件, 使用户可以通过插件从 通讯录平台直接调用第三方应用程序的相关功能, 减少了系统资源和存储空间的占用。
本公开实施例还提供了一种在通讯录中添加插件的装置和一种设备,用以保证上述方 法的实现及应用。 为了解决上述问题, 一方面, 本公开实施例公开了一种在通讯录中添加插件的方法, 所述通讯录具有开放的接口,所述插件为按所述接口定义的规范生成的第三方应用程序插 件; 所述的方法包括:
接收所述插件的安装请求, 依据所述请求对所述插件进行鉴权;
当鉴权通过后, 在通讯录中添加所述插件;
接收用户调用所述插件功能的请求, 依据所述用户请求调用所述插件的对应功能。 较佳地, 所述接口定义的规范包括, 用户界面 UI规范和预定义的权限规范。
较佳地, 所述接收所述插件的安装请求, 依据所述请求对所述插件进行鉴权的步骤包 括- 接收所述插件的安装请求, 依据所述请求判断所述插件是否采用了用户界面 υι规范 以及是否符合所述预定义的权限规范;
若所述插件采用了用户界面 UI规范以及符合所述预定义的权限规范, 则判定鉴权通 过;
若所述插件没有采用用户界面 UI规范或不符合所述预定义的权限规范, 则生成用于 提示用户判断是否继续安装的提示信息。
较佳地, 所述在通讯录中添加插件的步骤包括:
按照所述接口定义的规范采用指定方式在通讯录的相应位置展现所述的插件; 安装所述插件携带的功能数据包。
较佳地, 在接收用户调用所述插件功能的请求的步骤之前, 还包括:
判断是否在通讯录中设置了启用所述插件的功能;
若在通讯录中设置了启用所述插件的功能,则执行所述接收用户调用所述插件功能的 请求;
若在通讯录中未设置启用所述插件的功能,则生成用于提示用户是否启用所述插件功 能的提示信息。
较佳地, 所述接收用户调用所述插件功能的请求, 依据所述用户请求调用所述插件的 对应功能的步骤包括:
接收用户调用所述插件功能的请求, 打开所述插件携带的功能数据包, 通过所述功能 数据包开启进入关联的第三方应用程序的对应入口;
将通讯录的数据通过所述入口传输至所述第三方应用程序,在所述第三方应用程序中 执行相应的功能。
较佳地, 所述通讯录中包括所述用户绑定的账号的联系人信息。
另一方面, 本公开实施例还公开了一种在通讯录中添加插件的装置, 所述通讯录具有 开放的接口, 所述插件为按所述接口定义的规范生成的第三方应用程序插件; 所述的装置 包括- 请求接收模块, 用于接收所述插件的安装请求; 鉴权模块, 用于依据所述请求对所述插件进行鉴权;
添加模块, 用于在鉴权通过后, 在通讯录中添加所述插件;
调用模块, 用于接收用户调用所述插件功能的请求, 依据所述用户请求调用所述插件 的对应功能。
较佳地, 所述接口定义的规范包括, 用户界面 υι规范和预定义的权限规范。
较佳地, 所述鉴权模块包括- 权限规范判断子模块, 用于依据所述请求判断所述插件是否采用了用户界面 UI规范 以及是否符合所述预定义的权限规范;
若所述插件采用了用户界面 UI规范以及符合所述预定义的权限规范, 则调用鉴权通 过子模块, 若所述插件没有采用用户界面 υι规范或不符合所述预定义的权限规范, 则调 用第一提示子模块;
鉴权通过子模块, 用于判定鉴权通过;
第一提示子模块, 用于生成用于提示用户判断是否继续安装的提示信息。
较佳地, 所述添加模块包括:
展现子模块,用于按照所述接口定义的规范采用指定方式在通讯录的相应位置展现所 述的插件;
安装子模块, 用于安装所述插件携带的功能数据包。
较佳地, 所述的装置还包括:
启用判断模块, 用于判断是否在通讯录中设置了启用所述插件的功能; 若在通讯录中 设置了启用所述插件的功能, 则调用执行子模块; 若在通讯录中未设置启用所述插件的功 能, 则调用第二提示子模块。
执行子模块, 用于执行所述接收用户调用所述插件功能的请求;
第二提示子模块, 用于生成用于提示用户是否启用所述插件功能的提示信息。
较佳地, 所述调用模块包括:
入口开启子模块, 用于接收用户调用所述插件功能的请求, 打开所述插件携带的功能 数据包, 通过所述功能数据包开启进入关联的第三方应用程序的对应入口;
数据传输子模块, 用于将通讯录的数据通过所述入口传输至所述第三方应用程序, 在 所述第三方应用程序中执行相应的功能。
再一方面, 本公开实施例还公开了一种设备, 包括:
一个或多个处理器;
存储器; 和
一个或多个模块,所述一个或多个模块存储于所述存储器中并被配置成由所述一个或 多个处理器执行, 其中, 所述一个或多个模块具有如下功能- 接收所述插件的安装请求, 依据所述请求对所述插件进行鉴权;
当鉴权通过后, 在通讯录中添加所述插件; 接收用户调用所述插件功能的请求, 依据所述用户请求调用所述插件的对应功能。 本公开实施例包括以下一些优点:
本公开实施例通过开放移动设备通讯录的接口,从所述接口导入第三方应用程序的插 件, 使用户可以通过插件从通讯录平台直接调用第三方应用程序的相关功能, 减少繁琐的 操作步骤, 使得操作更加方便快捷, 提升了移动设备通讯录的可操作性。 而运行插件所占 用的系统资源远远低于运行应用程序所占用的系统资源,通讯录可以集成不同插件满足不 同的用户需求, 使通讯录的功能多样化, 同时在运行移动设备时保持良好的稳定性和响应 速度。
基于移动设备的通讯录开发插件, 已经有现成的 APP架构和 UI规范, 降低了开发设 计的技术要求和资金成本的门槛, 而且还提供了基于通讯录设备的运营销售渠道, 给予了 开发者的很大的便利, 促进了第三方应用程序插件的发展以及通讯录功能的完善。
此外, 通过获取其他平台账号的管理功能, 将其他平台的通讯录体系植入通讯录中, 方便用户管理。
应当理解的是, 以上的一般描述和后文的细节描述仅是示例性的, 并不能限制本公开 附图说明
图 1示出了本公开实施例提供的一种在通讯录中添加插件的方法实施例 1的示例性流 程图;
图 2a-2g示出了作为本公开实施例具体应用示例在通讯录平台中开放插件显示位置的 示意图;
图 3示出了应用本公开实施例调用插件相关功能的一种应用场景示例的示意图; 图 4示出了应用本公开实施例调用插件相关功能的一种应用场景示例的示意图; 图 5示出了应用本公开实施例调用插件相关功能的一种应用场景示例的示意图; 图 6示出了应用本公开实施例调用插件相关功能的一种应用场景示例的示意图; 图 7示出了应用本公开实施例调用插件相关功能的一种应用场景示例的示意图; 图 8示出了应用本公开实施例调用插件相关功能的一种应用场景示例的示意图; 图 9示出了应用本公开实施例调用插件相关功能的一种应用场景示例的示意图; 图 10示出了应用本公开实施例调用插件相关功能的一种应用场景示例的示意图 图 11示出了应用本公开实施例调用插件相关功能的一种应用场景示例的示意图; 图 12示出了应用本公开实施例调用插件相关功能的一种应用场景示例的示意图; 图 13示出了应用本公开实施例调用插件相关功能的一种应用场景示例的示意图; 图 14示出了本公开实施例提供的一种在通讯录中添加插件的方法实施例 2的示例性 流程图;
图 15示出了本公开实施例提供的一种在通讯录中添加插件的装置实施例的示例性结 构框图。 通过上述附图, 已示出本公开明确的实施例, 后文中将有更详细的描述。 这些附图和 文字描述并不是为了通过任何方式限制本公开构思的范围,而是通过参考特定实施例为本 领域技术人员说明本公开的概念。 具体实施方式
为使本公开实施例的上述目的、特征和优点能够更加明显易懂, 下面结合附图和具体 实施方式对本公开实施例作进一步详细的说明。
本公开实施例的核心构思之一在于, 通过开放移动设备通讯录的接口, 从所述接口导 入第三方应用程序的插件,使用户可以通过插件从通讯录平台直接调用第三方应用程序的 相关功能。
参照图 1, 示出了本公开实施例的一种在通讯录中添加插件的方法实施例 1的步骤流 程图, 在本公开实施例中, 所述通讯录具有开放的接口, 所述插件为按所述接口定义的规 范生成的第三方应用程序插件; 本实施例具体可以包括如下步骤:
步骤 101, 接收所述插件的安装请求, 依据所述请求对所述插件进行鉴权; 步骤 102, 当鉴权通过后, 在通讯录中添加所述插件;
步骤 103, 接收用户调用所述插件功能的请求, 依据所述用户请求调用该插件的对应 功能。
需要说明的是, 本公开实施例中所指 "通讯录"或"通讯录平台" (相对于其承载的开放 接口的功能而言) , 是指移动设备中安装或配置的通讯录应用程序, 如手机中的通讯录功 能。 在本公开实施例中, 所述移动设备可以为平板电脑、 个人数字助理、 手机等各种移动 设备, 本公开实施例对此不作限制。
在具体实现中, 通讯录中的联系人可以包括移动设备中存储的联系人信息, 例如, 用 户在手机通讯录中输入的联系人的姓名、 电话、 家庭地址、 电邮地址、 联系人生日等, 通 讯录中的联系人还可以包括云存储中的联系人信息,如存储在云服务器中的该用户提交过 的联系人信息。在本公开实施例的一种实施例中, 所述通讯录中还可以包括所述用户绑定 的账号的联系人信息。例如,用户通讯录中绑定了社交性网络服务 SNS/即时通讯 IM账号, 则通讯录中的联系人还可以包括该 SNS/IM账号中的所有联系人, 所述用户绑定的账号还 可以是游戏平台账号, 可以是在线语音 /视频通话服务的账号, 可以是网盘账号, 可以是 终端机互联服务的账号等涉及用户社交网络行为的账号。而在没有绑定账号的情况下, 而 需要用到用户相关账户联系人的情况下, 则可以临时账号授权的方式, 即通过通讯录进行 其他账号及其密码的验证, 获取该账号管理权限, 从而获得相关账户联系人的信息。
在具体实现中, 所述通讯录的开放接口可以为基于移动设备操作系统的 API接口(应 用程序接口) , 其可以包括但不限于操作系统 UI、 公共控件、 数据 (联系人数据) 及功 能 (如合并重复联系人) , 以及上述事项所对应的规则, 例如多音字的处理方法, 联系人 排序与分组依据等。 在本公开实施例中,所述插件可以理解为按所述通讯录的开放接口所定义的规范生成 的第三方应用程序插件。
作为本公开实施例的一种示例, 所述接口定义的规范可以包括, UI规范和预定义的 权限规范。 其中, 所述 UI规范可以包括编码设计规范和控件设计规范。 所述编码设计规 范可以理解为插件的编码要符合移动设备的操作系统及其通讯录的 API接口的编码要求; 所述控件设计规范可以理解为通讯录可以开放哪些具体位置以及具体以哪种展现方式展 现所述插件。
参照图 2, 示出了作为本公开实施例具体应用示例在通讯录平台中开放插件显示位置 的示意图。 例如, 如图 2a所示, 在通讯录的联系人信息界面中, 开放了 TAB、 group字段 和操作栏, 以提供给相应功能的插件进行显示; 如图 2b所示, 在通讯录主界面的"全部" 界面,显示通讯录的全部联系人,此界面开放操作栏, 以提供给相应功能的插件进行显示; 如图 2c所示, 在通讯录主界面的"全部"界面, 点击联系人査看其简介, 此界面开放标签 栏, 以提供给相应功能的插件进行显示; 如图 2d所示, 在通讯录的联系人信息编辑界面 中, 开放插件对联系人信息的写入权限, 此外, 此界面开放编辑项, 以提供给相应功能的 插件进行显示; 如图 2e所示, 在通讯录主界面的"群组"界面, 显示全部联系人分组, 此 界面开放分组栏, 以提供给相应功能的插件进行显示; 如图 2f 所示, 在通讯录的账号管 理界面中, 开放账户栏, 以提供给相应功能的插件进行显示; 如图 2g所示, 在通讯录的 插件管理界面中, 可以显示插件的安装信息, 及其对应的权限开关, 并且可以有全部插件 的统一权限开关, 用户均可以手动开启或关闭。 此外, 插件的卸载管理, 可以定义在通讯 录的插件管理界面中, 也可以定义在其他地方。
在具体实现中, 所述预定义的权限规范, 可以包括但不限于通讯录数据的读取和 /或 写入的权限, 关联的第三方应用程序数据的读取和 /或写入的权限, 插件的数据处理权限。
当一个依附于通讯录的插件与一个独立的 APP (应用)都可以实现同一个简单的应用 时, 相对于独立的 APP而言, 按规范生成的插件, 可以节省移动设备更多的系统资源和 存储空间。
应用本公开实施例, 当移动终端的通讯录平台接收到插件的安装请求后, 首先将会对 所述插件进行鉴权。 所谓鉴权, 即分析插件的合法性, 保障通讯录的安全运行, 例如, 防 止错误安装损害通讯录, 防止插件非法盗取用户资料、 非法发送服务指令等流氓应用等。
作为本公开实施例具体应用的示例, 插件权限的构成可以采用如下两种方式: 其中一种方式, 由插件开发者提前与通讯录开发者人工约定授权, 以固定 ID或云端 验证密钥的方式进行验证;
另外一种方式为用户手动授权, 插件发出安装请求后, 通讯录会将该插件应用的权限 开关显示在通讯录中, 用户可以手动开启或关闭。
前一种方式应用在步骤 101中可进行快速鉴权, 验证插件的合法性, 而不需要额外分 析插件的合法性, 方便安装并提供合法性保障; 后一种方式适用于插件管理, 在通讯录里 安装多个插件后, 对于不同联系人而言并不是所有的插件都适用, 通过控制插件权限的开 关, 保持联系人信息界面的整洁性和减小通讯录运行负担。
在本公开的一种实施例中, 所述步骤 101具体可以包括如下子步骤:
子步骤 Sl l, 接收所述插件的安装请求, 依据所述请求判断所述插件是否采用了用户 界面 UI规范以及是否符合所述预定义的权限规范; 若是, 则执行子步骤 S12; 若否, 则 执行子步骤 S13;
子步骤 S12, 判定鉴权通过;
子步骤 S13, 生成用于提示用户判断是否继续安装的提示信息。
可以理解, 由插件开发者提前与通讯录开发者人工约定授权, 以固定 ID或云端验证 密钥的方式进行验证的方式亦可在子步骤 S11中适用;当插件的权限超出接口定义的规范 范围时, 就需要用户根据提示信息自行判断插件的合法性, 以及判断是否继续安装。
当然, 上述判断处理方法只是作为示例, 在实施本公开实施例时, 可以根据实际情况 设置其他判断处理方法,本公开实施例对此不加以限制。另外,除了上述判断处理方法外, 本领域技术人员还可以实际需要采用其它判断处理方法, 本公开实施例对此也不加以限 制。
当鉴权通过后, 即可在移动终端的通讯录平台中添加所述插件。
在本公开的一种实施例中, 所述步骤 102具体可以包括以下子步骤:
子步骤 S21, 按照所述接口定义的规范采用指定方式在通讯录的相应位置展现所述的 插件;
子步骤 S22, 安装所述插件携带的功能数据包。
所述功能数据包为该插件的实体内容, 插件根据功能数据包的不同, 可以进行通讯录 与第三方应用程序的数据的读取和 /或写入, 也可以是其简单应用。
例如, 可以在通讯录平台中导入具有生日提醒功能的插件, 提醒用户通讯录中联系人 的生日。 在此, 通讯录数据可以理解为联系人及其生日, 插件在联系人信息界面生成生日 提醒功能按键, 根据用户的选择, 确定目标联系人、 提醒的期限、 提醒的方式等, 再调用 插件执行相应提醒功能。
在本公开的一种实施例中, 所述步骤 103具体可以包括以下子步骤:
子步骤 S31, 接收用户调用所述插件功能的请求, 打开所述插件携带的功能数据包, 通过所述功能数据包开启进入关联的第三方应用程序的对应入口;
子步骤 S32, 将通讯录的数据通过所述入口传输至所述第三方应用程序, 在所述第三 方应用程序中执行相应的功能。
以下通过几种应用场景的示例对所述步骤 103作进一步说明:
应用场景一:
参见图 3, 示出了本公开实施例的向目标联系人转账支付的插件的应用场景示例的示 意图。 通讯录的插件包括转账支付插件, 通讯录接收用户调用该插件功能的请求, 依据所述 用户请求调用该插件的对应功能的步骤包括:
接收用户提交的向目标联系人进行转账支付的请求,依据索虎用户请求打开转账支付 插件关联的第三方应用程序的对应入口;
将目标联系人和当前用户的数据通过所述入口传输至所述第三方应用程序,在第三方 应用程序中执行相应的转账支付功能。
应用场景二:
参见图 4, 示出了本公开实施例的向目标联系人送快递的插件的应用场景示例的示意 图。
通讯录的插件包括快递插件, 通讯录接收用户调用该插件功能的请求, 依据所述用户 请求调用该插件的对应功能的步骤包括:
接收用户提交的向目标联系人送快递的请求,依据所述用户请求打开快递插件关联的 第三方应用程序的对应入口;
将目标联系人和当前用户的数据通过所述入口传输至所述第三方应用程序,第三方应 用程序将用户和目标联系人的信息发送至快递公司。
应用场景三:
参见图 5, 示出了本公开实施例的向目标联系人添加人脉信息的插件的应用场景示例 的示意图。
通讯录的插件包括人脉插件, 通讯录接收用户调用该插件功能的请求, 依据用户请求 调用该插件的对应功能的步骤包括:
接收用户提交的向目标联系人进行添加人脉关系的请求,依据所述用户请求进行目标 联系人的人脉关系数据写入, 并打开所述人脉插件关联的第三方应用程序的对应入口; 将所述第三方应用程序中反馈的数据通过所述入口写入目标联系人信息中; 人脉插件将人脉关系数据写入与此人脉关系有关联的联系人信息中。
应用场景四:
参见图 6, 示出了本公开实施例的査询目标联系人地理位置的插件的应用场景示例的 示意图。
通讯录的插件包括位置査询插件, 通讯录接收用户调用该插件功能的请求, 依据所述 用户请求调用该插件的对应功能的步骤包括:
接收用户提交的査询目标联系人地理位置的请求, 依据用户请求, 向目标联系人发送 指定信息, 并打开位置査询插件关联的第三方应用程序的对应入口;
将当前用户和目标联系人回复的数据通过所述入口传输至所述第三方应用程序,在第 三方应用程序中执行相应的位置査询功能。
应用场景五:
参见图 7, 示出了本公开实施例的査询目标联系人名片的插件的应用场景示例的示意 图。
通讯录的插件包括名片插件, 通讯录接收用户调用该插件功能的请求, 依据所述用户 请求调用该插件的对应功能的步骤包括:
接收用户提交的査询目标联系人名片的请求,依据所述用户请求打开名片插件关联的 第三方应用程序的对应入口;
将目标联系人的数据通过所述入口传输至第三方应用程序,在第三方应用程序中执行 相应的査询名片功能。
应用场景六:
参见图 8, 示出了本公开实施例的娱乐应用的插件的应用场景示例的示意图。
通讯录的插件包括算命插件, 通讯录接收用户调用所述插件功能的请求, 依据用户请 求调用该插件的对应功能的步骤包括:
接收用户提交的向目标联系人进行算命的请求,依据所述用户请求打开算命插件关联 的第三方应用程序的对应入口;
将目标联系人和当前用户的数据通过所述入口传输至所述第三方应用程序,在第三方 应用程序中执行相应的算命功能。
应用场景七:
参见图 9, 示出了本公开实施例的与目标联系人进行游戏较量的插件的应用场景示例 的示意图。
通讯录的插件包括游戏中心插件,用户已通过该插件将目标联系人对应的游戏中心的 账号信息写入通讯录的目标联系人信息中, 通讯录接收用户调用该插件功能的请求, 依据 所述用户请求调用该插件的对应功能的步骤包括:
接收用户提交的向目标联系人进行游戏较量的请求,依据用户请求打开游戏中心插件 关联的第三方应用程序的对应入口;
将目标联系人和当前用户的数据通过所述入口传输至所述第三方应用程序,在第三方 应用程序中执行相应的游戏较量功能。
应用场景八:
参见图 10, 示出了本公开实施例的与目标联系人在线语音 /视频通话的插件的应用场 景示例的示意图。
通讯录的插件包括在线语音 /视频通话插件, 用户已通过该插件将目标联系人的在线 语音 /视频通话服务的账号信息写入通讯录的目标联系人信息中, 通过终端设备在线情况 判断对方是否在线, 通讯录接收用户调用所述插件功能的请求, 依据所述用户请求调用该 插件的对应功能的步骤包括:
接收用户提交的向目标联系人进行在线语音 /视频通话的请求, 依据用户请求打开在 线通话插件关联的第三方应用程序的对应入口;
将所述目标联系人和当前用户的数据通过所述入口传输至所述第三方应用程序,在第 三方应用程序中执行相应的在线语音 /视频通话功能。
应用场景九:
参见图 11,示出了本公开实施例的与目标联系人即时聊天的插件的应用场景示例的示 意图。
通讯录的插件包括即时聊天插件,用户已通过该插件将目标联系人即时聊天服务账号 的联系人信息对应写入通讯录的目标联系人信息中,通过终端设备在线情况判断对方是否 在线, 通讯录接收用户调用所述插件功能的请求, 依据所述用户请求调用该插件的对应功 能的步骤包括:
接收用户提交的向目标联系人进行即时聊天的请求,依据用户请求打开即时聊天插件 关联的第三方应用程序的对应入口;
将所述目标联系人和当前用户的数据通过所述入口传输至所述第三方应用程序,在第 三方应用程序中执行相应的即时聊天功能。
应用场景十:
参见图 12,示出了本公开实施例的与目标联系人分享文件的插件的应用场景示例的示 意图。
通讯录的插件包括网盘分享插件,用户已通过该插件将目标联系人的网盘账号信息写 入通讯录的目标联系人信息中, 通讯录接收用户调用该插件功能的请求, 依据所述用户请 求调用该插件的对应功能的步骤包括:
接收用户提交的与目标联系人进行分享文件的请求,依据所述用户请求打开网盘分享 插件关联的第三方应用程序的对应入口;
将目标联系人和当前用户的数据通过所述入口传输至所述第三方应用程序,在第三方 应用程序中执行相应的分享文件功能。
应用场景十一:
参见图 13, 示出了本公开实施例的与目标联系人联机的插件的应用场景示例的示意 图。
通讯录的插件包括双机互联插件,用户已通过该插件将目标联系人对应的联机服务的 账号信息写入通讯录的目标联系人信息中, 通讯录接收用户调用该插件功能的请求, 依据 用户请求调用该插件的对应功能的步骤包括:
接收用户提交的与目标联系人进行联机的请求,依据用户请求打开双机互联插件关联 的第三方应用程序的对应入口;
将所述目标联系人和当前用户的数据通过所述入口传输至所述第三方应用程序,在第 三方应用程序中执行相应的联机功能。
参照图 14,示出了本公开实施例一种在通讯录中添加插件的方法实施例 2的步骤流程 图, 具体可以包括以下步骤:
步骤 201, 接收所述插件的安装请求, 依据所述请求对所述插件进行鉴权; 步骤 202, 鉴权通过后, 在通讯录中添加所述插件;
步骤 203, 判断是否在通讯录中设置了启用该插件的功能; 若是, 则执行步骤 204; 若否, 则执行步骤 205;
步骤 204, 接收用户调用所述插件功能的请求, 依据所述用户请求调用该插件的对应 功能;
步骤 205, 生成用于提示用户是否启用该插件功能的提示信息。
应用本实施例, 在接收用户调用所述插件功能的请求之前, 检测在通讯录中设置了启 用该插件的功能。由于插件的设计理念不同,插件安装后可以默认开启,也可以默认关闭, 或者用户根据需求在关闭所述插件后重新启用, 或者其他情况导致插件关闭, 采用这种方 案, 可以在先检测是否在通讯录中设置启用了该插件, 让用户自行选择, 在需要时开启, 不需要时关闭, 可以节省资源, 提升用户的使用体验。
对于方法实施例, 为了简单描述, 故将其都表述为一系列的动作组合, 但是本领域技 术人员应该知悉,本公开实施例并不受所描述的动作顺序的限制,因为依据本公开实施例, 某些步骤可以采用其他顺序或者同时进行。 其次, 本领域技术人员也应该知悉, 说明书中 所描述的实施例均属于实施例, 所涉及的动作并不一定是本公开实施例所必须的。
参照图 15,示出了一种在通讯录中添加插件的装置实施例的结构框图,所述插件为按 所述接口定义的规范生成的第三方应用程序插件, 具体可以包括如下模块:
请求接收模块 301, 用于接收所述插件的安装请求,
鉴权模块 302, 用于依据所述请求对所述插件进行鉴权;
安装模块 303, 用于在鉴权通过后, 在通讯录中添加所述插件;
调用模块 304, 用于接收用户调用所述插件功能的请求, 依据所述用户请求调用该插 件的对应功能。
在具体实现中, 所述通讯录中可以包括所述用户绑定的账号的联系人信息。
在本公开的一种实施例中, 所述接口定义的规范具体可以包括, 用户界面 UI规范和 预定义的权限规范。
在本公开实施例中, 的是, 所述鉴权模块具体可以包括:
判断子模块, 用于依据所述请求判断所述插件是否采用了用户界面 UI规范以及是否 符合所述预定义的权限规范; 若所述插件采用了用户界面 UI规范以及符合所述预定义的 权限规范, 则调用鉴权通过子模块, 若所述插件没有采用用户界面 UI规范或不符合所述 预定义的权限规范, 则调用第一提示子模块;
鉴权通过子模块, 用于判定鉴权通过;
第一提示子模块, 用于生成用于提示用户判断是否继续安装的提示信息。
在本公开的一种实施例中, 所述添加模块具体可以包括:
展现子模块,用于按照所述接口定义的规范采用指定方式在通讯录的相应位置展现所 述的插件; 安装子模块, 用于安装所述插件携带的功能数据包。
在本公开实施例中, 的是, 所述调用模块具体可以包括:
入口开启子模块, 接收用户调用所述插件功能的请求, 打开所述插件携带的功能数据 包, 通过所述功能数据包开启进入关联的第三方应用程序的对应入口;
数据传输子模块, 将通讯录的数据通过所述入口传输至所述第三方应用程序, 在所述 第三方应用程序中执行相应的功能。
在本公开的一种实施例中, 所述装置还可以包括:
判断模块, 用于判断是否在通讯录中设置了启用该插件的功能; 若在通讯录中设置了 启用该插件的功能, 则调用执行子模块; 若在通讯录中未设置启用该插件的功能, 则调用 第二提示子模块。
执行子模块, 用于执行所述接收用户调用所述插件功能的请求;
第二提示子模块, 用于生成用于提示用户是否启用该插件功能的提示信息。
对于装置实施例而言, 由于其与在通讯录中添加插件的方法实施例基本相似, 所以描 述的比较简单, 相关之处参见在通讯录中添加插件的方法实施例的部分说明即可。
本公开实施例还提供了一种设备, 所述设备可以包括:
一个或多个处理器;
存储器; 和
一个或多个模块,所述一个或多个模块存储于所述存储器中并被配置成由所述一个或 多个处理器执行, 其中, 所述一个或多个模块具有如下功能- 接收所述插件的安装请求, 依据所述请求对所述插件进行鉴权;
当鉴权通过后, 在通讯录中添加所述插件;
接收用户调用所述插件功能的请求, 依据所述用户请求调用该插件的对应功能。 较佳地, 所述接口定义的规范可以包括, 用户界面 UI规范和预定义的权限规范。 较佳地, 所述一个或多个模块可以具有如下功能- 接收所述插件的安装请求, 依据所述请求判断所述插件是否采用了用户界面 υι规范 以及是否符合所述预定义的权限规范;
若所述插件采用了用户界面 υι规范以及符合所述预定义的权限规范, 则判定鉴权通 过;
若所述插件没有采用用户界面 UI规范或不符合所述预定义的权限规范, 则生成用于 提示用户判断是否继续安装的提示信息。
较佳地, 所述一个或多个模块可以具有如下功能- 按照所述接口定义的规范采用指定方式在通讯录的相应位置展现所述的插件; 安装所述插件携带的功能数据包。
较佳地, 所述一个或多个模块可以具有如下功能- 判断是否在通讯录中设置了启用该插件的功能; 若在通讯录中设置了启用该插件的功能,则执行所述接收用户调用所述插件功能的请 求;
若在通讯录中未设置启用该插件的功能,则生成用于提示用户是否启用该插件功能的 提示信息。
较佳地, 所述一个或多个模块可以具有如下功能- 接收用户调用所述插件功能的请求, 打开所述插件携带的功能数据包, 通过所述功能 数据包开启进入关联的第三方应用程序的对应入口;
将通讯录的数据通过所述入口传输至所述第三方应用程序,在所述第三方应用程序中 执行相应的功能。
较佳地, 所述通讯录中可以包括所述用户绑定的账号的联系人信息。
本实施例还提供了一种非易失性可读存储介质,该存储介质中存储有一个或多个模块 (programs) , 该一个或多个模块被应用在具有通讯录的设备时, 可以使得该设备执行如 下步骤的指令 (instructions) :
接收所述插件的安装请求, 依据所述请求对所述插件进行鉴权;
当鉴权通过后, 在通讯录中添加所述插件;
接收用户调用所述插件功能的请求, 依据所述用户请求调用该插件的对应功能。 较佳地, 所述接口定义的规范可以包括, 用户界面 UI规范和预定义的权限规范。 较佳地, 所述一个或多个模块可以具有如下功能- 接收所述插件的安装请求, 依据所述请求判断所述插件是否采用了用户界面 UI规范 以及是否符合所述预定义的权限规范;
若所述插件采用了用户界面 UI规范以及符合所述预定义的权限规范, 则判定鉴权通 过;
若所述插件没有采用用户界面 UI规范或不符合所述预定义的权限规范, 则生成用于 提示用户判断是否继续安装的提示信息。
较佳地, 所述一个或多个模块可以具有如下功能- 按照所述接口定义的规范采用指定方式在通讯录的相应位置展现所述的插件; 安装所述插件携带的功能数据包。
较佳地, 所述一个或多个模块可以具有如下功能- 判断是否在通讯录中设置了启用该插件的功能;
若在通讯录中设置了启用该插件的功能,则执行所述接收用户调用所述插件功能的请 求;
若在通讯录中未设置启用该插件的功能,则生成用于提示用户是否启用该插件功能的 提示信息。
较佳地, 所述一个或多个模块可以具有如下功能- 接收用户调用所述插件功能的请求, 打开所述插件携带的功能数据包, 通过所述功能 数据包开启进入关联的第三方应用程序的对应入口;
将通讯录的数据通过所述入口传输至所述第三方应用程序,在所述第三方应用程序中 执行相应的功能。
较佳地, 所述通讯录中可以包括所述用户绑定的账号的联系人信息。
对于设备实施例而言, 由于其与在通讯录中添加插件的方法实施例基本相似, 所以描 述的比较简单, 相关之处参见在通讯录中添加插件的方法实施例的部分说明即可。
本说明书中的各个实施例均采用递进的方式描述,每个实施例重点说明的都是与其他 实施例的不同之处, 各个实施例之间相同相似的部分互相参见即可。
本领域内的技术人员应明白, 本公开实施例的实施例可提供为方法、 装置、 或计算机 程序产品。 因此, 本公开实施例可采用完全硬件实施例、 完全软件实施例、 或结合软件和 硬件方面的实施例的形式。而且, 本公开实施例可采用在一个或多个其中包含有计算机可 用程序代码的计算机可用存储介质 (包括但不限于磁盘存储器、 CD-ROM、 光学存储器等) 上实施的计算机程序产品的形式。
本公开实施例是参照根据本公开实施例的方法、 终端设备 (系统)、 和计算机程序产品 的流程图和 I或方框图来描述的。应理解可由计算机程序指令实现流程图和 I或方框图中 的每一流程和 /或方框、 以及流程图和 /或方框图中的流程和 /或方框的结合。 可提供这 些计算机程序指令到通用计算机、专用计算机、 嵌入式处理机或其他可编程数据处理终端 设备的处理器以产生一个机器,使得通过计算机或其他可编程数据处理终端设备的处理器 执行的指令产生用于实现在流程图一个流程或多个流程和 /或方框图一个方框或多个方 框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理终端设备以特 定方式工作的计算机可读存储器中,使得存储在该计算机可读存储器中的指令产生包括指 令装置的制造品,该指令装置实现在流程图一个流程或多个流程和 I或方框图一个方框或 多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理终端设备上,使得在计 算机或其他可编程终端设备上执行一系列操作步骤以产生计算机实现的处理,从而在计算 机或其他可编程终端设备上执行的指令提供用于实现在流程图一个流程或多个流程和 / 或方框图一个方框或多个方框中指定的功能的步骤。
尽管已描述了本公开实施例的实施例,但本领域内的技术人员一旦得知了基本创造性 概念, 则可对这些实施例做出另外的变更和修改。 所以, 所附权利要求意欲解释为包括实 施例以及落入本公开实施例范围的所有变更和修改。
最后, 还需要说明的是, 在本文中, 诸如第一和第二等之类的关系术语仅仅用来将一 个实体或者操作与另一个实体或操作区分开来,而不一定要求或者暗示这些实体或操作之 间存在任何这种实际的关系或者顺序。 而且, 术语"包括"、 "包含 "或者其任何其他变体意 在涵盖非排他性的包含, 从而使得包括一系列要素的过程、 方法、 物品或者终端设备不仅 包括那些要素, 而且还包括没有明确列出的其他要素, 或者是还包括为这种过程、 方法、 物品或者终端设备所固有的要素。 在没有更多限制的情况下, 由语句 "包括一个 ...... "限定 的要素, 并不排除在包括所述要素的过程、 方法、 物品或者终端设备中还存在另外的相同 要素。
以上对本公开实施例所提供的一种在通讯录中添加插件的方法、一种在通讯录中添加 插件的装置和一种设备, 进行了详细介绍, 本文中应用了具体个例对本公开实施例的原理 及实施方式进行了阐述, 以上实施例的说明只是用于帮助理解本公开实施例的方法及其核 心思想; 同时, 对于本领域的一般技术人员, 依据本公开实施例的思想, 在具体实施方式 及应用范围上均会有改变之处, 综上所述, 本说明书内容不应理解为对本公开实施例的限 制。

Claims

权利要求
1、 一种在通讯录中添加插件的方法, 其特征在于, 所述通讯录具有开放的接口, 所 述插件为按所述接口定义的规范生成的第三方应用程序插件; 所述的方法包括:
接收所述插件的安装请求, 依据所述请求对所述插件进行鉴权;
当鉴权通过后, 在通讯录中添加所述插件;
接收用户调用所述插件功能的请求, 依据所述用户请求调用所述插件的对应功能。
2、 根据权利要求 1所述的方法, 其特征在于, 所述接口定义的规范包括, 用户界面 UI规范和预定义的权限规范。
3、 根据权利要求 2所述的方法, 其特征在于, 所述接收所述插件的安装请求, 依据 所述请求对所述插件进行鉴权的步骤包括:
接收所述插件的安装请求, 依据所述请求判断所述插件是否采用了用户界面 UI规范 以及是否符合所述预定义的权限规范;
若所述插件采用了用户界面 UI规范以及符合所述预定义的权限规范, 则判定鉴权通 过;
若所述插件没有采用用户界面 UI规范或不符合所述预定义的权限规范, 则生成用于 提示用户判断是否继续安装的提示信息。
4、 根据权利要求 1或 2或 3所述的方法, 其特征在于, 所述在通讯录中添加插件的 步骤包括:
按照所述接口定义的规范采用指定方式在通讯录的相应位置展现所述的插件; 安装所述插件携带的功能数据包。
5、 根据权利要求 1或 2或 3所述的方法, 其特征在于, 在接收用户调用所述插件功 能的请求的步骤之前, 还包括:
判断是否在通讯录中设置了启用所述插件的功能;
若在通讯录中设置了启用所述插件的功能,则执行所述接收用户调用所述插件功能的 请求;
若在通讯录中未设置启用所述插件的功能,则生成用于提示用户是否启用所述插件功 能的提示信息。
6、 根据权利要求 4所述的方法, 其特征在于, 所述接收用户调用所述插件功能的请 求, 依据所述用户请求调用所述插件的对应功能的步骤包括:
接收用户调用所述插件功能的请求,打开所述插件携带的功能数据包,通过所述功能 数据包开启进入关联的第三方应用程序的对应入口;
将通讯录的数据通过所述入口传输至所述第三方应用程序,在所述第三方应用程序中 执行相应的功能。
7、 根据权利要求 1或 2或 3或 6所述的方法, 其特征在于, 所述通讯录中包括所述 用户绑定的账号的联系人信息。
8、 一种在通讯录中添加插件的装置, 其特征在于, 所述通讯录具有开放的接口, 所 述插件为按所述接口定义的规范生成的第三方应用程序插件; 所述的装置包括:
请求接收模块, 用于接收所述插件的安装请求;
鉴权模块, 用于依据所述请求对所述插件进行鉴权;
添加模块, 用于在鉴权通过后, 在通讯录中添加所述插件;
调用模块,用于接收用户调用所述插件功能的请求,依据所述用户请求调用所述插件 的对应功能。
9、 根据权利要求 8所述的装置, 其特征在于, 所述接口定义的规范包括, 用户界面 UI规范和预定义的权限规范。
10、 根据权利要求 9所述的装置, 其特征在于, 所述鉴权模块包括:
权限规范判断子模块, 用于依据所述请求判断所述插件是否采用了用户界面 UI规范 以及是否符合所述预定义的权限规范;
若所述插件采用了用户界面 UI规范以及符合所述预定义的权限规范, 则调用鉴权通 过子模块, 若所述插件没有采用用户界面 UI规范或不符合所述预定义的权限规范, 则调 用第一提示子模块;
鉴权通过子模块, 用于判定鉴权通过;
第一提示子模块, 用于生成用于提示用户判断是否继续安装的提示信息。
11、 根据权利要求 8或 9或 10所述的装置, 其特征在于, 所述添加模块包括: 展现子模块,用于按照所述接口定义的规范采用指定方式在通讯录的相应位置展现所 述的插件;
安装子模块, 用于安装所述插件携带的功能数据包。
12、 根据权利要求 8或 9或 10所述的装置, 其特征在于, 还包括:
启用判断模块,用于判断是否在通讯录中设置了启用所述插件的功能;若在通讯录中 设置了启用所述插件的功能,则调用执行子模块;若在通讯录中未设置启用所述插件的功 能, 则调用第二提示子模块。
执行子模块, 用于执行所述接收用户调用所述插件功能的请求;
第二提示子模块, 用于生成用于提示用户是否启用所述插件功能的提示信息。
13、 根据权利要求 11所述的装置, 其特征在于, 所述调用模块包括:
入口开启子模块,用于接收用户调用所述插件功能的请求,打开所述插件携带的功能 数据包, 通过所述功能数据包开启进入关联的第三方应用程序的对应入口;
数据传输子模块,用于将通讯录的数据通过所述入口传输至所述第三方应用程序,在 所述第三方应用程序中执行相应的功能。
14、 一种设备, 其特征在于, 包括:
一个或多个处理器; 存储器; 和
一个或多个模块,所述一个或多个模块存储于所述存储器中并被配置成由所述一个或 多个处理器执行, 其中, 所述一个或多个模块具有如下功能- 接收所述插件的安装请求, 依据所述请求对所述插件进行鉴权;
当鉴权通过后, 在通讯录中添加所述插件;
接收用户调用所述插件功能的请求, 依据所述用户请求调用所述插件的对应功能。
PCT/CN2013/085883 2013-04-11 2013-10-24 一种在通讯录中添加插件的方法、装置和设备 WO2014166227A1 (zh)

Priority Applications (7)

Application Number Priority Date Filing Date Title
RU2015125631A RU2630553C2 (ru) 2013-04-11 2013-10-24 Способ, инструментарий и устройство для добавления подключаемого расширения в адресную книгу
KR1020157014010A KR101726526B1 (ko) 2013-04-11 2013-10-24 주소록에 플러그인을 추가하는 방법, 장치, 기기, 프로그램 및 기록매체
JP2015543270A JP6074516B2 (ja) 2013-04-11 2013-10-24 アドレス帳にプラグインを追加する方法、装置、設備、プログラム及び記録媒体
EP13881497.5A EP2985701A4 (en) 2013-04-11 2013-10-24 METHOD, MACHINE AND DEVICE FOR INSERTING PLUG-INS IN AN ADDRESS BOOK
MX2015008271A MX346616B (es) 2013-04-11 2013-10-24 Método, aparato y dispositivo para agregar un complemento a una libreta de direcciones.
BR112015016505A BR112015016505A2 (pt) 2013-04-11 2013-10-24 método, aparelho e dispositivo para adicionar plug-in em livro de endereços
US14/156,756 US20140310606A1 (en) 2013-04-11 2014-01-16 Method and device for providing plugin in contact list

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201310125562.4 2013-04-11
CN201310125562.4A CN103246533B (zh) 2013-04-11 2013-04-11 一种在通讯录中添加插件的方法、装置和设备

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US14/156,756 Continuation US20140310606A1 (en) 2013-04-11 2014-01-16 Method and device for providing plugin in contact list

Publications (1)

Publication Number Publication Date
WO2014166227A1 true WO2014166227A1 (zh) 2014-10-16

Family

ID=48926065

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2013/085883 WO2014166227A1 (zh) 2013-04-11 2013-10-24 一种在通讯录中添加插件的方法、装置和设备

Country Status (8)

Country Link
EP (1) EP2985701A4 (zh)
JP (1) JP6074516B2 (zh)
KR (1) KR101726526B1 (zh)
CN (1) CN103246533B (zh)
BR (1) BR112015016505A2 (zh)
MX (1) MX346616B (zh)
RU (1) RU2630553C2 (zh)
WO (1) WO2014166227A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2017536718A (ja) * 2015-09-17 2017-12-07 小米科技有限責任公司Xiaomi Inc. 応答拡張機能を表示する方法及び装置

Families Citing this family (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103246533B (zh) * 2013-04-11 2017-03-29 小米科技有限责任公司 一种在通讯录中添加插件的方法、装置和设备
CN104135566A (zh) * 2014-07-15 2014-11-05 北京奇虎科技有限公司 信息提供方法及客户端
CN104391700A (zh) * 2014-11-11 2015-03-04 百度在线网络技术(北京)有限公司 应用程序功能扩展方法和装置
CN104407889B (zh) * 2014-11-11 2018-09-07 百度在线网络技术(北京)有限公司 应用程序的修复方法和装置
CN104732380A (zh) * 2015-02-16 2015-06-24 小米科技有限责任公司 一种进行转账处理的方法和装置
CN105678525A (zh) * 2016-04-07 2016-06-15 陈包容 一种通讯录集成手机办公系统的方法及装置
CN108323236B (zh) * 2016-12-27 2021-02-12 华为技术有限公司 一种交互方法和终端
CN106941556B (zh) * 2017-04-20 2020-08-04 青岛海信移动通信技术股份有限公司 融合通信联系人信息的确定方法及装置
CN110908728B (zh) * 2018-09-15 2021-04-09 Oppo广东移动通信有限公司 权限配置方法及相关产品
CN109409081B (zh) * 2018-10-30 2023-06-27 努比亚技术有限公司 一种权限设置方法、移动终端以及计算机存储介质
CN109725952B (zh) * 2019-01-07 2021-09-24 深圳市网心科技有限公司 一种应用程序插件化的方法、系统以及相关装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101699405A (zh) * 2009-10-26 2010-04-28 中兴通讯股份有限公司 一种宿主程序和插件及插件间进行交互的方法及装置
CN101796486A (zh) * 2007-05-30 2010-08-04 索尼爱立信移动通讯有限公司 增强的本机通讯录应用
CN103036871A (zh) * 2012-11-19 2013-04-10 北京奇虎科技有限公司 浏览器应用插件支持装置和方法
CN103246533A (zh) * 2013-04-11 2013-08-14 北京小米科技有限责任公司 一种在通讯录中添加插件的方法、装置和设备

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6874143B1 (en) * 2000-06-21 2005-03-29 Microsoft Corporation Architectures for and methods of providing network-based software extensions
US7000230B1 (en) * 2000-06-21 2006-02-14 Microsoft Corporation Network-based software extensions
US7698685B2 (en) * 2005-10-12 2010-04-13 Microsoft Corporation Discovery, qualification, and activation of software add-in components
CN101291305A (zh) * 2008-06-25 2008-10-22 腾讯科技(深圳)有限公司 实现插件管理的方法及客户端
WO2009156964A1 (en) * 2008-06-25 2009-12-30 Nokia Corporation Launching an application
US8401973B1 (en) * 2009-11-19 2013-03-19 Adobe Systems Incorporated Method and system for managing a license for an add-on software component
KR101482151B1 (ko) * 2010-05-11 2015-01-14 에스케이플래닛 주식회사 웹 어플리케이션 실행 장치 및 방법
CN102682014A (zh) * 2011-03-14 2012-09-19 腾讯科技(深圳)有限公司 在浏览器上实现的开放式插件管理平台及插件管理方法
CN102609267B (zh) * 2012-02-16 2015-02-18 深圳市酷开网络科技有限公司 基于安卓浏览器的插件管理方法及系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101796486A (zh) * 2007-05-30 2010-08-04 索尼爱立信移动通讯有限公司 增强的本机通讯录应用
CN101699405A (zh) * 2009-10-26 2010-04-28 中兴通讯股份有限公司 一种宿主程序和插件及插件间进行交互的方法及装置
CN103036871A (zh) * 2012-11-19 2013-04-10 北京奇虎科技有限公司 浏览器应用插件支持装置和方法
CN103246533A (zh) * 2013-04-11 2013-08-14 北京小米科技有限责任公司 一种在通讯录中添加插件的方法、装置和设备

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2017536718A (ja) * 2015-09-17 2017-12-07 小米科技有限責任公司Xiaomi Inc. 応答拡張機能を表示する方法及び装置

Also Published As

Publication number Publication date
KR101726526B1 (ko) 2017-04-12
BR112015016505A2 (pt) 2017-07-11
MX2015008271A (es) 2015-09-29
EP2985701A1 (en) 2016-02-17
EP2985701A4 (en) 2016-04-06
RU2630553C2 (ru) 2017-09-12
MX346616B (es) 2017-03-23
CN103246533A (zh) 2013-08-14
RU2015125631A (ru) 2017-01-10
KR20150080578A (ko) 2015-07-09
JP6074516B2 (ja) 2017-02-01
JP2015537305A (ja) 2015-12-24
CN103246533B (zh) 2017-03-29

Similar Documents

Publication Publication Date Title
WO2014166227A1 (zh) 一种在通讯录中添加插件的方法、装置和设备
US9705887B2 (en) Remote processsing of mobile applications
US20200012810A1 (en) Exported digital relationships
US10063547B2 (en) Authorization authentication method and apparatus
US9338156B2 (en) System and method for integrating two-factor authentication in a device
JP5429912B2 (ja) 認証システム、認証サーバ、サービス提供サーバ、認証方法、及びプログラム
US20140310606A1 (en) Method and device for providing plugin in contact list
US11190522B2 (en) Access delegation using offline token
WO2013182006A1 (zh) 一种用于拦截应用程序对服务的调用的方法和装置
US9838869B1 (en) Delivering digital content to a mobile device via a digital rights clearing house
CN105512576A (zh) 一种数据安全存储的方法及电子设备
CA2828258C (en) Smart plug or cradle
WO2017088548A1 (zh) 基于社交身份的通信方法及服务器
US20150244664A1 (en) Enterprise messaging platform
US20230186304A1 (en) Transaction Validation Service
US20170244841A1 (en) Methods, systems, and apparatus for controlling a mobile
CN111949959A (zh) Oauth协议中的授权认证方法及装置
CN117716667A (zh) 针对web应用的基于代理的身份和访问管理
US9455972B1 (en) Provisioning a mobile device with a security application on the fly
KR20150003297A (ko) 사이버 id를 이용하여 보안 트랜잭션을 제공하는 방법 및 시스템
US8635692B2 (en) System and method for user friendly detection of spammers
CN112286632B (zh) 云平台、云平台管理方法、装置、电子设备及储存介质
CN107230080B (zh) 一种业务处理方法、装置和智能终端
WO2018010256A1 (zh) 一种wifi共享的方法和装置
CN108270741B (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: 13881497

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2015543270

Country of ref document: JP

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 20157014010

Country of ref document: KR

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: MX/A/2015/008271

Country of ref document: MX

ENP Entry into the national phase

Ref document number: 2015125631

Country of ref document: RU

Kind code of ref document: A

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: 112015016505

Country of ref document: BR

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 2013881497

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 112015016505

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20150709