Points collection method, device and storage medium

Abstract

The present invention provides a method, device and storage medium for collecting points; the method comprises: receiving service points of a corresponding target user pushed by different service systems, the service points being used to represent the service rights and interests provided by the corresponding service system to the target user; presenting the service points pushed by each service system and the collection status of each service point respectively; in response to a collection instruction for the service points, collecting the service points pushed by at least two service systems to the point account of the target user; and updating the collection status corresponding to the collected service points. Through the present invention, users can quickly collect points scattered in discrete point systems.

Description

1.1.1 Technical Field

[0002] The present invention relates to the field of Internet technology, and in particular to a method, device and storage medium for collecting points. 1.1.2 Background Technology

[0004] With the continuous development of the times, the rapid advancement of science and technology, and the continuous improvement of people's economic level, businesses will reward users with points in order to maintain customer groups and increase user stickiness, so as to increase user consumption enthusiasm.

[0005] However, in a discrete points system, points are obtained in many independent ways. Users need to find the corresponding items to collect points one by one to complete the collection of points. The operation of collecting points is very cumbersome and the user experience is poor. 1.1.3 Summary of the invention

[0007] The embodiments of the present invention provide a method, device and storage medium for collecting points, which can enable a user to quickly collect points dispersed in a discrete points system.

[0008] The technical solution of the embodiment of the present invention is achieved as follows:

[0009] An embodiment of the present invention provides a method for collecting points, including:

[0010] Receive service credits of corresponding target users pushed by different service systems, where the service credits are used to represent the service rights and interests provided by the corresponding service systems to the target users;

[0011] Respectively presenting the service points pushed by each service system and the claiming status of each corresponding service point;

[0012] In response to a claim instruction for the service points, claim the service points pushed by at least two of the service systems to a point account of the target user;

[0013] Update the claim status of the claimed service points.

[0014] In the above scheme, the method further comprises:

[0015] Generate a claim record corresponding to the claimed service points;

[0016] Performing a hash transformation on the claim record to obtain summary information corresponding to the claim record;

[0017] The summary information is stored in the blockchain network.

[0018] An embodiment of the present invention provides a device for collecting points, including:

[0019] A receiving module, used to receive service credits of corresponding target users pushed by different service systems, where the service credits are used to represent the service rights and interests provided by the corresponding service system to the target users;

[0020] A presentation module, used to present the service points pushed by each service system and the claiming status of each service point;

[0021] a receiving module, configured to receive the service points pushed by at least two of the service systems to the point account of the target user in response to a receiving instruction for the service points;

[0022] The update module is used to update the collection status corresponding to the collected service points.

[0023] In the above solution, the receiving module is further used to receive the service points corresponding to the target user pushed by different service systems when determining that the point task status corresponding to the target user is completed; or,

[0024] Receive service points corresponding to the target user pushed by different service systems based on the user profile of the target user.

[0025] In the above solution, the receiving module is further used to respond to the receiving instruction for the service points and collect the service points pushed by each service system to the point account of the target user.

[0026] In the above solution, the receiving module is further used to determine the service points pushed by at least two service systems selected by the target user;

[0027] In response to the instruction to collect the service points, the service points pushed by the selected at least two service systems are collected into the point account of the target user.

[0028] In the above solution, the claiming module is further used to obtain the remaining storage amount of the target user's points account in response to the claiming instruction for the service points;

[0029] When it is determined that the total amount of the service points pushed by different service systems is greater than the remaining storage amount, obtaining the first push time corresponding to the service points pushed by each of the service systems;

[0030] Based on the order of the first push times corresponding to the service points pushed by each of the service systems, the service points pushed by at least two of the service systems are collected into the points account of the target user, so that the number of points in the points account of the target user matches the storage limit of the points account.

[0031] In the above solution, the claiming module is further used to obtain the second push time corresponding to the service points whose claiming status is unclaimed;

[0032] When it is determined that the interval between the second push time and the current time reaches a preset time threshold, the service points in the collection status of uncollected are collected to the point account of the target user.

[0033] In the above solution, the receiving module is further used to receive the service points corresponding to the target user pushed by the target service system;

[0034] Obtaining the service points claiming record corresponding to the target user;

[0035] When it is determined based on the service point claiming record that there is a service point claiming record corresponding to the target service system, the service points pushed by the target service system are claimed to the point account of the target user.

[0036] In the above solution, the device further comprises: a prompt module, which is used to respectively obtain the collection time and validity period of the service points pushed by different service systems in the target account;

[0037] Based on the collection time and the validity period, prompt information is presented, and the prompt information is used to prompt the validity status of the service points.

[0038] In the above solution, the device further includes: a storage module for respectively obtaining the collection time and validity period of the service points pushed by different service systems in the target account;

[0039] Based on the collection time and the validity period, prompt information is presented, and the prompt information is used to prompt the validity status of the service points.

[0040] An embodiment of the present invention provides a terminal, including:

[0041] A memory for storing executable instructions;

[0042] The processor is used to implement the method for collecting points provided in an embodiment of the present invention when executing the executable instructions stored in the memory.

[0043] An embodiment of the present invention provides a storage medium storing executable instructions for causing a processor to execute the method for collecting points provided by the embodiment of the present invention.

[0044] The embodiments of the present invention have the following beneficial effects:

[0045] The present invention receives service points of corresponding target users pushed by different service systems, and in response to a collection instruction for the service points, collects the service points pushed by at least two service systems into the points account of the target user. In this way, since the service points pushed by different service systems are integrated, it is possible to collect the service points pushed by multiple service systems based on one collection instruction of the user without having to collect them one by one, so that the user can quickly collect the points scattered in discrete point systems, thereby improving the user experience. 1.1.4 Description of the Figures

[0047] Figure 1 A schematic diagram of collecting points provided for related technologies;

[0048] Figure 2A-2B A schematic diagram of an interface for collecting points provided for related technologies;

[0049] Figure 3 A schematic diagram of the architecture of a points claiming system 100 provided in an embodiment of the present invention;

[0050] Figure 4 A schematic diagram of the structure of a terminal 400 provided in an embodiment of the present invention;

[0051] Figure 5 A schematic diagram of a flow chart of a method for collecting points provided in an embodiment of the present invention;

[0052] Figure 6A-6B A schematic diagram of an interface for collecting points provided in an embodiment of the present invention;

[0053] Figure 7 A schematic diagram of collecting points provided in an embodiment of the present invention;

[0054] Figure 8 A schematic diagram of an interface for collecting points provided in an embodiment of the present invention;

[0055] Fig. 9 A schematic diagram of an interface for collecting points provided in an embodiment of the present invention;

[0056] Fig.10 A schematic diagram of the application architecture of the blockchain network provided by an embodiment of the present invention;

[0057] Fig.11 A schematic diagram of the structure of a blockchain in a blockchain network 600 provided in an embodiment of the present invention;

[0058] Fig.12 A schematic diagram of the functional architecture of a blockchain network 600 provided in an embodiment of the present invention;

[0059] Fig.13A schematic diagram of a flow chart of a method for collecting points provided in an embodiment of the present invention;

[0060] Fig.14 A schematic diagram of a flow chart of a method for collecting points provided in an embodiment of the present invention;

[0061] Fig.15 A schematic diagram of a flow chart of a method for collecting points provided in an embodiment of the present invention;

[0062] Fig.16 A schematic diagram of the composition structure of the points collection device 455 provided in an embodiment of the present invention. 1.1.5 Specific implementation methods

[0064] In order to make the purpose, technical solutions and advantages of the present invention clearer, the present invention will be further described in detail below in conjunction with the accompanying drawings. The described embodiments should not be regarded as limiting the present invention. All other embodiments obtained by ordinary technicians in the field without making creative work are within the scope of protection of the present invention.

[0065] In the following description, reference is made to “some embodiments”, which describe a subset of all possible embodiments, but it can be understood that “some embodiments” may be the same subset or different subsets of all possible embodiments and may be combined with each other without conflict.

[0066] In the following description, the terms "first\second\third" involved are merely used to distinguish similar objects and do not represent a specific ordering of the objects. It can be understood that "first\second\third" can be interchanged with a specific order or sequence where permitted, so that the embodiments of the present invention described herein can be implemented in an order other than that illustrated or described herein.

[0067] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as those commonly understood by those skilled in the art to which the present invention belongs. The terms used herein are only for the purpose of describing the embodiments of the present invention and are not intended to limit the present invention.

[0068] Before further describing the embodiments of the present invention in detail, the nouns and terms involved in the embodiments of the present invention are described. The nouns and terms involved in the embodiments of the present invention are subject to the following interpretations.

[0069] 1) Points are used to represent the service rights and interests provided to users. In some embodiments, points can be rewards in any form for users who complete corresponding tasks (i.e., use corresponding services), such as points after completing a recharge task, virtual currency after completing a game task, energy value after completing a green travel task, etc.; in other embodiments, points can also be virtual assets in any form that are actively pushed to users, such as coupons and game props that merchants actively push to users; in actual applications, users can use the points they have obtained to redeem actual / virtual items of corresponding value, such as daily necessities and game equipment of corresponding value; or, users can also use the points they have obtained to redeem corresponding permissions, such as corresponding membership permissions (such as upgrading to a super member) and corresponding levels (such as upgrading game levels).

[0070] 2) In response, it is used to indicate the conditions or states on which the executed operation depends. When the dependent conditions or states are met, one or more operations executed may be in real time or with a set delay. Unless otherwise specified, there is no restriction on the order in which the multiple operations executed are executed;

[0071] 3) User portraits, including user interest portraits and user basic portraits; among them,

[0072] User interest portrait refers to a virtual representation of a real user. It is a target user model based on a series of attribute data and is used to indicate the user's interest classification.

[0073] User basic portrait is a labeled picture of the user's information abstracted from the user's real gender, age, permanent login location and other basic information.

[0074] In order to realize the point collection in a discrete system, the related technology provides a method of completing the point collection in sequence according to the items. Figure 1 A schematic diagram of collecting points provided for related technology, see Figure 1 Each entry that can collect points corresponds to a collect button. If you need to collect all points, you need to click the collect button corresponding to each entry in turn.

[0075] Take completing tasks to earn points as an example. Figure 2A-2B A schematic diagram of an interface for collecting points provided for related technologies, see Figure 2A The interface presents the task items for which points can be obtained and the corresponding claim buttons for the task items. By clicking the claim button, the points corresponding to the task are claimed. For example, by clicking the claim button corresponding to "fill in your birthday date", the terminal deposits the 7 points corresponding to "fill in your birthday date" into the user's account, and then presents a prompt indicating that the points have been claimed successfully. See Figure 2B, "+7" is displayed to prompt the user that 7 points have been collected. If you need to collect the points corresponding to "Set your own automatic recharge", you need to click the corresponding collection button of "Set your own automatic recharge". In this way, as the number of tasks that can collect points increases, the number of points collected by users will also increase.

[0076] Based on this, a method for collecting points according to an embodiment of the present invention is proposed, which receives service points of a corresponding target user pushed by different service systems, and in response to a collection instruction for the service points, collects the service points pushed by at least two service systems to the point account of the target user; in this way, since the service points pushed by different service systems are integrated, it is possible to collect the service points pushed by multiple service systems based on one collection instruction of the user without having to collect them one by one, so that the user can quickly collect the points scattered in discrete point systems, thereby improving the user experience.

[0077] See also Figure 3 , Figure 3 The present invention provides an embodiment of the present invention. The service points collection system 100 is a schematic diagram of the architecture. To support an exemplary application, the service points collection module 300 is connected to multiple service systems 200 via a network (service system 200-1, service system 200-2 and service system 200-N are shown as examples). The service points collection module can be deployed as an independent electronic device or in a terminal 400. The network can be a wide area network or a local area network, or a combination of the two.

[0078] The service system 200 is used to push the service points of the corresponding target users;

[0079] The service credit acquisition module 300 is used to acquire the service credits of the corresponding target users pushed by different service systems and send them to the terminal 400;

[0080] Terminal 400 is used to receive service points of a corresponding target user pushed by different service systems; present the service points pushed by each service system and the collection status of each service point respectively; in response to a collection instruction for service points, collect the service points pushed by at least two service systems to the point account of the target user; and update the collection status corresponding to the collected service points.

[0081] In actual applications, terminal 400 can be various types of user terminals such as a smart phone, a tablet computer, a laptop computer, etc., and can also be a wearable computing device, a personal digital assistant (PDA), a desktop computer, a cellular phone, a media player, a navigation device, a game console, a television, or a combination of any two or more of these data processing devices or other data processing devices.

[0082] See also Figure 4 , Figure 4 is a schematic diagram of the structure of a terminal 400 provided in an embodiment of the present invention, Figure 4 The terminal 400 shown includes: at least one processor 410, a memory 450, at least one network interface 420 and a user interface 430. The various components in the terminal 400 are coupled together via a bus system 440. It is understood that the bus system 440 is used to achieve connection and communication between these components. In addition to the data bus, the bus system 440 also includes a power bus, a control bus and a status signal bus. However, for the sake of clarity, the bus system 440 is not shown in FIG. Figure 4 Various buses are labeled as bus system 440 .

[0083] The processor 410 may be an integrated circuit chip having signal processing capabilities, such as a general-purpose processor, a digital signal processor (DSP), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc., wherein the general-purpose processor may be a microprocessor or any conventional processor, etc.

[0084] The user interface 430 includes one or more output devices 431 that enable presentation of media content, including one or more speakers and / or one or more visual display screens. The user interface 430 also includes one or more input devices 432, including user interface components that facilitate user input, such as a keyboard, mouse, microphone, touch screen display, camera, other input buttons and controls.

[0085] The memory 450 may be removable, non-removable, or a combination thereof. Exemplary hardware devices include solid-state memory, hard disk drives, optical disk drives, etc. The memory 450 may optionally include one or more storage devices that are physically remote from the processor 410.

[0086] The memory 450 includes a volatile memory or a non-volatile memory, and may also include both volatile and non-volatile memories. The non-volatile memory may be a read-only memory (ROM), and the volatile memory may be a random access memory (RAM). The memory 450 described in the embodiment of the present invention is intended to include any suitable type of memory.

[0087] In some embodiments, memory 450 can store data to support various operations, examples of which include programs, modules, and data structures, or a subset or superset thereof, as exemplarily described below.

[0088] Operating system 451, including system programs for processing various basic system services and performing hardware-related tasks, such as a framework layer, a core library layer, a driver layer, etc., for implementing various basic services and processing hardware-based tasks;

[0089] A network communication module 452, used to reach other computing devices via one or more (wired or wireless) network interfaces 420, exemplary network interfaces 420 include: Bluetooth, Wireless Authentication (WiFi), and Universal Serial Bus (USB);

[0090] a presentation module 453 for enabling presentation of information via one or more output devices 431 (e.g., display screen, speaker, etc.) associated with the user interface 430 (e.g., a user interface for operating peripherals and displaying content and information);

[0091] The input processing module 454 is used to detect one or more user inputs or interactions from one of the one or more input devices 432 and translate the detected inputs or interactions.

[0092] In some embodiments, the device provided by the embodiments of the present invention can be implemented in software. Figure 4 A device 455 for collecting points stored in a memory 450 is shown, which may be software in the form of a program or plug-in, including the following software modules: a receiving module 4551, a presenting module 4552, a collecting module 4553, and an updating module 4554. These modules are logical and can therefore be arbitrarily combined or further split according to the functions implemented.

[0093] The functions of each module will be described below.

[0094] In other embodiments, the points collection device provided in the embodiments of the present invention may be implemented in hardware. As an example, the device provided in the embodiments of the present invention may be a processor in the form of a hardware decoding processor, which is programmed to execute the points collection method provided in the embodiments of the present invention. For example, the processor in the form of a hardware decoding processor may adopt one or more application specific integrated circuits (ASICs), DSPs, programmable logic devices (PLDs), complex programmable logic devices (CPLDs), field programmable gate arrays (FPGAs) or other electronic components.

[0095] The method for claiming points provided by the embodiment of the present invention will be described in conjunction with the exemplary application and implementation of the terminal provided by the embodiment of the present invention. Figure 5 , Figure 5 is a flow chart of the method for collecting points provided in an embodiment of the present invention, which will be combined with Figure 5 The steps shown are explained.

[0096] Step 501: The terminal receives service points of corresponding target users pushed by different service systems.

[0097] Here, service points are used to represent the service rights and interests provided by the corresponding service system to the target user. Service points can be virtual assets such as membership points, coupons, game coins, etc., which can be used to exchange rights and interests of corresponding value. It should be noted that the service system is the source of service points and can be any system that provides services to the target user, such as a recharge service system, a payment service system, a shopping service system, etc.

[0098] In actual implementation, the terminal receives the service points of the corresponding target user pushed by different service systems within a period of time, that is, the terminal can receive the service points pushed by different service systems at different times within a period of time.

[0099] In some embodiments, the terminal may receive service points in the following manner: the terminal receives service points of the corresponding target user pushed by different service systems when it is determined that the point task status corresponding to the target user is completed; or, receives service points of the corresponding target user pushed by different service systems based on the user portrait of the target user.

[0100] In actual implementation, the service system can pre-set point tasks and push corresponding service points when the target user completes the point tasks; the service system can also actively push service points to the target user, such as pushing service points corresponding to the target user based on the user portrait of the target user.

[0101] In some embodiments, users can complete the point task corresponding to the service system through the service system. When the target user completes the corresponding point task through the service system, the service system will push the service points of the corresponding point task. For example, if the point task is "recharge 100 yuan of phone bill", then after the target user uses the recharge system to complete the recharge of 100 yuan of phone bill, the recharge service system will push the corresponding service points of "recharge 100 yuan of phone bill" to the target user's terminal.

[0102] In some embodiments, the user portrait may include at least one of the following: user interest portrait, user basic portrait. Taking the user portrait including the user interest portrait and the user basic portrait as an example, in actual implementation, the service system pushes corresponding service points to the target user based on the user interest portrait and the user basic portrait. For example, when it is determined that the target user is a 21-year-old female who likes painting, the shopping service system pushes coupons for purchasing paint to the target user.

[0103] Step 502: The service points pushed by each service system and the claiming status of each corresponding service point are presented respectively.

[0104] In actual implementation, the terminal can present the service points pushed by the service system and the collection status of each service point in the graphical interface for collecting points, so that the target user can perform corresponding collection operations according to the presented service points and the corresponding collection status.

[0105] In some embodiments, the terminal may first present an operation button for claiming service credits in a graphical interface to prompt the user that there are service credits available for claiming; after receiving a user click on the operation button, the terminal presents the service credits pushed by the service system and the claim status of each service credit in the graphical interface. Figure 6A-6B A schematic diagram of the interface for collecting points provided in an embodiment of the present invention, see Figure 6A-6B The terminal presents a floating button of "get points" in the graphical interface. After receiving a click operation of the user on the floating button of "get points", the terminal presents the service points pushed by the service system and the collection status of each service point.

[0106] In other embodiments, after the user enters the graphical interface for collecting points, the service points pushed by the service system and the collection status of each service point are directly presented in the graphical interface.

[0107] Step 503: In response to the instruction to collect the service points, the service points pushed by at least two service systems are collected into the point account of the target user.

[0108] In actual implementation, the terminal can present an operation button for collecting service points. The target user triggers an instruction to collect service points by clicking the operation button. Based on the instruction to collect service points, the terminal collects the service points pushed by at least two service systems to the target user's points account. Figure 7 For a schematic diagram of receiving points provided in an embodiment of the present invention, see Figure 7 The service points pushed by multiple service systems correspond to the same "receive" operation button, that is, by receiving the user's click operation on the "receive" operation button, the service points pushed by the corresponding multiple service systems are received to the target user's point account.

[0109] In some embodiments, the terminal may realize the collection of points in the following manner: in response to the collection instruction for service points, the terminal collects the service points pushed by each service system to the point account of the target user.

[0110] In actual implementation, the terminal can present an operation button for collecting all service points that are available for collection. By clicking the operation button, the user triggers the collection instruction for all service points that are available for collection, and collects the service points pushed by each service system to the target user's points account. In this way, the user only needs one click to collect all points, which improves the user experience.

[0111] For example, see Figure 6B The terminal has an "One-click Collection" operation button in the graphical interface. Users can click "One-click Collection" to collect the service points pushed by the service system presented in the graphical interface to the target user's points account.

[0112] In some embodiments, the terminal can realize the collection of points in the following manner: the terminal determines the service points pushed by at least two service systems selected by the target user; in response to the instruction to collect the service points, the service points pushed by the selected at least two service systems are collected to the target user's points account.

[0113] In some embodiments, the terminal may add a selection button in the service points graphical interface presented by each service system push, for the user to select the service points they need to collect; in other embodiments, the terminal may present a filter box in the graphical interface for the user to filter the service points by entering filter conditions.

[0114] For example, see Figure 8 , Figure 8 This is a schematic diagram of an interface for collecting points provided in an embodiment of the present invention. The terminal sets a selection button for each service point pushed by a service system. The user selects the service points to be collected by clicking the selection button. If the user needs to collect all service points, the user can click the select all button. The terminal determines the service points pushed by at least two service systems selected by the user based on the user's click operation on each selection button.

[0115] In this way, more choices can be provided to users. For example, some service points may not be needed by users, so users can choose not to collect them; or some service points have a validity period, and users can choose to collect them when they need them.

[0116] In some embodiments, the terminal can implement the collection of points in the following ways: in response to an instruction to collect service points, obtain the remaining storage limit of the target user's points account; when it is determined that the total amount of service points pushed by different service systems is greater than the remaining storage limit, obtain the first push time corresponding to the service points pushed by each service system; based on the order of the first push time corresponding to the service points pushed by each service system, collect the service points pushed by at least two service systems to the target user's points account, so that the number of points in the target user's points account matches the storage limit of the points account.

[0117] In actual implementation, a storage limit can be set for the points account, that is, the number of points collected cannot exceed the storage limit. For example, if the storage limit is 1000, then the points account can only store 1000 points at most. If the total amount of service points pushed by different service systems is greater than the remaining storage limit, only part of the service points can be collected. For example, if the remaining balance of the points account is 400 points, and the total amount of points that can be collected is 500, then the target user can only collect 400 points.

[0118] Then, when the terminal determines that the total amount of service points pushed by different service systems is greater than the remaining storage amount, the terminal can give priority to receiving the service points with the earlier push time according to the first push time corresponding to the service points pushed by each service system. For example, the push time corresponding to "recharge 100 yuan of phone bill" is 2019-3-12 12:40, and the number of points is 100 points; the push time corresponding to "purchase rights package" is 2019-3-12 17:40, and the number of points is 300 points; the push time corresponding to "set recharge reminder" is 2019-3-114 10:20, and the number of points is 200 points; the push time corresponding to "purchase tickets" is 2019-3-15 18:50, and the number of points is 500 points. The remaining points amount is 500 points, then the service points corresponding to "recharge 100 yuan of phone bill" and "purchase rights package" are collected.

[0119] In some embodiments, when the terminal determines that the total amount of service points pushed by different service systems is greater than the remaining storage limit, it can also give priority to receiving service points that match the user's interests based on the user portrait of the target user; or, based on the target user's historical collection record, give priority to receiving service points pushed by the service system that the user has collected.

[0120] Step 504: Update the receipt status corresponding to the received service points.

[0121] In actual implementation, the terminal will change the collection status corresponding to the collected service points to "collected", thereby completing a valid points collection operation to avoid repeated collection of points.

[0122] In some embodiments, after updating the claim status corresponding to the claimed service points, the terminal may present a prompt message indicating successful claim in the graphical interface, for example, Fig. 9 A schematic diagram of an interface for collecting points provided in an embodiment of the present invention, wherein Fig. 9 After updating the receipt status corresponding to the received service points, a prompt message of "+800" is presented to prompt the user that 800 points have been received.

[0123] In some embodiments, for service points that the user has not collected for a long time, the terminal can automatically collect them: obtain the second push time corresponding to the service points with a collection status of uncollected; when it is determined that the interval between the second push time and the current time reaches a preset time threshold, the service points with a collection status of uncollected will be collected to the target user's points account.

[0124] In actual implementation, the preset time threshold can be set by the target user through the terminal, or it can be set by the terminal by default, that is, from the time the service points are pushed to the terminal, if the target user has not claimed them within the preset time, the terminal will automatically claim the service points to the target user's points account. For example, the preset time threshold can be set to one week, that is, from the time the service points are pushed to the terminal, if the target user has not claimed them within one week, the terminal will automatically claim them to the target user's points account. In this way, when the user forgets to claim the service points, they can be automatically claimed for the target user.

[0125] In some embodiments, a time for automatically claiming service credits can be preset, and when the time matches the time for automatically claiming service credits, the terminal will claim the service credits that are in the unclaimed state to the credit account of the target user. The preset time can be a periodic time, such as every Friday, so the terminal performs the automatic claiming operation every Friday and claims the service credits that are in the unclaimed state to the credit account of the target user.

[0126] In some embodiments, after the service points pushed by at least two service systems are collected into the points account of the target user, the terminal can automatically collect the service points: receive the service points of the corresponding target user pushed by the target service system; obtain the service points collection record corresponding to the target user; based on the service points collection record, when it is determined that there is a service points collection record for the corresponding target service system, collect the service points pushed by the target service system into the points account of the target user.

[0127] In actual implementation, after the service points pushed by at least two of the service systems are collected into the points account of the target user, when the terminal receives the service points of the corresponding target user pushed by the target service system, it will determine whether the service points pushed by the target service system have been collected based on the service points collection record of the target user. If so, the service points pushed by the target service system will be automatically collected into the points account of the target user; otherwise, the collection operation will not be performed until the collection instruction of the target user is received, and then the service points pushed by the target service system will be collected into the points account of the target user.

[0128] Here, the service points of the target user pushed by the target service system refer to the newly received service points after the collection operation is executed according to the user's collection instruction. The service points collection record is to record the relevant information of the received service points after each collection operation is executed by the terminal, including the service system corresponding to the service points, the push time, the collection time, etc.

[0129] In some embodiments, the terminal can collect points that match the user profile of the target user according to the user profile of the target user. Taking the user profile including the user interest profile and the user basic profile as an example, in actual implementation, according to the user interest profile and the user basic profile, the target user collects the service points pushed by the corresponding service system.

[0130] In some embodiments, the terminal can also obtain the collection time and validity period of the service points pushed by different service systems in the target account respectively; based on the collection time and validity period, present prompt information, which is used to prompt the validity status of the service points.

[0131] In actual implementation, points have an effective period for redemption, that is, after the effective period, the points cannot be redeemed for corresponding rights and interests. Here, the terminal obtains the collection time and effective period of the service points. When the service points are about to expire, a prompt message can be presented to prompt the user to use the corresponding service points as soon as possible. In this way, the expiration of service points can be avoided and the user experience can be improved.

[0132] In some embodiments, the terminal can also generate a receipt record corresponding to the service points received and store it in the blockchain network: generate a receipt record corresponding to the service points received; perform a hash transformation on the receipt record to obtain summary information of the corresponding receipt record; and store the summary information in the blockchain network.

[0133] Here, the embodiment of the present invention can also be combined with blockchain technology. After generating the collection record of the corresponding service points collected, a transaction for storing the collection record of the corresponding service points collected is generated, and the generated transaction is submitted to the node of the blockchain network, so that the node stores the collection record of the corresponding service points collected to the blockchain network after consensus on the transaction; before storing it in the blockchain network, the terminal can also obtain the summary information of the corresponding collection record for the collection record of the service points; and store the obtained summary information of the corresponding collection record in the blockchain network. Through the above method, the collection record is prevented from being tampered with, and the security of the user's points account is improved.

[0134] See also Fig.10 , Fig.10 The schematic diagram of the application architecture of the blockchain network provided for the embodiment of the present invention includes a business entity 400, an authentication center 500, and a blockchain network 600 (consensus nodes 610-1 to consensus nodes 610-3 are shown as an example), which are described below respectively.

[0135] The types of blockchain network 600 are flexible and diverse, for example, it can be any one of public chain, private chain or alliance chain. Taking the public chain as an example, any electronic device of the business subject, such as user terminal and server, can access the blockchain network 600 without authorization; taking the alliance chain as an example, after the business subject obtains authorization, its subordinate electronic devices (such as terminals / servers) can access the blockchain network 600, and at this time, it becomes a client node in the blockchain network 600.

[0136] In some embodiments, the client node can only be used as an observer of the blockchain network 600, that is, to provide support for business entities to initiate transactions (for example, for storing data on the chain or querying data on the chain). For the functions of the consensus node 610 of the blockchain network 600, such as sorting function, consensus service and account book function, the client node can implement them by default or selectively (for example, depending on the specific business needs of the business entity). Thus, the data and business processing logic of the business entity can be migrated to the blockchain network 600 to the greatest extent, and the credibility and traceability of the data and business processing process can be achieved through the blockchain network 600.

[0137] The consensus node in the blockchain network 600 receives transactions submitted by the client node of the business entity 400, executes the transactions to update the ledger or query the ledger, and various intermediate results or final results of the executed transactions can be returned to the client node of the business entity for display.

[0138] For example, the client node 410 can subscribe to events of interest in the blockchain network 600, such as transactions occurring in a specific organization / channel in the blockchain network 600, and the consensus node 610 pushes corresponding transaction notifications to the client node 410, thereby triggering the corresponding business logic in the client node 410.

[0139] The following uses the example of a business entity accessing a blockchain network to redeem points to illustrate an exemplary application of blockchain.

[0140] See also Fig.10 The business subject 400 involved in the points collection registers with the authentication center 500 to obtain a digital certificate. The digital certificate includes the public key of the business subject and the digital signature signed by the authentication center 500 on the public key and identity information of the business subject. It is used to attach to the transaction together with the digital signature of the business subject for the transaction and is sent to the blockchain network so that the blockchain network can take out the digital certificate and signature from the transaction, verify the reliability of the message (i.e., whether it has not been tampered with) and the identity information of the business subject who sent the message. The blockchain network will verify based on the identity, such as whether it has the authority to initiate the transaction. The client running on the electronic device (such as a terminal or server) under the jurisdiction of the business subject can request access to the blockchain network 600 and become a client node.

[0141] The client node 410 of the business entity 400 is used to collect points, for example, to receive service points of the corresponding target user pushed by different service systems, and the service points are used to represent the service rights and interests provided by the corresponding service system to the target user; to present the service points pushed by each of the service systems and the collection status of each of the service points respectively; to collect the service points pushed by at least two of the service systems to the point account of the target user in response to the collection instruction for the service points; to update the collection status corresponding to the collected service points; to generate a collection record corresponding to the collected service points; and to send the collection record to the blockchain network 600.

[0142] Among them, the operation of sending the collection record to the blockchain network 600 can be pre-set in the client node 410 business logic, when the collection record corresponding to the collected service points is generated, the client node 310 automatically sends the collection record to the blockchain network 600, or the business personnel of the business entity 400 can log in to the client node 410, manually pack the collection record, and send it to the blockchain network 600. When sending, the client node 410 generates a transaction corresponding to the storage operation according to the collection record corresponding to the collected service points, and specifies the smart contract to be called to implement the storage operation and the parameters passed to the smart contract in the transaction. The transaction also carries the digital certificate of the client node 410, the signed digital signature (for example, the summary of the transaction is encrypted using the private key in the digital certificate of the client node 410), and broadcasts the transaction to the consensus node 610 in the blockchain network 600.

[0143] When the consensus node 610 in the blockchain network 600 receives a transaction, it verifies the digital certificate and digital signature carried in the transaction. After successful verification, it confirms whether the business subject 400 has transaction authority based on the identity of the business subject 400 carried in the transaction. Any verification judgment in the digital signature and authority verification will cause the transaction to fail. After successful verification, the node 610 signs its own digital signature (for example, using the private key of node 610-1 to encrypt the summary of the transaction) and continues to broadcast in the blockchain network 600.

[0144] After receiving the successfully verified transaction, the consensus node 610 in the blockchain network 600 fills the transaction into a new block and broadcasts it. When the consensus node 610 in the blockchain network 600 broadcasts a new block, it will perform a consensus process on the new block. If the consensus is successful, the new block will be appended to the end of the blockchain stored by itself, and the state database will be updated according to the result of the transaction, and the transaction in the new block will be executed: for the transaction submitted to update the collection record, the collection record will be added to the state database.

[0145] As an example of blockchain, see Fig.11 , Fig.11 The schematic diagram of the structure of the blockchain in the blockchain network 600 provided in the embodiment of the present invention is that the header of each block can include the hash value of all transactions in the block, and also includes the hash value of all transactions in the previous block. The newly generated transaction records are filled into the block and after the consensus of the nodes in the blockchain network, they will be appended to the end of the blockchain to form a chain growth. The chain structure between blocks based on hash values ​​ensures the anti-tampering and anti-counterfeiting of transactions in the block.

[0146] The following describes an exemplary functional architecture of a blockchain network provided by an embodiment of the present invention. Fig.10 , Fig.12 The functional architecture diagram of the blockchain network 600 provided for an embodiment of the present invention includes an application layer 601, a consensus layer 602, a network layer 603, a data layer 604 and a resource layer 605, which are described below respectively.

[0147] The resource layer 605 encapsulates the computing resources, storage resources, and communication resources of each node 610 in the blockchain network 600.

[0148] The data layer 604 encapsulates various data structures for implementing the ledger, including the blockchain implemented as files in the file system, the key-value state database, and the existence proof (such as the hash tree of transactions in the block).

[0149] The network layer 603 encapsulates the functions of point-to-point (P2P) network protocol, data transmission mechanism and data verification mechanism, access authentication mechanism and business subject identity management.

[0150] Among them, the P2P network protocol realizes the communication between nodes 610 in the blockchain network 600, the data propagation mechanism ensures the propagation of transactions in the blockchain network 600, and the data verification mechanism is used to realize the reliability of data transmission between nodes 610 based on cryptographic methods (such as digital certificates, digital signatures, public / private key pairs); the access authentication mechanism is used to authenticate the identity of the business subject joining the blockchain network 600 according to the actual business scenario, and grant the business subject the right to access the blockchain network 600 when the authentication is passed; the business subject identity management is used to store the identity of the business subject allowed to access the blockchain network 600, and the authority (such as the type of transaction that can be initiated).

[0151] The consensus layer 602 encapsulates the mechanism (i.e., consensus mechanism) for the nodes 610 in the blockchain network 600 to reach consensus on blocks, transaction management, and account management functions. The consensus mechanism includes consensus algorithms such as POS, POW, and DPOS, and supports pluggable consensus algorithms.

[0152] Transaction management is used to verify the digital signature carried in the transaction received by the verification node 610, verify the identity information of the business subject, and determine whether it has the authority to conduct transactions based on the identity information (read relevant information from the business subject identity management); for business subjects that have obtained authorization to access the blockchain network 600, they all have digital certificates issued by the certification center. The business subject uses the private key in its own digital certificate to sign the submitted transaction, thereby declaring its legal identity.

[0153] Ledger management is used to maintain the blockchain and state database. For the blocks that have reached consensus, they are appended to the end of the blockchain; the transactions in the blocks that have reached consensus are executed, and when the transaction includes an update operation, the key-value pairs in the state database are updated; when the transaction includes a query operation, the key-value pairs in the state database are queried and the query results are returned to the client node of the business subject. Supports query operations on the state database in multiple dimensions, including: querying blocks based on block serial numbers (such as transaction hash values); querying blocks based on block hash values; querying blocks based on transaction serial numbers; querying transactions based on transaction serial numbers; querying business subject account data based on business subject account numbers (serial numbers); querying blockchains in channels based on channel names.

[0154] The application layer 601 encapsulates various services that can be implemented in the blockchain network, including transaction traceability, evidence storage, and verification.

[0155] The present invention receives service points of corresponding target users pushed by different service systems, and in response to a collection instruction for the service points, collects the service points pushed by at least two service systems into the points account of the target user. In this way, since the service points pushed by different service systems are integrated, it is possible to collect the service points pushed by multiple service systems based on one collection instruction of the user without having to collect them one by one, so that the user can quickly collect the points scattered in discrete point systems, thereby improving the user experience.

[0156] Next, we will use the application scenario of receiving all available service points with one click. Fig.13 , Fig.13 is a flow chart of the method for collecting points provided in an embodiment of the present invention, which will be combined with Figure 6B , Fig. 9 and Fig.13 The method for collecting points provided in the embodiment of the present invention is described. The method for collecting points provided in the embodiment of the present invention includes:

[0157] Step 701: When the service system determines that the point task status corresponding to the target user is completed, the service system pushes the service points corresponding to the target user.

[0158] Here, there are multiple service systems, and each service system pushes the service points of the corresponding target user after determining that the target user has completed the corresponding point task.

[0159] Step 702: The client receives the service points of the corresponding target users pushed by different service systems, and presents the service points pushed by each service system and the collection status of each service point, and presents a "one-click collection" button.

[0160] Here, in actual application, the client may be an instant messaging client, a microblog client, a short video client, etc. The client has a points collection function and receives service points pushed by different service systems.

[0161] For example, see Figure 6B The terminal presents an "One-click Collection" operation button in the graphical interface. The user can click "One-click Collection" to collect the service points pushed by the service system presented in the graphical interface to the target user's point account.

[0162] Step 703: Receive a user's click operation on a button.

[0163] Step 704: The service points pushed by each service system are collected together into the point account of the target user.

[0164] Step 705: Update the receipt status corresponding to the received service points, and store the receipt record corresponding to the received service points.

[0165] Here, the receiving status corresponding to the received service points is updated, that is, the receiving operation is completed. At this time, the relevant information of the received service points is recorded, such as the service system corresponding to the service points, the push time, the receiving time, etc.

[0166] In actual implementation, after updating the claim status corresponding to the claimed service points, the terminal can present a prompt message of successful claim, see Fig. 9 After updating the receipt status corresponding to the received service points, a prompt message of "+800" is presented to prompt the user that 800 points have been received.

[0167] Step 706: receiving the service points of the corresponding target user pushed by the target service system.

[0168] Here, the received service credits refer to newly received service credits after the service credit collection operation is completed based on the user's collection instruction.

[0169] Step 707: Obtain the service points claiming record corresponding to the target user.

[0170] Step 708: based on the service credit collection record, when it is determined that there is a service credit collection record corresponding to the target service system, the service credits pushed by the target service system are collected to the credit account of the target user.

[0171] Here, if the target user has received the service points pushed by the target service system, the terminal directly receives the service points pushed by the target service system to the target user's points account; otherwise, the receiving operation is not performed.

[0172] Step 709: Update the claiming status corresponding to the service points pushed by the target service system.

[0173] Next, we will use the application scenario of receiving service points pushed by multiple service systems selected by users with one click. Fig.14 , Fig.14 is a flow chart of the method for collecting points provided in an embodiment of the present invention, which will be combined with Figure 8 and Fig.14 The method for collecting points provided in the embodiment of the present invention is described. The method for collecting points provided in the embodiment of the present invention includes:

[0174] Step 801: The service system pushes the service points corresponding to the target user based on the user profile of the target user.

[0175] Here, there are multiple service systems, and each service system has a user portrait of a target user, and pushes the service points of the corresponding target user. The user portrait may include at least one of the following: user interest portrait, user basic portrait.

[0176] Step 802: The client receives the service points of the corresponding target users pushed by different service systems, and presents the service points pushed by each service system and the claiming status of each service point.

[0177] Here, each service system pushes a service point corresponding to a selection button, see Figure 8 Each service system pushes a service point with a selection button. Users click the selection button to select the service points they want to receive. If users need to receive all service points, they can click the select all button.

[0178] Step 803: The user receives the service points presented and selects the service points to be collected.

[0179] Step 804: Based on the user's selection operation, determine the service points pushed by the multiple service systems selected by the user.

[0180] Step 805: Receive the user's instruction to collect service points.

[0181] Step 806: The service points pushed by the selected multiple service systems are collected into the point account of the target user.

[0182] Step 807: Update the receipt status corresponding to the received service points.

[0183] Step 808: Obtain the push time corresponding to the service points whose claim status is unclaimed.

[0184] Step 809: When it is determined that the interval between the push time and the current time reaches the preset time threshold, the service points in the claiming status of unclaimed are claimed to the point account of the target user.

[0185] Here, the terminal can automatically collect service points that the user has not collected for a long time.

[0186] Step 810: Update the receipt status corresponding to the received service points.

[0187] The following is a description of the method for collecting points provided by the embodiment of the present invention. Fig.15 , Fig.15 is a flow chart of the method for collecting points provided in an embodiment of the present invention, which will be combined with Figure 6A-6B , Fig. 9 and Fig.15 The method for collecting points provided in an embodiment of the present invention is described.

[0188] Step 901: The user enters the points collection interface.

[0189] Step 902: The client obtains a service credits configuration file corresponding to the user.

[0190] Here, service points are used to represent the service rights and interests provided by the corresponding service system to the target user. Service points can be virtual assets such as membership points, coupons, game coins, etc., which can be used to exchange rights and interests of corresponding value. It should be noted that the points configuration file stores the service points of the corresponding users pushed by different service systems. The service system is the source of service points and can be any system that provides services to the target user, such as a recharge service system, a payment service system, a shopping service system, etc.

[0191] Step 903: The client determines whether there are service points that can be collected. If so, execute step 904; otherwise, execute step 905.

[0192] Step 904: The client displays operation buttons.

[0193] Here, the client presents the operation button in the graphical interface as a clickable operation button. In actual implementation, the operation button can be presented in the form of a floating button. For example, see Fig. 6A , the terminal presents a floating button of "Get Points" in the graphical interface.

[0194] Step 905: The client does not display the operation button.

[0195] Step 906: The client determines whether a click operation on the operation button is received. If so, execute step 907; otherwise, execute step 908.

[0196] Step 907: The client displays a list of points to be collected.

[0197] Here, the list of service credits that can be collected includes the service credits pushed by each service system and the collection status of each service credit. Figure 6B After receiving the user's click operation on the "Get Points" floating button, the service points pushed by each service system and the collection status of each service point are presented.

[0198] Step 908: The client keeps displaying the operation button.

[0199] Step 909: The client determines whether a click operation on the operation button is received again. If so, execute step 910; otherwise, execute step 911.

[0200] Step 910: The client hides the list of points to be collected and the operation buttons.

[0201] Here, when the user clicks the operation button again, the collectible service points are collected into the user's points account, and the collection status corresponding to the collected service points is updated.

[0202] In actual implementation, the user triggers the collection instruction for the service points by clicking the operation button. Based on the collection instruction, the terminal collects the service points that can be collected into the user's points account, updates the collection status corresponding to the collected service points, and sends the updated collection status to the server, thus completing an effective points collection operation. After the points collection operation is completed, the list of points to be collected is hidden and the operation button disappears.

[0203] In some embodiments, after completing the points collection operation, the terminal may present a prompt message that the points collection is successful. Fig. 9 After completing the points collection operation, a prompt message "+800" is displayed to remind the user that 800 points have been collected.

[0204] Step 911: The client keeps displaying the list of points to be collected.

[0205] Here, if no click operation on the operation button is received from the user, the collection instruction is not triggered, and the list of service points that can be collected remains displayed.

[0206] In some embodiments, the terminal may not require the user to perform two click operations. Instead, when the user performs a click operation on the operation button for the first time, after presenting a list of service points that can be collected, the terminal directly performs the points collection operation, collects the collectible service points to the user's points account, and updates the collection status corresponding to the collected service points.

[0207] The following is a description of an exemplary structure of the point claiming device 455 provided in an embodiment of the present invention implemented as a software module. Fig.16 , Fig.16 The schematic diagram of the structure of the points collection device 455 provided in the embodiment of the present invention is shown in FIG. Fig.16 , the points receiving device 455 provided in the embodiment of the present invention includes:

[0208] Receiving module 4551, used for receiving service credits of corresponding target users pushed by different service systems, where the service credits are used to represent the service rights and interests provided by the corresponding service system to the target user;

[0209] The presentation module 4552 is used to present the service points pushed by each service system and the claiming status of each service point;

[0210] A receiving module 4553, configured to receive the service points pushed by at least two of the service systems to the point account of the target user in response to a receiving instruction for the service points;

[0211] The updating module 4554 is used to update the receiving status corresponding to the received service points.

[0212] In some embodiments, the receiving module 4551 is further used to receive the service points corresponding to the target user pushed by different service systems when determining that the point task status corresponding to the target user is completed; or

[0213] Receive service points corresponding to the target user pushed by different service systems based on the user profile of the target user.

[0214] In some embodiments, the collection module 4553 is further used to respond to a collection instruction for the service points and collect the service points pushed by each of the service systems into the points account of the target user.

[0215] In some embodiments, the receiving module 4553 is further used to determine the service points pushed by at least two service systems selected by the target user;

[0216] In response to the instruction to collect the service points, the service points pushed by the selected at least two service systems are collected into the point account of the target user.

[0217] In some embodiments, the claiming module 4553 is further configured to obtain the remaining storage amount of the target user's points account in response to a claiming instruction for the service points;

[0218] When it is determined that the total amount of the service points pushed by different service systems is greater than the remaining storage amount, obtaining the first push time corresponding to the service points pushed by each of the service systems;

[0219] Based on the order of the first push times corresponding to the service points pushed by each of the service systems, the service points pushed by at least two of the service systems are collected into the points account of the target user, so that the number of points in the points account of the target user matches the storage limit of the points account.

[0220] In some embodiments, the claiming module 4553 is further used to obtain a second push time corresponding to the service points whose claiming status is unclaimed;

[0221] When it is determined that the interval between the second push time and the current time reaches a preset time threshold, the service points in the collection status of uncollected are collected to the point account of the target user.

[0222] In some embodiments, the receiving module 4553 is further used to receive the service points corresponding to the target user pushed by the target service system;

[0223] Obtaining the service points claiming record corresponding to the target user;

[0224] When it is determined based on the service point claiming record that there is a service point claiming record corresponding to the target service system, the service points pushed by the target service system are claimed to the point account of the target user.

[0225] In some embodiments, the device further comprises: a prompt module, for respectively obtaining the collection time and validity period of the service points pushed by different service systems in the target account;

[0226] Based on the collection time and the validity period, prompt information is presented, and the prompt information is used to prompt the validity status of the service points.

[0227] In some embodiments, the apparatus further comprises: a storage module for generating a claim record corresponding to the claimed service credits;

[0228] Performing a hash transformation on the claim record to obtain summary information corresponding to the claim record;

[0229] The summary information is stored in the blockchain network.

[0230] An embodiment of the present invention provides a storage medium storing executable instructions, wherein the executable instructions are stored. When the executable instructions are executed by a processor, the processor will be caused to execute the method provided by the embodiment of the present invention, for example, Figure 5 The method shown.

[0231] In some embodiments, the storage medium may be a memory such as FRAM, ROM, PROM, EPROM, EEPROM, flash memory, magnetic surface memory, optical disk, or CD-ROM; or various devices including one or any combination of the above memories.

[0232] In some embodiments, executable instructions may be in the form of a program, software, software module, script or code, written in any form of programming language (including compiled or interpreted languages, or declarative or procedural languages), and may be deployed in any form, including as a stand-alone program or as a module, component, subroutine or other unit suitable for use in a computing environment.

[0233] As an example, executable instructions may, but need not, correspond to a file in a file system, may be stored as part of a file storing other programs or data, such as in one or more scripts in a HyperText Markup Language (HTML) document, in a single file dedicated to the program in question, or in multiple coordinated files (e.g., files storing one or more modules, subroutines, or code portions).

[0234] By way of example, executable instructions may be deployed to be executed on one computing device, or on multiple computing devices located at one site, or on multiple computing devices distributed across multiple sites and interconnected by a communication network.

[0235] The above description is only an embodiment of the present invention and is not intended to limit the protection scope of the present invention. Any modification, equivalent replacement and improvement made within the spirit and scope of the present invention are included in the protection scope of the present invention.

Claims

1. A method for collecting points, characterized in that: The method comprises: Receive service credits of corresponding target users pushed by different service systems, where the service credits are used to represent the service rights and interests provided by the corresponding service systems to the target users; The service points pushed by each service system and the claiming status of each corresponding service point are presented respectively; Presenting an operation button for collecting the service credits, wherein the target user triggers an instruction to collect the service credits by clicking the operation button; wherein the service credits pushed by multiple service systems correspond to the same operation button; In response to the instruction to collect the service points, collect the service points pushed by each of the service systems into the point account of the target user; Update the claim status corresponding to the received service points; Obtain the second push time corresponding to the service points whose claim status is unclaimed; When it is determined that the interval between the second push time and the current time reaches a preset time threshold, the service points in the collection status of uncollected are collected to the point account of the target user.

2. The method according to claim 1, characterized in that The receiving of service points of corresponding target users pushed by different service systems includes: receiving service points corresponding to the target user pushed by different service systems when determining that the points task status corresponding to the target user is completed; or, Receive service points corresponding to the target user pushed by different service systems based on the user profile of the target user.

3. The method according to claim 1, characterized in that The method further comprises: Determining service points pushed by at least two service systems selected by the target user; In response to the instruction to collect the service points, the service points pushed by the selected at least two service systems are collected into the point account of the target user.

4. The method according to claim 1, characterized in that The method further comprises: In response to a claim instruction for the service points, obtaining a remaining storage amount of the target user's points account; When it is determined that the total amount of the service points pushed by different service systems is greater than the remaining storage amount, obtaining the first push time corresponding to the service points pushed by each of the service systems; Based on the order of the first push times corresponding to the service points pushed by each of the service systems, the service points pushed by at least two of the service systems are collected into the points account of the target user, so that the number of points in the points account of the target user matches the storage limit of the points account.

5. The method according to claim 1, characterized in that After the service points pushed by each of the service systems are collected together into the point account of the target user, the method further includes: Receiving the service points corresponding to the target user pushed by the target service system; Obtaining the service points claiming record corresponding to the target user; When it is determined based on the service point claiming record that there is a service point claiming record corresponding to the target service system, the service points pushed by the target service system are claimed to the point account of the target user.

6. The method according to claim 1, characterized in that The method further comprises: Generate a claim record corresponding to the claimed service points; Performing a hash transformation on the claim record to obtain summary information corresponding to the claim record; The summary information is stored in the blockchain network.

7. A device for collecting points, characterized in that: The device comprises: A receiving module, used to receive service credits of corresponding target users pushed by different service systems, where the service credits are used to represent the service rights and interests provided by the corresponding service system to the target users; a presentation module, used to present the service points pushed by each service system and the claiming status of each service point; present an operation button for claiming the service points, and the target user triggers a claiming instruction for the service points by clicking the operation button; wherein the service points pushed by multiple service systems correspond to the same operation button; A receiving module, configured to respond to the receiving instruction for the service points and receive the service points pushed by each of the service systems to the point account of the target user; An update module, used to update the claim status corresponding to the claimed service points; The collection module is also used to obtain the second push time corresponding to the service points with a collection status of uncollected; when it is determined that the interval between the second push time and the current time reaches a preset time threshold, the service points with a collection status of uncollected are collected to the points account of the target user.

8. A storage medium, characterized in that: Executable instructions are stored, which are used to cause the processor to execute and implement the method for collecting points described in any one of claims 1 to 6.

Images