Bill processing method, server and medium
By building a billing processing platform on the server and pre-writing a sub-bill template library, personalized bill templates are generated based on user information, solving the problems of high difficulty and low flexibility in bill delivery operations, and achieving flexible and efficient bill delivery.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- CHINA UNITED NETWORK COMM GRP CO LTD
- Filing Date
- 2022-12-28
- Publication Date
- 2026-07-03
AI Technical Summary
The existing electronic billing delivery process is difficult and inflexible, especially when dealing with multiple types of bills and multiple bills for the same user, which leads to waste of resources and user dissatisfaction.
By building a billing processing platform on the server, pre-compiling sub-bill templates for each bill type as a template library, and generating user-specific target bill templates based on delivery task information and user information, the complexity of operation is reduced and flexibility is improved.
It reduces the difficulty and increases the flexibility of bill delivery, eliminating the need for professional programmers to manually write code and adapting to the personalized billing needs of different users.
Smart Images
Figure CN115860736B_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of data processing, and more particularly to a billing processing method, server, and medium. Background Technology
[0002] In recent years, offline paper bills have been gradually replaced by online electronic bills, which not only meets the needs of paperless and environmental protection, but also significantly reduces the manpower and economic costs of bill delivery.
[0003] Existing electronic bills have relatively fixed content formats. For example, a phone bill typically includes information such as brand (operator name), name, phone number, and date, arranged in a fixed order. In current technology, each type of bill delivery requires programmers to write corresponding code. Programmers write the code based on the content format and other information for a specific bill type and send it to the server. When the scheduled delivery time for that type of bill arrives, the server receives the instruction, runs the code, retrieves the bill data for different users, generates the bill based on the data, and delivers it to the corresponding user. However, due to the rapid development of the internet and information technology, bill types have become diverse, no longer limited to phone bills, but also including bank credit card spending bills, points bills, product bills, and many others. Sometimes, the same billing party issues multiple bills to the same user, wasting resources and frequently disturbing the user, leading to dissatisfaction. To save on bill delivery resources, billing parties often choose to display all of a user's bill information on a single bill, making the bill content increasingly rich. Given this situation, specialized programmers are needed to develop delivery program code for different types of bills, resulting in high difficulty and low flexibility in bill delivery operations.
[0004] Therefore, a billing processing solution that is easy to implement and highly flexible is needed. Summary of the Invention
[0005] This application provides a billing processing method, server, and medium to solve the technical problems of high difficulty and low flexibility in existing bill delivery operations.
[0006] Firstly, this application provides a billing processing method, including:
[0007] Receive a bill delivery request sent by the operating terminal and determine the delivery task information in the bill delivery request;
[0008] The corresponding user group is determined based on the delivery task information;
[0009] For each user in the aforementioned delivery user group
[0010] Determine the user information and business scenario information corresponding to the user, and determine the user tag corresponding to the user based on the user information and business scenario information;
[0011] Determine the sub-bill template corresponding to the user tag, and generate the target bill template corresponding to the user based on the sub-bill template;
[0012] Based on the template type corresponding to the target bill template, obtain the bill data corresponding to the user;
[0013] Based on the billing data and the target billing template, a bill corresponding to the user is generated, and the bill is delivered to the user's corresponding user terminal.
[0014] In one possible implementation, determining the corresponding user group based on the delivery task information specifically includes:
[0015] Based on the delivery task information, an initial user group is determined. The delivery task information includes one or more of the following: delivery area information, billing time information, service type information, and billing type information.
[0016] The initial user group is filtered according to preset silent user filtering rules and / or harassment complaint records to obtain active users in the initial user group;
[0017] Based on the active users in the initial user group, the corresponding delivery user group is determined.
[0018] In one possible implementation, determining the user information and business scenario information corresponding to the user, and determining the user tag corresponding to the user based on the user information and business scenario information, specifically includes:
[0019] Information is extracted from the data corresponding to the user based on preset user attributes and business scenario attributes to determine the user information and business scenario information corresponding to the user. The user attributes include one or more of the following: user province affiliation, operator affiliation, user activity level, gender, and age. The business scenario attributes include one or more of the following: call charges, points, benefits, and service packages.
[0020] Based on the preset correspondence between information and tags, the tags corresponding to the user information and the tags corresponding to the business scenario information are determined respectively;
[0021] The user tag corresponding to the user is determined based on the tags corresponding to the user information and the tags corresponding to the business scenario information; or, the user tag corresponding to the user is determined based on the tags corresponding to the user information, the tags corresponding to the business scenario information, and the user's custom tags.
[0022] In one possible implementation, determining the sub-bill template corresponding to the user tag and generating the target bill template corresponding to the user based on the sub-bill template specifically includes:
[0023] Based on the preset correspondence between tags and sub-bill templates, determine the sub-bill template corresponding to the user tag;
[0024] Based on the preset correspondence between sub-bill templates and combination templates, determine the combination template corresponding to the sub-bill template, or combine each sub-bill template using a preset combination order to generate the corresponding combination template;
[0025] The target bill template corresponding to the user is determined based on the combined template.
[0026] In one possible implementation, after determining the user tag corresponding to the user based on the user information and business scenario information, the method further includes:
[0027] Based on the preset correspondence between tags and recommendation information, the recommendation information corresponding to the user tags is determined;
[0028] Accordingly, generating the bill corresponding to the user based on the bill data and the target bill template includes:
[0029] Based on the billing data, the target billing template, and the recommendation information corresponding to the user tag, a bill corresponding to the user is generated.
[0030] In one possible implementation, generating the bill corresponding to the user based on the bill data, the target bill template, and the recommendation information corresponding to the user tag specifically includes:
[0031] Determine the target data format corresponding to the target bill template, and use the target data format to process the bill data to obtain the target bill data;
[0032] Determine whether the bill display format information input by the operation terminal has been obtained. The bill display format information includes one or more of the following: background image information corresponding to the combined template, background image information corresponding to each sub-bill template, data display format information corresponding to each sub-bill template, and display format information corresponding to each recommendation information.
[0033] If so, then the bill corresponding to the user is generated based on the target bill data, the target bill template, the recommendation information corresponding to the user tag, and the bill display format information.
[0034] In one possible implementation, delivering the bill to the user's corresponding user terminal specifically includes:
[0035] Based on the template type corresponding to the target bill template, obtain the verification bill data corresponding to the user;
[0036] Determine whether the verified bill data is consistent with the bill data corresponding to the user;
[0037] If so, the corresponding target delivery platform is determined based on the delivery type information sent by the delivery terminal, and the bill is delivered to the user terminal corresponding to the user using the target delivery platform.
[0038] The delivery type information includes one or more of the following: email, SMS, and external web page links.
[0039] Secondly, this application provides a server, comprising:
[0040] The receiving module is used to receive the bill delivery request sent by the operating terminal and determine the delivery task information in the bill delivery request;
[0041] The processing module is configured to: determine the corresponding user group based on the delivery task information; for each user in the user group, determine the user information and business scenario information corresponding to the user, and determine the user tag corresponding to the user based on the user information and business scenario information; determine the sub-bill template corresponding to each user tag, and generate the target bill template corresponding to the user based on the sub-bill template; obtain the bill data corresponding to the user based on the template type corresponding to the target bill template; generate the bill corresponding to the user based on the bill data and the target bill template, and deliver the bill to the user terminal corresponding to the user.
[0042] Thirdly, this application provides a server, including: a processor, and a memory communicatively connected to the processor;
[0043] The memory stores computer-executed instructions;
[0044] The processor executes computer execution instructions stored in the memory to implement the above-described method.
[0045] Fourthly, this application provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement the above-described method.
[0046] Fifthly, this application provides a computer program product, including a computer program that, when executed by a processor, implements the above-described method.
[0047] The billing processing method, server, and medium provided in this application can receive bill delivery requests sent by operating terminals and determine the delivery task information in the bill delivery request; determine the corresponding delivery user group based on the delivery task information; for each user in the delivery user group, determine the user information and business scenario information corresponding to the user, and determine the user tag corresponding to the user based on the user information and business scenario information; determine the sub-bill template corresponding to each user tag, and generate the target bill template corresponding to the user based on the sub-bill template; obtain the bill data corresponding to the user based on the template type corresponding to the target bill template; generate the bill corresponding to the user based on the bill data and the target bill template, and deliver the bill to the user terminal corresponding to the user. In this application, instead of programmers writing program code corresponding to bill types, a billing processing platform is built on the server based on the program code. Through the billing processing platform on the server and the processing methods loaded therein, the operational difficulty of bill delivery is reduced and the flexibility of bill delivery is improved. Specifically, programmers can generate corresponding sub-bill templates based on the pre-written program code corresponding to each bill type, which are stored as a template library on the server. After receiving a bill delivery request from the terminal, the server can first filter out the corresponding user groups based on the delivery task information, and then determine the user tags for each user in the group based on user information and business scenario information. Next, it can determine the sub-bill template corresponding to each user tag, retrieve the corresponding sub-bill template from the template library, and combine them to generate the target bill template. The method of this application allows for the pre-setting of corresponding sub-bill templates for each bill type, and then the generation of user-specific bill templates based on the sub-bill templates corresponding to user tags. Through this setting, user-specific bill templates can be generated specifically for different user tags, and the final generated bill template does not require programmers to write corresponding program code; it only needs to be generated by combining existing sub-bill templates. This eliminates the need for professional programmers to process the bills, reducing the operational difficulty of bill delivery and improving its flexibility. Attached Figure Description
[0048] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.
[0049] Figure 1 This is a system architecture diagram of an embodiment of this application;
[0050] Figure 2 This is a flowchart of a billing processing method according to an embodiment of this application;
[0051] Figure 3 This is a schematic diagram of the structure of a server according to an embodiment of this application;
[0052] Figure 4 This is a schematic diagram of the server structure according to another embodiment of this application.
[0053] Reference numerals in the attached diagram: 1. Operating terminal; 2. Server; 3. Delivery terminal; 4. User terminal.
[0054] The accompanying drawings illustrate specific embodiments of this application, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concept of this application to those skilled in the art through reference to particular embodiments. Detailed Implementation
[0055] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.
[0056] The billing processing method, server, and media of this application can be used in electronic bill delivery scenarios, such as the delivery of electronic bills generated by network operators, e-commerce platforms, and online banks.
[0057] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties. Furthermore, the collection, use and processing of the relevant data must comply with the relevant laws, regulations and standards of the relevant countries and regions, and corresponding operation portals are provided for users to choose to authorize or refuse.
[0058] Existing electronic bills have relatively fixed content formats. For example, a phone bill typically includes information such as brand (operator name), name, phone number, and date, arranged in a fixed order. In current technology, the delivery of each type of bill requires programmers to write corresponding code. Programmers write the code based on the content format and other information for a specific bill type and send it to the server. When the scheduled delivery time for that type of bill arrives, the server receives the instruction, runs the code, retrieves the bill data for different users, generates the bill based on the data, and then delivers it to the corresponding user.
[0059] However, due to the rapid development of the internet and information technology, bill types have become diverse, no longer limited to phone bills, but also including bank credit card bills, points bills, product bills, and many others. Sometimes, the same billing party may issue multiple bills to the same user. To save on bill delivery resources, billing parties often choose to display all of a user's billing information on a single bill, making the bill content increasingly complex. This necessitates specialized programmers to develop separate delivery code for different types of bills, resulting in high complexity and low flexibility in bill delivery operations.
[0060] For example, a user subscribes to a mobile plan A from a certain operator and also subscribes to a data plan B. The operator needs to send the user three bills each month: a phone bill, a data bill, and a corresponding points bill. This not only wastes resources but also frequently bothers the user, leading to dissatisfaction. To save on bill delivery resources and reduce the number of deliveries, the operator needs to display the phone bill, data usage, and points information in a single bill. This requires specialized programmers to develop corresponding delivery code tailored to the user's specific needs (phone bill, data usage, and points). However, different users choose a variety of services, resulting in potentially different delivery code for each user, making bill delivery complex and inflexible.
[0061] Based on this technical problem, the inventive concept of this application is to provide a bill processing method that is easy to perform and highly flexible in bill delivery operations.
[0062] Specifically, the system can receive bill delivery requests from operating terminals and determine the delivery task information within the requests; determine the corresponding user group based on the delivery task information; for each user in the user group, determine the user information and business scenario information, and determine the user tag based on the user information and business scenario information; determine the sub-bill template corresponding to each user tag, and generate the target bill template for the user based on the sub-bill template; obtain the bill data for the user based on the template type corresponding to the target bill template; generate the bill for the user based on the bill data and the target bill template, and deliver the bill to the user's corresponding user terminal. In this application, instead of programmers writing program code for each bill type, a bill processing platform is built on the server based on the program code. This bill processing platform and its loaded processing methods reduce the operational difficulty of bill delivery and improve its flexibility. Specifically, programmers can generate corresponding sub-bill templates based on pre-written program code for each bill type, which are then stored as a template library on the server. After receiving a bill delivery request from the terminal, the server can first filter out the corresponding user groups based on the delivery task information, and then determine the user tags for each user in the group based on user information and business scenario information. Next, it can determine the sub-bill template corresponding to each user tag, retrieve the corresponding sub-bill template from the template library, and combine them to generate the target bill template. The method of this application allows for the pre-setting of corresponding sub-bill templates for each bill type, and then the generation of user-specific bill templates based on the sub-bill templates corresponding to user tags. Through this setting, user-specific bill templates can be generated specifically for different user tags, and the final generated bill template does not require programmers to write corresponding program code; it only needs to be generated by combining existing sub-bill templates. This eliminates the need for professional programmers to process the bills, reducing the operational difficulty of bill delivery and improving its flexibility.
[0063] The technical solution of this application and how the technical solution of this application solves the above-mentioned technical problems are described in detail below with specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of this application will be described below with reference to the accompanying drawings.
[0064] Figure 1 This is a system architecture diagram of an embodiment of this application, as shown below. Figure 1As shown, 1 represents the operation terminal, 2 represents the server, 3 represents the delivery terminal, and 4 represents the user terminal. Staff can send a bill delivery request to server 2 via operation terminal 1. Upon receiving the request, server 2 determines the corresponding user group based on the delivery task information in the request. For each user in the user group, it determines the user information and business scenario information, and based on these, determines the user's corresponding user tag. It then determines the sub-bill template corresponding to each user tag and generates the target bill template for the user based on the sub-bill template. Based on the template type of the target bill template, it obtains the user's bill data. Based on the bill data, the target bill template, the recommendation information corresponding to the user tag, and the bill display format information input by operation terminal 1, it generates the user's bill. Finally, based on the delivery type information sent by delivery terminal 3, it determines the corresponding target delivery platform and uses the target delivery platform to deliver the bill to the user's corresponding user terminal 4.
[0065] Example 1
[0066] Figure 2 This is a flowchart of a billing processing method provided in an embodiment of this application. This embodiment describes the billing processing method with the server as the executing entity. Figure 2 As shown, the billing method may include the following steps:
[0067] S101: Receive the bill delivery request sent by the operation terminal and determine the delivery task information in the bill delivery request.
[0068] In this embodiment, the operating terminal can be the operating terminal of the operator (or other bill initiator). For example, at the beginning of each month or other scheduled bill delivery time, the staff can send a bill delivery request to the server through the operating terminal so that the server can complete the bill delivery.
[0069] S102: Determine the corresponding user group based on the delivery task information.
[0070] In one possible implementation, step S102, which determines the corresponding user group based on the delivery task information, may include: determining an initial user group based on the delivery task information; filtering the initial user group based on preset silent user filtering rules and / or harassment complaint records to obtain active users in the initial user group; and determining the corresponding user group based on the active users in the initial user group.
[0071] In this embodiment, the delivery task information may include one or more of the following: delivery area information, billing time information, service type information, and billing type information. Delivery area information may be the region where the user to be delivered is located, such as their place of origin; billing time information may be the time the bill was generated, such as a November bill; billing type information may be the type of bill, such as a phone bill, points bill, benefits bill, or service bill, and the specific billing type can be flexibly set by those skilled in the art; service type information may be the type of service corresponding to the bill, such as a phone bill purchase service, and the specific service type can be flexibly set by those skilled in the art.
[0072] In this implementation, when staff send a bill delivery request to the server via the operating terminal, they can input information such as the delivery area, billing time, service type, and bill type on the terminal's operation page. For example, a November bill for a China Unicom user in Beijing.
[0073] In this embodiment, the silent user filtering rules can be the existing filtering rules used by bill initiators such as operator platforms, which will not be described in detail here.
[0074] In this implementation, an initial user group meeting the delivery task conditions is first determined based on the delivery task information. Then, active users within the initial user group are selected using preset silent user filtering rules and / or harassment complaint records. This setup not only identifies users meeting the delivery task conditions but also allows for secondary filtering to remove silent users and those with harassment complaint records, thus obtaining the user group that truly needs bill delivery and preventing users who do not want to receive bills from filing harassment complaints.
[0075] S103: For each user in the delivery user group, determine the user information and business scenario information corresponding to the user, and determine the user tag corresponding to the user based on the user information and business scenario information.
[0076] In one possible implementation, step S103 above, which involves determining the user information and business scenario information corresponding to the user, and determining the user tag corresponding to the user based on the user information and business scenario information, may include:
[0077] S1031: Extract information from the user's data based on preset user attributes and business scenario attributes to determine the user's corresponding user information and business scenario information.
[0078] S1032: Based on the preset correspondence between information and tags, determine the tags corresponding to user information and the tags corresponding to business scenario information respectively.
[0079] S1033: Determine the user's corresponding user tag based on the tags corresponding to the user information and the tags corresponding to the business scenario information.
[0080] In this embodiment, user attributes may include one or more of the following: user's province of origin, carrier affiliation, user activity level, gender, and age. Business scenario attributes may include one or more of the following: call charges, points, benefits, and service packages. Of course, user attributes and business scenario attributes are not limited to these, and those skilled in the art can flexibly set them according to actual needs.
[0081] In this embodiment, those skilled in the art can pre-set user attributes and business scenario attributes. After determining the user group, they can first obtain the data corresponding to each user in the user group, and then use the pre-set attributes to extract the user's corresponding information to determine the user information and business scenario information corresponding to the user.
[0082] In this embodiment, user basic information can be easily and accurately determined through user attributes, and information such as product orders or business types participated in by the user can be easily and accurately determined through business scenario attributes. Therefore, by using the user information and business scenario information corresponding to the user, and their corresponding tags, the user's situation can be comprehensively and accurately characterized. Furthermore, those skilled in the art can pre-set the correspondence between information and tags, that is, the correspondence between user information and tags, and the correspondence between business scenario information and tags. After determining the user information and business scenario information corresponding to the user, the user tags corresponding to the user can be easily and accurately determined according to the preset correspondence.
[0083] Alternatively, step S1033 can be replaced by determining the user's corresponding user tag based on the tags corresponding to the user information, the tags corresponding to the business scenario information, and the user's corresponding custom tag.
[0084] In this implementation, a user may have information that existing tags cannot represent. The operator can create a custom tag for the user and send it to the server via the terminal. This improves the comprehensiveness and accuracy of user tags.
[0085] S104: Determine the sub-bill template corresponding to the user tag, and generate the target bill template corresponding to the user based on the sub-bill template.
[0086] In this embodiment, the sub-bill template can be template program code pre-developed by programmers based on existing billing information. That is, code is written according to the content format and other information corresponding to a certain type of bill, and this code serves as the template for that type of bill. The sub-bill template can be the template corresponding to the smallest level of billing type after detailed segmentation, such as a phone bill template, points bill template, benefits bill template, or business bill templates corresponding to various services. The sub-bill template contains only a single type of billing content. The target bill template can include multiple types of billing content.
[0087] In one possible implementation, step S104, which determines the sub-bill template corresponding to each user tag and generates the target bill template corresponding to the user based on the sub-bill template, may include: determining the sub-bill template corresponding to the user tag based on a preset correspondence between tags and sub-bill templates; determining the combined template corresponding to the sub-bill template based on a preset correspondence between sub-bill templates and combined templates; and determining the target bill template corresponding to the user based on the combined template.
[0088] In this embodiment, the correspondence between sub-bill templates and combination templates can be that which types of sub-bill templates correspond to which combination templates, for example, sub-bill templates A and B correspond to combination template 1, and sub-bill templates A, B, and C correspond to combination template 2, etc.
[0089] In this embodiment, those skilled in the art can pre-set the correspondence between tags and sub-bill templates. After determining the user's tag, the corresponding sub-bill template for the user can be easily and conveniently determined. Furthermore, those skilled in the art can also pre-set the correspondence between sub-bill templates and combined templates. After determining the sub-bill template for the user, the corresponding target bill template for the user can be easily and conveniently determined without requiring programmers to write corresponding program code; they only need to call a pre-stored combined template from the template library.
[0090] Alternatively, step S104 above, which determines the sub-bill template corresponding to each user tag and generates the target bill template corresponding to the user based on the sub-bill template, may include: determining the sub-bill template corresponding to each user tag based on a preset correspondence between tags and sub-bill templates; combining each sub-bill template using a preset combination order to generate a corresponding combination template; and determining the target bill template corresponding to the user based on the combination template.
[0091] In this embodiment, after determining the sub-bill template corresponding to the user, the combined template can be obtained by combining these sub-bill templates according to the combination order, without the need to store the combined template in the template library in advance.
[0092] S105: Obtain the user's bill data based on the template type corresponding to the target bill template.
[0093] In this embodiment, the correspondence between the combined template and the template type can be preset. After determining the combined template (target bill template), the template type corresponding to the target bill template can be determined.
[0094] In this embodiment, the template type can represent the content to be included in the bill. For example, the template type can be call charges + points, call charges + benefits, call charges + specific services, etc. Those skilled in the art can flexibly set the specific template type, and no restrictions are imposed here.
[0095] In this embodiment, after determining the template type corresponding to the target bill template, the user's corresponding bill data can be obtained according to the template type. For example, if the template type is call charge + points, the user's corresponding call charge data and points data can be obtained and used as the bill data.
[0096] S106: Generate the bill for the user based on the bill data and the target bill template, and deliver the bill to the user's corresponding user terminal.
[0097] In one possible implementation, after determining the user tag corresponding to the user based on user information and business scenario information in step S103 above, it may further include: determining the recommendation information corresponding to the user tag based on the preset correspondence between the tag and the recommendation information.
[0098] Accordingly, step S106 above, which involves generating the user's corresponding bill based on the bill data and the target bill template, may include:
[0099] Generate a bill for the user based on the billing data, the target billing template, and the recommendation information corresponding to the user tags.
[0100] In this embodiment, the correspondence between tags and recommendation information can be flexibly set by those skilled in the art. For example, young women aged 25-35 can be recommended youth-oriented business packages, while middle-aged men aged 40-45 can be recommended office business packages.
[0101] In this implementation, recommendation information can also be determined based on user tags, and a bill corresponding to the user can be generated based on billing data, the target bill template, and the recommendation information corresponding to the user tags. This setup allows for precise information recommendations to users, preventing harassment complaints.
[0102] In one possible implementation, generating a bill for a user based on bill data, a target bill template, and recommendation information corresponding to the user tag may include: determining the target data format corresponding to the target bill template, and processing the bill data using the target data format to obtain the target bill data; determining whether the bill display format information input by the operating terminal has been obtained; if so, generating a bill for the user based on the target bill data, the target bill template, the recommendation information corresponding to the user tag, and the bill display format information.
[0103] In this embodiment, the bill display format information may include one or more of the following: background image information corresponding to the combined template, background image information corresponding to each sub-bill template, data display format information corresponding to each sub-bill template, and display format information corresponding to each recommendation. Those skilled in the art can flexibly set these parameters. The background image information corresponding to the combined template may be the background image information of the entire bill; the background image information corresponding to each sub-bill template may be the background image information of the corresponding portion of each sub-bill within the bill; the data display format information corresponding to each sub-bill template may be the display format of the data corresponding to each sub-bill, such as a bar chart, pie chart, line chart, etc.; the display format information corresponding to each recommendation may be the display format of each recommendation, such as font, text color, graphics, etc.
[0104] In this implementation, after determining the target bill template, the bill data can first be processed (data cleaning, formatting, etc.) using the target data format corresponding to the target bill template to ensure that the bill data conforms to the format requirements of the target bill template, thus facilitating the subsequent generation of the bill. Furthermore, the display format of the bill can be customized to enhance the user's bill reading experience.
[0105] In one possible implementation, the step S106 above, which involves delivering the bill to the user's corresponding user terminal, may include: obtaining the user's verification bill data according to the template type corresponding to the target bill template; determining whether the verification bill data is consistent with the user's corresponding bill data; if so, determining the corresponding target delivery platform according to the delivery type information sent by the delivery terminal, and using the target delivery platform to deliver the bill to the user's corresponding user terminal.
[0106] In this embodiment, the delivery type information may include one or more of email, SMS, and external web page links. Of course, the delivery type information is not limited to these, and those skilled in the art can set it flexibly. The external web page link may be an H5 web page link.
[0107] In this embodiment, after the bill is generated, the corresponding bill data can be retrieved a second time to verify the bill and improve its accuracy. Furthermore, delivery personnel can select the appropriate delivery type based on user needs or the delivery pressure on various platforms, and send the information to the server via the delivery terminal. This allows the server to determine the corresponding target delivery platform based on the delivery type information, ensuring the accuracy and timeliness of bill delivery and alleviating delivery pressure while ensuring users receive their bills.
[0108] In this embodiment, instead of programmers writing program code corresponding to each bill type, a bill processing platform is built on the server based on the program code. This server-side platform and its loaded processing methods reduce the operational difficulty of bill delivery and improve its flexibility. Specifically, programmers can generate corresponding sub-bill templates based on pre-written program code for each bill type, which are stored as a template library on the server. After receiving a bill delivery request from the terminal, the server can first filter out the corresponding user group based on the delivery task information, and then determine the user tag for each user in the group based on user information and business scenario information. Then, it can determine the sub-bill template corresponding to each user tag, retrieve the corresponding sub-bill template from the template library, and combine them to generate the target bill template. This method allows for the pre-setting of corresponding sub-bill templates for each bill type, and then the generation of a user-specific bill template based on the sub-bill templates corresponding to the user tags. This setup allows for the generation of user-specific bill templates tailored to different user tags. Furthermore, the generated bill templates do not require programmers to write corresponding code; they can be generated simply by combining existing sub-bill templates. This eliminates the need for professional programmers, reducing the operational difficulty of bill delivery and increasing its flexibility.
[0109] The billing method of this application is described below with a specific embodiment.
[0110] Example 2
[0111] In one specific example, China Unicom staff need to deliver bills to China Unicom users in Beijing in early December. The specific billing process is as follows:
[0112] The first step involves China Unicom staff entering information such as "November, Beijing, China Unicom" into the user interface of the terminal. Based on this information, the terminal generates a bill delivery request and sends it to the server.
[0113] The second step is that after receiving the data, the server determines the initial user group based on information such as "November, Beijing, China Unicom" and then filters the initial user group according to the preset silent user screening rules and harassment complaint records to obtain the target user group.
[0114] The third step involves the server determining the user information and business scenario information for each user in the delivery user group, and then determining the user tag based on the user information and business scenario information.
[0115] The fourth step is for the server to determine the sub-bill template corresponding to each user tag and generate the target bill template corresponding to the user based on the sub-bill template.
[0116] The fifth step involves the server retrieving the user's bill data based on the template type corresponding to the target bill template, and then processing the bill data using the target data format corresponding to the target bill template to obtain the target bill data.
[0117] The sixth step is for the server to determine the recommended information corresponding to the user's tags based on the preset correspondence between tags and recommended information.
[0118] Step 7: The server generates the user's bill based on the target bill data, the target bill template, the recommendation information corresponding to the user tags, and the bill display format information entered by the user terminal.
[0119] Step 8: The server obtains the user's verification bill data according to the template type corresponding to the target bill template, and verifies the bill using the verification bill data. After successful verification, the server determines the corresponding target delivery platform based on the delivery type information sent by the delivery terminal, and delivers the bill to the user's corresponding user terminal using the target delivery platform.
[0120] Figure 3 This is a schematic diagram of the structure of a server according to an embodiment of this application, as shown below. Figure 3As shown, the server includes: a receiving module 31, used to receive a bill delivery request sent by an operating terminal and determine the delivery task information in the bill delivery request; a processing module 32, used to determine the corresponding delivery user group based on the delivery task information; for each user in the delivery user group, determine the user information and business scenario information corresponding to the user, and determine the user tag corresponding to the user based on the user information and business scenario information; determine the sub-bill template corresponding to each user tag, and generate the target bill template corresponding to the user based on the sub-bill template; obtain the bill data corresponding to the user based on the template type corresponding to the target bill template; generate the bill corresponding to the user based on the bill data and the target bill template, and deliver the bill to the user terminal corresponding to the user. In one embodiment, the specific implementation function of the server can be described in steps S101-S106 of Embodiment 1, which will not be repeated here.
[0121] Figure 4 This is a schematic diagram of the server structure according to another embodiment of this application, as shown below. Figure 4 As shown, the server includes a processor 101 and a memory 102 communicatively connected to the processor 101; the memory 102 stores computer-executable instructions; the processor 101 executes the computer-executable instructions stored in the memory 102 to implement the steps of the billing processing method in the above-described method embodiments.
[0122] In the aforementioned server, the memory 102 and the processor 101 are electrically connected directly or indirectly to enable data transmission or interaction. For example, these components can be electrically connected to each other via one or more communication buses or signal lines, such as a bus connection. The memory 102 stores computer-executable instructions that implement data access control methods, including at least one software functional module that can be stored in the memory 102 in the form of software or firmware. The processor 101 executes various functional applications and data processing by running the software programs and modules stored in the memory 102.
[0123] The memory 102 may be, but is not limited to, Random Access Memory (RAM), Read Only Memory (ROM), Programmable Read-Only Memory (PROM), Erasable Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM), etc. The memory 102 stores programs, which are executed by the processor 101 upon receiving execution instructions. Furthermore, the software programs and modules within the memory 102 may include an operating system, which may include various software components and / or drivers for managing system tasks (e.g., memory management, storage device control, power management, etc.) and can communicate with various hardware or software components to provide an operating environment for other software components.
[0124] Processor 101 can be an integrated circuit chip with signal processing capabilities. The aforementioned processor 101 can be a general-purpose processor, including a Central Processing Unit (CPU), a Network Processor (NP), etc. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor can be a microprocessor or any conventional processor.
[0125] An embodiment of this application also provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement the steps of the various method embodiments of this application.
[0126] An embodiment of this application also provides a computer program product, including a computer program that, when executed by a processor, implements the steps of the various method embodiments of this application.
[0127] Other embodiments of this application will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of this application that follow the general principles of this application and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this application are indicated by the appended claims.
[0128] It should be understood that this application is not limited to the precise structure described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this application is limited only by the appended claims.
Claims
1. A billing processing method, characterized in that, include: Receive a bill delivery request sent by the operating terminal and determine the delivery task information in the bill delivery request; Based on the delivery task information, an initial user group is determined. The delivery task information includes one or more of the following: delivery area information, billing time information, service type information, and billing type information. The initial user group is filtered according to preset silent user filtering rules and / or harassment complaint records to obtain active users in the initial user group; Based on the active users in the initial user group, determine the corresponding delivery user group; For each user in the delivery user group, information is extracted from the data corresponding to the user according to preset user attributes and business scenario attributes to determine the user information and business scenario information corresponding to the user. The user attributes include one or more of the following: user province affiliation, operator affiliation, user activity level, gender, and age. The business scenario attributes include one or more of the following: phone bill, points, benefits, and service packages. Based on the preset correspondence between information and tags, the tags corresponding to the user information and the tags corresponding to the business scenario information are determined respectively; The user tag corresponding to the user is determined based on the tags corresponding to the user information and the tags corresponding to the business scenario information; or, the user tag corresponding to the user is determined based on the tags corresponding to the user information, the tags corresponding to the business scenario information, and the user's custom tags. Determine the sub-bill template corresponding to the user tag, and generate the target bill template corresponding to the user based on the sub-bill template; Based on the template type corresponding to the target bill template, obtain the bill data corresponding to the user; Based on the billing data and the target billing template, a bill corresponding to the user is generated, and the bill is delivered to the user's corresponding user terminal.
2. The method according to claim 1, characterized in that, The step of determining the sub-bill template corresponding to the user tag and generating the target bill template corresponding to the user based on the sub-bill template specifically includes: Based on the preset correspondence between tags and sub-bill templates, determine the sub-bill template corresponding to the user tag; Based on the preset correspondence between sub-bill templates and combination templates, determine the combination template corresponding to the sub-bill template, or combine each sub-bill template using a preset combination order to generate the corresponding combination template; The target bill template corresponding to the user is determined based on the combined template.
3. The method according to claim 2, characterized in that, After determining the user tag corresponding to the user based on the user information and business scenario information, the method further includes: Based on the preset correspondence between tags and recommendation information, the recommendation information corresponding to the user tags is determined; Accordingly, generating the bill corresponding to the user based on the bill data and the target bill template includes: Based on the billing data, the target billing template, and the recommendation information corresponding to the user tag, a bill corresponding to the user is generated.
4. The method according to claim 3, characterized in that, The step of generating the bill corresponding to the user based on the bill data, the target bill template, and the recommendation information corresponding to the user tag specifically includes: Determine the target data format corresponding to the target bill template, and use the target data format to process the bill data to obtain the target bill data; Determine whether the bill display format information input by the operation terminal has been obtained. The bill display format information includes one or more of the following: background image information corresponding to the combined template, background image information corresponding to each sub-bill template, data display format information corresponding to each sub-bill template, and display format information corresponding to each recommendation information. If so, then the bill corresponding to the user is generated based on the target bill data, the target bill template, the recommendation information corresponding to the user tag, and the bill display format information.
5. The method according to any one of claims 1-4, characterized in that, The step of delivering the bill to the user's corresponding user terminal specifically includes: Based on the template type corresponding to the target bill template, obtain the verification bill data corresponding to the user; Determine whether the verified bill data is consistent with the bill data corresponding to the user; If so, the corresponding target delivery platform is determined based on the delivery type information sent by the delivery terminal, and the bill is delivered to the user terminal corresponding to the user using the target delivery platform. The delivery type information includes one or more of the following: email, SMS, and external web page links.
6. A server, characterized in that, include: The receiving module is used to receive the bill delivery request sent by the operating terminal and determine the delivery task information in the bill delivery request; The processing module is configured to: determine an initial user group based on the delivery task information, which includes one or more of delivery area information, billing time information, service type information, and billing type information; filter the initial user group according to preset silent user screening rules and / or harassment complaint records to obtain active users within the initial user group; determine the corresponding delivery user group based on the active users within the initial user group; for each user in the delivery user group, extract information from the user's corresponding data according to preset user attributes and service scenario attributes to determine the user information and service scenario information corresponding to the user, whereby the user attributes include one or more of user province affiliation, operator affiliation, user activity level, gender, and age, and the service scenario attributes include one or more of call charges, points, benefits, and service packages; and determine the tags corresponding to the user information and the tags corresponding to the service scenario information according to a preset correspondence between information and tags. The user tag corresponding to the user is determined based on the tags corresponding to the user information and the tags corresponding to the business scenario information; or, the user tag corresponding to the user is determined based on the tags corresponding to the user information, the tags corresponding to the business scenario information, and the user's custom tags. Determine the sub-bill template corresponding to each user tag, and generate the target bill template corresponding to the user based on the sub-bill template; Based on the template type corresponding to the target bill template, obtain the bill data corresponding to the user; generate the bill corresponding to the user based on the bill data and the target bill template, and deliver the bill to the user terminal corresponding to the user.
7. A server, characterized in that, Includes a processor and a memory communicatively connected to the processor; The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory to implement the method as described in any one of claims 1 to 5.
8. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the method as described in any one of claims 1 to 5.