Incoming call business card pushing method
By generating and pushing label preference data based on user operation behavior, the problem of inaccurate content of incoming call card push in the existing technology is solved, and promotion efficiency and user experience are improved.
Patent Information
- Application Number
- CN202411308661.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-09-19
- Publication Date
- 2024-12-13
AI Technical Summary
The existing call card push technology has failed to deeply explore the interactive behavior between call card merchants and users, resulting in uneven quality of push content and the inability to push the user's behavioral habits, resulting in low promotion efficiency.
By generating and pushing incoming call cards based on label preference data, users use their operation behavior of historical incoming call cards to generate label preference data, optimize the content and button layout of incoming call cards, and improve the accuracy and efficiency of push.
It realizes personalized optimization of incoming call business cards, improves promotion efficiency, ensures that the pushed content is more in line with user needs, and improves click-through rate and user experience.
Smart Images
Figure CN119135799A_ABST
Abstract
Description
Technical Field
[0001] The present application belongs to the field of communication technology, and specifically relates to a method for pushing incoming caller business cards. Background Art
[0002] Caller card display technology is mainly used in the field of communication technology, such as user calls and messaging services. In the messaging service field, it is limited to displaying the caller name, sender avatar and other information that identifies the sender. As for the solution of sending caller card to users, it only stops at sending the content of the pre-prepared caller card message to users, without deeply exploring the interactive behavior between the caller card merchant and the user, resulting in uneven content pushed to users by caller card customers, and the failure to push content based on customer behavior habits, resulting in low promotion efficiency of caller card. Summary of the invention
[0003] The embodiment of the present application provides a method for pushing incoming business cards, which can solve the problem that the interactive behavior between the incoming business card merchant and the user is not deeply explored, resulting in the uneven content pushed to the user by the incoming business card customer, and the failure to push content based on the customer's behavioral habits, resulting in low promotion efficiency of the incoming business card.
[0004] In the first aspect, an embodiment of the present application provides a method for pushing a caller's business card, which is applied to a server. The method includes: responding to a caller's business card push request sent by a client, generating a first caller's business card according to label preference data, wherein the label preference data includes the number of buttons in the first caller's business card and the content of the buttons, and the label preference data is generated according to the user's operation behavior on the second caller's business card; and pushing the first caller's business card to the user's terminal device.
[0005] In the second aspect, an embodiment of the present application provides a method for pushing a caller's business card, which is applied to a terminal device, and the method includes: receiving a first caller's business card pushed by a server, the first caller's business card being generated by the server based on label preference data, the label preference data including the number of buttons in the first caller's business card and the content of the buttons, and the label preference data being generated based on the user's operating behavior on a second caller's business card; displaying the first caller's business card based on the manner in which the server pushes the first caller's business card, wherein the manner in which the server pushes the first caller's business card includes an RCS message or a text message.
[0006] In the third aspect, an embodiment of the present application provides a device for pushing a caller's business card, which includes: a generation module, used to respond to a caller's business card push request sent by a client, and generate a first caller's business card according to label preference data, the label preference data including the number of buttons in the first caller's business card and the content of the buttons, and the label preference data is generated based on the user's operation behavior on the second caller's business card; a sending module, used to push the first caller's business card to the user's terminal device.
[0007] In the fourth aspect, an embodiment of the present application provides a device for pushing a caller's business card, the device comprising: a receiving module, used to receive a first caller's business card pushed by a server, the first caller's business card is generated by the server according to label preference data, the label preference data includes the number of buttons in the first caller's business card and the content of the buttons, the label preference data is generated according to the user's operation behavior on the second caller's business card; a display module, used to display the first caller's business card according to the way in which the server pushes the first caller's business card, wherein the way in which the server pushes the first caller's business card includes RCS message or SMS.
[0008] In a fifth aspect, an embodiment of the present application provides an electronic device, comprising a processor, a memory, and a program or instruction stored in the memory and executable on the processor, wherein the program or instruction, when executed by the processor, implements the steps of the method described in the first aspect or implements the steps of the method described in the second aspect.
[0009] In a sixth aspect, an embodiment of the present application provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, the steps of the method described in the first aspect or the steps of the method described in the second aspect are implemented.
[0010] In the seventh aspect, an embodiment of the present application provides a computer program product, which includes a computer program stored on a non-transitory computer-readable storage medium, and the computer program includes program instructions. When the program instructions are executed by a computer, the computer executes the steps of the method described in the first aspect or implements the steps of the method described in the second aspect.
[0011] In an embodiment of the present application, by responding to a caller card push request sent by a client, a first caller card is generated according to label preference data, the label preference data including the number of buttons in the first caller card and the content of the buttons, the label preference data being generated according to the user's operating behavior on the second caller card; the first caller card is pushed to the user's terminal device, and the first caller card is generated according to the label preference data generated by the user's operating behavior on the second caller card, and through interaction with the user, optimization of the caller card is achieved, which can improve the promotion efficiency of the caller card. BRIEF DESCRIPTION OF THE DRAWINGS Figure 1 It is a flowchart of a method for pushing a calling card provided in an embodiment of the present application; Figure 2 This is a schematic diagram of a process for activating a caller business card capability provided in an embodiment of the present application; Figure 3 This is a schematic diagram of a process for configuring a caller business card template provided in an embodiment of the present application; Figure 4 This is a schematic diagram of a caller business card message flow provided by an embodiment of the present application; Figure 5 It is a flowchart of another incoming call business card push method provided by an embodiment of the present application; Figure 6 This is a schematic diagram of a process for viewing an incoming caller's business card provided in an embodiment of the present application; Figure 7 This is another schematic diagram of the process of viewing incoming caller business cards provided in an embodiment of the present application; Figure 8 It is a structural schematic diagram of a device for pushing incoming business cards provided in an embodiment of the present application; Fig. 9 It is a structural schematic diagram of another incoming call business card push device provided in an embodiment of the present application; Fig.10 It is a structural schematic diagram of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION
[0012] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.
[0013] The terms "first", "second", etc. in the specification and claims of the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable under appropriate circumstances, so that the embodiments of the present application can be implemented in an order other than those illustrated or described here, and the objects distinguished by "first", "second", etc. are generally of one type, and the number of objects is not limited. For example, the first object can be one or more. In addition, "and / or" in the specification and claims represents at least one of the connected objects, and the character " / " generally indicates that the objects associated with each other are in an "or" relationship.
[0014] The following is a detailed description of the incoming call business card push method provided by the embodiment of the present application through specific embodiments and application scenarios in conjunction with the accompanying drawings.
[0015] Figure 1 A method for pushing a caller business card provided by an embodiment of the present application is shown, and the method can be executed by a server. In other words, the method can be executed by software or hardware installed on the server, and the method includes the following steps: Step 102: In response to the incoming caller business card push request sent by the client, a first incoming caller business card is generated according to the tag preference data.
[0016] Specifically, the embodiments of the present application can be applicable to scenarios where B-end customers such as enterprises and merchants initiate service or marketing calls to their C-end users, and are applicable to various industries such as express logistics, transportation, banking and insurance. Users can clearly understand the identity of the caller, the intention of the call, etc. through the caller card message, and further promote the extension of other businesses. In an embodiment of the present application, after receiving the caller card push request sent by the client, the electronic device can generate a first caller card according to the label preference data, wherein the label preference data includes the number of buttons and the content of the buttons in the first caller card, and the label preference data is generated according to the user's operation behavior on the second caller card, and the second caller card can be a historical caller card, that is, a caller card that has been sent to the terminal device.
[0017] In one implementation, before generating the first incoming caller card according to the tag preference data in response to the incoming caller card push request sent by the client, the method further includes: Obtain the customer tag generated when the client is registered, wherein the customer tag includes the customer's information; obtain the template tag generated when the client configures the incoming call business card template; generate a user behavior tag based on the user's operation behavior on the second incoming call business card; generate the tag preference data based on the customer tag, the template tag and the user behavior tag.
[0018] Specifically, the embodiment of the present application includes a caller name card capability activation process, such as Figure 2 As shown in the figure, the process of activating the caller ID card capability mainly includes the following steps: The electronic device may include a voice notification module, a calling card module, a message module, and a data tag module. When a calling customer applies for activation of a calling card, the voice notification module sends the customer information when the client is registered to the calling card module, and the calling card module sends the customer information when the client is registered and the authorized calling card notification to the message module. After waiting for the administrator to approve the application, the message module returns the customer information to the calling card module, and the calling card module returns the merchant information to the voice notification module, and the voice notification module returns the activation result to the client.
[0019] The process of activating the caller ID card capability is mainly the process of the calling customer registering and obtaining the caller ID card capability. During the registration process, the customer needs to provide information such as the organization name, caller number, city, business license, etc. At the same time, the electronic device provides the ability to authenticate the customer's identity security so that the receiving user can better identify whether the calling customer is trustworthy. After the client successfully registers, a customer tag will be generated in the data tag module to reserve the message content of the subsequent push caller ID card.
[0020] The present application embodiment also includes a process for configuring a caller business card template, such as Figure 3 As shown in the figure, the process of configuring the incoming call card template includes the following steps: The client requests the voice notification module to configure the incoming caller card template, and the voice notification module sends a request to configure the incoming caller card template to the calling card module. The calling card module sends a request to configure the incoming caller card template to the message module, and the message module returns the configuration application information to the client. After the customer's template information is approved, the calling card module and the voice notification module complete the synchronization of template information. The calling card module sends a template tag to the data tag module, and the data tag module returns the creation result to the host card module.
[0021] The main purpose of configuring the caller card template process is to provide the calling client with the function of setting a personalized caller card. By setting basic information such as the purpose of each voice call and the call description, the caller can better understand the content of the call. The caller card module will synchronize the template data to the data label module to generate a template label corresponding to the original call template. The template label is a label corresponding to the template generated when the template is created based on the keywords contained in the template itself and the label words set by the user for the template.
[0022] The embodiment of the present application also includes a process of sending a caller business card message, such as Figure 4 As shown, the incoming call business card message process includes the following processes: Taking the push of the second incoming caller card as an example, the client sends a voice notification to the voice notification module, the voice notification module initiates a voice call to the user, and at the same time the voice notification module initiates a request to send an incoming caller card message to the incoming caller card module.
[0023] In an implementation manner, before generating the first incoming call card, the method further includes: encapsulating the long link to be sent to the terminal device into a short link, wherein the first incoming call card carries the short link.
[0024] Specifically, in the caller card module, the long link to be sent to the terminal device can be encapsulated into a short link, and then the data tag module is requested for the tag preference data of this transmission. Then the caller card module generates a second caller card according to the tag preference data, and sends the second caller card to the user's user terminal, and the message module performs receipt processing. In this way, the message displayed when the message reaches the recipient user is the accurate push content. After receiving the second incoming call business card, the user can operate the incoming call business card. The embodiment of the present application will record the user's operation behavior on the second business card and generate a user behavior tag. The embodiment of the present application provides a message content generation algorithm. The message content generation algorithm is an algorithm that dynamically generates tag preference data based on customer tags, template tags, and user behavior tags. Through this message content generation algorithm, tag preference data can be generated based on the recorded customer tags, template tags, and user behavior tags.
[0025] In one implementation, the user behavior tag includes the number of buttons and the content of the buttons, and generating the first incoming caller's business card based on the tag preference data includes: generating image content of the first incoming caller's business card based on the customer tag; generating text content of the first incoming caller's business card based on the template tag; generating buttons of the first incoming caller's business card based on the number of buttons and the content of the buttons.
[0026] Specifically, the user behavior tag includes the number of buttons and the content of the buttons in the caller card, and after obtaining the customer tag, template tag and user behavior tag, the image content of the first caller card can be generated according to the customer tag, the text content of the first caller card can be generated according to the template tag, and the buttons of the first caller card can be generated according to the number of buttons and the content of the buttons. For the scenario of ordinary SMS, the corresponding image content, text content and button elements are displayed in the H5 page.
[0027] Step 104: Push the first incoming caller's business card to the user's terminal device.
[0028] Specifically, after the first incoming caller name card is generated, the first incoming caller name card may be pushed to the user's terminal device.
[0029] The caller card push method provided in the embodiment of the present application generates a first caller card according to label preference data in response to a caller card push request sent by a client, wherein the label preference data includes the number of buttons in the first caller card and the content of the buttons, and the label preference data is generated according to the user's operation behavior on the second caller card; the first caller card is pushed to the user's terminal device, and the first caller card is generated according to the label preference data generated by the user's operation behavior on the second caller card. Through interaction with the user, the caller card is optimized, the promotion efficiency of the caller card can be improved, and the problem of not deeply exploring the interaction behavior between the merchant and the user of the caller card, resulting in uneven content pushed to the user by the caller card customer, and failing to push content based on the customer's behavior habits, resulting in low promotion efficiency of the caller card.
[0030] In one implementation, generating a user behavior tag according to the user's operation behavior on the second incoming caller's business card includes: The user behavior tag is generated according to the number of times the user clicks the button in the second incoming call business card and the button click expected value provided by the client.
[0031] Specifically, in an embodiment of the present application, after the second caller's business card is sent to the terminal device, each time the user clicks the button, the user's behavior will be recorded. Different user behavior labels are formed based on parameters such as the number of times the user clicks the button in the second caller's business card, the expected value of the button click provided by the client, the type of service provided by the button, and the click time. The content of the caller's business card push is optimized, so that the caller's business card received by the user is more in line with the user's needs and the click rate of the caller's business card is improved.
[0032] In one implementation, the user behavior tag includes the number of buttons and the content of the buttons, and generating the user behavior tag according to the number of times the user clicks the button in the second incoming call card and the button click expected value provided by the client includes: The content value score of each content is calculated based on the number of times all users click on similar buttons, the number of times users click on similar buttons in the second incoming call business card, and the expected value of button clicks; the content of each button is determined based on the content value score of each content; the number of buttons is determined based on whether the user clicks on buttons with similar customer labels, whether the user clicks on buttons with similar template labels, and the content value scores of each content.
[0033] Specifically, the content value of the button will be determined by calculating the scores of each content value. The content with the highest score will be ranked first. The content value with the highest score will become the first button, the content value with the second highest score will become the second button, and the content value with the third highest score will become the third button (the second and third will be displayed based on the number of buttons), and so on.
[0034] The content value of the button will be determined based on the weighted value of the number of times all users click on similar buttons, the weighted value of the number of times users click on similar buttons in the second caller card, the weighted value of the expected value of the button click set by the customer, and the setting above the button display threshold value, to determine which button and how many buttons need to be displayed in the user's message content. Among them, the weighted coefficients of the three values will be dynamically adjusted again according to the actual number of button clicks, which can further improve the button click rate.
[0035] The content is set to be ButtonScore, the number of times all users click on the same button is C1, the number of times all users click is A1, the number of times users click on the same button in the second incoming call card is C2, the number of times users click on the same button in the second incoming call card is A2, and the customer sets the expected value of clicking the button E. The button display threshold can be set by default. If ButtonScore exceeds 1, then: ButtonScore=C1*C1 / A1+C2*C2 / A2+E*(C1 / A1+C2 / A2) The number of buttons in the first incoming call business card is determined according to whether the user clicks on a button with a similar customer label, whether the user clicks on a button with a similar template label, and the content value score of each content.
[0036] In one implementation, determining the number of buttons according to whether the user clicks on buttons of similar customer tags, whether the user clicks on buttons of similar template tags, and content value scores of each content includes: If the user does not click on the button of the same type of customer tag, the number of buttons is one; if the user clicks on the button of the same type of customer tag, the user does not click on the button of the same type of template tag, and the content value with the second highest content value score does not exceed the preset threshold, the number of buttons is determined to be one; if the user clicks on the button of the same type of customer tag, the user does not click on the button of the same type of template tag, and the content value with the second highest content value score exceeds the preset threshold, the number of buttons is determined to be two.
[0037] Specifically, determine whether the user has clicked on a button with a similar customer label. If the user has not clicked on a button with a similar customer label, the number of buttons is one, that is, one button (the content value with the highest score) is displayed in the caller card; if yes, continue to determine.
[0038] Determine whether the user has clicked a button of the same template label. If the user has not clicked a button of the same template label, determine whether the second highest content value exceeds the preset threshold of the display threshold. If not, determine that the number of buttons is one, and display one button (the content value with the highest score) on the caller card. If the second highest content value exceeds the preset threshold, determine that the number of buttons in the caller card is two, and display two buttons (the content values with the highest scores); In one implementation, determining the number of buttons according to whether the user clicks on buttons of similar customer tags, whether the user clicks on buttons of similar template tags, and content value scores of each content includes: When the user clicks a button of a similar customer tag, the user clicks a button of a similar template tag and the second highest and third highest content values do not exceed a preset threshold, the number of the button is determined to be one.
[0039] Specifically, determine whether the user has clicked on a button with a similar customer label. If the user has not clicked on a button with a similar customer label, the number of buttons is one, that is, one button (the content value with the highest score) is displayed in the caller's business card. If yes, continue to determine whether the user has clicked on a button with a similar template label. If the user clicks on a button with a similar customer label, the user clicks on a button with a similar template label and the second highest and third highest content values do not exceed the preset threshold, determine that the number of buttons is one, that is, one button (the content value with the highest score) is displayed in the caller's business card.
[0040] In one implementation, determining the number of buttons according to whether the user clicks on buttons of similar customer tags, whether the user clicks on buttons of similar template tags, and content value scores of each content includes: When a user clicks a button of a similar customer tag, or a user clicks a button of a similar template tag and the second highest and third highest content values have content value scores exceeding a preset threshold, the number of buttons is determined based on the content values of the second highest and third highest content values that exceed the preset threshold.
[0041] Specifically, when a user clicks a button of a similar customer tag, or a user clicks a button of a similar template tag, and the second highest and third highest content values have content values that exceed the preset threshold, the number of buttons is determined based on the content value that exceeds the preset threshold among the second highest and third highest content values. That is, if a user has clicked a button of a similar template tag, it is determined whether the second and third highest content values exceed the preset threshold of the display threshold. If they do, the button that exceeds the preset threshold is displayed (if both the second and third values exceed, 3 buttons are displayed, and if only the second value exceeds, 2 buttons are displayed); if not, 1 button is displayed (the content value with the highest score).
[0042] As user behaviors continue to accumulate, user behavior tags will be dynamically updated, thereby driving the update of tag preference data, thereby achieving automatic optimization of caller business card push content and increasing user clicks.
[0043] Figure 5 Another incoming call business card push method provided by an embodiment of the present application is shown, and the method can be executed by a terminal device. In other words, the method can be executed by software or hardware installed in the terminal device, and the method includes the following steps: Step 502: Receive a first incoming caller card pushed by the server.
[0044] Specifically, the user's terminal device can receive a first caller business card pushed by a server. The first caller business card is generated by the server based on label preference data. The label preference data includes the number of buttons in the first caller business card and the content of the buttons, and the label preference data is generated based on the user's operation behavior on the second caller business card.
[0045] Step 504: Display the first incoming caller's business card according to the manner in which the server pushes the first incoming caller's business card.
[0046] Specifically, the server pushes the first incoming caller's business card in the form of RCS messages or text messages. The first incoming caller's business card received by the user's terminal device is divided into RCS messages (i.e., 5G messages) and ordinary terminal messages (i.e., ordinary text messages). If the user's terminal device is an RCS terminal device, the first incoming caller's business card is pushed to the terminal device via the RCS chatbot in the form of an RCS message. If the user's terminal device is an ordinary terminal, the first incoming caller's business card is implemented through the H5 business card in the text message. Therefore, the timing diagram of the process of viewing the incoming caller's business card in the embodiment of the present application is divided into two types, such as Figure 6 It is shown that the terminal device receives the RCS message. Figure 7 It is shown that the terminal device receives a normal SMS message.
[0047] like Figure 6 As shown, after receiving the first incoming caller card message, the terminal device can display the first incoming caller card. The user can click on the card element in the corresponding chatbot message dialog box, and the message module will automatically perform token authentication and trigger the corresponding behavior of the incoming caller card element. The behavior data will be passed to the data label module through the incoming caller card module. The data label module will record the user behavior label and update the label preference data according to the user behavior number label. For multiple different caller numbers, RCS messages can realize the display of messages for each incoming call in the same message dialog box.
[0048] like Figure 7As shown, after receiving the SMS of the first incoming caller card, the terminal device can display the first incoming caller card. The user can click on the link in the SMS, and the SMS module will automatically convert the short link into a long link, and then obtain the token through the authentication system, query the caller information in the incoming caller card system, and display the detailed page of the incoming caller card to the terminal device of the SMS recipient. The behavior data of the user clicking on the page element will be passed to the data label module through the incoming caller card module. The data label module will record the user behavior label and update the label preference data according to the user behavior label. The content of the SMS message will be self-optimized according to the user's behavior of clicking on the incoming caller card H5 page, and the content of the incoming caller card H5 page will also be optimized accordingly, so as to achieve the same effect as the incoming caller card of the RCS terminal.
[0049] In this way, by receiving the first incoming call business card pushed by the server, the first incoming call business card is generated by the server according to the label preference data, the label preference data includes the number of buttons and the content of the buttons in the first incoming call business card, and the label preference data is generated according to the user's operation behavior on the second incoming call business card; according to the way the server pushes the first incoming call business card, the first incoming call business card is displayed, wherein the way the server pushes the first incoming call business card includes RCS message or SMS, and the incoming call business card can implement different message push methods according to different terminal types, and display different business card contents, distinguish different terminal types to implement different types of message sending, thereby achieving coverage of various terminals. It is free from the limitations of hardware such as terminal device systems and models. The display of the incoming call business card is not affected by the change of the terminal. When the user changes the terminal used, the incoming call business card message received by the non-terminal can still be viewed. Different terminal types implement different message push methods, RCS terminal messages receive 5G messages, and ordinary terminals receive traditional SMS. Unlike the current way that the display of the incoming call business card needs to rely on the transformation of the terminal system or the embedding of SDK, the embodiment of the present application does not need to transform the terminal, that is, the calling business card can be displayed, and the personalized push does not need to update the terminal itself.
[0050] The following is an example of the application of the embodiment of the present application in the service. Attracting new riders: The food delivery platform attracts new riders from registered users, and informs users through the caller card message that the purpose of the call is to fill out a questionnaire and submit it to become a full-time rider.
[0051] Transportation: After the car owner confirms the taxi information with the customer through a voice call, the license plate number, color, brand and other information will be sent to the user to prevent the user from ignoring the car owner's arrival information. At the same time, the user can quickly submit relevant ride suggestions and opinions.
[0052] Express logistics: After the express is delivered to Fengchao or the post station, the consignee will be notified by voice to pick it up, and a caller card message will be sent at the same time, so that the user can quickly check the express information.
[0053] Property notification: The property conveys property management notifications through voice notifications, such as notifying owners of temporary water and power outages, events, etc., and sends caller business card messages at the same time to ensure that the owners are reached and avoid missing notifications.
[0054] Banking and insurance: Salespersons inform users of banking / insurance product information through voice notifications, and send caller business card messages to inform users of relevant product handling methods, allowing users to handle business in a timely manner through messages.
[0055] It should be noted that the execution subject of the incoming business card push method provided in the embodiment of the present application may be an incoming business card push device, or a control module in the incoming business card push device for executing the incoming business card push method. In the embodiment of the present application, the incoming business card push device executing the incoming business card push method is taken as an example to illustrate the incoming business card push device provided in the embodiment of the present application.
[0056] Figure 8 Schematic diagram of the structure of the incoming business card push device according to the embodiment of the present application. Figure 8 As shown, the incoming call business card pushing device 800 includes: a generating module 810 and a sending module 820 .
[0057] The generation module 810 is used to respond to the caller ID push request sent by the client, and generate a first caller ID according to the label preference data, wherein the label preference data includes the number of buttons in the first caller ID and the content of the buttons, and the label preference data is generated according to the user's operation behavior on the second caller ID; the sending module 820 is used to push the first caller ID to the user's terminal device.
[0058] In one implementation, the generation module 810 is also used to obtain the customer tag generated when the client is registered, wherein the customer tag includes the customer's information; obtain the template tag generated when the client configures the incoming call business card template; generate a user behavior tag based on the user's operation behavior on the second incoming call business card; and generate the tag preference data based on the customer tag, the template tag and the user behavior tag.
[0059] In one implementation, the generating module 810 is used to generate the user behavior tag according to the number of times the user clicks the button in the second incoming call business card and the button click expected value provided by the client.
[0060] In one implementation, the generation module 810 is used to calculate the content value score of each content based on the number of times all users click on similar buttons, the number of times users click on similar buttons in the second incoming call business card, and the expected value of button clicks; determine the content of each button based on the content value score of each content; determine the number of buttons based on whether the user clicks on a button with a similar customer label, whether the user clicks on a button with a similar template label, and the content value score of each content.
[0061] In one implementation, the generation module 810 is used to determine that the number of buttons is one when the user does not click on the button of the same type of customer tag; to determine that the number of buttons is one when the user clicks on the button of the same type of customer tag, the user does not click on the button of the same type of template tag, and the content value with the second highest content value score does not exceed a preset threshold; and to determine that the number of buttons is two when the user clicks on the button of the same type of customer tag, the user does not click on the button of the same type of template tag, and the content value with the second highest content value score exceeds the preset threshold.
[0062] In one implementation, the generation module 810 is used to determine that the number of buttons is one when a user clicks a button of a similar customer tag, a user clicks a button of a similar template tag and the second highest and third highest content values do not exceed a preset threshold.
[0063] In one implementation, the generation module 810 is used to determine the number of buttons based on the content values that exceed the preset threshold among the second highest and third highest content values when a user clicks a button of a similar customer tag or a user clicks a button of a similar template tag and the second highest and third highest content values have content value scores that exceed a preset threshold.
[0064] In one implementation, the generating module 810 is further configured to encapsulate the long link to be sent to the terminal device into a short link, and the first incoming call card carries the short link.
[0065] In one implementation, the generation module 810 is used to generate the image content of the first incoming caller's business card according to the customer tag; generate the text content of the first incoming caller's business card according to the template tag; and generate the buttons of the first incoming caller's business card according to the number of buttons and the content of the buttons.
[0066] The incoming business card push device in the embodiment of the present application can be a device, or a component, integrated circuit, or chip in a terminal. The device can be a mobile electronic device or a non-mobile electronic device. The embodiment of the present application is not specifically limited.
[0067] The incoming call business card push device in the embodiment of the present application may be a device with an operating system. The operating system may be an Android operating system, an iOS operating system, or other possible operating systems, which are not specifically limited in the embodiment of the present application.
[0068] The incoming call business card push device provided in the embodiment of the present application can achieve Figures 1 to 4 To avoid repetition, the various processes implemented by the method embodiment are not described here.
[0069] Fig. 9 Schematic diagram of the structure of the incoming business card push device according to the embodiment of the present application. Fig. 9 As shown, the incoming business card pushing device 900 includes: a receiving module 910 and a display module 920 .
[0070] A receiving module 910 is configured to receive a first incoming caller business card pushed by a server, wherein the first incoming caller business card is generated by the server according to label preference data, wherein the label preference data includes the number of buttons in the first incoming caller business card and the content of the buttons, and the label preference data is generated according to the user's operation behavior on a second incoming caller business card; The display module 920 is used to display the first incoming caller's business card according to the manner in which the server pushes the first incoming caller's business card, wherein the manner in which the server pushes the first incoming caller's business card includes an RCS message or a text message.
[0071] The incoming business card push device in the embodiment of the present application can be a device, or a component, integrated circuit, or chip in a terminal. The device can be a mobile electronic device or a non-mobile electronic device. The embodiment of the present application is not specifically limited.
[0072] The incoming call business card push device in the embodiment of the present application may be a device with an operating system. The operating system may be an Android operating system, an iOS operating system, or other possible operating systems, which are not specifically limited in the embodiment of the present application.
[0073] The incoming call business card push device provided in the embodiment of the present application can achieve Figures 5 to 7 To avoid repetition, the various processes implemented by the method embodiment are not described here.
[0074] Alternatively, if Fig.10As shown, an embodiment of the present application further provides an electronic device 1000, including a processor 1001 and a memory 1002, wherein the memory 1002 stores a program or instruction that can be executed on the processor 1001, and the program or instruction, when executed by the processor 1001, achieves: in response to a caller card push request sent by a client, generating a first caller card according to label preference data, wherein the label preference data includes the number of buttons in the first caller card and the content of the buttons, and the label preference data is generated according to the user's operation behavior on the second caller card; and pushing the first caller card to the user's terminal device.
[0075] In one implementation, before generating a first incoming caller business card in response to a caller business card push request sent by a client according to tag preference data, a customer tag generated when the client is registered is obtained, the customer tag including customer information; a template tag generated when the client configures an incoming caller business card template is obtained; a user behavior tag is generated according to the user's operation behavior on the second incoming caller business card; and the tag preference data is generated according to the customer tag, the template tag and the user behavior tag.
[0076] In one implementation, the user behavior tag is generated according to the number of times the user clicks a button in the second incoming call business card and an expected value of button clicks provided by the client.
[0077] In one implementation, the content value score of each content is calculated based on the number of times all users click on similar buttons, the number of times users click on similar buttons in the second incoming call business card, and the expected value of button clicks; the content of each button is determined based on the content value scores of each content; the number of buttons is determined based on whether the user clicks on buttons with similar customer labels, whether the user clicks on buttons with similar template labels, and the content value scores of each content.
[0078] In one implementation, when the user does not click on a button of a similar customer tag, the number of buttons is one; when the user clicks on a button of a similar customer tag, the user does not click on a button of a similar template tag, and the content value with the second highest content value score does not exceed a preset threshold, the number of buttons is determined to be one; when the user clicks on a button of a similar customer tag, the user does not click on a button of a similar template tag, and the content value with the second highest content value score exceeds the preset threshold, the number of buttons is determined to be two.
[0079] In one implementation, when a user clicks a button of a similar customer tag, a user clicks a button of a similar template tag and the second highest and third highest content values do not exceed a preset threshold, the number of buttons is determined to be one.
[0080] In one implementation, when a user clicks a button of a similar customer tag, or a user clicks a button of a similar template tag and the second highest and third highest content values have content value scores exceeding a preset threshold, the number of buttons is determined based on the content values of the second highest and third highest content values that exceed the preset threshold.
[0081] In one implementation, the image content of the first incoming caller's business card is generated according to the customer tag; the text content of the first incoming caller's business card is generated according to the template tag; and the buttons of the first incoming caller's business card are generated according to the number of buttons and the button contents.
[0082] In one implementation, before generating the image content of the first incoming caller's business card according to the customer tag, the long link to be sent to the terminal device is encapsulated into a short link, and the first incoming caller's business card carries the short link.
[0083] Alternatively, when the program or instruction is executed by the processor 1001, it is implemented: receiving a first caller's business card pushed by a server, the first caller's business card is generated by the server according to label preference data, the label preference data includes the number of buttons in the first caller's business card and the content of the buttons, and the label preference data is generated according to the user's operation behavior on the second caller's business card; displaying the first caller's business card according to the way in which the server pushes the first caller's business card, wherein the way in which the server pushes the first caller's business card includes RCS message or SMS.
[0084] The specific execution steps can refer to the various steps of the above-mentioned caller business card push method embodiment, and can achieve the same technical effect. To avoid repetition, they will not be repeated here.
[0085] It should be noted that the electronic devices in the embodiments of the present application include: servers, terminals, or other devices except terminals.
[0086] The above electronic device structure does not constitute a limitation on the electronic device. The electronic device may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently. For example, the input unit may include a graphics processing unit (GPU) and a microphone, and the display unit may be configured with a display panel in the form of a liquid crystal display, an organic light-emitting diode, etc. The user input unit includes a touch panel and at least one of other input devices. The touch panel is also called a touch screen. Other input devices may include, but are not limited to, a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, and a joystick, which will not be repeated here.
[0087] The memory can be used to store software programs and various data. The memory may mainly include a first storage area for storing programs or instructions and a second storage area for storing data, wherein the first storage area may store an operating system, an application program or instructions required for at least one function (such as a sound playback function, an image playback function, etc.), etc. In addition, the memory may include a volatile memory or a non-volatile memory, or the memory may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. Volatile memory can be random access memory (RAM), static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM) and direct memory bus random access memory (DRRAM).
[0088] The processor may include one or more processing units; optionally, the processor integrates an application processor and a modem processor, wherein the application processor mainly processes operations related to the operating system, user interface, and application programs, and the modem processor mainly processes wireless communication signals, such as a baseband processor. It is understandable that the modem processor may not be integrated into the processor.
[0089] An embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, each process of the above-mentioned incoming call business card push method embodiment is implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.
[0090] The processor is the processor in the electronic device described in the above embodiment. The readable storage medium includes a computer readable storage medium, such as ROM, RAM, magnetic disk or optical disk.
[0091] An embodiment of the present application also provides a computer program product, which includes a computer program stored on a non-transitory computer-readable storage medium, and the computer program includes program instructions. When the program instructions are executed by a computer, the computer executes the various processes of the embodiment of the above-mentioned incoming call business card push method, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.
[0092] It should be noted that, in this article, the terms "comprise", "include" or any other variant thereof are intended to cover non-exclusive inclusion, so that the process, method, article or device including a series of elements includes not only those elements, but also includes other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise one..." do not exclude the presence of other identical elements in the process, method, article or device including the element. In addition, it should be pointed out that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in reverse order according to the functions involved, for example, the described method may be performed in an order different from that described, and various steps may also be added, omitted, or combined. In addition, the features described with reference to certain examples may be combined in other examples.
[0093] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a computer software product, which is stored in a storage medium (such as ROM / RAM, a magnetic disk, or an optical disk), and includes a number of instructions for enabling a terminal (which can be a mobile phone, a computer, a server, or a network device, etc.) to execute the methods described in each embodiment of the present application.
[0094] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of the present application, ordinary technicians in this field can also make many forms without departing from the purpose of the present application and the scope of protection of the claims, all of which are within the protection of the present application.
Claims
1. A method for pushing a calling card, characterized in that: Applicable to servers, including: In response to a caller card push request sent by a client, generating a first caller card according to label preference data, wherein the label preference data includes the number of buttons in the first caller card and the content of the buttons, and the label preference data is generated according to the user's operation behavior on the second caller card; Push the first incoming caller name card to the user's terminal device.
2. The method according to claim 1, characterized in that Before generating the first incoming caller card according to the tag preference data in response to the incoming caller card push request sent by the client, the method further includes: Obtaining a client tag generated when the client registers, wherein the client tag includes client information; Obtain the template tag generated when the client configures the incoming call business card template; generating a user behavior tag according to the user's operation behavior on the second incoming call business card; The tag preference data is generated according to the customer tag, the template tag and the user behavior tag.
3. The method according to claim 2, characterized in that The generating a user behavior tag according to the user's operation behavior on the second incoming call business card includes: The user behavior tag is generated according to the number of times the user clicks the button in the second incoming call business card and the button click expected value provided by the client.
4. The method according to claim 3, characterized in that The user behavior tag includes the number of buttons and the content of the buttons. The generating of the user behavior tag according to the number of times the user clicks the buttons in the second incoming call card and the button click expected value provided by the client includes: Calculate the content value score of each content according to the number of times all users click on the same type of buttons, the number of times users click on the same type of buttons in the second incoming call business card, and the button click expected value; Determining the content of each button according to the content value score of each content; The number of the buttons is determined according to whether the user clicks on buttons of similar customer tags, whether the user clicks on buttons of similar template tags, and the content value scores of each content.
5. The method according to claim 4, characterized in that The determining the number of the buttons according to whether the user clicks on buttons of the same type of customer tags, whether the user clicks on buttons of the same type of template tags, and the content value scores of each content includes: In the case where the user does not click on a button with a similar customer label, the number of the button is one; In the case where the user clicks a button of a similar customer tag, the user does not click a button of a similar template tag, and the content value of the second highest content value score does not exceed a preset threshold, determining that the number of the button is one; When the user clicks a button of a similar customer tag, the user does not click a button of a similar template tag, and the content value with the second highest content value score exceeds the preset threshold, it is determined that the number of the buttons is two.
6. The method according to claim 4, characterized in that The determining the number of the buttons according to whether the user clicks on buttons of the same type of customer tags, whether the user clicks on buttons of the same type of template tags, and the content value scores of each content includes: When the user clicks a button of a similar customer tag, the user clicks a button of a similar template tag and the second highest and third highest content values do not exceed a preset threshold, the number of the button is determined to be one.
7. The method according to claim 4, characterized in that The determining the number of the buttons according to whether the user clicks on buttons of the same type of customer tags, whether the user clicks on buttons of the same type of template tags, and the content value scores of each content includes: When a user clicks a button of a similar customer tag, or a user clicks a button of a similar template tag and the second highest and third highest content values have content value scores exceeding a preset threshold, the number of buttons is determined based on the content values of the second highest and third highest content values that exceed the preset threshold.
8. The method according to claim 2, characterized in that: The user behavior tag includes the number of buttons and the content of the buttons, and generating a first incoming call card according to the tag preference data includes: Generating the image content of the first incoming caller's business card according to the customer tag; Generate the text content of the first incoming caller's business card according to the template tag; A button of the first incoming caller business card is generated according to the number of the buttons and the content of the buttons.
9. The method according to claim 1, characterized in that: Before generating the first incoming caller name card, the method further includes: The long link to be sent to the terminal device is encapsulated into a short link, and the first incoming call card carries the short link.
10. A method for pushing a calling card, characterized in that: Applied to terminal equipment, including: Receive a first incoming call business card pushed by a server, where the first incoming call business card is generated by the server according to label preference data, where the label preference data includes the number of buttons in the first incoming call business card and the content of the buttons, and the label preference data is generated according to the user's operation behavior on a second incoming call business card; The first incoming caller's business card is displayed according to the manner in which the server pushes the first incoming caller's business card, wherein the manner in which the server pushes the first incoming caller's business card includes an RCS message or a text message.