IoT device-based rights processing method and apparatus

Abstract

The embodiment of the specification provides an IoT device-based benefit processing method and device, wherein the IoT device-based benefit processing method comprises the following steps: after an IoT device performs identity credential login of a user, in a benefit recommendation process to the user, obtaining an identity label of the user and a third-party label of a merchant, converting the third-party label into a conversion label, further matching the identity label and the conversion label with a recommended benefit configured by a benefit policy to obtain a target recommended benefit of the user, performing benefit rendering according to a benefit template of the target recommended benefit, and showing a rendered benefit recommendation page obtained by the rendering to the user through the IoT device, so as to realize benefit recommendation to the user by means of the IoT device.

Description

[0001] This application is a divisional application of the Chinese patent application No. CN202411026198.0, filed on July 29, 2024, entitled "IoT device-based benefit processing method and device". TECHNICAL FIELD

[0002] The present document relates to the technical field of data processing, and in particular to an IoT device-based benefit processing method and device. BACKGROUND

[0003] With the continuous development and promotion of the Internet, the application range of online services based on the Internet is also becoming more and more extensive, and has gradually covered most users. In this case, various forms of online services have appeared, and service scenarios in which online services cooperate with IoT (Internet of Things) devices have also appeared, such as user face login through IoT devices deployed in a merchant, and corresponding order payment based on face login. However, as IoT devices are applied more and more widely in merchants, the merchants have higher and higher requirements for the functionality of IoT devices, which brings certain challenges to institutions providing IoT devices. SUMMARY

[0004] One or more embodiments of the present specification provide an IoT device-based benefit processing method, comprising: performing identity credential login of a user on an IoT device of a merchant, and obtaining an identity tag of the user and a third-party tag in the merchant. Converting the third-party tag based on a tag mapping relationship to obtain a converted tag mapped by the third-party tag. Matching the identity tag and the converted tag with a recommended benefit configured by a benefit policy of the IoT device to obtain a target recommended benefit of the user. Rendering the benefit according to a benefit template of the target recommended benefit, and displaying a rendered benefit recommendation page on an interactive screen of the IoT device.

[0005] One or more embodiments of the present specification provide an IoT device-based benefit processing device, comprising: a tag obtaining module configured to perform identity credential login of a user on an IoT device of a merchant, and obtain an identity tag of the user and a third-party tag in the merchant. A tag conversion module configured to convert the third-party tag based on a tag mapping relationship to obtain a converted tag mapped by the third-party tag. A matching module configured to match the identity tag and the converted tag with a recommended benefit configured by a benefit policy of the IoT device to obtain a target recommended benefit of the user. A rendering and displaying module configured to render the benefit according to a benefit template of the target recommended benefit, and display a rendered benefit recommendation page on an interactive screen of the IoT device.

[0006] One or more embodiments of the specification provide an IoT device-based benefit processing device, comprising: a processor; and a memory configured to store computer executable instructions that, when executed, cause the processor to: log in a user's identity credential at an IoT device of a merchant, and acquire an identity tag of the user and a third-party tag at the merchant. Convert the third-party tag based on a tag mapping relationship to obtain a converted tag mapped from the third-party tag. Match the identity tag and the converted tag with a recommended benefit configured by a benefit policy of the IoT device to obtain a target recommended benefit of the user. Render the benefit according to a benefit template of the target recommended benefit, and display a rendered benefit recommendation page through an interactive screen of the IoT device.

[0007] One or more embodiments of the specification provide a computer readable storage medium for storing computer executable instructions, which, when executed, implement the following processes: log in a user's identity credential at an IoT device of a merchant, and acquire an identity tag of the user and a third-party tag at the merchant. Convert the third-party tag based on a tag mapping relationship to obtain a converted tag mapped from the third-party tag. Match the identity tag and the converted tag with a recommended benefit configured by a benefit policy of the IoT device to obtain a target recommended benefit of the user. Render the benefit according to a benefit template of the target recommended benefit, and display a rendered benefit recommendation page through an interactive screen of the IoT device. BRIEF DESCRIPTION OF DRAWINGS

[0008] In order to more clearly illustrate the technical solutions in the one or more embodiments of the specification or the prior art, brief descriptions will be given to the drawings needed to be used in the embodiments or prior art descriptions. Obviously, the drawings in the following description are only some embodiments described in the specification, and for those skilled in the art, other drawings can also be obtained without creative labor based on these drawings;

[0009] Figure 1 A schematic diagram of an IoT device-based benefit processing method implementation environment provided by one or more embodiments of the specification;

[0010] Figure 2 A benefit processing method processing flowchart provided by one or more embodiments of the specification;

[0011] Figure 3 A schematic diagram of a benefit recommendation page provided by one or more embodiments of the specification;

[0012] Figure 4 A flowchart illustrating a rights processing method based on IoT devices for offline merchant scenarios, provided by one or more embodiments of this specification.

[0013] Figure 5 A schematic diagram illustrating an embodiment of an IoT device-based rights processing apparatus provided in one or more embodiments of this specification;

[0014] Figure 6 This is a schematic diagram of the structure of an IoT-based rights processing device provided for one or more embodiments of this specification. Detailed Implementation

[0015] To enable those skilled in the art to better understand the technical solutions in one or more embodiments of this specification, the technical solutions in one or more embodiments of this specification will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this specification, and not all of the embodiments. Based on one or more embodiments of this specification, all other embodiments obtained by those skilled in the art without creative effort should fall within the protection scope of this document.

[0016] The rights processing method based on IoT devices provided in one or more embodiments of this specification can be applied to the implementation environment of merchant marketing. (Refer to...) Figure 1 The implementation environment includes at least:

[0017] The merchant's IoT device 101 is used for user login with identity credentials within the merchant, as well as for recommending benefits to users. It can also perform order settlement based on the benefit recommendations. The IoT device 101 is equipped with a service component, which is used by the IoT device 101 to perform identity login, benefit recommendations and order settlement.

[0018] The implementation environment may also include an application server 102 and a merchant system 103. During the process of recommending benefits, the service components deployed on the IoT device 101 need to interact with the application server 102 and the merchant system 103. The application server 102 and the merchant system 103 are used to cooperate with the IoT device 101 to recommend benefits to users.

[0019] In this implementation environment, when recommending benefits to the merchant's users, the merchant's IoT device 101, after logging in with the user's identity credentials, obtains the user's identity tag from the application server 102 and the user's third-party tag in the merchant system 103. For the third-party tag obtained from the merchant system 103, it is converted into a corresponding conversion tag based on the tag mapping relationship. On this basis, by matching the identity tag and conversion tag with the recommended benefits configured in the benefit strategy of the IoT device 101, the target recommended benefit to be recommended to the user is obtained. Finally, the benefit is rendered according to the benefit template of the target recommended benefit, and the rendered benefit recommendation page is displayed to the user through the interactive screen of the IoT device 101. In this way, the IoT device 101 realizes the recommendation of benefits to the user.

[0020] This specification provides one or more embodiments of a rights handling method based on IoT devices, as follows:

[0021] Reference Figure 2 The rights processing method based on IoT devices provided in this embodiment specifically includes steps S202 to S208.

[0022] Step S202: Log in to the merchant's IoT device using the user's identity credentials and obtain the user's identity tag and the merchant's third-party tag.

[0023] The IoT device for merchants mentioned in this embodiment refers to the IoT device deployed in the merchant's premises. Through this IoT device, users within the merchant can log in using their identity credentials, and the merchant can recommend benefits to users. Furthermore, the merchant can settle user orders based on the recommended benefits.

[0024] Optionally, the IoT device is configured with a first interactive screen for interacting with users and / or a second interactive screen for interacting with merchants; an IoT device configured with a first interactive screen and a second interactive screen can be called a dual-screen IoT device, and an IoT device configured with a first interactive screen can be called a single-screen IoT device.

[0025] Specifically, an IoT device can be an IoT device provided by a payment institution to a merchant for payment purposes (payment IoT device). This IoT device can interact / cooperate with the merchant's POS device to log in with the user's identity credentials and settle orders. Alternatively, this IoT device can interact / cooperate with the payment institution's backend server (i.e., the application server of the payment institution's payment application) through an interface call to log in with the user's identity credentials and settle orders.

[0026] Furthermore, by deploying service components on IoT devices, these devices can recommend benefits to users. These service components can be application components, such as payment application components of a payment institution. By deploying payment application components on a merchant's IoT device, the IoT device can interact with the application server of the payment application, as well as with the merchant's POS equipment or merchant system.

[0027] Optionally, the rights processing method based on IoT devices provided in this embodiment can be applied to the service components of applications deployed on IoT devices.

[0028] In practice, for IoT devices to recommend benefits to users, it is necessary to log in with the user's identity credentials. Specifically, during the process of logging in with the user's identity credentials on the IoT device, the user can log in with the identity credentials through interaction with the IoT device, or the merchant can log in with the user's identity credentials through the IoT device.

[0029] In one optional implementation of this embodiment, user authentication login is performed on the merchant's IoT device using any of the following methods:

[0030] Login with identity credentials by scanning the login identifier displayed on the first interactive screen using the application installed on the user's terminal; login with identity credentials by scanning the user identifier displayed on the application using the IoT device; login with identity credentials based on the user's identity credentials information entered on the second interactive screen; and login with identity credentials based on the identity information obtained by identity recognition from the user image collected by the IoT device.

[0031] The following sections provide a detailed explanation of the implementation process of the four methods for user authentication login on merchant IoT devices provided above.

[0032] (1) Regarding the method of logging in with identity credentials by scanning the login identifier displayed on the first interactive screen through the application installed on the user's user terminal, in the specific execution process, the application can parse the login identifier displayed on the first interactive screen, call the query interface to query the merchant's identity credentials according to the parsing result, obtain the identity credentials information returned by the interface call, and send the identity credentials information to the IoT device so that the IoT device can log in with the user's identity credentials based on the identity credentials information;

[0033] For example, users can scan the login identifier code displayed on the first interactive screen of an IoT device through the payment application of a payment institution. After decoding the login identifier code, the user calls the query interface to query the merchant for the user's identity credential information based on the decoding result. The merchant queries the user's identity credential information in the correspondence between the user identity identifier and identity credential based on the user identity identifier passed in the interface call and returns it. The identity credential information returned by the interface call is sent to the IoT device for identity credential login.

[0034] In addition, for the method of logging in with identity credentials by scanning the login identifier displayed on the first interactive screen through the application installed on the user's terminal, the application can also parse the login identifier displayed on the first interactive screen, and jump to the merchant's sub-program within the application based on the parsing result. The sub-program queries the user's identity credential information and sends it to the IoT device, so that the IoT device can log in with the user's identity credentials based on the identity credential information.

[0035] (2) Regarding the method of logging in with identity credentials by scanning the user identifier displayed by the application through the IoT device, in the specific execution process, the IoT device can scan the user identifier displayed by the application on the user terminal and perform identifier parsing. Based on the parsing result, it calls the query interface to query the merchant for identity credentials, obtains the identity credentials information returned by the interface call, and logs in with the user's identity credentials based on the identity credentials information.

[0036] (3) For the method of logging in with identity credentials based on the user's identity credentials entered on the second interactive screen, the user's identity credentials entered by the merchant on the second interactive screen can be used to log in with identity credentials; whereby the user's identity credentials can be the user's membership credentials at the merchant, and the identity credentials information can be the member ID.

[0037] (4) Regarding the method of logging in with identity credentials based on identity information obtained from user images collected by IoT devices, in the specific execution process, after the IoT device collects the user image, it can call the identity verification interface provided by the payment institution through the program component of the application of the deployed payment institution to perform user identity recognition, query the user's identity credentials information based on the identity recognition result, and finally log in with the user's identity credentials based on the identity credentials information.

[0038] In this embodiment, based on the user's identity credentials login on the merchant's IoT device, during the process of recommending benefits to the user, the user's identity tag and the user's third-party tag at the merchant are first obtained.

[0039] Among them, identity tags refer to data tags related to a user's identity. Based on the program components of a payment institution's payment application, identity tags can be obtained from the payment application. Identity tags can be data tags related to a user's identity within the payment application. Third-party tags refer to tags configured by the merchant for the user. Third-party tags include standardized tags corresponding to the user's data in the merchant's data, determined from pre-configured standardized tags, and / or new tags configured by the merchant for the user.

[0040] In practice, when obtaining user identity tags and third-party tags from merchants, the identity tags and third-party tags can be obtained based on the service components of the application deployed on the IoT device, using the corresponding interfaces configured in the service components.

[0041] Specifically, in one optional implementation of this embodiment, obtaining the user's identity tag and the merchant's third-party tag includes:

[0042] Call the identity tag interface of the service component to obtain the identity tag corresponding to the user's identity information in the application;

[0043] Call the third-party tag interface of the service component to obtain the third-party tag associated with the user's user information under the merchant, and / or obtain the third-party tag corresponding to the user's consumption record under the merchant.

[0044] In this context, a user's identity information in the application can be their date of birth, occupation, and / or place of residence. Correspondingly, the identity tags associated with this identity information can be date of birth tags, occupation tags, and / or place of residence tags.

[0045] The third-party tags associated with a user's information under a merchant can be tags such as whether the user is a merchant member, whether the user is a dormant user, whether the user has churned, the list tags of the user's added-to-cart list, and / or the amount tags of the user's added-to-cart amount.

[0046] The third-party tags corresponding to a user's consumption records under a merchant can be product tags or category tags that have been frequently purchased in the past 30 days.

[0047] Step S204: Based on the tag mapping relationship, the third-party tag is converted to obtain the converted tag of the third-party tag mapping.

[0048] In this embodiment, to improve the accuracy and comprehensiveness of the benefit recommendations, during the tag acquisition process, not only the user's identity tag is acquired, but also the user's third-party tags at the merchant. Here, the acquired third-party tags at the merchant may be non-standardized tags. In order to avoid the inability to identify non-standardized tags during the subsequent tag and benefit matching process, the third-party tags at the merchant are converted to standardize the third-party tags.

[0049] Specifically, in one optional implementation of this embodiment, the third-party tags are converted based on the tag mapping relationship to obtain the converted tags of the third-party tag mapping, including:

[0050] Read the pre-configured tag mapping relationship of the merchant, and query the standardized tag of the third-party tag mapping in the read tag mapping relationship as the conversion tag.

[0051] The tag mapping relationship records the mapping relationship between merchants' third-party tags and standardized tags. Specifically, different merchants can be configured with their own tag mapping relationships, or the service providers of IoT devices can pre-configure their own tag mapping relationships. During the tag conversion process, the tag mapping relationship is determined according to the service provider to which the IoT devices deployed by the merchant belong, and then the user's third-party tags in the merchant are converted into standardized tags according to the determined tag mapping relationship.

[0052] Step S206: Match the identity tag and the conversion tag with the recommended benefits configured in the rights and benefits policy of the IoT device to obtain the user's target recommended benefits.

[0053] The benefit strategy described in this embodiment refers to a pre-configured strategy for recommending benefits to users. Specifically, the benefit strategy consists of the recommended benefit and the benefit tag rules configured for that benefit. For example, benefit strategy 1 might configure a birthday discount benefit, with the benefit tag rule specifying that the user is eligible for the birthday discount if the month in their birth date tag matches the current month. Another example is benefit strategy 2, which configures a single-item discount benefit, with the benefit tag rule specifying that the user is eligible for a single-item discount if the tag of a frequently purchased item in the past 30 days overlaps with the item specified for the single-item discount benefit.

[0054] Here, the rights and benefits strategy of IoT devices can be a rights and benefits strategy pre-configured by the IoT device service provider for different merchants' IoT devices; the rights and benefits strategy of IoT devices can also refer to the rights and benefits strategy configured from different perspectives during the process of recommending rights and benefits to users based on IoT devices. In this case, the rights and benefits strategy of IoT devices can also be replaced by the merchant's rights and benefits strategy, the user's rights and benefits strategy, or the rights and benefits strategy for identity credentials (for example, the rights and benefits strategy for member users).

[0055] In practice, based on the user's identity tag and the conversion tag obtained from the third-party tag conversion, the user's identity tag and conversion tag are matched with the recommended benefits configured in the benefit policy. The target recommended benefit to be recommended to the user is determined based on the matching result. Specifically, in the process of matching the identity tag and conversion tag with the recommended benefits configured in the benefit policy of the IoT device, it can be detected whether there are tags in the identity tag and conversion tag that meet the benefit tag rules of the recommended benefit. If so, the recommended benefit is taken as the target recommended benefit to be recommended to the user; if not, no processing is required.

[0056] In practical applications, to improve the targeting of benefit recommendations, multiple benefit conditions can be configured for the recommended benefits in the benefit strategy. This configuration of benefit conditions enhances the effectiveness of user filtering, thereby improving the targeting of benefit recommendations. In this embodiment, one optional implementation involves matching identity tags and conversion tags with the recommended benefits configured in the benefit strategy to obtain the user's target recommended benefits, including:

[0057] Detect whether there is a tag among the identity tag and the conversion tag that satisfies the rights tag rule of the recommended rights; the rights tag rule is obtained by combining multiple rights conditions corresponding to the tag; if yes, the recommended rights to which the rights tag rule is satisfied are taken as the target recommended rights; if no, no processing is required.

[0058] Furthermore, in practical applications, there may be situations where multiple benefit strategies are configured simultaneously. For example, if benefit strategy 1 is configured to recommend birthday discount benefits to users for merchants, benefit strategy 2 is configured to recommend single-item discount benefits to users at the same time. However, in actual benefit redemption scenarios, there may often be mutually exclusive benefits. In this regard, this embodiment avoids the occurrence of mutually exclusive benefits by setting the priority of benefit strategies.

[0059] Specifically, in one optional implementation of this embodiment, identity tags and conversion tags are matched with the recommended benefits configured in the benefits policy to obtain the user's target recommended benefits, including:

[0060] If the IoT device is configured with multiple rights and benefits policies, the identity tag and the conversion tag are matched with the recommended rights and benefits configured in each rights and benefits policy to obtain candidate recommended rights and benefits;

[0061] Based on the priority of each benefit strategy, the candidate benefit that meets the preset conditions is selected as the target benefit.

[0062] If there is only one candidate recommendation right, then that candidate recommendation right can be used as the target recommendation right to recommend to the user; if there are multiple candidate recommendation rights, then the candidate recommendation rights are sorted according to their respective priorities from high to low, and the candidate recommendation right with the highest priority is used as the target recommendation right to recommend to the user.

[0063] Step S208: Render the benefits based on the benefit template of the target recommended benefits, and display the rendered benefit recommendation page through the interactive screen of the IoT device.

[0064] The above method matches user identity tags and conversion tags with the recommended benefits configured in the benefits strategy to obtain target recommended benefits for users. Here, in the process of recommending target recommended benefits to users, the benefits are rendered according to the benefit template of the target recommended benefits, and the rendered benefit recommendation page is displayed on the interactive screen of IoT devices. This is to improve users' perception and interest in the benefit recommendations, thereby improving the conversion rate of the benefits being used and redeemed after the benefits are recommended, and ultimately helping merchants increase the number of payment transactions.

[0065] In one optional implementation of this embodiment, rights rendering is performed based on the rights template of the target recommended rights, including:

[0066] Based on the display parameters of the first interactive screen of the IoT device and the benefit type of the target recommended benefit, determine the template parameters of the benefit template of the target recommended benefit, and obtain the rendering material corresponding to the target recommended benefit or the benefit type;

[0067] The benefit recommendation page is rendered based on the benefit template, the template parameters, and the rendering materials, representing the target recommended benefit.

[0068] The display parameters may include the screen type (landscape / portrait), screen size, and / or the size / position of the screen area where the benefits are displayed; the rendering materials include background images and / or text for recommending the benefits.

[0069] For example, Figure 3 The birthday benefits page shown has a background image and text for the birthday benefits on the left, and the details of the birthday benefits are displayed on the right, along with a control 301 for claiming the birthday benefits.

[0070] In practice, after rendering the benefits and obtaining the benefit recommendation page, the rendered benefit recommendation page is displayed on the interactive screen of the IoT device. During this process, the benefit recommendation page can be displayed to users through the first interactive screen of the IoT device. In addition, the benefit reminder of the target recommended benefit can also be displayed to merchant personnel through the second interactive screen of the IoT device, thereby improving the merchant personnel's awareness of the benefit recommendation. Furthermore, the merchant personnel can also remind users to claim the recommended target benefit through voice reminders, which helps to improve the conversion rate of benefit usage and redemption after the benefit recommendation, and ultimately helps merchants increase the number of payment transactions.

[0071] Specifically, in one optional implementation of this embodiment, the rights recommendation page obtained by displaying the rendering on the interactive screen of an IoT device includes: displaying a rights reminder of the target recommended rights on the second interactive screen, and displaying the rights recommendation page on the first interactive screen.

[0072] In this embodiment, after the rights recommendation page is displayed and rendered on the interactive screen of the IoT device, the user can claim rights based on the rights recommendation page and can use and redeem rights based on the claimed rights. In an optional implementation of this embodiment, after the rights recommendation page is displayed and rendered on the interactive screen of the IoT device, the following operations are performed: if the rights control configured on the rights recommendation page is detected to be triggered, the target recommended rights are issued to the user, or the target recommended rights are issued to the user's user account; the settlement amount of the user's pending order on the IoT device is calculated based on the target recommended rights, and the order is settled on the IoT device according to the settlement amount.

[0073] In summary, the IoT device-based rights processing method provided in this embodiment allows merchants' IoT devices to recommend rights to their users. In addition to user login using their identity credentials, the method obtains both the user's identity tag in the application and the user's third-party tag within the merchant's ecosystem. Based on tag mapping relationships, the third-party tags obtained from the merchant are converted into corresponding standardized tags. Then, by matching the identity tags and converted tags with the recommended rights configured in the rights strategy, the target recommended rights are determined. Finally, the rights are rendered according to the rights template of the target recommended rights, and the rendered rights recommendation page is displayed to the user through the interactive screen of the IoT device. This enhances the user's perception and interest in the rights recommendations, thereby increasing the conversion rate of rights usage and redemption after recommendation, and ultimately helping merchants increase the number of payment transactions.

[0074] The following example illustrates the application of an IoT-based rights processing method provided in this embodiment in an offline merchant scenario. Figure 4The rights processing method based on IoT devices provided in this embodiment will be further explained below. Figure 4 The method for handling rights and interests based on IoT devices and applied to offline merchant scenarios includes the following steps.

[0075] Step S402: Log in to the merchant's IoT device using the user's identity credentials.

[0076] Among them, the IoT device is a dual-screen IoT device equipped with a user screen (first interactive screen) for interacting with users and a merchant screen (second interactive screen) for interacting with merchants.

[0077] Step S404: Call the identity tag interface of the service component deployed on the IoT device to obtain the identity tag corresponding to the user's identity information in the application.

[0078] Step S406: Call the third-party tag interface of the service component to obtain the third-party tags associated with the user's user information under the merchant and the third-party tags corresponding to the consumption records.

[0079] Step S408: Convert the third-party tags based on the tag mapping relationship to obtain standardized tags.

[0080] Step S410: Match the identity tag and standardized tag with the recommended rights configured in the rights strategy of the identity credential to obtain the target recommended rights.

[0081] Step S412: Display a reminder of the target recommended benefits on the merchant screen of the IoT device.

[0082] Step S414: Render the benefits based on the benefit template of the target recommended benefits, and display the benefit recommendation page on the user screen of the IoT device.

[0083] Step S416: If the rights control configured on the rights recommendation page is triggered, the target recommended rights are issued to the user.

[0084] Step S418: Calculate the settlement amount of the user's pending orders based on the target recommendation benefits, and settle the orders on the IoT device according to the settlement amount.

[0085] It should be noted that any one or any combination of steps S402 to S418 can be replaced by the corresponding technical means provided in steps S202 to S208 as needed for implementation and deployment, which will not be elaborated here.

[0086] This specification provides an embodiment of a rights processing device based on an IoT device as follows:

[0087] In the above embodiments, a rights processing method based on an IoT device is provided, and correspondingly, a rights processing device based on an IoT device is also provided, which will be described below with reference to the accompanying drawings.

[0088] Reference Figure 5 This illustration shows a schematic diagram of an embodiment of a rights processing device based on an IoT device provided in this embodiment.

[0089] Since the apparatus embodiments correspond to the method embodiments, the descriptions are relatively simple. For relevant parts, please refer to the corresponding descriptions of the method embodiments provided above. The apparatus embodiments described below are merely illustrative.

[0090] This embodiment provides a rights processing device based on an IoT device, the device comprising:

[0091] The tag acquisition module 502 is configured to log in to the merchant's IoT device using the user's identity credentials and to acquire the user's identity tag and a third-party tag in the merchant's IoT device.

[0092] The tag conversion module 504 is configured to convert the third-party tags based on the tag mapping relationship to obtain the converted tags mapped by the third-party tags;

[0093] The matching module 506 is configured to match the identity tag and the conversion tag with the recommended benefits configured in the rights and benefits policy of the IoT device to obtain the user's target recommended benefits;

[0094] The rendering and display module 508 is configured to render the benefits based on the benefit template of the target recommended benefits, and display the rendered benefit recommendation page through the interactive screen of the IoT device.

[0095] This specification provides an embodiment of a rights processing device based on an IoT device as follows:

[0096] Corresponding to the above-described method for handling rights based on an IoT device, and based on the same technical concept, one or more embodiments of this specification also provide a device for handling rights based on an IoT device, which is used to execute the above-described method for handling rights based on an IoT device. Figure 6 This is a schematic diagram of the structure of an IoT-based rights processing device provided for one or more embodiments of this specification.

[0097] This embodiment provides a rights processing device based on an IoT device, comprising:

[0098] like Figure 6As shown, the rights processing device based on the IoT device can vary significantly due to differences in configuration or performance. It may include one or more processors 601 and a memory 602, where one or more applications or data may be stored. The memory 602 may be temporary or persistent storage. The applications stored in the memory 602 may include one or more modules (not shown), each module including a series of computer-executable instructions within the IoT device-based rights processing device. Furthermore, the processor 601 may be configured to communicate with the memory 602, executing the series of computer-executable instructions in the memory 602 on the IoT device-based rights processing device. The IoT device-based rights processing device may also include one or more power supplies 603, one or more wired or wireless network interfaces 604, one or more input / output interfaces 605, one or more keyboards 606, etc.

[0099] In one specific embodiment, the IoT-based rights processing device includes a memory and one or more programs, wherein the one or more programs are stored in the memory, and the one or more programs may include one or more modules, and each module may include a series of computer-executable instructions for the IoT-based rights processing device, and is configured to be executed by one or more processors. The one or more programs include computer-executable instructions for performing the following:

[0100] Log in to the merchant's IoT device using the user's identity credentials and obtain the user's identity tag and a third-party tag in the merchant's account;

[0101] Based on the tag mapping relationship, the third-party tags are transformed to obtain the transformed tags mapped from the third-party tags;

[0102] The identity tag and the conversion tag are matched with the recommended benefits configured in the rights and benefits policy of the IoT device to obtain the user's target recommended benefits;

[0103] The benefits are rendered based on the benefit template of the target recommended benefits, and the rendered benefit recommendation page is displayed on the interactive screen of the IoT device.

[0104] This specification provides an embodiment of a computer-readable storage medium as follows:

[0105] Corresponding to the above-described method for handling rights based on IoT devices, and based on the same technical concept, one or more embodiments of this specification also provide a computer-readable storage medium.

[0106] The computer-readable storage medium provided in this embodiment is used to store computer-executable instructions, which, when executed, implement the following process:

[0107] Log in to the merchant's IoT device using the user's identity credentials and obtain the user's identity tag and a third-party tag in the merchant's account;

[0108] Based on the tag mapping relationship, the third-party tags are transformed to obtain the transformed tags mapped from the third-party tags;

[0109] The identity tag and the conversion tag are matched with the recommended benefits configured in the rights and benefits policy of the IoT device to obtain the user's target recommended benefits;

[0110] The benefits are rendered based on the benefit template of the target recommended benefits, and the rendered benefit recommendation page is displayed on the interactive screen of the IoT device.

[0111] It should be noted that the embodiments of a computer-readable storage medium described in this specification and the embodiments of a method for processing the rights of an IoT device described in this specification are based on the same inventive concept. Therefore, the specific implementation of this embodiment can be referred to the implementation of the corresponding method described above, and the repeated parts will not be described again.

[0112] The various embodiments in this specification are described in a progressive manner. The same or similar parts between the various embodiments can be referred to each other. Each embodiment focuses on describing the differences from other embodiments. For example, the device embodiment, equipment embodiment and computer-readable storage medium embodiment are all similar to the method embodiment, so the description is relatively simple. When reading the relevant content of the device embodiment, equipment embodiment and computer-readable storage medium embodiment, please refer to the description of the method embodiment.

[0113] The foregoing has described specific embodiments of this specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims may be performed in a different order than that shown in the embodiments and may still achieve the desired result. Furthermore, the processes depicted in the drawings do not necessarily require the specific or sequential order shown to achieve the desired result. In some embodiments, multitasking and parallel processing are possible or may be advantageous.

[0114] In the 1930s, improvements to a technology could be clearly distinguished as either hardware improvements (e.g., improvements to the circuit structure of diodes, transistors, switches, etc.) or software improvements (improvements to the methodology). However, with technological advancements, many improvements to the methodology today can be considered direct improvements to the hardware circuit structure. Designers almost always obtain the corresponding hardware circuit structure by programming the improved methodology into the hardware circuit. Therefore, it cannot be said that an improvement to the methodology cannot be implemented using hardware physical modules. For example, a Programmable Logic Device (PLD) (such as a Field Programmable Gate Array (FPGA)) is such an integrated circuit whose logic function is determined by the user programming the device. Designers can program and "integrate" a digital system onto a PLD themselves, without needing chip manufacturers to design and manufacture dedicated integrated circuit chips. Furthermore, nowadays, instead of manually manufacturing integrated circuit chips, this programming is mostly implemented using "logic compiler" software. Similar to the software compiler used in program development, the original code before compilation must also be written in a specific programming language, called a Hardware Description Language (HDL). There are many HDLs, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, and RHDL (Ruby Hardware Description Language). Currently, the most commonly used are VHDL (Very-High-Speed ​​Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art should also understand that by simply performing some logic programming on the method flow using one of these hardware description languages ​​and programming it into an integrated circuit, the hardware circuit implementing the logical method flow can be easily obtained.

[0115] The controller can be implemented in any suitable manner. For example, it can take the form of a microprocessor or processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro)processor, logic gates, switches, application-specific integrated circuits (ASICs), programmable logic controllers, and embedded microcontrollers. Examples of controllers include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicon Labs C8051F320. A memory controller can also be implemented as part of the control logic of the memory. Those skilled in the art will also recognize that, in addition to implementing the controller in purely computer-readable program code form, the same functionality can be achieved by logically programming the method steps to make the controller take the form of logic gates, switches, application-specific integrated circuits, programmable logic controllers, and embedded microcontrollers. Therefore, such a controller can be considered a hardware component, and the means included therein for implementing various functions can also be considered as structures within the hardware component. Alternatively, the means for implementing various functions can be considered as both software modules implementing the method and structures within the hardware component.

[0116] The systems, devices, modules, or units described in the above embodiments can be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, a computer can be, for example, a personal computer, laptop computer, cellular phone, camera phone, smartphone, personal digital assistant, media player, navigation device, email device, game console, tablet computer, wearable device, or any combination of these devices.

[0117] For ease of description, the above apparatus is described by dividing it into various functional units. Of course, when implementing the embodiments of this specification, the functions of each unit can be implemented in one or more software and / or hardware.

[0118] Those skilled in the art will understand that one or more embodiments of this specification can be provided as a method, system, or computer program product. Therefore, one or more embodiments of this specification may take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this specification may take the form of a computer program product embodied on one or more computer-readable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0119] This specification is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this specification. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0120] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0121] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0122] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0123] Memory may include non-persistent storage in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

[0124] Computer-readable media include both permanent and non-permanent, removable and non-removable media that can store information using any method or technology. Information can be computer-readable instructions, data structures, program modules, or other data. Examples of computer-readable storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0125] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising at least one…" does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0126] One or more embodiments of this specification can be described in the general context of computer-executable instructions, such as program modules, that are executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc., that perform a particular task or implement a particular abstract data type. One or more embodiments of this specification can also be practiced in distributed computing environments where tasks are performed by remote processing devices connected via a communication network. In distributed computing environments, program modules can reside in local and remote computer storage media, including storage devices.

[0127] The above description is merely an embodiment of this document and is not intended to limit the scope of this document. Various modifications and variations can be made to this document by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this document should be included within the scope of the claims of this document.

Claims

1. A method for handling rights based on IoT devices, comprising: Log in to the merchant's dual-screen IoT device using the user's identity credentials, and obtain the user's identity tag and the third-party tag in the merchant's device; Based on the tag mapping relationship, the third-party tags are converted to obtain standardized tags mapped from the third-party tags; If the dual-screen IoT device is configured with multiple rights and interests policies, the identity tag and the standardized tag are matched with the recommended rights and interests configured by each rights and interests policy to obtain candidate recommended rights and interests, and the candidate recommended rights and interests that meet the priority conditions among the candidate recommended rights and interests are selected as the target recommended rights and interests. The benefits are rendered according to the benefit template of the target recommended benefits. The benefit reminder of the target recommended benefits is displayed on the merchant screen configured on the dual-screen IoT device, and the rendered benefit recommendation page is displayed on the user screen configured on the dual-screen IoT device.

2. The method for processing rights based on IoT devices according to claim 1, after the steps of rendering rights according to the rights template of the target recommended rights, displaying the rights reminder of the target recommended rights on the merchant screen configured on the dual-screen IoT device, and displaying the rendered rights recommendation page on the user screen configured on the dual-screen IoT device, further includes: If the rights control configured on the rights recommendation page is triggered, the target recommended rights are issued to the user; Based on the target recommendation benefits, the settlement amount of the user's pending orders on the dual-screen IoT device is calculated, and the order settlement is performed on the dual-screen IoT device according to the settlement amount.

3. The rights processing method based on IoT devices according to claim 1, wherein the rights processing method based on IoT devices is applied to the service components of the application deployed on the dual-screen IoT device.

4. The rights processing method based on IoT devices according to claim 3, wherein the user's identity credential login further includes any one of the following methods: Login with identity credentials by scanning the login identifier displayed on the user's screen using the application installed on the user's terminal; login with identity credentials by scanning the user identifier displayed on the application using the dual-screen IoT device; and login with identity credentials by recognizing the user's image collected by the dual-screen IoT device.

5. The rights processing method based on IoT devices according to claim 3, wherein obtaining the user's identity tag and the merchant's third-party tag includes: Call the identity tag interface of the service component to obtain the identity tag corresponding to the user's identity information in the application; Call the third-party tag interface of the service component to obtain the third-party tag associated with the user's user information under the merchant, and / or obtain the third-party tag corresponding to the user's consumption record under the merchant.

6. The rights processing method based on IoT devices according to claim 1, wherein converting the third-party tag based on the tag mapping relationship to obtain the standardized tag mapped by the third-party tag includes: Read the pre-configured tag mapping relationship of the merchant, and query the standardized tag of the third-party tag mapping in the read tag mapping relationship.

7. The method for processing rights based on IoT devices according to claim 1, wherein rendering rights according to the rights template of the target recommended rights includes: Based on the display parameters of the user screen and the benefit type of the target recommended benefit, determine the template parameters of the benefit template of the target recommended benefit, and obtain the rendering material corresponding to the target recommended benefit or the benefit type; The benefit recommendation page is rendered based on the benefit template, the template parameters, and the rendering materials, representing the target recommended benefit.

8. A rights processing device based on an IoT device, comprising: The tag acquisition module is configured to log in to the merchant's dual-screen IoT device using the user's identity credentials, and to acquire the user's identity tag and a third-party tag in the merchant's device. The tag conversion module is configured to convert the third-party tags based on the tag mapping relationship to obtain standardized tags mapped by the third-party tags; The matching module is configured to, if the dual-screen IoT device is configured with multiple rights and interests policies, match the identity tag and the standardized tag with the recommended rights and interests configured by each rights and interests policy respectively to obtain candidate recommended rights and interests, and select the candidate recommended rights and interests whose priority meets the preset conditions as the target recommended rights and interests. The rendering and display module is configured to render the benefits based on the benefit template of the target recommended benefits, display the benefit reminder of the target recommended benefits on the merchant screen configured on the dual-screen IoT device, and display the rendered benefit recommendation page on the user screen configured on the dual-screen IoT device.

9. A rights processing device based on an IoT device, comprising: processor; And, a memory configured to store computer-executable instructions, which, when executed, cause the processor to: Log in to the merchant's dual-screen IoT device using the user's identity credentials, and obtain the user's identity tag and the third-party tag in the merchant's device; Based on the tag mapping relationship, the third-party tags are converted to obtain standardized tags mapped from the third-party tags; If the dual-screen IoT device is configured with multiple rights and interests policies, the identity tag and the standardized tag are matched with the recommended rights and interests configured by each rights and interests policy to obtain candidate recommended rights and interests, and the candidate recommended rights and interests that meet the priority conditions among the candidate recommended rights and interests are selected as the target recommended rights and interests. The benefits are rendered according to the benefit template of the target recommended benefits. The benefit reminder of the target recommended benefits is displayed on the merchant screen configured on the dual-screen IoT device, and the rendered benefit recommendation page is displayed on the user screen configured on the dual-screen IoT device.

10. A computer-readable storage medium for storing computer-executable instructions that, when executed, implement the steps of the method of claim 1.

Images