WO2020024435A1 - 一种信息处理方法和系统 - Google Patents

一种信息处理方法和系统 Download PDF

Info

Publication number
WO2020024435A1
WO2020024435A1 PCT/CN2018/110587 CN2018110587W WO2020024435A1 WO 2020024435 A1 WO2020024435 A1 WO 2020024435A1 CN 2018110587 W CN2018110587 W CN 2018110587W WO 2020024435 A1 WO2020024435 A1 WO 2020024435A1
Authority
WO
WIPO (PCT)
Prior art keywords
scenario
user data
interrupted
background server
outbound
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2018/110587
Other languages
English (en)
French (fr)
Inventor
蔡灵敏
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Ping An Technology Shenzhen Co Ltd
Original Assignee
Ping An Technology Shenzhen Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Ping An Technology Shenzhen Co Ltd filed Critical Ping An Technology Shenzhen Co Ltd
Publication of WO2020024435A1 publication Critical patent/WO2020024435A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M3/00—Automatic or semi-automatic exchanges
    • H04M3/42—Systems providing special services or facilities to subscribers
    • H04M3/436—Arrangements for screening incoming calls, i.e. evaluating the characteristics of a call before deciding whether to answer it

Definitions

  • the present application relates to the field of computer technology, and in particular, to an information processing method and system.
  • the present application provides an information processing method and system to interrupt users who do not need to make outgoing calls.
  • this application provides an information processing method.
  • the method is applied to a system including a background server and an outbound call platform.
  • the method includes:
  • the background server obtains user data to be interrupted
  • the outbound platform performs an automatic outbound call according to the updated outbound user list.
  • the present application provides an information processing system, which includes a background server and an outbound platform;
  • the background server is configured to obtain user data to be interrupted
  • the background server configured to push the user data to the outbound platform
  • the outbound calling platform is configured to update an outbound calling user list according to the received user data
  • the outbound calling platform is configured to perform automatic outbound calling according to the updated outbound user list.
  • an embodiment of the present application provides a computer device including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the first Aspect of the method.
  • an embodiment of the present application provides a computer non-volatile readable storage medium, which is characterized in that the computer non-volatile readable storage medium includes a stored program, and where the program is controlled when the program is run
  • the device on which the computer non-volatile readable storage medium is located executes the method according to the first aspect.
  • the background server pushes the user data to the outbound platform, and the outbound platform updates the outbound user list according to the user data, so that the outbound platform can update according to the update.
  • the outgoing call user list automatically performs outgoing calls. Since the user data to be interrupted corresponds to users who do not need to make outgoing calls again, the outgoing call platform makes outgoing calls based on the outgoing call user list. Therefore, the outgoing call platform makes external calls based on the user data to be interrupted. After the calling user list is updated, the updated user list no longer includes users corresponding to the user data to be interrupted, so the above method can be used to interrupt users who do not need to be called again.
  • FIG. 1 is a schematic flowchart of an information processing method according to an embodiment of the present application
  • FIG. 2 is a schematic flowchart of another information processing method according to an embodiment of the present application.
  • FIG. 3 is a schematic structural diagram of an information processing system according to an embodiment of the present application.
  • FIG. 4 is a schematic flowchart of another information processing method according to an embodiment of the present application.
  • FIG. 5 is a schematic structural diagram of a background server according to an embodiment of the present application.
  • FIG. 6 is a schematic flowchart of another information processing method according to an embodiment of the present application.
  • FIG. 7 is a schematic structural diagram of an outbound call platform according to an embodiment of the present application.
  • FIG. 8 is a schematic structural diagram of another background server according to an embodiment of the present application.
  • FIG. 9 is a schematic structural diagram of another outbound calling platform provided by an embodiment of the present application.
  • FIG. 1 is a schematic flowchart of an information processing method according to an embodiment of the present application. The method is applied to a system including a background server and an outbound call platform. The method includes the following steps:
  • the background server obtains user data to be interrupted.
  • the background server pushes user data to the outbound platform.
  • the outbound calling platform updates the outbound calling user list according to the received user data.
  • the outbound platform performs an automatic outbound call according to the updated outbound user list.
  • the user data to be interrupted corresponds to a user who does not need to make an outbound call, that is, the user data to be interrupted is user data that no longer performs an automatic outbound call.
  • the outbound platform does not Then, an outbound call is performed to the user corresponding to the above user data, and the background server sends the above user data to the outbound platform, so that the outbound platform can update the outbound user list according to the above user data, and the outbound platform can then update the user based on the updated user.
  • the list performs automatic outbound calls.
  • the outbound platform Since the updated outbound user list no longer includes users corresponding to the user data to be interrupted, the outbound platform only needs to continue to perform automatic outbound calls based on the updated outbound user list.
  • a user who makes an outbound call initiates a call and interrupts users who do not need to make an outbound call, which is conducive to improving the hit rate of automatic outbound calls.
  • the background server and the outbound platform can be set in the same device or separately.
  • the specific setting method can be set according to actual needs, and is not specifically limited here.
  • the outbound user list can also be stored in the background server. After the background server obtains the user data to be interrupted, it directly updates the outbound user list. The user list is sent to the outbound platform, so that the outbound platform performs an automatic outbound call according to the received outbound user list.
  • the specific implementation can be set according to actual needs, and is not specifically limited here.
  • FIG. 2 is a schematic flowchart of another information processing method according to an embodiment of the present application. As shown in FIG. 2, when step 101 is performed, the following steps may be implemented:
  • the background server obtains a scene that needs to be interrupted.
  • the background server determines the user data to be interrupted according to the scene where the interruption is needed.
  • the scene information that needs to be interrupted can be configured in the background server in advance.
  • the background server can periodically obtain the user data generated during the period according to the scenes that need to be interrupted, and then determine whether the user data is to be interrupted according to the user data.
  • User data In practical applications, the above period can be set to 1 minute.
  • the scenarios that need to be interrupted include: an active consultation scenario and a network online transaction service scenario.
  • step 202 after determining that the scene to be interrupted is an active consultation scenario and a network online service scenario, in step 202, when the scene that needs to be interrupted is an active consultation scenario, the background server will The acquired user data is used as the user data to be interrupted.
  • the background server uses the user data entered by the user as the user data to be interrupted.
  • the background server may determine whether it is an active consultation scenario or an online service scenario according to the current scenario.
  • the background server can obtain the content of the call, and obtain the user data according to the content of this consultation, and use the obtained user data as the user data to be interrupted.
  • the scenario is an online business scenario
  • the background server can obtain The user data entered by the user during the online transaction process, and the user data entered by the user is used as the user data to be interrupted.
  • the active consultation scenario includes a scenario corresponding to a user actively calling;
  • the online transaction service scenario includes a corresponding scenario when online vehicle insurance services are processed.
  • the user data to be interrupted when the scenario requiring interruption is an active consultation scenario, includes the user's phone number and scenario information used to indicate that the scenario is an active consultation scenario; when the scenario requiring interruption is to be handled online During a business scenario, the user data to be interrupted includes the phone number, license plate number, and scenario information used to indicate that the scenario is an online business scenario.
  • the user's active call is received.
  • the user's phone number and scene information that is, the scene corresponding to the user's active call
  • the background server interrupts according to the recorded information and needs.
  • the scene information determines whether the user is a user to be interrupted.
  • the phone number or license plate number entered by the user will be received.
  • the back-end server will receive the user's phone number, license plate number, and scenario information (that is, the online online business scenario).
  • the background server judges whether the user is a user to be interrupted according to the recorded information and scene information that needs to be interrupted.
  • the background server can obtain user data corresponding to the user to be interrupted after determining the user to be interrupted, and then the background server can use the interface with the outbound platform to update the user data to be interrupted, such as The phone number is pushed to the outbound platform.
  • the user data includes, but is not limited to, the user's phone number.
  • the specific situation can be set according to actual needs. For example, if the user pays attention to the public number of the outbound platform, the personal information can be Pay attention to the username of the public account.
  • the outbound platform updates the outbound user list according to the received user data to be interrupted.
  • the outbound platform may be in the outbound user list. Delete the record containing the user data to be interrupted, or the outbound platform can also mark the invalid user data in the outbound user list as invalid.
  • the specific update method is not specifically limited here, and the outbound platform is external
  • automatic outgoing calls are performed according to the updated outgoing user list. In this way, automatic outgoing calls to user data that needs to be interrupted can be avoided, which is conducive to improving the hit rate of automatic outgoing calls.
  • FIG. 3 is a schematic structural diagram of an information processing system according to an embodiment of the present application. As shown in FIG. 3, the system includes a background server 31 and an outbound platform 32;
  • the background server 31 is configured to obtain user data to be interrupted
  • the background server 31 is configured to push user data to the outbound platform 32;
  • the outbound calling platform 32 is configured to update the outbound calling user list according to the received user data
  • the outbound calling platform 32 is configured to perform automatic outbound calling according to the updated outbound calling user list.
  • the background server 31 when configured to obtain user data to be interrupted, it is specifically configured to:
  • the background server 31 obtains a scene that needs to be interrupted
  • the background server 31 determines the user data to be interrupted according to the scene that needs to be interrupted.
  • the background server 31 when used to determine the user data to be interrupted according to the scenario that needs to be interrupted, it is specifically used to:
  • the background server uses the user data obtained during this consultation as the user data to be interrupted;
  • the background server treats the user data entered by the user as the user data to be interrupted.
  • the active consultation scenario includes a scenario corresponding to a user actively calling;
  • the online transaction service scenario includes a corresponding scenario when online vehicle insurance services are processed.
  • the user data to be interrupted when the scenario requiring interruption is an active consultation scenario, includes the user's phone number and scenario information used to indicate that the scenario is an active consultation scenario; when the scenario requiring interruption is to be handled online During a business scenario, the user data to be interrupted includes the phone number, license plate number, and scenario information used to indicate that the scenario is an online business scenario.
  • the background server pushes the user data to the outbound platform, and the outbound platform updates the outbound user list according to the user data, so that the outbound platform can update according to the update.
  • the outgoing call user list automatically performs outgoing calls. Since the user data to be interrupted corresponds to users who do not need to make outgoing calls again, the outgoing call platform makes outgoing calls based on the outgoing call user list. Therefore, the outgoing call platform makes external calls based on the user data to be interrupted. After the calling user list is updated, the updated user list no longer includes users corresponding to the user data to be interrupted, so the above method can be used to interrupt users who do not need to be called again.
  • FIG. 4 is a schematic flowchart of another information processing method according to an embodiment of the present application. The method is executed on a background server. As shown in FIG. 4, the method includes the following steps:
  • the background server pushes the user data to the outbound platform, and the outbound platform updates the outbound user list according to the user data, so that the outbound platform can update according to the update.
  • the outgoing call user list automatically performs outgoing calls. Since the user data to be interrupted corresponds to users who do not need to make outgoing calls again, the outgoing call platform makes outgoing calls based on the outgoing call user list. Therefore, the outgoing call platform makes external calls based on the user data to be interrupted. After the calling user list is updated, the updated user list no longer includes users corresponding to the user data to be interrupted, so the above method can be used to interrupt users who do not need to be called again.
  • FIG. 5 is a schematic structural diagram of a background server according to an embodiment of the present application. As shown in FIG. 5, the background server includes:
  • the obtaining unit 51 is configured to obtain user data to be interrupted.
  • the sending unit 52 is configured to push user data to the outbound platform.
  • the background server pushes the user data to the outbound platform, and the outbound platform updates the outbound user list according to the user data, so that the outbound platform can update according to the update.
  • the outgoing call user list automatically performs outgoing calls. Since the user data to be interrupted corresponds to users who do not need to make outgoing calls again, the outgoing call platform makes outgoing calls based on the outgoing call user list. After the calling user list is updated, the updated user list no longer includes users corresponding to the user data to be interrupted, so the above method can be used to interrupt users who do not need to be called again.
  • FIG. 6 is a schematic flowchart of another information processing method according to an embodiment of the present application. The method is executed on an outbound platform. The method includes the following steps:
  • the background server pushes the user data to the outbound platform, and the outbound platform updates the outbound user list according to the user data, so that the outbound platform can update according to the update.
  • the outgoing call user list automatically performs outgoing calls. Since the user data to be interrupted corresponds to users who do not need to make outgoing calls again, the outgoing call platform makes outgoing calls based on the outgoing call user list. Therefore, the outgoing call platform makes external calls based on the user data to be interrupted. After the calling user list is updated, the updated user list no longer includes users corresponding to the user data to be interrupted, so the above method can be used to interrupt users who do not need to be called again.
  • FIG. 7 is a schematic structural diagram of an outbound call platform according to an embodiment of the present application. As shown in FIG. 7, the outbound call platform includes:
  • the receiving unit 71 is configured to receive user data to be interrupted sent by a background server.
  • the updating unit 72 is configured to update the outgoing call user list according to the user data.
  • the outgoing call unit 73 is configured to perform automatic outgoing call according to the updated outgoing call user list.
  • the background server pushes the user data to the outbound platform, and the outbound platform updates the outbound user list according to the user data, so that the outbound platform can update according to the update.
  • the outgoing call user list automatically performs outgoing calls. Since the user data to be interrupted corresponds to users who do not need to make outgoing calls again, the outgoing call platform makes outgoing calls based on the outgoing call user list. Therefore, the outgoing call platform makes external calls based on the user data to be interrupted. After the calling user list is updated, the updated user list no longer includes users corresponding to the user data to be interrupted, so the above method can be used to interrupt users who do not need to be called again.
  • FIG. 8 is a schematic structural diagram of another background server provided by an embodiment of the present application.
  • the background server 2000 may include one or more of the following components: a processing component 2002, a memory 2004, a power supply component 2006, and a multimedia component 2008. , Audio component 2010, input / output (I / O) interface 2012, sensor component 2014, and communication component 2016.
  • the processing component 2002 generally controls the overall operations of the background server 2000, such as operations associated with display, phone calls, data communications, camera operations, and recording operations.
  • the processing element 2002 may include one or more processors 2020 to execute instructions to complete all or part of the steps of the method described above.
  • the processing component 2002 may include one or more modules to facilitate the interaction between the processing component 2002 and other components.
  • the processing component 2002 may include a multimedia module to facilitate the interaction between the multimedia component 2008 and the processing component 2002.
  • the memory 2004 is configured to store various types of data to support the operation of the background server 2000. Examples of these data include instructions for any application or method for operating on the background server 2000, contact data, phone book data, messages, pictures, videos, and so on.
  • the memory 2004 may 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), Programming read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk.
  • SRAM static random access memory
  • EEPROM electrically erasable programmable read-only memory
  • EPROM Programming read-only memory
  • PROM programmable read-only memory
  • ROM read-only memory
  • magnetic memory flash memory
  • flash memory magnetic disk or optical disk.
  • the power component 2006 provides power to various components of the background server 2000.
  • the power component 2006 may include a power management system, one or more power sources, and other components associated with generating, managing, and distributing power for the background server 2000.
  • the multimedia component 2008 includes a screen that provides an output interface between the background server 2000 and the user.
  • the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive an input signal from a user.
  • the touch panel includes one or more touch sensors to sense touch, swipe, and gestures on the touch panel. The touch sensor can not only sense the boundary of a touch or slide action, but also detect duration and pressure related to the touch or slide operation.
  • the multimedia component 2008 includes a front camera and / or a rear camera. When the device 2000 is in an operation mode, such as a shooting mode or a video mode, the front camera and / or the rear camera can receive external multimedia data. Each front camera and rear camera can be a fixed optical lens system or have focal length and optical zoom capabilities.
  • the audio component 2010 is configured to output and / or input audio signals.
  • the audio component 2010 includes a microphone (MIC).
  • the microphone is configured to receive an external audio signal.
  • the received audio signal may be further stored in the memory 2004 or transmitted via the communication component 2016.
  • the audio component 2010 further includes a speaker for outputting audio signals.
  • the I / O interface 2012 provides an interface between the processing component 2002 and a peripheral interface module.
  • the peripheral interface module may be a keyboard, a click wheel, a button, or the like. These buttons may include, but are not limited to: a home button, a volume button, a start button, and a lock button.
  • the sensor component 2014 includes one or more sensors for providing status evaluation of various aspects for the background server 2000.
  • the sensor component 2014 can detect the on / off status of the background server 2000 and the relative positioning of the components, such as the display and keypad of the background server 2000.
  • the sensor component 2014 can also detect the background server 2000 or a component of the background server 2000. The location changes, the presence or absence of the user's contact with the background server 2000, the orientation or acceleration / deceleration of the background server 2000, and the temperature change of the background server 2000.
  • the sensor component 2014 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact.
  • the sensor component 2014 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications.
  • the sensor component 2014 may further include an acceleration sensor, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.
  • the communication component 2016 is configured to facilitate wired or wireless communication between the background server 2000 and other devices.
  • the background server 2000 can access a wireless network based on a communication standard, such as Wi-Fi, 2G or 3G, or a combination thereof.
  • the communication section 2016 receives a broadcast signal or broadcast-related information from an external broadcast management system via a broadcast channel.
  • the communication component 2016 further includes a near field communication (NFC) module to facilitate short-range communication.
  • the NFC module can be implemented based on radio frequency identification (RFID) technology, infrared data association (IrDA) technology, ultra wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.
  • RFID radio frequency identification
  • IrDA infrared data association
  • UWB ultra wideband
  • Bluetooth Bluetooth
  • the background server 2000 may be implemented by one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), The programming gate array (FPGA), controller, microcontroller, microprocessor, or other electronic components are implemented to perform the method shown in FIG. 4.
  • ASICs application-specific integrated circuits
  • DSPs digital signal processors
  • DSPDs digital signal processing devices
  • PLDs programmable logic devices
  • FPGA programming gate array
  • controller microcontroller, microprocessor, or other electronic components are implemented to perform the method shown in FIG. 4.
  • a computer non-volatile readable storage medium including instructions may be executed by the processor 2020 of the background server 2000 to complete the foregoing method.
  • the computer non-volatile readable storage medium may be a ROM, a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, and the like.
  • the processor 2020 is configured to: obtain user data to be interrupted; and push the user data to the outbound platform.
  • the processor 2020 when the processor 2020 is configured to obtain user data to be interrupted, the processor 2020 is specifically configured to: obtain a scene that needs to be interrupted; and determine the user data to be interrupted according to the scene that needs to be interrupted.
  • the processor 2020 is configured to determine the user data to be interrupted according to a scenario where interruption is required, and is specifically used to:
  • the scenario requiring interruption is an active consultation scenario
  • the user data obtained during this consultation is used as the user data to be interrupted
  • the scenario requiring interruption is an online service scenario
  • the user data input by the user is taken as the user data to be interrupted.
  • the active consultation scenario includes a scenario corresponding to a user actively calling;
  • the online transaction service scenario includes a corresponding scenario when online vehicle insurance services are processed.
  • the user data to be interrupted when the scenario requiring interruption is an active consultation scenario, includes the user's phone number and scenario information used to indicate that the scenario is an active consultation scenario; when the scenario requiring interruption is to be handled online During a business scenario, the user data to be interrupted includes the phone number, license plate number, and scenario information used to indicate that the scenario is an online business scenario.
  • the computer non-volatile readable storage medium stores a computer program for executing: obtaining user data to be interrupted; and pushing the user data to an outbound platform.
  • FIG. 9 is a schematic structural diagram of another outbound calling platform provided by an embodiment of the present application.
  • the outbound calling platform 3000 may include one or more of the following components: a processing component 3002, a memory 3004, a power supply component 3006, and multimedia.
  • the processing component 3002 generally controls overall operations of the outbound platform 3000, such as operations associated with display, telephone calls, data communications, camera operations, and recording operations.
  • the processing element 3002 may include one or more processors 3020 to execute instructions to complete all or part of the steps of the method described above.
  • the processing component 3002 may include one or more modules to facilitate interaction between the processing component 3002 and other components.
  • the processing component 3002 may include a multimedia module to facilitate the interaction between the multimedia component 3008 and the processing component 3002.
  • the memory 3004 is configured to store various types of data to support the operation of the outbound platform 3000. Examples of these data include instructions for any application or method for operating on the outbound platform 3000, contact data, phone book data, messages, pictures, videos, etc.
  • the memory 3004 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), Programming read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk.
  • SRAM static random access memory
  • EEPROM electrically erasable programmable read-only memory
  • EPROM Programming read-only memory
  • PROM programmable read-only memory
  • ROM read-only memory
  • magnetic memory flash memory
  • flash memory magnetic disk or optical disk.
  • the power component 3006 provides power to various components of the outbound platform 3000.
  • the power component 3006 may include a power management system, one or more power sources, and other components associated with generating, managing, and distributing power for the outbound platform 3000.
  • the multimedia component 3008 includes a screen that provides an output interface between the outbound platform 3000 and the user.
  • the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive an input signal from a user.
  • the touch panel includes one or more touch sensors to sense touch, swipe, and gestures on the touch panel. The touch sensor can not only sense the boundary of a touch or slide action, but also detect duration and pressure related to the touch or slide operation.
  • the multimedia component 3008 includes a front camera and / or a rear camera.
  • the front camera and / or the rear camera can receive external multimedia data.
  • Each front camera and rear camera can be a fixed optical lens system or have focal length and optical zoom capabilities.
  • the audio component 3010 is configured to output and / or input audio signals.
  • the audio component 3010 includes a microphone (MIC).
  • the microphone When the outbound platform 3000 is in an operation mode, such as a call mode, a recording mode, and a voice recognition mode, the microphone is configured to receive an external audio signal.
  • the received audio signal may be further stored in the memory 3004 or transmitted via the communication component 3016.
  • the audio component 3010 further includes a speaker for outputting audio signals.
  • the I / O interface 3012 provides an interface between the processing component 3002 and a peripheral interface module.
  • the peripheral interface module may be a keyboard, a click wheel, a button, or the like. These buttons may include, but are not limited to: a home button, a volume button, a start button, and a lock button.
  • the sensor component 3014 includes one or more sensors for providing status evaluation of various aspects for the outbound platform 3000.
  • the sensor component 3014 can detect the on / off state of the outbound platform 3000, and the relative positioning of the components, such as the display and keypad of the outbound platform 3000.
  • the sensor component 3014 can also detect the outbound platform 3000 or the outbound platform 3000 The position of a component changes, the presence or absence of contact between the user and the outbound platform 3000, the orientation or acceleration / deceleration of the outbound platform 3000, and the temperature change of the outbound platform 3000.
  • the sensor assembly 3014 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact.
  • the sensor component 3014 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications.
  • the sensor assembly 3014 may further include an acceleration sensor, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.
  • the communication component 3016 is configured to facilitate wired or wireless communication between the outbound platform 3000 and other devices.
  • the outgoing call platform 3000 can access a wireless network based on a communication standard, such as Wi-Fi, 2G or 3G, or a combination thereof.
  • the communication section 3016 receives a broadcast signal or broadcast-related information from an external broadcast management system via a broadcast channel.
  • the communication component 3016 further includes a near field communication (NFC) module to facilitate short-range communication.
  • the NFC module can be implemented based on radio frequency identification (RFID) technology, infrared data association (IrDA) technology, ultra wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.
  • RFID radio frequency identification
  • IrDA infrared data association
  • UWB ultra wideband
  • Bluetooth Bluetooth
  • the outbound platform 3000 may be implemented by one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), A programmable gate array (FPGA), controller, microcontroller, microprocessor, or other electronic component is implemented to perform the method shown in FIG. 6.
  • ASICs application specific integrated circuits
  • DSPs digital signal processors
  • DSPDs digital signal processing devices
  • PLDs programmable logic devices
  • FPGA programmable gate array
  • controller microcontroller, microprocessor, or other electronic component is implemented to perform the method shown in FIG. 6.
  • a computer non-volatile readable storage medium including instructions such as a memory 3004 including instructions, may be provided, which may be executed by the processor 3020 of the outbound platform 3000 to complete the above method.
  • the computer non-volatile readable storage medium may be a ROM, a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, and the like.
  • the processor 3020 is configured to: receive user data to be interrupted sent by the background server; update the outgoing call user list according to the user data; and perform automatic outgoing call according to the updated outgoing call user list.
  • the above computer non-volatile readable storage medium stores a computer program for executing: receiving user data to be interrupted sent by a background server; updating the outgoing call user list according to the user data; and updating the outgoing call user list according to the update Make an automatic outbound call.
  • An embodiment of the present application further provides a computer device.
  • the computer device includes a memory and a processor.
  • the memory is used to store information including program instructions.
  • the processor is used to control the execution of the program instructions.
  • the computer device application includes a background server and an outgoing call.
  • the background server obtains the user data to be interrupted; the background server pushes the user data to the outbound platform; the outbound platform calls the user according to the received user data The list is updated; the outbound platform performs automatic outbound calls based on the updated outbound user list.
  • the background server obtains a scene that needs to be interrupted; the background server determines the user data to be interrupted according to the scene that needs to be interrupted.
  • the background server uses the user data obtained during this consultation as the user data to be interrupted;
  • the background server treats the user data entered by the user as the user data to be interrupted.
  • the active consultation scenario includes a scenario corresponding to a user actively calling;
  • the online transaction service scenario includes a corresponding scenario when the vehicle insurance service is processed online.
  • the user data to be interrupted when the scenario requiring interruption is an active consultation scenario, includes the user's phone number and scenario information used to indicate that the scenario is an active consultation scenario; when the scenario requiring interruption is an online business scenario, The user data to be interrupted includes the phone number, license plate number, and scene information used to indicate that the scene is an online business scenario.
  • An embodiment of the present application further provides a computer non-volatile readable storage medium.
  • the computer non-volatile readable storage medium includes a stored program.
  • the computer non-volatile readable storage medium is applied to include a background server and an external call.
  • the device where the computer nonvolatile readable storage medium is located performs the following steps: the background server obtains the user data to be interrupted; the background server pushes the user data to the outbound platform; the outbound platform The outgoing call user list is updated according to the received user data; the outgoing call platform performs automatic outgoing calls according to the updated outgoing call user list.
  • the device controlling the computer's non-volatile readable storage medium further performs the following steps: the background server obtains the scenes that need to be interrupted; the background server determines the user data to be interrupted according to the scenes that need to be interrupted.
  • the device that controls the computer's non-volatile readable storage medium further performs the following steps:
  • the scenario requiring interruption is an active consultation scenario
  • the background server treats the user data obtained during this consultation as a standby Interrupted user data
  • the background server uses the user data entered by the user as the user data to be interrupted.
  • the active consultation scenario includes a scenario corresponding to a user actively calling;
  • the online transaction service scenario includes a corresponding scenario when the vehicle insurance service is processed online.
  • the user data to be interrupted when the scenario requiring interruption is an active consultation scenario, includes the user's phone number and scenario information used to indicate that the scenario is an active consultation scenario; when the scenario requiring interruption is an online business scenario, The user data to be interrupted includes the phone number, license plate number, and scene information used to indicate that the scene is an online business scenario.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Telephonic Communication Services (AREA)

Abstract

本申请提供一种信息处理方法和系统，该方法包括：后台服务器获取待中断的用户数据；后台服务器将用户数据推送给外呼平台；外呼平台根据接收到的用户数据对外呼用户列表进行更新；外呼平台根据更新后的外呼用户列表进行自动外呼，通过上述方法可以对不需要再外呼用户进行中断，有利于提高自动外呼的命中率。

Description

一种信息处理方法和系统
本申请要求于2018年07月31日提交中国专利局、申请号为201810857993.2、发明名称为“一种信息处理方法和系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及计算机技术领域，尤其涉及一种信息处理方法和系统。
背景技术
目前，可以利用外呼平台，进行用户的自动外呼。但是有些情况下，由于情况的变化，不需要再外呼某些用户，所以需要中断机制。在用户被中断后，就不需要再针对这些用户进行外呼来推荐业务，因此需要一种针对这类用户的自动外呼的中断机制。
申请内容
本申请提供了一种信息处理方法和系统，以对不需要外呼的用户进行中断。
具体地，本申请是通过如下技术方案实现的：
第一方面，本申请提供了一种信息处理方法，所述方法应用在包括后台服务器和外呼平台的系统中，所述方法包括：
所述后台服务器获取待中断的用户数据；
所述后台服务器将所述用户数据推送给所述外呼平台；
所述外呼平台根据接收到的所述用户数据对外呼用户列表进行更新；
所述外呼平台根据更新后的所述外呼用户列表进行自动外呼。
第二方面，本申请提供了一种信息处理系统，所述系统包括后台服务器和外呼平台；
所述后台服务器，用于获取待中断的用户数据；
所述后台服务器，用于将所述用户数据推送给所述外呼平台；
所述外呼平台，用于根据接收到的所述用户数据对外呼用户列表进行更新；
所述外呼平台，用于根据更新后的所述外呼用户列表进行自动外呼。
第三方面，本申请实施例提供一种计算机设备，包括存储器、处理器以及存储在存储器中并可在处理器上运行的计算机程序，其特征在于，处理器执行计算机程序时实现如上述第一方面所述的方法。
第四方面，本申请实施例提供一种计算机非易失性可读存储介质，其特征在于，所述计算机非易失性可读存储介质包括存储的程序，其中，在所述程序运行时控制所述计算机非易失性可读存储介质所在设备执行如上述第一方面所述的方法。
上述技术方案中的任一个技术方案具有如下有益效果：
在本申请实施例中，在后台服务器获取待中断的用户数据后，后台服务器将该用户数据推送给外呼平台，外呼平台根据该用户数据对外呼用户列表进行更新，以便外呼平台根据更新后的外呼用户列表进行自动外呼，由于待中断的用户数据对应不需要再进行外呼的用户，外呼平台根据外呼用户列表外呼用户，因此外呼平台根据待中断的用户数据对外呼用户列表进行更新后，更新后的外呼用户列表中不再包括待中断的用户数据对应的用户，因此通过上述方法可以对不需要再外呼用户进行中断。
附图说明
图1为本申请实施例提供的一种信息处理方法的流程示意图；
图2为本申请实施例提供的另一种信息处理方法的流程示意图；
图3为本申请实施例提供的一种信息处理系统的结构示意图；
图4为本申请实施例提供的另一种信息处理方法的流程示意图；
图5为本申请实施例提供的一种后台服务器的结构示意图；
图6为本申请实施例提供的另一种信息处理方法的流程示意图；
图7为本申请实施例提供的一种外呼平台的结构示意图；
图8为本申请实施例提供的另一种后台服务器的结构示意图；
图9为本申请实施例提供的另一种外呼平台的结构示意图。
具体实施方式
这里将详细地对示例性实施例进行说明，其示例表示在附图中。下面的描述涉及附图时，除非另有表示，不同附图中的相同数字表示相同或相似的要素。以下示例性实施例中所描述的实施方式并不代表与本申请相一致的所有实施方式。相反，它们仅是与如所附权利要求书中所详述的、本申请的一些方面相一致的装置和方法的例子。
在本申请使用的术语是仅仅出于描述特定实施例的目的，而非旨在限制本申请。在本申请和所附权利要求书中所使用的单数形式的“一种”、“所述”和“该”也旨在包括多数形式，除非上下文清楚地表示其他含义。还应当理解，本文中使用的术语“和/或”是指并包含一个或多个相关联的列出项目的任何或所有可能组合。
取决于语境，如在此所使用的词语“如果”可以被解释成为“在……时”或“当……时”或“响应于确定”。
图1为本申请实施例提供的一种信息处理方法的流程示意图，该方法应用在包括后台服务器和外呼平台的系统中，该方法包括以下步骤：
101、后台服务器获取待中断的用户数据。
102、后台服务器将用户数据推送给外呼平台。
103、外呼平台根据接收到的用户数据对外呼用户列表进行更新。
104、外呼平台根据更新后的外呼用户列表进行自动外呼。
具体的，待中断的用户数据对应不需要再进行外呼的用户，即待中断的用户数据为不再进行自动外呼的用户数据，在后台服务器获取上述用户数据后，为了使外呼平台不再对上述用户数据对应的用户进行外呼，后台服务器将上述用户数据发送给外呼平台，以便外呼平台根据上述用户数据进行外呼用户列表的更新，然后外呼平台可以根据更新后的用户列表进行自动外呼，由于更新后的外呼用户列表中不再包括待中断的用户数据对应的用户，所以外呼平台在根据更新后的外呼用户列表进行自动外呼时，只对需要继续进行外呼的用户发起呼叫，对不需要再外呼的用户进行中断，从而有利于提高自动外呼的命中率。
需要注意的是，后台服务器和外呼平台可以设置在同一设备中，也可以分开设置，具体的设置方式可以根据实际需要进行设定，在此不做具体限定。
需要再次注意的是，外呼用户列表也可以存储在后台服务器，后台服务器在获取到待中断的用户数据后，直接对外呼用户列表进行更新，在服务器更新完毕后，可以将更新后的外呼用户列表发送给外呼平台，以使外呼平台根据接收到的外呼用户列表进行自动外呼，具体的实现方式可以根据实际需要进行设定，在此不做具体限定。
图2为本申请实施例提供的另一种信息处理方法的流程示意图，如图2所示，在执行步骤101时，可以通过以下步骤实现：
201、后台服务器获取需要中断的场景。
202、后台服务器根据需要中断的场景，确定待中断的用户数据。
具体的，可以预先在后台服务器中配置需要中断的场景信息，后台服务器可以周期性的根据需要中断的场景，获取本周期内产生的用户数据，然后根据用户数据确定该用户数据是否为待中断的用户数据。实际应用中，上述周期可以设置为1分钟。
在一个可行的实施方案中，需要中断的场景包括：主动咨询场景和网络在线办理业务场景。
在一个可行的实施方案中，当确定待中断的场景为主动咨询场景和网络在线办理业务场景后，在执行步骤202时，当需要中断的场景为主动咨询场景时，后台服务器将本次咨询时获取到的用户数据作为待中断的用户数据；当需要中断的场景为在线办理业务场景时，后台服务器将用户输入的用户数据作为待中断的用户数据。
具体的，当预设的待中断在场景为主动咨询场景和网络在线办理业务场景时，后台服务器可以根据当前的场景确定是否为主动咨询场景或在线办理业务场景，当场景为主动咨询场景时，后台服务器可以获取本次通话的内容，并根据本次咨询的内容，获取到用户数据，并将获取到的用户数据作为待中断的用户数据，当场景为在线办理业务场景，后台服务器可以获取到用户在本次在线办理业务的过程中输入的用户数据，并将用户输入的用户数据作为待中断的用户数据。
在一个可行的实施方案中，主动咨询场景包括用户主动呼叫时对应的场景；在线办理业务场景包括在线办理车辆保险业务时对应的场景。
在一个可行的实施方案中，当需要中断的场景为主动咨询场景时，待中断的用户数据包括用户的电话号码和用于表示场景为主动咨询场景的场景信息；当需要中断的场景为在线办理业务场景时，待中断的用户数据包括用户输入的电话号码、车牌号和用于表示场景为在线办理业务场景的场景信息。
具体的，主动咨询场景下，会接收到用户的主动呼叫，此时可以记录下用户的电话号码和场景信息(即用户主动呼叫时对应的场景)，这样，后台服务器根据记录的信息以及需要中断的场景信息判断该用户是否为待中断的用户。在线办理业务场景下，如车辆保险业务，会接收到用户输入的电话号码或者车牌号，这样，后台服务器根据输入的用户的电话号码或者车牌号、场景信息(即网络在线办理业务场景)，这样，后台服务器根据记录的信息以及需要中断的场景信息判断该用户是否为待中断的用户。
在一个可行的实施方案中，后台服务器在确定待中断的用户后，可以获得待中断用户对应的用户数据，然后后台服务器可以通过与外呼平台之间的接口，将待中断的用户数据，如电话号码推送至外呼平台，需要注意的是，用户数据包括但不限于用户的电话号码，具体情况可以根据实际需要进行设置，例如，如果用户关注了外呼平台的公众号，则个人信息可以关注该公众号的用户名。
在一个可行的实施方案中，在外呼平台接收到待中断的用户数据后，外呼平台根据接收到的待中断的用户数据对外呼用户列表进行更新，例如，外呼平台可以在外呼用户列表中将包含该待中断的用户数据的记录删除，或者，外呼平台也可以在外呼用户列表中将包含该待中断的用户数据标记为失效，具体更新方式在此不做具体限定，外呼平台对外呼用户列表更新之后，根据更新后的外呼用户列表进行自动外呼，这样，就可以避免对需要中断的用户数据的自动外呼，从而有利于提高自动外呼的命中率。
图3为本申请实施例提供的一种信息处理系统的结构示意图，如图3所示，该系统包括后台服务器31和外呼平台32；
后台服务器31，用于获取待中断的用户数据；
后台服务器31，用于将用户数据推送给外呼平台32；
外呼平台32，用于根据接收到的用户数据对外呼用户列表进行更新；
外呼平台32，用于根据更新后的外呼用户列表进行自动外呼。
在一个可行的实施方案中，在后台服务器31用于获取待中断的用户数据时，具体用于：
后台服务器31获取需要中断的场景；
后台服务器31根据需要中断的场景，确定待中断的用户数据。
在一个可行的实施方案中，在后台服务器31用于根据需要中断的场景，确定待中断的用户数据时，具体用于：
当需要中断的场景为主动咨询场景时，后台服务器将本次咨询时获取到的用户数据作为待中断的用户数据；
当需要中断的场景为在线办理业务场景时，后台服务器将用户输入的用户数据作为待中 断的用户数据。
在一个可行的实施方案中，主动咨询场景包括用户主动呼叫时对应的场景；在线办理业务场景包括在线办理车辆保险业务时对应的场景。
在一个可行的实施方案中，当需要中断的场景为主动咨询场景时，待中断的用户数据包括用户的电话号码和用于表示场景为主动咨询场景的场景信息；当需要中断的场景为在线办理业务场景时，待中断的用户数据包括用户输入的电话号码、车牌号和用于表示场景为在线办理业务场景的场景信息。
关于上述实施例中的系统，后台服务器31和外呼平台32执行操作的具体方式已经在有关该方法的实施例中进行了详细描述，此处将不做详细阐述说明。
在本申请实施例中，在后台服务器获取待中断的用户数据后，后台服务器将该用户数据推送给外呼平台，外呼平台根据该用户数据对外呼用户列表进行更新，以便外呼平台根据更新后的外呼用户列表进行自动外呼，由于待中断的用户数据对应不需要再进行外呼的用户，外呼平台根据外呼用户列表外呼用户，因此外呼平台根据待中断的用户数据对外呼用户列表进行更新后，更新后的外呼用户列表中不再包括待中断的用户数据对应的用户，因此通过上述方法可以对不需要再外呼用户进行中断。
图4为本申请实施例提供的另一种信息处理方法的流程示意图，该方法执行在后台服务器，如图4所示，该方法包括以下步骤：
401、获取待中断的用户数据。
402、将用户数据推送给外呼平台。
关于上述实施例中的方法的具体方式已经在有关该方法的实施例中进行了详细描述，此处将不做详细阐述说明。
在本申请实施例中，在后台服务器获取待中断的用户数据后，后台服务器将该用户数据推送给外呼平台，外呼平台根据该用户数据对外呼用户列表进行更新，以便外呼平台根据更新后的外呼用户列表进行自动外呼，由于待中断的用户数据对应不需要再进行外呼的用户，外呼平台根据外呼用户列表外呼用户，因此外呼平台根据待中断的用户数据对外呼用户列表进行更新后，更新后的外呼用户列表中不再包括待中断的用户数据对应的用户，因此通过上述方法可以对不需要再外呼用户进行中断。
图5为本申请实施例提供的一种后台服务器的结构示意图，如图5所示，后台服务器包括：
获取单元51，用于获取待中断的用户数据.
发送单元52，用于将用户数据推送给外呼平台。
关于上述实施例中的后台服务器的具体方式已经在有关该方法的实施例中进行了详细描述，此处将不做详细阐述说明。
在本申请实施例中，在后台服务器获取待中断的用户数据后，后台服务器将该用户数据推送给外呼平台，外呼平台根据该用户数据对外呼用户列表进行更新，以便外呼平台根据更新后的外呼用户列表进行自动外呼，由于待中断的用户数据对应不需要再进行外呼的用户，外呼平台根据外呼用户列表外呼用户，因此外呼平台根据待中断的用户数据对外呼用户列表进行更新后，更新后的外呼用户列表中不再包括待中断的用户数据对应的用户，因此通过上述方法可以对不需要再外呼用户进行中断。
图6为本申请实施例提供的另一种信息处理方法的流程示意图，该方法执行在外呼平台，该方法包括以下步骤：
601、接收后台服务器发送的待中断的用户数据。
602、根据用户数据对外呼用户列表进行更新。
603、根据更新后的外呼用户列表进行自动外呼。
关于上述实施例中的方法的具体方式已经在有关该方法的实施例中进行了详细描述，此处将不做详细阐述说明。
在本申请实施例中，在后台服务器获取待中断的用户数据后，后台服务器将该用户数据推送给外呼平台，外呼平台根据该用户数据对外呼用户列表进行更新，以便外呼平台根据更新后的外呼用户列表进行自动外呼，由于待中断的用户数据对应不需要再进行外呼的用户，外呼平台根据外呼用户列表外呼用户，因此外呼平台根据待中断的用户数据对外呼用户列表进行更新后，更新后的外呼用户列表中不再包括待中断的用户数据对应的用户，因此通过上述方法可以对不需要再外呼用户进行中断。
图7为本申请实施例提供的一种外呼平台的结构示意图，如图7所示，该外呼平台包括：
接收单元71，用于接收后台服务器发送的待中断的用户数据。
更新单元72，用于根据用户数据对外呼用户列表进行更新。
外呼单元73，用于根据更新后的外呼用户列表进行自动外呼。
关于上述实施例中的外呼平台的具体方式已经在有关该方法的实施例中进行了详细描述，此处将不做详细阐述说明。
在本申请实施例中，在后台服务器获取待中断的用户数据后，后台服务器将该用户数据推送给外呼平台，外呼平台根据该用户数据对外呼用户列表进行更新，以便外呼平台根据更新后的外呼用户列表进行自动外呼，由于待中断的用户数据对应不需要再进行外呼的用户，外呼平台根据外呼用户列表外呼用户，因此外呼平台根据待中断的用户数据对外呼用户列表 进行更新后，更新后的外呼用户列表中不再包括待中断的用户数据对应的用户，因此通过上述方法可以对不需要再外呼用户进行中断。
图8为本申请实施例提供的另一种后台服务器的结构示意图，如图8所示，后台服务器2000可以包括以下一个或多个组件：处理组件2002，存储器2004，电源组件2006，多媒体组件2008，音频组件2010，输入/输出(I/O)的接口2012，传感器组件2014，以及通信组件2016。
处理组件2002通常控制后台服务器2000的整体操作，诸如与显示，电话呼叫，数据通信，相机操作和记录操作相关联的操作。处理元件2002可以包括一个或多个处理器2020来执行指令，以完成上述的方法的全部或部分步骤。此外，处理组件2002可以包括一个或多个模块，便于处理组件2002和其他组件之间的交互。例如，处理部件2002可以包括多媒体模块，以方便多媒体组件2008和处理组件2002之间的交互。
存储器2004被配置为存储各种类型的数据以支持后台服务器2000的操作。这些数据的示例包括用于在后台服务器2000上操作的任何应用程序或方法的指令，联系人数据，电话簿数据，消息，图片，视频等。存储器2004可以由任何类型的易失性或非易失性存储设备或者它们的组合实现，如静态随机存取存储器(SRAM)，电可擦除可编程只读存储器(EEPROM)，可擦除可编程只读存储器(EPROM)，可编程只读存储器(PROM)，只读存储器(ROM)，磁存储器，快闪存储器，磁盘或光盘。
电力组件2006为后台服务器2000的各种组件提供电力。电力组件2006可以包括电源管理系统，一个或多个电源，及其他与为后台服务器2000生成、管理和分配电力相关联的组件。
多媒体组件2008包括在后台服务器2000和用户之间的提供一个输出接口的屏幕。在一些实施例中，屏幕可以包括液晶显示器(LCD)和触摸面板(TP)。如果屏幕包括触摸面板，屏幕可以被实现为触摸屏，以接收来自用户的输入信号。触摸面板包括一个或多个触摸传感器以感测触摸、滑动和触摸面板上的手势。触摸传感器可以不仅感测触摸或滑动动作的边界，而且还检测与触摸或滑动操作相关的持续时间和压力。在一些实施例中，多媒体组件2008包括一个前置摄像头和/或后置摄像头。当设备2000处于操作模式，如拍摄模式或视频模式时，前置摄像头和/或后置摄像头可以接收外部的多媒体数据。每个前置摄像头和后置摄像头可以是一个固定的光学透镜系统或具有焦距和光学变焦能力。
音频组件2010被配置为输出和/或输入音频信号。例如，音频组件2010包括一个麦克风(MIC)，当后台服务器2000处于操作模式，如呼叫模式、记录模式和语音识别模式时，麦克风被配置为接收外部音频信号。所接收的音频信号可以被进一步存储在存储器2004或经由通信组件2016发送。在一些实施例中，音频组件2010还包括一个扬声器，用于输出音频信 号。
I/O接口2012为处理组件2002和外围接口模块之间提供接口，上述外围接口模块可以是键盘，点击轮，按钮等。这些按钮可包括但不限于：主页按钮、音量按钮、启动按钮和锁定按钮。
传感器组件2014包括一个或多个传感器，用于为后台服务器2000提供各个方面的状态评估。例如，传感器组件2014可以检测到后台服务器2000的打开/关闭状态，组件的相对定位，例如组件为后台服务器2000的显示器和小键盘，传感器组件2014还可以检测后台服务器2000或后台服务器2000一个组件的位置改变，用户与后台服务器2000接触的存在或不存在，后台服务器2000方位或加速/减速和后台服务器2000的温度变化。传感器组件2014可以包括接近传感器，被配置用来在没有任何的物理接触时检测附近物体的存在。传感器组件2014还可以包括光传感器，如CMOS或CCD图像传感器，用于在成像应用中使用。在一些实施例中，该传感器组件2014还可以包括加速度传感器，陀螺仪传感器，磁传感器，压力传感器或温度传感器。
通信组件2016被配置为便于后台服务器2000和其他设备之间有线或无线方式的通信。后台服务器2000可以接入基于通信标准的无线网络，如Wi-Fi，2G或3G，或它们的组合。在一个示例性实施例中，通信部件2016经由广播信道接收来自外部广播管理系统的广播信号或广播相关信息。在一个示例性实施例中，通信部件2016还包括近场通信(NFC)模块，以促进短程通信。例如，在NFC模块可基于射频识别(RFID)技术，红外数据协会(IrDA)技术，超宽带(UWB)技术，蓝牙(BT)技术和其他技术来实现。
在示例性实施例中，后台服务器2000可以被一个或多个应用专用集成电路(ASIC)、数字信号处理器(DSP)、数字信号处理设备(DSPD)、可编程逻辑器件(PLD)、现场可编程门阵列(FPGA)、控制器、微控制器、微处理器或其他电子元件实现，用于执行图4所示的方法。
在示例性实施例中，还提供了一种包括指令的计算机非易失性可读存储介质，例如包括指令的存储器2004，上述指令可由后台服务器2000的处理器2020执行以完成上述方法。例如，计算机非易失性可读存储介质可以是ROM、随机存取存储器(RAM)、CD-ROM、磁带、软盘和光数据存储设备等。其中，处理器2020被配置为：获取待中断的用户数据；将用户数据推送给外呼平台。
在一个可行的实施方案中，处理器2020被配置为获取待中断的用户数据时，具体用于：获取需要中断的场景；根据需要中断的场景，确定待中断的用户数据。
在一个可行的实施方案中，处理器2020被配置为根据需要中断的场景，确定待中断的 用户数据时，具体用于：
当需要中断的场景为主动咨询场景时，将本次咨询时获取到的用户数据作为待中断的用户数据；
当需要中断的场景为在线办理业务场景时，将用户输入的用户数据作为待中断的用户数据。
在一个可行的实施方案中，主动咨询场景包括用户主动呼叫时对应的场景；在线办理业务场景包括在线办理车辆保险业务时对应的场景。
在一个可行的实施方案中，当需要中断的场景为主动咨询场景时，待中断的用户数据包括用户的电话号码和用于表示场景为主动咨询场景的场景信息；当需要中断的场景为在线办理业务场景时，待中断的用户数据包括用户输入的电话号码、车牌号和用于表示场景为在线办理业务场景的场景信息。
上述计算机非易失性可读存储介质储有计算机程序，计算机程序用于执行：获取待中断的用户数据；将用户数据推送给外呼平台。
图9为本申请实施例提供的另一种外呼平台的结构示意图，如图9所示，外呼平台3000可以包括以下一个或多个组件：处理组件3002，存储器3004，电源组件3006，多媒体组件3008，音频组件3010，输入/输出(I/O)的接口3012，传感器组件3014，以及通信组件3016。
处理组件3002通常控制外呼平台3000的整体操作，诸如与显示，电话呼叫，数据通信，相机操作和记录操作相关联的操作。处理元件3002可以包括一个或多个处理器3020来执行指令，以完成上述的方法的全部或部分步骤。此外，处理组件3002可以包括一个或多个模块，便于处理组件3002和其他组件之间的交互。例如，处理部件3002可以包括多媒体模块，以方便多媒体组件3008和处理组件3002之间的交互。
存储器3004被配置为存储各种类型的数据以支持外呼平台3000的操作。这些数据的示例包括用于在外呼平台3000上操作的任何应用程序或方法的指令，联系人数据，电话簿数据，消息，图片，视频等。存储器3004可以由任何类型的易失性或非易失性存储设备或者它们的组合实现，如静态随机存取存储器(SRAM)，电可擦除可编程只读存储器(EEPROM)，可擦除可编程只读存储器(EPROM)，可编程只读存储器(PROM)，只读存储器(ROM)，磁存储器，快闪存储器，磁盘或光盘。
电力组件3006为外呼平台3000的各种组件提供电力。电力组件3006可以包括电源管理系统，一个或多个电源，及其他与为外呼平台3000生成、管理和分配电力相关联的组件。
多媒体组件3008包括在外呼平台3000和用户之间的提供一个输出接口的屏幕。在一些实施例中，屏幕可以包括液晶显示器(LCD)和触摸面板(TP)。如果屏幕包括触摸面板， 屏幕可以被实现为触摸屏，以接收来自用户的输入信号。触摸面板包括一个或多个触摸传感器以感测触摸、滑动和触摸面板上的手势。触摸传感器可以不仅感测触摸或滑动动作的边界，而且还检测与触摸或滑动操作相关的持续时间和压力。在一些实施例中，多媒体组件3008包括一个前置摄像头和/或后置摄像头。当外呼平台3000处于操作模式，如拍摄模式或视频模式时，前置摄像头和/或后置摄像头可以接收外部的多媒体数据。每个前置摄像头和后置摄像头可以是一个固定的光学透镜系统或具有焦距和光学变焦能力。
音频组件3010被配置为输出和/或输入音频信号。例如，音频组件3010包括一个麦克风(MIC)，当外呼平台3000处于操作模式，如呼叫模式、记录模式和语音识别模式时，麦克风被配置为接收外部音频信号。所接收的音频信号可以被进一步存储在存储器3004或经由通信组件3016发送。在一些实施例中，音频组件3010还包括一个扬声器，用于输出音频信号。
I/O接口3012为处理组件3002和外围接口模块之间提供接口，上述外围接口模块可以是键盘，点击轮，按钮等。这些按钮可包括但不限于：主页按钮、音量按钮、启动按钮和锁定按钮。
传感器组件3014包括一个或多个传感器，用于为外呼平台3000提供各个方面的状态评估。例如，传感器组件3014可以检测到外呼平台3000的打开/关闭状态，组件的相对定位，例如组件为外呼平台3000的显示器和小键盘，传感器组件3014还可以检测外呼平台3000或外呼平台3000一个组件的位置改变，用户与外呼平台3000接触的存在或不存在，外呼平台3000方位或加速/减速和外呼平台3000的温度变化。传感器组件3014可以包括接近传感器，被配置用来在没有任何的物理接触时检测附近物体的存在。传感器组件3014还可以包括光传感器，如CMOS或CCD图像传感器，用于在成像应用中使用。在一些实施例中，该传感器组件3014还可以包括加速度传感器，陀螺仪传感器，磁传感器，压力传感器或温度传感器。
通信组件3016被配置为便于外呼平台3000和其他设备之间有线或无线方式的通信。外呼平台3000可以接入基于通信标准的无线网络，如Wi-Fi，2G或3G，或它们的组合。在一个示例性实施例中，通信部件3016经由广播信道接收来自外部广播管理系统的广播信号或广播相关信息。在一个示例性实施例中，通信部件3016还包括近场通信(NFC)模块，以促进短程通信。例如，在NFC模块可基于射频识别(RFID)技术，红外数据协会(IrDA)技术，超宽带(UWB)技术，蓝牙(BT)技术和其他技术来实现。
在示例性实施例中，外呼平台3000可以被一个或多个应用专用集成电路(ASIC)、数字信号处理器(DSP)、数字信号处理设备(DSPD)、可编程逻辑器件(PLD)、现场可编程门阵列(FPGA)、控制器、微控制器、微处理器或其他电子元件实现，用于执行图6所示的方法。
在示例性实施例中，还提供了一种包括指令的计算机非易失性可读存储介质，例如包括指令的存储器3004，上述指令可由外呼平台3000的处理器3020执行以完成上述方法。例如，计算机非易失性可读存储介质可以是ROM、随机存取存储器(RAM)、CD-ROM、磁带、软盘和光数据存储设备等。其中，处理器3020被配置为：接收后台服务器发送的待中断的用户数据；根据用户数据对外呼用户列表进行更新；根据更新后的外呼用户列表进行自动外呼。
上述计算机非易失性可读存储介质储有计算机程序，计算机程序用于执行：接收后台服务器发送的待中断的用户数据；根据用户数据对外呼用户列表进行更新；根据更新后的外呼用户列表进行自动外呼。
本申请实施例还提供了一种计算机设备，该计算机设备包括存储器和处理器，存储器用于存储包括程序指令的信息，处理器用于控制程序指令的执行，计算机设备应用在包括后台服务器和外呼平台的系统中，程序指令被处理器加载并执行时实现以下步骤：后台服务器获取待中断的用户数据；后台服务器将用户数据推送给外呼平台；外呼平台根据接收到的用户数据对外呼用户列表进行更新；外呼平台根据更新后的外呼用户列表进行自动外呼。
可选地，程序指令被处理器加载并执行时还实现以下步骤：后台服务器获取需要中断的场景；后台服务器根据需要中断的场景，确定待中断的用户数据。
可选地，程序指令被处理器加载并执行时还实现以下步骤：当需要中断的场景为主动咨询场景时，后台服务器将本次咨询时获取到的用户数据作为待中断的用户数据；当需要中断的场景为在线办理业务场景时，后台服务器将用户输入的用户数据作为待中断的用户数据。
可选地，主动咨询场景包括用户主动呼叫时对应的场景；在线办理业务场景包括在线办理车辆保险业务时对应的场景。
可选地，当需要中断的场景为主动咨询场景时，待中断的用户数据包括用户的电话号码和用于表示场景为主动咨询场景的场景信息；当需要中断的场景为在线办理业务场景时，待中断的用户数据包括用户输入的电话号码、车牌号和用于表示场景为在线办理业务场景的场景信息。
本申请实施例还提供了一种计算机非易失性可读存储介质，计算机非易失性可读存储介质包括存储的程序，计算机非易失性可读存储介质应用在包括后台服务器和外呼平台的系统中，其中，在程序运行时控制计算机非易失性可读存储介质所在设备执行以下步骤：后台服务器获取待中断的用户数据；后台服务器将用户数据推送给外呼平台；外呼平台根据接收到的用户数据对外呼用户列表进行更新；外呼平台根据更新后的外呼用户列表进行自动外呼。
可选地，在程序运行时控制计算机非易失性可读存储介质所在设备还执行以下步骤： 后台服务器获取需要中断的场景；后台服务器根据需要中断的场景，确定待中断的用户数据。
可选地，在程序运行时控制计算机非易失性可读存储介质所在设备还执行以下步骤：当需要中断的场景为主动咨询场景时，后台服务器将本次咨询时获取到的用户数据作为待中断的用户数据；当需要中断的场景为在线办理业务场景时，后台服务器将用户输入的用户数据作为待中断的用户数据。
可选地，主动咨询场景包括用户主动呼叫时对应的场景；在线办理业务场景包括在线办理车辆保险业务时对应的场景。
可选地，当需要中断的场景为主动咨询场景时，待中断的用户数据包括用户的电话号码和用于表示场景为主动咨询场景的场景信息；当需要中断的场景为在线办理业务场景时，待中断的用户数据包括用户输入的电话号码、车牌号和用于表示场景为在线办理业务场景的场景信息。
本领域技术人员在考虑说明书及实践这里公开的公开后，将容易想到本公开的其它实施方案。本申请旨在涵盖本公开的任何变型、用途或者适应性变化，这些变型、用途或者适应性变化遵循本公开的一般性原理并包括本公开未公开的本技术领域中的公知常识或惯用技术手段。说明书和实施例仅被视为示例性的，本公开的真正范围和精神由下面的权利要求指出。
应当理解的是，本公开并不局限于上面已经描述并在附图中示出的精确结构，并且可以在不脱离其范围进行各种修改和改变。本公开的范围仅由所附的权利要求来限制。

Claims (20)

  1. 一种信息处理方法，其特征在于，所述方法应用在包括后台服务器和外呼平台的系统中，所述方法包括：
    所述后台服务器获取待中断的用户数据；
    所述后台服务器将所述用户数据推送给所述外呼平台；
    所述外呼平台根据接收到的所述用户数据对外呼用户列表进行更新；
    所述外呼平台根据更新后的所述外呼用户列表进行自动外呼。
  2. 如权利要求1所述的方法，其特征在于，所述后台服务器获取待中断的用户数据，包括：
    所述后台服务器获取需要中断的场景；
    所述后台服务器根据所述需要中断的场景，确定所述待中断的用户数据。
  3. 如权利要求2所述的方法，其特征在于，所述后台服务器根据所述需要中断的场景，确定所述待中断的用户数据，包括：
    当所述需要中断的场景为主动咨询场景时，所述后台服务器将本次咨询时获取到的用户数据作为所述待中断的用户数据；
    当所述需要中断的场景为在线办理业务场景时，所述后台服务器将用户输入的用户数据作为所述待中断的用户数据。
  4. 如权利要求3所述的方法，其特征在于，
    所述主动咨询场景包括用户主动呼叫时对应的场景；
    所述在线办理业务场景包括在线办理车辆保险业务时对应的场景。
  5. 如权利要求3所述的方法，其特征在于，
    当所述需要中断的场景为主动咨询场景时，所述待中断的用户数据包括用户的电话号码和用于表示场景为主动咨询场景的场景信息；
    当所述需要中断的场景为在线办理业务场景时，所述待中断的用户数据包括用户输入的电话号码、车牌号和用于表示场景为在线办理业务场景的场景信 息。
  6. 一种信息处理系统，其特征在于，所述系统包括后台服务器和外呼平台；
    所述后台服务器，用于获取待中断的用户数据；
    所述后台服务器，用于将所述用户数据推送给所述外呼平台；
    所述外呼平台，用于根据接收到的所述用户数据对外呼用户列表进行更新；
    所述外呼平台，用于根据更新后的所述外呼用户列表进行自动外呼。
  7. 如权利要求6所述的系统，其特征在于，在所述后台服务器用于获取待中断的用户数据时，具体用于：
    所述后台服务器获取需要中断的场景；
    所述后台服务器根据所述需要中断的场景，确定所述待中断的用户数据。
  8. 如权利要求7所述的系统，其特征在于，在所述后台服务器用于根据所述需要中断的场景，确定所述待中断的用户数据时，具体用于：
    当所述需要中断的场景为主动咨询场景时，所述后台服务器将本次咨询时获取到的用户数据作为所述待中断的用户数据；
    当所述需要中断的场景为在线办理业务场景时，所述后台服务器将用户输入的用户数据作为所述待中断的用户数据。
  9. 如权利要求8所述的系统，其特征在于，
    所述主动咨询场景包括用户主动呼叫时对应的场景；
    所述在线办理业务场景包括在线办理车辆保险业务时对应的场景。
  10. 如权利要求8所述的系统，其特征在于，
    当所述需要中断的场景为主动咨询场景时，所述待中断的用户数据包括用户的电话号码和用于表示场景为主动咨询场景的场景信息；
    当所述需要中断的场景为在线办理业务场景时，所述待中断的用户数据包括用户输入的电话号码、车牌号和用于表示场景为在线办理业务场景的场景信息。
  11. 一种计算机设备，包括存储器和处理器，所述存储器用于存储包括程序指令的信息，所述处理器用于控制所述程序指令的执行，其特征在于，所述 计算机设备应用在包括后台服务器和外呼平台的系统中，所述程序指令被所述处理器加载并执行时实现以下步骤：
    所述后台服务器获取待中断的用户数据；
    所述后台服务器将所述用户数据推送给所述外呼平台；
    所述外呼平台根据接收到的所述用户数据对外呼用户列表进行更新；
    所述外呼平台根据更新后的所述外呼用户列表进行自动外呼。
  12. 根据权利要求11所述的计算机设备，其特征在于，所述程序指令被所述处理器加载并执行时还实现以下步骤：
    所述后台服务器获取需要中断的场景；
    所述后台服务器根据所述需要中断的场景，确定所述待中断的用户数据。
  13. 根据权利要求12所述的计算机设备，其特征在于，所述程序指令被所述处理器加载并执行时还实现以下步骤：
    当所述需要中断的场景为主动咨询场景时，所述后台服务器将本次咨询时获取到的用户数据作为所述待中断的用户数据；
    当所述需要中断的场景为在线办理业务场景时，所述后台服务器将用户输入的用户数据作为所述待中断的用户数据。
  14. 根据权利要求13所述的计算机设备，其特征在于，
    所述主动咨询场景包括用户主动呼叫时对应的场景；
    所述在线办理业务场景包括在线办理车辆保险业务时对应的场景。
  15. 根据权利要求13所述的计算机设备，其特征在于，
    当所述需要中断的场景为主动咨询场景时，所述待中断的用户数据包括用户的电话号码和用于表示场景为主动咨询场景的场景信息；
    当所述需要中断的场景为在线办理业务场景时，所述待中断的用户数据包括用户输入的电话号码、车牌号和用于表示场景为在线办理业务场景的场景信息。
  16. 一种计算机非易失性可读存储介质，其特征在于，所述计算机非易失性可读存储介质包括存储的程序，所述计算机非易失性可读存储介质应用 在包括后台服务器和外呼平台的系统中，其中，在所述程序运行时控制所述计算机非易失性可读存储介质所在设备执行以下步骤：
    所述后台服务器获取待中断的用户数据；
    所述后台服务器将所述用户数据推送给所述外呼平台；
    所述外呼平台根据接收到的所述用户数据对外呼用户列表进行更新；
    所述外呼平台根据更新后的所述外呼用户列表进行自动外呼。
  17. 根据权利要求16所述的计算机非易失性可读存储介质，其特征在于，在所述程序运行时控制所述计算机非易失性可读存储介质所在设备还执行以下步骤：
    所述后台服务器获取需要中断的场景；
    所述后台服务器根据所述需要中断的场景，确定所述待中断的用户数据。
  18. 根据权利要求17所述的计算机非易失性可读存储介质，其特征在于，在所述程序运行时控制所述计算机非易失性可读存储介质所在设备还执行以下步骤：
    当所述需要中断的场景为主动咨询场景时，所述后台服务器将本次咨询时获取到的用户数据作为所述待中断的用户数据；
    当所述需要中断的场景为在线办理业务场景时，所述后台服务器将用户输入的用户数据作为所述待中断的用户数据。
  19. 根据权利要求18所述的计算机非易失性可读存储介质，其特征在于，
    所述主动咨询场景包括用户主动呼叫时对应的场景；
    所述在线办理业务场景包括在线办理车辆保险业务时对应的场景。
  20. 根据权利要求18所述的计算机非易失性可读存储介质，其特征在于，
    当所述需要中断的场景为主动咨询场景时，所述待中断的用户数据包括用户的电话号码和用于表示场景为主动咨询场景的场景信息；
    当所述需要中断的场景为在线办理业务场景时，所述待中断的用户数据包括用户输入的电话号码、车牌号和用于表示场景为在线办理业务场景的场景信息。
PCT/CN2018/110587 2018-07-31 2018-10-17 一种信息处理方法和系统 Ceased WO2020024435A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810857993.2A CN109246322B (zh) 2018-07-31 2018-07-31 一种信息处理方法和系统
CN201810857993.2 2018-07-31

Publications (1)

Publication Number Publication Date
WO2020024435A1 true WO2020024435A1 (zh) 2020-02-06

Family

ID=65073314

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/110587 Ceased WO2020024435A1 (zh) 2018-07-31 2018-10-17 一种信息处理方法和系统

Country Status (2)

Country Link
CN (1) CN109246322B (zh)
WO (1) WO2020024435A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111160778A (zh) * 2019-12-30 2020-05-15 佰聆数据股份有限公司 基于大数据的外呼项目审核评估方法、系统及计算机设备

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8443435B1 (en) * 2010-12-02 2013-05-14 Juniper Networks, Inc. VPN resource connectivity in large-scale enterprise networks
CN103327199A (zh) * 2012-03-20 2013-09-25 华为技术有限公司 实现外呼的方法、装置和系统
CN105282349A (zh) * 2014-07-09 2016-01-27 同程网络科技股份有限公司 自动外呼集中控制构架及其控制方法
CN106572087A (zh) * 2016-10-19 2017-04-19 上海携程商务有限公司 语音外呼系统

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102450039B (zh) * 2011-05-31 2013-12-04 华为技术有限公司 外呼方法、外呼服务器及外呼系统
US9014359B1 (en) * 2013-01-11 2015-04-21 Time Warner Cable Enterprises Llc Generation of phone number lists and call filtering
CN108024020A (zh) * 2016-11-03 2018-05-11 广东亿迅科技有限公司 一种基于呼叫中心系统的黑名单管理系统及其实现方法
CN108074123A (zh) * 2016-11-14 2018-05-25 平安科技（深圳）有限公司 外呼名单的分配方法及系统
CN107864300B (zh) * 2016-11-14 2020-01-07 平安科技（深圳）有限公司 外呼方法及系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8443435B1 (en) * 2010-12-02 2013-05-14 Juniper Networks, Inc. VPN resource connectivity in large-scale enterprise networks
CN103327199A (zh) * 2012-03-20 2013-09-25 华为技术有限公司 实现外呼的方法、装置和系统
CN105282349A (zh) * 2014-07-09 2016-01-27 同程网络科技股份有限公司 自动外呼集中控制构架及其控制方法
CN106572087A (zh) * 2016-10-19 2017-04-19 上海携程商务有限公司 语音外呼系统

Also Published As

Publication number Publication date
CN109246322B (zh) 2021-10-29
CN109246322A (zh) 2019-01-18

Similar Documents

Publication Publication Date Title
WO2016183992A1 (zh) 对账户与设备的控制关系进行管理的方法、装置和系统
WO2019109564A1 (zh) 屏幕显示控制的方法和装置
CN109669730B (zh) 一种进程保活方法、装置、电子设备及介质
CN106203167B (zh) 应用权限管理方法及装置
CN109600303B (zh) 内容分享方法、装置及存储介质
US11397596B2 (en) Method and device for controlling pop-up window, electronic device, and storage medium
CN110674343A (zh) 账户信息的处理方法、装置、服务器以及终端
CN105847520A (zh) 实现通话过程中录音的方法及装置
CN105653903B (zh) 应用程序权限的管理方法及装置
CN107094094B (zh) 应用程序的连网方法、装置及终端
EP3136697B1 (en) Contact record processing method and apparatus
WO2020024454A1 (zh) 一种时间信息获取方法、装置和可读存储介质
CN106056010A (zh) 终端处理消息的方法、装置及终端
CN105791097A (zh) 一种群消息接收处理方法、装置及终端
CN106936970A (zh) 通话信息备注方法及装置
CN106126488A (zh) 信息存储方法及装置
CN105843894A (zh) 信息推荐方法及装置
CN107241432B (zh) 消息接收方法、装置、电子设备及计算机可存储介质
CN105786561B (zh) 进程调用的方法及装置
CN106201738B (zh) 系统广播调用方法及装置
CN105893128B (zh) 一种应用程序调用管理的方法和装置
WO2020024436A1 (zh) 一种用户信息的更新方法、系统和服务器
WO2020024435A1 (zh) 一种信息处理方法和系统
CN107846481B (zh) 账户管理方法及装置
CN107885308A (zh) 省电方法及装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18928404

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18928404

Country of ref document: EP

Kind code of ref document: A1