WO2023045673A1 - 呼叫时间提醒的方法及终端 - Google Patents

呼叫时间提醒的方法及终端 Download PDF

Info

Publication number
WO2023045673A1
WO2023045673A1 PCT/CN2022/114237 CN2022114237W WO2023045673A1 WO 2023045673 A1 WO2023045673 A1 WO 2023045673A1 CN 2022114237 W CN2022114237 W CN 2022114237W WO 2023045673 A1 WO2023045673 A1 WO 2023045673A1
Authority
WO
WIPO (PCT)
Prior art keywords
time
call
mobile terminal
user
period
Prior art date
Application number
PCT/CN2022/114237
Other languages
English (en)
French (fr)
Inventor
章亚星
Original Assignee
荣耀终端有限公司
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 荣耀终端有限公司 filed Critical 荣耀终端有限公司
Publication of WO2023045673A1 publication Critical patent/WO2023045673A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M1/00—Substation equipment, e.g. for use by subscribers
    • H04M1/64—Automatic arrangements for answering calls; Automatic arrangements for recording messages for absent subscribers; Arrangements for recording conversations
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M1/00—Substation equipment, e.g. for use by subscribers
    • H04M1/72—Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
    • H04M1/724—User interfaces specially adapted for cordless or mobile telephones
    • H04M1/72448—User interfaces specially adapted for cordless or mobile telephones with means for adapting the functionality of the device according to specific conditions
    • H04M1/72451—User interfaces specially adapted for cordless or mobile telephones with means for adapting the functionality of the device according to specific conditions according to schedules, e.g. using calendar applications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M1/00—Substation equipment, e.g. for use by subscribers
    • H04M1/72—Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
    • H04M1/724—User interfaces specially adapted for cordless or mobile telephones
    • H04M1/72484—User interfaces specially adapted for cordless or mobile telephones wherein functions are triggered by incoming communication events
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/16—Communication-related supplementary services, e.g. call-transfer or call-hold

Definitions

  • the present application relates to the field of terminals, in particular to a method and terminal for calling time reminder.
  • Modern communication networks have provided users with a myriad of features and functions that make it easier to stay in touch with friends, family, colleagues, and others.
  • the called party sometimes receives an incoming call when he is busy or other times when it is inconvenient to answer the call. At this time, the called party cannot answer the incoming call. Faced with this situation, the caller often cannot intuitively know how long it is more appropriate to call again at an interval, and an inappropriate call timing will bring a bad experience to the caller and the called party.
  • This application provides a call time reminder method and terminal, by predicting and reminding the caller of the appropriate time to call again when a missed call occurs, it can solve the problem of low communication efficiency between the two calling parties.
  • a method for reminding call time is provided, which is applied to a first mobile terminal, including: receiving a call initiated by a caller through a second mobile terminal; when it is determined that a missed call event occurs, obtaining time information for calling again; sending a call time reminder message to the second mobile terminal, where the call time reminder message is used to remind the caller of the time information of the call again.
  • the call initiated by the caller through the second mobile terminal may include a call initiated by the caller through telephone dialing, or a call initiated by the caller through an instant messaging application program.
  • time information of calling again may refer to the time when the callee has a higher probability of answering the call.
  • the call time reminder method by analyzing and quantifying the user status, user equipment usage habits, etc., to determine its impact on the re-call time, the prediction result of the re-call time is more accurate, and the probability of a successful call between the two parties is improved. possibility.
  • the time information of calling again is the waiting time of calling again or the time of calling again.
  • the sending the call time reminder message to the second mobile terminal specifically includes: sending the call time reminder message to the second mobile terminal through a short message message; or, send the call time reminder message to the second mobile terminal through an instant messaging application program.
  • the instant messaging may include a third-party instant messaging application program, or may include an instant messaging application program built in the first mobile terminal.
  • the call time reminder message is voice and/or text.
  • the call time prediction model is used to use the user status, the user's usage habits of the first mobile terminal, and the user's use of the first mobile terminal real-time operating frequency.
  • the user may refer to the called party.
  • the user's usage habit of the first mobile terminal may be characterized by the duration of the user's single use of the first mobile terminal, or the duration of the user's use of the first mobile terminal at different times of the day.
  • the real-time operating frequency of the first mobile terminal by the user may be the frequency at which the user uses the first mobile terminal during the period when the missed call event occurs or in a period adjacent to it.
  • the time period involved in the process of characterizing the user's usage habits of the first mobile terminal (denoted as the first time period) and the time period involved in the process of characterizing the user's real-time operation frequency of the first mobile terminal (denoted as the first time period) Two periods), can be flexibly divided according to needs, and the first period and the second period are different.
  • the time information of re-calling is obtained based on the call time prediction model, which specifically includes: collecting target information, and the target information It is used to indicate the user status, the user's usage habits of the first mobile terminal and the user's real-time operation frequency of the first mobile terminal; determine the user event impact factor, equipment usage, etc.
  • the target information rate impact factor and real-time operation frequency impact factor wherein, the user event impact factor is used to indicate the influence of the user habit on the re-call time, and the equipment usage impact factor is used to indicate the user’s influence on the first
  • the real-time operation frequency impact factor is used to indicate the impact of the user's real-time operation frequency on the first mobile terminal on the re-call time
  • the equipment utilization rate influencing factor and the real-time operating frequency influencing factor determine the time information of calling again.
  • the determining the time information of calling again according to the user event influencing factor, the equipment usage influencing factor and the real-time operating frequency influencing factor It specifically includes: determining the callback timeliness parameter according to the user event impact factor, the equipment usage rate impact factor and the real-time operation frequency impact factor, and the callback timeliness parameter is used to indicate the timeliness of calling again; The pre-acquired historical callback duration of the user and the callback timeliness parameter obtain the time information of the call again.
  • the The method further includes: converting the timeliness of the callback to obtain a conversion parameter, and the conversion parameter is positively correlated with the waiting time for calling again.
  • the corresponding relationship between the user status and the user event influencing factor is obtained; the current user status of the user is determined according to the target information; The user event influencing factor corresponding to the current user status of the user is determined in the corresponding relationship between the user status and the user event influencing factor.
  • the method further includes: dividing the first period of a day into multiple sub-periods, and the duration of each sub-period is the first duration; obtaining each of the The duration during which the first mobile terminal is not used within the sub-period.
  • the first time period of a day may refer to the whole day, that is, the first time period may be a time period from 00:00 to 24:00.
  • the first time period may also be a time period during a day when the user has a call requirement, such as 09:00-18:00 during working hours.
  • the method further includes: acquiring the occurrence time of the missed call event, and determining the target sub-period where the occurrence time is located, the target sub-period It is a certain one of the multiple sub-periods; according to the first duration and the unused duration of the first mobile terminal in the target sub-period, determine the device utilization factor influencing factor.
  • multiple time periods during which the first mobile terminal is not used in the target sub-period in multiple days within the preset historical period are obtained;
  • the first time length and the time length during which the first mobile terminal is not used within the target sub-period, and determining the device usage factor specifically includes: determining the first mobile terminal within the target sub-period in the multiple days The average value of multiple periods of time when the mobile terminal is not in use, to obtain the average period of time in which the first mobile terminal is not in use within the target sub-period; according to the first duration and the first The average duration of non-use of the mobile terminal is used to determine the influencing factor of the device utilization rate.
  • the method provided by this implementation by counting the device use (or non-use) time of the user in the target sub-period for a long period of time, calculating the average value, and then using the average value to determine the impact factor of the device usage rate, it is possible to use more
  • the data can more accurately reflect the impact of the user's device usage habits on the time to call again, so that the time to call again can be more accurately predicted based on the usage factor.
  • determining the influence of the device usage rate according to the first duration and the duration during which the first mobile terminal is not used within the target sub-period factors including: Wherein, IF2 represents the device utilization factor, T1 represents the first duration of the sub-period, and t represents the average non-use duration of the first mobile terminal within the target sub-period.
  • the method further includes: determining a second time period based on the time when the missed call event occurs; selecting multiple moment, and the time interval between every two adjacent moments is the second duration; at each said moment, whether the user uses the first mobile terminal is counted; Whether the statistics result of the first mobile terminal is used at the time and the number of the time are used to determine the real-time operating frequency influencing factor.
  • a mobile terminal including: one or more processors; one or more memories; the one or more memories store one or more computer programs, and the one or more computer programs Instructions are included, and when the instructions are executed by the one or more processors, the terminal device executes the method described in any implementation manner of the above first aspect.
  • a computer-readable storage medium stores a computer-executable program, and when the computer-executable program is invoked by a computer, the computer executes the above-mentioned first aspect.
  • a computer program product including instructions is provided, and when the computer program product is run on a terminal device, the terminal device is made to execute the method described in any implementation manner of the above first aspect.
  • FIG. 1A and FIG. 1B are schematic diagrams of interfaces of some call reminders.
  • FIG. 2 is a schematic diagram of a system architecture applicable to a calling time reminder method provided in an embodiment of the present application.
  • FIG. 3 is a schematic structural diagram of a first mobile terminal 100 provided in an embodiment of the present application.
  • FIG. 4 is a block diagram of the software structure of the first mobile terminal 100 according to the embodiment of the present application.
  • 5A to 5D are schematic diagrams of some GUIs that may be involved in the setting process of the call time prediction function provided by the embodiment of the present application.
  • FIG. 6A and FIG. 6B are schematic diagrams of GUIs when some callers receive a call time reminder message according to the embodiment of the present application.
  • FIG. 7 is a schematic flowchart of a method for calling time reminder provided by an embodiment of the present application.
  • FIG. 8 is a schematic structural diagram of a main frame of a calling time prediction system 800 provided in an embodiment of the present application.
  • FIG. 9 is a schematic diagram of functions of modules of a calling time prediction system 800 provided in an embodiment of the present application.
  • FIG. 10 is a schematic flowchart of call time prediction performed by various modules of the call time prediction system 800 provided in the embodiment of the present application.
  • FIG. 11 is a schematic flowchart of another method for calling time reminder provided by the embodiment of the present application.
  • Fig. 12 is a schematic diagram of the time duration distribution of a user not using a device in different time periods according to an embodiment of the present application.
  • first and second are used for descriptive purposes only, and cannot be understood as indicating or implying relative importance or implicitly specifying the quantity of indicated technical features.
  • definition of “first” and “second” features may expressly or implicitly include one or more of these features.
  • references to "one embodiment” or “some embodiments” or the like in this specification means that a particular feature, structure, or characteristic described in connection with the embodiment is included in one or more embodiments of the present application.
  • appearances of the phrases “in one embodiment,” “in some embodiments,” “in other embodiments,” “in other embodiments,” etc. in various places in this specification are not necessarily All refer to the same embodiment, but mean “one or more but not all embodiments” unless specifically stated otherwise.
  • the terms “including”, “comprising”, “having” and variations thereof mean “including but not limited to”, unless specifically stated otherwise.
  • the call process refers to the process of exchanging two-way voice streams and video streams between users on both sides of the call with the help of mobile terminals.
  • the call process can be a point-to-point call, for example, the users on both sides of the call use a walkie-talkie to perform the call process.
  • the call process can also be transferred by other devices to complete the call.
  • a subscriber identification module (subscriber identification module, SIM) card is installed in the terminal device, and the SIM card is used to perform a call process through the operator network.
  • an instant messaging application such as WeChat, skype, etc.
  • the instant messaging application is used to execute the call process.
  • a call refers to the establishment of a connection between users in a communication.
  • the automatic telephone exchange system as an example, it is the actions that the caller performs in order to get in touch with the called person, that is, the actions required to make a call.
  • the called party can remind the caller that it is inconvenient for the called party to answer the call at present by sending a reminder text message or the like through the terminal.
  • a reminder text message or the like For example, as shown in Figure 1A and Figure 1B, in a possible scenario, if the callee receives a mobile phone call during the meeting, the callee can click the text message on the incoming call page as shown in Figure 1A Icon 101, and on the page shown in Figure 1B, select the appropriate text message reply content (such as "being in a meeting, contact later") or edit the text message reply content independently to send to the caller, and inform the caller that it is inconvenient to answer the phone now.
  • the appropriate text message reply content such as "being in a meeting, contact later
  • the existing reminder method can only make the caller know that it is not suitable to contact the other party at present, but cannot know when to call the other party again to make a successful call, resulting in poor user experience.
  • the embodiment of the present application provides a call time reminder method, by predicting the time of calling again according to the user status of the callee, the user's device usage habits, the user's real-time operation of the device, etc. Push it to the caller, so that the caller can initiate the call again at the right time, thereby increasing the probability of a successful call between the two parties and improving the user experience.
  • FIG. 2 it is a schematic diagram of a system architecture applicable to a calling time reminder method provided in an embodiment of the present application.
  • the system architecture includes a first mobile terminal 100 of a callee (or called party) and a second mobile terminal 200 of a caller (or called party).
  • a communication connection can be established between the first mobile terminal 100 and the second mobile terminal 200 through a wired network or a wireless network.
  • the first mobile terminal 100 can establish a communication connection with the second mobile terminal 200 through a cellular network
  • the cellular network can be, for example, the fifth generation mobile communication technology (5 th generation, 5G), the sixth generation mobile communication technology (6 th generation , 6G) and future arbitrary communication systems, etc.
  • the embodiment of the present application does not specifically limit the network type for communication between the first mobile terminal 100 and the second mobile terminal 200 .
  • the first mobile terminal 100 and the second mobile terminal 200 can be various types of electronic devices with voice and/or video call capabilities, such as mobile phones, tablet computers (pad), notebook computers, desktop Computers, in-vehicle devices, wearable devices, ultra-mobile personal computers (UMPC), netbooks, personal digital assistants (personal digital assistants, PDAs), wireless terminals in industrial control (industrial control), unmanned driving Wireless terminals in (self driving), wireless terminals in remote medical, wireless terminals in smart grid, wireless terminals in transportation safety, and smart cities Terminal devices such as wireless terminals, wireless terminals in smart homes, and artificial intelligence devices, the embodiment of the present application does not impose any restrictions on the specific types of the first mobile terminal 100 and the second mobile terminal 200.
  • FIG. 3 it is a schematic structural diagram of a first mobile terminal 100 provided in this embodiment of the present application.
  • FIG. 3 shows a schematic structural diagram of the first mobile terminal 100 .
  • the first mobile terminal 100 may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (universal serial bus, USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, Antenna 2, mobile communication module 150, wireless communication module 160, audio module 170, speaker 170A, receiver 170B, microphone 170C, earphone jack 170D, sensor module 180, button 190, motor 191, indicator 192, camera 193, display screen 194 , and a subscriber identification module (subscriber identification module, SIM) card interface 195, etc.
  • SIM subscriber identification module
  • the sensor module 180 may include a pressure sensor 180A, a gyroscope sensor 180B, an air pressure sensor 180C, a magnetic sensor 180D, an acceleration sensor 180E, a distance sensor 180F, a proximity light sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, bone conduction sensor 180M, etc.
  • the structure illustrated in the embodiment of the present application does not constitute a specific limitation on the first mobile terminal 100 .
  • the first mobile terminal 100 may include more or fewer components than shown in the illustration, or combine some components, or separate some components, or arrange different components.
  • the illustrated components can be realized in hardware, software or a combination of software and hardware.
  • the processor 110 may include one or more processing units, for example: the processor 110 may include an application processor (application processor, AP), a modem processor, a graphics processing unit (graphics processing unit, GPU), an image signal processor (image signal processor, ISP), controller, memory, video codec, digital signal processor (digital signal processor, DSP), baseband processor, and/or neural network processor (neural-network processing unit, NPU) wait. Wherein, different processing units may be independent devices, or may be integrated in one or more processors.
  • application processor application processor, AP
  • modem processor graphics processing unit
  • GPU graphics processing unit
  • image signal processor image signal processor
  • ISP image signal processor
  • controller memory
  • video codec digital signal processor
  • DSP digital signal processor
  • baseband processor baseband processor
  • neural network processor neural-network processing unit, NPU
  • the controller may be the nerve center and command center of the first mobile terminal 100 .
  • the controller can generate an operation control signal according to the instruction opcode and timing signal, and complete the control of fetching and executing the instruction.
  • a memory may also be provided in the processor 110 for storing instructions and data.
  • the memory in processor 110 is a cache memory.
  • the memory may hold instructions or data that the processor 110 has just used or recycled. If the processor 110 needs to use the instruction or data again, it can be called directly from the memory. Repeated access is avoided, and the waiting time of the processor 110 is reduced, thus improving the efficiency of the system.
  • processor 110 may include one or more interfaces.
  • the interface may include an integrated circuit (inter-integrated circuit, I2C) interface, an integrated circuit built-in audio (inter-integrated circuit sound, I2S) interface, a pulse code modulation (pulse code modulation, PCM) interface, a universal asynchronous transmitter (universal asynchronous receiver/transmitter, UART) interface, mobile industry processor interface (mobile industry processor interface, MIPI), general-purpose input and output (general-purpose input/output, GPIO) interface, subscriber identity module (subscriber identity module, SIM) interface, and /or universal serial bus (universal serial bus, USB) interface, etc.
  • I2C integrated circuit
  • I2S integrated circuit built-in audio
  • PCM pulse code modulation
  • PCM pulse code modulation
  • UART universal asynchronous transmitter
  • MIPI mobile industry processor interface
  • GPIO general-purpose input and output
  • subscriber identity module subscriber identity module
  • SIM subscriber identity module
  • USB universal serial bus
  • the I2S interface can be used for audio communication.
  • processor 110 may include multiple sets of I2S buses.
  • the processor 110 may be coupled to the audio module 170 through an I2S bus to implement communication between the processor 110 and the audio module 170 .
  • the audio module 170 can transmit audio signals to the wireless communication module 160 through the I2S interface, so as to realize the function of answering calls.
  • the PCM interface can also be used for audio communication, sampling, quantizing and encoding the analog signal.
  • the audio module 170 and the wireless communication module 160 may be coupled through a PCM bus interface.
  • the audio module 170 can also transmit audio signals to the wireless communication module 160 through the PCM interface, so as to realize the function of answering calls. Both the I2S interface and the PCM interface can be used for audio communication.
  • the interface connection relationship between the modules shown in the embodiment of the present application is only a schematic illustration, and does not constitute a structural limitation of the first mobile terminal 100 .
  • the first mobile terminal 100 may also adopt different interface connection methods in the above embodiments, or a combination of multiple interface connection methods.
  • the wireless communication function of the first mobile terminal 100 can be realized by the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, the modem processor and the baseband processor.
  • the mobile communication module 150 can provide wireless communication solutions including 2G/3G/4G/5G applied on the first mobile terminal 100 .
  • the mobile communication module 150 may include at least one filter, switch, power amplifier, low noise amplifier (low noise amplifier, LNA) and the like.
  • the mobile communication module 150 can receive electromagnetic waves through the antenna 1, filter and amplify the received electromagnetic waves, and send them to the modem processor for demodulation.
  • the mobile communication module 150 can also amplify the signals modulated by the modem processor, and convert them into electromagnetic waves through the antenna 1 for radiation.
  • at least part of the functional modules of the mobile communication module 150 may be set in the processor 110 .
  • at least part of the functional modules of the mobile communication module 150 and at least part of the modules of the processor 110 may be set in the same device.
  • the wireless communication module 160 can provide applications on the first mobile terminal 100 including wireless local area networks (wireless local area networks, WLAN) (such as wireless fidelity (wireless fidelity, Wi-Fi) network), bluetooth (bluetooth, BT), global Wireless communication solutions such as global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), and infrared (IR).
  • the wireless communication module 160 may be one or more devices integrating at least one communication processing module.
  • the wireless communication module 160 receives electromagnetic waves via the antenna 2 , frequency-modulates and filters the electromagnetic wave signals, and sends the processed signals to the processor 110 .
  • the wireless communication module 160 can also receive the signal to be sent from the processor 110 , frequency-modulate it, amplify it, and convert it into electromagnetic waves through the antenna 2 for radiation.
  • the software system of the first mobile terminal 100 may adopt a layered architecture, an event-driven architecture, a micro-kernel architecture, a micro-service architecture, or a cloud architecture.
  • the software structure of the first mobile terminal 100 is exemplarily described by taking an Android system with a layered architecture as an example.
  • FIG. 4 is a block diagram of the software structure of the first mobile terminal 100 according to the embodiment of the present application.
  • the layered architecture divides the software into several layers, and each layer has a clear role and division of labor. Layers communicate through software interfaces.
  • the Android system is divided into four layers, which are respectively the application program layer, the application program framework layer, the Android runtime (Android runtime) and the system library, and the kernel layer from top to bottom.
  • the application layer can consist of a series of application packages.
  • the application package may include application programs such as camera, gallery, calendar, call, map, navigation, WLAN, Bluetooth, music, video, and short message.
  • the application framework layer provides an application programming interface (application programming interface, API) and a programming framework for applications in the application layer.
  • the application framework layer includes some predefined functions. As shown in Figure 4, the application framework layer can include window manager, content provider, view system, phone manager, resource manager, notification manager, etc.
  • a window manager is used to manage window programs.
  • the window manager can get the size of the display screen, determine whether there is a status bar, lock the screen, capture the screen, etc.
  • Content providers are used to store and retrieve data and make it accessible to applications.
  • Said data may include video, images, audio, calls made and received, browsing history and bookmarks, phonebook, etc.
  • the view system includes visual controls, such as controls for displaying text, controls for displaying pictures, and so on.
  • the view system can be used to build applications.
  • a display interface can consist of one or more views.
  • a display interface including a text message notification icon may include a view for displaying text and a view for displaying pictures.
  • the phone manager is used to provide a communication function of the first mobile terminal 100 .
  • the management of call status including connected, hung up, etc.).
  • the resource manager provides various resources for the application, such as localized strings, icons, pictures, layout files, video files, and so on.
  • the notification manager enables the application to display notification information in the status bar, which can be used to convey notification-type messages, and can automatically disappear after a short stay without user interaction.
  • the notification manager is used to notify the download completion, message reminder, etc.
  • the notification manager can also be a notification that appears on the top status bar of the system in the form of a chart or scroll bar text, such as a notification of an application running in the background, or a notification that appears on the screen in the form of a dialog window. For example, prompting text information in the status bar, emitting a prompt sound, terminal vibration, and indicator light flashing, etc.
  • the Android Runtime includes core library and virtual machine. The Android runtime is responsible for the scheduling and management of the Android system.
  • the core library consists of two parts: one part is the function function that the java language needs to call, and the other part is the core library of Android.
  • the application layer and the application framework layer run in virtual machines.
  • the virtual machine executes the java files of the application program layer and the application program framework layer as binary files.
  • the virtual machine is used to perform functions such as obstacle life cycle management, stack management, thread management, security and exception management, and garbage collection.
  • a system library can include multiple function modules. For example: surface manager (surface manager), media library (Media Libraries), 3D graphics processing library (eg: OpenGL ES), 2D graphics engine (eg: SGL), etc.
  • the surface manager is used to manage the display subsystem and provides the fusion of 2D and 3D layers for multiple applications.
  • the media library supports playback and recording of various commonly used audio and video formats, as well as still image files, etc.
  • the media library can support a variety of audio and video encoding formats, such as: MPEG4, H.264, MP3, AAC, AMR, JPG, PNG, etc.
  • the 3D graphics processing library is used to implement 3D graphics drawing, image rendering, compositing, and layer processing, etc.
  • 2D graphics engine is a drawing engine for 2D drawing.
  • the kernel layer is the layer between hardware and software.
  • the kernel layer includes at least a display driver, a camera driver, an audio driver, and a sensor driver.
  • the method for reminding the call time may be applied in various application scenarios where the callee does not answer the call (such as a call call, a video call, etc.).
  • the callee's mobile terminal obtains a missed call (such as the callee misses, rejects the call initiated by the caller, etc.)
  • the mobile terminal can predict the time when the callee is convenient to answer the call according to the call time prediction model , and push it to the caller's mobile terminal to remind the caller to initiate the call again at an appropriate time.
  • the calling time reminding method provided in the embodiment of the present application, the caller's probability of calling again can be improved, and the call experience of the user can be improved.
  • the callee's first mobile terminal has a call time prediction function
  • the opening mode of this function may include multiple methods, such as: (1) the user (such as the callee) independently opens this function according to needs; (2) When the first mobile terminal detects that there is a missed call, the function is automatically enabled; (3) the first mobile terminal defaults that the function is enabled.
  • FIG. 5A to FIG. 5D they are schematic diagrams of some user graphical interfaces (user graphical interface, GUI) that may be involved in the setting process of the call time prediction function provided by the embodiment of the present application.
  • GUI user graphical interface
  • the home screen interface may include an application icon display area 10 for displaying various types of application (application, App) icons, such as a clock icon, a calendar icon, a gallery icon, a memo icon, a file management icon, an email icon, a music icon, etc. icon, determiner icon, video icon, sports health icon, weather icon, browser icon, smart assistant icon, settings icon, voice recorder icon, etc.
  • application application, App
  • a tray application icon display area 30 may be displayed below the page indicator, for displaying a plurality of tray application icons, such as a camera application icon, an address book application icon, a phone dial application icon, an information application icon, and the like.
  • the main screen interface of the mobile phone may include more or less application program icons or tray application icons than shown in the figure, which is not limited in this application.
  • a status bar 40 can also be displayed on the top of the main screen interface, and the status bar 40 can include: one or more signal strength indicators of mobile communication signals (or cellular signals), wireless fidelity (wireless fidelity, Wi- Fi) One or more signal strength indicators of the signal, battery indicator of the mobile phone, time indicator, etc.
  • the mobile phone may receive an input operation (such as a click operation) from the user (such as the callee) on the setting icon; in response to the above input operation, the mobile phone may display the setting details interface as shown in FIG. 5B .
  • an input operation such as a click operation
  • the user such as the callee
  • the setting details interface may include multiple business setting items (or business setting columns), such as wireless and network setting items, Bluetooth setting items, desktop and wallpaper setting items, display setting items, sound setting items, call Setting entries, battery setting entries, storage setting entries, healthy use of mobile phone setting entries, security and privacy setting entries, etc.
  • the call setting item can be used to set the call (such as a voice call, a video call), such as a call back reminder can be set, so that when the callee does not answer the call, the mobile phone can push the call time reminder message to the caller.
  • the setting details interface may also include more or fewer types of setting items than those shown in the illustration, which is not limited in this application.
  • the mobile phone may receive an input operation (such as a click operation) performed by the user on the call setting item; in response to the above operation, the mobile phone may display the call setting interface as shown in FIG. 5C .
  • an input operation such as a click operation
  • the call setting interface may include a call time reminder-general setting column, and a description for this option may be displayed under the call time reminder-general setting column, such as "When this function is enabled, when there is an unavailable When answering a call, you can push the call time reminder to the caller to notify the appropriate time to call again, so as to improve the possibility of successful call.”
  • the call setting interface can also be set with a call time reminder-custom setting bar.
  • a description for this function may be displayed under the call time reminder-custom setting option, such as "When this function is turned on, the call time reminder can be turned on for a specific contact, and the appropriate time for calling again can be pushed to the specific contact.”
  • the user can select to enable the switch control in the Call Time Reminder-General Settings column to enable the call time reminder general mode.
  • the call time reminder general mode can refer to any call received, when the user does not answer, the call time reminder can be pushed to the corresponding caller, prompting the caller to call again at an appropriate time; or, the call time
  • the reminder general mode can also filter invalid numbers, and only push the call time reminder message to the caller corresponding to the valid number.
  • an invalid number may refer to a number of a virtual advertiser or salesman, or a number marked as invalid by the user; in contrast, a valid number may be a number conforming to the format specified by the call operator, or a number that has not been marked as invalid by the user.
  • the call time reminder general mode may not perform call time prediction for the missed call, that is to say, even if the call If the call is not answered, the called party will not push the call time reminder message to the caller.
  • the user can also choose to enable the switch control in the call time reminder-custom setting column, and use the custom mode of call time reminder.
  • the mobile phone can display contacts under different types of calls, such as contacts in the address book, WeChat contacts, QQ contacts people wait.
  • the user can input an operation (such as a click operation) that acts on the next page indicator corresponding to a contact of a certain call type, and set a call time reminder for a specific contact under the call type on the next page.
  • the mobile phone can display the address book as shown in Figure 5D
  • the contact interface after which, the user can perform personalized settings on whether to enable the call time reminder function for different contacts in the contact interface of the address book.
  • the call setting interface may also include a bar for adding contacts of other call types, and the user may add contact information of other call types by inputting an operation (such as a click operation) acting on the adding bar.
  • an operation such as a click operation
  • the interface of contacts in the address book may include a list of contacts in the address book, and a call-back reminder switch control is set in a column corresponding to each contact.
  • a way for the user to personalize whether to enable the call-back reminder function for different contacts may be, for example, as follows: the user sets the call-back reminder function corresponding to different contacts to on or off by controlling the switch control.
  • the callee can set the callback reminder switch of the father, mother, and friend A in the address book contacts to an on state, and set the callback reminder switch controls corresponding to friend B and friend C It is closed, which means that when the callee does not answer the call from any one of his father, mother, or friend A, the callee's mobile phone can automatically send a call time reminder message to the other party; and when the callee does not answer When the mobile phone of friend B or friend C is connected, the called party's mobile phone will not send the call time message to the other party.
  • call time reminder setting method shown in Figure 5A to Figure 5D is only an example, in practical applications, it can also be set in other ways, for example, the call duration reminder function can be implemented in the call application Settings (including call time reminder general settings and call time reminder custom settings), etc., are not limited in this application.
  • FIG. 6A and FIG. 6B it is a schematic diagram of a GUI when some callers receive a call time reminder message according to the embodiment of the present application.
  • the call time reminder message may be presented to the caller in different forms, such as text and/or voice.
  • the call type is a telephone call
  • the call time reminder message can be sent to the caller in the form of a short message, and the content of the short message can indicate the waiting time for another call, such as "Hello!
  • the call time reminder message can be passed through the instant messaging App Reply to the caller, the content of the message is, for example, "Hello, the call you initiated was not answered in time, and the call may be successfully answered after 20 minutes, thank you”.
  • the call time reminder message may also indicate the specific time or specific period when the caller calls again.
  • the content of the call time reminder message may also be "Hello, the call you called was not answered in time, and calling the owner again at 09:40 may be successfully answered, thank you”.
  • the content of the call time reminder message may also be "Hello, the call you called was not answered in time, and calling the owner again during the period of 09:40-09:45 may be successfully answered” and so on.
  • the called person pushes the time information of calling again to the caller, which can increase the probability of a successful conversation between the two parties when the caller calls again, thereby improving the efficiency of the call , and improve user experience.
  • FIG. 7 it is a schematic flowchart of a method for calling time reminder provided by the embodiment of the present application.
  • the method may be performed by the called party's first mobile terminal, and may specifically include the following steps:
  • the first mobile terminal receives a call initiated by a caller through the second mobile terminal.
  • the first mobile terminal is the terminal equipment of the callee
  • the second mobile terminal is the terminal equipment of the caller
  • the types of calls initiated by the caller can be various, for example, it may include: a call initiated by dialing a mobile phone; or a call initiated by an instant messaging App.
  • the call can be a voice call or a video call.
  • the embodiment of the present application does not limit the method of initiating a call and the specific type of the call.
  • the callee's terminal automatically hangs up after the call duration reaches the preset threshold, or the callee's terminal is set to the do-not-disturb mode The call is automatically hung up, the callee's terminal is set to call transfer mode and the call is not answered, etc.
  • the first mobile terminal when there is a missed call event, in response to the missed call event, the first mobile terminal will perform a call time prediction operation based on the call time prediction model, wherein the call time prediction operation is used to predict the probability of calling again The time is appropriate to increase the probability that the user will make another successful call.
  • the call time prediction model can be used to obtain the time information of calling again according to the user status, the user's usage habits of the first mobile terminal, and the user's real-time operation frequency of the first mobile terminal.
  • the user in the embodiment of the present application may refer to the called party.
  • the user's usage habits of the first mobile terminal can be characterized by the length of time the user uses the first mobile terminal for a single time, or the length of time the user uses the first mobile terminal at different times of the day; the user's real-time operation of the first mobile terminal
  • the frequency may be the frequency at which the user uses the first mobile terminal during the period when the missed call event occurs or in a period nearby.
  • the above-mentioned time periods involved in characterizing the user's habit of using the first mobile terminal may be, for example, dividing the first time period of a day (such as 00:00-24:00, etc.) into multiple sub-time periods, each sub-time period
  • the duration of the time period is the first duration; characterize the time period involved in the real-time operation frequency process of the first mobile terminal by the user (recorded as the second time period), which can be the time period at which the missed call event occurs or is related to the missed call
  • the second time period may be determined based on the time when the missed call event occurs, for example, the second time period may be within 2 minutes after the missed call event occurs.
  • the above-mentioned first time period and second time period can be flexibly divided according to needs, and the first time period and the second time period can be different.
  • the process for the first mobile terminal to obtain the time information of calling again based on the call time prediction model may include: the first mobile terminal collects target information, and the target information is used to indicate the user status, the user's usage habits of the first mobile terminal and the real-time operating frequency of the user on the first mobile terminal; afterward, the first mobile terminal determines the user event influencing factor, the device usage influencing factor and the real-time operating frequency influencing factor according to the target information, wherein the user event influencing factor is used to indicate the user's habit
  • the equipment utilization factor is used to indicate the impact of the user's usage habits on the first mobile terminal on the call time again
  • the real-time operation frequency impact factor is used to indicate the user's real-time operation on the first mobile terminal Influence of frequency on re-call time;
  • the first mobile terminal may determine the time information of re-call according to the user event influence factor, equipment usage influence factor and real-time operation frequency influence factor.
  • the first mobile terminal may determine the callback timeliness parameter according to the user event influencing factor, the device usage influencing factor and the real-time operating frequency influencing factor, and the callback timely parameter is used to indicate the timeliness of calling again; after that, the second A mobile terminal can obtain the time information of calling again according to the pre-acquired historical callback duration and callback timeliness parameters of the user.
  • the time information of calling again is the waiting time of calling again, and the timeliness parameter of callback is negatively correlated with the waiting time of calling again, according to the historical callback time of the user and the timeliness parameter of callback
  • the time information for calling again can specifically include: the first mobile terminal converts the timeliness of the callback to obtain a conversion parameter, which is positively correlated with the waiting time for calling again; after that, the first mobile terminal can call back according to the user's history
  • the duration and transition parameters get information about when to call again.
  • the first mobile terminal may determine the user event influencing factor according to the user state, and the specific process may include: the first mobile terminal may obtain the user state and user event in various ways (such as from a server, a third-party device, etc.) The corresponding relationship between the influencing factors, wherein the corresponding relationship can be manually determined based on experience; when a missed call event occurs, the first mobile terminal can determine the current user state of the user according to the target information, and from the user state The user event influencing factor corresponding to the current user state is determined in the corresponding relationship with the user event influencing factor.
  • the user event influencing factor can also be determined according to the user state in the following manner: the first mobile terminal can obtain a coefficient corresponding to the user state in advance (such as from a server, a third-party device, etc.), and the coefficient can be used In order to characterize the probability that a user can answer a call under different user states, these coefficients may all be within the same preset coefficient range; when a missed call event occurs, the first mobile terminal may determine the user’s call according to the target information.
  • the current user state, and the coefficient corresponding to the user state that the user is currently in can be selected, and the corresponding user event impact factor can be determined according to a preset algorithm.
  • the first mobile terminal may also determine the device usage factor according to the habit of using the device.
  • the specific process may include: first, dividing the first period of the day into multiple sub-periods, and the duration of each sub-period is First duration; after that, obtain the unused duration of the first mobile terminal in each sub-period; when a missed call event occurs, obtain the occurrence time of the missed call event, and determine the target sub-period where the occurrence time is located , wherein, the target sub-period is one of the above multiple sub-periods; then, according to the first duration and the unused duration of the first mobile terminal within the target sub-period, determine the device usage factor.
  • the unused duration of the first mobile terminal within the target sub-period may be determined based on the unused duration of the first mobile terminal within a preset historical period.
  • the first mobile terminal can obtain a plurality of time lengths during which the first mobile terminal is not used in the target sub-period of multiple days in the preset historical period (such as within a year); then, determine the first mobile terminal in the target sub-period of the multiple days
  • the average value of multiple time lengths when the terminal is not in use is used to obtain the average time length in which the first mobile terminal is not used in the target sub-period; after that, use the average time length in which the first mobile terminal is not used in the target sub-period based on the first time length and the average Duration, to determine the impact factor of equipment usage.
  • the first mobile terminal may determine the real-time operating frequency influencing factor according to the device operating frequency of the user during the time period (or adjacent time period) when the missed call event occurs.
  • the specific process may include: the first mobile terminal determines the second time period based on the time when the missed call event occurs, and the second time period is the time period where the missed call event occurs, or is related to the time when the missed call event occurs.
  • the call event takes place in a period adjacent to the time; then, based on preset rules, select a plurality of moments in the second period, and make the time interval between every two adjacent moments the second duration; Whether the user uses the first mobile terminal at each moment; then, determine the real-time operating frequency impact factor according to the statistical results of whether the user uses the first mobile terminal at each moment, and the number of moments.
  • the specific process of triggering the first mobile terminal to perform the call time prediction operation may include: when the call is not answered, the first mobile terminal may generate corresponding missed call information, such as missed call information, missed Receive video call information, etc.; when the first mobile terminal detects that there is newly added missed call information, it can be determined that a missed call event occurs; Obtain the predicted recall time information.
  • missed call information such as missed call information, missed Receive video call information, etc.
  • the first mobile terminal may also determine the occurrence of the missed call event in other ways, for example: when the first mobile terminal detects that the system automatically hangs up the call, it may determine that the missed call event occurs; or, when the first mobile terminal When the terminal detects that the callee enters the operation of hanging up the call, it can determine that a missed call event occurs; or, when the first mobile terminal detects that the call is stopped, and the call has not been answered before the stop, it can determine that A missed call event, etc., should occur.
  • the above-mentioned method for the first mobile terminal to determine the occurrence of the missed call event is only an example. In practical applications, the first mobile terminal can also determine the occurrence of the missed call event in other ways. The embodiment of the present application There is no limit to this.
  • the first mobile terminal sends a call time reminder message to the second mobile terminal, where the call time reminder message is used to remind the caller of time information for calling again.
  • the time information of calling again may include, for example, the waiting time for calling again or the specific time of calling again.
  • the following will take the time information of calling again as the waiting time for calling again as an example.
  • the first mobile terminal may generate missed call information associated with the missed call event, and the missed call information may include, for example, the type of call, communication information of the caller, The identification (identification, ID) of the caller (such as phone number, instant messaging number (such as WeChat ID, QQ number), etc.), the time when the call is received, etc.
  • the first mobile terminal can obtain the caller's communication information according to the missed call information, and send a call time reminder message to the second mobile terminal according to the communication information.
  • the first mobile terminal may push the call time reminder message to the second mobile terminal in a manner consistent with the call type. For example, if the second mobile terminal initiates a call to the first mobile terminal by means of a mobile phone dial, the first mobile terminal can push the call time reminder to the second mobile terminal according to the acquired missed call information of the second mobile terminal. information. For another example, if the second mobile terminal initiates a call to the first mobile terminal through an instant messaging App (such as WeChat), the first mobile terminal can send a call to the corresponding contact person through the instant messaging App according to the call missed information corresponding to the call. Send a call time reminder message.
  • an instant messaging App such as WeChat
  • the call time reminder message can be embodied in various forms.
  • the call time reminder message can be presented in a text form (such as SMS text, WeChat text, etc.), as shown in FIG. 6A or FIG. 6B.
  • the call time reminder message may also be presented in a voice form (such as MMS voice, WeChat voice, etc.).
  • the terminal device of the callee can predict the time information that the callee is convenient to answer, and push the time information to the caller, thereby Remind the caller to re-initiate the call to the called party at the right time to increase the possibility of a successful call between the two parties, thereby improving the user's call experience.
  • the call time prediction function of the first mobile terminal may be implemented by a call time prediction model.
  • a call time prediction model can be used to obtain the time information of calling again according to the user's state, the user's usage habits of the first mobile terminal and the user's real-time operation frequency of the first mobile terminal, so that the caller can be more accurately reminded of the time of calling again, improving The probability that the calling party and the called party will successfully communicate.
  • FIG. 8 it is a schematic structural diagram of a main frame of a call time prediction system 800 provided in the embodiment of the present application.
  • the call time prediction system 800 may include a data collection and processing module 801 , a callback timeliness evaluation module 802 , a parameter conversion module 803 and a call callback duration prediction module 804 .
  • the call time prediction system 800 can also be described as a call time prediction model, and each module it includes can be located at the application layer as shown in FIG. 4 .
  • the data collection and processing module 801 is mainly responsible for collecting data related to user status, user's device usage habits, user's real-time operation of the device, and processing these data. Among them, the data collection and processing module 801 can collect data related to user status, user's device practical habits, etc. according to user communication data, device operation data, application operation data, user operation device log, user call record log, etc.
  • the data related to the user state may include, for example, time information, location information, schedule information, step information, etc., which can be used to analyze the data of the user's state; the data related to the user's device usage habits may include, for example The length of time the user uses the device each time; the data related to the user's real-time operation of the device may include, for example, the frequency of the user's use of the device in the current period, and so on.
  • the data collection and processing module 801 can call multiple application programming interfaces (application programming interface, API) to collect the above-mentioned information from multiple application programs, multiple sensors, databases, etc. in the first mobile terminal related data.
  • API application programming interface
  • the data collection and processing module 801 can also perform data processing according to the collected relevant data, and determine multiple influencing factors that affect the calling time again.
  • data processing according to the collected relevant data, and determine multiple influencing factors that affect the calling time again.
  • the call-back timeliness assessment module 802 can be used to determine multiple impact factors obtained according to the data collection and processing module 801, such as user event impact factors, device usage impact factors, real-time operating frequency impact factors, etc. , to determine the callback timeliness parameter.
  • the call time prediction system 800 may further include a parameter conversion module (not shown in FIG. 9 ).
  • the parameter conversion module 803 can be used as an optional module. For example, when the algorithm used determines that the callback timeliness evaluation parameter obtained is negatively correlated with the callback duration, in order to provide a more intuitive reminder to the caller, the callback needs to be timely The performance evaluation parameter is converted into a positive correlation with the waiting time for another call, and this operation can be performed by the parameter conversion module 803 at this time.
  • the call callback duration prediction module 804 may be configured to determine the callback duration according to the data processed by the above modules.
  • the call callback duration prediction module 804 can be used to determine and analyze the time interval for the user to execute the callback, for example, according to the user's historical callback behavior recorded by the first mobile terminal, it can obtain the time interval for the user to execute the callback in different time periods.
  • the dial-up time interval determine the average value of the callback time interval in this period; later, when there is another missed call in this period, the average value of the callback time interval and the callback timeliness parameter can be used to predict the callback time .
  • the structure shown in the embodiment of the present application does not constitute a specific limitation on the call time prediction system 800 .
  • the call time prediction system 800 may include more or fewer modules than shown in the figure, or combine some modules, or split some modules.
  • the illustrated modules may be implemented in hardware, software, or a combination of hardware and software.
  • FIG. 10 it is a schematic flow chart of calling time prediction performed by various modules of the calling time prediction system provided in the embodiment of the present application.
  • the data collection and processing module determines the user event impact factor, equipment usage impact factor, and real-time operation frequency impact factor, and sends the user event impact factor, equipment usage impact factor, and real-time operation frequency impact factor to the callback timeliness Evaluation module.
  • the user event impact factor (denoted as IF1), the equipment utilization factor (denoted as IF2) and the real-time operation factor can be respectively determined according to the target information according to the predicted algorithm model.
  • Frequency Impact Factor (denoted as IF3).
  • the target information may specifically include a combination of multiple pieces of information, and different items of information included in the target information may be used to determine the above-mentioned user event influencing factor IF1, device usage influencing factor IF2, and real-time operating frequency influencing factor IF3.
  • the callback timeliness evaluation module determines a callback timeliness parameter according to the acquired user event impact factor, equipment usage factor and real-time operation frequency impact factor.
  • the callback timeliness assessment module is used to determine the callback timeliness parameter (denoted as M1) based on the acquired user event impact factor IF1, equipment usage factor IF2 and real-time operation frequency impact factor IF3 using a preset algorithm model ), the callback timeliness parameter M1 can comprehensively reflect the influence of user event influence factor IF1, device utilization factor IF2 and real-time operation frequency influence factor IF3 on the time to call again.
  • the callback timeliness module determines that the obtained dial-back timeliness parameter M1 may be positively correlated with the waiting time for calling again, or may be negatively correlated with the waiting time for calling again. Wherein, when M1 is negatively correlated with the waiting time of calling again, the following step S1003 may be executed by the parameter conversion module in the call time prediction system to perform parameter conversion on the callback timeliness parameter M1.
  • the parameter conversion module performs parameter conversion on the callback timeliness parameter M1 to obtain the conversion parameter.
  • the parameter conversion module can use a preset algorithm model to perform parameter conversion on the callback timeliness parameter M1, and obtain the conversion parameter (denoted as M2).
  • the algorithm model can make the conversion parameter M2 negatively correlated with the call-back timeliness parameter M1, that is, the conversion parameter M2 determined through the algorithm model is positively correlated with the waiting time for calling again.
  • the call callback time prediction module determines the waiting time for calling again according to the user's historical callback time and conversion parameters.
  • the user's historical callback duration is used to reflect the user's callback habits for missed calls based on the user's historical callback data for missed calls.
  • the historical callback duration may specifically be an average duration for the user to perform callback in different divided time periods.
  • the call time reminder method by analyzing and quantifying the user status, user equipment usage habits, etc., to determine its impact on the re-call time, the prediction result of the re-call time is more accurate, and the success of the call between the two parties is improved. possibility.
  • FIG. 11 it is a schematic flowchart of a method for calling time reminder provided by the embodiment of the present application. This process can be carried out by each module in the call time prediction system shown in Figure 8, including the following steps:
  • the first mobile terminal collects target information through the data collection and processing module, wherein the target information is used to indicate the user status, the user's usage habits of the first mobile terminal, and the user's real-time operating frequency of the first mobile terminal.
  • the call time reminder method provided by the embodiment of the present application can predict the call back duration based on multiple index parameters such as user status, usage habits of the first mobile terminal, and real-time operation frequency of the first mobile terminal by the user.
  • the user in the embodiment of the present application may correspond to the called party.
  • the user state may include multiple types, such as meeting state, dining state, driving state, walking state, resting state and so on.
  • the target information may include information or a combination of information used to analyze and obtain the user's status, such as time information, location information, schedule information, connection information with other devices, step count information, and the like.
  • the user's usage habits of the first mobile terminal may refer to the duration of the user's use of the first mobile terminal each time, the frequency of the user's use of the first mobile terminal at different times of the day, and the like.
  • the target information may also include information or a combination of information used to analyze and obtain the user's usage habits of the first mobile terminal, such as whether the user uses the first mobile terminal in different periods of the day, whether the user uses the first mobile terminal in different periods of the day The duration of the terminal and so on.
  • the first mobile terminal determines a user event impact factor according to the target information.
  • the first mobile terminal may determine the user status according to the target information through the data collection and processing module.
  • Different information or different combinations of information may correspond to different user states. Exemplarily, as shown in Table 1, it is an example of the corresponding relationship between some user states and different information (or different information combinations) provided in the embodiment of the present application.
  • the analysis process can be, for example: the user can record the schedule on the first mobile terminal (such as the calendar App of the first mobile terminal) to be within the time period of 09:00-11:00 meeting, the first mobile terminal may determine that the user is in a meeting state within the time period of 09:00-11:00 according to the schedule corresponding to the specific time period.
  • the first mobile terminal such as the calendar App of the first mobile terminal
  • the analysis process can be, for example: the first mobile terminal can belong to the preset meal time period according to the current time (such as 06:00-08:00, 11:00-13:00 or 17:00-19:00), and according to the user's current location at a dining place, it is determined that the user is currently in a dining state.
  • the current time such as 06:00-08:00, 11:00-13:00 or 17:00-19:00
  • the analysis process can be, for example: the first mobile terminal can be positioned on the road according to the current location of the user, and the first mobile terminal is connected to the vehicle-mounted device, and it is determined that the user is driving at this time. status or ride status.
  • the analysis process may be, for example: the first mobile terminal may determine that the user is in a walking state according to the real-time increase in the number of steps in the pedometer.
  • the first mobile terminal can obtain more other types of information through the data collection and processing module, and determine the user status based on these information. Not limited.
  • the corresponding waiting time for calling again is also different.
  • the waiting time for the corresponding call again may be longer.
  • the waiting time for the corresponding call again is relatively short. .
  • this application sets the user event impact factor to represent the impact of different user states on waiting for calling again.
  • Different user states may correspond to different user event impact factor values.
  • the value of the user event impact factor is positively correlated with the impact of the user state on the timeliness of callback. That is to say, if the value of the user event impact factor corresponding to a certain user state is larger, then Indicates that the more timely the user calls back in this user state, the shorter the corresponding waiting time for calling again.
  • the first mobile terminal may pre-acquire the correspondence between the user state and the user event impact factor (denoted as IF1), wherein the size of the user event impact factor corresponding to different user states may be based on experience Sure.
  • the method of determining the user event influencing factors corresponding to different user states may be: first, setting the coefficient range (thl1, thr1) corresponding to the user event influencing factors; , select different values from the coefficient range (thl1, thr1) as coefficients corresponding to different user states; this coefficient can be used to determine the user event impact factor, or this coefficient can also be used to directly represent the magnitude of the user event impact factor.
  • the coefficient range corresponding to the user event impact factor is (0, 2)
  • the greater the user event impact factor IF1 the higher the timeliness of the callback, and the shorter the call callback time may be.
  • the first mobile terminal can obtain the current user state of the user through the analysis of the data collection and processing module; after that, the first mobile terminal can obtain the current state of the user based on the corresponding relationship between the user state and the user event impact factor.
  • the user event impact factor corresponding to the user status at .
  • the first mobile terminal determines a device usage factor influencing factor according to the target information.
  • the present application sets the device usage factor to represent the influence of the time the user uses the device each time on the waiting time of the call again.
  • the target information may include information such as the duration of the user not using the device within each time period, and the first mobile terminal may determine the device usage factor corresponding to each time period according to the foregoing information in the target information.
  • the process for the first mobile terminal to obtain the device usage factor according to the target information may include: taking days (24h) as the time unit, dividing 24h in a day into multiple sub-periods on average, and the duration of each sub-period (ie The above-mentioned first duration) may be T1; then, count the duration that the user does not use the first mobile terminal in each sub-period; determine the device utilization factor according to T1 and the duration that the user does not use the first mobile terminal in each sub-period.
  • the above statistical method it is possible to accumulate and count the duration of the user not using the device in each sub-period of multiple days (such as every day within a year) within the preset historical period (such as one year); then, use the accumulated statistical results to determine the preset historical period
  • the average duration of not using the device corresponding to each sub-period in the period for example, assuming that the average duration of the user not using the device corresponding to each sub-period in the preset historical period is shown in Table 3:
  • the average duration of the user not using the device corresponding to each sub-period and the duration T1 of each sub-period are used to determine the device usage rate impact factor corresponding to each sub-period.
  • the device utilization factor corresponding to each sub-period can be determined and obtained by the following formula (1-1):
  • IF2 represents the impact factor of device usage
  • T1 represents the duration corresponding to each sub-period
  • t represents the average duration of the corresponding user not using the device within the sub-period.
  • the calculation methods listed above will make the equipment utilization rate impact factor positively correlated with the callback timeliness. That is to say, if the value of the equipment utilization rate impact factor is larger, it means that the user's callback timeliness is higher, and the corresponding call-back timeliness is higher. The waiting time for calls will be shorter.
  • the method for the first mobile terminal to obtain the duration of not using the device in each sub-period of each time unit (such as every day) within the preset historical period may include: when the first mobile terminal is a new device, the user may The device usage data on the previously used device is sent to the first mobile terminal through data transfer (such as data cloning), and the first mobile terminal can use the acquired device usage data on the original device to determine the device usage factor.
  • the first mobile terminal can record the duration data of the user using or not using the first mobile terminal, and the first mobile terminal can subsequently use the relevant data recorded by the first mobile terminal itself to determine the device
  • the utilization rate impact factor, or the device utilization rate impact factor may be comprehensively determined by using the device duration data on the original device and the duration data recorded by the first mobile terminal itself.
  • the preset historical period here may be a historical period with a fixed duration, such as within one year before the present; or, it may also be a historical period with an indeterminate duration, such as the first mobile terminal recording device usage and/or non-use The period of dynamic accumulation from the start time of the duration data of the device to the current time. This application is not limited to this.
  • the first mobile terminal may also determine the user's equipment usage influencing factor in other ways.
  • the first mobile terminal may also determine the influence factor of the device usage rate according to the duration of continuous use of the device by the user in each period and the unit duration corresponding to the period.
  • the first mobile terminal determines a real-time operating frequency impact factor according to the target information.
  • the real-time operation frequency influence factor may be used to represent the frequency of the user operating the device. It can be understood that if the user checks the first mobile terminal more frequently, the probability of being answered when calling again will be higher, and the waiting time for calling again may be shorter. In order to predict the time of calling again more accurately, in the embodiment of the present application, a real-time operation frequency influence factor is set to represent the influence of the frequency of use of the user equipment on the waiting time of calling again.
  • the process of determining the real-time operating frequency impact factor may include: dividing the time period adjacent to the time when the missed call event occurs (such as 1 minute before the missed call occurs) with T2 (corresponding to the second duration) as the time unit (corresponding to In the second time period), obtain a plurality of moments with a time interval of T2; respectively count whether the user is using the first mobile terminal at each moment; use a preset algorithm to determine the real-time operating frequency influence factor IF3 according to the statistical results.
  • the preset algorithm can be set flexibly.
  • IF3 can be obtained by determining the percentage of the number of times m of the user using the device at n moments, that is, IF3 can be determined by the following formula (1-2):
  • IF3 is the real-time operating frequency impact factor
  • m is the number of times the user uses the device at n time points, and m is less than or equal to n
  • n is the number of statistical time points, and n is an integer greater than 1.
  • IF3 can also be determined by the following formula (1-3):
  • IF3 is the real-time operation frequency impact factor
  • m is the number of times the user uses the device in n moments, m is less than or equal to n;
  • n is the number of statistical moments, n is an integer greater than 1;
  • formula (1-1) can be used to determine the real-time operating frequency influence factor as:
  • the greater the real-time operation frequency impact factor the higher the frequency of the user's use of the device, the greater the possibility of answering the call, and the correspondingly shorter waiting time for another call.
  • the embodiment of the present application can set the coefficient range (thr2, thl2) of the real-time operation frequency factor, so that the obtained real-time operation frequency factor is determined to fall within the coefficient range, thereby making it easier Objectively evaluate the impact of real-time operation results on the waiting time for another call. For example, set the coefficient range corresponding to the operating frequency impact factor of the embodiment to (0, 2), at this time, the constant c in the formula (1-2) can be set to 2, so that the obtained IF3 result is within the coefficient range
  • the settlement result of IF3 may be within the set coefficient range through normalization processing in other ways, which is not limited in this embodiment of the present application.
  • the first mobile terminal determines the callback timeliness parameter through the callback timeliness module.
  • the first mobile terminal may determine the callback timeliness parameter according to the obtained IF1, IF2 and IF3 through the callback timeliness module.
  • the callback timeliness evaluation module can determine the callback timeliness parameter M1 through the following formula (1-4):
  • the call-back timeliness parameter is used to comprehensively reflect the impact of the obtained IF1, IF2 and IF3 on the re-call time.
  • the callback timeliness can be positively correlated with IF1, IF2, and IF3.
  • the callback timeliness parameters can also be calculated through other algorithm models, such as IF1, IF2, and IF3. summation or weighted summation etc.
  • the first mobile terminal acquires a conversion parameter according to the timeliness parameter of the callback, and the conversion parameter is positively correlated with the duration of the callback.
  • the callback timeliness parameter obtained through the above-mentioned determination methods from steps S1102 to S1105 is a positive expectation value.
  • the larger the positive expectation value the faster the caller can call back, and the waiting time for calling again is negative.
  • the larger the callback timeliness parameter means the shorter the waiting time for calling again. Therefore, in order to obtain a more intuitive prediction result of the waiting time for calling again, it is necessary to convert the timeliness parameters of the callback through this step, and obtain the converted data that is positively correlated with the waiting time for calling again, so as to remind the caller more intuitively Time to call again.
  • the conversion parameter M2 can be determined by the following formulas (1-5) and formulas (1-6):
  • thr3 and thl3 are coefficient ranges (thr3, thl3) to which the preset callback timeliness parameters belong, and thr3 and thl3 are positive integers greater than 0.
  • the first mobile terminal obtains the waiting prediction result of calling again according to the user's historical callback duration and conversion parameters.
  • the callback habit of the callee when receiving a missed call may also affect the callback duration. For example, some callees are used to calling back in time after learning that there is a missed call, and the callback time may be shorter at this time; while some callees are used to choosing to call back after a longer period of time (such as after work) after learning that there is a missed call. ) callback, the corresponding callback time may be longer at this time. Therefore, in order to more accurately predict the duration of the callback, this step can be used to determine the duration of the callback according to the callee's habit of calling back.
  • the first mobile terminal may just record the callback data of the user.
  • the callback data can be the callback time when the user receives missed calls at different times of the day, for example, divide each day into multiple time periods according to a certain time interval T3, if the user receives a missed call in a certain time period , record the user's callback duration for the missed call, and use it as the user's callback duration corresponding to this period, so as to reflect the user's callback habit in this period.
  • the user receives a missed call at 09:21 (corresponding to the period 09:20-09:40), and after 10 minutes (that is, 09:31) calls If the call is called back, the user's callback time corresponding to the time period 09:20-09:40 is 10 minutes.
  • the first mobile terminal can record in real time the historical callback data corresponding to each time the user calls back, and when predicting the duration of the callback, use the recorded historical callback data to determine the average user callback data corresponding to each time period, and then use the The conversion parameter in step S1106 is corrected with the average data of the user's callback to obtain a more accurate callback time.
  • the first mobile terminal may also use user callback data within a preset historical time period to modify the conversion parameter. For example, the first mobile terminal may determine the average call-back duration of the user in each period of the day by using the call-back data of the user in the previous year, and use the average call-back duration of the user to correct the conversion parameters.
  • the first mobile terminal uses the user's average call-back duration and the conversion parameter to determine the prediction result Rt of the waiting duration of the current call again, for example, can be determined by formula (1-7):
  • M2 is the conversion parameter
  • t is the average value of the callback time of the corresponding user in the current period.
  • the first mobile terminal sends a call time reminder message to the second mobile terminal.
  • the call time reminder message includes a predicted waiting time for calling again, and is used to prompt the caller to call again at an appropriate time.
  • the first mobile terminal may send the call time reminder message to the second mobile terminal, such as through a text message, an instant messaging App, and the like.
  • the call time reminder message can be presented to the caller in various ways, such as in text form, voice form and so on. This embodiment of the present application does not limit it.
  • step S1106 in the embodiment of the present application is an optional step.
  • quantified parameters such as user status, user device usage habits, and real-time operating frequency of the device are all positive to the waiting time for calling back again Correlation (the smaller the quantized parameter means the shorter the callback duration)
  • the conversion of the callback timeliness parameter in step S1106 may not be performed.
  • the execution order of steps S1102 to S1104 is not limited to the order shown above.
  • the call time reminder method provided by the embodiment of the present application mainly quantifies the user status, the user's device usage habits, and the user's real-time dynamic usage as parameters, and then obtains the prediction result of the call-back duration based on these parameters .
  • the determination methods listed above are only used to better understand the call time reminder method provided by the embodiment of the present application. In other embodiments, other determination methods can also be set to quantify the user status, etc., and then determine the call time again. The time is not limited by this application.
  • the call time reminder method by analyzing and quantifying the user status, user equipment usage habits, etc., to determine its impact on the re-call time, the prediction result of the re-call time is more accurate, and the success of the call between the two parties is improved. possibility.
  • the embodiment of the present application also provides a terminal device, including: a display; one or more processors; one or more memories; one or more computer programs are stored in the one or more memories , the one or more computer programs include instructions, which, when executed by the one or more processors, cause the terminal device to perform one or more steps in any one of the above methods.
  • the embodiment of the present application also provides a computer-readable storage medium, which stores instructions in the computer-readable storage medium, and when it is run on a computer or processor, the computer or processor executes the above-mentioned One or more steps in any method.
  • the embodiment of the present application also provides a computer program product including instructions.
  • the computer program product is run on the computer or the processor, the computer or the processor is made to perform one or more steps in any one of the above methods.
  • all or part of them may be implemented by software, hardware, firmware or any combination thereof.
  • software When implemented using software, it may be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer instructions.
  • the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable devices.
  • the computer instructions may be stored in or transmitted via a computer-readable storage medium.
  • the computer instructions may be transmitted from one web site, computer, server, or data center to another web site, computer, server or data center for transmission.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer, or a data storage device such as a server or a data center integrated with one or more available media.
  • the available medium may be a magnetic medium (for example, a floppy disk, a hard disk, or a magnetic tape), an optical medium (for example, DVD), or a semiconductor medium (for example, a solid state disk (solid state disk, SSD)), etc.
  • the processes can be completed by computer programs to instruct related hardware.
  • the programs can be stored in computer-readable storage media.
  • When the programs are executed may include the processes of the foregoing method embodiments.
  • the aforementioned storage medium includes: ROM or random access memory RAM, magnetic disk or optical disk, and other various media that can store program codes.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Human Computer Interaction (AREA)
  • Telephone Function (AREA)

Abstract

本申请涉及终端领域，提供了一种呼叫时间提醒的方法及终端。该呼叫时间提醒的方法包括：接收呼叫者通过第二移动终端发起的呼叫；当确定发生未接呼叫事件时，基于呼叫时间预测模型获取再次呼叫的时间信息；向所述第二移动终端发送呼叫时间提醒消息，所述呼叫时间提醒消息用于向所述呼叫者提示所述再次呼叫的时间信息。本申请提供的呼叫时间提醒的方法通过在通话呼叫未被接听时，被叫者的移动终端预测被叫者方便接听的时间信息，并向呼叫者推送该时间信息，从而提高双方成功通话的概率，以及提升用户的通话体验。

Description

呼叫时间提醒的方法及终端
本申请要求于2021年09月26日提交国家知识产权局、申请号为202111131953.8、申请名称为“呼叫时间提醒的方法及终端”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及终端领域，尤其涉及一种呼叫时间提醒的方法及终端。
背景技术
现代通信网络已向用户提供了大量的特征和功能，使得用户朋友、家庭、同事以及其他人更加容易地保持联系。然而，在实际应用中，被叫者有时会在忙碌或其他不方便接听通话的时刻收到来电，此时，被呼叫者无法接听来电。面对这种情形，呼叫者经常无法直观地获知需间隔多长时间再次呼叫更为合适，而不合适的呼叫时机会给呼叫者和被呼叫者带来不佳的体验。
发明内容
本申请提供了一种呼叫时间提醒的方法及终端，通过发生未接呼叫时，预测并向呼叫者提醒再次呼叫的合适时间，能够解决呼叫双方通话效率低的问题。
第一方面，提供了一种呼叫时间提醒的方法，应用于第一移动终端，包括：接收呼叫者通过第二移动终端发起的呼叫；当确定发生未接呼叫事件时，基于呼叫时间预测模型获取再次呼叫的时间信息；向所述第二移动终端发送呼叫时间提醒消息，所述呼叫时间提醒消息用于向所述呼叫者提示所述再次呼叫的时间信息。
可选地，呼叫者通过第二移动终端发起的呼叫可以包括呼叫者通过电话拨号方式发起的呼叫，也可以包括呼叫者通过即时通讯应用程序发起的呼叫等。
需要说明的，再次呼叫的时间信息可以指被叫者接听呼叫概率较高的时间。
根据本实现方式提供的呼叫时间提醒的方法，通过将分析并量化用户状态、用户设备使用习惯等，确定其对再次呼叫时间的影响，使得再次呼叫时间的预测结果更加准确，提升双方通话成功的可能性。
结合第一方面，在第一方面的某些实现方式中，所述再次呼叫的时间信息为再次呼叫的等待时长或者为再次呼叫的时刻。
结合第一方面，在第一方面的某些实现方式中，所述向所述第二移动终端发送呼叫时间提醒消息，具体包括：通过短信方式向所述第二移动终端发送所述呼叫时间提醒消息；或者，通过即时通讯应用程序向所述第二移动终端发送所述呼叫时间提醒消息。
其中，即时通讯可以包括第三方即时通讯应用程序，也可以包括第一移动终端自带的即时通讯应用程序。
结合第一方面，在第一方面的某些实现方式中，所述呼叫时间提醒消息为语音和/ 或文本。
结合第一方面，在第一方面的某些实现方式中，所述呼叫时间预测模型用于根据用户状态、用户对所述第一移动终端的使用习惯和所述用户对所述第一移动终端的实时操作频率。
其中，用户可以指被叫者。用户对第一移动终端的使用习惯可以以用户单次使用该第一移动终端的时长，或者用户在每天的不同时段使用第一移动终端的时长等来表征。用户对第一移动终端的实时操作频率可以以在未接呼叫事件发生时的时段或者邻近时段中，用户使用该第一移动终端的频率。
应理解，上述表征用户对第一移动终端的使用习惯过程中所涉及的时段(记为第一时段)，与表征用户对第一移动终端的实时操作频率过程中所涉及的时段(记为第二时段)，均可以根据需要灵活划分获得，第一时段和第二时段不相同。
结合第一方面，在第一方面的某些实现方式中，所述当确定发生未接呼叫事件时，基于呼叫时间预测模型获取再次呼叫的时间信息，具体包括：收集目标信息，所述目标信息用于指示所述用户状态、所述用户对所述第一移动终端的使用习惯和所述用户对所述第一移动终端的实时操作频率；根据所述目标信息确定用户事件影响因子、设备使用率影响因子和实时操作频率影响因子，其中，所述用户事件影响因子用于指示所述用户习惯对再次呼叫时间的影响，所述设备使用率影响因子用于指示所述用户对所述第一移动终端的使用习惯对再次呼叫时间的影响，所述实时操作频率影响因子用于指示所述用户对所述第一移动终端的实时操作频率对再次呼叫时间的影响；根据所述用户事件影响因子、所述设备使用率影响因子和所述实时操作频率影响因子确定所述再次呼叫的时间信息。
结合第一方面，在第一方面的某些实现方式中，所述根据所述用户事件影响因子、所述设备使用率影响因子和所述实时操作频率影响因子确定所述再次呼叫的时间信息，具体包括：根据所述用户事件影响因子、所述设备使用率影响因子和所述实时操作频率影响因子确定回拨及时性参数，所述回拨及时性参数用于指示再次呼叫的及时性；根据预获取的所述用户的历史回拨时长和所述回拨及时性参数获取所述再次呼叫的时间信息。
结合第一方面，在第一方面的某些实现方式中，当再次呼叫的时间信息为再次呼叫的等待时长，且所述回拨及时性参数与所述再次呼叫的等待时长负相关时，所述方法还包括：对所述回拨及时性进行转换，获得转换参数，所述转换参数与所述再次呼叫的等待时长正相关。
应理解，通过将回拨及时性转换为与再次呼叫等待时长正相关的转换参数，便于后续利用该转换参数获取能够直观反映再次呼叫时间的时间信息。
结合第一方面，在第一方面的某些实现方式中，获取所述用户状态与所述用户事件影响因子的对应关系；根据所述目标信息确定所述用户当前的用户的状态；从所述用户状态与所述用户事件影响因子的对应关系中确定所述用户当前的用户的状态对应的所述用户事件影响因子。
结合第一方面，在第一方面的某些实现方式中，所述方法还包括：将一天中的第一时段划分为多个子时段，每个子时段的时长为第一时长；获取每个所述子时段内所 述第一移动终端未被使用的时长。
可选地，一天中的第一时段可以指一整天，也即第一时段可以是00:00-24:00这一时段。或者，该第一时段也可以是一天中用户有呼叫需求的时段，比如工作时段09:00-18:00等。
结合第一方面，在第一方面的某些实现方式中，所述方法还包括：获取所述未接呼叫事件的发生时间，并确定所述发生时间所在的目标子时段，所述目标子时段为所述多个子时段中的某一个；根据所述第一时长和所述目标子时段内所述第一移动终端未被使用的时长，确定所述设备使用率影响因子。
结合第一方面，在第一方面的某些实现方式中，获取预设历史时段内多天中所述目标子时段内所述第一移动终端未被使用的多个时长；所述根据所述第一时长和所述目标子时段内所述第一移动终端未被使用的时长，确定所述设备使用率影响因子，具体包括：确定所述多天中所述目标子时段内所述第一移动终端未被使用的多个时长的平均值，获取所述目标子时段内所述第一移动终端未被使用的平均时长；根据所述第一时长和所述目标子时段内所述第一移动终端未被使用的平均时长，确定所述设备使用率影响因子。
根据本实现方式提供的方法，通过统计较长时间内用户在目标子时段内的设备使用(或未使用)时长，求取平均值，再利用平均值确定设备使用率影响因子，可以利用较多的数据，更加准确地反映用户的设备使用习惯对再次呼叫的时间的影响，以便后续能够基于该使用率影响因子更加准确地预测再次呼叫的时间。
结合第一方面，在第一方面的某些实现方式中，所述根据所述第一时长和所述目标子时段内所述第一移动终端未被使用的时长，确定所述设备使用率影响因子，具体包括：
Figure PCTCN2022114237-appb-000001
其中，IF2表示所述设备使用率因子，T1表示所述子时段的第一时长，t表示所述目标子时段内所述第一移动终端未被使用的平均时长。
结合第一方面，在第一方面的某些实现方式中，所述方法还包括：以所述未接呼叫事件发生的时间为基准，确定第二时段；在所述第二时段内选择多个时刻，且每两个相邻的所述时刻之间的时间间隔为第二时长；统计在每个所述时刻，所述用户是否使用所述第一移动终端；根据所述用户在每个所述时刻是否使用所述第一移动终端的统计结果，以及所述时刻的数量，确定所述实时操作频率影响因子。
第二方面，提供了一种移动终端，包括：一个或多个处理器；一个或多个存储器；所述一个或多个存储器存储有一个或多个计算机程序，所述一个或多个计算机程序包括指令，当所述指令被所述一个或多个处理器执行时，使得所述终端设备执行如上述第一方面中的任一实现方式所述的方法。
第三方面，提供了一种计算机可读存储介质，所述计算机可读存储介质存储有计算机可执行程序，所述计算机可执行程序在被计算机调用时，使所述计算机执行如上述第一方面中的任一实现方式所述的方法。
第四方面，提供了一种包含指令的计算机程序产品，当所述计算机程序产品在终端设备上运行时，使得所述终端设备执行如上述第一方面中任一实现方式所述的方法。
附图说明
图1A和图1B是一些呼叫提醒的界面示意图。
图2为本申请实施例提供的一种呼叫时间提醒的方法适用的系统架构示意图。
图3为本申请实施例提供的一种第一移动终端100的结构示意图。
图4本申请实施例的第一移动终端100的软件结构框图。
图5A至图5D为本申请实施例提供的呼叫时间预测功能设置过程中可能涉及的一些GUI示意图。
图6A和图6B为本申请实施例提供的一些呼叫者接收到呼叫时间提醒消息时的GUI示意图。
图7为本申请实施例提供的一种呼叫时间提醒的方法的示意性流程图。
图8为本申请实施例提供的一种呼叫时间预测系统800主体框架的示意性结构图。
图9为本申请实施例提供的一种呼叫时间预测系统800各模块功能的示意图。
图10为本申请实施例提供的呼叫时间预测系统800的各个模块执行呼叫时间预测的示意性流程图。
图11为本申请实施例提供的另一种呼叫时间提醒的方法的示意性流程图。
图12是本申请实施例提供的一种不同时段用户不使用设备的时长分布示意图。
具体实施方式
需要说明的是，本申请实施例的实施方式部分使用的术语仅用于对本申请的具体实施例进行解释，而非旨在限定本申请。在本申请实施例的描述中，除非另有说明，“/”表示或的意思，例如，A/B可以表示A或B；本文中的“和/或”仅仅是一种描述关联障碍物的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，在本申请实施例的描述中，除非另有说明，“多个”是指两个或多于两个，“至少一个”、“一个或多个”是指一个、两个或两个以上。
以下，术语“第一”、“第二”仅用于描述目的，而不能理解为指示或暗示相对重要性或者隐含指明所指示的技术特征的数量。由此，限定有“第一”、“第二”特征可以明示或者隐含地包括一个或者更多个该特征。
在本说明书中描述的参考“一个实施例”或“一些实施例”等意味着在本申请的一个或多个实施例中包括结合该实施例描述的特定特征、结构或特点。由此，在本说明书中的不同之处出现的语句“在一个实施例中”、“在一些实施例中”、“在其他一些实施例中”、“在另外一些实施例中”等不是必然都参考相同的实施例，而是意味着“一个或多个但不是所有的实施例”，除非是以其他方式另外特别强调。术语“包括”、“包含”、“具有”及它们的变形都意味着“包括但不限于”，除非是以其他方式另外特别强调。
首先，为了便于理解，下面首先对本申请实施例可能涉及的相关术语和概念进行介绍。
1、通话过程
通话过程是指通话双方用户借助移动终端，完成双向的语音流、视频流的交换过程。通话过程可以为点对点通话，如通话双方用户利用对讲机执行通话过程。通话过 程还可以利用其它设备中转，完成通话。比如，终端设备中安装有用户标识模块(subscriber identification module，SIM)卡，利用SIM卡通过运营商网络执行通话过程。又比如，移动终端中安装有即时通讯应用程序(如微信、skype等)，利用即时通讯应用程序执行通话过程。
2、呼叫
呼叫是指通信中用户之间连接的建立操作。以自动电话交换系统为例，它是呼叫者为了与被叫者取得联系而执行的操作，即通话所需要的操作。
目前当被叫者未接听呼叫时，被叫者可以通过终端以发送提醒短信等方式向呼叫者提示被呼叫者当前不方便接听呼叫。比如，结合图1A和图1B所示，在一种可能的场景下，如果被叫者在开会期间接收到手机来电，此时被叫者可以点击如图1A所示的通话来电页面上的短信图标101，并在图1B所示的页面选择合适的短信回复内容(如“正在开会，稍后联系”)或者自主编辑短信回复内容发送给呼叫者，告知呼叫者此时不方便接电话。
然而，现有的这种提醒方式仅能使呼叫者获知当前不适宜联系对方，而无法获知何时再次呼叫对方才能够成功通话，导致用户体验不佳。
针对上述问题，本申请实施例提供了一种呼叫时间提醒的方法，通过根据被叫者的用户状态、用户的设备使用习惯、用户对设备的实时操作情况等预测再次呼叫的时间，并将其推送给呼叫者，使得呼叫者能够在合适的时间再次发起呼叫，从而提高双方通话成功的概率，提升用户体验。
示例性的，如图2所示，为本申请实施例提供的一种呼叫时间提醒的方法适用的系统架构示意图。该系统架构包括被叫者(或称被叫方)的第一移动终端100和呼叫者(或称呼叫方)的第二移动终端200。
在该系统架构中，第一移动终端100和第二移动终端200之间可以通过有线网络或无线网络建立通信连接。比如，第一移动终端100可以和第二移动终端200通过蜂窝网络建立通信连接，蜂窝网络例如可以是第五代移动通信技术(5 th generation，5G)、第六代移动通信技术(6 th generation，6G)以及未来任意通信系统等。本申请实施例对第一移动终端100和第二移动终端200之间进行通信的网络类型不做具体限定。
在一些实施例中，第一移动终端100和第二移动终端200可以是具有语音和/或视频通话能力的多种类型的电子设备，例如可以是手机、平板电脑(pad)、笔记本电脑、台式电脑、车载设备、可穿戴设备、超级移动个人计算机(ultra-mobile personal computer，UMPC)、上网本、个人数字助理(personal digital assistant，PDA)、工业控制(industrial control)中的无线终端、无人驾驶(self driving)中的无线终端、远程医疗(remote medical)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端、人工智能(artificial intelligence)设备等终端设备，本申请实施例对第一移动后终端100和第二移动终端200的具体类型不作任何限制。
示例性的，如图3所示，为本申请实施例提供的一种第一移动终端100的结构示意图。
图3示出了第一移动终端100的结构示意图。第一移动终端100可以包括处理器110，外部存储器接口120，内部存储器121，通用串行总线(universal serial bus，USB)接口130，充电管理模块140，电源管理模块141，电池142，天线1，天线2，移动通信模块150，无线通信模块160，音频模块170，扬声器170A，受话器170B，麦克风170C，耳机接口170D，传感器模块180，按键190，马达191，指示器192，摄像头193，显示屏194，以及用户标识模块(subscriber identification module，SIM)卡接口195等。其中传感器模块180可以包括压力传感器180A，陀螺仪传感器180B，气压传感器180C，磁传感器180D，加速度传感器180E，距离传感器180F，接近光传感器180G，指纹传感器180H，温度传感器180J，触摸传感器180K，环境光传感器180L，骨传导传感器180M等。
可以理解的是，本申请实施例示意的结构并不构成对第一移动终端100的具体限定。在本申请另一些实施例中，第一移动终端100可以包括比图示更多或更少的部件，或者组合某些部件，或者拆分某些部件，或者不同的部件布置。图示的部件可以以硬件，软件或软件和硬件的组合实现。
处理器110可以包括一个或多个处理单元，例如：处理器110可以包括应用处理器(application processor，AP)，调制解调处理器，图形处理器(graphics processing unit，GPU)，图像信号处理器(image signal processor，ISP)，控制器，存储器，视频编解码器，数字信号处理器(digital signal processor，DSP)，基带处理器，和/或神经网络处理器(neural-network processing unit，NPU)等。其中，不同的处理单元可以是独立的器件，也可以集成在一个或多个处理器中。
其中，控制器可以是第一移动终端100的神经中枢和指挥中心。控制器可以根据指令操作码和时序信号，产生操作控制信号，完成取指令和执行指令的控制。
处理器110中还可以设置存储器，用于存储指令和数据。在一些实施例中，处理器110中的存储器为高速缓冲存储器。该存储器可以保存处理器110刚用过或循环使用的指令或数据。如果处理器110需要再次使用该指令或数据，可从所述存储器中直接调用。避免了重复存取，减少了处理器110的等待时间，因而提高了系统的效率。
在一些实施例中，处理器110可以包括一个或多个接口。接口可以包括集成电路(inter-integrated circuit，I2C)接口，集成电路内置音频(inter-integrated circuit sound，I2S)接口，脉冲编码调制(pulse code modulation，PCM)接口，通用异步收发传输器(universal asynchronous receiver/transmitter，UART)接口，移动产业处理器接口(mobile industry processor interface，MIPI)，通用输入输出(general-purpose input/output，GPIO)接口，用户标识模块(subscriber identity module，SIM)接口，和/或通用串行总线(universal serial bus，USB)接口等。
I2S接口可以用于音频通信。在一些实施例中，处理器110可以包含多组I2S总线。处理器110可以通过I2S总线与音频模块170耦合，实现处理器110与音频模块170之间的通信。在一些实施例中，音频模块170可以通过I2S接口向无线通信模块160传递音频信号，实现接听通话的功能。
PCM接口也可以用于音频通信，将模拟信号抽样，量化和编码。在一些实施例中，音频模块170与无线通信模块160可以通过PCM总线接口耦合。在一些实施例中，音 频模块170也可以通过PCM接口向无线通信模块160传递音频信号，实现接听通话的功能。所述I2S接口和所述PCM接口都可以用于音频通信。
可以理解的是，本申请实施例示意的各模块间的接口连接关系，只是示意性说明，并不构成对第一移动终端100的结构限定。在本申请另一些实施例中，第一移动终端100也可以采用上述实施例中不同的接口连接方式，或多种接口连接方式的组合。
第一移动终端100的无线通信功能可以通过天线1，天线2，移动通信模块150，无线通信模块160，调制解调处理器以及基带处理器等实现。
移动通信模块150可以提供应用在第一移动终端100上的包括2G/3G/4G/5G等无线通信的解决方案。移动通信模块150可以包括至少一个滤波器，开关，功率放大器，低噪声放大器(low noise amplifier，LNA)等。移动通信模块150可以由天线1接收电磁波，并对接收的电磁波进行滤波，放大等处理，传送至调制解调处理器进行解调。移动通信模块150还可以对经调制解调处理器调制后的信号放大，经天线1转为电磁波辐射出去。在一些实施例中，移动通信模块150的至少部分功能模块可以被设置于处理器110中。在一些实施例中，移动通信模块150的至少部分功能模块可以与处理器110的至少部分模块被设置在同一个器件中。
无线通信模块160可以提供应用在第一移动终端100上的包括无线局域网(wireless local area networks，WLAN)(如无线保真(wireless fidelity，Wi-Fi)网络)，蓝牙(bluetooth，BT)，全球导航卫星系统(global navigation satellite system，GNSS)，调频(frequency modulation，FM)，近距离无线通信技术(near field communication，NFC)，红外技术(infrared，IR)等无线通信的解决方案。无线通信模块160可以是集成至少一个通信处理模块的一个或多个器件。无线通信模块160经由天线2接收电磁波，将电磁波信号调频以及滤波处理，将处理后的信号发送到处理器110。无线通信模块160还可以从处理器110接收待发送的信号，对其进行调频，放大，经天线2转为电磁波辐射出去。
示例性的，第一移动终端100的软件系统可以采用分层架构，事件驱动架构，微核架构，微服务架构，或云架构。本发明实施例以分层架构的Android系统为例，示例性说明第一移动终端100的软件结构。图4是本申请实施例的第一移动终端100的软件结构框图。
分层架构将软件分成若干个层，每一层都有清晰的角色和分工。层与层之间通过软件接口通信。在一些实施例中，将Android系统分为四层，从上至下分别为应用程序层，应用程序框架层，安卓运行时(Android runtime)和系统库，以及内核层。
应用程序层可以包括一系列应用程序包。如图4所示，应用程序包可以包括相机，图库，日历，通话，地图，导航，WLAN，蓝牙，音乐，视频，短信息等应用程序。
应用程序框架层为应用程序层的应用程序提供应用编程接口(application programming interface，API)和编程框架。应用程序框架层包括一些预先定义的函数。如图4所示，应用程序框架层可以包括窗口管理器，内容提供器，视图系统，电话管理器，资源管理器，通知管理器等。
窗口管理器用于管理窗口程序。窗口管理器可以获取显示屏大小，判断是否有状态栏，锁定屏幕，截取屏幕等。
内容提供器用来存放和获取数据，并使这些数据可以被应用程序访问。所述数据可以包括视频，图像，音频，拨打和接听的电话，浏览历史和书签，电话簿等。
视图系统包括可视控件，例如显示文字的控件，显示图片的控件等。视图系统可用于构建应用程序。显示界面可以由一个或多个视图组成的。例如，包括短信通知图标的显示界面，可以包括显示文字的视图以及显示图片的视图。
电话管理器用于提供第一移动终端100的通信功能。例如通话状态的管理(包括接通，挂断等)。
资源管理器为应用程序提供各种资源，比如本地化字符串，图标，图片，布局文件，视频文件等等。
通知管理器使应用程序可以在状态栏中显示通知信息，可以用于传达告知类型的消息，可以短暂停留后自动消失，无需用户交互。比如通知管理器被用于告知下载完成，消息提醒等。通知管理器还可以是以图表或者滚动条文本形式出现在系统顶部状态栏的通知，例如后台运行的应用程序的通知，还可以是以对话窗口形式出现在屏幕上的通知。例如在状态栏提示文本信息，发出提示音，终端振动，指示灯闪烁等。
Android Runtime包括核心库和虚拟机。Android runtime负责安卓系统的调度和管理。
核心库包含两部分：一部分是java语言需要调用的功能函数，另一部分是安卓的核心库。
应用程序层和应用程序框架层运行在虚拟机中。虚拟机将应用程序层和应用程序框架层的java文件执行为二进制文件。虚拟机用于执行障碍物生命周期的管理，堆栈管理，线程管理，安全和异常的管理，以及垃圾回收等功能。
系统库可以包括多个功能模块。例如：表面管理器(surface manager)，媒体库(Media Libraries)，三维图形处理库(例如：OpenGL ES)，2D图形引擎(例如：SGL)等。
表面管理器用于对显示子系统进行管理，并且为多个应用程序提供了2D和3D图层的融合。
媒体库支持多种常用的音频，视频格式回放和录制，以及静态图像文件等。媒体库可以支持多种音视频编码格式，例如:MPEG4，H.264，MP3，AAC，AMR，JPG，PNG等。
三维图形处理库用于实现三维图形绘图，图像渲染，合成，和图层处理等。
2D图形引擎是2D绘图的绘图引擎。
内核层是硬件和软件之间的层。内核层至少包含显示驱动，摄像头驱动，音频驱动，传感器驱动。
应理解，本申请实施例提供的呼叫时间提醒的方法可以应用于多种被叫者未接听呼叫(如通话呼叫、视频呼叫等)的应用场景下。比如，被叫者的移动终端获取到未接呼叫(如被叫者漏接、拒接呼叫者发起的呼叫等)时，该移动终端可以根据呼叫时间预测模型预测被叫者方便接听呼叫的时间，并将其推送给呼叫者的移动终端，提醒呼叫者在合适时间再次发起呼叫。通过本申请实施例提供的呼叫时间提醒的方法，能够提高呼叫者再次呼叫成功的概率，提升用户的通话体验。
在一些实施例中，被叫者的第一移动终端具有呼叫时间预测功能，该功能的开启方式可以包括多种，比如：(1)由用户(如被叫者)根据需要自主开启该功能；(2)第一移动终端在检测到有未接呼叫时，自动开启该功能；(3)第一移动终端默认该功能处于开启状态等。
以下结合附图，以第一移动终端是手机为例，对上述方式(1)中的呼叫时间预测功能的开启方式进行示例性介绍。
如图5A至图5D所示，为本申请实施例提供的呼叫时间预测功能设置过程中可能涉及的一些用户图形界面(user graphical interface，GUI)示意图。
如图5A所示，为手机的主屏幕界面示意图。该主屏幕界面可以包括应用图标显示区域10，用于显示多种类型的应用程序(application，App)图标，如时钟图标、日历图标、图库图标、备忘录图标、文件管理图标、电子邮件图标、音乐图标、确定器图标、视频图标、运动健康图标、天气图标、浏览器图标、智慧助手图标、设置图标、录音机图标等。多个应用程序图标下方可以有页面指示符显示区域20，该区域包括的页面指示符用于表明当前显示的页面与其他页面的位置关系。页面指示符的下方可以显示有托盘应用图标显示区域30，用于显示多个托盘应用图标，例如相机应用图标、通讯录应用图标、电话拨号应用图标、信息应用图标等。在另一些实施例中，手机的主屏幕界面可以包括比图示更多或更少的应用程序图标或托盘应用图标，本申请对此不作限定。在该主屏幕界面的上方还可以显示有状态栏40，该状态栏40可以包括：移动通信信号(或称蜂窝信号)的一个或多个信号强度指示符、无线保真(wireless fidelity，Wi-Fi)信号的一个或多个信号强度指示符，手机的电量指示符，时间指示符等。
在一些实施例中，手机可以接收用户(如被叫者)作用于设置图标的输入操作(如点击操作)；响应于上述输入操作，手机可以显示如图5B所示的设置详情界面。
如图5B所示，设置详情界面可以包括多项业务设置条目(或称业务设置栏)，例如无线和网络设置条目、蓝牙设置条目、桌面和壁纸设置条目、显示设置条目、声音设置条目、通话设置条目、电池设置条目、存储设置条目、健康使用手机设置条目、安全和隐私设置条目等。通话设置条目可以用于对通话(如语音通话、视频通话)进行设置，如可以设置呼叫回拨提醒，使得在被叫者未接听通话呼叫时，手机可以向呼叫者推送呼叫时间提醒消息。在实际应用中，设置详情界面还可以包括比图示更多或更少类型的设置条目，本申请对此不做限定。
在一些实施例中，手机可以接收用户作用于通话设置条目的输入操作(如点击操作)；响应于上述操作，手机可以显示如图5C所示的通话设置界面。
示例性的，如图5C所示，通话设置界面可以包括呼叫时间提醒-通用设置栏，该呼叫时间提醒-通用设置栏下方可以显示针对该选项的说明，比如“开启此功能时，当有未接呼叫时，可以向呼叫者推送呼叫时间提醒，通知再次呼叫的合适时间，以提高呼叫成功的可能性。”可选地，该通话设置界面还可以设置有呼叫时间提醒-自定义设置栏。示例性的，呼叫时间提醒-自定义设置选项下方可以显示针对该功能的说明，比如“开启此功能时，可对特定联系人开启呼叫时间提醒，对特定联系人推送再次呼叫的合适时间。”
在一些实施例中，用户可以选择开启呼叫时间提醒-通用设置栏中的开关控件，开启呼叫时间提醒通用模式。其中，该呼叫时间提醒通用模式可以指对接收到到的任意呼叫，在用户未接听时，都可以向对应的呼叫者推送呼叫时间提醒，提示呼叫者再次呼叫的合适时间；或者，该呼叫时间提醒通用模式也可以过滤无效号码，仅向有效号码对应的呼叫者推送呼叫时间提醒消息。示例性的，无效号码例如可以指虚拟广告商或推销商的号码，或者也可以由用户自主标记为无效的号码等；相对的，有效号码可以是符合通话运营商规定格式的号码，或未被标记为无效的号码等。比如以电话通话为例，当接收到的呼叫号码被识别为广告、推销等类别时，该呼叫时间提醒通用模式可以不针对该未接呼叫进行呼叫时间预测，也就是说，此时即使该通话呼叫未被接听，被叫者也不会向呼叫者推送呼叫时间提醒消息。
在另一些实施例中，用户也可以选择开启呼叫时间提醒-自定义设置栏中的开关控件，使用呼叫时间提醒的自定义模式。示例性的，如图5C所示，用户点击开启呼叫时间提醒-自定义设置栏中的开关控件后，手机可以显示不同类型通话下的联系人，比如通讯录联系人、微信联系人、QQ联系人等。用户可以输入作用于某一通话类型联系人对应的下一页指示符的操作(如点击操作)，在下一页对该通话类型下特定联系人进行呼叫时间提醒设置。比如，当用户需要对通讯录中的特定联系人设置呼叫时间提醒时，可以点击该通讯录联系人对应的下一页指示符；响应于上述操作，手机可以显示如图5D所示的通讯录联系人界面，之后，用户可以在该通讯录联系人界面，对不同联系人是否开启呼叫时间提醒功能进行个性化设置。
可选地，通话设置界面还可以包括其他通话类型联系人添加栏，用户可以通过输入作用于该添加栏的操作(如点击操作)，添加其他通话类型中的联系人信息。
在一些实施例中，如图5D所示，通讯录联系人界面可以包括通讯录中的联系人列表，每一联系人对应的栏中设置有回拨提醒开关控件。用户对不同联系人是否开启回拨提醒功能进行个性化设置的方式例如可以是：用户通过控制开关控件，设置不同联系人对应的回拨提醒功能开启或关闭。比如，如图5D所示，被叫者可以将通讯录联系人中的爸爸、妈妈、朋友A的回拨提醒开关设置为开启状态，并将朋友B和朋友C对应的回拨提醒开关控件设置为关闭状态，这就意味着当被叫者未接听来自爸爸、妈妈、朋友A中任一人的手机来电时，被叫者的手机可以自动向对方发送呼叫时间提醒消息；而当被叫者未接通朋友B或朋友C的手机来电时，被叫者的手机不会向对方发送呼叫时间消息。
需要说明的是，图5A至图5D所示的呼叫时间提醒设置的方式仅为示例，在实际应用中，还可以采用其他方式对其进行设置，比如可以在通话应用中进行呼叫时长提醒功能的设置(包括呼叫时间提醒通用设置和呼叫时间提醒自定义设置)等，本申请对此不作限定。
示例性的，如图6A和图6B所示，为本申请实施例提供的一些呼叫者接收到呼叫时间提醒消息时的GUI示意图。
其中，在不同的呼叫类型下，该呼叫时间提醒消息可以以不同的形式呈现给呼叫者，如文本和/或语音形式。比如，如图6A所示，当呼叫类型是电话呼叫时，该呼叫时间提醒消息可以短信形式发送给呼叫者，短信内容可以指示再次呼叫的等待时间， 例如是“您好！您呼叫的电话未被及时接听，20分钟后再次呼叫机主可能会被成功接听，谢谢”再比如，如图6B所示，当呼叫类型为通过即时通讯App呼叫时，该呼叫时间提醒消息可以通过该即时通讯App回复给呼叫者，消息内容例如为“您好，您发起的通话呼叫未被及时接听，20分钟后再次呼叫可能会被成功接听，谢谢”。
可选地，呼叫时间提醒消息也可以指示呼叫者再次呼叫的具体时刻或具体时段。比如，呼叫时间提醒消息的内容还可以是“您好，您呼叫的电话未被及时接听，09:40再次呼叫机主可能会被成功接听，谢谢”。再比如，呼叫时间提醒消息的内容还可以是“您好，您呼叫的电话未被及时接听，09:40-09:45这一时段内再次呼叫机主可能会被成功接听”等。
根据本申请实施例提供的呼叫时间提醒的方法，通过在通话无应答时，被叫者向呼叫者推送再次呼叫的时间信息，能够提高呼叫者再次呼叫时双方成功通话的概率，进而提高通话效率，并提升用户体验。
示例性的，如图7所示，为本申请实施例提供的一种呼叫时间提醒的方法的示意性流程图。该方法可以由被叫者的第一移动终端来执行，具体可以包括以下步骤：
S701，第一移动终端接收呼叫者通过第二移动终端发起的呼叫。
其中，第一移动终端为被叫者的终端设备，第二移动终端为呼叫者的终端设备。
需要说明的是，本申请中呼叫者发起的呼叫的类型可以有多种，例如可以包括：通过手机拨号发起的呼叫；或者，通过即时通讯App发起的呼叫等。该呼叫可以是语音呼叫，也可以是视频呼叫。本申请实施例对呼叫发起方式以及呼叫的具体类型不作限定。
S702，当第一移动终端确定发生未接呼叫事件时，基于呼叫时间预测模型获取再次呼叫的时间信息。
其中，导致未接呼叫事件发生的原因可以有多种，如漏接、拒接、呼叫时长达到预设阈值后由被叫者的终端自动挂断、被叫者的终端被设置为免打扰模式导致呼叫被自动挂断、被叫者的终端被设置为通话转移模式导致呼叫无人接听等等。
在一些实施例中，当有未接呼叫事件时，响应于该未接呼叫事件，第一移动终端会基于呼叫时间预测模型执行呼叫时间预测操作，其中，呼叫时间预测操作用于预测再次呼叫的合适时间，提高用户再次呼叫成功的概率。
在一些实施例中，该呼叫时间预测模型可以用于根据用户状态、用户对第一移动终端的使用习惯和用户对第一移动终端的实时操作频率获取再次呼叫的时间信息。其中，本申请实施例中的用户可以指被叫者。用户对第一移动终端的使用习惯可以以用户单次使用该第一移动终端的时长，或者用户在每天的不同时段使用第一移动终端的时长等来表征；用户对第一移动终端的实时操作频率可以以在未接呼叫事件发生时的时段或者邻近时段中，用户使用该第一移动终端的频率。
应理解，上述表征用户对第一移动终端的使用习惯过程中所涉及的时段，例如可以是将一天中的第一时段(例如00:00-24:00等)划分为多个子时段，每个子时段的时长为第一时长；表征用户对第一移动终端的实时操作频率过程中所涉及的时段(记为第二时段)，可以是未接呼叫事件的发生时刻所在的时段或者与未接呼叫时间发生时刻邻近的时段，该第二时段可以以未接呼叫事件发生的时间为基准确定，如第二时段 可以是未接呼叫事件发生时刻之后的2min内等。上述第一时段和第二时段可以根据需要灵活划分，第一时段和第二时段可以不相同。
示例性的，第一移动终端基于呼叫时间预测模型获取再次呼叫的时间信息的过程可以包括：第一移动终端收集目标信息，该目标信息用于指示用户状态、用户对第一移动终端的使用习惯和用户对第一移动终端的实时操作频率；之后，第一移动终端根据目标信息确定用户事件影响因子、设备使用率影响因子和实时操作频率影响因子，其中，用户事件影响因子用于指示用户习惯对再次呼叫时间的影响，设备使用率影响因子用于指示用户对第一移动终端的使用习惯对再次呼叫时间的影响，实时操作频率影响因子用于指示用户对所述第一移动终端的实时操作频率对再次呼叫时间的影响；之后，第一移动终端可以根据用户事件影响因子、设备使用率影响因子和实时操作频率影响因子确定再次呼叫的时间信息。具体地，第一移动终端可以根据用户事件影响因子、设备使用率影响因子和实时操作频率影响因子确定回拨及时性参数，该回拨及时性参数用于指示再次呼叫的及时性；之后，第一移动终端可以根据预获取的用户的历史回拨时长和回拨及时性参数获取再次呼叫的时间信息。
在一些实施例中，当再次呼叫的时间信息为再次呼叫的等待时长，且回拨及时性参数与再次呼叫的等待时长呈负相关时，根据用户的历史回拨时长和回拨及时性参数获取再次呼叫的时间信息可以具体包括：第一移动终端对回拨及时性进行转换，获得转换参数，该转换参数与再次呼叫的等待时长正相关；之后，第一移动终端可以根据用户的历史回拨时长和转换参数获取再次呼叫的时间信息。
其中，该利用呼叫时间预测模型预测再次呼叫时间所涉及的示例性算法将在下文进行介绍，此处暂不详述。
在一些实施例中，第一移动终端可以根据用户状态确定用户事件影响因子，具体过程可以包括：第一移动终端可以通过多种方式(比如从服务器、第三方设备等)获取用户状态与用户事件影响因子之间的对应关系，其中，该对应关系可以由人工基于经验确定；当有未接呼叫事件发生时，第一移动终端可以根据目标信息确定用户当前所处的用户状态，并且从用户状态与用户事件影响因子之间的对应关系中确定当前的用户状态对应的用户事件影响因子。
需要说明的是，根据用户状态确定对应的用户事件影响因子的方式可以有多种，以上介绍的方式仅为示例，但在实际应用中，并不仅限于此。比如，在另一些实施例中，还可以通过以下方式根据用户状态确定用户事件影响因子：第一移动终端可以预先(比如从服务器、第三方设备等)获取用户状态对应的系数，该系数可以用于表征不同用户状态下用户能够接听呼叫的概率，可选地，这些系数可以均位于同一个预设的系数范围内；当有未接呼叫事件发生时，第一移动终端可以根据目标信息确定用户当前所处的用户状态，并且可以选择用户当前所处的用户状态对应的系数，按照预设算法确定对应的用户事件影响因子。
在一些实施例中，第一移动终端还可以根据使用设备的习惯确定设备使用率影响因子，具体过程可以包括：首先，将一天中的第一时段划分为多个子时段，每个子时段的时长为第一时长；之后，获取每个子时段内第一移动终端未被使用的时长；当有未接呼叫事件发生时，获取该未接呼叫事件的发生时间，并确定该发生时间所在的目 标子时段，其中，目标子时段为上述多个子时段中的某一个；之后，根据第一时长和目标子时段内第一移动终端未被使用的时长，确定设备使用率影响因子。其中，目标子时段内的第一移动终端未被使用的时长可以基于预设历史时段内第一移动终端未被使用的时长来确定。比如：第一移动终端可以获取预设历史时段内(如一年内)多天中目标子时段内第一移动终端未被使用的多个时长；然后，确定该多天中目标子时段内第一移动终端未被使用的多个时长的平均值，获取目标子时段内第一移动终端未被使用的平均时长；之后，再利用根据第一时长和目标子时段内第一移动终端未被使用的平均时长，确定设备使用率影响因子。
应理解，通过统计较长时间内用户在目标子时段内的设备使用(或未使用)时长，求取平均值，再利用平均值确定设备使用率影响因子，可以实现利用较多的数据，更加准确地反映用户的设备使用习惯对再次呼叫的时间的影响，以便后续能够基于该使用率影响因子更加准确地预测再次呼叫的时间。
在一些实施例中，第一移动终端可以根据用户在未接呼叫事件发生时的时段(或者邻近时段)的设备操作频率，确定实时操作频率影响因子。示例性的，该具体过程可以包括：第一移动终端以未接呼叫事件发生的时间为基准，确定第二时段，该第二时段为未接呼叫事件发生的时间所在的时段，或者与未接呼叫事件发生的时间邻近的时段；然后，基于预设规则，在所该第二时段内选择多个时刻，并且使每两个相邻的时刻之间的时间间隔为第二时长；统计在每个时刻用户是否使用第一移动终端；然后，根据用户在每个时刻是否使用第一移动终端的统计结果，以及时刻的数量，确定实时操作频率影响因子。
在一些实施例中，触发第一移动终端执行该呼叫时间预测操作的具体过程可以包括：当呼叫未被接听时，第一移动终端可以生成对应的未接呼叫信息，比如未接来电信息、未接视频通话信息等；当第一移动终端检测到有新增的未接呼叫信息时，可以确定发生未接呼叫事件；响应于该未接呼叫事件的发生，第一移动终端根据呼叫时间预测模型获取预测的再次呼叫的时间信息。
可选地，第一移动终端还可以通过其他方式确定发生未接呼叫事件，比如：当第一移动终端检测到系统自动挂断呼叫时，可以确定发生未接呼叫事件；或者，当第一移动终端检测到被叫者输入挂断呼叫的操作时，可以确定发生未接呼叫事件；又或者，当第一移动终端检测到呼叫停止，且在停止之前该通话呼叫一直未被接听时，可以确定该发生未接呼叫事件等。
需要说明的是，上述介绍的第一移动终端确定发生未接呼叫事件的方式仅为示例，在实际应用中，第一移动终端还可以通过其他方式确定未接呼叫事件的发生，本申请实施例对此不作限定。
其中，第一移动终端具体基于呼叫时间预测模型预测再次呼叫的时间信息的过程将在下文进行更为详细地介绍，此处暂不详述。
S703，第一移动终端向第二移动终端发送呼叫时间提醒消息，该呼叫时间提醒消息用于向呼叫者提示再次呼叫的时间信息。
其中，再次呼叫的时间信息例如可以包括再次呼叫的等待时长或者再次呼叫的具体时刻等。为描述更加清晰，以下将以再次呼叫的时间信息是再次呼叫的等待时长为 例进行介绍。
在一些实施例中，当发生未接呼叫事件后，第一移动终端可以生成与该未接呼叫事件关联的未接呼叫信息，该未接呼叫信息例如可以包括呼叫类型、呼叫者的通信信息、呼叫者的标识(identification，ID)(如电话号码、即时通讯号码(如微信号、QQ号)等)、接收到呼叫的时间等。第一移动终端可以根据该未接呼叫信息获取呼叫者的通信信息，并根据该通信信息向第二移动终端发送呼叫时间提醒消息。
第一移动终端向第二移动终端发送呼叫时间提醒消息的方式可以有多种。示例性的，第一移动终端可以采用与呼叫类型一致的方式向第二移动终端推送该呼叫时间提醒消息。比如，若第二移动终端通过手机拨号的方式向第一移动终端发起通话呼叫，则第一移动终端可以根据获取到的第二移动终端的未接呼叫信息向第二移动终端推送该呼叫时间提醒消息。再比如，若第二移动终端通过即时通讯App(如微信)向第一移动终端发起通话呼叫，则第一移动终端可以根据该呼叫对应的呼叫未接信息通过该即时通讯App向对应的联系人发送呼叫时间提醒消息。
呼叫时间提醒消息可以具体呈现为多种形式。比如，该呼叫时间提醒消息可以呈现为文本形式(如短信文本、微信文本等)，可如图6A或图6B所示。又比如，该呼叫时间提醒消息也可以呈现为语音形式(比如彩信语音、微信语音等)等。
根据本申请实施例提供的呼叫时间提醒的方法，通过当通话呼叫未被接听时，被叫者的终端设备可以预测被叫者方便接听的时间信息，并向该呼叫者推送该时间信息，从而提醒呼叫者在合适的时间再次发起对被叫者的呼叫，提高双方成功通话的可能性，进而提升用户的通话体验。
本申请实施例中，第一移动终端的呼叫时间预测功能可以通过呼叫时间预测模型来实现。考虑到在实际应用中，用户所处的状态、用户使用设备的习惯、接到呼叫的邻近时段用户实用设备的频率均会对再次呼叫的时间造成影响，因而，本申请实施例中的呼叫时间预测模型可以用于根据用户状态、用户对第一移动终端的使用习惯和用户对第一移动终端的实时操作频率获取再次呼叫的时间信息，从而可以更加准确地提醒呼叫方再次呼叫的时间，提升呼叫方和被叫方成功通话的概率。
为更好地理解本申请实施例中的预测再次呼叫的时间信息的过程，以下结合附图对呼叫时间预测模型包括的各个模块以及不同模块对应的功能进行介绍。
示例性的，如图8所示，为本申请实施例提供的一种呼叫时间预测系统800主体框架的示意性结构图。该呼叫时间预测系统800可以包括数据收集及处理模块801、回拨及时性评估模块802、参数转换模块803以及呼叫回拨时长预测模块804。呼叫时间预测系统800也可以被描述为呼叫时间预测模型，其包括的各个模块可以位于如图4所示的应用层。
结合图9所示，以下对该呼叫时间预测系统800中各个模块的功能进行介绍。
在一些实施例中，数据收集及处理模块801主要负责收集与用户状态、用户的设备使用习惯、用户对设备的实时操作情况等相关的数据，并对这些数据进行处理。其中，该数据收集与处理模块801可以根据用户通讯数据、设备操作数据、应用操作数据、用户操作设备日志、用户通话记录日志等收集与用户状态、用户的设备实用习惯等相关的数据。示例性的，与用户状态相关的数据例如可以包括时间信息、位置信息、 日程安排信息、步数信息等可以用于分析用户所处状态的数据；与用户的设备使用习惯相关的数据例如可以包括用户每次使用设备的时长；与用户对设备的实时操作情况相关的数据例如可以包括用户当前时段使用设备的频率等等。在一种可能的实现方式中，数据收集及处理模块801可以调用多个应用程序接口(application programming interface，API)从第一移动终端中的多个应用程序、多个传感器、数据库等位置收集上述相关数据。
此外，数据收集及处理模块801还可以根据收集的相关数据进行数据处理，确定影响再次呼叫时间的多个影响因子。具体处理过程请参见下文实施例中的介绍，此处暂不详述。
在一些实施例中，回拨及时性评估模块802可以用于对根据数据收集和处理模块801确定获得的多个影响因子，如用户事件影响因子、设备使用率影响因子、实时操作频率影响因子等，确定回拨及时性参数。
在一些实施例中，该呼叫时间预测系统800还可以包括参数转换模块(图9未示出)。参数转换模块803可以作为可选模块，例如当使用的算法确定得到的回拨及时性评估参数与回拨时长为负相关时，为了能向呼叫者进行更加直观的提醒，需要将该回拨及时性评估参数转换为与再次呼叫的等待时长呈正相关，此时可通过该参数转换模块803执行该操作。
在一些实施例中，呼叫回拨时长预测模块804可以用于根据上述模块处理后的数据确定获取回拨时长。示例性的，该呼叫回拨时长预测模块804可以用于对用户执行回拨的时间间隔进行确定分析，比如可以根据第一移动终端记录的用户历史回拨行为，获取用户在不同时间段执行回拨的时间间隔，确定该时段的回拨时间间隔的平均值；之后，当在该时段再次有未接呼叫时，可利用该回拨时间间隔的平均值以及回拨及时性参数预测回拨时间。
可以理解的是，本申请实施例示意的结构并不构成对呼叫时间预测系统800的具体限定。在本申请另一些实施例中，呼叫时间预测系统800可以包括比图示更多或更少的模块，或者组合某些模块，或者拆分某些模块。图示的模块可以以硬件、软件或者硬件和软件的组合实现。
示例性的，如图10所示，为本申请实施例提供的呼叫时间预测系统的各个模块执行呼叫时间预测的示意性流程图。
S1001，数据收集及处理模块确定用户事件影响因子、设备使用率影响因子和实时操作频率影响因子，并将该用户事件影响因子、设备使用率影响因子和实时操作频率影响因子发送至回拨及时性评估模块。
在一些实施例中，数据收集及处理模块收集目标信息后，可以按照预测的算法模型根据目标信息分别确定用户事件影响因子(记为IF1)、设备使用率影响因子(记为IF2)和实时操作频率影响因子(记为IF3)。其中，目标信息可以具体包括多项信息的组合，确定上述用户事件影响因子IF1、设备使用率影响因子IF2和实时操作频率影响因子IF3所使用的可以是目标信息包括的不同项信息。
S1002，回拨及时性评估模块根据获取的用户事件影响因子、设备使用率影响因子和实时操作频率影响因子确定回拨及时性参数。
应理解，回拨及时性评估模块用于利用预设的算法模型，基于获取的用户事件影响因子IF1、设备使用率影响因子IF2和实时操作频率影响因子IF3确定回拨及时性参数(记为M1)，该回拨及时性参数M1可以综合反映用户事件影响因子IF1、设备使用率影响因子IF2和实时操作频率影响因子IF3对再次呼叫的时间的影响。
在一些实施例中，回拨及时性模块采用的算法模型可以有多种，比如对IF1、IF2和IF3求和或加权求和等。该回拨及时性模块确定获得的回拨及时性参数M1可以与再次呼叫的等待时长呈正相关，或者也可以与再次呼叫的等待时长呈负相关。其中，当M1与再次呼叫的等待时长呈负相关时，还可以通过该呼叫时间预测系统中的参数转换模块执行下述步骤S1003，对该回拨及时性参数M1进行参数转换。
S1003，参数转换模块对回拨及时性参数M1进行参数转换，获取转换参数。
其中，参数转换模块可以利用预设的算法模型，对回拨及时性参数M1进行参数转换，获取转换参数(记为M2)。示例性的，该算法模型可以使转换参数M2与回拨及时性参数M1呈负相关，也即通过该算法模型确定获得的转换参数M2与再次呼叫的等待时长呈正相关。
应理解，通过本步骤的参数转换过程，可以在回拨及时性参数与再次呼叫的等待时长呈负相关时，将其转换为与再次呼叫的等待时长呈正相关，以便后续更加准确地预测再次呼叫的时间。
S1004，呼叫回拨时长预测模块根据用户的历史回拨时长和转换参数，确定再次呼叫的等待时长。
应理解，用户的历史回拨时长用于基于用户对未接呼叫的回拨历史数据，反映用户针对未接呼叫的回拨习惯。该历史回拨时长可以具体是用户在不同的划分时段内执行回拨的平均时长。
根据本申请实施例提供的呼叫时间提醒的方法，通过将分析并量化用户状态、用户设备使用习惯等，确定其对再次呼叫时间的影响，使得再次呼叫时间的预测结果更加准确，提升双方通话成功的可能性。
为更好地理解本申请实施例提供的呼叫时间提醒的方法，以下结合附图对预测呼叫时间的具体过程进行介绍。
示例性的，如图11所示，为本申请实施例提供的一种呼叫时间提醒的方法的示意性流程图。该过程可以通过图8所示的呼叫时间预测系统中的各个模块执行，包括以下步骤：
S1101，第一移动终端通过数据收集和处理模块收集目标信息，其中，目标信息用于指示用户状态、用户对第一移动终端的使用习惯和用户对第一移动终端的实时操作频率。
应理解，本申请实施例提供的呼叫时间提醒的方法可以依据用户状态、对第一移动终端的使用习惯、用户对第一移动终端的实时操作频率等多项指标参数预测呼叫回拨时长。其中，本申请实施例中的用户可以对应于被叫者。
在一些实施例中，用户状态可以包括多种类型，比如会议状态、用餐状态、驾车状态、步行状态、休息状态等等。该目标信息可以包括用于分析获取用户状态的信息或信息组合，比如时间信息、位置信息、日程安排信息、与其他设备的连接信息、步 数信息等等。
在一些实施例中，用户对第一移动终端的使用习惯可以指用户每次使用第一移动终端的时长、用户在一天内的不同时段使用第一移动终端的频率等。该目标信息还可以包括用于分析获取用户对第一移动终端使用习惯的信息或者信息组合，比如用户在一天中不同时段内是否使用第一移动终端、用户在一天中不同时段内使用第一移动终端的时长等等。
S1102，第一移动终端根据目标信息确定用户事件影响因子。
在一些实施例中，第一移动终端可以通过数据收集和处理模块根据目标信息确定用户状态。不同信息或者不同信息组合可以对应于不同的用户状态。示例性的，如表1所示，为本申请实施例提供的一些用户状态与不同信息(或不同信息组合)之间的对应关系示例。
表1
Figure PCTCN2022114237-appb-000002
结合表1所示，针对用户状态E1，分析过程例如可以是：用户可以在第一移动终端(如第一移动终端的日历App)上记录日程安排为在09:00-11:00时间段内开会，则第一移动终端可以根据该特定时间段对应的日程安排，确定用户在09:00-11:00时间段内处于开会状态。
结合表1所示，针对用户状态E2，分析过程例如可以是：第一移动终端可以根据当前时间属于预设的用餐时间段(如06:00-08:00、11:00-13:00或17:00-19:00中任意一个时间段)，以及根据用户当前位置定位在餐饮场所，确定用户当前处于用餐状态。
结合表1所示，针对用户状态E3，分析过程例如可以是：第一移动终端可以根据用户当前的位置定位在道路，且该第一移动终端与车载设备处于连接状态，确定用户此时处于开车状态或乘车状态。
结合表1所示，针对用户状态E4，分析过程例如可以是：第一移动终端可以根据计步器中的步数在实时增加，确定用户处于步行状态。
表1中列出的信息类型仅为示例，在实际应用中，第一移动终端可以通过数据收集和处理模块获取更多其他类型的信息，并基于这些信息确定用户状态，本申请实施例对此不作限定。
可以理解的，用户处于不同用户状态时，接听呼叫的方便程度不相同，对应的再次呼叫的等待时长也不相同。比如，当用户处于会议状态时，认为用户的开会行为会 使得用户不方便在会议期间接听呼叫，需要在会议结束后再次发起呼叫，此时对应的再次呼叫的等待时长可能较长。又比如，当用户处于驾车状态或乘车状态时，认为用户的开车行为或乘车行为不会影响其接听呼叫，可以在短时间内再次发起呼叫，此时对应的再次呼叫的等待时长较短。
因此，为了更加准确地预测再次呼叫的等待时长，本申请通过设置用户事件影响因子以表示不同的用户状态对再次呼叫的等待的影响。不同用户状态可以对应不同的用户事件影响因子数值。为描述清楚，这里以用户事件影响因子的数值与用户状态对回拨及时性的影响呈正相关为例进行介绍，也就是说，如果某一用户状态对应的用户事件影响因子的数值越大，则表示该用户状态下用户回拨越及时，对应的再次呼叫的等待时间会越短。
在一种可能的实现方式下，第一移动终端可以预先获取用户状态与用户事件影响因子(记为IF1)之间的对应关系，其中，不同用户状态对应的用户事件影响因子的大小可以根据经验确定。示例性的，不同用户状态对应的用户事件影响因子的确定方式可以是：首先，设置用户事件影响因子对应的系数范围(thl1，thr1)；然后，根据不同的用户状态对再次呼叫等待时长的影响，从该系数范围(thl1，thr1)内选取不同的数值作为不同用户状态对应的系数；该系数可以用于确定用户事件影响因子，或者该系数也可以用于直接表示用户事件影响因子的大小。举例来说，假设用户事件影响因子对应的系数范围为(0，2)，考虑到会议状态对应的回拨及时性较低，再次呼叫等待时长可能较长，则可以从(0，2)范围内选择0.3作为会议状态E1对应的用户事件影响因子，具体可以表示为IF1(E1)＝0.3；而考虑到驾车状态或乘车状态对应的回拨及时性较高，则可以从(0，2)范围内选择1.8作为驾车状态或乘车状态E3对应的用户事件影响因子，具体可以表示为IF1(E3)＝1.8。换句话说，用户事件影响因子IF1越大，意味着回拨及时性越高，呼叫回拨时长可能越短。
在一些实施例中，第一移动终端可以通过数据收集和处理模块分析得到用户当前所处的用户状态；之后，第一移动终端可以基于用户状态与用户事件影响因子的对应关系，获取用户当前所处的用户状态对应的用户事件影响因子。
S1103，第一移动终端根据目标信息确定设备使用率影响因子。
可以理解的，用户每次使用第一移动终端的时长会影响再次呼叫的等待时长。因此，为了更加准确地预测该再次呼叫的等待时长，本申请通过设置设备使用率影响因子以表示用户每次使用设备的时长对该再次呼叫等待时长的影响。
在一些实施例中，目标信息可以包括用户在各时段内不使用设备的时长等信息，第一移动终端可以根据目标信息中的前述信息确定每个时段对应的设备使用率影响因子。
作为一个示例，第一移动终端根据目标信息获取设备使用率影响因子的过程可以包括：以天(24h)为时间单位，将一天中的24h平均划分为多个子时段，每个子时段的时长(即上述第一时长)可以为T1；然后，统计用户在每个子时段内不使用第一移动终端的时长；根据T1以及每个子时段内用户不使用第一移动终端的时长确定设备使用率影响因子。举例来说，如图12所示，设T1＝20min，将一天24h划分为时长均为20min的多个子时段；之后，统计用户在每个子时段内不使用第一移动终端的时长， 比如以图12中所示的子时段09:00-09:20、09:20-09:40、09:40-10:00、10:00-10:20为例，每个子时段中用户不使用设备的时长统计结果可以如表2所示：
表2
子时段 不使用设备的时长
…… ……
09:00-09:20 5min
09:20-09:40 0min
09:40-10:00 15min
10:00-10:20 12min
…… ……
按照上述统计方式，可以累积统计预设历史时段(比如一年)内多天(如一年内每一天)各个子时段用户不使用设备的时长；然后，利用累积的统计结果，确定该预设历史时段内每个子时段对应的不使用设备的平均时长，示例性的，假设预设历史时段内各个子时段对应的用户不使用设备的平均时长为表3所示：
表3
时段 预设时段内不使用设备的平均时长
…… ……
09:00-09:20 5min
09:20-09:40 3min
09:40-10:00 10min
10:00-10:20 15min
…… ……
最后，利用各个子时段对应的用户不使用设备的平均时长以及各个子时段的时长T1，确定每个子时段对应的设备使用率影响因子。示例性的，每个子时段对应的设备使用率影响因子可以通过以下公式(1-1)确定获得：
Figure PCTCN2022114237-appb-000003
其中，IF2表示设备使用率影响因子；T1表示每个子时段对应的时长；t表示该子时段内对应的用户不使用设备的平均时长。
上述列举的计算方式，会使得设备使用率影响因子的与回拨及时性呈正相关，也就是说，如果设备使用率影响因子的数值越大，则表示用户回拨及时性越高，对应的再次呼叫的等待时间会越短。
在一些实施例中，第一移动终端获取预设历史时段内每个时间单位(如每天)各子时段不使用设备的时长的方式可以包括：当第一移动终端是新设备时，可将用户之前使用的设备上的设备使用数据通过数据转移(如数据克隆)方式发送至第一移动终端，第一移动终端可以利用获取的原设备上的设备使用数据确定该设备使用率影响因子。在第一移动终端的使用过程中，第一移动终端可以记录用户使用和或不使用该第一移动终端的时长数据，第一移动终端后续可以利用该第一移动终端自身记录的相关数据确定设备使用率影响因子，或者也可以利用原设备上的设备时长数据和该第一移 动终端自身记录的时长数据综合确定设备使用率影响因子。
应理解，上述预设历史时段越长，获得的不使用设备的平均时长能够越准确地反映用户在每个子时段的设备使用率，因而，当用户新使用第一移动终端时，可以通过原有设备记录的设备使用和/或不使用时长确定设备使用率因子，从而更加准确地表示用户设备使用情况(或设备使用习惯)对再次呼叫时间的影响；而当第一移动终端自身记录有足够的设备使用和/或不使用的时长数据(如记录超过一年的目标数据)后，该第一移动终端可以利用自身记录的相关数据计算该设备使用率影响因子。
还应理解，这里的预设历史时段可以是固定时长的历史时段，如当前之前的一年内；或者，也可以是时长不固定的历史时段，如第一移动终端记录设备使用和/或不使用设备的时长数据的开始时间至当前时间的动态累计的时段。本申请对此不作限定。
需要说明的是，在另一些实施例中，第一移动终端还可以通过其他方式确定用户的设备使用率影响因子。比如，第一移动终端也可以通过用户在各个时段内连续使用设备的时长，以及该时段对应的单位时长确定设备使用率影响因子。
S1104，第一移动终端根据目标信息确定实时操作频率影响因子。
其中，实时操作频率影响因子可以用于表示用户操作设备的频率。可以理解的，若用户查看第一移动终端比较频繁，则再次呼叫时被接听的概率会较高，再次呼叫的等待时长可能会越短。为了更加准确地预测再次呼叫的时间，本申请实施例通过设置实时操作频率影响因子来表示用户设备使用频率对再次呼叫的等待时长的影响。
示例性的，实时操作频率影响因子的确定过程可以包括：以T2(对应于第二时长)为时间单位划分未接呼叫事件发生时刻邻近的时间段(如未接呼叫发生之前的1min)(对应于第二时间段)，得到时间间隔为T2的多个时刻；分别统计各个时刻用户是否在使用第一移动终端；利用预设算法，根据统计结果确定实时操作频率影响因子IF3。其中，预设算法可以灵活设置，比如可以通过确定n个时刻中用户使用设备的次数m所占的百分比获得IF3，也即可通过以下公式(1-2)确定获得IF3：
Figure PCTCN2022114237-appb-000004
其中，IF3为实时操作频率影响因子；m为n个时刻中用户使用设备的次数，m小于或等于n；n为统计的时刻数量，n为大于1的整数。
或者，还可以通过以下公式(1-3)确定获得IF3：
Figure PCTCN2022114237-appb-000005
其中，IF3为实时操作频率影响因子；m为n个时刻中用户使用设备的次数，m小于或等于n；n为统计的时刻的数量，n为大于1的整数；c为大于1的常数，如c＝2。
举例来说，假设未接呼叫发生的时间为09:24:00，则以该时间之前的时间段为分析对象，以T2为30s，n为10为例对其进行划分，得到的各个时刻以及时刻对应的是否使用设备的结果如表4所示：
表4
n 时间点 是否使用第一移动终端
1 09:24:00 否
2 09:23:30 是
3 09:23:00 是
4 09:22:30 否
5 09:22:00 是
6 09:21:30 是
7 09:21:00 是
8 09:20:30 是
9 09:20:00 是
10 09:19:30 是
之后，可以利用公式(1-1)确定实时操作频率影响因子为：
Figure PCTCN2022114237-appb-000006
通过上述确定过程，可以获取在接收的未接呼叫时，用户实时的设备操作情况对回拨时长的影响。其中，实时操作频率影响因子越大，意味着用户使用设备的频率越高，可能接听呼叫的可能也就越大，对应的再次呼叫的等待时长可能越短。
为了更加客观地评估实时操作结果对回拨时长的影响，本申请实施例可以设置实时操作频率因子的系数范围(thr2，thl2)，使得确定获取的实时操作频率因子落入该系数范围，从而更加客观地评估实时操作结果对再次呼叫等待时长的影响。例如，设置实施例操作频率影响因子对应的系数范围为(0，2)，此时可以通过将公式(1-2)中的常数c设置为2，以使得到的IF3结果处于系数范围内
Figure PCTCN2022114237-appb-000007
此外，还可以通过其他方式的归一化处理使得IF3的结算结果处于设置的系数范围内，本申请实施例对此不作限定。
需要说明的是，这里仅以公式(1-2)和公式(1-3)为例对确定IF3的方式进行介绍，但在实际应用中，其它的可以使确定结果IF3与使用次数呈正相关的算法均可以应用于此处，本申请实施例对此不作限定。
S1105，第一移动终端通过回拨及时性模块确定回拨及时性参数。
考虑到用户状态、用户的设备使用习惯和用户当下使用设备的动态数据均会影响再次呼叫的等待时长的预测结果，因而需要综合上述获得的各项影响因子，以综合评估被叫者在当前呼叫未接的情况下的回拨及时性。
在一些实施例中，第一移动终端可以通过回拨及时性模块根据上述获得的IF1、IF2和IF3确定回拨及时性参数。示例性的，回拨及时性评估模块可以通过以下公式(1-4)确定回拨及时性参数M1：
M1＝IF1×IF2×IF3     (1-4)
作为一个示例，以用户状态是E1，结合上述示例的各影响因子的取值为例，回拨及时性参数M1为：M1＝1.8×1.6×0.75＝2.16。
该回拨及时性参数用于综合反映上述获得的IF1、IF2和IF3对再次呼叫时间的影响。该回拨及时性可以与IF1、IF2和IF3呈正相关，在上述列举的公式(1-4)之外，还可以通过其他算法模型计算该回拨及时性参数，比如对IF1、IF2和IF3进行求和或者加权求和等。
S1106，第一移动终端根据回拨及时性参数获取转换参数，该转换参数与回拨时长 呈正相关。
应理解，通过上述步骤S1102至步骤S1105的确定方式得到的回拨及时性参数为正向期望值，该正向期望值越大，意味着呼叫方可以回拨越快，而再次呼叫的等待时间为负向期望值，回拨及时性参数越大意味着再次呼叫的等待的时长越短。因此，为了获取更加直观的再次呼叫等待时长的预测结果，需要通过本步骤对回拨及时性参数进行转换，得到与再次呼叫的等待时长呈正相关的转换数据，以便后续更加直观地向呼叫者提醒再次呼叫的时间。
其中，对回拨及时性参数进行转换的方式可以有多种。比如可以通过以下公式(1-5)和公式(1-6)确定转换参数M2：
th＝(thr3-thl3)/4     (1-5)
M2＝M1-th       (1-6)
thr3和thl3为预设的回拨及时性参数所属的系数范围(thr3，thl3)，thr3和thl3为大于0的正整数。
引用上述M1的取值示例2.16，M1的取值范围为(0，4)，此时M2＝0.08。
S1107，第一移动终端根据用户历史回拨时长和转换参数获取再次呼叫的等待预测结果。
应理解，被叫者接收到未接呼叫的回拨习惯可能也会影响回拨时长。比如，有些被叫者获知有未接呼叫后，习惯及时回拨，此时回拨时长可能较短；而有些被叫者获知有未接呼叫后，习惯选择在较长时间后(如下班后)回拨，此时对应的回拨时长可能较长。因此，为了更加准确地预测回拨时长，可以通过该步骤根据被叫者的回拨习惯确定回拨时长。
示例性的，一种可能的实现方式中，第一移动终端可以就记录用户的回拨数据。该回拨数据可以是用户在每天的不同时段接到未接呼叫时的回拨时间，比如，按照一定时间间隔T3将每天划分为多个时段，如果用户的某一个时段接收到未接呼叫时，记录用户针对该未接呼叫的回拨时长，并将其作为该时段对应的用户回拨时长，以反映用户在该时段的回拨习惯。举例来说，假设T3为20min将一天划分为多个时段，用户在09:21(对应时段09:20-09:40)接收到未接呼叫，并且在10min后(也即09:31)对该呼叫进行回拨，则时段09:20-09:40对应的用户回拨时长就是10min。第一移动终端可以实时记录每一次用户回拨时对应的历史回拨数据，当预测回拨时长时，利用记录的历史回拨数据，确定每个时段对应的用户回拨平均数据，然后利用该用户回拨平均数据对步骤S1106中的转换参数进行修正，获得更加准确的回拨时长。
可选地，在一种可能的实现方式中，第一移动终端还可以利用预设历史时间段内的用户回拨数据对转换参数进行修正。比如，第一移动终端可以利用当前之前一年内的用户回拨数据，确定每天每个时段内的用户回拨时长平均值，并利用该用户回拨时长平均值对转换参数进行修正。
在一些实施例中，第一移动终端利用用户回拨平均时长和转换参数确定当前再次呼叫的等待时长的预测结果Rt例如可以通过公式(1-7)确定：
Rt＝(1-M2)×t     (1-7)
其中，M2为转换参数；t为当前时段内对应的用户回拨时长平均值。
举例来说，假设当前时段为09:20-09:40，用户在该时段内的用户回拨时长平均值为5min，且M2为上述确定获得的示例性数值0.08，则此时回拨时长的预测结果Rt＝(1-0.08)×5＝4.6min。
S1108，第一移动终端向第二移动终端发送呼叫时间提醒消息。
其中，该呼叫时间提醒消息包括预测的再次呼叫的等待时长，用于向呼叫者提示再次呼叫的合适时间。
第一移动终端向第二移动终端发送呼叫时间提醒消息的方式可以有多种，比如通过短信、即时讯通App等。该呼叫时间提醒消息可以以多种方式呈现给呼叫者，比如以文本形式、语音形式等。本申请实施例对此不作限定。
需要说明的是，本申请实施例示出的再次呼叫的等待时长的确定方式仅为示例，但并不作为限定。在实际应用中，还可以通过其它方式(如公式)将用户状态、用户的设备使用习惯等量化为特定参数，预测该再次呼叫的等待时长。
还需要说明的是，本申请实施例中的步骤S1106为可选步骤，比如，如果对用户状态、用户设备使用习惯、设备实时操作频率等量化后的参数均与再次回拨的等待时长为正相关(量化后的参数越小表示回拨时长越短)，则可以不执行步骤S1106中对回拨及时性参数进行转换。此外，步骤S1102至步骤S1104的执行顺序也并不仅限于上述示出的顺序。
总的来说，本申请实施例提供的呼叫时间提醒的方法主要通过将用户状态、用户的设备使用习惯、用户的实时动态使用情况等量化为参数，进而根据这些参数获得回拨时长的预测结果。上述列举的确定方式仅用于更好地理解本申请实施例提供的呼叫时间提醒的方法，在另一些实施例中，还可以设置其他的确定方式对用户状态等进行量化，进而确定再次呼叫的时间，本申请对此并不限定。
根据本申请实施例提供的呼叫时间提醒的方法，通过将分析并量化用户状态、用户设备使用习惯等，确定其对再次呼叫时间的影响，使得再次呼叫时间的预测结果更加准确，提升双方通话成功的可能性。
基于同样的技术构思，本申请实施例还提供了一种终端设备，包括：显示器；一个或多个处理器；一个或多个存储器；所述一个或多个存储器存储有一个或多个计算机程序，所述一个或多个计算机程序包括指令，当所述指令被所述一个或多个处理器执行时，使得所述终端设备执行上述任一个方法中的一个或多个步骤。
基于同样的技术构思，本申请实施例还提供了一种计算机可读存储介质，该计算机可读存储介质中存储有指令，当其在计算机或处理器上运行时，使得计算机或处理器执行上述任一个方法中的一个或多个步骤。
基于同样的技术构思，本申请实施例还提供了一种包含指令的计算机程序产品。当该计算机程序产品在计算机或处理器上运行时，使得计算机或处理器执行上述任一个方法中的一个或多个步骤。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用 计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者通过所述计算机可读存储介质进行传输。所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线)或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质(例如，固态硬盘(solid state disk，SSD))等。
本领域普通技术人员可以理解实现上述实施例方法中的全部或部分流程，该流程可以由计算机程序来指令相关的硬件完成，该程序可存储于计算机可读取存储介质中，该程序在执行时，可包括如上述各方法实施例的流程。而前述的存储介质包括：ROM或随机存储记忆体RAM、磁碟或者光盘等各种可存储程序代码的介质。
以上所述，仅为本申请实施例的具体实施方式，但本申请实施例的保护范围并不局限于此，任何在本申请实施例揭露的技术范围内的变化或替换，都应涵盖在本申请实施例的保护范围之内。因此，本申请实施例的保护范围应以所述权利要求的保护范围为准。

Claims (17)

  1. 一种呼叫时间提醒的方法，其特征在于，应用于第一移动终端，包括：
    接收呼叫者通过第二移动终端发起的呼叫；
    当确定发生未接呼叫事件时，基于呼叫时间预测模型获取再次呼叫的时间信息；
    向所述第二移动终端发送呼叫时间提醒消息，所述呼叫时间提醒消息用于向所述呼叫者提示所述再次呼叫的时间信息。
  2. 根据权利要求1所述的方法，其特征在于，所述再次呼叫的时间信息为再次呼叫的等待时长或者为再次呼叫的时刻。
  3. 根据权利要求1或2所述的方法，其特征在于，所述向所述第二移动终端发送呼叫时间提醒消息，具体包括：
    通过短信方式向所述第二移动终端发送所述呼叫时间提醒消息；或者，
    通过即时通讯应用程序向所述第二移动终端发送所述呼叫时间提醒消息。
  4. 根据权利要求1-3中任一项所述的方法，其特征在于，所述呼叫时间提醒消息为语音和/或文本。
  5. 根据权利要求1-4中任一项所述的方法，其特征在于，所述呼叫时间预测模型用于根据用户状态、用户对所述第一移动终端的使用习惯和所述用户对所述第一移动终端的实时操作频率确定所述再次呼叫的时间信息。
  6. 根据权利要求5所述的方法，其特征在于，所述当确定发生未接呼叫事件时，基于呼叫时间预测模型获取再次呼叫的时间信息，具体包括：
    收集目标信息，所述目标信息用于指示所述用户状态、所述用户对所述第一移动终端的使用习惯和所述用户对所述第一移动终端的实时操作频率；
    根据所述目标信息确定用户事件影响因子、设备使用率影响因子和实时操作频率影响因子，其中，所述用户事件影响因子用于指示所述用户习惯对再次呼叫时间的影响，所述设备使用率影响因子用于指示所述用户对所述第一移动终端的使用习惯对再次呼叫时间的影响，所述实时操作频率影响因子用于指示所述用户对所述第一移动终端的实时操作频率对再次呼叫时间的影响；
    根据所述用户事件影响因子、所述设备使用率影响因子和所述实时操作频率影响因子确定所述再次呼叫的时间信息。
  7. 根据权利要求6所述的方法，其特征在于，所述根据所述用户事件影响因子、所述设备使用率影响因子和所述实时操作频率影响因子确定所述再次呼叫的时间信息，具体包括：
    根据所述用户事件影响因子、所述设备使用率影响因子和所述实时操作频率影响因子确定回拨及时性参数，所述回拨及时性参数用于指示再次呼叫的及时性；
    根据预获取的所述用户的历史回拨时长和所述回拨及时性参数获取所述再次呼叫的时间信息。
  8. 根据权利要求7所述的方法，其特征在于，当再次呼叫的时间信息为再次呼叫的等待时长，且所述回拨及时性参数与所述再次呼叫的等待时长负相关时，所述根据预获取的所述用户的历史回拨时长和所述回拨及时性参数获取所述再次呼叫的时间信 息，具体包括：
    对所述回拨及时性进行转换，获得转换参数，所述转换参数与所述再次呼叫的等待时长正相关；
    根据预获取的所述用户的历史回拨时长和所述转换参数获取所述再次呼叫的时间信息。
  9. 根据权利要求6-8中任一项所述的方法，其特征在于，所述方法还包括：
    获取所述用户状态与所述用户事件影响因子的对应关系；
    根据所述目标信息确定所述用户当前的用户的状态；
    从所述用户状态与所述用户事件影响因子的对应关系中确定所述用户当前的用户的状态对应的所述用户事件影响因子。
  10. 根据权利要求1-9中任一项所述的方法，其特征在于，所述方法还包括：
    将一天中的第一时段划分为多个子时段，每个子时段的时长为第一时长；
    获取每个所述子时段内所述第一移动终端未被使用的时长。
  11. 根据权利要求10所述的方法，其特征在于，所述方法还包括：
    获取所述未接呼叫事件的发生时间，并确定所述发生时间所在的目标子时段，所述目标子时段为所述多个子时段中的某一个；
    根据所述第一时长和所述目标子时段内所述第一移动终端未被使用的时长，确定所述设备使用率影响因子。
  12. 根据权利要求11所述的方法，其特征在于，获取预设历史时段内多天中所述目标子时段内所述第一移动终端未被使用的多个时长；
    所述根据所述第一时长和所述目标子时段内所述第一移动终端未被使用的时长，确定所述设备使用率影响因子，具体包括：
    计算所述多天中所述目标子时段内所述第一移动终端未被使用的多个时长的平均值，获取所述目标子时段内所述第一移动终端未被使用的平均时长；
    根据所述第一时长和所述目标子时段内所述第一移动终端未被使用的平均时长，确定所述设备使用率影响因子。
  13. 根据权利要求11或12所述的方法，其特征在于，所述根据所述第一时长和所述目标子时段内所述第一移动终端未被使用的时长，确定所述设备使用率影响因子，具体包括：
    Figure PCTCN2022114237-appb-100001
    其中，IF2表示所述设备使用率因子，T1表示所述子时段的第一时长，t表示所述目标子时段内所述第一移动终端未被使用的平均时长。
  14. 根据权利要求6-13中任一项所述的方法，其特征在于，所述方法还包括：
    以所述未接呼叫事件发生的时间为基准，确定第二时段；
    在所述第二时段内选择多个时刻，且每两个相邻的所述时刻之间的时间间隔为第二时长；
    统计在每个所述时刻，所述用户是否使用所述第一移动终端；
    根据所述用户在每个所述时刻是否使用所述第一移动终端的统计结果，以及所述 时刻的数量，确定所述实时操作频率影响因子。
  15. 一种移动终端，其特征在于，包括：
    一个或多个处理器；
    一个或多个存储器；
    所述一个或多个存储器存储有一个或多个计算机程序，所述一个或多个计算机程序包括指令，当所述指令被所述一个或多个处理器执行时，使得所述终端设备执行如权利要求1至14中任一项所述的方法。
  16. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质存储有计算机可执行程序，所述计算机可执行程序在被计算机调用时，使所述计算机执行如权利要求1至14中任一项所述的方法。
  17. 一种包含指令的计算机程序产品，其特征在于，当所述计算机程序产品在第一移动终端上运行时，使得所述第一移动终端执行如权利要求1至14中任一项所述的方法。
PCT/CN2022/114237 2021-09-26 2022-08-23 呼叫时间提醒的方法及终端 WO2023045673A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202111131953.8 2021-09-26
CN202111131953.8A CN115643337B (zh) 2021-09-26 2021-09-26 呼叫时间提醒的方法及终端

Publications (1)

Publication Number Publication Date
WO2023045673A1 true WO2023045673A1 (zh) 2023-03-30

Family

ID=84940252

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/114237 WO2023045673A1 (zh) 2021-09-26 2022-08-23 呼叫时间提醒的方法及终端

Country Status (2)

Country Link
CN (1) CN115643337B (zh)
WO (1) WO2023045673A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116431695A (zh) * 2023-06-08 2023-07-14 荣耀终端有限公司 一种推荐信息确定方法、电子设备和存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5742674A (en) * 1995-12-22 1998-04-21 At&T Corp. Automatic call-back system and method using data indicating best time to call
CN101202983A (zh) * 2006-12-12 2008-06-18 北京三星通信技术研究有限公司 主叫预获知被叫时间的方法及系统
CN105933552A (zh) * 2016-04-22 2016-09-07 广东小天才科技有限公司 一种主动提醒呼叫方再次呼叫的方法及系统
WO2016145739A1 (zh) * 2015-03-18 2016-09-22 中兴通讯股份有限公司 一种实现通话提醒的方法和装置
CN106375539A (zh) * 2015-07-21 2017-02-01 中兴通讯股份有限公司 未接来电提示方法、装置及被叫终端

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103188619A (zh) * 2011-12-28 2013-07-03 宇龙计算机通信科技(深圳)有限公司 提醒用户呼叫的方法、装置及移动终端
CN106506332A (zh) * 2016-10-31 2017-03-15 宇龙计算机通信科技(深圳)有限公司 自动回复方法及装置
CN109561195A (zh) * 2019-01-25 2019-04-02 努比亚技术有限公司 来电回复方法、装置、移动终端以及存储介质
CN110062110A (zh) * 2019-04-24 2019-07-26 国网上海市电力公司 基于模糊理论的来电用户排序方法与智能呼叫方法及系统

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5742674A (en) * 1995-12-22 1998-04-21 At&T Corp. Automatic call-back system and method using data indicating best time to call
CN101202983A (zh) * 2006-12-12 2008-06-18 北京三星通信技术研究有限公司 主叫预获知被叫时间的方法及系统
WO2016145739A1 (zh) * 2015-03-18 2016-09-22 中兴通讯股份有限公司 一种实现通话提醒的方法和装置
CN106375539A (zh) * 2015-07-21 2017-02-01 中兴通讯股份有限公司 未接来电提示方法、装置及被叫终端
CN105933552A (zh) * 2016-04-22 2016-09-07 广东小天才科技有限公司 一种主动提醒呼叫方再次呼叫的方法及系统

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116431695A (zh) * 2023-06-08 2023-07-14 荣耀终端有限公司 一种推荐信息确定方法、电子设备和存储介质
CN116431695B (zh) * 2023-06-08 2023-10-20 荣耀终端有限公司 一种推荐信息确定方法、电子设备和存储介质

Also Published As

Publication number Publication date
CN115643337B (zh) 2023-10-20
CN115643337A (zh) 2023-01-24

Similar Documents

Publication Publication Date Title
US10206074B2 (en) Remote access to a mobile communication device over a wireless local area network (WLAN)
WO2020192456A1 (zh) 一种语音交互方法及电子设备
WO2020207326A1 (zh) 一种对话消息的发送方法及电子设备
EP4145286A1 (en) Memory management method and electronic device
WO2020211705A1 (zh) 一种联系人的推荐方法及电子设备
US10091643B2 (en) Method and apparatus for displaying associated information in electronic device
WO2020006711A1 (zh) 一种消息的播放方法及终端
CN107464557A (zh) 通话录音方法、装置、移动终端及存储介质
WO2021057452A1 (zh) 一种原子服务的呈现方法及装置
KR20150062686A (ko) 전자 장치의 스팸 필터링 방법 및 그 전자 장치
WO2020259554A1 (zh) 可进行学习的关键词搜索方法和电子设备
WO2023045673A1 (zh) 呼叫时间提醒的方法及终端
CN116048933B (zh) 一种流畅度检测方法
WO2021042881A1 (zh) 消息通知方法及电子设备
CN115460180A (zh) 视频通话的处理方法和装置、电子设备
CN114371895B (zh) 一种终端设备、邮件标记方法和存储介质
CN112640408A (zh) 一种呼叫提示方法及终端
CN114531413A (zh) 电子设备及其邮件同步方法和可读介质
CN114125353A (zh) 视频电话的呼叫方法、终端设备以及存储介质
WO2019153687A1 (zh) 一种通话记录的管理方法及终端
CN108566475A (zh) 联系人信息处理方法和装置、电子设备、存储介质
CN114115509B (zh) 一种应用管理方法及终端
CN116033064B (zh) 卡片显示的方法、电子设备及可读存储介质
CN116089320B (zh) 垃圾回收方法和相关装置
WO2019047127A1 (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: 22871726

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE