Product information pushing method and device, operator equipment and storage medium

Abstract

The invention provides a product information pushing method and device, operator equipment and a storage medium. The method comprises the steps of obtaining a user type and current product package information of a user according to a user account; if the user type is a home network type, obtaining to-be-pushed standard product package information from a pre-constructed standard product package information base according to a main account number of the user account number; splitting the to-be-pushed standard product package information according to product types to obtain multiple pieces of product information; according to the current product package information, obtaining initial to-be-pushed product information from the multiple pieces of product information; according to the current product package information and the initial to-be-pushed product information, final pushed product information of different product types is determined; and sending the finally pushed product information of the different product types to the user side, so that the user side displays the finally pushed product information according to the product types. According to the method provided by the invention, the product information can be accurately pushed, and the personalized requirements of customers are met.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a product information push method, apparatus, operator equipment, and storage medium. Background Technology

[0002] The telecommunications industry's growth relies on the continuous expansion of its user base. However, as the market approaches saturation, the growth potential for new users has shrunk significantly, prompting operators to shift their focus to existing users. The core of existing user management lies in identifying potential needs and pushing relevant products when adding services to existing plans, based on users' existing spending power and package structure.

[0003] Currently, existing technologies use three methods—supervised learning, reinforcement learning, and clustering hierarchical analysis—to segment customers and push unified product information based on the customer segment level.

[0004] However, existing technologies can only achieve coarse-grained push notifications at the customer group level, that is, push the same product information to the same customer group level. The pushed product information is not accurate and cannot meet the personalized needs of customers. Summary of the Invention

[0005] This application provides a product information push method, apparatus, operator equipment, and storage medium to achieve the effect of accurately pushing product information and meeting the personalized needs of customers.

[0006] In a first aspect, embodiments of this application provide a product information push method, comprising: receiving a product push request sent by a user terminal, wherein the product push request carries a user account; obtaining user type and current product package information of the user based on the user account; if the user type is a local network type, obtaining the main account of the user account; obtaining standard product package information to be pushed from a pre-built standard product package information database based on the main account; splitting the standard product package information to be pushed according to product type to obtain multiple product information; obtaining initial product information to be pushed from the multiple product information based on the current product package information; determining the final product information to be pushed for different product types based on the current product package information and the initial product information to be pushed; and sending the final product information to be pushed for different product types to the user terminal, so that the user terminal displays the final product information to be pushed according to the product type.

[0007] In one possible implementation, the standard product package information to be pushed is obtained from a pre-built standard product package information database based on the main account, including: obtaining multiple standard product package information from the pre-built standard product package information database based on the main account; obtaining the province identifier of the main account; obtaining the province identifier of each standard product package information; and determining the standard product package information that is the same as the province identifier of the main account from the province identifiers of the multiple standard product package information as the standard product package information to be pushed.

[0008] In one possible implementation, based on the current product package information, initial product information to be pushed is obtained from multiple product information sources, including: based on the current product package information, and according to pre-built product push constraint rules, initial product information to be pushed is obtained from multiple product information sources.

[0009] In one possible implementation, the final product information to be pushed for different product types is determined based on the current product package information and the initial product information to be pushed, including: obtaining multiple incremental pricing models corresponding to different product types; using the multiple incremental pricing models corresponding to different product types, calculating multiple incremental prices for different product types based on the current product package information and the initial product information to be pushed; obtaining the minimum incremental price for different product types from the multiple incremental prices for different product types; and determining the final product information to be pushed for different product types based on the minimum incremental price for different product types.

[0010] In one possible implementation, after determining the final product information pushed for different product types, the method further includes: obtaining a first voice call parameter, a first data traffic parameter, and a first broadband parameter from the final product information pushed for different product types; obtaining a second voice call parameter, a second data traffic parameter, and a second broadband parameter from the current product package information; if the first voice call parameter is greater than the second voice call parameter, obtaining an incremental voice call parameter; if the first data traffic parameter is greater than the second data traffic parameter, obtaining an incremental data traffic parameter; if the first broadband parameter is greater than the second broadband parameter, obtaining an incremental broadband parameter; and sending the incremental voice call parameter, incremental data traffic parameter, and incremental broadband parameter to the user terminal so that the user terminal displays the incremental voice call parameter, incremental data traffic parameter, and incremental broadband parameter according to the product type.

[0011] In one possible implementation, before receiving a product push request sent by the user, the method further includes: configuring multiple business types for different preset business scenarios; configuring standard product package information for each business type to obtain a pre-built standard product package information database.

[0012] Secondly, embodiments of this application provide a product information push device, comprising:

[0013] The receiving module is used to receive product push requests sent by the user client, where the product push request carries the user account.

[0014] The first acquisition module is used to obtain user type and current product package information based on user account.

[0015] The second acquisition module is used to acquire the main account of the user account if the user type is the same as the one on this network.

[0016] The third acquisition module is used to obtain the standard product package information to be pushed from the pre-built standard product package information database based on the main account.

[0017] The fourth acquisition module is used to split the standard product package information to be pushed into multiple product information according to product type.

[0018] The fifth acquisition module is used to obtain the initial product information to be pushed from multiple product information based on the current product package information.

[0019] The determination module is used to determine the final product information to be pushed for different product types based on the current product package information and the initial product information to be pushed.

[0020] The sending module is used to send the final product information of different product types to the user terminal, so that the user terminal can display the final product information according to the product type.

[0021] Thirdly, embodiments of this application provide an operator device, including: a memory and a processor;

[0022] The memory stores computer-executed instructions;

[0023] The processor executes computer execution instructions stored in the memory, causing the processor to perform the first aspect and / or various possible implementations of the first aspect as described above.

[0024] Fourthly, embodiments of this application provide a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement the first aspect and / or various possible implementations of the first aspect.

[0025] Fifthly, embodiments of this application provide a computer program product, including a computer program that, when executed by a processor, implements the first aspect and / or various possible implementations of the first aspect.

[0026] The product information push method, apparatus, operator equipment, and storage medium provided in this application embodiment obtain user type and current product package information based on the user account carried in the product push request; when the user type is the local network type, the primary account of the user account is obtained; based on the primary number of the user account, standard product package information to be pushed is filtered from a pre-built standard product package information database; the standard product package information to be pushed is split according to product type to obtain multiple product information, realizing the transformation of the traditional package packaging form into modular products to adapt to the user's personalized needs. Based on the user's current product package information, initial product information to be pushed is obtained from multiple product information; ensuring that the pushed product information is deeply associated with the user's current product package information; based on the current product package information and the initial product information to be pushed, the final product information to be pushed for different product types is determined; the final product information to be pushed for different product types is sent to the user terminal so that the user terminal can display the final pushed product information according to product type. This breaks through the limitations of traditional coarse-grained push and achieves accurate push of product information to meet the personalized needs of customers. Attached Figure Description

[0027] 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.

[0028] Figure 1 A system structure diagram of the product information push method provided in the embodiments of this application;

[0029] Figure 2 A flowchart illustrating the product information push method provided in this application embodiment;

[0030] Figure 3 This is a schematic diagram of the structure of the product information push device provided in the embodiments of this application;

[0031] Figure 4 This is a schematic diagram of the structure of the operator equipment provided in the embodiments of this application.

[0032] 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

[0033] 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.

[0034] Figure 1 A system structure diagram of the product information push method provided in the embodiments of this application is shown below. Figure 1 As shown, it includes a user display unit 101, a data service unit 102, a computing logic unit 103, and an operation configuration unit 104.

[0035] In this embodiment, the user display unit 101 is used to display the login account box, connects with the operator's device authentication system based on the OAuth 2.0 protocol, obtains the user account through the unified login interface, and completes the legality verification through the authentication system; it is also used for error prompts and displaying the product information push interface.

[0036] In this embodiment, the data service unit 102 includes an authentication system and a user basic data center. The authentication system verifies the legitimacy of user login information and marks user accounts. Marking includes information such as local mobile phone number, local broadband number, external network number, landline number, and incorrect number information. The user basic data center is used to query basic user information.

[0037] In this embodiment, the computational logic unit 103 is used to split the standard product package information to be pushed; based on the decision tree model and the Drools rule engine, it executes the pre-built product push constraint rules, filters out inapplicable product information according to the package type in the current product package information; uses multiple incremental pricing models corresponding to different product types to calculate multiple incremental prices for different product types; and identifies the incremental resource parameters.

[0038] In this embodiment, the operation configuration unit 104 is used to configure multiple service types for different preset business scenarios; for each service type, standard product package information is configured to build a standard product package information database. Optionally, a province identifier is added to each standard product package information in the standard product package information database to establish an association index between user accounts and standard product package information.

[0039] The telecommunications industry's growth relies on the continuous expansion of its user base. However, as the market approaches saturation, the growth potential for new users has shrunk significantly, leading operators to shift their focus to existing users. The core of existing user management lies in identifying potential needs and pushing relevant products when adding services, based on users' existing spending power and package structure. Currently, existing technologies use supervised learning, reinforcement learning, and clustering / stratification methods to segment customers and push uniform product information according to these segments. However, current technologies can only achieve coarse-grained push notifications at the customer segment level, meaning the same product information is pushed to the same customer segment. This results in inaccurate product information and an inability to meet customers' personalized needs.

[0040] To address the aforementioned technical problems, this application proposes the following technical concept: Considering that pushing the same product information to the same customer group level leads to inaccurate product information and fails to meet customers' personalized needs, the inventors conceived of using the primary number associated with the user account to filter standard product package information to be pushed to the current user. This transforms the traditional packaged format into modular products, adapting to users' personalized needs, and deeply associating the pushed product information with the user's current product package information, enabling targeted product information pushes to any user, breaking through the limitations of traditional coarse-grained pushes. Specifically, based on the primary number associated with the user account, standard product package information to be pushed is filtered from a pre-built standard product package information database. This information is then split according to product type to obtain multiple product information items, thus transforming the traditional packaged format into modular products that adapt to users' personalized needs. Based on the user's current product plan information, initial product information to be pushed is obtained from multiple product information sources; ensuring that the pushed product information is deeply correlated with the user's current product plan information; based on the current product plan information and the initial product information to be pushed, the final product information to be pushed for different product types is determined; the final product information to be pushed for different product types is sent to the user's terminal so that the user's terminal can display the final pushed product information according to the product type. This achieves accurate product information push and meets the personalized needs of customers.

[0041] 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 now be described with reference to the accompanying drawings.

[0042] Figure 2 This is a flowchart illustrating the product information push method provided in the embodiments of this application, such as... Figure 2 As shown, the method includes:

[0043] S201: Receive a product push request sent by the user client, wherein the product push request carries the user account.

[0044] In this embodiment, the user terminal provides a user login interface, which displays a login account box to collect the user's login information. After the user enters their user account, the system calls the OAuth 2.0 protocol to connect to the operator's equipment SSO platform, obtains the user account and password information through the unified login interface, and requests the authentication system to verify the user's legitimacy based on the user account, password information, and login time. Once the authentication system confirms that there are no problems, subsequent operations can be performed.

[0045] In this embodiment, the user actively triggers a product push request on the user's end to request business processing.

[0046] In this embodiment, the product push request carries a user account, which can be a mobile phone number or a broadband number.

[0047] S202: Based on the user account, obtain the user type and the user's current product package information.

[0048] In this embodiment, after a user successfully logs in, a user account information query request is sent to the authentication system based on two parameters: the current user account and the login time. Upon receiving the request, the authentication system compares the information with stored data. Once the comparison is complete, the user account is flagged. The flagged information includes whether the user's mobile phone number is from the local network, broadband number from the local network, number from another network, landline number, or incorrect number information. In this embodiment, user accounts flagged as having a local mobile phone number or broadband number are categorized as belonging to the local network type, while user accounts flagged as having an other network number, landline number, or incorrect number information are categorized as belonging to another network type.

[0049] In this embodiment, if the user type is a different network type, it is determined that the user does not meet the conditions for handling the business, an error message indicating that the user does not meet the handling requirements is sent to the user's terminal, and the process is terminated.

[0050] In this embodiment, if the user type is the local broadband type, the subsequent loop steps are performed to ensure that product information is only pushed to users of the local network type who meet the business processing requirements.

[0051] In this embodiment, only when the user type is "local network type" is the user's basic information queried from the user basic data center via the GraphQL interface. The request parameter is the login account, and the returned information is the current product package information, including 8 core fields: package type, main package account, package price, number of package members, member accounts, basic voice minutes, basic data allowance, and broadband speed. Among these, package type, main package account, package price, and number of package members are mandatory fields. If the package does not include member accounts, basic voice minutes, basic data allowance, and broadband speed, they may not be returned. The returned information is saved.

[0052] In this embodiment, the package types include single-card users, primary and secondary card users, broadband-integrated packages, single-broadband users, and secondary card users. A single-card user is someone who owns only one card. A primary and secondary card user is someone who has subscribed to a package that binds a primary card and a secondary card; the primary card is the core of the package, and the secondary card shares the resources of the primary card. A broadband-integrated package refers to someone who has subscribed to a package that integrates broadband and other services. A single-broadband user is someone who has only subscribed to broadband services and has not subscribed to mobile communication or other services such as a secondary card. A secondary card user is someone who uses a secondary card; this secondary card belongs to the primary card in a primary and secondary card package and is not an independent core of the package, but depends on the package resources and payment mechanism of the primary card.

[0053] S203: If the user type is "this network type", obtain the main account of the user account.

[0054] For example, when a user using a secondary SIM card initiates a product information push request, and the user account is the secondary SIM card user's mobile phone number or broadband number, the product information push needs to be based on the primary SIM card user's mobile phone number or broadband number, i.e., the primary account. In step S202, the package primary account in the returned information is the primary SIM card user's primary account.

[0055] S204: Obtain the standard product package information to be pushed from the pre-built standard product package information database based on the main account.

[0056] Specifically, from the pre-built standard product package information database, multiple standard product package information is obtained based on the main account; the province identifier of the main account is obtained; the province identifier of each standard product package information is obtained; from the province identifiers of multiple standard product package information, the standard product package information that is the same as the province identifier of the main account is identified as the standard product package information to be pushed.

[0057] In this embodiment, the main account is associated with key attributes such as the province of origin, and the associated province identifier is obtained. In the pre-built standard product package information database, each standard product package information is associated with a province identifier, indicating which province's users can subscribe to the standard product package. Specifically, the province identifier of the main account is matched one by one with the province identifiers of each standard product package information to determine whether there is any standard product package information that can be pushed to the user's province. If no standard product package information can be pushed, an error message indicating that the business processing requirements are not met is sent to the user's terminal; if there is standard product package information that can be pushed, the process proceeds to the next step. By combining the two methods, it is ensured that the product package information pushed subsequently complies with the operating rules of the user's current province.

[0058] S205: The standard product package information to be pushed is split according to product type to obtain multiple product information.

[0059] In this embodiment, the standard product package information to be pushed is broken down into three independent product units based on product type: secondary SIM card, broadband, and secondary SIM card + broadband. This transforms the traditional packaged format into modular products, adapting to users' personalized needs. For example, if only a secondary SIM card needs to be installed or only broadband needs to be subscribed, this provides a flexible product foundation for subsequent accurate product information pushes.

[0060] S206: Based on the current product package information, obtain the initial product information to be pushed from multiple product information sources.

[0061] Specifically, based on the current product package information and in accordance with the pre-built product push constraint rules, the initial product information to be pushed is obtained from multiple product information sources.

[0062] In this embodiment, the package type is obtained from the current product package information.

[0063] In this embodiment, the pre-built product push constraint rules are as follows: For single-SIM users, no second broadband service or products related to the primary SIM card are pushed; for primary and secondary SIM card users, no second broadband service or products related to the primary SIM card are pushed; for single-broadband users, no secondary SIM card or products related to the first broadband service are pushed; for broadband-plus-service users, no primary SIM card or products related to the first broadband service are pushed. Optionally, there is also a package type for full-SIM full-service users who have both broadband-plus-service and primary / secondary SIM card services; in this case, no products related to the primary SIM card or the first broadband service are pushed.

[0064] In this embodiment, based on the decision tree model and the Drools rule engine, pre-built product push constraint rules are executed to filter out inapplicable product information according to the package type in the current product package information. By matching the package type in the current product package information with the product's compatibility, conflicting or redundant push options are eliminated, such as avoiding repeatedly pushing the primary card to users who already have primary and secondary cards, ensuring that the products pushed later are consistent with user needs and package structure, and improving push accuracy.

[0065] S207: Based on the current product package information and the initial product information to be pushed, determine the final product information to be pushed for different product types.

[0066] Specifically, step S207 includes S2071 to S2074:

[0067] S2071: Obtain multiple incremental pricing models corresponding to different product types.

[0068] S2072: Employ multiple incremental pricing models corresponding to different product types, and calculate multiple incremental prices for different product types based on the current product package information and the initial product information to be pushed.

[0069] In this embodiment, the application scenarios for multiple incremental pricing models include adding a secondary SIM card to an unchanged product package, adding a secondary SIM card to an upgraded product package, offering broadband for a minimum spend commitment, adding broadband, converting a single SIM card to a bundled package, and converting a primary and secondary SIM card to a bundled broadband package.

[0070] Among them, adding a secondary SIM card to an unchanged product package and adding a secondary SIM card to an upgraded product package belong to the incremental pricing model corresponding to the secondary SIM card product type; offering broadband with a minimum spending commitment and adding broadband belong to the incremental pricing model corresponding to the broadband product type; and converting a single SIM card to a bundled package and converting a primary and secondary SIM card to a broadband bundled package belong to the incremental pricing model corresponding to the secondary SIM card + broadband product type.

[0071] In this embodiment, the scenario of adding a supplementary SIM card to an unchanged product plan is as follows: the user retains the current product plan information and only adds a supplementary SIM card. The formula for the incremental pricing model of adding a supplementary SIM card to an unchanged product plan is:

[0072]

[0073] In the formula, This represents incremental pricing, where S represents the monthly price per supplementary card (in yuan / month / card), and K represents the number of new supplementary cards. The constraint for the number of new supplementary cards is k ≤ M. max M max This indicates the maximum number of supplementary cards allowed. When calculating incremental pricing, simply obtain the monthly price per supplementary card. For example, adding a supplementary card increases the price by 10 yuan per month, then S=10.

[0074] In this embodiment, the scenario for upgrading a product plan and adding a secondary SIM card is: the user upgrades their current product plan and adds a secondary SIM card. The formula for the incremental pricing model for upgrading a product plan and adding a secondary SIM card is:

[0075]

[0076] In the formula, Indicates incremental pricing, P old This indicates the package price in the user's current product package information, in yuan / month; P new This indicates the base plan price of the target plan, K indicates the number of new supplementary SIM cards, and S indicates the base plan price. i This represents the monthly price per card for the i-th supplementary card.

[0077] For example, if the user's current product package fee is 39 yuan / month, the basic package fee of the target package is 58 yuan / month, and a new supplementary card is added with a monthly price of 10 yuan / month / card, then the incremental pricing is (58-39)+10=29.

[0078] In this embodiment, the scenario of offering free broadband upon commitment of a minimum spending requirement means that the user receives free broadband after committing to a minimum spending amount. The formula for the incremental pricing model of offering free broadband upon commitment of a minimum spending requirement is as follows:

[0079]

[0080] In the formula, Indicates incremental pricing, P new The constraint condition is P new≥ C min C min This is the minimum spending requirement, or minimum charge. The `max()` function ensures that the price is non-negative, meaning the base price of the target plan is not lower than the price of the user's current plan, i.e., P. new You must spend more than or equal to the minimum spending amount to enjoy free broadband.

[0081] For example, the user's current product package information shows a package fee of 59 yuan / month, a minimum charge of 89 yuan / month for broadband, and a free 300Mbps broadband. The target package's basic package fee must be greater than 89 yuan / month, with an incremental pricing of 30 yuan / month, which can obtain 300Mbps broadband for free without any additional broadband fees.

[0082] In this embodiment, the scenario for adding broadband is: a user adding a second broadband connection or a single broadband service. The formula for the incremental pricing model for adding broadband is:

[0083]

[0084] In the formula, This indicates incremental pricing, where B represents the unit price for new broadband, in yuan / month. old This indicates the package pricing information in the current product package details, P new This represents the base package price of the target package. When only broadband is added and the current product package information is not changed, ΔP=B.

[0085] In this embodiment, the scenario of single-SIM to converged service is: a single-SIM user switching to a converged service plan. Single-SIM to converged service includes two cases: single-SIM + broadband and single-SIM + broadband + secondary SIM. The formula for the incremental pricing model corresponding to single-SIM + broadband is:

[0086]

[0087] In the formula, Indicates incremental pricing, P old This indicates the package pricing information in the current product package details, P new This indicates the base plan fee for the target plan. For example, the current product plan includes 10GB of data and has a plan fee of 39 yuan / month. The target plan is a bundled plan, which includes 10GB of data and 300Mbps broadband. The base plan fee for the target plan is 59 yuan / month, and the incremental pricing is 20 yuan / month. That is, the current user pays an extra 20 yuan to get broadband service.

[0088] The formula for the incremental pricing model corresponding to single SIM card + broadband + secondary SIM card is as follows:

[0089]

[0090] In the formula, Indicates incremental pricing, P old This indicates the package pricing information in the current product package details, P new This indicates the base price of the target plan, and S represents the monthly price of a single secondary SIM card. For example, the current product plan includes 10GB of data, and the plan price in the current product plan information is 39 yuan / month. The target plan is a bundled plan that includes 10GB of data + 300Mbps broadband. The base price of the target plan is 59 yuan / month, the price for adding a secondary SIM card is 10 yuan / month, and the incremental pricing is 30 yuan / month. That is, the current user pays an extra 30 yuan to get broadband service and a secondary SIM card.

[0091] In this embodiment, the scenario of primary and secondary SIM card users upgrading to a broadband converged package is as follows: primary and secondary SIM card users upgrade to a broadband converged package.

[0092] In this embodiment, there are two scenarios for the primary and secondary SIM card broadband integration: one is adding only broadband, and the other is adding both broadband and a secondary SIM card. The number of secondary SIM cards included in the broadband integration package is M. When the basic broadband integration package only includes broadband and does not include any additional secondary SIM cards...

[0093] In this embodiment, when the number of secondary SIM cards included in the broadband bundled package is greater than or equal to the number of secondary SIM cards in the current product package information, and the primary and secondary SIM cards are merged into a package that only adds broadband and does not include secondary SIM cards, the incremental pricing model formula is as follows:

[0094]

[0095] In the formula, Indicates incremental pricing, P old This indicates the package pricing information in the current product package details, P new This indicates the base plan fee for the target plan, and N represents the number of supplementary SIM cards in the current product plan information.

[0096] For example, the current product package fee is 89 yuan / month, and the target package's basic fee is 129 yuan / month. If the current product package is changed to the target fee package, two supplementary cards cannot be used. Therefore, the cost of two supplementary cards needs to be added to the target package's basic fee. The supplementary card price is 10 yuan / month / card. This is incremental pricing, i.e., 129 + 2 × 10 - 89 = 60 yuan.

[0097] In this embodiment, when the number of secondary SIM cards included in the broadband bundled package is greater than or equal to the number of secondary SIM cards in the current product package information, the primary and secondary SIM cards are merged into a new broadband connection, and an additional secondary SIM card is added. That is, one additional secondary SIM card is needed on top of the target package. In this case, the formula for the incremental pricing model is:

[0098]

[0099] In this embodiment, when the number of secondary SIM cards included in the broadband converged package is less than the number of secondary SIM cards specified in the current product package information, the primary and secondary SIM card users cannot use the secondary SIM cards, and the number of secondary SIM cards must be reduced. The formula for the incremental pricing model of the primary and secondary SIM card broadband converged package is as follows:

[0100]

[0101] In the formula, Indicates incremental pricing, P old This indicates the package pricing information in the current product package details, P new This indicates the base plan fee for the target plan.

[0102] Optionally, the incremental pricing model also includes a scenario for primary card upgrades, where users upgrade their primary card plan without any additional services. The formula for the incremental pricing model for primary card upgrades is as follows:

[0103]

[0104] In the formula, P oldThis indicates the package pricing information in the current product package details, P new This indicates the base plan fee for the target plan.

[0105] S2073: Obtain the lowest incremental price for different product types from multiple incremental prices for different product types.

[0106] In this embodiment, when the product type is a secondary SIM card, two incremental pricing models are calculated using the unchanged product package plus a secondary SIM card and the upgraded product package plus a secondary SIM card. The lowest incremental pricing for the product type of secondary SIM card is obtained from these two incremental pricing models. When the product type is broadband, two incremental pricing models are calculated using the commitment to provide broadband with a minimum spend and the addition of broadband. The lowest incremental pricing for the product type of broadband is obtained from these two incremental pricing models. When the product type is secondary SIM card + broadband, two incremental pricing models are calculated using the single SIM card to converged and primary and secondary SIM card to broadband converged models. The lowest incremental pricing for the product type of secondary SIM card + broadband is obtained from these two incremental pricing models.

[0107] In this embodiment, a min-heap data structure is used to quickly extract the minimum incremental pricing for different product types, perform price compliance checks, exclude negative prices, and only take the minimum incremental pricing that is positive or higher.

[0108] In this embodiment, the min-heap is a data structure that can retrieve the lowest incremental price in a short time, reducing user waiting time and improving user experience. Furthermore, the lowest incremental price may result in a negative price due to incorrect parameter configuration, but the price cannot be negative during actual business transactions as it is illogical. By filtering out negative values, the incremental price ultimately displayed to the user is ensured to be reasonable.

[0109] S2074: Determine the final product information to be pushed for different product types based on the minimum incremental pricing for different product types.

[0110] In this embodiment, the initial product information to be pushed corresponding to the lowest incremental pricing of different product types is determined as the final product information to be pushed for different product types.

[0111] S208: Send the final product information for different product types to the user terminal so that the user terminal can display the final product information according to the product type.

[0112] In this embodiment, the final product information for different product types is sent to the user terminal so that the user terminal responds to the user's selection operation on the product information push interface and displays the final product information for different product types.

[0113] Optionally, the content displayed on the user's end may also include incremental resource parameters, which include incremental voice call parameters, incremental traffic parameters, and incremental bandwidth parameters.

[0114] Specifically, from the final product information pushed for different product types, the system obtains the first voice call parameters, the first data usage parameters, and the first broadband parameters; it also obtains the second voice call parameters, the second data usage parameters, and the second broadband parameters from the current product package information; if the first voice call parameter is greater than the second voice call parameter, it obtains the incremental voice call parameters; if the first data usage parameter is greater than the second data usage parameter, it obtains the incremental data usage parameters; if the first broadband parameter is greater than the second broadband parameter, it obtains the incremental broadband parameters; and it sends the incremental voice call parameters, incremental data usage parameters, and incremental broadband parameters to the user terminal so that the user terminal displays the incremental voice call parameters, incremental data usage parameters, and incremental broadband parameters according to the product type.

[0115] The incremental voice call parameter represents the additional voice calls obtained by the pushed product information compared to the user's current product plan; the incremental data traffic parameter represents the additional data traffic obtained by the pushed product information compared to the user's current product plan; and the incremental broadband parameter represents the additional broadband bandwidth obtained by the pushed product information compared to the user's current product plan. For example, if the user's current product plan includes 200 minutes of second voice calls per month, and the pushed product information includes 350 minutes of first voice calls per month, then the incremental voice call parameter is 150 minutes.

[0116] In this embodiment, the user terminal triggers a dynamic page rendering engine to load a responsive page framework based on the terminal type. A price anchoring strategy is adopted to prominently display the pre-added X yuan / month price tag on the product information push interface. Based on calculations of minimum incremental pricing, incremental voice call parameters, incremental data parameters, and incremental broadband parameters, a differentiated product information push interface is assembled in real time, incorporating component-based designs including price comparisons and resource increment indicators. A price display component for each user and a resource increment tag component are designed. Specifically, resource increments are only acquired when they are positive, indicating improvements in data, voice, and broadband speeds. If they remain unchanged or are negative, they are not displayed. For original packages without voice, data, or broadband, an increase is directly indicated to enhance the user's perceived value. The product push information interface elements include the pre-added +X yuan / month price tag, product type, and the final pushed product information. After user confirmation, further order interaction is supported, providing a standardized order interface that allows users to trigger the business processing flow after confirming the product.

[0117] Optionally, the initial product information to be pushed for multiple incremental pricing for different product types can be displayed in ascending order of incremental pricing.

[0118] In summary, based on the user account carried in the product push request, the system obtains the user type and the user's current product package information. When the user type is "this network type," it obtains the user account's primary account. Based on the user account's primary account number, it filters the standard product package information to be pushed from a pre-built standard product package information database. This information is then split according to product type, resulting in multiple product information items. This transforms the traditional packaged format into modular products, adapting to users' personalized needs. Based on the user's current product package information, it obtains the initial product information to be pushed from multiple product information items, ensuring a deep correlation between the pushed product information and the user's current product package information. Based on the current product package information and the initial product information to be pushed, it determines the final product information to be pushed for different product types. Finally, it sends the final product information for different product types to the user's device, allowing the user to display the final pushed product information according to product type. This overcomes the limitations of traditional coarse-grained push notifications, accurately pushing product information and meeting customers' personalized needs.

[0119] Based on the above embodiments, this embodiment describes the configuration process before receiving product push requests sent by the user terminal, as detailed below:

[0120] S301: Configure multiple service types for different preset business scenarios.

[0121] Among them, the preset business scenarios are package types, and different preset business scenarios include primary and secondary card users, single card users, broadband users, and single broadband users.

[0122] In this embodiment, it supports importing and exporting business scenario configurations in XML / JSON format, and supports selecting business scenarios by province identifier, such as adding a secondary SIM card, promising broadband with low spending, adding a second broadband connection, converting to converged service, and adding a primary SIM card. It features a rule-based visual editor, enabling drag-and-drop configuration of business logic, and supports nested configuration of IF-THEN-ELSE conditional branches.

[0123] S302: Configure standard product package information for each business type to obtain a pre-built standard product package information database.

[0124] In this embodiment, standard product package parameters and parameter thresholds can be configured, such as package tariffs, maximum number of members, upper limit of the number of secondary cards, voice parameters, data traffic parameters, and broadband speed parameters. It supports configuring gift policies and visual materials, and at the same time, a parameter validator is built to ensure the legality of tariff configuration.

[0125] In this embodiment, the configured standard product package information is stored in the standard product package information database according to the JSON Schema specification, and a field index is established to complete the construction of the standard product package information database.

[0126] Among them, the gift strategy refers to the configured gift information.

[0127] Optionally, gift information can be obtained from a pre-built standard product package information database and added to the final product push information.

[0128] In summary, different business scenarios correspond to different user groups. Configuring multiple business types for different preset business scenarios allows common needs within the same scenario to be extracted into business types, avoiding irrelevant push notifications. By configuring and setting standard product package information for different business types, a data foundation is provided for pushing product information to users.

[0129] Figure 3 This is a schematic diagram of the structure of the product information push device provided in the embodiments of this application, such as... Figure 3 As shown, the product information push device provided in this embodiment includes: a receiving module 301, a first acquisition module 302, a second acquisition module 303, a third acquisition module 304, a fourth acquisition module 305, a fifth acquisition module 306, a determining module 307, and a sending module 308.

[0130] The receiving module 301 is used to receive a product push request sent by the user terminal, wherein the product push request carries the user account.

[0131] The first acquisition module 302 is used to acquire user type and user's current product package information based on user account;

[0132] The second acquisition module 303 is used to acquire the main account of the user account if the user type is the local network type;

[0133] The third acquisition module 304 is used to obtain the standard product package information to be pushed from the pre-built standard product package information database according to the main account;

[0134] The fourth acquisition module 305 is used to split the standard product package information to be pushed according to product type to obtain multiple product information;

[0135] The fifth acquisition module 306 is used to acquire the initial product information to be pushed from multiple product information based on the current product package information;

[0136] The determination module 307 is used to determine the final product information to be pushed for different product types based on the current product package information and the initial product information to be pushed.

[0137] The sending module 308 is used to send the final product information of different product types to the user terminal so that the user terminal can display the final product information according to the product type.

[0138] In one possible implementation, the third acquisition module 304 is specifically used to: acquire multiple standard product package information from a pre-built standard product package information database based on the main account; acquire the province identifier of the main account; acquire the province identifier of each standard product package information; and determine the standard product package information that is the same as the province identifier of the main account from the province identifiers of the multiple standard product package information as the standard product package information to be pushed.

[0139] In one possible implementation, the fifth acquisition module 306 is specifically used to: based on the current product package information and in accordance with pre-built product push constraint rules, acquire initial product information to be pushed from multiple product information.

[0140] In one possible implementation, the determining module 307: obtains multiple incremental pricing models corresponding to different product types; uses the multiple incremental pricing models corresponding to different product types to calculate multiple incremental prices for different product types based on the current product package information and the initial product information to be pushed; obtains the minimum incremental price for different product types from the multiple incremental prices for different product types; and determines the final product information to be pushed for different product types based on the minimum incremental price for different product types.

[0141] In one possible implementation, the product information push device further includes a display module, configured to: obtain first voice call parameters, first data traffic parameters, and first broadband parameters from the final pushed product information of different product types; obtain second voice call parameters, second data traffic parameters, and second broadband parameters from the current product package information; if the first voice call parameter is greater than the second voice call parameter, obtain incremental voice call parameters; if the first data traffic parameter is greater than the second data traffic parameter, obtain incremental data traffic parameters; if the first broadband parameter is greater than the second broadband parameter, obtain incremental broadband parameters; and send the incremental voice call parameters, incremental data traffic parameters, and incremental broadband parameters to the user terminal, so that the user terminal displays the incremental voice call parameters, incremental data traffic parameters, and incremental broadband parameters according to the product type.

[0142] In one possible implementation, the product information push device further includes a configuration module for configuring multiple business types for different preset business scenarios; and for each business type, configuring standard product package information to obtain a pre-built standard product package information database.

[0143] The product information push device provided in this embodiment can execute the method provided in the above method embodiment. Its implementation principle and technical effect are similar, and will not be described in detail here.

[0144] Figure 4 This is a schematic diagram of the structure of the operator equipment provided in an embodiment of this application. Figure 4 As shown, the operator equipment provided in this embodiment includes at least one processor 401 and a memory 402. Optionally, the operator equipment further includes a communication component 403. The processor 401, memory 402, and communication component 403 are connected via a bus.

[0145] In a specific implementation, at least one processor 401 executes computer execution instructions stored in memory 402, causing at least one processor 401 to perform the above-described method.

[0146] The specific implementation process of processor 401 can be found in the above method embodiments, and its implementation principle and technical effect are similar. It will not be repeated here.

[0147] In the above embodiments, it should be understood that the processor can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), etc. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in this invention can be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules within the processor.

[0148] The memory may include random access memory (RAM) and may also include non-volatile memory (NVM), such as at least one disk storage device.

[0149] The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc. For ease of illustration, the buses shown in the accompanying drawings are not limited to a single bus or a single type of bus.

[0150] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the above-described method.

[0151] This application also provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, implement the above-described method.

[0152] The aforementioned readable storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk. The readable storage medium can be any available medium accessible to a general-purpose or special-purpose computer.

[0153] An exemplary readable storage medium is coupled to a processor, enabling the processor to read information from and write information to the readable storage medium. Of course, the readable storage medium can also be a component of the processor. The processor and the readable storage medium can reside in an Application Specific Integrated Circuit (ASIC). Alternatively, the processor and the readable storage medium can exist as discrete components in the device.

[0154] The division of units is merely a logical functional division; in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be indirect coupling or communication connection through some interfaces, devices, or units, and may be electrical, mechanical, or other forms.

[0155] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0156] In addition, the functional units in the various embodiments of the present invention can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0157] If a function is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this invention, or the part that contributes to the prior art, or a part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0158] Those skilled in the art will understand that all or part of the steps of the above-described method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When executed, the program performs the steps of the above-described method embodiments; and the aforementioned storage medium includes various media capable of storing program code, such as ROM, RAM, magnetic disks, or optical disks.

[0159] Finally, it should be noted that other embodiments of the invention will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This invention is intended to cover any variations, uses, or adaptations of the invention that follow the general principles of the invention and include common knowledge or customary techniques in the art not disclosed herein, and is not limited to the precise structures described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of the invention is limited only by the appended claims.

Claims

1. A product information push method, characterized in that, Applied to carrier equipment, including: Receive a product push request sent by the user client, wherein the product push request carries the user account. Based on the user account, obtain the user type and the user's current product package information; If the user type is the same as the user's own network type, obtain the main account of the user account. Obtain the standard product package information to be pushed from the pre-built standard product package information database, based on the main account; The standard product package information to be pushed is split according to product type to obtain multiple product information; Based on the current product package information, obtain the initial product information to be pushed from the multiple product information; Based on the current product package information and the initial product information to be pushed, determine the final product information to be pushed for different product types; The final product information for the different product types is sent to the user terminal so that the user terminal can display the final product information according to the product type.

2. The method according to claim 1, characterized in that, The step of retrieving the standard product package information to be pushed from the pre-built standard product package information database according to the main account includes: Multiple standard product package information are obtained from the pre-built standard product package information database based on the main account; Obtain the province identifier of the main account; The province identifier for obtaining information on each standard product package; From the province identifiers of the multiple standard product package information, the standard product package information that is the same as the province identifier of the main account is identified as the standard product package information to be pushed.

3. The method according to claim 1, characterized in that, The step of obtaining initial product information to be pushed from the plurality of product information based on the current product package information includes: Based on the current product package information, and in accordance with the pre-built product push constraint rules, the initial product information to be pushed is obtained from the multiple product information.

4. The method according to claim 1, characterized in that, The step of determining the final product information to be pushed to different product types based on the current product package information and the initial product information to be pushed includes: Obtain multiple incremental pricing models corresponding to different product types; Using multiple incremental pricing models corresponding to different product types, and based on the current product package information and the initial product information to be pushed, multiple incremental prices for different product types are calculated. From multiple incremental pricing options for the different product types, obtain the lowest incremental price for each product type. Based on the minimum incremental pricing for each product type, the final product information to be pushed for each product type is determined.

5. The method according to any one of claims 1-4, characterized in that, After determining the final product information to be pushed for different product types, the process also includes: The first voice call parameters, the first traffic parameters, and the first broadband parameters are obtained from the final product information pushed out for the different product types. Obtain the second voice call parameters, second data traffic parameters, and second broadband parameters from the current product package information; If the first voice call parameter is greater than the second voice call parameter, then obtain the incremental voice call parameter; If the first flow parameter is greater than the second flow parameter, then obtain the incremental flow parameter; If the first broadband parameter is greater than the second broadband parameter, then the incremental broadband parameter is obtained; The incremental voice call parameters, the incremental data traffic parameters, and the incremental broadband parameters are sent to the user terminal so that the user terminal can display the incremental voice call parameters, the incremental data traffic parameters, and the incremental broadband parameters according to the product type.

6. The method according to any one of claims 1-4, characterized in that, Before receiving the product push request sent by the user terminal, the method further includes: Configure multiple service types for different preset business scenarios; Configure standard product package information for each business type to obtain a pre-built standard product package information database.

7. A product information push device, characterized in that, Applied to carrier equipment, including: The receiving module is used to receive product push requests sent by the user terminal, wherein the product push request carries the user account. The first acquisition module is used to acquire the user type and the user's current product package information based on the user account; The second acquisition module is used to acquire the main account of the user account when the user type is the local network type; The third acquisition module is used to obtain the standard product package information to be pushed from the pre-built standard product package information database according to the main account; The fourth acquisition module is used to split the standard product package information to be pushed according to product type to obtain multiple product information; The fifth acquisition module is used to acquire initial product information to be pushed from the multiple product information based on the current product package information; The determination module is used to determine the final product information to be pushed for different product types based on the current product package information and the initial product information to be pushed. The sending module is used to send the final product information of the different product types to the user terminal, so that the user terminal can display the final product information according to the product type.

8. A carrier equipment, characterized in that, include: Memory, used to store computer programs; A processor for executing the computer program to implement the method as described in any one of claims 1-6.

9. 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-6.

10. A computer program product, characterized in that, Includes a computer program that, when executed by a processor, implements the method described in any one of claims 1-6.

Images