WO2020019291A1 - 信息处理方法、电子设备、服务器和信息处理系统 - Google Patents

信息处理方法、电子设备、服务器和信息处理系统 Download PDF

Info

Publication number
WO2020019291A1
WO2020019291A1 PCT/CN2018/097404 CN2018097404W WO2020019291A1 WO 2020019291 A1 WO2020019291 A1 WO 2020019291A1 CN 2018097404 W CN2018097404 W CN 2018097404W WO 2020019291 A1 WO2020019291 A1 WO 2020019291A1
Authority
WO
WIPO (PCT)
Prior art keywords
added service
software value
electronic device
purchase request
identifier
Prior art date
Application number
PCT/CN2018/097404
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 PCT/CN2018/097404 priority Critical patent/WO2020019291A1/zh
Priority to CN201880041770.7A priority patent/CN110859046A/zh
Publication of WO2020019291A1 publication Critical patent/WO2020019291A1/zh

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/40Network security protocols
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/10Protecting distributed programs or content, e.g. vending or licensing of copyrighted material ; Digital rights management [DRM]
    • G06F21/12Protecting executable software
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/30Authentication, i.e. establishing the identity or authorisation of security principals
    • G06F21/44Program or device authentication

Definitions

  • the present application relates to the field of information processing technologies, and in particular, to an information processing method, an electronic device, a server, and an information processing system.
  • the service provider After the user purchases the software value-added service, the service provider sends the activation credential containing the activation information (usually including the activation card number, password, and verification code) to the user.
  • the electronic device After the user enters the activation information in the electronic device, the electronic device sends the activation information to Server authentication, after the server determines that the activation information is the activation information issued by the server, authorizes the electronic device to use the software value-added server that has been purchased.
  • This application provides an information processing method, an electronic device, a server, and an information processing system, with the aim of reducing the probability of misappropriation of software services purchased by users.
  • the present application provides an information processing method, including:
  • the first electronic device or the second electronic device sends a software value-added service purchase request to the server, and the software value-added service purchase request carries a device identifier of the first electronic device;
  • the server After the server successfully purchases the software value-added service, the server binds the device identifier to the software value-added service, and sends an activation verification code bound to the software value-added service to a user preset receiver;
  • the first electronic device After receiving the activation verification code input by the user, the first electronic device sends an authorization request to the server, where the authorization request carries the activation verification code and the device identifier;
  • the server After the server receives the authorization request, if the activation verification code and the device identification carried in the authorization request match the activation verification code and the device identification on the server side, the software value-added service is activated.
  • the present application provides a data processing method and an information processing method, which are applied to an electronic device and include:
  • an authorization request is sent to the server, where the authorization request carries the activation verification code and the device identification, so that the server receives the authorization request. Then, if the activation verification code and the device identification carried in the authorization request match the activation verification code and the device identification code on the server side, the software value-added service is activated.
  • the present application provides an information processing method, which is applied to a server and includes:
  • the activation verification code and device identification carried in the authorization request are related to the server-side activation verification Both the code and the device identification match, and the software value-added service is activated.
  • the present application provides an information processing system including: an electronic device and a server; the electronic device includes a first electronic device, or the electronic device includes a first electronic device and a second electronic device;
  • the first electronic device or the second electronic device is configured to send a software value-added service purchase request to the server, and the software value-added service purchase request carries a device identifier of the first electronic device;
  • the server is configured to bind the device identification with the software value-added service after the software value-added service is successfully purchased, and send an activation verification code corresponding to the software value-added service to a preset receiver of the user;
  • the first electronic device is further configured to send an authorization request to the server after acquiring the activation verification code, where the authorization request carries the activation verification code and the device identifier;
  • the server is further configured to, after receiving the authorization request, activate the software value-added service if the activation verification code and device identification carried in the authorization request match the activation verification code and device identification of the server.
  • the present application provides an electronic device, including:
  • the first sending module is configured to send a software value-added service purchase request to the server, where the software value-added service purchase request carries a device identifier of the electronic device, so that the server will send a software value-added service after the software value-added service purchase is successful.
  • the device identifier is bound to the software value-added service, and sends an activation verification code bound to the software value-added service to a receiver preset by a user;
  • a second sending module configured to send an authorization request to the server after receiving the activation verification code input by a user, where the authorization request carries the activation verification code and the device identifier, so that the server After receiving the authorization request, if the activation verification code and the device identification carried in the authorization request match both the server-side activation verification code and the device identification code, the software value-added service is activated.
  • the present application provides a server, including:
  • a first receiving module configured to receive a software value-added service purchase request, where the software value-added service purchase request carries a device identification of a first electronic device;
  • a fourth sending module configured to bind the device identifier to the software value-added service after the software value-added service is successfully purchased, and send an activation bound to the software value-added service to a user preset receiver Verification code
  • An authorization module is configured to, after receiving an authorization request sent by the first electronic device and carrying the activation verification code and the device identifier, if the activation verification code and device identification carried in the authorization request are related to all The server-side activation verification code and the device identification match, and the software value-added service is activated.
  • an information processing method, an electronic device, a server, and an information processing system provided in the embodiments of the present application, after a user purchases a software value-added service, compare the software value-added service purchased by the user with the device identification of the terminal device used by the user Binding.
  • the software value-added service needs to be activated, after the user enters the activation verification code in the electronic device, the authorization request sent by the electronic device to the server includes the activation verification code and the device identification of the terminal device, so that the server receives the authorization After the request, the user is verified based on the device identification and activation verification code.
  • FIG. 1 is a schematic diagram of an information processing method according to an embodiment of the present invention
  • FIG. 2 is an implementation flowchart of an information processing method according to an embodiment of the present invention
  • FIG. 3 is an implementation flowchart of a software value-added service purchase request sent by a first electronic device to a server according to an embodiment of the present invention
  • FIG. 4 is another implementation flowchart of the first electronic device sending a software value-added service purchase request to a server according to an embodiment of the present invention
  • FIG. 5 is another implementation flowchart of an information processing method according to an embodiment of the present invention.
  • FIG. 6 is another implementation flowchart of an information processing method according to an embodiment of the present invention.
  • FIG. 7 is a schematic structural diagram of an information processing system according to an embodiment of the present invention.
  • FIG. 8 is a schematic structural diagram of an electronic device according to an embodiment of the present invention.
  • FIG. 9 is a schematic structural diagram of a server according to an embodiment of the present invention.
  • FIG. 1 is a schematic diagram of an information processing method according to an embodiment of the present application.
  • the user sends a software value-added service purchase request to the server through the first electronic device or the second electronic device, and the software value-added service purchase request carries a device identifier of the first electronic device.
  • the server binds the device identification of the first electronic device to the software value-added service, and returns an activation verification code bound to the software value-added service to the user.
  • the user enters the activation verification code into the first electronic device, and the first electronic device sends an authorization request to the server.
  • the authorization request carries the identification of the software value-added service, the activation verification code entered by the user, and the device identification of the first electronic device.
  • the server receives the authorization request sent by the first electronic device, if the activation verification code and device identification carried in the authorization request match the server-side activation verification code and device identification, the software value-added service is activated, otherwise the software value-added service is not activated .
  • the identification and identification of the first electronic device is unique to the first electronic device, even if the activation verification code is stolen, since the device identification of the electronic device using the stolen activation verification code is different from the device identification of the first electronic device, the software Value-added services cannot be activated, thereby avoiding activating the software value-added services on other electronic devices after the activation verification code is stolen, reducing the probability of software value-added services being stolen.
  • FIG. 2 is an implementation flowchart of an information processing method according to an embodiment of the present application, which may include:
  • Step S21 The first electronic device or the second electronic device sends a software value-added service purchase request to the server, and the software value-added service purchase request carries a device identifier of the first electronic device.
  • the software value-added service may be purchased through the first electronic device, or the software value-added service may be purchased through the second electronic device.
  • the first electronic device may automatically obtain the device identification of the first electronic device, or the user may manually enter the device identification of the first electronic device.
  • the user may manually input the device identification of the first electronic device.
  • the software value-added service purchase request carries the identifier of the software value-added service to be purchased. Unlike the prior art, in the embodiment of the present application, the software value-added service purchase request carries the identifier of the software value-added service to be purchased. Carrying the device identification of the first electronic device.
  • Step S22 After the software value-added service is successfully purchased, the server binds the device identification of the first electronic device to the software value-added service, and sends an activation verification code bound to the software value-added service to a user preset receiver.
  • the server after the software value-added service is successfully purchased, the server only returns the activation verification code to the user, and does not need to return the activation card number and password to the user.
  • the server binds the software value-added service with the device identification of the first electronic device.
  • a server can be an independent server or a server group consisting of two or more servers.
  • the user's preset receiver can be a short message receiver, such as a mobile phone number; it can also be a mail receiver, such as an email address; or, it can be another receiver that can receive information, such as the user's on the first electronic device.
  • the activation verification codes bound to different software value-added services may be the same or different.
  • the activation verification code bound to the software value-added service can be generated in advance by the server. Then, when different electronic devices purchase the software value-added service, the corresponding activation verification code is the same.
  • the activation verification code bound to the software value-added service may also be generated after the server binds the device identifier. At this time, the server may generate the activation verification code by using the identification identifier of the first electronic device. Then, when different electronic devices purchase the software value-added service, the corresponding activation verification codes may be the same or different. In this case, the activation verification code is also bound to the device identification of the first electronic device.
  • Step S23 After receiving the activation verification code input by the user, the first electronic device sends an authorization request to the server, where the authorization request carries the activation verification code input by the user and the device identification of the first electronic device.
  • the user checks the activation verification code through the preset receiver, and enters the activation verification code into the first electronic device. Specifically, the user enters the activation verification code into the software that provides the software value-added service in the first electronic device. After that, the user triggers the software to generate and send an authorization request to request the server to activate the software value-added service.
  • the device identification of the first electronic device may be obtained automatically by software, or may be manually input by a user. If the device identification of the first electronic device is manually input by the user, after the user inputs the device identification of the first electronic device into the software, the software is triggered to generate and send an authorization request.
  • the authorization request carries information such as the activation card number, password, and verification code.
  • the authorization request carries the activation verification code and the device identification of the first electronic device.
  • Step S24 After the server receives the authorization request, if the activation verification code and the device identification carried in the authorization request match the server-side activation verification code and the device identification, the software value-added service is activated.
  • the authorization request carries the identifier of the software value-added service to be activated.
  • the server can determine the activation verification code and device identifier that are bound to the software value-added service based on the software value-added service identifier. (Hereinafter referred to as the server-side activation verification code and device identification), the server compares the activation verification code and device identification carried in the authorization request with the server-side activation verification code and device identification. If they are the same, the authorization request is explained The activation verification code and device identification carried in the server match the activation verification code and device identification on the server side, and then the software value-added service is activated. Thereafter, the first electronic device user can use the software value-added service.
  • the authorization request may not carry the identifier of the software value-added service to be activated.
  • the server checks whether any software value-added service is bound to the activation verification code and device identification carried in the authorization request. If found, it indicates that the activation verification code and device identification carried in the authorization request are related to the server. If both the activation verification code and the device identification match, the software value-added service is activated. Thereafter, the first electronic device user can use the software value-added service.
  • the information processing method provided in this application also sends the device identification of the electronic device using the software value-added service to the server when purchasing the software value-added service.
  • the device identification of the electronic device using the software value-added service Binding with the software value-added service, so the activation verification code bound to the software value-added service can only be used for electronic devices bound to the software value-added service, avoiding the activation of the software value-added service on other electronic devices after the activation verification code is stolen, which reduces the Probability of software value-added services being stolen.
  • the information processing method provided in this application may further include:
  • the first electronic device or the second electronic device sends a software value-added service viewing request to the server, and the software value-added service viewing request carries a device identification of the first electronic device.
  • the user After the user purchases the software value-added service, the user can view the information about the software value-added service that he has purchased on the first electronic device or the second electronic device.
  • the server After receiving the software value-added service viewing request, the server returns to the receiver preset by the user information about the software value-added service bound to the device identification of the first electronic device.
  • the server After receiving the software value-added service viewing request, the server determines the bound software value-added service according to the device identification carried in the software value-added service viewing request, and then obtains the related information about the determined software value-added service.
  • the related information of the software value-added service may include: attribute information of the software value-added service, for example, the name or identification of the software value-added service, version, purchase time, use period, and so on.
  • the user does not need to activate the software value-added service (ie, does not need to enter an activation verification code) to view the software value-added service that has been purchased. Even if the user is required to input the device identification of the electronic device, compared with the prior art that requires the user to input multiple information (activation card number, password, verification code, etc.), the amount of information input by the user is also small, thus simplifying user operations.
  • an implementation flowchart of a software value-added service purchase request sent by the first electronic device to the server may include:
  • Step S31 The first electronic device obtains an identifier of the software value-added service input by the user.
  • the identification of the software value-added service may be input by a user through a keyboard, or may be selected and input through a software value-added service list provided by the first electronic device.
  • Step S32 When the first electronic device obtains the purchase request sending instruction carrying the identifier of the software value-added service, it obtains the device identifier corresponding to the account currently used by the user according to the preset correspondence between the user account and the device identifier.
  • the first electronic device After the user inputs the identification of the software value-added service, the first electronic device is triggered to generate a purchase request sending instruction (the instruction carries the identification of the software value-added service input by the user) to instruct the first electronic device to send a purchase request.
  • a purchase request sending instruction the instruction carries the identification of the software value-added service input by the user
  • the device identification of the first electronic device is entered into the first electronic device according to the portal provided by the first electronic device, so that the first electronic device establishes a user account. Correspondence with device identification.
  • Step S33 The first electronic device generates a software value-added service purchase request, and the software value-added service purchase request encapsulates a device identifier and a software value-added service identifier.
  • Step S34 The first electronic device sends a software value-added service purchase request to the server.
  • the first electronic device automatically obtains the device identifier of the first electronic device and generates a purchase request according to the correspondence between the user account and the device identifier.
  • another implementation flowchart of sending a software value-added service purchase request by the first electronic device to the server may include:
  • Step S41 The first electronic device obtains an identifier of a software value-added service input by a user.
  • the identification of the software value-added service may be input by a user through a keyboard, or may be selected and input through a software value-added service list provided by the first electronic device.
  • Step S42 When the first electronic device obtains the purchase request sending instruction carrying the identifier of the software value-added service, it reads the device identifier of the first electronic device through a preset interface.
  • the first electronic device After the user inputs the identification of the software value-added service, the first electronic device is triggered to generate a purchase request sending instruction (the instruction carries the identification of the software value-added service input by the user) to instruct the first electronic device to send a purchase request.
  • a purchase request sending instruction the instruction carries the identification of the software value-added service input by the user
  • the first electronic device itself provides an interface through which the first electronic device can read the device identification of the first electronic device.
  • Step S43 The first electronic device generates a software value-added service purchase request, and the software value-added service purchase request encapsulates a device identifier of the first electronic device and the identifier of the software value-added service.
  • Step S44 The first electronic device sends a software value-added service purchase request to the server.
  • the first electronic device automatically obtains the device identification of the first electronic device without requiring any operation by the user, which simplifies user operations.
  • an implementation manner in which the first electronic device or the second electronic device sends a software value-added service purchase request to the server may be:
  • the first electronic device or the second electronic device obtains the identifier of the software value-added service input by the user, and the device identifier of the first electronic device.
  • the first electronic device or the second electronic device When the first electronic device or the second electronic device obtains the purchase request sending instruction, it generates a software value-added service purchase request, and the software value-added service purchase request encapsulates a device identifier input by the user and an identifier of the software value-added service input by the user.
  • the first electronic device or the second electronic device sends a software value-added service purchase request to the server.
  • each time a software value-added service is purchased the user manually enters the device identification of the first electronic device.
  • FIG. 5 Another implementation flowchart of the information processing method provided by this embodiment of the present application may include:
  • Step S51 Send a software value-added service purchase request to the server, where the software value-added service purchase request carries the device identification of the first electronic device, so that the server can identify the device of the first electronic device and the software after the software value-added service purchase is successful.
  • the value-added service is bound, and an activation verification code bound to the software value-added service is sent to a receiver preset by the user.
  • the software value-added service can be purchased through the first electronic device or the second electronic device.
  • the first electronic device may automatically obtain the device identification of the first electronic device, or the user may manually enter the device identification of the first electronic device.
  • the software value-added service purchase request carries the identifier of the software value-added service to be purchased. Unlike the prior art, in the embodiment of the present application, the software value-added service purchase request carries the identifier of the software value-added service to be purchased. Carrying the device identification of the first electronic device.
  • the server After the software value-added service is successfully purchased, the server only returns the activation verification code to the user, and does not need to return the activation card number and password to the user. In addition, the server binds the software value-added service with the device identification of the first electronic device.
  • a server can be an independent server or a server group consisting of two or more servers.
  • the user's preset receiver can be a short message receiver, such as a mobile phone number; it can also be a mail receiver, such as an email address; or, it can be another receiver that can receive information, such as the user's on the first electronic device.
  • the activation verification codes bound to different software value-added services may be the same or different.
  • the activation verification code bound to the software value-added service can be generated in advance by the server. Then, when different electronic devices purchase the software value-added service, the corresponding activation verification code is the same.
  • the activation verification code bound to the software value-added service may also be generated after the server binds the device identifier. At this time, the server may generate the activation verification code by using the identification identifier of the first electronic device. Then, when different electronic devices purchase the software value-added service, the corresponding activation verification codes may be the same or different. In this case, the activation verification code is also bound to the device identification of the first electronic device.
  • Step S52 After receiving the activation verification code input by the user, send an authorization request to the server, where the authorization request carries the activation verification code input by the user and the device identification of the first electronic device, so that after the server receives the authorization request, If the activation verification code and device identification carried in the authorization request match the server-side activation verification code and device identification code, the software value-added service is activated.
  • the user checks the activation verification code through the preset receiver, and enters the activation verification code into the first electronic device. Specifically, the user enters the activation verification code into the software that provides the software value-added service in the first electronic device. The user then triggers the software to generate and send an authorization request to request the server to activate the software value-added service.
  • the device identification of the first electronic device may be obtained automatically by software, or may be manually input by a user. If the device identification of the first electronic device is manually input by the user, after the user inputs the device identification of the first electronic device into the software, the software is triggered to generate and send an authorization request.
  • the authorization request carries information such as the activation card number, password, and verification code.
  • the authorization request carries the activation verification code and the device identification of the first electronic device.
  • the authorization request carries the identifier of the software value-added service to be activated.
  • the server can determine the activation verification code and device identifier that are bound to the software value-added service based on the software value-added service identifier. (Hereinafter referred to as the server-side activation verification code and device identification), the server compares the activation verification code and device identification carried in the authorization request with the server-side activation verification code and device identification. If they are the same, the authorization request is explained The activation verification code and device identification carried in the server match the activation verification code and device identification on the server side, and then the software value-added service is activated. Thereafter, the first electronic device user can use the software value-added service.
  • the authorization request may not carry the identifier of the software value-added service to be activated.
  • the server checks whether any software value-added service is bound to the activation verification code and device identification carried in the authorization request. If found, it indicates that the activation verification code and device identification carried in the authorization request are related to the server. If both the activation verification code and the device identification match, the software value-added service is activated. Thereafter, the first electronic device user can use the software value-added service.
  • the information processing method provided in this application also sends the device identification of the electronic device using the software value-added service to the server when purchasing the software value-added service.
  • the device identification of the electronic device using the software value-added service Binding with the software value-added service, so the activation verification code bound to the software value-added service can only be used for electronic devices bound to the software value-added service, avoiding the activation of the software value-added service on other electronic devices after the activation verification code is stolen, reducing Probability of software value-added services being stolen.
  • the first electronic device may further send a software value-added service review request to the server, where the software value-added service review request carries the device identifier of the first electronic device, and After the server receives the software value-added service viewing request, the server returns the software value-added service related information bound to the device identifier of the first electronic device to the receiver preset by the user.
  • the user After the user purchases the software value-added service, the user can view the related information of the software value-added service that he has purchased on the first electronic device.
  • the server After receiving the software value-added service viewing request, the server determines the bound software value-added service according to the device identification carried in the software value-added service viewing request, and then obtains the related information about the determined software value-added service.
  • the related information of the software value-added service may include: attribute information of the software value-added service, for example, the name or identification of the software value-added service, version, purchase time, use period, and so on.
  • the user does not need to activate the software value-added service (that is, does not need to enter an activation verification code) to view the software value-added service that has been purchased. Even if the user is required to input the device identification of the electronic device, compared with the prior art that requires the user to input multiple information (activation card number, password, verification code, etc.), the amount of information input by the user is also small, thus simplifying user operations.
  • an implementation manner in which the first electronic device sends a soft A value-added service purchase request to the server may be:
  • the identification of the software value-added service may be input by a user through a keyboard, or may be selected and input through a software value-added service list provided by the first electronic device.
  • the device identifier corresponding to the account currently used by the user is acquired according to the preset correspondence between the user account and the device identifier.
  • the first electronic device After the user inputs the identification of the software value-added service, the first electronic device is triggered to generate a purchase request sending instruction (the instruction carries the identification of the software value-added service input by the user) to instruct the first electronic device to send a purchase request.
  • a purchase request sending instruction the instruction carries the identification of the software value-added service input by the user
  • the device identification of the first electronic device is entered into the first electronic device according to the portal provided by the first electronic device, so that the first electronic device establishes a user account. Correspondence with device identification.
  • a software value-added service purchase request is generated, and the software value-added service purchase request encapsulates the acquired device identifier and the software value-added service identifier entered by the user.
  • the first electronic device automatically obtains the device identifier of the first electronic device and generates a purchase request according to the correspondence between the user account and the device identifier.
  • another implementation manner in which the first electronic device sends a software value-added service purchase request to the server may be:
  • the identification of the software value-added service may be input by a user through a keyboard, or may be selected and input through a software value-added service list provided by the first electronic device.
  • the device identifier of the electronic device is read through a preset interface. After the user inputs the identification of the software value-added service, the first electronic device is triggered to generate a purchase request sending instruction (the instruction carries the identification of the software value-added service input by the user) to instruct the first electronic device to send a purchase request.
  • the first electronic device itself provides an interface through which the first electronic device can read the device identification of the first electronic device.
  • a software value-added service purchase request is generated, and the software value-added service purchase request encapsulates the read device identifier and the software value-added service identifier input by the user.
  • the device identifier of the first electronic device is completely obtained by the first electronic device automatically, without any operation by the user, which simplifies user operations.
  • another implementation manner in which the first electronic device sends a software value-added service purchase request to the server may be:
  • a software value-added service purchase request is generated, and the software value-added service purchase request encapsulates a device identifier input by the user and an identifier of the software value-added service input by the user.
  • each time a software value-added service is purchased the user manually enters the device identification of the first electronic device.
  • FIG. 6 Another implementation flowchart of the information processing method provided by this embodiment of the present application may include:
  • Step S61 Receive a software value-added service purchase request, where the software value-added service purchase request carries a device identification of the first electronic device.
  • the software value-added service purchase request may be sent by the first electronic device, or may be sent by the second electronic device. That is, when the user of the first electronic device wants to use the software value-added service in the first electronic device, the software value-added service can be purchased through the first electronic device or the second electronic device.
  • the first electronic device may automatically obtain the device identification of the first electronic device, or the user may manually enter the device identification of the first electronic device.
  • the user may manually input the device identification of the first electronic device.
  • the software value-added service purchase request carries the identifier of the software value-added service to be purchased. Unlike the prior art, in the embodiment of the present application, the software value-added service purchase request carries the identifier of the software value-added service to be purchased. Carrying the device identification of the first electronic device.
  • Step S62 After the software value-added service is successfully purchased, the device identification of the first electronic device is bound to the software value-added service, and an activation verification code bound to the software value-added service is sent to a preset user.
  • the server after the software value-added service is successfully purchased, the server only returns the activation verification code to the user, and does not need to return the activation card number and password to the user.
  • the server binds the software value-added service with the device identification of the first electronic device.
  • a server can be an independent server or a server group consisting of two or more servers.
  • the user's preset receiver can be a short message receiver, such as a mobile phone number; it can also be a mail receiver, such as an email address; or, it can be another receiver that can receive information, such as the user's on the first electronic device.
  • the activation verification codes bound to different software value-added services may be the same or different.
  • the activation verification code bound to the software value-added service can be generated in advance by the server. Then, when different electronic devices purchase the software value-added service, the corresponding activation verification code is the same.
  • the activation verification code bound to the software value-added service may also be generated after the server binds the device identifier. At this time, the server may generate the activation verification code by using the identification identifier of the first electronic device. Then, when different electronic devices purchase the software value-added service, the corresponding activation verification codes may be the same or different. In this case, the activation verification code is also bound to the device identification of the first electronic device.
  • Step S63 After receiving the authorization request sent by the first electronic device and carrying the activation verification code and the device identification of the first electronic device, if the activation verification code and device identification carried in the authorization request and the server-side activation verification code Match both the device identification and activate the software value-added services mentioned above.
  • the user checks the activation verification code through the preset receiver, and enters the activation verification code into the first electronic device. Specifically, the user enters the activation verification code into the software that provides the software value-added service in the first electronic device. After that, the user triggers the software to generate and send an authorization request to request the server to activate the software value-added service.
  • the device identification of the first electronic device may be obtained automatically by software, or may be manually input by a user. If the device identification of the first electronic device is manually input by the user, after the user inputs the device identification of the first electronic device into the software, the software is triggered to generate and send an authorization request.
  • the authorization request carries information such as the activation card number, password, and verification code.
  • the authorization request carries the activation verification code and the device identification of the first electronic device.
  • the authorization request carries the identifier of the software value-added service to be activated.
  • the server can determine the activation verification code and device identifier that are bound to the software value-added service based on the software value-added service identifier. (Hereinafter referred to as the server-side activation verification code and device identification), the server compares the activation verification code and device identification carried in the authorization request with the server-side activation verification code and device identification. If they are the same, the authorization request is explained The activation verification code and device identification carried in the server match the activation verification code and device identification on the server side, and then the software value-added service is activated. Thereafter, the first electronic device user can use the software value-added service.
  • the authorization request may not carry the identifier of the software value-added service to be activated.
  • the server checks whether any software value-added service is bound to the activation verification code and device identification carried in the authorization request. If found, it indicates that the activation verification code and device identification carried in the authorization request are related to the server. If both the activation verification code and the device identification match, the software value-added service is activated. Thereafter, the first electronic device user can use the software value-added service.
  • the information processing method provided in this application also sends the device identification of the electronic device using the software value-added service to the server when purchasing the software value-added service.
  • the device identification of the electronic device using the software value-added service Binding with the software value-added service, so the activation verification code bound to the software value-added service can only be used for electronic devices bound to the software value-added service, avoiding the activation of the software value-added service on other electronic devices after the activation verification code is stolen, reducing Probability of software value-added services being stolen.
  • the information processing method provided in this application may further include:
  • the preset information of the software value-added service bound to the device identification carried in the software value-added service viewing request is returned to the user's preset receiver.
  • the user After the user purchases the software value-added service, the user can view the information about the software value-added service that he has purchased on the first electronic device or the second electronic device.
  • the server After receiving the software value-added service review request, the server determines the bound software value-added service according to the device identification carried in the software value-added service review request, and then obtains the related software value-added service information.
  • the related information of the software value-added service may include: attribute information of the software value-added service, for example, the name or identification of the software value-added service, version, purchase time, use period, and so on.
  • the user does not need to activate the software value-added service (that is, does not need to enter an activation verification code) to view the software value-added service that has been purchased. Even if the user is required to input the device identification of the electronic device, compared with the prior art that requires the user to input multiple information (activation card number, password, verification code, etc.), the amount of information input by the user is also small, thus simplifying user operations.
  • an implementation manner of the server receiving the software value-added service purchase request may be: receiving a software value-added service purchase request sent by the first electronic device;
  • the software value-added service purchase request is obtained by the first electronic device when the software value-added service identifier entered by the user is obtained.
  • a purchase request that carries the software value-added service identifier is sent, an instruction is sent according to a preset user account corresponding to the device identifier The relationship is generated after the device identifier corresponding to the account currently used by the user is obtained.
  • the software value-added service purchase request encapsulates the acquired device identifier and the software value-added service identifier.
  • the identification of the software value-added service may be input by a user through a keyboard, or may be selected and input through a software value-added service list provided by the first electronic device.
  • the first electronic device After the user inputs the identification of the software value-added service, the first electronic device is triggered to generate a purchase request sending instruction (the instruction carries the identification of the software value-added service input by the user) to instruct the first electronic device to send a purchase request.
  • a purchase request sending instruction the instruction carries the identification of the software value-added service input by the user
  • the device identification of the first electronic device is entered into the first electronic device according to the portal provided by the first electronic device, so that the first electronic device establishes a user account. Correspondence with device identification.
  • the first electronic device automatically obtains the device identifier of the first electronic device and generates a purchase request according to the correspondence between the user account and the device identifier.
  • another implementation manner for the server to receive the software value-added service purchase request may be: receiving a software value-added service purchase request sent by the first electronic device;
  • the first electronic device reads the device identifier of the first electronic device through a preset interface when it obtains the software value-added service identifier input by the user and obtains the purchase request that carries the software value-added service identifier.
  • the software value-added service purchase request encapsulates the read device identification and the above-mentioned software value-added service identification.
  • the identification of the software value-added service may be input by a user through a keyboard, or may be selected and input through a software value-added service list provided by the first electronic device.
  • the first electronic device After the user inputs the identification of the software value-added service, the first electronic device is triggered to generate a purchase request sending instruction (the instruction carries the identification of the software value-added service input by the user) to instruct the first electronic device to send a purchase request.
  • a purchase request sending instruction the instruction carries the identification of the software value-added service input by the user
  • the first electronic device itself provides an interface through which the first electronic device can read the device identification of the first electronic device.
  • the device identifier of the first electronic device is completely obtained by the first electronic device automatically, without any operation by the user, which simplifies user operations.
  • another implementation manner for the server to receive the software value-added service purchase request may be: receiving a software value-added service purchase request sent by the first electronic device or the second electronic device;
  • the first electronic device or the second electronic device obtains the identifier of the software value-added service input by the user, and the device identifier of the first electronic device.
  • the software value-added service purchase request is generated after receiving the purchase request sending instruction.
  • the device identification of the first electronic device and the identification of the software value-added service are encapsulated therein.
  • each time a software value-added service is purchased the user manually enters the device identification of the first electronic device.
  • the present application also provides an information processing system, which includes an electronic device and a server.
  • FIG. 7 it is a schematic structural diagram of an information processing system according to an embodiment of the present application.
  • the information processing system may include only the first electronic device, that is, only the electronic devices that need to use software value-added services; the information processing system may also include both the first electronic device and the second electronic device, where the first The electronic device is an electronic device that requires software value-added services.
  • the second electronic device is an electronic device that is different from the first electronic device.
  • the second electronic device may be an electronic device that requires software value-added services, or it may not require software value-added services. Electronic equipment for service.
  • the software value-added services used by the first electronic device and the second electronic device may be the same or different.
  • the first electronic device may be an aerial photography drone, a personal computer, a smart phone, a smart watch, a smart bracelet, a smart home and other hardware products
  • the second electronic device may be a personal computer, a smart phone, a tablet computer and other communication terminals. It can be seen that the first electronic device and the second electronic device may be the same type of electronic device.
  • the first electronic device or the second electronic device is configured to send a software value-added service purchase request to the server, where the software value-added service purchase request carries a device identifier of the first electronic device.
  • the server is configured to bind the device identification of the first electronic device with the software value-added service after the software value-added service is successfully purchased, and send an activation verification code corresponding to the purchased software value-added service to a user preset receiver.
  • the first electronic device is further configured to send an authorization request to the server after acquiring the activation verification code, where the authorization request carries the obtained activation verification code and the device identifier of the first electronic device.
  • the server is also used to activate the software value-added service if the activation verification code and device identification carried in the authorization request match the server-side activation verification code and device identification after receiving the authorization request.
  • the information processing system provided in this application also sends the device identification of the electronic device using the software value-added service to the server when purchasing the software value-added service.
  • the device identification of the electronic device using the software value-added service Binding with the software value-added service, so the activation verification code bound to the software value-added service can only be used for electronic devices bound to the software value-added service, avoiding the activation of the software value-added service on other electronic devices after the activation verification code is stolen, reducing Probability of software value-added services being stolen.
  • the first electronic device or the second electronic device is further configured to send a software value-added service viewing request to the server, where the software value-added service viewing request carries a device identification of the first electronic device;
  • the server is further configured to, after receiving the software value-added service viewing request, return to the receiver preset by the user information related to the software value-added service bound to the device identification of the first electronic device.
  • the first electronic device when the first electronic device sends a software value-added service purchase request to the server, it may be specifically used to:
  • the device identifier corresponding to the account currently used by the user is acquired according to the preset correspondence between the user account and the device identifier.
  • a software value-added service purchase request is generated, and the software value-added service purchase request encapsulates the acquired device identifier and the software value-added service identifier input by the user.
  • the first electronic device when the first electronic device sends a software value-added service purchase request to the server, it may be specifically used to:
  • the device identifier of the first electronic device is read through a preset interface
  • a software value-added service purchase request is generated, and the software value-added service purchase request encapsulates the read device identifier and the software value-added service identifier input by the user.
  • the first electronic device or the second electronic device when the first electronic device or the second electronic device sends a software value-added service purchase request to the server, it may be specifically used to:
  • the first electronic device or the second electronic device obtains the identifier of the software value-added service input by the user, and the device identifier of the first electronic device.
  • the first electronic device or the second electronic device When the first electronic device or the second electronic device receives the purchase request sending instruction, it generates a software value-added service purchase request.
  • the software value-added service purchase request encapsulates the device identifier input by the user and the software value-added service identifier input by the user. .
  • the first electronic device or the second electronic device sends the generated software value-added service purchase request to the server.
  • This application also provides an electronic device.
  • a schematic structural diagram of the electronic device provided in this application is shown in FIG. 8 and may include:
  • the first sending module 81 is configured to send a software value-added service purchase request to the server.
  • the software value-added service purchase request carries a device identifier of the electronic device, so that the server binds the device identifier to the software value-added service after the software value-added service purchase is successful. And send the activation verification code bound to the software value-added service to the receiver preset by the user.
  • the second sending module 82 is configured to send an authorization request to the server after receiving the activation verification code input by the user, where the authorization request carries the activation verification code and the device identifier, so that after the server receives the authorization request, if the authorization request.
  • the activation verification code and device identification carried in the server match the activation verification code and device identification code on the server side to activate the software value-added service.
  • the device identification of the electronic equipment using the software value-added services is also sent to the server. After the software value-added service is successfully purchased, the device identification of the electronic equipment using the software value-added services and The software value-added service is bound, so that the software value-added service-bound activation verification code can only be used for electronic devices bound to the software value-added service, which avoids the activation of the software value-added service on other electronic devices after the activation verification code is stolen, reducing the software The probability of misappropriation of value-added services.
  • the electronic device provided in this application may further include:
  • the third sending module is configured to send a software value-added service review request to the server, where the software value-added service review request carries the device identification of the first electronic device, so that the server presets to the user after receiving the software value-added service review request.
  • the receiver returns information about the software value-added service bound to the device identification of the first electronic device.
  • the first sending module 81 may be specifically configured to:
  • the device identifier corresponding to the account currently used by the user is acquired according to the preset correspondence between the user account and the device identifier.
  • the software value-added service purchase request encapsulates the acquired device identification and the software value-added service identification entered by the user.
  • the first sending module 81 may be specifically configured to:
  • the device identification of the electronic device is read through a preset interface.
  • a software value-added service purchase request is generated, and the software value-added service purchase request is packaged with a reading device identifier and a software value-added service identifier input by the user.
  • the first sending module 81 may be specifically configured to:
  • a software value-added service purchase request is generated, and the software value-added service purchase request encapsulates a device identifier input by the user and an identifier of the software value-added service input by the user.
  • the server sends the generated software value-added service purchase request.
  • This application also provides a server.
  • a schematic structural diagram of the server is shown in FIG. 9 and may include:
  • the first receiving module 91 is configured to receive a software value-added service purchase request, where the software value-added service purchase request carries a device identification of the first electronic device.
  • the fourth sending module 92 is configured to bind the device identification with the software value-added service after the software value-added service is successfully purchased, and send an activation verification code bound to the software value-added service to a receiver preset by the user.
  • the authorization module 93 is configured to, after receiving the authorization request carrying the activation verification code and the device identification sent by the first electronic device, if the activation verification code and the device identification carried in the authorization request are the same as those of the server-side activation verification code and device identification Match and activate software value-added services.
  • the server provided in this application includes a device identification of an electronic device using software value-added service in the received purchase request. After the software value-added service is successfully purchased, the device identification of the electronic device using the software value-added service is bound to the software value-added service Therefore, the activation verification code bound to the software value-added service can only be used for electronic equipment bound to the software value-added service, to avoid activating the software value-added service on other electronic devices after the activation verification code is stolen, reducing the probability of the software value-added service being stolen .
  • the server provided in this application may further include:
  • the third sending module is configured to send a software value-added service review request to the server.
  • the software value-added service review request carries a device identification, so that the server returns the preset value to the user after receiving the software value-added service review request.
  • the first receiving module 91 is specifically configured to receive a software value-added service purchase request sent by the first electronic device;
  • the software value-added service purchase request is obtained by the first electronic device when the software value-added service identifier entered by the user is obtained.
  • a purchase request that carries the software value-added service identifier is sent, an instruction is sent according to a preset correspondence between the user account and the device identifier. The relationship is generated after the device identifier corresponding to the account currently used by the user is obtained.
  • the software value-added service purchase request encapsulates the acquired device identifier and the software value-added service identifier.
  • the first receiving module 91 is specifically configured to receive a software value-added service purchase request sent by the first electronic device;
  • the first electronic device reads the device identifier of the first electronic device through a preset interface when it obtains the software value-added service identifier input by the user and obtains the purchase request that carries the software value-added service identifier.
  • the software value-added service purchase request encapsulates the read device identification and the above-mentioned software value-added service identification.
  • the first receiving module 91 is specifically configured to receive a software value-added service purchase request sent by the first electronic device or the second electronic device;
  • the first electronic device or the second electronic device obtains the identifier of the software value-added service input by the user, and the device identifier of the first electronic device.
  • the software value-added service purchase request is generated after receiving the purchase request sending instruction.
  • the device identification of the first electronic device and the identification of the software value-added service are encapsulated therein.

Abstract

本申请公开了一种信息处理方法、电子设备、服务器和信息处理系统,在购买软件增值服务时,将使用软件增值服务的电子设备的设备标识也发送给服务器(S21),软件增值服务购买成功后,将使用该软件增值服务的电子设备的设备标识与该软件增值服务绑定(S22),电子设备向服务器发送的授权请求中同时携带激活验证码和设备标识(S23),服务器接收到授权请求时,只有授权请求中携带的激活验证码和设备标识与本地的激活验证码和设备标识匹配才激活软件增值服务(S24),避免激活验证码被盗后在其它电子设备上激活软件增值服务,降低了软件增值服务被盗用的概率。

Description

信息处理方法、电子设备、服务器和信息处理系统 技术领域
本申请涉及信息处理技术领域,尤其涉及一种信息处理方法、电子设备、服务器和信息处理系统。
背景技术
随着电子设备(如,航拍无人机、个人电脑、智能手机、智能手表、智能家居等)智能化的发展,越来越多的电子设备供应商为电子设备提供软件增值服务。
用户在购买软件增值服务后,服务方将包含激活信息(通常包含激活卡号、密码及验证码等)的激活凭证发送给用户,用户在电子设备中输入激活信息之后,电子设备将激活信息发送给服务方认证,服务方在判断出激活信息为其下发的激活信息后,授权电子设备使用已购买的软件增值服务器。
然而,发明人研究发现,在实际应用中,用户购买的软件增值服务易出现被盗用的情况。因此,如何降低用户购买的软件增值服务被盗用的概率成为亟待解决的技术问题。
发明内容
本申请提供了一种信息处理方法、电子设备、服务器和信息处理系统,目的在于降低用户购买的软件服务被盗用的概率。
第一方面,本申请提供一种信息处理方法,包括:
第一电子设备或第二电子设备向服务器发送软件增值服务购买请求,所述软件增值服务购买请求中携带有所述第一电子设备的设备标识;
所述服务器在所述软件增值服务购买成功后,将所述设备标识与所述软件增值服务绑定,并向用户预置的接收方发送与所述软件增值服务绑定的激活验证码;
所述第一电子设备在接收用户输入的所述激活验证码后,向所述服务器发送授权请求,所述授权请求中携带有所述激活验证码和所述设备标识;
所述服务器在接收所述授权请求后,若所述授权请求中携带的激活验证码和设备标识,与所述服务器端的激活验证码和设备标识均匹配,激活所述软件增值服务。
第二方面,本申请提供一种数据处理方法,信息处理方法,应用于电子设备,包括:
向服务器发送软件增值服务购买请求,所述软件增值服务购买请求中携带有所述电子设备的设备标识,以使所述服务器在所述软件增值服务购买成功后,将所述设备标识与所述软件增值服务绑定,并向用户预置的接收方发送与所述软件增值服务绑定的激活验证码;
在接收用户输入的所述激活验证码后,向所述服务器发送授权请求,所述授权请求中携带有所述激活验证码和所述设备标识,以使所述服务器在接收到所述授权请求后,若所述授权请求中携带的激活验证码和设备标识,与所述服务器端的激活验证码和设备标识码均匹配,激活所述软件增值服务。
第三方面,本申请提供一种信息处理方法,应用于服务器,包括:
接收软件增值服务购买请求,所述软件增值服务购买请求中携带有第一电子设备的设备标识;
在所述软件增值服务购买成功后,将所述设备标识与所述软件增值服务绑定,并向用户预置的接收方发送与所述软件增值服务绑定的激活验证码;
在接收到所述第一电子设备发送的携带有所述激活验证码和所述设备标识的授权请求后,若所述授权请求中携带的激活验证码及设备标识,与所述服务器端的激活验证码和设备标识均匹配,激活所述软件增值服务。
第四方面,本申请提供一种信息处理系统,包括:电子设备和服务器;所述电子设备包括第一电子设备,或者,所述电子设备包括第一电子设备和第二电子设备;
所述第一电子设备或所述第二电子设备用于向所述服务器发送软件增值服务购买请求,所述软件增值服务购买请求中携带有所述第一电子设备的设备标识;
所述服务器用于在所述软件增值服务购买成功后,将所述设备标识与所述软件增值服务绑定,并向用户预置的接收方发送与所述软件增值服务对应的激活验证码;
所述第一电子设备还用于在获取所述激活验证码后,向所述服务器发送授权请求,所述授权请求中携带有所述激活验证码和所述设备标识;
所述服务器还用于在接收所述授权请求后,若所述授权请求中携带的激活验证码和设备标识,与所述服务器端的激活验证码和设备标识均匹配,激活所述软件增值服务。
第五方面,本申请提供一种电子设备,包括:
第一发送模块,用于向服务器发送软件增值服务购买请求,所述软件增值服务购买请求中携带有所述电子设备的设备标识,以使所述服务器在所述软件增值服务购买成功后,将所述设备标识与所述软件增值服务绑定,并向用户预置的接收方发送与所述软件增值服务绑定的激活验证码;
第二发送模块,用于在接收用户输入的所述激活验证码后,向所述服务器发送授权请求,所述授权请求中携带有所述激活验证码和所述设备标识,以使所述服务器在接收到所述授权请求后,若所述授权请求中携带的激活验证码和设备标识,与所述服务器端的激活验证码和设备标识码均匹配,激活所述软件增值服务。
第六方面,本申请提供一种服务器,包括:
第一接收模块,用于接收软件增值服务购买请求,所述软件增值服务购买请求中携带有第一电子设备的设备标识;
第四发送模块,用于在所述软件增值服务购买成功后,将所述设备标识与所述软件增值服务绑定,并向用户预置的接收方发送与所述软件增值服务绑定的激活验证码;
授权模块,用于在接收到所述第一电子设备发送的携带有所述激活验证码和所述设备标识的授权请求后,若所述授权请求中携带的激活验证码及设备标识,与所述服务器端的激活验证码和设备标识均匹配,激活所述软件增值服务。
由上述方案可知,本申请实施例提供的一种信息处理方法、电子设备、 服务器和信息处理系统,在用户购买软件增值服务后,将用户购买的软件增值服务与用户使用的终端设备的设备标识绑定,当需要激活软件增值服务时,用户在电子设备输入激活验证码后,电子设备向服务器发送的授权请求中除了携带激活验证码,还包括终端设备的设备标识,使得服务器在接收到授权请求后,根据设备标识及激活验证码对用户进行校验,只有在授权请求中携带的激活验证码和设备标识,与服务器端的根据软件增值服务的标识确定的,软件增值服务绑定的激活验证码和设备标识均匹配时,才授权电子设备使上述软件增值服务,否则不授权终端设备使用软件增值服务,从而避免激活验证码被盗取后在其它电子设备上激活上述软件增值服务,降低了软件增值服务被盗用的概率。
附图说明
为了更清楚地说明本申请实施例或现有技术中的技术方案,下面将对实施例或现有技术描述中所需要使用的附图作简单地介绍,显而易见地,下面描述中的附图仅仅是本申请的一些实施例,对于本领域普通技术人员来讲,在不付出创造性劳动的前提下,还可以根据这些附图获得其他的附图。
图1为本发明实施例提供的信息处理方法的原理图;
图2为本发明实施例提供的信息处理方法的一种实现流程图;
图3为本发明实施例提供的第一电子设备向服务器发送软件增值服务购买请求的一种实现流程图;
图4为本发明实施例提供的第一电子设备向服务器发送软件增值服务购买请求的另一种实现流程图;
图5为本发明实施例提供的信息处理方法的另一种实现流程图;
图6为本发明实施例提供的信息处理方法的又一种实现流程图;
图7为本发明实施例提供的信息处理系统的一种结构示意图;
图8为本发明实施例提供的电子设备的一种结构示意图;
图9为本发明实施例提供的服务器的一种结构示意图。
具体实施方式
本说明书中各个实施例采用递进的方式描述,每个实施例重点说明的都是与其它实施例的不同之处,各个实施例之间相同或相似部分互相参见即可。
请参阅图1,图1为本申请实施例提供的信息处理方法的原理图。本申请实施例中,用户通过第一电子设备或第二电子设备向服务器发送软件增值服务购买请求,该软件增值服务购买请求中携带有第一电子设备的设备标识。服务器在上述购买成功后,将第一电子设备的设备标识与软件增值服务绑定,并向用户返回与软件增值服务绑定的激活验证码。用户将激活验证码输入第一电子设备,由第一电子设备向服务器发送授权请求,该授权请求中携带有软件增值服务的标识,用户输入的激活验证码,以及第一电子设备的设备标识。服务器在接收到第一电子设备发送的授权请求后,若授权请求中携带的激活验证码和设备标识,与服务器端的激活验证码和设备标识均匹配,激活软件增值服务,否则不激活软件增值服务。由于第一电子设备的识别标识第一电子设备独有的,因此,即便激活验证码被盗,由于使用被盗激活验证码的电子设备的设备标识与第一电子设备的设备标识不同,因此软件增值服务不能被激活,从而避免激活验证码被盗取后在其它电子设备上激活上述软件增值服务,降低了软件增值服务被盗用的概率。
请参阅图2,图2为本申请实施例提供的信息处理方法的一种实现流程图,可以包括:
步骤S21:第一电子设备或第二电子设备向服务器发送软件增值服务购买请求,该软件增值服务购买请求中携带有第一电子设备的设备标识。
当第一电子设备的用户想要在第一电子设备中使用软件增值服务时,可以通过第一电子设备购买该软件增值服务,或者,通过第二电子设备购买该软件增值服务。
当通过第一电子设备购买软件增值服务时,第一电子设备可以自动获取第一电子设备的设备标识,也可以由用户手动输入第一电子设备的设备 标识。
当通过第二电子设备购买软件增值服务时,可以由用户手动输入第一电子设备的设备标识。
通常,软件增值服务购买请求中会携带所要购买的软件增值服务的标识,与现有技术不同,本申请实施例中,软件增值服务购买请求中除了携带所要购买的软件增值服务的标识外,还携带第一电子设备的设备标识。
步骤S22:服务器在软件增值服务购买成功后,将第一电子设备的设备标识与软件增值服务绑定,并向用户预置的接收方发送与软件增值服务绑定的激活验证码。
软件增值服务如何购买成功可以参看现有技术中成熟的实现方式,这里不再详述。
本申请实施例中,在软件增值服务购买成功后,服务器只向用户返回激活验证码,而不需要向用户返回激活卡号和密码。此外,服务器还将软件增值服务与第一电子设备的设备标识绑定。
服务器可以是一个独立的服务器,也可以由两个或多个服务器组成的服务器群组。
用户预置的接收方可以是短信接收方,如手机号;也可以是邮件接收方,如电子邮箱;或者,可以是其它可以接收信息的接收方,例如,可以是用户在第一电子设备的提供商提供的网站内注册的帐号。
其中,不同的软件增值服务绑定的激活验证码可以相同,也可以不同。
软件增值服务绑定的激活验证码可以是服务器预先生成的,那么,不同的电子设备购买该软件增值服务时,对应的激活验证码是一样的。
软件增值服务绑定的激活验证码也可以是服务器绑定设备标识后才生成的,此时,服务器可以利用第一电子设备的识别标识生成激活验证码。那么,不同的电子设备购买该软件增值服务时,对应的激活验证码可以是相同的,也可以是不同的。此种情况下,激活验证码与第一电子设备的设备标识也是绑定的。
步骤S23:第一电子设备在接收用户输入的激活验证码后,向服务器发送授权请求,该授权请求中携带有用户输入的激活验证码和第一电子设 备的设备标识。
用户通过上述预置的接收方查看激活验证码,并将激活验证码输入第一电子设备,具体的,用户将激活验证码输入第一电子设备内的提供上述软件增值服务的软件。之后,用户触发该软件生成并发送授权请求,以请求服务器将软件增值服务激活。
其中,第一电子设备的设备标识可以由软件自动获取,或者,可以由用户手动输入。若第一电子设备的设备标识由用户手动输入,则用户在将第一电子设备的设备标识输入软件后,触发软件生成并发送授权请求。
与现有技术中的授权请求中携带激活卡号、密码及验证码等信息不同,本申请实施例中,授权请求中携带的是激活验证码和第一电子设备的设备标识。
步骤S24:服务器在接收授权请求后,若授权请求中携带的激活验证码和设备标识,与服务器端的激活验证码和设备标识均匹配,激活软件增值服务。
通常,授权请求中会携带所要激活的软件增值服务的标识,服务器在接收到授权请求后,根据软件增值服务的标识,可以确定服务器端存储的与软件增值服务绑定的激活验证码和设备标识(以下简称服务器端的激活验证码和设备标识),服务器将授权请求中携带的激活验证码和设备标识,与服务器端的激活验证码和设备标识均进行比对,若二者均相同,说明授权请求中携带的激活验证码和设备标识,与服务器端的激活验证码和设备标识均匹配,则激活软件增值服务,此后第一电子设备用户可以使用软件增值服务。
在一可选的实施例中,授权请求中可以不携带所要激活的软件增值服务的标识。则服务器在接收到授权请求后,查找是否有软件增值服务绑定了授权请求中携带的激活验证码和设备标识,若查找到,则说明授权请求中携带的激活验证码和设备标识,与服务器端的激活验证码和设备标识均匹配,则激活软件增值服务,此后第一电子设备用户可以使用软件增值服务。
本申请提供的信息处理方法,在购买软件增值服务时,将使用软件增 值服务的电子设备的设备标识也发送给服务器,软件增值服务购买成功后,将使用该软件增值服务的电子设备的设备标识与该软件增值服务绑定,从而软件增值服务绑定的激活验证码只能用于软件增值服务绑定的电子设备,避免激活验证码被盗后在其它电子设备上激活软件增值服务,降低了软件增值服务被盗用的概率。
发明人发现,现有技术中,用户在购买软件增值服务后,必须在激活软件增值服务后,才能查看其已购买的软件增值服务,给用户带来不便,为解决该问题,在一可选的实施例中,在软件增值服务购买成功后,本申请提供的信息处理方法还可以包括:
第一电子设备或第二电子设备向服务器发送软件增值服务查看请求,该软件增值服务查看请求中携带有第一电子设备的设备标识。
用户在购买软件增值服务后,可以在第一电子设备或第二电子设备查看其已经购买的软件增值服务的相关信息。
服务器在接收到软件增值服务查看请求后,向用户预置的接收方返回与第一电子设备的设备标识绑定的软件增值服务的相关信息。
服务器在接收到软件增值服务查看请求后,根据软件增值服务查看请求中携带的设备标识确定所绑定的软件增值服务,然后获取所确定的软件增值服务的相关信息。
软件增值服务的相关信息可以包括:软件增值服务的属性信息,例如,软件增值服务的名称或标识,版本,购买时间,使用期限等等。
本申请提供的信息处理方法,在软件增值服务购买成功后,用户无需激活软件增值服务(即不需要输入激活验证码)即可查看已经购买的软件增值服务。即便需要用户输入电子设备的设备标识,与现有技术中需要用户输入多个信息(激活卡号、密码及验证码等)相比,用户输入的信息量也很少,因此,简化了用户操作。
在一可选的实施例中,第一电子设备向服务器发送软件增值服务购买请求的一种实现流程图如图3所示,可以包括:
步骤S31:第一电子设备获取用户输入的软件增值服务的标识。该软件增值服务的标识可以由用户通过键盘输入,也可以通过第一电子设备提供的软件增值服务列表选择输入。
步骤S32:第一电子设备获取到携带软件增值服务的标识的购买请求发送指令时,根据预置的用户账户与设备标识的对应关系,获取与用户当前使用的账户对应的设备标识。
用户输入软件增值服务的标识后,触发第一电子设备生成购买请求发送指令(该指令中携带有用户输入的软件增值服务的标识),以指示第一电子设备发送购买请求。
用户在购买第一电子设备后,可以在首次使用该第一电子设备时,根据第一电子设备提供的入口将第一电子设备的设备标识输入第一电子设备,以便第一电子设备建立用户账户与设备标识的对应关系。
步骤S33:第一电子设备生成软件增值服务购买请求,该软件增值服务购买请求中封装有设备标识,以及软件增值服务的标识。
步骤S34:第一电子设备向服务器发送软件增值服务购买请求。
本申请实施例中,第一电子设备根据用户账户与设备标识的对应关系自动获取第一电子设备的设备标识并生成购买请求。
在另一可选的实施例中,第一电子设备向服务器发送软件增值服务购买请求的另一种实现流程图如图4所示,可以包括:
步骤S41:第一电子设备获取用户输入的软件增值服务的标识。该软件增值服务的标识可以由用户通过键盘输入,也可以通过第一电子设备提供的软件增值服务列表选择输入。
步骤S42:第一电子设备获取到携带软件增值服务的标识的购买请求发送指令时,通过预置接口读取第一电子设备的设备标识。
用户输入软件增值服务的标识后,触发第一电子设备生成购买请求发送指令(该指令中携带有用户输入的软件增值服务的标识),以指示第一电子设备发送购买请求。
与图3所示实施例不同,本实施例中,第一电子设备自身提供一个接 口,通过该接口第一电子设备可以读取第一电子设备的设备标识。
步骤S43:第一电子设备生成软件增值服务购买请求,该软件增值服务购买请求中封装有第一电子设备的设备标识,以及上述软件增值服务的标识。
步骤S44:第一电子设备向服务器发送软件增值服务购买请求。
与图3所示实施例不同,本实施例完全由第一电子设备自动获取第一电子设备的设备标识,而不需要用户任何操作,简化了用户操作。
在另一可选的实施例中,第一电子设备或第二电子设备向服务器发送软件增值服务购买请求的一种实现方式可以为:
第一电子设备或第二电子设备获取用户输入的软件增值服务的标识,以及第一电子设备的设备标识。
第一电子设备或第二电子设备获取到购买请求发送指令时,生成软件增值服务购买请求,该软件增值服务购买请求中封装有用户输入的设备标识,以及用户输入的软件增值服务的标识。
第一电子设备或第二电子设备向服务器发送软件增值服务购买请求。
与图3和图4所示实施例不同,本实施例中,每次购买软件增值服务时,均由用户手动输入第一电子设备的设备标识。
下面从使用软件增值服务的电子设备(为便于叙述,记为第一电子设备)的角度说明本申请实施例提供的信息处理方法的实现方式。如图5所示,为本申请实施例提供的信息处理方法的另一种实现流程图,可以包括:
步骤S51:向服务器发送软件增值服务购买请求,该软件增值服务购买请求中携带有第一电子设备的设备标识,以使服务器在软件增值服务购买成功后,将第一电子设备的设备标识与软件增值服务绑定,并向用户预置的接收方发送与软件增值服务绑定的激活验证码。
当第一电子设备的用户想要在第一电子设备中使用软件增值服务时,可以通过第一电子设备或第二电子设备购买该软件增值服务。
第一电子设备可以自动获取第一电子设备的设备标识,也可以由用户 手动输入第一电子设备的设备标识。
通常,软件增值服务购买请求中会携带所要购买的软件增值服务的标识,与现有技术不同,本申请实施例中,软件增值服务购买请求中除了携带所要购买的软件增值服务的标识外,还携带第一电子设备的设备标识。
软件增值服务如何购买成功可以参看现有技术中成熟的实现方式,这里不再详述。
在软件增值服务购买成功后,服务器只向用户返回激活验证码,而不需要向用户返回激活卡号和密码。此外,服务器还将软件增值服务与第一电子设备的设备标识绑定。
服务器可以是一个独立的服务器,也可以由两个或多个服务器组成的服务器群组。
用户预置的接收方可以是短信接收方,如手机号;也可以是邮件接收方,如电子邮箱;或者,可以是其它可以接收信息的接收方,例如,可以是用户在第一电子设备的提供商提供的网站内注册的帐号。
其中,不同的软件增值服务绑定的激活验证码可以相同,也可以不同。
软件增值服务绑定的激活验证码可以是服务器预先生成的,那么,不同的电子设备购买该软件增值服务时,对应的激活验证码是一样的。
软件增值服务绑定的激活验证码也可以是服务器绑定设备标识后才生成的,此时,服务器可以利用第一电子设备的识别标识生成激活验证码。那么,不同的电子设备购买该软件增值服务时,对应的激活验证码可以是相同的,也可以是不同的。此种情况下,激活验证码与第一电子设备的设备标识也是绑定的。
步骤S52:在接收用户输入的激活验证码后,向服务器发送授权请求,该授权请求中携带有用户输入的激活验证码和第一电子设备的设备标识,以使服务器在接收到授权请求后,若授权请求中携带的激活验证码和设备标识,与服务器端的激活验证码和设备标识码均匹配,激活软件增值服务。
用户通过上述预置的接收方查看激活验证码,并将激活验证码输入第一电子设备,具体的,用户将激活验证码输入第一电子设备内的提供上述软件增值服务的软件。之后,用户触发该软件生成并发送授权请求,以请 求服务器将软件增值服务激活。
其中,第一电子设备的设备标识可以由软件自动获取,或者,可以由用户手动输入。若第一电子设备的设备标识由用户手动输入,则用户在将第一电子设备的设备标识输入软件后,触发软件生成并发送授权请求。
与现有技术中的授权请求中携带激活卡号、密码及验证码等信息不同,本申请实施例中,授权请求中携带的是激活验证码和第一电子设备的设备标识。
通常,授权请求中会携带所要激活的软件增值服务的标识,服务器在接收到授权请求后,根据软件增值服务的标识,可以确定服务器端存储的与软件增值服务绑定的激活验证码和设备标识(以下简称服务器端的激活验证码和设备标识),服务器将授权请求中携带的激活验证码和设备标识,与服务器端的激活验证码和设备标识均进行比对,若二者均相同,说明授权请求中携带的激活验证码和设备标识,与服务器端的激活验证码和设备标识均匹配,则激活软件增值服务,此后第一电子设备用户可以使用软件增值服务。
在一可选的实施例中,授权请求中可以不携带所要激活的软件增值服务的标识。则服务器在接收到授权请求后,查找是否有软件增值服务绑定了授权请求中携带的激活验证码和设备标识,若查找到,则说明授权请求中携带的激活验证码和设备标识,与服务器端的激活验证码和设备标识均匹配,则激活软件增值服务,此后第一电子设备用户可以使用软件增值服务。
本申请提供的信息处理方法,在购买软件增值服务时,将使用软件增值服务的电子设备的设备标识也发送给服务器,软件增值服务购买成功后,将使用该软件增值服务的电子设备的设备标识与该软件增值服务绑定,从而软件增值服务绑定的激活验证码只能用于软件增值服务绑定的电子设备,避免激活验证码被盗后在其它电子设备上激活软件增值服务,降低了软件增值服务被盗用的概率。
在一可选的实施例中,在软件增值服务购买成功后,第一电子设备还 可以向服务器发送软件增值服务查看请求,该软件增值服务查看请求中携带有第一电子设备的设备标识,以使服务器在接收到软件增值服务查看请求后,向用户预置的接收方返回与第一电子设备的设备标识绑定的软件增值服务的相关信息。
用户在购买软件增值服务后,可以在第一电子设备查看其已经购买的软件增值服务的相关信息。
服务器在接收到软件增值服务查看请求后,根据软件增值服务查看请求中携带的设备标识确定所绑定的软件增值服务,然后获取所确定的软件增值服务的相关信息。
软件增值服务的相关信息可以包括:软件增值服务的属性信息,例如,软件增值服务的名称或标识,版本,购买时间,使用期限等等。
本申请提供的信息处理方法,在软件增值服务购买成功后,用户无需激活软件增值服务(即不需要输入激活验证码)即可查看已经购买的软件增值服务。即便需要用户输入电子设备的设备标识,与现有技术中需要用户输入多个信息(激活卡号、密码及验证码等)相比,用户输入的信息量也很少,因此,简化了用户操作。
在一可选的实施例中,第一电子设备向服务器发送软甲增值服务购买请求的一种实现方式可以为:
获取用户输入的软件增值服务的标识。该软件增值服务的标识可以由用户通过键盘输入,也可以通过第一电子设备提供的软件增值服务列表选择输入。
当获取到携带软件增值服务的标识的购买请求发送指令时,根据预置的用户账户与设备标识的对应关系,获取与用户当前使用的账户对应的设备标识。
用户输入软件增值服务的标识后,触发第一电子设备生成购买请求发送指令(该指令中携带有用户输入的软件增值服务的标识),以指示第一电子设备发送购买请求。
用户在购买第一电子设备后,可以在首次使用该第一电子设备时,根 据第一电子设备提供的入口将第一电子设备的设备标识输入第一电子设备,以便第一电子设备建立用户账户与设备标识的对应关系。
生成软件增值服务购买请求,该软件增值服务购买请求中封装有获取的设备标识,以及用户输入的软件增值服务的标识。
向服务器发送软件增值服务购买请求。
本申请实施例中,第一电子设备根据用户账户与设备标识的对应关系自动获取第一电子设备的设备标识并生成购买请求。
在一可选的实施例中,第一电子设备向服务器发送软件增值服务购买请求的另一种实现方式可以为:
获取用户输入的软件增值服务的标识。该软件增值服务的标识可以由用户通过键盘输入,也可以通过第一电子设备提供的软件增值服务列表选择输入。
当接获取到携带有上述用户输入的软件增值服务的标识的购买请求发送指令时,通过预置接口读取电子设备的设备标识。用户输入软件增值服务的标识后,触发第一电子设备生成购买请求发送指令(该指令中携带有用户输入的软件增值服务的标识),以指示第一电子设备发送购买请求。
与前一实施例不同,本实施例中,第一电子设备自身提供一个接口,通过该接口第一电子设备可以读取第一电子设备的设备标识。
生成软件增值服务购买请求,该软件增值服务购买请求中封装有读取的设备标识,以及上述用户输入的软件增值服务的标识。
向服务器发送所生成的软件增值服务购买请求。
与前一实施例不同,本实施例完全由第一电子设备自动获取第一电子设备的设备标识,而不需要用户任何操作,简化了用户操作。
在一可选的实施例中,第一电子设备向服务器发送软件增值服务购买请求的又一种实现方式可以为:
获取用户输入的软件增值服务的标识,以及第一电子设备的设备标识;
当获取到购买请求发送指令时,生成软件增值服务购买请求,该软件 增值服务购买请求中封装有上述用户输入的设备标识,以及上述用户输入的软件增值服务的标识。
向服务器发送所生成的软件增值服务购买请求。
与前两个实施例不同,本实施例中,每次购买软件增值服务时,均由用户手动输入第一电子设备的设备标识。
下面从服务器的角度说明本申请实施例提供的信息处理方法的实现方式。如图6所示,为本申请实施例提供的信息处理方法的又一种实现流程图,可以包括:
步骤S61:接收软件增值服务购买请求,该软件增值服务购买请求中携带有第一电子设备的设备标识。
软件增值服务购买请求可以由第一电子设备发送,也可以由第二电子设备发送。也就是说,当第一电子设备的用户想要在第一电子设备中使用软件增值服务时,可以通过第一电子设备或第二电子设备购买该软件增值服务。
当通过第一电子设备购买软件增值服务时,第一电子设备可以自动获取第一电子设备的设备标识,也可以由用户手动输入第一电子设备的设备标识。
当通过第二电子设备购买软件增值服务时,可以由用户手动输入第一电子设备的设备标识。
通常,软件增值服务购买请求中会携带所要购买的软件增值服务的标识,与现有技术不同,本申请实施例中,软件增值服务购买请求中除了携带所要购买的软件增值服务的标识外,还携带第一电子设备的设备标识。
步骤S62:在上述软件增值服务购买成功后,将第一电子设备的设备标识与软件增值服务绑定,并向用户预置的接收方发送与上述软件增值服务绑定的激活验证码。
软件增值服务如何购买成功可以参看现有技术中成熟的实现方式,这里不再详述。
本申请实施例中,在软件增值服务购买成功后,服务器只向用户返回 激活验证码,而不需要向用户返回激活卡号和密码。此外,服务器还将软件增值服务与第一电子设备的设备标识绑定。
服务器可以是一个独立的服务器,也可以由两个或多个服务器组成的服务器群组。
用户预置的接收方可以是短信接收方,如手机号;也可以是邮件接收方,如电子邮箱;或者,可以是其它可以接收信息的接收方,例如,可以是用户在第一电子设备的提供商提供的网站内注册的帐号。
其中,不同的软件增值服务绑定的激活验证码可以相同,也可以不同。
软件增值服务绑定的激活验证码可以是服务器预先生成的,那么,不同的电子设备购买该软件增值服务时,对应的激活验证码是一样的。
软件增值服务绑定的激活验证码也可以是服务器绑定设备标识后才生成的,此时,服务器可以利用第一电子设备的识别标识生成激活验证码。那么,不同的电子设备购买该软件增值服务时,对应的激活验证码可以是相同的,也可以是不同的。此种情况下,激活验证码与第一电子设备的设备标识也是绑定的。
步骤S63:在接收到第一电子设备发送的携带有上述激活验证码和第一电子设备的设备标识的授权请求后,若授权请求中携带的激活验证码及设备标识,与服务器端的激活验证码和设备标识均匹配,激活上述软件增值服务。
用户通过上述预置的接收方查看激活验证码,并将激活验证码输入第一电子设备,具体的,用户将激活验证码输入第一电子设备内的提供上述软件增值服务的软件。之后,用户触发该软件生成并发送授权请求,以请求服务器将软件增值服务激活。
其中,第一电子设备的设备标识可以由软件自动获取,或者,可以由用户手动输入。若第一电子设备的设备标识由用户手动输入,则用户在将第一电子设备的设备标识输入软件后,触发软件生成并发送授权请求。
与现有技术中的授权请求中携带激活卡号、密码及验证码等信息不同,本申请实施例中,授权请求中携带的是激活验证码和第一电子设备的设备标识。
通常,授权请求中会携带所要激活的软件增值服务的标识,服务器在接收到授权请求后,根据软件增值服务的标识,可以确定服务器端存储的与软件增值服务绑定的激活验证码和设备标识(以下简称服务器端的激活验证码和设备标识),服务器将授权请求中携带的激活验证码和设备标识,与服务器端的激活验证码和设备标识均进行比对,若二者均相同,说明授权请求中携带的激活验证码和设备标识,与服务器端的激活验证码和设备标识均匹配,则激活软件增值服务,此后第一电子设备用户可以使用软件增值服务。
在一可选的实施例中,授权请求中可以不携带所要激活的软件增值服务的标识。则服务器在接收到授权请求后,查找是否有软件增值服务绑定了授权请求中携带的激活验证码和设备标识,若查找到,则说明授权请求中携带的激活验证码和设备标识,与服务器端的激活验证码和设备标识均匹配,则激活软件增值服务,此后第一电子设备用户可以使用软件增值服务。
本申请提供的信息处理方法,在购买软件增值服务时,将使用软件增值服务的电子设备的设备标识也发送给服务器,软件增值服务购买成功后,将使用该软件增值服务的电子设备的设备标识与该软件增值服务绑定,从而软件增值服务绑定的激活验证码只能用于软件增值服务绑定的电子设备,避免激活验证码被盗后在其它电子设备上激活软件增值服务,降低了软件增值服务被盗用的概率。
在一可选的实施例中,本申请提供的信息处理方法还可以包括:
在接收到第一电子设备或第二电子设备发送的软件增值服务查看请求后,向用户预置的接收方返回与软件增值服务查看请求中携带的设备标识绑定的软件增值服务的相关信息。
本申请实施例中,
用户在购买软件增值服务后,可以在第一电子设备或第二电子设备查看其已经购买的软件增值服务的相关信息。
服务器在接收到软件增值服务查看请求后,根据软件增值服务查看请 求中携带的设备标识确定所绑定的软件增值服务,然后获取所确定的软件增值服务的相关信息。
软件增值服务的相关信息可以包括:软件增值服务的属性信息,例如,软件增值服务的名称或标识,版本,购买时间,使用期限等等。
本申请提供的信息处理方法,在软件增值服务购买成功后,用户无需激活软件增值服务(即不需要输入激活验证码)即可查看已经购买的软件增值服务。即便需要用户输入电子设备的设备标识,与现有技术中需要用户输入多个信息(激活卡号、密码及验证码等)相比,用户输入的信息量也很少,因此,简化了用户操作。
在一可选的实施例中,服务器接收软件增值服务购买请求的一种实现方式可以为:接收第一电子设备发送的软件增值服务购买请求;
该软件增值服务购买请求由第一电子设备在获取用户输入的软件增值服务的标识,当获取到携带上述软件增值服务的标识的购买请求发送指令时,根据预置的用户账户与设备标识的对应关系,获取与用户当前使用的账户对应的设备标识后生成,该软件增值服务购买请求中封装有所获取的设备标识,以及软件增值服务的标识。
软件增值服务的标识可以由用户通过键盘输入,也可以通过第一电子设备提供的软件增值服务列表选择输入。
用户输入软件增值服务的标识后,触发第一电子设备生成购买请求发送指令(该指令中携带有用户输入的软件增值服务的标识),以指示第一电子设备发送购买请求。
用户在购买第一电子设备后,可以在首次使用该第一电子设备时,根据第一电子设备提供的入口将第一电子设备的设备标识输入第一电子设备,以便第一电子设备建立用户账户与设备标识的对应关系。
本申请实施例中,第一电子设备根据用户账户与设备标识的对应关系自动获取第一电子设备的设备标识并生成购买请求。
在一可选的实施例中,服务器接收软件增值服务购买请求的另一种实 现方式可以为:接收第一电子设备发送的软件增值服务购买请求;
该软件增值服务购买请求由第一电子设备在获取用户输入的软件增值服务的标识,获取到携带软件增值服务的标识的购买请求发送指令时,通过预置接口读取第一电子设备的设备标识后生成,该软件增值服务购买请求中封装有所读取的设备标识,以及上述软件增值服务的标识。
软件增值服务的标识可以由用户通过键盘输入,也可以通过第一电子设备提供的软件增值服务列表选择输入。
用户输入软件增值服务的标识后,触发第一电子设备生成购买请求发送指令(该指令中携带有用户输入的软件增值服务的标识),以指示第一电子设备发送购买请求。
与前一实施例不同,本实施例中,第一电子设备自身提供一个接口,通过该接口第一电子设备可以读取第一电子设备的设备标识。
与前一实施例不同,本实施例完全由第一电子设备自动获取第一电子设备的设备标识,而不需要用户任何操作,简化了用户操作。
在一可选的实施例中,服务器接收软件增值服务购买请求的又一种实现方式可以为:接收第一电子设备或第二电子设备发送的软件增值服务购买请求;
该软件增值服务购买请求由第一电子设备或第二电子设备获取用户输入的软件增值服务的标识,以及第一电子设备的设备标识;接收到购买请求发送指令后生成,该软件增值服务购买请求中封装有第一电子设备的设备标识,以及上述软件增值服务的标识。
与前两个实施例不同,本实施例中,每次购买软件增值服务时,均由用户手动输入第一电子设备的设备标识。
与方法实施例相对应,本申请还提供一种信息处理系统,该信息处理系统包括电子设备和服务器,如图7所示,为本申请实施例提供的信息处理系统的一种结构示意图,该信息处理系统中,可以仅包括第一电子设备,即仅包括需要使用软件增值服务的电子设备;该信息处理系统中,也可以 既包括第一电子设备,又包括第二电子设备,其中第一电子设备是需要使用软件增值服务的电子设备,第二电子设备是与第一电子设备不同的电子设备,第二电子设备可以是需要使用软件增值服务的电子设备,也可以是不需要使用软件增值服务的电子设备。第一电子设备和第二电子设备使用的软件增值服务可以相同,也可以不同。
第一电子设备可以是航拍无人机,个人电脑、智能手机、智能手表、智能手环、智能家居等硬件产品,第二电子设备可以是个人电脑,智能手机、平板电脑等通讯终端。可以看出,第一电子设备和第二电子设备可以是相同类型的电子设备。
第一电子设备或第二电子设备用于向服务器发送软件增值服务购买请求,该软件增值服务购买请求中携带有第一电子设备的设备标识。
服务器用于在软件增值服务购买成功后,将第一电子设备的设备标识与软件增值服务绑定,并向用户预置的接收方发送与购买的软件增值服务对应的激活验证码。
第一电子设备还用于在获取所述激活验证码后,向服务器发送授权请求,该授权请求中携带有获取的激活验证码和第一电子设备的设备标识。
服务器还用于在接收到授权请求后,若授权请求中携带的激活验证码和设备标识,与服务器端的激活验证码和设备标识均匹配,激活软件增值服务。
本申请提供的信息处理系统,在购买软件增值服务时,将使用软件增值服务的电子设备的设备标识也发送给服务器,软件增值服务购买成功后,将使用该软件增值服务的电子设备的设备标识与该软件增值服务绑定,从而软件增值服务绑定的激活验证码只能用于软件增值服务绑定的电子设备,避免激活验证码被盗后在其它电子设备上激活软件增值服务,降低了软件增值服务被盗用的概率。
在一可选的实施例中,第一电子设备或第二电子设备还用于,向服务器发送软件增值服务查看请求,该软件增值服务查看请求中携带有第一电子设备的设备标识;
服务器还用于在接收到软件增值服务查看请求后,向用户预置的接收方返回与第一电子设备的设备标识绑定的软件增值服务的相关信息。
在一可选的实施例中,第一电子设备向服务器发送软件增值服务购买请求时,具体可以用于:
获取用户输入的软件增值服务的标识。
获取到携带软件增值服务的标识的购买请求发送指令时,根据预置的用户账户与设备标识的对应关系,获取与用户当前使用的账户对应的设备标识。
生成软件增值服务购买请求,该软件增值服务购买请求中封装有获取的设备标识,以及上述用户输入的软件增值服务的标识。
向服务器发送所生成的软件增值服务购买请求。
在一可选的实施例中,第一电子设备向服务器发送软件增值服务购买请求时,具体可以用于:
获取用户输入的软件增值服务的标识。
获取到携带软件增值服务的标识的购买请求发送指令时,通过预置接口读取第一电子设备的设备标识;
生成软件增值服务购买请求,该软件增值服务购买请求中封装有读取的设备标识,以及上述用户输入的软件增值服务的标识。
向服务器发送所生成的软件增值服务购买请求。
在一可选的实施例中,第一电子设备或第二电子设备向服务器发送软件增值服务购买请求时,具体可以用于:
第一电子设备或第二电子设备获取用户输入的软件增值服务的标识,以及第一电子设备的设备标识。
第一电子设备或第二电子设备接收到购买请求发送指令时,生成软件增值服务购买请求,该软件增值服务购买请求中封装有上述用户输入的设备标识,以及上述用户输入的软件增值服务的标识。
第一电子设备或第二电子设备向服务器发送所生成的软件增值服务购买请求。
本申请还提供一种电子设备,本申请提供的电子设备的一种结构示意图如图8所示,可以包括:
第一发送模块81和第二发送模块82;其中,
第一发送模块81用于向服务器发送软件增值服务购买请求,该软件增值服务购买请求中携带有电子设备的设备标识,以使服务器在软件增值服务购买成功后,将设备标识与软件增值服务绑定,并向用户预置的接收方发送与软件增值服务绑定的激活验证码。
第二发送模块82用于在接收用户输入的上述激活验证码后,向服务器发送授权请求,该授权请求中携带有激活验证码和设备标识,以使服务器在接收到授权请求后,若授权请求中携带的激活验证码和设备标识,与服务器端的激活验证码和设备标识码均匹配,激活软件增值服务。
本申请提供的电子设备,在购买软件增值服务时,将使用软件增值服务的电子设备的设备标识也发送给服务器,软件增值服务购买成功后,将使用该软件增值服务的电子设备的设备标识与该软件增值服务绑定,从而软件增值服务绑定的激活验证码只能用于软件增值服务绑定的电子设备,避免激活验证码被盗后在其它电子设备上激活软件增值服务,降低了软件增值服务被盗用的概率。
在一可选的实施例中,本申请提供的电子设备还可以包括:
第三发送模块,用于向服务器发送软件增值服务查看请求,该软件增值服务查看请求中携带有第一电子设备的设备标识,以使服务器在接收到软件增值服务查看请求后,向用户预置的接收方返回与第一电子设备的设备标识绑定的软件增值服务的相关信息。
在一可选的实施例中,第一发送模块81具体可以用于:
获取用户输入的软件增值服务的标识。
当获取到携带软件增值服务的标识的购买请求发送指令时,根据预置的用户账户与设备标识的对应关系,获取与用户当前使用的账户对应的设备标识。
生成软件增值服务购买请求,该软件增值服务购买请求中封装有所获取的设备标识,以及用户输入的软件增值服务的标识。
向服务器发送所生成的软件增值服务购买请求。
在一可选的实施例中,第一发送模块81具体可以用于:
获取用户输入的软件增值服务的标识。
当接获取到携带软件增值服务的标识的购买请求发送指令时,通过预置接口读取电子设备的设备标识。
生成软件增值服务购买请求,该软件增值服务购买请求中封装有所读取设备标识,以及用户输入的软件增值服务的标识。
向服务器发送所生成的软件增值服务购买请求。
在一可选的实施例中,第一发送模块81具体可以用于:
获取用户输入的软件增值服务的标识,以及电子设备的设备标识。
当获取到购买请求发送指令时,生成软件增值服务购买请求,该软件增值服务购买请求中封装有用户输入的设备标识,以及用户输入的软件增值服务的标识。
向。服务器发送所生成的软件增值服务购买请求。
本申请还提供一种服务器,该服务器的一种结构示意图如图9所示,可以包括:
第一接收模块91,第四发送模块92和授权模块93;其中,
第一接收模块91用于接收软件增值服务购买请求,该软件增值服务购买请求中携带有第一电子设备的设备标识。
第四发送模块92用于在软件增值服务购买成功后,将设备标识与软件增值服务绑定,并向用户预置的接收方发送与软件增值服务绑定的激活验 证码。
授权模块93用于在接收到第一电子设备发送的携带有激活验证码和设备标识的授权请求后,若授权请求中携带的激活验证码及设备标识,与服务器端的激活验证码和设备标识均匹配,激活软件增值服务。
本申请提供的服务器,接收的购买请求中携带有使用软件增值服务的电子设备的设备标识,软件增值服务购买成功后,将使用该软件增值服务的电子设备的设备标识与该软件增值服务绑定,从而软件增值服务绑定的激活验证码只能用于软件增值服务绑定的电子设备,避免激活验证码被盗后在其它电子设备上激活软件增值服务,降低了软件增值服务被盗用的概率。
在一可选的实施例中,本申请提供的服务器还可以包括:
第三发送模块,用于向服务器发送软件增值服务查看请求,该软件增值服务查看请求中携带有设备标识,以使服务器在接收到软件增值服务查看请求后,向用户预置的接收方返回与设备标识绑定的软件增值服务的相关信息。
在一可选的实施例中,第一接收模块91具体用于,接收第一电子设备发送的软件增值服务购买请求;
该软件增值服务购买请求由第一电子设备在获取用户输入的软件增值服务的标识,当获取到携带上述软件增值服务的标识的购买请求发送指令时,根据预置的用户账户与设备标识的对应关系,获取与用户当前使用的账户对应的设备标识后生成,该软件增值服务购买请求中封装有所获取的设备标识,以及软件增值服务的标识。
在一可选的实施例中,第一接收模块91具体用于,接收第一电子设备发送的软件增值服务购买请求;
该软件增值服务购买请求由第一电子设备在获取用户输入的软件增值服务的标识,获取到携带软件增值服务的标识的购买请求发送指令时,通 过预置接口读取第一电子设备的设备标识后生成,该软件增值服务购买请求中封装有所读取的设备标识,以及上述软件增值服务的标识。
在一可选的实施例中,第一接收模块91具体用于,接收第一电子设备或第二电子设备发送的软件增值服务购买请求;
该软件增值服务购买请求由第一电子设备或第二电子设备获取用户输入的软件增值服务的标识,以及第一电子设备的设备标识;接收到购买请求发送指令后生成,该软件增值服务购买请求中封装有第一电子设备的设备标识,以及上述软件增值服务的标识。
所属领域的技术人员可以清楚地了解到,为描述的方便和简洁,上述描述的数据发送端和数据接收端的具体工作过程,可以参考前述方法实施例中的对应过程,在此不再赘述。
对所公开的实施例的上述说明,使本领域专业技术人员能够实现或使用本申请。对这些实施例的多种修改对本领域的专业技术人员来说将是显而易见的,本文中所定义的一般原理可以在不脱离本申请的精神或范围的情况下,在其它实施例中实现。因此,本申请将不会被限制于本文所示的这些实施例,而是要符合与本文所公开的原理和新颖特点相一致的最宽的范围。

Claims (30)

  1. 一种信息处理方法,其特征在于,包括:
    第一电子设备或第二电子设备向服务器发送软件增值服务购买请求,所述软件增值服务购买请求中携带有所述第一电子设备的设备标识;
    所述服务器在所述软件增值服务购买成功后,将所述设备标识与所述软件增值服务绑定,并向用户预置的接收方发送与所述软件增值服务绑定的激活验证码;
    所述第一电子设备在接收用户输入的所述激活验证码后,向所述服务器发送授权请求,所述授权请求中携带有所述激活验证码和所述设备标识;
    所述服务器在接收所述授权请求后,若所述授权请求中携带的激活验证码和设备标识,与所述服务器端的激活验证码和设备标识均匹配,激活所述软件增值服务。
  2. 根据权利要求1所述的方法,其特征在于,在所述软件增值服务购买成功后,还包括:
    所述第一电子设备或所述第二电子设备向所述服务器发送软件增值服务查看请求,所述软件增值服务查看请求中携带有所述设备标识;
    所述服务器在接收到所述软件增值服务查看请求后,向用户预置的接收方返回与所述设备标识绑定的软件增值服务的相关信息。
  3. 根据权利要求1所述的方法,其特征在于,所述第一电子设备向服务器发送软件增值服务购买请求,包括:
    所述第一电子设备获取用户输入的所述软件增值服务的标识;
    所述第一电子设备获取到携带所述软件增值服务的标识的购买请求发送指令时,根据预置的用户账户与设备标识的对应关系,获取与用户当前使用的账户对应的设备标识;
    所述第一电子设备生成软件增值服务购买请求,所述软件增值服务购买请求中封装有所述设备标识,以及所述软件增值服务的标识;
    所述第一电子设备向所述服务器发送所述软件增值服务购买请求。
  4. 根据权利要求1所述的方法,其特征在于,所述第一电子设备向服务器发送软件增值服务购买请求,包括:
    所述第一电子设备获取用户输入的所述软件增值服务的标识;
    所述第一电子设备获取到携带所述软件增值服务的标识的购买请求发送指令时,通过预置接口读取所述第一电子设备的设备标识;
    所述第一电子设备生成软件增值服务购买请求,所述软件增值服务购买请求中封装有所述设备标识,以及所述软件增值服务的标识;
    所述第一电子设备向所述服务器发送所述软件增值服务购买请求。
  5. 根据权利要求1所述的方法,其特征在于,所述第一电子设备或第二电子设备向服务器发送软件增值服务购买请求,包括:
    所述第一电子设备或所述第二电子设备获取用户输入的所述软件增值服务的标识,以及所述第一电子设备的设备标识;
    所述第一电子设备或所述第二电子设备接收到购买请求发送指令时,生成软件增值服务购买请求,所述软件增值服务购买请求中封装有所述设备标识,以及所述软件增值服务的标识;
    所述第一电子设备或所述第二电子设备向所述服务器发送所述软件增值服务购买请求。
  6. 一种信息处理方法,应用于电子设备,其特征在于,包括:
    向服务器发送软件增值服务购买请求,所述软件增值服务购买请求中携带有所述电子设备的设备标识,以使所述服务器在所述软件增值服务购买成功后,将所述设备标识与所述软件增值服务绑定,并向用户预置的接收方发送与所述软件增值服务绑定的激活验证码;
    在接收用户输入的所述激活验证码后,向所述服务器发送授权请求,所述授权请求中携带有所述激活验证码和所述设备标识,以使所述服务器在接收到所述授权请求后,若所述授权请求中携带的激活验证码和设备标识,与所述服务器端的激活验证码和设备标识码均匹配,激活所述软件增值服务。
  7. 根据权利要求6所述的方法,其特征在于,在所述软件增值服务购买成功后,还包括:
    向所述服务器发送软件增值服务查看请求,所述软件增值服务查看请求中携带有所述设备标识,以使所述服务器在接收到所述软件增值服务查 看请求后,向用户预置的接收方返回与所述设备标识绑定的软件增值服务的相关信息。
  8. 根据权利要求6所述的方法,其特征在于,所述向服务器发送软件增值服务购买请求,包括:
    获取用户输入的所述软件增值服务的标识;
    当获取到携带所述软件增值服务的标识的购买请求发送指令时,根据预置的用户账户与设备标识的对应关系,获取与用户当前使用的账户对应的设备标识;
    生成软件增值服务购买请求,所述软件增值服务购买请求中封装有所述设备标识,以及所述软件增值服务的标识;
    向所述服务器发送所述软件增值服务购买请求。
  9. 根据权利要求6所述的方法,其特征在于,所述向服务器发送软件增值服务购买请求,包括:
    获取用户输入的所述软件增值服务的标识;
    当接获取到携带所述软件增值服务的标识的购买请求发送指令时,通过预置接口读取所述电子设备的设备标识;
    生成软件增值服务购买请求,所述软件增值服务购买请求中封装有所述设备标识,以及所述软件增值服务的标识;
    向所述服务器发送所述软件增值服务购买请求。
  10. 根据权利要求6所述的方法,其特征在于,所述向服务器发送软件增值服务购买请求,包括:
    获取用户输入的所述软件增值服务的标识,以及所述电子设备的设备标识;
    当获取到购买请求发送指令时,生成软件增值服务购买请求,所述软件增值服务购买请求中封装有所述设备标识,以及所述软件增值服务的标识;
    向所述服务器发送所述软件增值服务购买请求。
  11. 一种信息处理方法,应用于服务器,其特征在于,包括:
    接收软件增值服务购买请求,所述软件增值服务购买请求中携带有第 一电子设备的设备标识;
    在所述软件增值服务购买成功后,将所述设备标识与所述软件增值服务绑定,并向用户预置的接收方发送与所述软件增值服务绑定的激活验证码;
    在接收到所述第一电子设备发送的携带有所述激活验证码和所述设备标识的授权请求后,若所述授权请求中携带的激活验证码及设备标识,与所述服务器端的激活验证码和设备标识均匹配,激活所述软件增值服务。
  12. 根据权利要求11所述的方法,其特征在于,还包括:
    在接收到所述第一电子设备或第二电子设备发送的软件增值服务查看请求后,向用户预置的接收方返回与所述软件增值服务查看请求中携带的设备标识绑定的软件增值服务的相关信息。
  13. 根据权利要求11所述的方法,其特征在于,所述接收软件增值服务购买请求,包括:接收所述第一电子设备发送的软件增值服务购买请求;
    所述软件增值服务购买请求由所述第一电子设备在获取用户输入的所述软件增值服务的标识,当获取到携带所述软件增值服务的标识的购买请求发送指令时,根据预置的用户账户与设备标识的对应关系,获取与用户当前使用的账户对应的设备标识后生成,所述软件增值服务购买请求中封装有所获取的设备标识,以及所述软件增值服务的标识。
  14. 根据权利要求11所述的方法,其特征在于,所述接收软件增值服务购买请求,包括:接收所述第一电子设备发送的软件增值服务购买请求;
    所述软件增值服务购买请求由所述第一电子设备在获取用户输入的所述软件增值服务的标识,获取到携带所述软件增值服务的标识的购买请求发送指令时,通过预置接口读取所述第一电子设备的设备标识后生成,所述软件增值服务购买请求中封装有所读取的设备标识,以及所述软件增值服务的标识。
  15. 根据权利要求11所述的方法,其特征在于,所述接收软件增值服务购买请求,包括:接收所述第一电子设备或第二电子设备发送的软件增值服务购买请求;
    所述软件增值服务购买请求由所述第一电子设备或所述第二电子设备 获取用户输入的所述软件增值服务的标识,以及所述第一电子设备的设备标识;接收到购买请求发送指令后生成,所述软件增值服务购买请求中封装有所述第一电子设备的设备标识,以及所述软件增值服务的标识。
  16. 一种信息处理系统,其特征在于,包括:电子设备和服务器;所述电子设备包括第一电子设备,或者,所述电子设备包括第一电子设备和第二电子设备;
    所述第一电子设备或所述第二电子设备用于向所述服务器发送软件增值服务购买请求,所述软件增值服务购买请求中携带有所述第一电子设备的设备标识;
    所述服务器用于在所述软件增值服务购买成功后,将所述设备标识与所述软件增值服务绑定,并向用户预置的接收方发送与所述软件增值服务对应的激活验证码;
    所述第一电子设备还用于在获取所述激活验证码后,向所述服务器发送授权请求,所述授权请求中携带有所述激活验证码和所述设备标识;
    所述服务器还用于在接收所述授权请求后,若所述授权请求中携带的激活验证码和设备标识,与所述服务器端的激活验证码和设备标识均匹配,激活所述软件增值服务。
  17. 根据权利要求16所述的系统,其特征在于,所述第一电子设备或所述第二电子设备还用于,向所述服务器发送软件增值服务查看请求,所述软件增值服务查看请求中携带有所述设备标识;
    所述服务器还用于在接收到所述软件增值服务查看请求后,向用户预置的接收方返回与所述设备标识绑定的软件增值服务的相关信息。
  18. 根据权利要求16所述的系统,其特征在于,所述第一电子设备向所述服务器发送软件增值服务购买请求时,具体用于:
    获取用户输入的所述软件增值服务的标识;
    获取到携带所述软件增值服务的标识的购买请求发送指令时,根据预置的用户账户与设备标识的对应关系,获取与用户当前使用的账户对应的设备标识;
    生成软件增值服务购买请求,所述软件增值服务购买请求中封装有所 述设备标识,以及所述软件增值服务的标识;
    向所述服务器发送所述软件增值服务购买请求。
  19. 根据权利要求16所述的系统,其特征在于,所述第一电子设备向所述服务器发送软件增值服务购买请求时,具体用于:
    获取用户输入的所述软件增值服务的标识;
    获取到携带所述软件增值服务的标识的购买请求发送指令时,通过预置接口读取所述第一电子设备的设备标识;
    生成软件增值服务购买请求,所述软件增值服务购买请求中封装有所述设备标识,以及所述软件增值服务的标识;
    向所述服务器发送所述软件增值服务购买请求。
  20. 根据权利要求16所述的系统,其特征在于,所述第一电子设备或第二电子设备向服务器发送软件增值服务购买请求时,具体用于:
    所述第一电子设备或所述第二电子设备获取用户输入的所述软件增值服务的标识,以及所述第一电子设备的设备标识;
    所述第一电子设备或所述第二电子设备接收到购买请求发送指令时,生成软件增值服务购买请求,所述软件增值服务购买请求中封装有所述设备标识,以及所述软件增值服务的标识;
    所述第一电子设备或所述第二电子设备向所述服务器发送所述软件增值服务购买请求。
  21. 一种电子设备,其特征在于,包括:
    第一发送模块,用于向服务器发送软件增值服务购买请求,所述软件增值服务购买请求中携带有所述电子设备的设备标识,以使所述服务器在所述软件增值服务购买成功后,将所述设备标识与所述软件增值服务绑定,并向用户预置的接收方发送与所述软件增值服务绑定的激活验证码;
    第二发送模块,用于在接收用户输入的所述激活验证码后,向所述服务器发送授权请求,所述授权请求中携带有所述激活验证码和所述设备标识,以使所述服务器在接收到所述授权请求后,若所述授权请求中携带的激活验证码和设备标识,与所述服务器端的激活验证码和设备标识码均匹配,激活所述软件增值服务。
  22. 根据权利要求21所述的电子设备,其特征在于,还包括:
    第三发送模块,用于向所述服务器发送软件增值服务查看请求,所述软件增值服务查看请求中携带有所述设备标识,以使所述服务器在接收到所述软件增值服务查看请求后,向用户预置的接收方返回与所述设备标识绑定的软件增值服务的相关信息。
  23. 根据权利要求21所述的电子设备,其特征在于,所述第一发送模块具体用于:
    获取用户输入的所述软件增值服务的标识;
    当获取到携带所述软件增值服务的标识的购买请求发送指令时,根据预置的用户账户与设备标识的对应关系,获取与用户当前使用的账户对应的设备标识;
    生成软件增值服务购买请求,所述软件增值服务购买请求中封装有所述设备标识,以及所述软件增值服务的标识;
    向所述服务器发送所述软件增值服务购买请求。
  24. 根据权利要求21所述的电子设备,其特征在于,所述第一发送模块具体用于:
    获取用户输入的所述软件增值服务的标识;
    当接获取到携带所述软件增值服务的标识的购买请求发送指令时,通过预置接口读取所述电子设备的设备标识;
    生成软件增值服务购买请求,所述软件增值服务购买请求中封装有所述设备标识,以及所述软件增值服务的标识;
    向所述服务器发送所述软件增值服务购买请求。
  25. 根据权利要求21所述的电子设备,其特征在于,所述第一发送模块具体用于:
    获取用户输入的所述软件增值服务的标识,以及所述电子设备的设备标识;
    当获取到购买请求发送指令时,生成软件增值服务购买请求,所述软件增值服务购买请求中封装有所述设备标识,以及所述软件增值服务的标识;
    向所述服务器发送所述软件增值服务购买请求。
  26. 一种服务器,其特征在于,包括:
    第一接收模块,用于接收软件增值服务购买请求,所述软件增值服务购买请求中携带有第一电子设备的设备标识;
    第四发送模块,用于在所述软件增值服务购买成功后,将所述设备标识与所述软件增值服务绑定,并向用户预置的接收方发送与所述软件增值服务绑定的激活验证码;
    授权模块,用于在接收到所述第一电子设备发送的携带有所述激活验证码和所述设备标识的授权请求后,若所述授权请求中携带的激活验证码及设备标识,与所述服务器端的激活验证码和设备标识均匹配,激活所述软件增值服务。
  27. 根据权利要求26所述的服务器,其特征在于,还包括:
    第五发送模块,用于在接收到所述第一电子设备或第二电子设备发送的软件增值服务查看请求后,向用户预置的接收方返回与所述软件增值服务查看请求中携带的设备标识绑定的软件增值服务的相关信息。
  28. 根据权利要求26所述的服务器,其特征在于,所述第一接收模块具体用于,接收所述第一电子设备发送的软件增值服务购买请求;
    所述软件增值服务购买请求由所述第一电子设备在获取用户输入的所述软件增值服务的标识,当获取到携带所述软件增值服务的标识的购买请求发送指令时,根据预置的用户账户与设备标识的对应关系,获取与用户当前使用的账户对应的设备标识后生成,所述软件增值服务购买请求中封装有所获取的设备标识,以及所述软件增值服务的标识。
  29. 根据权利要求26所述的服务器,其特征在于,所述第一接收模块具体用于,接收所述第一电子设备发送的软件增值服务购买请求;
    所述软件增值服务购买请求由所述第一电子设备在获取用户输入的所述软件增值服务的标识,获取到携带所述软件增值服务的标识的购买请求发送指令时,通过预置接口读取所述第一电子设备的设备标识后生成,所述软件增值服务购买请求中封装有所读取的设备标识,以及所述软件增值服务的标识。
  30. 根据权利要求26所述的服务器,其特征在于,所述第一接收模块具体用于,接收所述第一电子设备或第二电子设备发送的软件增值服务购买请求;
    所述软件增值服务购买请求由所述第一电子设备或所述第二电子设备获取用户输入的所述软件增值服务的标识,以及所述第一电子设备的设备标识;接收到购买请求发送指令后生成,所述软件增值服务购买请求中封装有所述第一电子设备的设备标识,以及所述软件增值服务的标识。
PCT/CN2018/097404 2018-07-27 2018-07-27 信息处理方法、电子设备、服务器和信息处理系统 WO2020019291A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2018/097404 WO2020019291A1 (zh) 2018-07-27 2018-07-27 信息处理方法、电子设备、服务器和信息处理系统
CN201880041770.7A CN110859046A (zh) 2018-07-27 2018-07-27 信息处理方法、电子设备、服务器和信息处理系统

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2018/097404 WO2020019291A1 (zh) 2018-07-27 2018-07-27 信息处理方法、电子设备、服务器和信息处理系统

Publications (1)

Publication Number Publication Date
WO2020019291A1 true WO2020019291A1 (zh) 2020-01-30

Family

ID=69180603

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/097404 WO2020019291A1 (zh) 2018-07-27 2018-07-27 信息处理方法、电子设备、服务器和信息处理系统

Country Status (2)

Country Link
CN (1) CN110859046A (zh)
WO (1) WO2020019291A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112765587A (zh) * 2021-01-20 2021-05-07 Oppo广东移动通信有限公司 业务操作验证方法和装置、控制方法和装置、服务器
CN114741664B (zh) * 2022-04-21 2024-01-09 巨翊科技(上海)有限公司 一种软件的授权方法、装置及系统

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103002415B (zh) * 2011-09-15 2015-08-26 阿里巴巴集团控股有限公司 一种通过短信发送验证码的方法和装置
CN106034134A (zh) * 2015-03-19 2016-10-19 腾讯科技(深圳)有限公司 网页应用程序中进行身份认证请求的方法、辅助方法及装置

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
FI20031482A (fi) * 2003-10-10 2005-04-11 Open Bit Oy Ltd Maksutapahtumatietojen prosessointi
JP2005189913A (ja) * 2003-12-24 2005-07-14 Nec Saitama Ltd ソフトウェアライセンス管理方法およびプログラム
US20060064761A1 (en) * 2004-09-22 2006-03-23 Microsoft Corporation Issuing unlock codes from a server with third party billing
US8417641B1 (en) * 2006-01-31 2013-04-09 Kyocera Corporation System for licensing mobile applications, features, and devices
CN104579671B (zh) * 2013-10-29 2018-01-16 中国银联股份有限公司 身份验证方法及系统
US9536060B2 (en) * 2014-05-03 2017-01-03 Clevx, Llc Network information system with license registration and method of operation thereof
CN106503492A (zh) * 2016-10-27 2017-03-15 厦门中控生物识别信息技术有限公司 一种授权管理方法、服务器、客户设备和系统

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103002415B (zh) * 2011-09-15 2015-08-26 阿里巴巴集团控股有限公司 一种通过短信发送验证码的方法和装置
CN106034134A (zh) * 2015-03-19 2016-10-19 腾讯科技(深圳)有限公司 网页应用程序中进行身份认证请求的方法、辅助方法及装置

Also Published As

Publication number Publication date
CN110859046A (zh) 2020-03-03

Similar Documents

Publication Publication Date Title
US11093981B2 (en) Smart broadcasting device
US10387856B2 (en) Online payment method, system, and apparatus
CN102821104B (zh) 授权的方法、装置和系统
US8201232B2 (en) Authentication, identity, and service management for computing and communication systems
CN100566248C (zh) 数字签名保证系统、方法和装置
CN106716960B (zh) 用户认证方法和系统
CN106716918B (zh) 用户认证方法和系统
US20180041893A1 (en) Method and system of multi-terminal mapping to a virtual sim card
CN106875177A (zh) 订单处理方法、装置及支付服务器
CN110335111B (zh) 数据处理方法、系统、终端及服务器
CN112039826B (zh) 应用于小程序端的登录方法和装置,电子设备,可读介质
TWI270284B (en) Method and system for downloading and authenticating digital copyright
US9286462B2 (en) Apparatus and method for automatic login
WO2020019291A1 (zh) 信息处理方法、电子设备、服务器和信息处理系统
WO2020044088A1 (zh) 一种文件传输的方法及其装置、设备/终端/服务器
KR101748615B1 (ko) 접속 정보 확인에 기초한 모바일 간편 결제 보조 장치 및 그 동작 방법
CN109784915B (zh) 内容预置方法和装置
CN109034759B (zh) 一种数据转移方法及相关设备
US10867068B2 (en) Personal computing devices with assisted form completion
US20020042780A1 (en) Method for purchasing an electronic document in a network
CN106716401A (zh) 一种数据交互处理方法、装置以及系统
KR101103634B1 (ko) 이동 단말기를 이용한 카드사 서버의 인증 방법 및 카드사 서버
CN110365646B (zh) 将实体关联到第一服务器的方法及装置
CN114417318A (zh) 第三方页面的跳转方法、装置和电子设备
CN110134530A (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: 18928087

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: 18928087

Country of ref document: EP

Kind code of ref document: A1