WO2019178985A1 - 预知通话条件的方法、电子装置、终端设备及存储介质 - Google Patents
预知通话条件的方法、电子装置、终端设备及存储介质 Download PDFInfo
- Publication number
- WO2019178985A1 WO2019178985A1 PCT/CN2018/095355 CN2018095355W WO2019178985A1 WO 2019178985 A1 WO2019178985 A1 WO 2019178985A1 CN 2018095355 W CN2018095355 W CN 2018095355W WO 2019178985 A1 WO2019178985 A1 WO 2019178985A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- mobile phone
- state
- status
- call
- terminal
- Prior art date
Links
Images
Classifications
-
- 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/72454—User interfaces specially adapted for cordless or mobile telephones with means for adapting the functionality of the device according to specific conditions according to context-related or environment-related conditions
Definitions
- the present application relates to the field of mobile communication technologies, and relates to a method for predicting a call condition, an electronic device, a terminal device, and a storage medium.
- the technical problem to be solved by the present application is to overcome the problem of tentative dialing in the prior art that the caller cannot meet the call condition, and a method, an electronic device, a terminal device and a storage medium for predicting the call condition are proposed. Monitor and record the status of the mobile phone, so that the caller can know whether the other party's mobile phone meets the call condition before calling, and avoid invalid tentative call.
- a method for predicting a call condition includes the following steps:
- S1 receiving a local number uploaded by the mobile phone end and an associated mobile phone state, and determining, according to the state of the mobile phone, whether the mobile phone terminal is in a non-communication network or a shutdown state, wherein the mobile phone state includes real-time acquisition by monitoring Four states of power on, power off, start call and end call;
- An electronic device wherein the electronic device stores a system for predicting a call condition, and the system for predicting a call condition includes:
- a status receiving module configured to receive a local number uploaded by the mobile terminal and an associated mobile phone status, where the mobile phone status includes four states of starting, shutting down, starting a call, and ending a call obtained by monitoring real time;
- the abnormality determining module is configured to determine, according to the state of the mobile phone, whether the mobile phone terminal is in a non-communication network or a shutdown state;
- the request receiving module is configured to receive a mobile phone state acquisition request uploaded by the viewing party mobile phone end;
- the status query sending module is configured to send the status of the mobile phone to be queried according to the request to the mobile phone end.
- a terminal device comprising a memory and a processor, wherein the memory stores a system of predictive call conditions executable by the processor, the system performing the following steps when executed by the processor :
- S1 receiving a local number uploaded by the mobile phone end and an associated mobile phone state, and determining, according to the state of the mobile phone, whether the mobile phone terminal is in a non-communication network or a shutdown state, wherein the mobile phone state includes real-time acquisition by monitoring Four states of power on, power off, start call and end call;
- a computer readable storage medium having stored therein a system for predicting a call condition, the system for predicting a call condition being executable by at least one processor to cause the at least one processor to perform the following Step operation:
- S1 receiving a local number uploaded by the mobile phone end and an associated mobile phone state, and determining, according to the state of the mobile phone, whether the mobile phone terminal is in a non-communication network or a shutdown state, wherein the mobile phone state includes real-time acquisition by monitoring Four states of power on, power off, start call and end call;
- the positive progress of the application is that the user can see whether the other party's mobile phone satisfies the call condition before making a call, thereby avoiding situations such as busy, shutdown, etc., avoiding useless work, improving efficiency and user experience.
- FIG. 1 is a flow chart showing a first embodiment of a method for predicting a call condition according to the present application
- FIG. 2 is a flow chart showing a second embodiment of a method for predicting a call condition according to the present application
- FIG. 3 is a flowchart of Embodiment 3 of a method for predicting a call condition according to the present application
- FIG. 4 is a flow chart showing a fourth embodiment of a method for predicting a call condition according to the present application
- FIG. 5 is a flowchart of Embodiment 5 of a method for predicting a call condition according to the present application
- FIG. 6 is a schematic diagram of a program module of a first embodiment of a system for predicting a call condition in an electronic device of the present application
- FIG. 7 is a schematic diagram showing the hardware architecture of an embodiment of a terminal device of the present application.
- the present application proposes a method of predicting a call condition.
- the method for predicting a call condition includes the following steps:
- the state of the mobile phone includes four states of starting, shutting down, starting a call, and ending a call obtained by monitoring real-time.
- This method is only for mobile phones equipped with specific software programs that upload associated mobile phone status and mobile phone number to one or more designated servers according to the installed program.
- the mobile terminal also needs to have a listener installed.
- the mobile terminal In the normal state, the mobile terminal periodically uploads the associated mobile phone status and mobile phone number at preset time intervals.
- the four states of powering on, powering off, starting a call, and ending a call are monitored by instant uploading, that is, as soon as any state changes of any of the four states are found, the changed state of the mobile phone is uploaded to the server.
- No communication network and shutdown are abnormal states, which are obtained by the server based on the state of the mobile phone uploaded by the mobile terminal and the monitoring of the voice of the mobile phone.
- the server after receiving the mobile phone status and the mobile phone number uploaded by each mobile phone, the server does not actively send the mobile phone to the corresponding mobile phone terminal that contains the mobile phone numbers in the address book, but via the mobile phone terminal that needs to use this function. (ie, view the mobile terminal) Proactively initiate a request to obtain the status of the mobile phone corresponding to the relevant mobile phone number.
- the status of the mobile phone sent to the mobile phone is the last mobile phone status of the corresponding mobile phone, that is, the latest mobile phone status of the mobile phone.
- the contact in the address book of the mobile phone can be displayed for display, which is displayed on the contact details page.
- the search number does not necessarily need to be searched through the address book, it is preferably displayed on the call page with the contact, so that the user can know the mobile phone status of the other party in time.
- the user can see whether the other party's mobile phone satisfies the call condition before making a call, thereby avoiding situations such as busy, shutdown, etc., avoiding useless work, improving efficiency and user experience.
- the abnormality determination of the non-communication network includes the following steps:
- S111 determining whether the state of the mobile phone last uploaded by the mobile terminal is a non-communication network, if otherwise, executing S112, if yes, executing S111 in a loop;
- S115 Identify the mobile phone state of the mobile phone as a non-communication network and save the mobile phone number of the mobile phone end, and update the upload time to the current time.
- the following is an example of judging whether the mobile phone is a non-communication network state, and specifically describes:
- the mobile phone status is uploaded every 5 minutes, and the status update status of the mobile phone 1 stored in the server is as follows:
- 13912341234 Start a call 2017-11-30 12:07 13912341234 Normal standby 2017-11-30 12:10 13912341234 End call 2017-11-30 12:12 13912341234 Normal standby 2017-11-30 12:15
- the server obtains the mobile phone at 12:20. The last time the mobile phone status is normal standby, and the upload time is 2017-11-30 12:15;
- the server calculates that the last update interval is 5 minutes. If the preset interval threshold is 8 minutes, the last update interval at this time has not exceeded 8 minutes, so the decision step is repeated.
- the server obtains the mobile phone again at 12:25. The last time the mobile phone status is normal standby, and the upload time is still 2017-11-30 12:15;
- the server calculates that the last update interval is 10 minutes. At this time, the last update interval exceeds 8 minutes. Therefore, it is determined that the mobile phone is in the state of no communication network, and the state of the non-communication network is associated with the mobile phone number of the mobile phone 1 as follows. :
- the abnormality determination of the shutdown includes the following steps:
- a prompt tone will be played during the connection process, for example, a “beep” long tone in the connection, indicating that the other party’s “beep” short tone during the call indicates that the machine is down. "The call you made has been stopped", etc., the stop sound is the last one.
- S123 Identify the mobile phone state of the mobile phone as a non-communication network and save the mobile phone number of the mobile phone end, and update the upload time to the current time.
- the server determines that the sound is consistent with the pre-stored downtime, and determines that the mobile phone is in a shutdown state;
- the server associates the shutdown status with the mobile phone number of the mobile phone 1 and saves the following table:
- the S2 includes the following steps:
- the request since it is a request to acquire the mobile phone status of all the contacts in the address book, the request only includes the number of its own phone, and does not include the number of the other party's mobile phone to be queried.
- the mobile terminal is configured to package and upload the address book in the local machine according to the address book acquisition request of the server.
- the contact information of the contact saved in the mobile phone address book includes a mobile phone number, a fixed phone number, an email address, etc., and the mobile phone end used by all the contacts in the mobile phone address book uploads the mobile phone status to the server. Therefore, this step needs to find out the mobile phone numbers of the mobile phones that upload the mobile phone status to the server.
- the latest mobile phone status that is queried is sent to the mobile phone, but the unqueried can be skipped, and the mobile phone status with no result or empty is sent to the mobile phone.
- the request sent by the mobile phone user only includes the number of the local device, and does not include the number of the mobile phone of the other party to be queried. To distinguish between the user needs to get the phone status of all contacts in the address book.
- the user can directly obtain the mobile phone status of all contacts in the address book at one time, and is particularly suitable for the situation that multiple people need to be contacted in a short time.
- the mobile phone status acquisition request when the mobile phone status acquisition request is to acquire the mobile phone status of a single contact, the mobile phone status acquisition request includes the single contact.
- the mobile phone number, the S2 includes the following steps:
- the mobile phone status acquisition request includes a local number for viewing the mobile phone end, and further includes a mobile phone number of the mobile phone end of the individual contact to be viewed, and the foregoing information included in the request is arranged according to the agreed rules.
- the information of the specific location in the request is intercepted, that is, the mobile phone number of the single contact.
- the request includes the local number of the mobile phone, so after the result is queried, the server may feed back the result of the query to the mobile phone.
- the user can view the mobile phone status of the other party according to each specific call object, and the speed is faster than querying the entire address book.
- the present application proposes an electronic device, which may be a server on which is stored a system 20 for predicting a call condition, which system 20 may be divided into one or more program modules.
- FIG. 4 shows a schematic diagram of a program module of the first embodiment of the system 20 for predicting a call condition.
- the system 20 can be divided into a status receiving module 201, an abnormality determining module 202, and a request receiving module. 203 and status query sending module 204.
- the program module referred to in the present application refers to a series of computer program instructions capable of performing a specific function. The following description will specifically describe the specific functions of the program modules 201-204.
- the status receiving module 201 is configured to receive a local number uploaded by the mobile phone end and an associated mobile phone status, where the mobile phone status includes four states of starting, shutting down, starting a call, and ending a call obtained by monitoring real-time.
- the abnormality determining module 202 is configured to determine, according to the state of the mobile phone, whether the mobile phone terminal is in a non-communication network or a shutdown abnormal state.
- the request receiving module 203 is configured to receive a mobile phone state acquisition request uploaded by the viewer mobile terminal.
- the status query sending module 204 is configured to send the status of the mobile phone to be queried according to the request to the mobile phone end.
- the status of the mobile phone sent to the mobile phone is the last mobile phone status of the corresponding mobile phone, that is, the latest mobile phone status of the mobile phone.
- the electronic device updates the mobile phone status of the mobile phone 1 to no communication network at 2017-11-30 12:35;
- the user of the mobile phone 2 sends a request for checking the status of the mobile phone of the mobile phone at 2017-11-30 12:38, and the electronic device transmits the status of the non-communication network of the mobile phone 1 to the mobile phone 2 by comparing.
- the user of the mobile phone 2 requests to view the mobile phone status of all contacts in the address book as an example, and specifically:
- the mobile two-way electronic device sends a request for obtaining the mobile phone status of all contacts in the address book
- the electronic device After receiving the address book uploaded by the mobile phone 2, the electronic device knows that only the eight mobile phone numbers are the same as the mobile phone number of the address book by comparing with the existing saved mobile phone number;
- the electronic device sends the last uploaded mobile phone status saved in association with the same 8 mobile phone numbers to the mobile phone 2.
- the present application also proposes a terminal device.
- the terminal device 2 is a device capable of automatically performing numerical calculation and/or information processing according to an instruction set or stored in advance.
- the terminal device 2 can be a smartphone, a tablet, a laptop, a desktop computer, a rack server, a blade server, a tower server, or a rack server (including a stand-alone server, or a server cluster composed of multiple servers).
- the terminal device 2 includes at least, but not limited to, a system 20 that can communicate with each other via a system bus to the memory 21, the processor 22, the network interface 23, and the foreseeable call conditions. among them:
- the memory 21 includes at least one type of computer readable storage medium including a flash memory, a hard disk, a multimedia card, a card type memory (eg, SD or DX memory, etc.), a random access memory (RAM), Static Random Access Memory (SRAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), Programmable Read Only Memory (PROM), magnetic memory, magnetic disk, optical disk, and the like.
- the memory 21 may be an internal storage unit of the terminal device 2, such as a hard disk or memory of the terminal device 2.
- the memory 21 may also be an external storage device of the terminal device 2, such as a plug-in hard disk equipped on the terminal device 2, a smart memory card (SMC), and a secure digital device.
- the memory 21 may also include both the internal storage unit of the terminal device 2 and its external storage device.
- the memory 21 is generally used to store an operating system installed in the terminal device 2 and various types of application software, such as program code of the system 20 for predicting the call condition. Further, the memory 21 can also be used to temporarily store various types of data that have been output or are to be output.
- the processor 22 may be a Central Processing Unit (CPU), controller, microcontroller, microprocessor, or other data processing chip in some embodiments.
- the processor 22 is typically used to control the overall operation of the terminal device 2, such as performing control and processing related to data interaction or communication with the terminal device 2.
- the processor 22 is configured to run program code or processing data stored in the memory 21, such as the system 20 for running the predicted call condition.
- the network interface 23 may comprise a wireless network interface or a wired network interface, which is typically used to establish a communication connection between the terminal device 2 and other terminal devices.
- the network interface 23 is configured to connect the terminal device 2 to an external terminal through a network, establish a data transmission channel, a communication connection, and the like between the terminal device 2 and an external terminal.
- the network may be an intranet, an Internet, a Global System of Mobile communication (GSM), a Wideband Code Division Multiple Access (WCDMA), a 4G network, or a 5G network.
- Wireless or wired networks such as network, Bluetooth, Wi-Fi, etc.
- FIG. 5 only shows the terminal device 2 with the components 21-23, but it should be understood that not all illustrated components are required to be implemented, and more or fewer components may be implemented instead.
- system 20 of the predictive call conditions stored in the memory 21 may be executed by one or more processors (the processor 22 in this embodiment) to perform the operations of the method for predicting the call conditions described above. .
- the present application is a computer readable storage medium having stored therein a system 20 for predicting a call condition, the system 20 for predicting a call condition being executable by one or more processors to implement the predictive call described above Conditional method or operation of an electronic device.
Landscapes
- Engineering & Computer Science (AREA)
- Environmental & Geological Engineering (AREA)
- Human Computer Interaction (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Telephonic Communication Services (AREA)
- Mobile Radio Communication Systems (AREA)
- Telephone Function (AREA)
Abstract
本申请公开了一种预知通话条件的方法、电子装置、终端设备及存储介质，属于移动通信技术领域。一种预知通话条件的方法，包括以下步骤：S1、接收手机端上传的本机号码和相关联的手机状态，并根据所述手机状态判断所述手机端是否处于无通讯网络或停机两种异常状态；所述手机状态包括通过监听实时获取的开机、关机、开始通话和结束通话四种状态；S2、接收查看方手机端上传的手机状态获取请求，根据所述请求中包含的所要查询的手机号码调取相应的手机状态发送至查看手机端上。本申请可使用户在拨打电话前就可以看到对方手机是否满足通话条件，从而避开诸如占线、关机等情况，避免做无用功，提高效率和用户体验。
Description
本申请申明享有2018年3月22日递交的申请号为201810240924.7、名称为“预知通话条件的方法、电子装置、终端设备及存储介质”的中国专利申请的优先权，该中国专利申请的整体内容以参考的方式结合在本申请中。
本申请涉及移动通信技术领域，涉及一种预知通话条件的方法、电子装置、终端设备及存储介质。
随着网络技术和手机技术的发展，手机已经成为人们工作生活中必不可少的沟通工具，通过拨打电话可以随时随地联系到对方，与之进行通话。
然而，也会碰到对方正在通话，即占线状态，无法接通的情况，当碰到这种场景的时候，只能挂断电话，待对方通话结束后再行拨打。对方什么时候通话结束是不可知的，一方只能隔一段时间后再做尝试，若通过未结束再继续等待。这种一遍遍的“试探”，效率低下，体验也不好，为双方的沟通带来障碍。
发明内容
本申请要解决的技术问题是为了克服现有技术中因无法预知对方是满足通话条件而产生试探性拨打的问题，提出了一种预知通话条件的方法、电子装置、终端设备及存储介质，通过监测记录手机的状态，使得拨打方能在打电话前得知对方手机是否满足通话条件，避免无效的试探性拨打。
本申请是通过下述技术方案来解决上述技术问题：
一种预知通话条件的方法，包括以下步骤：
S1、接收手机端上传的本机号码和相关联的手机状态，并根据所述手机状态判断所述手机端是否处于无通讯网络或停机两种异常状态，所述手机状态包括通过监听实时获取的开机、关机、开始通话和结束通话四种状态；
S2、接收查看手机端上传的手机状态获取请求，根据所述请求中包含的所要查询的手机号码调取相应的手机状态发送至查看手机端上。
一种电子装置，所述电子装置上存储有预知通话条件的系统，所述预知通话条件的系统包括：
状态接收模块，用于接收手机端上传的本机号码和相关联的手机状态，所述手机状态包括通过监听实时获取的开机、关机、开始通话和结束通话四种状态；
异常判断模块，用于根据所述手机状态判断所述手机端是否处于无通讯网络或停机两种异常状态；
请求接收模块，用于接收查看方手机端上传的手机状态获取请求；
状态查询发送模块，用于根据所述请求调取所要查询的手机状态发送至查看手机端上。
一种终端设备，包括存储器和处理器，其特征在于，所述存储器上存储有可被所述处理器执行的预知通话条件的系统，所述系统被所述处理器执行时实现以下步骤的操作：
S1、接收手机端上传的本机号码和相关联的手机状态，并根据所述手机状态判断所述手机端是否处于无通讯网络或停机两种异常状态，所述手机状态包括通过监听实时获取的开机、关机、开始通话和结束通话四种状态；
S2、接收查看手机端上传的手机状态获取请求，根据所述请求中包含的所要查询的手机号码调取相应的手机状态发送至查看手机端上。
一种计算机可读存储介质，所述计算机可读存储介质内存储有预知通话条件的系统，所述预知通话条件的系统可被至少一个处理器所执行，以使所述至少一个处理器执行以下步骤的操作：
S1、接收手机端上传的本机号码和相关联的手机状态，并根据所述手机状态判断所述手机端是否处于无通讯网络或停机两种异常状态，所述手机状态包括通过监听实时获取的开机、关机、开始通话和结束通话四种状态；
S2、接收查看手机端上传的手机状态获取请求，根据所述请求中包含的所要查询的手机号码调取相应的手机状态发送至查看手机端上。
本申请的积极进步效果在于：用户在拨打电话前，就可以看到对方手机是否满足通话条件，从而避开诸如占线、关机等情况，避免做无用功，提高效率和用户体验。
图1示出了本申请预知通话条件的方法实施例一的流程图；
图2示出了本申请预知通话条件的方法实施例二的流程图；
图3示出了本申请预知通话条件的方法实施例三的流程图；
图4示出了本申请预知通话条件的方法实施例四的流程图；
图5示出了本申请预知通话条件的方法实施例五的流程图；
图6示出了本申请电子装置中预知通话条件的系统第一实施例的程序模块示意图；
图7示出了本申请终端设备一实施例的硬件架构示意图。
下面通过实施例的方式进一步说明本申请，但并不因此将本申请限制在所述的实施例范围之中。
首先，本申请提出一种预知通话条件的方法。
在实施例一中，如图1所示，所述的预知通话条件的方法包括如下步骤：
S1、接收手机端上传的本机号码和相关联的手机状态(优选为按上传时 间顺序保存，类似于堆栈)，并根据所述手机状态判断所述手机端是否处于无通讯网络或停机两种状态；所述手机状态包括通过监听实时获取的开机、关机、开始通话和结束通话四种状态。
本方法仅针对装有特定软件程序的手机端，这些手机端根据安装的程序向一个或多个指定服务器上传相关联的手机状态和手机号码。
此外，手机端还需要安装有监听程序。
在常规状态下，手机端按预设的时间间隔定时上传相关联的手机状态和手机号码。
开机、关机、开始通话和结束通话这四种状态是通过监听即时上传的，即只要一发现有这四种状态种任意一种状态的变化，就将变化后的手机状态上传给服务器。
无通讯网络和停机这两种为异常状态，分别由服务器根据手机端上传的手机状态和对该手机通话音的监听经过逻辑判断之后得出的。
服务器保存相关联的手机状态和手机号码的格式可参考下表：
| 号码 | 状态 | 上传时间 |
| 13912341234 | 关机 | 2017-11-30 12：00 |
| 13812341234 | 开机 | 2017-11-30 12：00 |
| 13712341234 | 正常待机 | 2017-11-30 12：00 |
| … | … | … |
S2、接收查看手机端上传的手机状态获取请求，根据所述请求调取所要查询的手机状态发送至查看手机端上。
本方法中，服务器接收到各手机端上传的手机状态和手机号码后不会主动下发至那些通讯录中包含有这些手机号码的相应手机端上，而是经由需要使用这项功能的手机端(即查看手机端)主动发起请求以获取相关手机号码对应的手机状态。
所述发送至查看手机端上的手机状态为相对应的手机端最后一次上传 的手机状态，即该手机端最新的手机状态。
当手机状态发送至查看手机端上后，可以对应查看手机端的通讯录中的联系人进行显示，具体显示在联系人的详细信息页。但由于查找号码并不一定需要通过通讯录进行查找，因此优选还可以显示在与该联系人的通话页上，以便用户及时得知对方的手机状态。
本实施例中，用户在拨打电话前就可以看到对方手机是否满足通话条件，从而避开诸如占线、关机等情况，避免做无用功，提高效率和用户体验。
在实施例二中，基于实施例一的基础上，如图2所示，所述无通讯网络的异常判断包括以下步骤：
S111、判断手机端最后一次上传的手机状态是否为无通讯网络，若否则执行S112，若是则循环执行S111；
S112、判断手机端最后一次上传的手机状态是否为停机，若否则执行S113，若是则执行S111；
S113、计算手机端最后一次上传时间至当前时刻的末次更新间隔；
S114、判断末次更新间隔是否超过预设的间隔阈值，若是则执行S115，若否则执行S111；
S115、将手机端的手机状态识别为无通讯网络与该手机端的手机号码关联保存，并将上传时间更新为当前时刻。
下面以判断手机一是否为无通讯网络状态为例，做具体说明：
1、假设手机一在常规状态下，每5分钟上传一次手机状态，服务器中保存有该手机一的状态更新状况如下表所示：
| 号码 | 状态 | 上传时间 |
| … | … | … |
| 13912341234 | 开机 | 2017-11-30 12：00 |
| 13912341234 | 正常待机 | 2017-11-30 12：05 |
| 13912341234 | 开始通话 | 2017-11-30 12：07 |
| 13912341234 | 正常待机 | 2017-11-30 12：10 |
| 13912341234 | 结束通话 | 2017-11-30 12：12 |
| 13912341234 | 正常待机 | 2017-11-30 12：15 |
2、服务器在12:20获取到该手机一最后一次手机状态为正常待机，而上传时间为2017-11-30 12:15；
3、服务器计算得到末次更新间隔为5分钟，假设预设的间隔阈值为8分钟，则此时的末次更新间隔还没超过8分钟，因此继续重复判断步骤；
4、服务器在12:25再次获取到该手机一最后一次手机状态为正常待机，而上传时间仍然为2017-11-30 12:15；
5、服务器计算得到末次更新间隔为10分钟，此时的末次更新间隔超过了8分钟，因此判断该手机一处于无通讯网络状态，将该无通讯网络状态与手机一的手机号码关联保存如下表：
| 号码 | 状态 | 上传时间 |
| … | … | … |
| 13912341234 | 正常待机 | 2017-11-30 12：15 |
| 13912341234 | 无通讯网络 | 2017-11-30 12：25 |
在实施例三中，基于实施例二的基础上，如图3所示，所述停机的异常判断包括以下步骤：
S121、监听手机端被呼叫时播放的音效；
S122、判断所述音效是否与预存的停机音一致，若是执行S123；
当一方拨通电话号码与另一方通话时，在接通过程中会播放提示音，比如表示连接中的“嘟嘟”长音，表示对方在通话中的“嘟嘟”短音，表示停机的“您拨打的电话已停机”等，这里所述停机音即为最后一种。这里所述几种方式仅为示例。
S123、将手机端的手机状态识别为无通讯网络与该手机端的手机号码关联保存，并将上传时间更新为当前时刻。
接上例，以判断手机一是否为停机状态为例，做具体说明：
1、假设服务器中记录手机一的当前状态为无通讯网络，而之后在13:00有一用户试图拨打手机一，服务器监听到通话连接过程中播放的声音为“您拨打的电话已停机”；
2、服务器判断该声音与预存的停机音一致，判断手机一为停机状态；
3、服务器将停机状态与手机一的手机号码关联保存如下表：
| 号码 | 状态 | 上传时间 |
| … | … | … |
| 13912341234 | 无通讯网络 | 2017-11-30 12：35 |
| 13912341234 | 停机 | 2017-11-30 13：00 |
在实施例四中，基于实施例一的基础上，如图4所示，当所述手机状态获取请求为获取通讯录中的所有联系人的手机状态时，所述S2包括以下步骤：
S211、接收查看手机端上传的手机状态获取请求。
具体地，由于是请求获取通讯录中的所有联系人的手机状态，因而该请求中仅包含其本机的号码，而不包含所要查询的对方手机的号码。
S212、向所述查看手机端发送通讯录获取请求。
S213、接收所述查看手机端上传的通讯录。
具体地，查看手机端根据服务器的通讯录获取请求，将本机中的通讯录进行打包上传。
S214、将所述通讯录中的手机号码与保存的手机号码进行一一比对，找出相同的手机号码。
具体地，手机通讯录中保存的联系人的联系方式包括手机号码、固定电 话号码、邮箱等，而且并不是一个手机通讯录中所有联系人使用的手机端都是将其手机状态上传至服务器保存的，因此本步骤需要找出那些将手机状态上传至服务器的手机端的手机号码。
S215、将保存的与所述相同的手机号码相关联的最新的手机状态发送至查看手机端上。
具体地，将查询到的最新的手机状态发送至查看手机端上，而没查询到的可以跳过，也可以发送无结果或者为空等类似意思的手机状态至查看手机端上，
本实施例中，当某一手机用户需要获取通讯录中的所有联系人的手机状态时，其发送的请求中仅包含其本机的号码，而不包含所要查询的对方手机的号码，以此来区分该用户需要获取通讯录中的所有联系人的手机状态。
本实施例，可以使得用户一次直接获取到其通讯录中所有联系人的手机状态，特别适用于在短时间内需要联系多人的情况。
在实施例五中，基于实施例一的基础上，如图5所示，当所述手机状态获取请求为获取单个联系人的手机状态时，所述手机状态获取请求中包含有该单个联系人的手机号码，所述S2包括以下步骤：
S221、接收查看手机端上传的手机状态获取请求；
具体地，所述手机状态获取请求中包含有查看手机端的本机号码，还包含有所要查看的单个联系人的手机端的手机号码，请求中包含的上述信息按约定的规则进行排列。
S222、截取所述手机状态获取请求中包含的所述单个联系人的手机号码。
具体地，截取请求中特定位置的信息，即为所述单个联系人的手机号码。
S223、判断保存的手机号码中是否具有与所述单个联系人的手机号码相同的手机号码，若是则执行S224，若否则直接结束；
S224、将保存的与所述相同的手机号码相关联的手机状态发送至查看手机端上。
具体地，由于请求中包含有查看手机端的本机号码，因而在查询到结果后，服务器可以对应将该查询到的结果反馈给查看手机端。
本实施例可以使得用户根据其每次的特定通话对象查看对方的手机状态，相比查询整个通讯录的方式速度更快。
其次，本申请提出了一种电子装置，这种电子装置可以是一种服务器，所述电子装置上存储有预知通话条件的系统20，所述系统20可以被分割为一个或者多个程序模块。
例如，图4示出了所述预知通话条件的系统20第一实施例的程序模块示意图，该实施例中，所述系统20可以被分割为状态接收模块201、异常判断模块202、请求接收模块203和状态查询发送模块204。其中，本申请所称的程序模块是指能够完成特定功能的一系列计算机程序指令。以下描述将具体介绍所述程序模块201-204的具体功能。
所述状态接收模块201用于接收手机端上传的本机号码和相关联的手机状态，所述手机状态包括通过监听实时获取的开机、关机、开始通话和结束通话四种状态。
所述异常判断模块202用于根据所述手机状态判断所述手机端是否处于无通讯网络或停机两种异常状态。
所述请求接收模块203用于接收查看方手机端上传的手机状态获取请求。
所述状态查询发送模块204用于根据所述请求调取所要查询的手机状态发送至查看手机端上。
这里所述发送至查看手机端上的手机状态为相对应的手机端最后一次上传的手机状态，即该手机端最新的手机状态。
一、下面以手机二的用户请求查看手机一的手机状态为例，做具体说明：
1、电子装置在2017-11-30 12：35更新了手机一的手机状态为无通讯网络；
2、手机二的用户在2017-11-30 12：38发送了查看手机一的手机状态的请求，电子装置通过比对将手机一的无通讯网络状态发送至手机二上。
二、下面以手机二的用户请求查看其通讯录中所有联系人的手机状态为例，做具体说明：
假设手机二的通讯录中有8个联系人的手机端具备上传手机状态的功能。
1、手机二向电子装置发送获取其通讯录中所有联系人的手机状态的请求；
2、电子装置接收到手机二上传的通讯录后，通过与其现有保存的手机号码比对得知，仅有8个手机号码与通讯录的手机号码相同；
3、电子装置将与相同的8个手机号码关联保存的最后一次上传的手机状态发送至手机二上。
再次，本申请还提出来一种终端设备。
参阅图6所示，是本申请终端设备一实施例的硬件架构示意图。本实施例中，所述终端设备2是一种能够按照事先设定或者存储的指令，自动进行数值计算和/或信息处理的设备。例如，可以是智能手机、平板电脑、笔记本电脑、台式计算机、机架式服务器、刀片式服务器、塔式服务器或机柜式服务器(包括独立的服务器，或者多个服务器所组成的服务器集群)等。如图所示，所述终端设备2至少包括，但不限于，可通过系统总线相互通信连接存储器21、处理器22、网络接口23、以及预知通话条件的系统20。其中：
所述存储器21至少包括一种类型的计算机可读存储介质，所述可读存储介质包括闪存、硬盘、多媒体卡、卡型存储器(例如，SD或DX存储器 等)、随机访问存储器(RAM)、静态随机访问存储器(SRAM)、只读存储器(ROM)、电可擦除可编程只读存储器(EEPROM)、可编程只读存储器(PROM)、磁性存储器、磁盘、光盘等。在一些实施例中，所述存储器21可以是所述终端设备2的内部存储单元，例如该终端设备2的硬盘或内存。在另一些实施例中，所述存储器21也可以是所述终端设备2的外部存储设备，例如该终端设备2上配备的插接式硬盘，智能存储卡(Smart Media Card,SMC)，安全数字(Secure Digital,SD)卡，闪存卡(Flash Card)等。当然，所述存储器21还可以既包括所述终端设备2的内部存储单元也包括其外部存储设备。本实施例中，所述存储器21通常用于存储安装于所述终端设备2的操作系统和各类应用软件，例如所述预知通话条件的系统20的程序代码等。此外，所述存储器21还可以用于暂时地存储已经输出或者将要输出的各类数据。
所述处理器22在一些实施例中可以是中央处理器(Central Processing Unit，CPU)、控制器、微控制器、微处理器、或其他数据处理芯片。该处理器22通常用于控制所述终端设备2的总体操作，例如执行与所述终端设备2进行数据交互或者通信相关的控制和处理等。本实施例中，所述处理器22用于运行所述存储器21中存储的程序代码或者处理数据，例如运行所述的预知通话条件的系统20等。
所述网络接口23可包括无线网络接口或有线网络接口，该网络接口23通常用于在所述终端设备2与其他终端设备之间建立通信连接。例如，所述网络接口23用于通过网络将所述终端设备2与外部终端相连，在所述终端设备2与外部终端之间的建立数据传输通道和通信连接等。所述网络可以是企业内部网(Intranet)、互联网(Internet)、全球移动通讯系统(Global System of Mobile communication，GSM)、宽带码分多址(Wideband Code Division Multiple Access，WCDMA)、4G网络、5G网络、蓝牙(Bluetooth)、Wi-Fi等无线或有线网络。
需要指出的是，图5仅示出了具有组件21-23的终端设备2，但是应理解的是，并不要求实施所有示出的组件，可以替代的实施更多或者更少的组件。
在本实施例中，存储于存储器21中的所述预知通话条件的系统20可以被一个或多个处理器(本实施例为处理器22)所执行，以完成上述预知通话条件的方法的操作。
此外，本申请一种计算机可读存储介质，该计算机可读存储介质内存储有预知通话条件的系统20，该预知通话条件的系统20可被一个或多个处理器执行时，实现上述预知通话条件的方法或电子装置的操作。
虽然以上描述了本申请的具体实施方式，但是本领域的技术人员应当理解，这仅是举例说明，本申请的保护范围是由所附权利要求书限定的。本领域的技术人员在不背离本申请的原理和实质的前提下，可以对这些实施方式做出多种变更或修改，但这些变更和修改均落入本申请的保护范围。
Claims (20)
- 一种预知通话条件的方法，其特征在于，包括以下步骤：S1、接收手机端上传的本机号码和相关联的手机状态，并根据所述手机状态判断所述手机端是否处于无通讯网络或停机两种异常状态，所述手机状态包括通过监听实时获取的开机、关机、开始通话和结束通话四种状态；S2、接收查看手机端上传的手机状态获取请求，根据所述请求中包含的所要查询的手机号码调取相应的手机状态发送至查看手机端上。
- 根据权利要求1所述的预知通话条件的方法，其特征在于，S1中的所述手机端安装有监听程序，所述手机端按预设的时间间隔定时上传手机状态和手机号码，当监听到手机发生开机、关机、开始通话和结束通话四种状态中的任意一种状态变化时，即时将相应的手机状态上传；所述本机号码和相关联的手机状态按上传时间顺序保存。
- 根据权利要求2所述的预知通话条件的方法，其特征在于，所述无通讯网络的异常判断包括以下步骤：S111、判断手机端最后一次上传的手机状态是否为无通讯网络，若否则执行S112，若是则循环执行S111；S112、判断手机端最后一次上传的手机状态是否为停机，若否则执行S113，若是则执行S111；S113、计算手机端最后一次上传时间至当前时刻的末次更新间隔；S114、判断末次更新间隔是否超过预设的间隔阈值，若是则执行S115，若否则执行S111；S115、将手机端的手机状态识别为无通讯网络与该手机端的手机号码关联保存，并将上传时间更新为当前时刻。
- 根据权利要求3所述的预知通话条件的方法，其特征在于，所述停机的异常判断包括以下步骤：S121、监听手机端被呼叫时播放的音效；S122、判断所述音效是否与预存的停机音一致，若是执行S123；S123、将手机端的手机状态识别为无通讯网络与该手机端的手机号码关联保存，并将上传时间更新为当前时刻。
- 根据权利要求1所述的预知通话条件的方法，其特征在于，当所述手机状态获取请求为获取通讯录中的所有联系人的手机状态时，所述S2包括以下步骤：S211、接收查看手机端上传的手机状态获取请求；S212、向所述查看手机端发送通讯录获取请求；S213、接收所述查看手机端上传的通讯录；S214、将所述通讯录中的手机号码与保存的手机号码进行一一比对，找出相同的手机号码；S215、将保存的与所述相同的手机号码相关联的最新的手机状态发送至查看手机端上。
- 根据权利要求1所述的预知通话条件的方法，其特征在于，当所述手机状态获取请求为获取单个联系人的手机状态时，所述手机状态获取请求中包含有该单个联系人的手机号码，所述S2包括以下步骤：S221、接收查看手机端上传的手机状态获取请求；S222、截取所述手机状态获取请求中包含的所述单个联系人的手机号码；S223、判断保存的手机号码中是否具有与所述单个联系人的手机号码相同的手机号码，若是则执行S224，若否则直接结束；S224、将保存的与所述相同的手机号码相关联的手机状态发送至查看手机端上。
- 根据权利要求1-6中任一项所述的预知通话条件的方法，其特征在于，所述手机状态对应该手机端的通讯录中的联系人显示在相应的联系人的 详细信息页和/或呼叫页上。
- 一种电子装置，其特征在于，所述电子装置上存储有预知通话条件的系统，所述预知通话条件的系统包括：状态接收模块，用于接收手机端上传的本机号码和相关联的手机状态，所述手机状态包括通过监听实时获取的开机、关机、开始通话和结束通话四种状态；异常判断模块，用于根据所述手机状态判断所述手机端是否处于无通讯网络或停机两种异常状态；请求接收模块，用于接收查看方手机端上传的手机状态获取请求；状态查询发送模块，用于根据所述请求调取所要查询的手机状态发送至查看手机端上。
- 一种终端设备，包括存储器和处理器，其特征在于，所述存储器上存储有可被所述处理器执行的预知通话条件的系统，所述系统被所述处理器执行时实现以下步骤的操作：S1、接收手机端上传的本机号码和相关联的手机状态，并根据所述手机状态判断所述手机端是否处于无通讯网络或停机两种异常状态，所述手机状态包括通过监听实时获取的开机、关机、开始通话和结束通话四种状态；S2、接收查看手机端上传的手机状态获取请求，根据所述请求中包含的所要查询的手机号码调取相应的手机状态发送至查看手机端上。
- 根据权利要求9所述的终端设备，其特征在于，S1中的所述手机端安装有监听程序，所述手机端按预设的时间间隔定时上传手机状态和手机号码，当监听到手机发生开机、关机、开始通话和结束通话四种状态中的任意一种状态变化时，即时将相应的手机状态上传；所述本机号码和相关联的手机状态按上传时间顺序保存；所述无通讯网络的异常判断包括以下步骤：S111、判断手机端最后一次上传的手机状态是否为无通讯网络，若否则 执行S112，若是则循环执行S111；S112、判断手机端最后一次上传的手机状态是否为停机，若否则执行S113，若是则执行S111；S113、计算手机端最后一次上传时间至当前时刻的末次更新间隔；S114、判断末次更新间隔是否超过预设的间隔阈值，若是则执行S115，若否则执行S111；S115、将手机端的手机状态识别为无通讯网络与该手机端的手机号码关联保存，并将上传时间更新为当前时刻。
- 根据权利要求10所述的终端设备，其特征在于，所述停机的异常判断包括以下步骤：S121、监听手机端被呼叫时播放的音效；S122、判断所述音效是否与预存的停机音一致，若是执行S123；S123、将手机端的手机状态识别为无通讯网络与该手机端的手机号码关联保存，并将上传时间更新为当前时刻。
- 根据权利要求9所述的终端设备，其特征在于，当所述手机状态获取请求为获取通讯录中的所有联系人的手机状态时，所述S2包括以下步骤：S211、接收查看手机端上传的手机状态获取请求；S212、向所述查看手机端发送通讯录获取请求；S213、接收所述查看手机端上传的通讯录；S214、将所述通讯录中的手机号码与保存的手机号码进行一一比对，找出相同的手机号码；S215、将保存的与所述相同的手机号码相关联的最新的手机状态发送至查看手机端上。
- 根据权利要求9所述的终端设备，其特征在于，当所述手机状态获取请求为获取单个联系人的手机状态时，所述手机状态获取请求中包含有该单个联系人的手机号码，所述S2包括以下步骤：S221、接收查看手机端上传的手机状态获取请求；S222、截取所述手机状态获取请求中包含的所述单个联系人的手机号码；S223、判断保存的手机号码中是否具有与所述单个联系人的手机号码相同的手机号码，若是则执行S224，若否则直接结束；S224、将保存的与所述相同的手机号码相关联的手机状态发送至查看手机端上。
- 根据权利要求9-13中任一项所述的终端设备，其特征在于，所述手机状态对应该手机端的通讯录中的联系人显示在相应的联系人的详细信息页和/或呼叫页上。
- 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质内存储有预知通话条件的系统，所述预知通话条件的系统可被至少一个处理器所执行，以使所述至少一个处理器执行以下步骤的操作：S1、接收手机端上传的本机号码和相关联的手机状态，并根据所述手机状态判断所述手机端是否处于无通讯网络或停机两种异常状态，所述手机状态包括通过监听实时获取的开机、关机、开始通话和结束通话四种状态；S2、接收查看手机端上传的手机状态获取请求，根据所述请求中包含的所要查询的手机号码调取相应的手机状态发送至查看手机端上。
- 根据权利要求15所述的计算机可读存储介质，其特征在于，S1中的所述手机端安装有监听程序，所述手机端按预设的时间间隔定时上传手机状态和手机号码，当监听到手机发生开机、关机、开始通话和结束通话四种状态中的任意一种状态变化时，即时将相应的手机状态上传；所述本机号码和相关联的手机状态按上传时间顺序保存；所述无通讯网络的异常判断包括以下步骤：S111、判断手机端最后一次上传的手机状态是否为无通讯网络，若否则执行S112，若是则循环执行S111；S112、判断手机端最后一次上传的手机状态是否为停机，若否则执行S113，若是则执行S111；S113、计算手机端最后一次上传时间至当前时刻的末次更新间隔；S114、判断末次更新间隔是否超过预设的间隔阈值，若是则执行S115，若否则执行S111；S115、将手机端的手机状态识别为无通讯网络与该手机端的手机号码关联保存，并将上传时间更新为当前时刻。
- 根据权利要求16所述的计算机可读存储介质，其特征在于，所述停机的异常判断包括以下步骤：S121、监听手机端被呼叫时播放的音效；S122、判断所述音效是否与预存的停机音一致，若是执行S123；S123、将手机端的手机状态识别为无通讯网络与该手机端的手机号码关联保存，并将上传时间更新为当前时刻。
- 根据权利要求15所述的计算机可读存储介质，其特征在于，当所述手机状态获取请求为获取通讯录中的所有联系人的手机状态时，所述S2包括以下步骤：S211、接收查看手机端上传的手机状态获取请求；S212、向所述查看手机端发送通讯录获取请求；S213、接收所述查看手机端上传的通讯录；S214、将所述通讯录中的手机号码与保存的手机号码进行一一比对，找出相同的手机号码；S215、将保存的与所述相同的手机号码相关联的最新的手机状态发送至查看手机端上。
- 根据权利要求15所述的计算机可读存储介质，其特征在于，当所述手机状态获取请求为获取单个联系人的手机状态时，所述手机状态获取请求中包含有该单个联系人的手机号码，所述S2包括以下步骤：S221、接收查看手机端上传的手机状态获取请求；S222、截取所述手机状态获取请求中包含的所述单个联系人的手机号码；S223、判断保存的手机号码中是否具有与所述单个联系人的手机号码相同的手机号码，若是则执行S224，若否则直接结束；S224、将保存的与所述相同的手机号码相关联的手机状态发送至查看手机端上。
- 根据权利要求15-19中任一项所述的计算机可读存储介质，其特征在于，所述手机状态对应该手机端的通讯录中的联系人显示在相应的联系人的详细信息页和/或呼叫页上。
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810240924.7A CN108551522A (zh) | 2018-03-22 | 2018-03-22 | 预知通话条件的方法、电子装置、终端设备及存储介质 |
| CN201810240924.7 | 2018-03-22 |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| WO2019178985A1 true WO2019178985A1 (zh) | 2019-09-26 |
Family
ID=63516751
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| PCT/CN2018/095355 WO2019178985A1 (zh) | 2018-03-22 | 2018-07-12 | 预知通话条件的方法、电子装置、终端设备及存储介质 |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN108551522A (zh) |
| WO (1) | WO2019178985A1 (zh) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112422750A (zh) * | 2019-08-22 | 2021-02-26 | 中兴通讯股份有限公司 | 获取终端状态的方法、终端、系统及计算机可读存储介质 |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102307242A (zh) * | 2011-09-27 | 2012-01-04 | 杨维全 | 一种跨社交网络平台的通讯录的实现方法及系统 |
| CN102340599A (zh) * | 2011-10-26 | 2012-02-01 | 中兴通讯股份有限公司 | 终端通话时的处理方法、终端以及处理系统 |
| CN102892094A (zh) * | 2011-07-19 | 2013-01-23 | 米特尔网络公司 | 用于确定移动设备之间的网络关系的系统和方法 |
| CN103647883A (zh) * | 2013-12-04 | 2014-03-19 | 惠州Tcl移动通信有限公司 | 一种共享手机状态信息的方法及系统 |
| CN104394273A (zh) * | 2014-11-21 | 2015-03-04 | 深圳市中兴移动通信有限公司 | 一种联系人显示方法、装置及终端 |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8995965B1 (en) * | 2010-03-25 | 2015-03-31 | Whatsapp Inc. | Synthetic communication network method and system |
| CN101909102B (zh) * | 2010-07-22 | 2014-05-07 | 宇龙计算机通信科技(深圳)有限公司 | 一种清理联系人信息的方法、装置及通信终端 |
| CN103188654A (zh) * | 2011-12-27 | 2013-07-03 | 富泰华工业（深圳）有限公司 | 更新手机状态的系统及装置 |
| CN106027736B (zh) * | 2016-05-18 | 2020-03-20 | 珠海市魅族科技有限公司 | 通讯录的标记方法和装置 |
-
2018
- 2018-03-22 CN CN201810240924.7A patent/CN108551522A/zh active Pending
- 2018-07-12 WO PCT/CN2018/095355 patent/WO2019178985A1/zh active Application Filing
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102892094A (zh) * | 2011-07-19 | 2013-01-23 | 米特尔网络公司 | 用于确定移动设备之间的网络关系的系统和方法 |
| CN102307242A (zh) * | 2011-09-27 | 2012-01-04 | 杨维全 | 一种跨社交网络平台的通讯录的实现方法及系统 |
| CN102340599A (zh) * | 2011-10-26 | 2012-02-01 | 中兴通讯股份有限公司 | 终端通话时的处理方法、终端以及处理系统 |
| CN103647883A (zh) * | 2013-12-04 | 2014-03-19 | 惠州Tcl移动通信有限公司 | 一种共享手机状态信息的方法及系统 |
| CN104394273A (zh) * | 2014-11-21 | 2015-03-04 | 深圳市中兴移动通信有限公司 | 一种联系人显示方法、装置及终端 |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108551522A (zh) | 2018-09-18 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8885565B2 (en) | Mixed off-site/on-site prediction computation for reducing wireless reconnection time of a computing device | |
| US9942839B2 (en) | Reducing wireless reconnection time of a computing device | |
| CN104038908B (zh) | 发送推送消息的方法和装置 | |
| EP2122929B1 (en) | Network oriented control system for self-configuration and self-optimization measurements | |
| US9552199B2 (en) | Method and apparatus of prompting an update of an application | |
| CN109032805A (zh) | 一种弹性扩缩容方法、装置、服务器及存储介质 | |
| CN111050378B (zh) | 网络搜索方法、装置及电子设备 | |
| US9872148B2 (en) | Adaptive mobile wireless call rescue | |
| WO2019227623A1 (zh) | 呼叫平台的数据处理方法、装置、设备及存储介质 | |
| WO2019178985A1 (zh) | 预知通话条件的方法、电子装置、终端设备及存储介质 | |
| CN112737975A (zh) | 缓冲区容量调整方法及装置 | |
| WO2018126884A1 (zh) | 一种终端设备的节电方法及终端设备 | |
| US20160057615A1 (en) | Transfer of status information concerning a mobile device via a cloud based service | |
| CN109639490B (zh) | 一种宕机通知方法及装置 | |
| CN106604244B (zh) | 一种对通知消息进行提示的方法和装置 | |
| US11943127B2 (en) | Network-based control method for power consumption of applications, terminal and storage medium | |
| CN110753308B (zh) | 定位设备及用于定位设备的方法 | |
| CN112804301A (zh) | 设备状态的确定方法、装置、网关及存储介质 | |
| US10966104B2 (en) | Email synchronization method and device | |
| CN114024878A (zh) | 数据传输方法、装置、介质和设备 | |
| CN108763601B (zh) | 一种在双内核浏览器中自动切换的控制方法及控制装置 | |
| CN112118420A (zh) | 一种监控系统自动配置方法及装置 | |
| WO2018228343A1 (zh) | 道路救援方法及应用服务器 | |
| CN110809265A (zh) | 一种基于移动终端的后台管理方法和装置 | |
| EP4220398A1 (en) | Method and apparatus for keeping client alive, and electronic device and storage medium |
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: 18911068 Country of ref document: EP Kind code of ref document: A1 |
|
| NENP | Non-entry into the national phase |
Ref country code: DE |
|
| 32PN | Ep: public notification in the ep bulletin as address of the adressee cannot be established |
Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 12/01/2021) |
|
| 122 | Ep: pct application non-entry in european phase |
Ref document number: 18911068 Country of ref document: EP Kind code of ref document: A1 |