WO2019000738A1 - 一号多终端的来电管理方法、装置、被管理设备及服务器 - Google Patents

一号多终端的来电管理方法、装置、被管理设备及服务器 Download PDF

Info

Publication number
WO2019000738A1
WO2019000738A1 PCT/CN2017/107715 CN2017107715W WO2019000738A1 WO 2019000738 A1 WO2019000738 A1 WO 2019000738A1 CN 2017107715 W CN2017107715 W CN 2017107715W WO 2019000738 A1 WO2019000738 A1 WO 2019000738A1
Authority
WO
WIPO (PCT)
Prior art keywords
incoming call
managed
identifier
management
managed device
Prior art date
Application number
PCT/CN2017/107715
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 华为技术有限公司
Priority to EP17916138.5A priority Critical patent/EP3637947B1/en
Priority to CN201780012820.4A priority patent/CN108702422B/zh
Priority to US16/624,133 priority patent/US10841422B2/en
Publication of WO2019000738A1 publication Critical patent/WO2019000738A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M3/00—Automatic or semi-automatic exchanges
    • H04M3/42—Systems providing special services or facilities to subscribers
    • H04M3/436—Arrangements for screening incoming calls, i.e. evaluating the characteristics of a call before deciding whether to answer it
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M1/00—Substation equipment, e.g. for use by subscribers
    • H04M1/57—Arrangements for indicating or recording the number of the calling subscriber at the called subscriber's set
    • H04M1/575—Means for retrieving and displaying personal data about calling party
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M19/00—Current supply arrangements for telephone systems
    • H04M19/02—Current supply arrangements for telephone systems providing ringing current or supervisory tones, e.g. dialling tone or busy tone
    • H04M19/04—Current supply arrangements for telephone systems providing ringing current or supervisory tones, e.g. dialling tone or busy tone the ringing-current being generated at the substations
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M3/00—Automatic or semi-automatic exchanges
    • H04M3/42—Systems providing special services or facilities to subscribers
    • H04M3/42025—Calling or Called party identification service
    • H04M3/42034—Calling party identification service
    • H04M3/42059—Making use of the calling party identifier
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M3/00—Automatic or semi-automatic exchanges
    • H04M3/42—Systems providing special services or facilities to subscribers
    • H04M3/42136—Administration or customisation of services
    • H04M3/42153—Administration or customisation of services by subscriber
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M3/00—Automatic or semi-automatic exchanges
    • H04M3/42—Systems providing special services or facilities to subscribers
    • H04M3/42136—Administration or customisation of services
    • H04M3/4217—Managing service interactions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M3/00—Automatic or semi-automatic exchanges
    • H04M3/42—Systems providing special services or facilities to subscribers
    • H04M3/42229—Personal communication services, i.e. services related to one subscriber independent of his terminal and/or location
    • H04M3/42246—Personal communication services, i.e. services related to one subscriber independent of his terminal and/or location where the subscriber uses a multi-mode terminal which moves and accesses different networks with at least one network having a wireline access including cordless PBX
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M3/00—Automatic or semi-automatic exchanges
    • H04M3/42—Systems providing special services or facilities to subscribers
    • H04M3/42229—Personal communication services, i.e. services related to one subscriber independent of his terminal and/or location
    • H04M3/42263—Personal communication services, i.e. services related to one subscriber independent of his terminal and/or location where the same subscriber uses different terminals, i.e. nomadism
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M3/00—Automatic or semi-automatic exchanges
    • H04M3/42—Systems providing special services or facilities to subscribers
    • H04M3/46—Arrangements for calling a number of substations in a predetermined sequence until an answer is obtained
    • H04M3/465—Arrangements for simultaneously calling a number of substations until an answer is obtained
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/60—Subscription-based services using application servers or record carriers, e.g. SIM application toolkits
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
    • H04W8/183—Processing at user equipment or user record carrier
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/26—Network addressing or numbering for mobility support
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/18—Service support devices; Network management devices
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M2203/00—Aspects of automatic or semi-automatic exchanges
    • H04M2203/20—Aspects of automatic or semi-automatic exchanges related to features of supplementary services
    • H04M2203/2005—Temporarily overriding a service configuration
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices
    • H04W88/06—Terminal devices adapted for operation in multiple networks or having at least two operational modes, e.g. multi-mode terminals

Definitions

  • the present invention relates to the field of e-embedded Subscriber Identity Module (eSIM) technology, and in particular, to a multi-sim call management method and apparatus.
  • eSIM e-embedded Subscriber Identity Module
  • the multi-terminal referred to in the multi-terminal service No. 1 can be regarded as multiple International Mobile Subscriber Identification Numbers (IMSIs) but have the same mobile station integrated service digital network number (Mobile Subscriber International ISDN/PSTN). Number, MSISDN) Multiple terminals.
  • IMSIs International Mobile Subscriber Identification Numbers
  • MSISDN Mobile Subscriber International ISDN/PSTN
  • the above-mentioned multi-terminal usually includes a management device and at least one managed device, wherein the management device can implement the first-number multi-terminal service for each managed device, and in order to implement the multi-terminal service No. 1, it needs to be in the eSIM of the managed device.
  • both the management device and the managed device can receive the incoming call, that is, the management device and the managed device.
  • the device will ring at the same time.
  • the user can only connect the phone through one terminal of the multi-terminal, that is, the terminal that first responds to the incoming call event acts as the called terminal, and establishes a call with the calling terminal.
  • the management device and the managed device are in different use scopes of the user, if the user needs to complete the establishment of the call through the management device, but the management device is managed or managed.
  • the establishment of a call with the calling terminal can be achieved as long as the incoming call is preferentially connected.
  • the user cannot complete the establishment of the call with the calling terminal through the management device, that is, the telephone is misconnected.
  • the embodiment of the invention provides a caller management method, device, managed device and server for the No. 1 multi-terminal, which can solve the problem of telephone misconnection.
  • the embodiment of the present invention provides the following solutions:
  • an embodiment of the present invention provides a method for managing an incoming call of a multiple terminal.
  • the method includes: the managed device parses the incoming call, obtains the incoming call information, and then determines the communication subunit corresponding to the called identifier. If the managed device has performed an incoming call screening setting for the communication subunit in response to the remote management command sent by the remote management server ES, the incoming call event is not responded.
  • the remote management server is responsible for providing the opening and remote management functions of the No. 1 multi-terminal service. It should be noted that for the managed device, the communication is performed once.
  • the caller information includes a called identifier that points to the configuration file; the communication subunit is configured to implement a communication function corresponding to the configuration file on the managed device, the communication function includes at least receiving an incoming call directed to the configuration file; and the remote management command includes the managed The ID of the managed profile in the device.
  • the management device carried by the user through the priority response to the incoming call event by the managed device cannot complete the establishment of the call with the calling terminal, thereby causing the phone to be misconnected.
  • the management device is used as the initiator of the management operation to initiate a request message to the managed device through the ES, and then the incoming call screening setting is completed by the managed device.
  • the managed device performs a masking operation on the incoming call that satisfies the shielding condition, so that the user cannot perceive the incoming call event, so that the user can only The incoming call event is handled by the management device.
  • the incoming call screening setting implemented by the embodiment of the present invention is only for the incoming call whose called number is the specified number, and does not affect the communication of the user on the data service, the calling service or other services.
  • the management device and the managed device are called 133XXXXXXX.
  • the user dials 133XXXXXXX through the calling terminal, and the incoming call is managed. The device will not be responded.
  • the implementation manner in which the managed device does not respond to the incoming call may be automatic shielding or the incoming call may not be received at the managed device side.
  • the device may determine whether it has passed the wear authentication by means of detection or the like, and further, the device may also determine whether it is in a motion state. Afterwards, the device can feed back the detection result to other devices that are associated with the device. The other device can determine which device is the management device and which device is the device by comparing the status of the device with the received detection result of the device. The managed device, after which the determination result of the device identity is fed back to the device.
  • at least two devices that have an association relationship can perform corresponding functions according to their own identity, for example, a device that confirms its identity as a management device, and can implement management of other managed devices to perform call-to-call screening settings, and confirm identity.
  • the incoming call screening setting can be implemented by catering to the remote management command initiated by the management device.
  • the device may pre-store the distinguishing condition between the management device and the managed device, and then determine the priority condition of the other device by determining which condition is met by the device, and receiving the condition that the other device sends the other device, and then determining the priority of the other device and the device. Which device is the management device, which device or device is the managed device, and the identity of each device is notified, and the management device manages the managed device to complete the incoming call screening setting. It should be noted that the manner for determining the identity of the management device and the managed device is not limited to the above-mentioned examples, and may also include other methods for distinguishing the management priorities, which are not limited herein.
  • the managed device before the managed device does not respond to the incoming call event, the managed device receives the remote management command sent by the ES, and determines the communication subunit corresponding to the identifier of the managed configuration file, and then responds to the remote management.
  • the instruction performs an incoming call screening setting on the communication subunit corresponding to the identifier of the managed configuration file. It can be seen that if the user attempts to block all incoming calls to be processed by the communication sub-unit corresponding to the identifier of the managed configuration file, the shielding setting needs to be performed in advance according to the remote management command sent by the ES.
  • the managed device performs an incoming call screening setting on the communication subunit corresponding to the identifier of the managed configuration file, including: the managed device uses the incoming call filtering technology, for example, an incoming call under the Android system.
  • the call screening service performs the incoming call screening setting of the communication subunit corresponding to the identifier of the managed configuration file; or the managed device sets an empty incoming call for the communication subunit corresponding to the identifier of the managed configuration file.
  • the incoming call screening setting is to add a designated identifier to the communication subunit, so that when an incoming call is made, the communication is made.
  • the subunit detects that it has the specified identity and does not respond to the incoming call event.
  • not responding to an incoming call event includes rejecting an incoming call event or ignoring an incoming call event. That is to say, the result of the masking operation implemented in the embodiment of the present invention is that the managed device does not respond to the incoming call.
  • the called identity includes one of a Temporary Mobile Subscriber Identity (TMSI), an International Mobile Subscriber Identity (IMSI), and a Mobile Station Integrated Services Digital Network Number (MSISDN).
  • TMSI Temporary Mobile Subscriber Identity
  • IMSI International Mobile Subscriber Identity
  • MSISDN Mobile Station Integrated Services Digital Network Number
  • the managed device determines the communication subunit corresponding to the called identifier, if the communication subunit does not perform the incoming call screening setting, the managed device prompts the user to respond to the incoming call event. That is, the incoming call is processed according to the current normal incoming call processing flow.
  • an embodiment of the present invention provides a method for managing an incoming call of a multiple terminal.
  • the method includes: establishing a connection between the management device and the managed device; determining that the management device is in a motion state when the management device determines that the connection is disconnected; and managing the managed device to block the incoming call if the management device is in a motion state.
  • the management device if the management device is in a motion state, the management device manages the managed device to block the incoming call, including: if the management device is in a motion state, and the motion state remains for a preset duration, the management device manages the managed device Block incoming calls.
  • the default management device and the managed device already know whether they have the identity of management or management.
  • the device can also identify its identity by means of query, for example, the user can manage the device and be managed.
  • a management relationship is established between devices, which device is set as the management device, and which device or devices are the managed devices. In this way, when the management device confirms that the connection with the managed device is disconnected and the management device is in a motion state, the managed device is directly triggered to perform the incoming call screening setting.
  • the management device manages the managed device to block the incoming call, including: the management device sends a remote management command to the managed device, the remote management command includes an identifier of the managed configuration file of the managed device; and the managed device receives Remotely managing the instructions and determining a communication sub-unit corresponding to the identity of the managed configuration file; the managed device performs an incoming call screening setting on the communication sub-unit in response to the remote management instruction.
  • the method includes: the managed device parses the incoming call, and obtains the incoming call information, where the incoming call information includes the called identifier; if the managed device has performed the pair The incoming call screening setting of the communication subunit corresponding to the called identifier does not respond to the incoming call event; the management device resolves the incoming call to obtain the incoming call information; if the management device has not performed the incoming call screening of the communication subunit corresponding to the called identifier Set to respond to incoming call events.
  • an embodiment of the present invention provides a method for managing an incoming call of a multiple terminal.
  • the method includes: the server receives the remote management instruction sent by the remote management server ES, and deletes or freezes the routing information corresponding to the identifier of the managed configuration file in response to the remote management instruction, so that the routing information of the managed device cannot be found, There will be no calls to the managed device, and there will be no call misconnections at the managed device.
  • the routing information is used to address the called party, and the remote management command includes an identifier of the managed configuration file in the managed device.
  • the server cannot find the routing information that has been deleted after receiving the routing query request, which means that the server cannot feed back the routing information that has been deleted.
  • the communication service server may ensure that the managed device cannot perceive the incoming call of the phone because the routing information of the managed device is frozen after the calling terminal initiates the call by temporarily freezing the routing information.
  • the server manages the configuration file for the target, and supplements the call restriction for the managed configuration file, that is, restricts the managed service as the called service when the called device is called.
  • the above two exemplary implementations may eventually result in the inability to query the routing information of the managed device in the communication network, and also because there is only management in the communication network after the calling terminal initiates the call.
  • the routing information corresponding to the device so there is no case where the call is responded to on the managed device.
  • the server after the server deletes or freezes the routing information corresponding to the identifier in response to the remote management instruction, the server receives the routing query request, and in response to the routing query request, queries the corresponding identifier of the frozen identifier. If the routing information is used, the server does not feed back the routing information corresponding to the frozen identifier.
  • an embodiment of the present invention provides a method for managing an incoming call of a multiple terminal.
  • the method includes: establishing a connection between the management device and the managed device; determining, when the management device determines that the connection is disconnected, determining whether the management device is in a motion state; and if the management device is in a motion state, the management device management server masking the incoming call.
  • the management device management server shields the incoming call, including: if the management device is in a motion state, and the motion state remains for a preset duration, the management device management server shields the incoming call.
  • the management device management server shields the incoming call, including: the management device sends a remote management command to the server, the remote management command includes an identifier of the managed configuration file of the managed device; the server receives the remote management command, and responds The remote management command deletes or freezes the routing information corresponding to the identifier, so that the communication subunit corresponding to the identifier in the managed device cannot respond to the incoming call event.
  • the method includes: the management device parses the incoming call, obtains the incoming call information, and the incoming call information includes the called identifier; if the management device does not perform the corresponding corresponding to the called identifier The incoming call screening setting of the communication subunit responds to the incoming call event; if the managed device has performed the incoming call screening setting for the communication subunit corresponding to the called identity, the incoming call event is not responded.
  • an embodiment of the present invention provides a No. 1 multi-terminal call management device.
  • the device is applied to the managed device, and the functions implemented in the foregoing method embodiments may be implemented.
  • the functions may be implemented by using hardware or by executing corresponding software through hardware.
  • the hardware or software includes one or more modules corresponding to the above functions.
  • an embodiment of the present invention provides a No. 1 multi-terminal call management device.
  • the device is applied to a server, and the functions implemented in the foregoing method embodiments may be implemented.
  • the functions may be implemented by using hardware or by executing corresponding software through hardware.
  • the hardware or software includes one or more modules corresponding to the above functions.
  • an embodiment of the present invention provides a managed device.
  • the structure of the managed device includes a processor and a transceiver configured to support the managed device to perform a corresponding function in the above method.
  • the transceiver is used to support communication between the managed device and other devices such as servers.
  • the managed device can also include a memory for coupling with the processor that holds the program instructions and data necessary for the managed device.
  • an embodiment of the present invention provides a server.
  • the structure of the server includes a processor and a communication interface configured to support the server to perform the corresponding functions of the above methods.
  • the communication interface is used to support communication between the server and other devices, such as managed devices.
  • the server can also include a memory for coupling with the processor that holds the program instructions and data necessary for the server.
  • an embodiment of the present invention provides a No. 1 multi-terminal call management system.
  • the system includes: the management device sends a remote management instruction to the managed device through the remote management server ES, and then receives the remote management instruction by the management device, and determines a communication subunit corresponding to the identifier of the managed configuration file, and responds to the remote management
  • the instruction performs an incoming call screening setting on the communication subunit corresponding to the identifier of the managed configuration file.
  • the remote management instruction includes an identifier of the managed configuration file in the managed device. Subsequently, when the managed device receives the incoming call, the incoming call is parsed, and the incoming call information is obtained. If the managed device has performed the incoming call screening setting of the communication subunit corresponding to the called identifier in the incoming call information, the incoming call is not responded. event.
  • the system further includes: the management device parses the incoming call, and obtains the incoming call information, and responds to the incoming call event if the management device has not performed the incoming call screening setting of the communication subunit corresponding to the called identifier.
  • an embodiment of the present invention provides a No. 1 multi-terminal call management system.
  • the system includes: the management device sends a remote management instruction to the server through the remote management server ES, and then the server receives the remote management instruction, deletes or freezes the routing information corresponding to the identifier, so that the communication subunit corresponding to the identifier in the managed device cannot respond Incoming call event.
  • the remote management command includes an identifier of the managed configuration file of the managed device.
  • the system further includes: the management device parses the incoming call, and obtains the incoming call information, and if the management device does not perform the incoming call screening setting of the communication subunit corresponding to the called identifier in the incoming call information, the response Incoming call event.
  • an embodiment of the present invention provides a computer program product, the computer program product comprising software code for performing any one of the foregoing first and second aspects and various possible designs thereof. method.
  • the embodiment of the present invention provides a computer program product, the computer program product comprising software code for performing the third aspect, the fourth aspect, and any of the various possible designs described above. method.
  • an embodiment of the present invention provides a computer storage medium, including instructions.
  • the instruction When the instruction is run on an electronic device, the electronic device is caused to perform the method of any of the first, second aspects, and various possible designs thereof.
  • an embodiment of the present invention provides a computer storage medium, including instructions.
  • the instruction When the instruction is run on an electronic device, the electronic device is caused to perform the method of any of the above-described third, fourth aspects, and various possible designs thereof.
  • FIG. 1 is a schematic structural diagram of a terminal according to an embodiment of the present disclosure
  • FIG. 2 is a schematic structural diagram of a communication network system according to an embodiment of the present invention.
  • FIG. 3 is a schematic diagram of a process for an MSC to obtain routing information according to an embodiment of the present disclosure
  • FIG. 4 is a flowchart of a method for managing an incoming call of a multiple terminal according to an embodiment of the present invention
  • FIG. 5 is a flowchart of another method for managing an incoming call of a multiple terminal according to an embodiment of the present invention.
  • FIG. 6 is an interaction diagram of an incoming call management method for a multiple terminal according to an embodiment of the present invention.
  • FIG. 7 is an interaction diagram of another caller management method for a multi-terminal terminal according to an embodiment of the present invention.
  • FIG. 8 is a flowchart of another method for managing an incoming call of a multiple terminal according to an embodiment of the present invention.
  • FIG. 9 is a schematic diagram of another process for an MSC to obtain routing information according to an embodiment of the present disclosure.
  • FIG. 10 is an interaction diagram of another caller management method for a multi-terminal of the first embodiment according to an embodiment of the present invention.
  • FIG. 11 is an interaction diagram of another caller management method for a multi-terminal terminal according to an embodiment of the present invention.
  • FIG. 12 is an interaction diagram of another caller management method for a multi-terminal terminal according to an embodiment of the present invention.
  • FIG. 13 is a schematic diagram of an application scenario for managing a mobile phone by a wearable device according to an embodiment of the present disclosure
  • FIG. 14 is a schematic diagram of an application scenario of a mobile phone management watch and a tablet computer according to an embodiment of the present invention.
  • FIG. 15 is a schematic structural diagram of an incoming call management apparatus of a multiple terminal according to an embodiment of the present disclosure
  • FIG. 16 is a schematic structural diagram of a managed device according to an embodiment of the present disclosure.
  • FIG. 17 is a schematic structural diagram of another caller management device of a multi-terminal terminal according to an embodiment of the present invention.
  • FIG. 18 is a schematic structural diagram of a server according to an embodiment of the present disclosure.
  • FIG. 19 is a schematic structural diagram of a No. 1 multi-terminal call management system according to an embodiment of the present invention.
  • FIG. 20 is a schematic structural diagram of another No. 1 multi-terminal call management system according to an embodiment of the present invention.
  • the embodiment of the present invention is applicable to the application scenario of the number one terminal, that is, based on the eSIM technology, two or more terminals can share the same number, that is, the MSISDNs of the multiple terminals are the same, that is, the telephone numbers are the same.
  • the configuration file corresponding to the same number may be different on different terminals. For example, the information such as the IMSI and the key may be different. In essence, the configuration file corresponding to the same number on different terminals is used.
  • the service of the contracted carrier is the same. For example, the service traffic of the data traffic and the duration of the call service are the same, and are shared among the terminals.
  • the multi-terminal in the multi-terminal No. 1 includes a management device and a managed device.
  • the management device can not only open the number one terminal service for each managed device, but also manage other terminals, for example, the shielding setting of the incoming call event mentioned later in the embodiment of the present invention.
  • a terminal that the user desires to complete the call establishment with the calling terminal is regarded as a management device, and a terminal that has the same MSISDN and different IMSI as the management device is regarded as a managed device.
  • the management device may be a portable mobile phone, and the managed device may be a tablet PC (Tablet PC) that is not convenient to carry.
  • Tablet PC Tablet PC
  • the user places the managed device in the home for the family to use, and the user carries the management device to go out, if there is an incoming call, it is likely that the family will first pick up the tablet through the home, and this will make the caller
  • the call is established between the terminal and the tablet as the managed device. This means that the user cannot answer the call through the mobile phone that he carries.
  • the management device can be a watch worn by the user, and the managed device can be a mobile phone.
  • the managed device can be a mobile phone.
  • the user When the user is out of the door, it is very likely that the watch is only worn and the phone is placed at home. If there is an incoming call, because the user is exercising, it may not be able to notice the incoming call information on the watch in time, and the family is mistakenly connected by the mobile phone, so that the call is established between the mobile phone placed at home and the calling terminal. This means that the user cannot answer the call through the watch that he wears.
  • the management device may be a portable mobile phone, and the managed device may be an in-vehicle device.
  • the managed device may be an in-vehicle device.
  • the managed configuration file can be deactivated on the managed device, for example, the profile is set to an unusable state (disable state) to ensure that the user cannot pass the call after the calling terminal initiates the call.
  • the management device answers the call. Since the configuration file is a must-have element for communication, deactivating the configuration file means that all services are unusable, which means that other communication problems can also arise, for example, the managed device is deactivated due to the deactivated managed configuration file.
  • the data function cannot be used normally, and it cannot be used as a calling terminal to initiate a call to other terminals.
  • the embodiment of the present invention provides a caller management method for the number one terminal to implement the server on the managed device or the network side.
  • the ability of the managed device to respond to incoming calls is limited, that is, the ability of the managed device to respond to incoming calls is managed.
  • the server may be a Home Location Register (HLR) or a Home Subscriber Server (HSS) server for implementing communication services.
  • HLR Home Location Register
  • HSS Home Subscriber Server
  • the embodiment of the present invention can be used for a terminal, and the terminal can be a management device or a managed device, and the terminal can include a notebook computer, a smart phone, or a wristband.
  • the terminal is provided with at least a display screen, an input device and a processor.
  • the terminal 100 includes a processor 101, a memory 102, a camera 103, an RF circuit 104, an audio circuit 105, and a speaker.
  • 106 a microphone 107, an input device 108, other input devices 109, a display screen 110, a touch panel 111, a display panel 112, an output device 113, and a power source 114.
  • the display screen 110 is composed of at least a touch panel 111 as an input device and a display panel 112 as an output device. It should be noted that the terminal structure shown in FIG. 1 does not constitute a limitation on the terminal, and may include more or less components than those illustrated, or combine some components, or split some components, or different. The component arrangement is not limited herein.
  • the components of the terminal 100 will be specifically described below with reference to FIG. 1 :
  • the radio frequency (RF) circuit 104 can be used for receiving and transmitting information during the transmission or reception of information or during a call. For example, if the terminal 100 is a mobile phone, the terminal 100 can receive the downlink information sent by the base station through the RF circuit 104. Thereafter, it is transmitted to the processor 101 for processing; in addition, data related to the uplink is transmitted to the base station.
  • RF circuits include, but are not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a Low Noise Amplifier (LNA), a duplexer, and the like.
  • LNA Low Noise Amplifier
  • RF circuitry 104 can also communicate with the network and other devices via wireless communication.
  • the wireless communication can use any communication standard or protocol, including but not limited to Global System of Mobile communication (GSM), General Packet Radio Service (GPRS), Code Division Multiple Access (Code Division). Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Long Term Evolution (LTE), E-mail, Short Messaging Service (SMS), and the like.
  • GSM Global System of Mobile communication
  • GPRS General Packet Radio Service
  • CDMA Code Division Multiple Access
  • WCDMA Wideband Code Division Multiple Access
  • LTE Long Term Evolution
  • E-mail Short Messaging Service
  • the memory 102 can be used to store software programs and modules, and the processor 101 is stored in the memory 101 by running. Software programs and modules to perform various functional applications and data processing of the terminal 100.
  • the memory 101 may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application required for at least one function (for example, a sound playing function, an image playing function, etc.); and the storage data area may be Data (such as audio data, video data, etc.) created in accordance with the use of the terminal 100 is stored.
  • the memory 101 may include a high speed random access memory, and may also include a nonvolatile memory such as at least one magnetic disk storage device, flash memory device, or other volatile solid state storage device.
  • Other input devices 109 can be used to receive input numeric or character information, as well as to generate key signal inputs related to user settings and function control of terminal 100.
  • other input devices 109 may include, but are not limited to, a physical keyboard, function keys (eg, volume control buttons, switch buttons, etc.), trackballs, mice, joysticks, light rats (light mice are touches that do not display visual output)
  • function keys eg, volume control buttons, switch buttons, etc.
  • trackballs mice
  • mice joysticks
  • light rats light mice are touches that do not display visual output
  • One or more of a sensitive surface, or an extension of a touch sensitive surface formed by a touch screen may also include sensors built into the terminal 100, such as gravity sensors, acceleration sensors, etc., and the terminal 100 may also use parameters detected by the sensors as input data.
  • the display screen 110 can be used to display information input by the user or information provided to the user as well as various menus of the terminal 100, and can also accept user input.
  • the display panel 112 can be configured in the form of a liquid crystal display (LCD), an organic light-emitting diode (OLED), or the like.
  • the touch panel 111 is also called a touch screen or a touch sensitive screen.
  • the contact or non-contact operation of the user on or near the user may be collected (for example, the user may use any suitable object or accessory such as a finger or a stylus on the touch panel 111 or in the vicinity of the touch panel 111, or Including the somatosensory operation; the operation includes a single point control operation, a multi-point control operation and the like, and drives the corresponding connection device according to a preset program.
  • the touch panel 111 may further include two parts: a touch detection device and a touch controller.
  • the touch detection device detects the touch orientation and posture of the user, and detects a signal brought by the touch operation, and transmits a signal to the touch controller; the touch controller receives the touch information from the touch detection device, and converts the signal into the processor 101.
  • the information that can be processed is transmitted to the processor 101, and the commands sent from the processor 101 can also be received and executed.
  • the touch panel 111 can be implemented by using various types such as resistive, capacitive, infrared, and surface acoustic waves, and the touch panel 111 can be implemented by any technology developed in the future.
  • the touch panel 111 can cover the display panel 112, and the user can cover the display panel 112 according to the content displayed by the display panel 112 (including but not limited to a soft keyboard, a virtual mouse, a virtual button, an icon, etc.).
  • the touch panel 111 operates on or near the touch panel 111. After detecting the operation thereon or nearby, the touch panel 111 transmits to the processor 101 to determine the user input, and then the processor 101 provides the display panel 112 according to the user input. Corresponding visual output.
  • the touch panel 111 and the display panel 112 are used as two independent components to implement the input and output functions of the terminal 100 in FIG. 1, in some embodiments, the touch panel 111 may be integrated with the display panel 112. To implement the input and output functions of the terminal 100.
  • the RF circuit 104, the speaker 106, and the microphone 107 provide an audio interface between the user and the terminal 100.
  • the audio circuit 105 can transmit the converted audio data to the speaker 106 for conversion to the sound signal output.
  • the microphone 107 can convert the collected sound signal into a signal, which is received by the audio circuit 105.
  • the audio data is then converted to audio data, and the audio data is output to the RF circuit 104 for transmission to a device such as another terminal, or the audio data is output to the memory 102 for the processor 101 to perform further processing in conjunction with the content stored in the memory 102.
  • the camera 103 can acquire image frames in real time and transmit them to
  • the processor 101 processes and stores the processed results to the memory 102 and/or presents the processed results to the user via the display panel 112.
  • the processor 101 is the control center of the terminal 100, connecting various portions of the entire terminal 100 using various interfaces and lines, by running or executing software programs and/or modules stored in the memory 102, and recalling data stored in the memory 102.
  • the various functions and processing data of the terminal 100 are executed to perform overall monitoring of the terminal 100.
  • the processor 101 can also implement management of the communication subunit, for example, configuring the communication subunit.
  • the processor 101 may include one or more processing units; the processor 101 may further integrate an application processor and a modem processor, wherein the application processor mainly processes an operating system, a user interface (User Interface, UI) And the application, etc., the modem processor mainly handles wireless communication. It can be understood that the above modem processor may not be integrated into the processor 101.
  • the terminal 100 may further include a power source 114 (for example, a battery) for supplying power to the respective components.
  • a power source 114 for example, a battery
  • the power source 114 may be logically connected to the processor 101 through the power management system, thereby managing charging, discharging, and the like through the power management system. And power consumption and other functions.
  • the terminal 100 may further include a Bluetooth module, a Near Field Communication (NFC) module, and a Wireless-Fidelity (Wi-Fi) module. , global positioning system (GPS) module, speaker, accelerometer, gyroscope, etc., will not be described here.
  • the Bluetooth module can be used for establishing a Bluetooth connection and communicating with other Bluetooth-enabled devices within a certain distance (within the distance specified by the Bluetooth protocol);
  • the NFC module can be used for establishing an NFC connection between the mobile phone and other devices supporting NFC communication. And communicating with each other; the terminal 100 can establish a Wi-Fi connection and perform data transmission through the Wi-Fi module.
  • the management device and the managed device can be implemented as the terminal shown in FIG. 1 .
  • the management device is the mobile phone and the managed device is the in-vehicle device.
  • the calling terminal initiates a call by visiting a Visited Mobile-services Switching Centre (VMSC) or a Gateway Mobile Switching Center (GMSC), and then the Mobile Network Operator (MNO) from the provider HLR.
  • VMSC Visited Mobile-services Switching Centre
  • GMSC Gateway Mobile Switching Center
  • MNO Mobile Network Operator
  • the routing information of the management device and the managed device is obtained in the vendor HSS, and the initiating mode is used to initiate an incoming call to the device corresponding to multiple routing information according to the acquired routing information.
  • the implementation process of obtaining the routing information by the Mobile Switching Center (MSC) is shown in FIG. 3 .
  • the HLR/HSS database can be set in the above-mentioned vendor HLR.
  • the MSC initiates a query request for the called routing information to the HLR/HSS, and then searches for multiple routing information corresponding to the MSISDN, such as routing information 1 and routing information 2, from the HLR/HSS database.
  • the routing information 1 is routing information corresponding to the management device IMSI1
  • the routing information 2 is routing information corresponding to the managed device IMSI2.
  • the HLR/HSS then feeds back routing information 1 and routing information 2 to the MSC.
  • An embodiment of the present invention provides a method for managing an incoming call of a multi-terminal terminal. As shown in FIG. 4, the method includes at least steps 201 to 203. In the embodiment of the present invention, step 204 may also be included.
  • Step 201 The managed device parses the incoming call to obtain the incoming call information.
  • the caller information includes the called identity.
  • the called identifier may include, but is not limited to, one of a Temporary Mobile Subscriber Identity (TMSI), an IMSI, and an MSISDN.
  • TMSI Temporary Mobile Subscriber Identity
  • IMSI IMSI
  • MSISDN MSISDN
  • the managed device After the managed device receives the incoming call, the managed device directly blocks the incoming call that meets the screening condition.
  • the shielding condition is that the communication subunit corresponding to the configuration file pointed by the called identifier performs the incoming call screening setting.
  • the managed device itself can sense the incoming call of the calling terminal, but does not remind the user to answer the call through voice, display, etc. after sensing the incoming call, that is, from the user's perception. From the perspective, the user has no perception of incoming calls that satisfy the screening conditions.
  • Step 202 The managed device determines a communication subunit corresponding to the called identifier.
  • the communication subunit is configured to implement a communication function corresponding to the configuration file on the managed device, and the communication function includes at least receiving an incoming call directed to the configuration file.
  • Step 203 If the managed device has performed the incoming call screening setting for the communication subunit in response to the remote management command sent by the remote management server (ES), the incoming call event is not responded.
  • the remote management instruction includes an identifier of the managed configuration file in the managed device; the non-responding incoming call event includes: rejecting the incoming call event or ignoring the incoming call event.
  • the managed device determines whether the incoming call screening setting needs to be performed on the corresponding communication subunit according to the managed configuration file identifier carried in the management instruction.
  • the subsequent received incoming call determines whether the incoming call meets the screening condition to determine whether a response is required, that is, if the called identifier included in the subsequently received incoming call event corresponds to the managed profile identifier, the managed device can determine not to Respond to the incoming call event.
  • the remote management command may also carry the management service identifier, so that the managed device triggers the incoming call screening setting after receiving the remote management command and identifying the management service identifier, where the management service identifier is used for
  • the remote management command is an instruction for triggering an incoming call screening setting for a communication subunit corresponding to the specified profile.
  • the managed device may verify the validity of the management instruction, and after the management instruction passes the verification, that is, after confirming that the management instruction is executable, the managed device responds according to the identifier of the managed configuration file.
  • the communication sub-unit performs an incoming call screening setting, that is, masking sets the incoming call to the managed profile.
  • Step 204 If the communication subunit does not perform the incoming call screening setting, the managed device prompts the user to respond to the incoming call event.
  • the device may determine whether it has passed the wear authentication by means of detection or the like, and further, the device may also determine whether it is in a motion state. Afterwards, the device can feed back the detection result to other devices that are associated with the device. The other device can determine which device is the management device and which device is the device by comparing the status of the device with the received detection result of the device. The managed device, after which the determination result of the device identity is fed back to the device.
  • at least two devices that have an association relationship can perform corresponding functions according to their own identity, for example, a device that confirms its identity as a management device, and can implement management of other managed devices to perform call-to-call screening settings, and confirm identity.
  • the incoming call screening setting can be implemented by catering to the remote management command initiated by the management device.
  • the device may pre-store the distinguishing condition between the management device and the managed device, and then determine the priority condition of the other device by determining which condition is met by the device, and receiving the condition that the other device sends the other device, and then determining the priority of the other device and the device. Which device is the management device, which device or device is the managed device, and the identity of each device is notified, and the management device manages the managed device to complete the incoming call screening setting.
  • the manner for determining the identity of the management device and the managed device is not limited to the above-exemplified cases, and may also include other methods for distinguishing management priorities, for example, the user may also pre-predict according to his own behavior.
  • the preset conditions for distinguishing the identity of the device are set first, and the specific content of the preset condition is not limited herein.
  • the purpose of setting the preset condition is to determine from the at least two devices associated with each other a management device for managing other devices, and at the same time, to determine the managed device managed by the management device.
  • the peer device determines to issue the management according to the managed device parameter carried by the management command.
  • the commanded device is the managed device, and the peer device is determined as the management device according to the peer device parameter, and the peer device performs the incoming call screening setting on the managed device, and returns a response to the managed device. It can be seen that the execution process of the incoming call screening setting can be triggered not only by the two parties through interaction, but also by the form of unilaterally requesting.
  • the device can send remote management commands carrying the device parameters to other peer devices through the ES.
  • the other peer device determines the identity of the peer device according to the device parameter carried by the remote management command and the device parameter of the peer device that receives the remote management command. If the peer device determines that the peer device is the managed device, the peer device responds to the remote management command, that is, the peer device performs the incoming call screening setting and sends a response message to the peer device. If the peer device determines that the peer device should be the management device at this time, it does not respond to the remote management command. Optionally, the peer device is used as the management device to initiate a remote management process for the device.
  • the identity query/confirmation request is sent to the ES, and the ES acquires the state of each device at this time, and judges the identity of each device, and then returns the judgment result of each device separately.
  • each device can only receive its own judgment result, and cooperate with other devices to perform the incoming call screening setting according to the identity indicated by the judgment result.
  • each device can also receive the judgment result of each device, and then clear The identity of oneself and the identity of one or more other devices associated with itself, and complete the incoming call screening settings.
  • the priority of the terminal to answer the call may be set in advance in the terminal, so that the terminal subsequently determines the identity of the device with other terminals through the form of data interaction.
  • the priority of the answering phone can be set to be higher in the mobile phone than in the mobile state and in the wearable device, and higher than the other devices.
  • the management device is used as the initiator of the management operation to initiate a remote management command to the managed device through the ES, and then the managed device completes blocking the incoming call that satisfies the shielding condition. Settings. In this way, after the calling terminal initiates the call, since the managed device has completed the shielding setting, the user can only complete the answering of the call through the management device.
  • the masking operation implemented by the embodiment of the present invention is only for the called subscriber number to be a designated telephone, that is, it does not affect the communication of the user on the data service or other services, and is only performed for the service of the incoming call.
  • Selectively masked, and the incoming call referred to herein is an incoming call with the specified number as the called subscriber number.
  • the management device For example, in the actual use process of the management device and the managed device, if the management device and the managed device are in different use scopes of the user, if the user needs to complete the establishment of the call through the management device, then the management device is For the management device, after the incoming call screening setting is completed, only the management device can establish the call with the calling terminal. It should be noted that, for the managed device, only the incoming call event is not responded, but the service data or other services other than the incoming call event may also be executed.
  • step 301 and step 302 are further included.
  • Step 301 The managed device receives a remote management command sent by the ES.
  • Step 302 The managed device determines a communication subunit corresponding to the identifier of the managed configuration file, and performs an incoming call screening setting on the communication subunit corresponding to the identifier of the managed configuration file in response to the remote management instruction.
  • the inbound call screening setting of the communication subunit corresponding to the identifier of the managed configuration file by the managed device includes one of the following:
  • the managed device uses the incoming call filtering technology to perform an incoming call screening setting for the communication subunit corresponding to the identity of the managed configuration file.
  • the filtering software for implementing the incoming call filtering may be installed on the managed device, and the incoming call that needs to be filtered is pre-configured in the filtering software, that is, the input to the managed configuration file in the managed device.
  • Call events are blocked, and can also be implemented using the function/system service that filters incoming calls in the processing flow of incoming call events provided by the operating system, such as the call screening service provided by Android. The result of this function is to enable the communication subunit to not respond to incoming call events. If the managed device receives the incoming call and the incoming call meets the preset shielding requirement, the incoming call screening operation is implemented.
  • the managed device can also be configured with an incoming call filtering function, which means that the managed device itself implements a partial or full incoming call screening operation without installing any filtering software.
  • the managed device sets an empty incoming call whitelist for the communication sub-unit corresponding to the identifier of the managed configuration file to block the call initiated by the MSISDN that is not in the incoming call whitelist as the calling number.
  • the incoming call whitelist is used to record the calling number that the user is allowed to call in. For example, a user initiates an incoming call to the managed device, and the number of the incoming call used by the user is not recorded in the incoming call white list.
  • the managed device considers that the user does not have the right to initiate a call to the managed device, or the user of the managed device does not want to receive the incoming call of the user.
  • the communication subunit detects that the calling number of the user is not white. In the list, the incoming call event of the user is rejected or ignored.
  • the incoming call whitelist is set to empty, it means that no call is recorded in the incoming call whitelist, which means that any incoming call is regarded as a communicator that cannot be managed by the managed profile.
  • the status of the unit answering, or the user of the managed device does not want to hear any user's incoming call, so as to block the call initiated by the MSISDN that is not in the incoming call white list as the calling number.
  • the whitelist only includes the number 186XXXXXXX, only the number 186XXXXXXX can be entered as the calling number, and the incoming call event initiated by other numbers will be directly rejected or ignored. Therefore, setting an empty whitelist for a communication subunit means that all the calling numbers of the incoming calls directed to the managed configuration file are not in the whitelist, thereby implementing the incoming call screening of the communication subunit corresponding to the configuration file. Effect.
  • the managed device adds a designated identifier to the communication subunit corresponding to the identifier of the managed configuration file, so that after the communication subunit detects that the user has the specified identifier after receiving the incoming call event, the incoming call event is triggered.
  • the designation identifier is used to indicate that the management device has performed the incoming call screening setting for the communication subunit.
  • a status bit can be added to the communication subunit.
  • the status bit When the status bit is set to 0, it indicates that the communication subunit is subjected to the incoming call screening setting. Therefore, remote control commands are used to be managed
  • the status bit of the communication subunit corresponding to the file is set to "0".
  • the communication subunit checks that its status bit is "0" and does not respond to the incoming call.
  • the communication subunit that does not add the specified identifier still needs to perform the process of incoming call normally, and for the communication subunit to which the specified identifier is added, the communication subunit needs to implement the incoming call screening operation, that is, for each call. The incoming calls are not responding.
  • the shielding setting needs to be performed in advance according to the remote management command sent by the ES.
  • the above-mentioned exemplified shielding settings and the corresponding shielding operation means are only possible as a possible implementation manner, which is not limited herein.
  • the implementation process for the management device to initiate the incoming call screening setting through the ES includes steps 401 to 409.
  • Step 401 The management device sends a first request message to the ES.
  • the first request message is used to instruct the ES to send a second request message to the managed device; the second request message is used to instruct the managed device to perform an incoming call screening setting of the communication subunit pointing to the managed configuration file, that is, the mask pointing is The setting of the incoming call event of the management profile; the specified phone includes an incoming call event with the managed profile corresponding to the MSISDN as the called subscriber number.
  • the MSISDN is a possible identifier for the management configuration file.
  • the management configuration file may also use other existing or new information as the identifier for distinguishing different management configuration files, which is not limited herein.
  • the first request message carries at least the identifier of the managed device and the management service identifier, where the management service identifier is used as the identifier of the remote management service that needs to perform the mask setting, and the second request message carries at least the identifier of the managed configuration file.
  • management business identification that is, the above remote management instructions.
  • the first request message may be regarded as a management request message initiated by the management device to the ES, and may be sent by the management device's number one multi-terminal service management module to the ES to notify the ES, and the management device attempts to adjust The function of the managed device, that is, the implementation of some functions of the managed device.
  • Step 402 The ES receives the first request message sent by the management device.
  • the ES After receiving the first request message sent by the management device, the ES authenticates the management device, determines the identity of the management device, and finds the identifier of the managed configuration file corresponding to the identifier of the managed device, and then generates a second request message.
  • the second request message carries the identifier of the managed configuration file that is found, and the management service identifier carried in the first request message.
  • Step 403 The ES sends a second request message to the managed device.
  • Step 404 The managed device receives the second request message sent by the ES.
  • Step 405 The managed device performs an incoming call screening setting that points to the communication subunit of the managed configuration file.
  • the foregoing mask setting process may include: the managed device determines, according to the managed configuration file identifier in the second request message, a communication subunit corresponding to the managed configuration file identifier, and performs an incoming call screening setting on the communication subunit, and the specific event manner may be Refer to the description of steps 301 and 302.
  • Step 406 The managed device sends a response message to the ES.
  • the response message is used to indicate that the managed device has completed the incoming call screening setting.
  • Step 407 The ES receives the response message sent by the managed device.
  • Step 408 The ES sends a response message to the management device.
  • Step 409 The management device receives the response message sent by the ES.
  • the embodiment of the invention provides a method for managing the incoming call of the number one terminal. As shown in FIG. 7, the method includes steps 501 to 503. It should be noted that, in the initial state, if there is a portable terminal such as a smart phone among the at least two devices associated with each other, the portable terminal may be used as the management device by default, and the device having the associated relationship with the portable terminal is used as the Manage devices. That is, in addition to the preset conditions, the user can also directly set the management device and the managed device in the terminal, or the device can also learn its identity and the identity of other devices associated with itself through negotiation or query. For the specific implementation process, refer to the description below in step 204, and details are not described herein again.
  • Step 501 The management device establishes a connection with the managed device.
  • the connection may be a connection that is limited to the distance between the management device and the managed device, such as a Bluetooth pairing, or a connection established by accessing the same wireless network, and is not limited herein.
  • Step 502 When the management device determines that the connection is disconnected, it is determined whether the management device is in a motion state.
  • both the management device and the managed device can sense the device having a connection relationship with the managed device. Therefore, for the management device, if the managed device and the management device are connected, The method of disconnecting, the management device is identifiable, and the method for determining that the management device is disconnected from the managed device is a prior art, and details are not described herein.
  • the method for determining whether the device is in a state of motion can be detected by various sensors that are provided by the management device, and the method for determining whether the device is in a state of motion is a prior art, and is not described herein.
  • Step 503 If the management device is in a motion state, the management device manages the managed device to block the incoming call.
  • the management device is a watch and the managed device is a mobile phone
  • the mobile phone when the user wears the watch to go out and trash, usually because the time of going out is short, the mobile phone is placed at home, so that the watch as the management device and the managed device After the phone is far away, it will be disconnected.
  • the watch not only detects disconnection from the mobile phone, but also detects that the watch itself is in motion, and the watch can manage the mobile phone to block incoming calls. In this way, if an incoming call comes in, the user can directly answer the call through the watch, and the mobile phone located at home will not sense the incoming call.
  • the management device may further determine whether the duration of the motion state reaches a preset duration. If the management device is in the motion state and the motion state remains for a preset duration, the management device manages the managed device to block the incoming call.
  • the preset duration may be preset by the user or the device supplier according to the experience value, and the specific setting manner, the length of the preset duration, and the like are not limited herein.
  • the motion state of the management device is maintained for a preset duration, it may be determined that the management device is currently in use, thereby triggering a remote management process initiated by the management device.
  • identity verification mode of the management device and the managed device refer to the description below in step 204, and details are not described herein again.
  • the method for the management device to manage the incoming call by the management device may be the method in steps 401 to 409 in the foregoing embodiment, and details are not described herein.
  • the masking operation can be automatically cancelled by the corresponding remote management command.
  • the manner in which the management device re-establishes the connection with the managed device may include, but is not limited to, an implementation manner for establishing a connection between the device and the device, such as Bluetooth.
  • the embodiment of the invention provides a call management method for the number one terminal, as shown in FIG. Step 601 and step 602 are included. In the embodiment of the present invention, step 603 may also be included.
  • Step 601 The server receives a remote management command sent by the ES.
  • the remote management instruction includes an identifier of the managed configuration file in the managed device.
  • the server may comprise an HLR or an HSS.
  • Step 602 The server deletes or freezes the routing information corresponding to the identifier in response to the remote management instruction.
  • the managed device cannot sense the incoming call of the phone, and there is no misconnection.
  • the routing information corresponding to the above-mentioned freeze identifier can be regarded as temporary freezing, that is, when the user needs to restore the function of the managed device, the previous freezing of the routing information can be released, that is, the frozen routing information is restored.
  • the shielding setting may be implemented, and the supplementary service for automatically opening the call restriction for the managed configuration file on the managed device may be automatically responded to by the remote management command. , such as:
  • BAIC Barring of All Incoming Calls
  • the MSC obtains the implementation process of the routing information.
  • the MSC initiates a query request for the called routing information to the HLR/HSS, and then searches for multiple routing information corresponding to the MSISDN, such as routing information 1 and routing information 2, from the HLR/HSS database.
  • routing information 1 and routing information 2 are temporarily frozen.
  • the MSC can only obtain the routing information 1. In other words, the incoming call initiated by the calling terminal is only received by the management device, and the managed device cannot receive the call request.
  • Step 603 After receiving the route query request by the server, and querying the routing information corresponding to the frozen identifier in response to the route query request, the server does not feed back the routing information corresponding to the frozen identifier.
  • the identifier that has been frozen in step 603 refers to the managed profile identifier.
  • the server cannot find the routing information that has been deleted after receiving the routing query request, which means that the server cannot feed back the routing information that has been deleted.
  • the server may temporarily freeze the routing information or the server provides a call-restricted supplementary service for the managed device for the managed configuration file, ensuring that after the calling terminal initiates the call, due to the managed device The routing information is frozen so that the managed device cannot perceive incoming calls to the phone.
  • another implementation manner of the implementation process of the management device initiating the incoming call screening setting by the ES includes steps 701 to 705, and then selectively performs step 707 or step 707 according to actual conditions, and finally executes. Step 708 to step 711.
  • Step 701 The management device sends a first request message to the ES.
  • the first request message is used to instruct the ES to send a second request message to the server; the second request message is used to instruct the server to perform a call setting to block the designated phone as the called user.
  • the first request message carries at least the IMSI of the management device, the identifier of the managed device, and the management service identifier.
  • the second request message carries at least the identifier of the management device, the identifier of the managed device, and the management service identifier.
  • the first request message may be regarded as a management request message initiated by the management device to the ES, and may be sent by the management device's number one multi-terminal service management module to the ES to notify the ES, and the management device attempts to adjust The function of the managed device, that is, the implementation of some functions of the managed device.
  • Step 702 The ES receives the first request message sent by the management device.
  • the ES After receiving the first request message sent by the management device, the ES determines the managed profile identifier of the managed device according to the management device and the managed device identifier in the first request message.
  • the second request message is then generated according to the data format agreed with the server.
  • the second request message carries the identifier of the management device acquired by the ES, the identifier of the managed configuration file, and the management service identifier carried in the first request message.
  • Step 703 The ES sends a second request message to the server.
  • Step 704 The server receives the second request message sent by the ES.
  • the second request message may be regarded as a remote management command sent by the ES to the server, and the remote management command carries a managed profile identifier that needs to be managed.
  • the mask setting is performed.
  • Step 705 The server determines the incoming call service that the management device associates with the managed device.
  • step 705 After the step 705 is performed, step 706 or step 707 may be performed, and then step 708 is performed.
  • Step 706 The server temporarily freezes the call routing information corresponding to the IMSI of the managed configuration file in the incoming call service.
  • Step 707 The server opens a call restriction supplementary service for the managed configuration file of the managed device.
  • Step 708 The server sends a response message to the ES.
  • the response message is used to indicate that the server has completed the masking setting.
  • Step 709 The ES receives a response message sent by the server.
  • Step 710 The ES sends a response message to the management device.
  • Step 711 The management device receives the response message sent by the ES.
  • the steps 708 to 711 are similar to the steps 406 to 409, and may be referred to the foregoing description, and details are not described herein again.
  • the method flow shown in FIG. 11 is similar to the method flow shown in FIG. 10, except that the ES is used to forward the message to the server for the management device, and the operation flow for forwarding the message to the management device for the server.
  • the blocking operation is implemented by the message exchange between the management device and the server.
  • the method flow includes steps 801 to 805.
  • Step 801 The management device sends a first request message to the server.
  • Step 802 The server receives a first request message sent by the management device.
  • Step 803 The server performs shielding setting.
  • step 706 the process of implementing the mask setting by the server may refer to step 706 or step 707, and details are not described herein again.
  • Step 804 The server sends a response message to the management device.
  • Step 805 The management device receives a response message sent by the server.
  • the embodiment of the invention provides a method for managing the incoming call of the number one terminal. As shown in FIG. 12, the method includes steps 901 to 903. It should be noted that, in the initial state, if there is one of at least two devices associated with each other A portable terminal such as a smart phone may default to the portable terminal as a management device, and a device associated with the portable terminal as a managed device.
  • Step 901 The management device establishes a connection with the managed device.
  • Step 902 When the management device determines that the connection is disconnected, it is determined whether the management device is in a motion state.
  • Step 903 If the management device is in a motion state, the management device management server shields the incoming call.
  • the method for the management device management server to block the incoming call may be, for example, the method described in the foregoing steps 701 to 711, and may be the method from step 801 to step 805, and details are not described herein.
  • the wearable device can be carried by the mobile device. Therefore, the priority of answering the phone is high. device.
  • the wearable device can be a device such as a watch or a wristband that is convenient for the user to carry with him or her.
  • the wearable device is within the reachable range of the mobile phone, it is considered that the mobile phone and the wearable device are within the range operable by the user, that is, when there is an incoming call, the user can answer the call through the mobile phone or the wearable device, There will be a misconnection.
  • the wearable device is a device that meets the preset condition and is regarded as a management device, so that the wearable device is authenticated by the wearable device.
  • the incoming call event screening process of the managed configuration file is triggered to ensure that after the calling terminal initiates the call, the user can receive the call through the wearable device that is regarded as the management device. .
  • the mobile phone as the managed device is in a state where the call is not connected or is turned off, etc., it is not necessary to perform the problem that the currently managed device cannot cause the call to be misconnected because the call cannot be answered.
  • the operation flow of the shielded incoming call event provided by the embodiment of the present invention.
  • the wearable device as the management device is in a state where the call is not connected or is turned off, etc., it is considered that the user can only answer the call through the managed device at this time, and therefore, it is not necessary to trigger the above-mentioned shielding.
  • the operational flow of the call event is not necessary to trigger the above-mentioned shielding.
  • the wearable device can activate the eSIM and attach the network only after the wearable device is authenticated by wearing, in order to reduce the power consumption of the wearable device. Therefore, there are conditions for realizing the operational flow shown in the embodiment of the present invention. It is also because the wearable device that wears the authentication has higher portability, so that the authenticated wearable device can be configured with higher management authority, that is, the wearable device is the management device, and the others are wearable. A device that is associated with a device and has opened a multi-terminal service is considered a managed device.
  • the wearable device may prompt the user to trigger the embodiment of the present invention by prompting, ringing, shaking, presenting a message, and the like. The process of shielding incoming calls.
  • the following content may be displayed: “Detecting that the device has been disconnected from the mobile phone, is the other device blocked?” and prompting the user to complete the input of the instruction on the wearable device, for example, , setting a button for indicating "yes” and “no” on the wearable device, or presenting a touchable area for the user to select “yes” and “no” on the touch screen of the wearable device, or prompting
  • the user inputs commands and the like by means of voice, which is not mentioned here.
  • FIG. 14 a schematic diagram of an application scenario of a mobile phone managing a wearable watch and a tablet computer is provided.
  • the mobile phone is a management device, and the watch and the tablet computer are managed devices.
  • the watch and the tablet computer are managed devices.
  • taking a dual-card mobile phone as an example in the management interface of the first-number multi-card (ie, the number one multi-terminal), two pairs of cards inserted in the mobile phone are displayed.
  • the No. 1 multi-card information that is, the card No. 1 card information of Card 1 and Card 2 in the figure.
  • the user can untie the card 1 or other devices (ie, managed devices) already associated with the card 2 through the touch screen operation, for example, the watch 1 and the tablet 1.
  • the display interface of the mobile phone jumps from the management interface of the No. 1 multi-card to the card 1 sub-card management interface (ie, has the No. 1 card relationship with the card 1).
  • Other profiles provide multiple options in the secondary card management interface, such as call function and data function. Users can choose to enable or disable the corresponding function of a managed device through touch screen operation.
  • the current status of each managed device that is, offline or online, may also be displayed in the secondary card management interface.
  • FIG. 14 is only a schematic diagram of a possible implementation manner, and the trigger condition of the interface jump, the display manner of the management content, the type of the secondary card function, and the like are not limited.
  • the management device can detect that the managed device is powered on and connected. Then, the user is prompted to trigger the operation flow of sending the management command in the remote management of the embodiment of the present invention by using a prompting manner such as ringing, shaking, and presenting a message.
  • a prompting manner such as ringing, shaking, and presenting a message.
  • the mobile phone if the mobile phone is in the unlocked state, it is considered that the user is operating on the mobile phone, that is, after the calling terminal initiates the call, the user can directly answer the call through the mobile phone, and therefore, the mobile phone is preferentially selected.
  • the management device is usually a device used by the user to answer the phone. According to the actual usage behavior of the user, it can be concluded that the priority of setting the management device from high to low can be: wearable device that has been certified to wear and is out of the mobile phone range, mobile phone, tablet computer or vehicle device that is unlocked. And other equipment.
  • the method of setting the management device is not limited to the foregoing implementation manner, and may be adjusted according to the actual usage scenario of the user, and is not limited thereto.
  • the embodiment of the invention provides a No. 1 multi-terminal call management device, which is applied to a managed device.
  • the device includes corresponding hardware structures and/or software modules for performing various functions.
  • the present invention can be implemented in a combination of hardware or hardware and computer software in combination with the elements and algorithm steps of the various examples described in the embodiments disclosed herein. Whether a function is implemented in hardware or computer software to drive hardware depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods for implementing the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present invention.
  • the embodiment of the present invention may divide the function module into the device according to the foregoing method example.
  • each function module may be divided according to each function, or two or more functions may be integrated into one processing module.
  • the above integrated modules can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of the module in the embodiment of the present invention is schematic, and is only a logical function division, and the actual implementation may have another division manner.
  • FIG. 15 is a schematic diagram of a possible structure of the No. 1 multi-terminal call management device involved in the foregoing embodiment.
  • the first terminal multi-terminal call management device 10 includes a processing module 11 and a communication module 12, and may further include a storage module 13 in the embodiment of the present invention.
  • the processing module 11 is configured to support the No. 1 multi-terminal call management device. Step 10 to step 204 in FIG. 4 and FIG. 5, step 302 in FIG. 5;
  • the communication module 12 is configured to support the No. 1 multi-terminal call management device 10 to perform step 301 in FIG. 5, and support the number one.
  • the storage module 13 is configured to store required program codes and data.
  • the processing module 11 can be implemented as a processor or a controller, for example, the processor 101 in FIG. 1 , which can be a central processing unit (CPU), a general-purpose processor, and a digital signal processor (Digital). Signal Processor (DSP), Application-Specific Integrated Circuit (ASIC), Field Programmable Gate Array (FPGA) or other programmable logic device, transistor logic device, hardware component, or any combination thereof. It is possible to implement or carry out the various illustrative logical blocks, modules and circuits described in connection with the present disclosure.
  • the processor may also be a combination of computing functions, for example, including one or more microprocessor combinations, a combination of a DSP and a microprocessor, and the like.
  • the communication module 12 can be implemented as a transceiver, a transceiver circuit, a communication interface, or the like.
  • the storage module 13 can be implemented as a memory.
  • the managed device 20 includes: a processor 21, a transceiver 22, a memory 23, and a bus. twenty four.
  • the processor 21, the transceiver 22 and the memory 23 are connected to each other through a bus 24; the bus 24 may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus. Wait.
  • PCI Peripheral Component Interconnect
  • EISA Extended Industry Standard Architecture
  • the bus can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in Figure 16, but it does not mean that there is only one bus or one type of bus.
  • the embodiment of the invention provides a No. 1 multi-terminal call management device, which is applied to a server.
  • the device includes corresponding hardware structures and/or software modules for performing various functions.
  • the present invention can be implemented in a combination of hardware or hardware and computer software in combination with the elements and algorithm steps of the various examples described in the embodiments disclosed herein. Whether a function is implemented in hardware or computer software to drive hardware depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods for implementing the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present invention.
  • the embodiment of the present invention may divide the function module into the device according to the foregoing method example.
  • each function module may be divided according to each function, or two or more functions may be integrated into one processing module.
  • the above integrated modules can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of the module in the embodiment of the present invention is schematic, and is only a logical function division, and the actual implementation may have another division manner.
  • the first multi-terminal call management device 30 includes a processing module 31 and a communication module 32.
  • the storage module 33 may also be included.
  • the processing module 31 is configured to support the No. 1 multi-terminal call management device 30 to perform step 602 and step 603 in FIG. 8;
  • the communication module 32 is configured to support the No. 1 multi-terminal call management device 30 to perform step 601 in FIG. 8 , and Supporting data interaction between modules in the first-number multi-terminal call management device 30, and/or supporting communication between the management device where the device 30 is located and other devices such as managed devices;
  • the storage module 33 is configured to store required Program code and data.
  • the processing module 31 can be implemented as a processor or a controller, such as a CPU, a general purpose processor, a DSP, an ASIC, an FPGA or other programmable logic device, a transistor logic device, a hardware component, or any combination thereof. It is possible to implement or carry out the various illustrative logical blocks, modules and circuits described in connection with the present disclosure.
  • the processor may also be a combination of computing functions, for example, including one or more microprocessor combinations, a combination of a DSP and a microprocessor, and the like.
  • the communication module 32 can be implemented as a transceiver, a transceiver circuit, a communication interface, or the like.
  • the storage module 33 can be implemented as a memory.
  • the server 40 includes a processor 41, a communication interface 42, a memory 43, and a bus 44.
  • the processor 41, the communication interface 42 and the memory 43 are mutually connected by a bus 44; the bus 44 may be a PCI bus or an EISA bus or the like.
  • the bus can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in Figure 18, but it does not mean that there is only one bus or one type of bus.
  • the embodiment of the present invention provides a first-number multi-terminal call management system 50.
  • the system 50 includes a management device 51, an ES 52, and a managed device 53.
  • the management device 51 transmits a remote management command to the managed device 53 via the ES 52.
  • the remote management instruction includes an identifier of the managed configuration file in the managed device;
  • the managed device 51 receives the remote management command and determines a communication subunit corresponding to the identity of the managed profile, and in response to the remote management command, performs a call mask setting on the communication subunit corresponding to the identity of the managed profile.
  • the managed device 53 parses the incoming call and obtains the incoming call information.
  • the caller information includes the called identity.
  • the managed device 53 If the managed device 53 has performed the incoming call screening setting for the communication subunit corresponding to the called identity, it does not respond to the incoming call event.
  • the management device 51 parses the incoming call and obtains the incoming call information. If the management device 51 has not performed the incoming call screening setting of the communication subunit corresponding to the called identifier, it responds to the incoming call event.
  • the embodiment of the present invention provides a first-number multi-terminal call management system 60.
  • the system 60 includes a management device 61, an ES 62, and a server 63.
  • the management device 61 transmits a remote management command to the server 63 via the ES 62.
  • the remote management command includes an identifier of the managed configuration file of the managed device.
  • the server 63 receives the remote management command, deletes or freezes the routing information corresponding to the identifier, so that the communication subunit corresponding to the identifier in the managed device cannot respond to the incoming call event.
  • the management device 61 parses the incoming call and obtains the incoming call information.
  • the caller information includes the called identity. If the management device 61 has not performed the incoming call screening setting of the communication subunit corresponding to the called identity, it responds to the incoming call event.
  • the management device 61 can implement the management of the managed device on the server 63 through the ES 62, or directly communicate with the server 63 without using the ES 62, that is, directly on the server 63. Implement management of managed devices.
  • the embodiment of the present invention provides a computer program product, where the computer program product includes software code, and the software code is used to execute the method flow shown in FIG. 4 and FIG.
  • Embodiments of the present invention provide a computer program product, where the computer program product includes software code, the soft The code is used to execute the method flow shown in Figure 8.
  • Embodiments of the present invention provide a computer storage medium including instructions.
  • the instruction When the instruction is run on the electronic device, the electronic device is caused to perform the method flow as shown in FIG. 4 and FIG. 5.
  • Embodiments of the present invention provide a computer storage medium including instructions.
  • the instruction When the instruction is run on the electronic device, the electronic device is caused to perform the method flow as shown in FIG.
  • the functions described in the embodiments of the present invention may be implemented in hardware, software, firmware, or any combination thereof.
  • the functions may be stored in a computer readable medium or transmitted as one or more instructions or code on a computer readable medium.
  • Computer readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one location to another.
  • a storage medium may be any available media that can be accessed by a general purpose or special purpose computer.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Databases & Information Systems (AREA)
  • Human Computer Interaction (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Telephone Function (AREA)
  • Telephonic Communication Services (AREA)

Abstract

本申请提供一种一号多终端的来电管理方法、装置、被管理设备及服务器，涉及eSIM技术领域，能够解决电话误接的问题。该方法包括：被管理设备解析入呼叫，得到来电信息，并确定与被叫标识对应的通信子单元，之后若被管理设备响应于ES发送的远程管理指令，已执行过对通信子单元的入呼叫屏蔽设置，则不响应入呼叫事件；或者，服务器接收ES发送的远程管理指令，并响应于远程管理指令，删除或冻结标识对应的路由信息，以使被管理设备中的标识对应的通信子单元无法响应入呼叫事件。本申请适用于一号多终端的来电管理过程。

Description

一号多终端的来电管理方法、装置、被管理设备及服务器
本申请要求于2017年6月26日提交中国专利局、申请号为201710494840.1、申请名称为“一号多终端的远程管理的方法和设备”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及嵌入式国际移动用户身份识别模块(e-embedded Subscriber Identity Module，eSIM)技术领域，尤其涉及一种一号多终端(multi-sim)的来电管理方法及装置。
背景技术
随着eSIM技术的发展，一号多终端业务应运而生。一号多终端业务所指的多终端可以被视为多个具有不同国际移动用户识别码(International Mobile Subscriber Identification Number，IMSI)，却具有相同移动台综合业务数字网号码(Mobile Subscriber International ISDN/PSTN number，MSISDN)的多台终端。
上述多终端通常包括一个管理设备和至少一个被管理设备，其中，管理设备可以实现为各个被管理设备开通一号多终端业务，为了实现一号多终端业务，则需要在被管理设备的eSIM中加载与管理设备具有关联关系的配置文件(profile)。这样，在主叫终端向MSISDN所对应的终端发起呼叫时，由于管理设备与被管理设备因具有相同的MSISDN，因此，管理设备与被管理设备都可以接收到入呼叫，即管理设备和被管理设备会同时振铃，此时，用户只能通过多终端中的一个终端接通电话，即最先响应该入呼叫事件的终端作为被叫终端，与主叫终端建立通话。
但在管理设备与被管理设备的实际使用过程中，若管理设备与被管理设备分处于不同用户的使用范围内时，如果用户需要通过管理设备完成通话的建立，但对于管理设备或是被管理设备而言，只要优先接通了该入呼叫，就能够实现与主叫终端之间通话的建立。也就意味着，在通过被管理设备优先接通电话的情况下，用户则无法通过管理设备完成与主叫终端之间通话的建立，即造成了电话误接。
发明内容
本发明实施例提供一种一号多终端的来电管理方法、装置、被管理设备及服务器，能够解决电话误接的问题。
为了解决上述问题，本发明实施例提供如下方案：
第一方面，本发明实施例提供一种一号多终端来电管理方法。该方法包括：被管理设备解析入呼叫，得到来电信息，之后确定与被叫标识对应的通信子单元。若被管理设备响应于远程管理服务器ES发送的远程管理指令，已执行过对通信子单元的入呼叫屏蔽设置，则不响应入呼叫事件。其中，远程管理服务器负责提供一号多终端业务的开通、远程管理等功能。需要说明的是，对于被管理设备而言，在执行过一次对通 信子单元的入呼叫屏蔽设置后，只要不解除该入呼叫屏蔽设置，那么之后被管理设备所接收到的每一个满足屏蔽要求的入呼叫事件都会按照已完成的入呼叫屏蔽设置进行屏蔽操作。其中，来电信息包括指向配置文件的被叫标识；通信子单元用于在被管理设备上实现对应于配置文件的通信功能，通信功能至少包括接听指向配置文件的入呼叫；远程管理指令包括被管理设备中的被管理配置文件的标识。现有技术中，因通过被管理设备优先响应入呼叫事件而导致用户随身携带的管理设备无法完成与主叫终端之间通话的建立，从而造成电话误接。相比于现有技术，在本发明实施例中，由管理设备作为管理操作的发起端，通过ES向被管理设备发起请求消息，之后由被管理设备完成入呼叫屏蔽设置。这样在主叫终端发起呼叫后，由于被管理设备已经完成了屏蔽设置，因此，对于满足屏蔽条件的入呼叫，被管理设备执行屏蔽操作，使用户无法感知到入呼叫事件，从而使用户只能通过管理设备处理入呼叫事件。并且，本发明实施例所实现的入呼叫屏蔽设置仅针对被叫号码为指定号码的入呼叫而言，不会影响用户在数据业务、主叫业务或是其他业务上的通信。比如，在用户选用一号多终端业务后，管理设备和被管理设备作为被叫的号码为133XXXXXXXX，通过本发明实施例的远程管理方法，用户通过主叫终端拨打133XXXXXXXX，该入呼叫在被管理设备不会被响应。其中，被管理设备不响应该入呼叫的实现方式可以为自动屏蔽或是在被管理设备侧根本收不到该入呼叫。
需要说明的是，对于存在关联关系的至少两个设备而言，设备可以通过检测等方式判断自身是否通过了佩戴认证，此外，设备还可以判断自身是否处于运动状态。之后，设备可以将检测结果反馈给与自身存在关联关系的其他设备，该其他设备可以通过将自身状态与接收到的该设备的检测结果进行比对，确定哪个设备为管理设备，以及哪个设备为被管理设备，之后将设备身份的确定结果反馈给该设备。这样，存在关联关系的至少两个设备就可以根据自身的身份来执行相应的功能，比如，确认自身身份为管理设备的设备，可以实现管理其他被管理设备执行入呼叫屏蔽设置，而确认自身身份为被管理设备的设备，可以迎合管理设备发起的远程管理指令实现入呼叫屏蔽设置。
当然，设备也可以预存管理设备与被管理设备的区分条件，之后通过判断自身满足哪个条件，以及接收到其他设备发送的其他设备所满足的条件，确定其他设备与自身的优先级情况，之后确定出哪个设备为管理设备，哪个或是哪些设备为被管理设备，并告知各个设备的身份，实现管理设备管理被管理设备完成入呼叫屏蔽设置。需要说明的是，用于判断管理设备与被管理设备身份的方式不仅限于上述例举的情况，还可以包括其他用于区分管理优先级的方式，在此不做限定。在一种可能的设计中，在被管理设备不响应入呼叫事件之前，被管理设备接收ES发送的远程管理指令，并确定与被管理配置文件的标识对应的通信子单元，之后响应于远程管理指令，对与被管理配置文件的标识对应的通信子单元进行入呼叫屏蔽设置。由此可见，若用户试图屏蔽被管理配置文件的标识对应的通信子单元所要处理的所有入呼叫，则需要预先根据ES发送的远程管理指令进行屏蔽设置。
在一种可能的设计中，被管理设备对与被管理配置文件的标识对应的通信子单元进行入呼叫屏蔽设置包括：被管理设备使用来电过滤技术，比如，安卓系统下的来电 过滤服务(call screening service)，进行对被管理配置文件的标识对应的通信子单元的入呼叫屏蔽设置；或者，被管理设备为与被管理配置文件的标识对应的通信子单元设置空的来电接听白名单，以屏蔽不属于来电接听白名单中的移动台综合业务数字网号码MSISDN作为主叫号码发起的呼叫；或者，入呼叫屏蔽设置是为通信子单元添加指定标识，以使来电时，通信子单元检测到自身具有指定标识，则不响应入呼叫事件。上述例举的几种可以采用的屏蔽设置及对应的屏蔽操作手段，仅作为一种可能的实现方式，在此不做限定。
在一种可能的设计中，不响应入呼叫事件包括：拒绝入呼叫事件或忽略入呼叫事件。也就意味着，本发明实施例中实现的屏蔽操作所导致的结果为被管理设备不响应入呼叫。
在一种可能的设计中，被叫标识包括临时移动用户标识TMSI、国际移动用户识别码IMSI、移动台综合业务数字网号码MSISDN中的一项。
在一种可能的设计中，在被管理设备确定与被叫标识对应的通信子单元之后，若通信子单元未进行过入呼叫屏蔽设置，则被管理设备提示用户响应入呼叫事件。即按照目前正常的入呼叫处理流程来处理入呼叫。
第二方面，本发明实施例提供一种一号多终端来电管理方法。该方法包括：管理设备与被管理设备建立连接；当管理设备确定连接断开，则判断管理设备是否处于运动状态；如果管理设备处于运动状态，则管理设备管理被管理设备屏蔽入呼叫。
在一种可能的设计中，如果管理设备处于运动状态，则管理设备管理被管理设备屏蔽入呼叫，包括：如果管理设备处于运动状态，且运动状态保持预设时长，则管理设备管理被管理设备屏蔽入呼叫。需要说明的是，此时默认管理设备与被管理设备已经知道自身是否具备管理或是被管理的身份，当然设备也可以通过查询等方式明确自身的身份，比如，用户可以在管理设备与被管理设备之间建立管理关系时设置好哪个设备为管理设备，以及哪个或是哪些设备为被管理设备。这样在管理设备确认与被管理设备之间的连接断开且管理设备处于运动状态时，直接触发被管理设备执行入呼叫屏蔽设置。
在一种可能的设计中，管理设备管理被管理设备屏蔽入呼叫，包括：管理设备向被管理设备发送远程管理指令，远程管理指令包括被管理设备的被管理配置文件的标识；被管理设备接收远程管理指令，并确定与被管理配置文件的标识对应的通信子单元；被管理设备响应于远程管理指令，对通信子单元进行入呼叫屏蔽设置。
在一种可能的设计中，在对通信子单元进行入呼叫屏蔽设置之后，该方法包括：被管理设备解析入呼叫，得到来电信息，来电信息包括被叫标识；若被管理设备已执行过对被叫标识对应的通信子单元的入呼叫屏蔽设置，则不响应入呼叫事件；管理设备解析入呼叫，得到来电信息；若管理设备未执行过对被叫标识对应的通信子单元的入呼叫屏蔽设置，则响应入呼叫事件。
第三方面，本发明实施例提供一种一号多终端来电管理方法。该方法包括：服务器接收远程管理服务器ES发送的远程管理指令，并响应于远程管理指令，删除或冻结被管理配置文件的标识对应的路由信息，这样就无法查找到被管理设备的路由信息，也就不会有电话呼入被管理设备，也就不会出现呼叫在被管理设备处被误接的情况。 其中，路由信息是用于对被叫进行寻址的，远程管理指令包括被管理设备中的被管理配置文件的标识。需要说明的是，对于已经被删除的路由信息而言，服务器接收到路由查询请求之后则无法再查找到已经被删除的路由信息，也就意味着，服务器无法反馈已经被删除的路由信息。在本发明实施例中，通信业务服务器可以通过暂时冻结路由信息的方式，确保在主叫终端发起呼叫后，由于被管理设备的路由信息被冻结而使被管理设备无法感知到电话的呼入；或者，服务器针对目标被管理配置文件，为被管理配置文件开通呼叫限制的补充业务，即限制被管理设备作为被叫时的通话业务。需要说明的是，上述两种例举的实现方式，最终都会导致在通信网络中无法查询到被管理设备的路由信息，也正是因为在主叫终端发起呼叫后，由于通信网络中仅存在管理设备对应的路由信息，所以不会出现呼叫在被管理设备上被响应的情况。
在一种可能的设计中，在服务器响应于远程管理指令，删除或冻结标识对应的路由信息之后，在服务器接收到路由查询请求，且响应于路由查询请求，查询到已被冻结的标识对应的路由信息，则服务器不反馈已被冻结的标识对应的路由信息。
第四方面，本发明实施例提供一种一号多终端来电管理方法。该方法包括：管理设备与被管理设备建立连接；当管理设备确定连接断开，则判断管理设备是否处于运动状态；如果管理设备处于运动状态，则管理设备管理服务器屏蔽入呼叫。
在一种可能的设计中，如果管理设备处于运动状态，则管理设备管理服务器屏蔽入呼叫，包括：如果管理设备处于运动状态，且运动状态保持预设时长，则管理设备管理服务器屏蔽入呼叫。
在一种可能的设计中，管理设备管理服务器屏蔽入呼叫，包括：管理设备向服务器发送远程管理指令，远程管理指令包括被管理设备的被管理配置文件的标识；服务器接收远程管理指令，并响应于远程管理指令，删除或冻结标识对应的路由信息，以使被管理设备中的标识对应的通信子单元无法响应入呼叫事件。
在一种可能的设计中，在删除或冻结标识对应的路由信息之后，方法包括：管理设备解析入呼叫，得到来电信息，来电信息包括被叫标识；若管理设备未执行过对被叫标识对应的通信子单元的入呼叫屏蔽设置，则响应入呼叫事件；若被管理设备已执行过对被叫标识对应的通信子单元的入呼叫屏蔽设置，则不响应入呼叫事件。
第五方面，本发明实施例提供一种一号多终端来电管理装置。该装置应用于被管理设备，可以实现上述方法实施例中所实现的功能，所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个上述功能相应的模块。
第六方面，本发明实施例提供一种一号多终端来电管理装置。该装置应用于服务器，可以实现上述方法实施例中所实现的功能，所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个上述功能相应的模块。
第七方面，本发明实施例提供一种被管理设备。该被管理设备的结构中包括处理器和收发器，该处理器被配置为支持该被管理设备执行上述方法中相应的功能。该收发器用于支持该被管理设备与诸如服务器等其他设备之间的通信。该被管理设备还可以包括存储器，该存储器用于与处理器耦合，其保存该被管理设备必要的程序指令和数据。
第八方面，本发明实施例提供一种服务器。该服务器的结构中包括处理器和通信接口，该处理器被配置为支持该服务器执行上述方法中相应的功能。该通信接口用于支持该服务器与诸如被管理设备等其他设备之间的通信。该服务器还可以包括存储器，该存储器用于与处理器耦合，其保存该服务器必要的程序指令和数据。
第九方面，本发明实施例提供一种一号多终端来电管理系统。该系统包括：管理设备通过远程管理服务器ES，向被管理设备发送远程管理指令，之后被管理设备接收远程管理指令，并确定与被管理配置文件的标识对应的通信子单元，且响应于远程管理指令，对与被管理配置文件的标识对应的通信子单元进行入呼叫屏蔽设置。其中，远程管理指令包括被管理设备中的被管理配置文件的标识。后续当被管理设备接收到入呼叫时，解析入呼叫，得到来电信息，若被管理设备已执行过对来电信息中的被叫标识对应的通信子单元的入呼叫屏蔽设置，则不响应入呼叫事件。
在一种可能的设计中，该系统还包括：管理设备解析入呼叫，得到来电信息，若管理设备未执行过对被叫标识对应的通信子单元的入呼叫屏蔽设置，则响应入呼叫事件。
第十方面，本发明实施例提供一种一号多终端来电管理系统。该系统包括：管理设备通过远程管理服务器ES，向服务器发送远程管理指令，之后服务器接收远程管理指令，删除或冻结标识对应的路由信息，以使被管理设备中的标识对应的通信子单元无法响应入呼叫事件。其中，远程管理指令包括被管理设备的被管理配置文件的标识。
在一种可能的设计中，该系统还包括：管理设备解析入呼叫，得到来电信息，若管理设备未执行过对来电信息中的被叫标识对应的通信子单元的入呼叫屏蔽设置，则响应入呼叫事件。
第十一方面，本发明实施例提供一种计算机程序产品，该计算机程序产品包括软件代码，该软件代码用于执行上述第一、二方面及其各种可能的设计中任意一项所述的方法。
第十二方面，本发明实施例提供一种计算机程序产品，该计算机程序产品包括软件代码，该软件代码用于执行上述第三、四方面及其各种可能的设计中任意一项所述的方法。
第十三方面，本发明实施例提供一种计算机存储介质，包括指令。当该指令在电子设备上运行时，使得该电子设备执行上述第一、二方面及其各种可能的设计中任意一项所述的方法。
第十四方面，本发明实施例提供一种计算机存储介质，包括指令。当该指令在电子设备上运行时，使得该电子设备执行上述第三、四方面及其各种可能的设计中任意一项所述的方法。
附图说明
图1为本发明实施例提供的一种终端结构示意图；
图2为本发明实施例提供的一种通信网络系统的结构示意图；
图3为本发明实施例提供的一种MSC获取路由信息的过程示意图；
图4为本发明实施例提供的一种一号多终端的来电管理方法流程图；
图5为本发明实施例提供的另一种一号多终端的来电管理方法流程图；
图6为本发明实施例提供的一种一号多终端的来电管理方法交互图；
图7为本发明实施例提供的另一种一号多终端的来电管理方法交互图；
图8为本发明实施例提供的另一种一号多终端的来电管理方法流程图；
图9为本发明实施例提供的另一种MSC获取路由信息的过程示意图；
图10为本发明实施例提供的另一种一号多终端的来电管理方法交互图；
图11为本发明实施例提供的另一种一号多终端的来电管理方法交互图；
图12为本发明实施例提供的另一种一号多终端的来电管理方法交互图；
图13为本发明实施例提供的一种可穿戴设备管理手机的应用场景示意图；
图14为本发明实施例提供的一种手机管理手表、平板电脑的应用场景示意图；
图15为本发明实施例提供的一种一号多终端的来电管理装置的结构示意图；
图16为本发明实施例提供的一种被管理设备的结构示意图；
图17为本发明实施例提供的另一种一号多终端的来电管理装置的结构示意图；
图18为本发明实施例提供的一种服务器的结构示意图；
图19为本发明实施例提供的一种一号多终端来电管理系统的结构示意图；
图20为本发明实施例提供的另一种一号多终端来电管理系统的结构示意图。
具体实施方式
下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行描述。
本发明实施例适用于一号多终端的应用场景，即基于eSIM技术，可以实现两个甚至多个终端共用同一个号码，即多个终端的MSISDN相同，也就是电话号码相同。而相同号码所对应的配置文件，在不同的终端上会有所不同，比如，IMSI、密钥等信息会存在差异，而从本质上看，相同号码所对应的位于不同终端上的配置文件所签约的运营商业务相同，比如，数据流量、通话业务时长等运营商业务相同，且在各个终端之间共享。
本发明实施例中一号多终端中的多终端包括管理设备和被管理设备。其中，管理设备不仅可以为各个被管理设备开通一号多终端业务，还可以对其他终端进行管理，比如，本发明实施例后文会提到的入呼叫事件的屏蔽设置等。一般情况下，将用户期望实现与主叫终端完成通话建立的终端视为管理设备，而对于与该管理设备具备相同MSISDN且IMSI不同的终端，则被视为被管理设备。
例如，在场景1中，管理设备可以为方便携带的手机，被管理设备可以为不方便携带的平板电脑(Tablet Personal Computer，Tablet PC)。在用户将被管理设备放置在家中供家人使用的过程中，且用户携带管理设备外出的情况下，若有来电，则很可能被家人通过家中的平板电脑抢先接听，而这样就会使主叫终端与作为被管理设备的平板电脑之间完成通话建立。也就意味着，用户无法通过随身携带的手机接听该来电。
再例如，在场景2中，管理设备可以为随身佩戴的手表，被管理设备可以为手机。用户在出门运动时，很可能只佩戴了手表，而将手机放在家中。若有来电，因用户正在运动，很可能没能及时注意到手表上提示的来电信息，而被家人通过手机误接来电，从而使放置在家中的手机与主叫终端之间完成通话建立。也就意味着，用户无法通过随身佩戴的手表接听该来电。
再例如，在场景3中，管理设备可以为方便携带的手机，被管理设备可以为车载设备。在用户将设置有该车载设备的汽车借给其他人驾驶后，若有来电，很可能因其他人的习惯性接听操作或是用户长时间未接听，而导致其他人通过车载设备接听来电，从而使车载设备与主叫终端之间完成通话建立。也就意味着，用户无法通过随身携带的手机接听该来电。
由此可见，在很多场景下，一号多终端业务的使用都会造成来电误接问题的发生。目前，为了解决这一问题，可以通过在被管理设备上去激活被管理配置文件，比如，将profile设置为无法使用的状态(disable状态)，以确保在主叫终端发起呼叫后，用户无法通过被管理设备接听来电。由于配置文件是实现通信能力的必备元素，因此，去激活配置文件意味着所有业务无法使用，也就是说这样也会引发其他通信问题，比如，被管理设备因被去激活被管理配置文件而无法正常使用数据功能，也无法作为主叫终端向其他终端发起呼叫等。
因此，为了更好的解决一号多终端业务引起的电话误接的问题，本发明实施例提供了一种一号多终端的来电管理方法，以实现在被管理设备上或是网络侧的服务器上限制被管理设备响应来电的能力，即对被管理设备响应来电的能力进行管理。其中，服务器可以为归属位置寄存器(Home Location Register，HLR)或归属签约用户服务器(Home Subscriber Server，HSS)等用于实现通信业务的服务器。
本发明实施例可以用于一种终端，该终端可以为管理设备或被管理设备，该终端可以包括笔记本电脑、智能手机或手环等设备。该终端至少设置有显示屏、输入设备和处理器，以终端100为例，如图1所示，该终端100中包括处理器101、存储器102、摄像头103、RF电路104、音频电路105、扬声器106、话筒107、输入设备108、其他输入设备109、显示屏110、触控面板111、显示面板112、输出设备113、以及电源114等部件。其中，显示屏110至少由作为输入设备的触控面板111和作为输出设备的显示面板112组成。需要说明的是，图1中示出的终端结构并不构成对终端的限定，可以包括比图示更多或更少的部件，或者组合某些部件，或者拆分某些部件，或者不同的部件布置，在此不做限定。
下面结合图1对终端100的各个构成部件进行具体的介绍：
射频(Radio Frequency，RF)电路104可用于收发信息或通话过程中，信号的接收和发送，比如，若该终端100为手机，那么该终端100可以通过RF电路104，将基站发送的下行信息接收后，传送给处理器101处理；另外，将涉及上行的数据发送给基站。通常，RF电路包括但不限于天线、至少一个放大器、收发信机、耦合器、低噪声放大器(Low Noise Amplifier，LNA)、双工器等。此外，RF电路104还可以通过无线通信与网络和其他设备通信。该无线通信可以使用任一通信标准或协议，包括但不限于全球移动通讯系统(Global System of Mobile communication，GSM)、通用分组无线服务(General Packet Radio Service，GPRS)、码分多址(Code Division Multiple Access，CDMA)、宽带码分多址(Wideband Code Division Multiple Access，WCDMA)、长期演进(Long Term Evolution，LTE)、电子邮件、短消息服务(Short Messaging Service，SMS)等。
存储器102可用于存储软件程序以及模块，处理器101通过运行存储在存储器101 的软件程序以及模块，从而执行终端100的各种功能应用以及数据处理。存储器101可主要包括存储程序区和存储数据区，其中，存储程序区可存储操作系统、至少一个功能所需的应用程序(比如，声音播放功能、图象播放功能等)等；存储数据区可存储根据终端100的使用所创建的数据(比如，音频数据、视频数据等)等。此外，存储器101可以包括高速随机存取存储器，还可以包括非易失性存储器，例如至少一个磁盘存储器件、闪存器件、或其他易失性固态存储器件。
其他输入设备109可用于接收输入的数字或字符信息，以及产生与终端100的用户设置以及功能控制有关的键信号输入。具体地，其他输入设备109可包括但不限于物理键盘、功能键(比如，音量控制按键、开关按键等)、轨迹球、鼠标、操作杆、光鼠(光鼠是不显示可视输出的触摸敏感表面，或者是由触摸屏形成的触摸敏感表面的延伸)等中的一种或多种。其他输入设备109还可以包括终端100内置的传感器，比如，重力传感器、加速度传感器等，终端100还可以将传感器所检测到的参数作为输入数据。
显示屏110可用于显示由用户输入的信息或提供给用户的信息以及终端100的各种菜单，还可以接受用户输入。此外，显示面板112可以采用液晶显示器(Liquid Crystal Display，LCD)、有机发光二极管(Organic Light-Emitting Diode，OLED)等形式来配置显示面板112；触控面板111，也称为触摸屏、触敏屏等，可收集用户在其上或附近的接触或者非接触操作(比如，用户使用手指、触笔等任何适合的物体或附件在触控面板111上或在触控面板111附近的操作，也可以包括体感操作；该操作包括单点控制操作、多点控制操作等操作类型)，并根据预先设定的程式驱动相应的连接装置。需要说明的是，触控面板111还可以包括触摸检测装置和触摸控制器两个部分。其中，触摸检测装置检测用户的触摸方位、姿势，并检测触摸操作带来的信号，将信号传送给触摸控制器；触摸控制器从触摸检测装置上接收触摸信息，并将它转换成处理器101能够处理的信息，再传送给处理器101，并且，还能接收处理器101发来的命令并加以执行。此外，可以采用电阻式、电容式、红外线以及表面声波等多种类型实现触控面板111，也可以采用未来发展的任何技术实现触控面板111。一般情况下，触控面板111可覆盖显示面板112，用户可以根据显示面板112显示的内容(该显示内容包括但不限于软键盘、虚拟鼠标、虚拟按键、图标等)，在显示面板112上覆盖的触控面板111上或者附近进行操作，触控面板111检测到在其上或附近的操作后，传送给处理器101以确定用户输入，随后处理器101根据用户输入，在显示面板112上提供相应的视觉输出。虽然在图1中，触控面板111与显示面板112是作为两个独立的部件来实现终端100的输入和输出功能，但是在某些实施例中，可以将触控面板111与显示面板112集成，以实现终端100的输入和输出功能。
RF电路104、扬声器106，话筒107可提供用户与终端100之间的音频接口。音频电路105可将接收到的音频数据转换后的信号，传输到扬声器106，由扬声器106转换为声音信号输出；另一方面，话筒107可以将收集的声音信号转换为信号，由音频电路105接收后转换为音频数据，再将音频数据输出至RF电路104以发送给诸如另一终端的设备，或者将音频数据输出至存储器102，以便处理器101结合存储器102中存储的内容进行进一步的处理。另外，摄像头103可以实时采集图像帧，并传送给 处理器101处理，并将处理后的结果存储至存储器102和/或将处理后的结果通过显示面板112呈现给用户。
处理器101是终端100的控制中心，利用各种接口和线路连接整个终端100的各个部分，通过运行或执行存储在存储器102内的软件程序和/或模块，以及调用存储在存储器102内的数据，执行终端100的各种功能和处理数据，从而对终端100进行整体监控。此外，处理器101还可以实现对通信子单元的管理，比如，对通信子单元进行配置等。需要说明的是，处理器101可以包括一个或多个处理单元；处理器101还可以集成应用处理器和调制解调处理器，其中，应用处理器主要处理操作系统、用户界面(User Interface，UI)和应用程序等，调制解调处理器主要处理无线通信。可以理解的是，上述调制解调处理器也可以不集成到处理器101中。
终端100还可以包括给各个部件供电的电源114(比如，电池)，在本发明实施例中，电源114可以通过电源管理系统与处理器101逻辑相连，从而通过电源管理系统实现管理充电、放电、以及功耗等功能。
此外，图1中还存在未示出的部件，比如，终端100还可以包括蓝牙模块、近距离无线通讯技术(Near Field Communication，NFC)模块、无线保真(Wireless-Fidelity，Wi-Fi)模块、全球定位系统(global positioning system，GPS)模块、扬声器、加速计、陀螺仪等，在此不再赘述。其中，蓝牙模块，可用于手机在特定距离内(蓝牙协议规定的距离内)与其他支持蓝牙功能的设备建立蓝牙连接并互相通信；NFC模块，可用于手机与其他支持NFC通信的设备建立NFC连接并互相通信；终端100可通过Wi-Fi模块建立Wi-Fi连接并进行数据传输。
如图2所示，为本发明实施例提供的一种通信网络系统。其中，管理设备与被管理设备可以实现为如图1所示的终端，在本发明实施例中，以管理设备为手机、被管理设备为车载设备为例进行描述。主叫终端通过访问移动交换中心(Visited Mobile-services Switching Centre，VMSC)或网关移动交换中心(Gateway Mobile Switching Center，GMSC)发起呼叫，之后通信网络运营商(Mobile Network Operator，MNO)从供应商HLR(也可以为供应商HSS)中获取管理设备与被管理设备的路由信息，并根据已获取的路由信息，采取同振模式同时对多条路由信息对应的设备发起入呼叫。
其中，移动交换中心(Mobile Switching Center，MSC)获取路由信息的实现过程，如图3所示。其中，HLR/HSS数据库可以设置于上述供应商HLR中。MSC向HLR/HSS发起被叫路由信息的查询请求，之后从HLR/HSS数据库中查找到MSISDN所对应的多条路由信息，比如，路由信息1和路由信息2。其中，路由信息1为管理设备IMSI1所对应的路由信息，路由信息2为被管理设备IMSI2所对应的路由信息。之后HLR/HSS将路由信息1和路由信息2反馈给MSC。
本发明实施例提供了一种一号多终端的来电管理方法，如图4所示，该方法至少包括步骤201至步骤203。在本发明实施例中，还可以包括步骤204。
步骤201、被管理设备解析入呼叫，得到来电信息。
其中，来电信息包括被叫标识。在本发明实施例中，被叫标识可以包括但不仅限于临时移动用户标识(Temporary Mobile Subscriber Identity，TMSI)、IMSI、MSISDN中的一项。
在被管理设备接收到入呼叫后，由被管理设备直接屏蔽对满足屏蔽条件的入呼叫。其中，屏蔽条件是被叫标识指向的配置文件对应的通信子单元进行过入呼叫屏蔽设置。也就意味着，被管理设备本身是可以感应到主叫终端的电话呼入的，只不过在感应到电话呼入后并不通过声音、显示等方式提醒用户去接听该电话，即从用户感知角度而言，用户对于满足屏蔽条件的入呼叫毫无感知。
步骤202、被管理设备确定与被叫标识对应的通信子单元。
其中，通信子单元用于在被管理设备上实现对应于配置文件的通信功能，通信功能至少包括接听指向配置文件的入呼叫。
步骤203、若被管理设备响应于远程管理服务器(Entitlement Server，ES)发送的远程管理指令，已执行过对通信子单元的入呼叫屏蔽设置，则不响应入呼叫事件。
其中，远程管理指令包括被管理设备中的被管理配置文件的标识；不响应入呼叫事件包括：拒绝入呼叫事件或忽略入呼叫事件。
在本发明实施例中，被管理设备根据管理指令中携带的被管理配置文件标识来确定是否需要对相应的通信子单元执行入呼叫屏蔽设置。后续接收到入呼叫再判断入呼叫是否满足屏蔽条件来决定是否需要响应，即若后续接收到的入呼叫事件中包含的被叫标识与被管理配置文件标识对应，则被管理设备就能够确定不响应该次入呼叫事件。
需要说明的是，远程管理指令中还可以携带有管理业务标识，从而使被管理设备在接收到该远程管理指令且识别到管理业务标识后，触发入呼叫屏蔽设置，其中，管理业务标识用于表示远程管理指令为用于触发对指定配置文件对应的通信子单元进行入呼叫屏蔽设置的指令。在被管理设备接收到该管理指令后，可以验证该管理指令的有效性，并在该管理指令通过验证后，即确认该管理指令可执行后，被管理设备根据被管理配置文件的标识对响应通信子单元进行入呼叫屏蔽设置，即进行屏蔽对指向被管理配置文件的入呼叫进行屏蔽设置。
步骤204、若通信子单元未进行过入呼叫屏蔽设置，则被管理设备提示用户响应入呼叫事件。
需要说明的是，对于存在关联关系的至少两个设备而言，设备可以通过检测等方式判断自身是否通过了佩戴认证，此外，设备还可以判断自身是否处于运动状态。之后，设备可以将检测结果反馈给与自身存在关联关系的其他设备，该其他设备可以通过将自身状态与接收到的该设备的检测结果进行比对，确定哪个设备为管理设备，以及哪个设备为被管理设备，之后将设备身份的确定结果反馈给该设备。这样，存在关联关系的至少两个设备就可以根据自身的身份来执行相应的功能，比如，确认自身身份为管理设备的设备，可以实现管理其他被管理设备执行入呼叫屏蔽设置，而确认自身身份为被管理设备的设备，可以迎合管理设备发起的远程管理指令实现入呼叫屏蔽设置。当然，设备也可以预存管理设备与被管理设备的区分条件，之后通过判断自身满足哪个条件，以及接收到其他设备发送的其他设备所满足的条件，确定其他设备与自身的优先级情况，之后确定出哪个设备为管理设备，哪个或是哪些设备为被管理设备，并告知各个设备的身份，实现管理设备管理被管理设备完成入呼叫屏蔽设置。需要说明的是，用于判断管理设备与被管理设备身份的方式不仅限于上述例举的情况，还可以包括其他用于区分管理优先级的方式，比如用户还可以根据自己的行为习惯预 先设置上述用于区别设备身份的预设条件，对于预设条件的具体内容，在此不做限定。设置预设条件的目的在于，从至少两个存在关联的设备中，确定出唯一一个用于管理其他设备的管理设备，与此同时，也确定出被该管理设备管理的被管理设备。
对于被管理设备而言，若被管理设备发出携带有被管理设备参数的管理指令，且对端设备在接收到该管理指令后，根据该管理指令所携带的被管理设备参数，确定发出该管理指令的设备为被管理设备，同时根据对端设备参数确定对端设备为管理设备，则对端设备对该被管理设备进行入呼叫屏蔽设置，并向该被管理设备返回响应。由此可见，入呼叫屏蔽设置的执行过程不仅可以由双方通过交互来触发，还可以通过单方面提出请求的形式来触发。
对于一台设备而言，该设备可以通过ES向其他对端设备发送携带该设备参数的远程管理指令。其他对端设备在接收到该远程管理指令之后，根据该远程管理指令所携带的该设备参数，结合接收到该远程管理指令的对端设备的设备参数，进行对端设备身份的判断。若对端设备判断此时该对端设备为被管理设备，则该对端设备对远程管理指令进行响应，即该对端设备执行入呼叫屏蔽设置并向该设备发送响应消息。如果对端设备判断此时该对端设备应该作为管理设备，则不对该远程管理指令进行响应。可选的，由该对端设备作为管理设备针对该设备发起远程管理流程。
或者，一台设备判断需要进行身份确认后，发送身份查询/确认请求到ES，ES此时获取各设备的状态，并对各设备的身份进行判断，然后将对各设备的判断结果返分别回给各设备。需要说明的是，每个设备可以仅接收到自身的判断结果，并依据判断结果所指示的身份配合其他设备执行入呼叫屏蔽设置，当然，每个设备也可以接收各设备的判断结果，之后明确自身的身份以及与自身存在关联关系的其他一个或是多个设备的身份，并完成入呼叫屏蔽设置。
在本发明实施例中，也可以预先在终端中设置终端接听电话的优先级，以便于终端后续通过数据交互的形式与其他终端判断自身的设备身份。比如，接听电话优先级可以设置为处于运动状态的手机的优先级高于处于运动状态且通过佩戴认证的可穿戴设备，高于处于静止状态的手机，高于其他设备。
现有技术中，因用户通过被管理设备优先接通电话而导致管理设备无法完成与主叫终端之间通话的建立，从而造成电话误接。相比于现有技术，在本发明实施例中，由管理设备作为管理操作的发起端，通过ES向被管理设备发起远程管理指令，之后由被管理设备完成对满足屏蔽条件的入呼叫进行屏蔽设置。这样在主叫终端发起呼叫后，由于被管理设备已经完成了屏蔽设置，因此，用户只能通过管理设备完成电话的接听。并且，本发明实施例所实现的屏蔽操作，仅针对被叫用户号码为指定电话而言，即不会影响用户在数据业务或是其他业务上的通信，仅针对电话呼入这一项业务进行选择性的屏蔽，且这里所指的电话呼入是以指定号码作为被叫用户号码的入呼叫。
比如，在管理设备与被管理设备的实际使用过程中，若管理设备与被管理设备分处于不同用户的使用范围内时，如果用户需要通过管理设备完成通话的建立，那么对于管理设备或是被管理设备而言，完成入呼叫屏蔽设置之后，只有管理设备能够实现与主叫终端之间通话的建立。需要说明的是，对于被管理设备而言，仅是不响应入呼叫事件，但还可以执行业务数据或是其他除响应入呼叫事件以外的业务。
在被管理设备不响应入呼叫事件之前，被管理设备上还需要根据ES发送的远程管理指令来完成入呼叫屏蔽设置。因此，在如图4所示的实现方式的基础上，还可以实现为如图5所示的实现方式，其中，在图5中，还包括步骤301和步骤302。
步骤301、被管理设备接收ES发送的远程管理指令。
步骤302、被管理设备确定与被管理配置文件的标识对应的通信子单元，并响应于远程管理指令，对与被管理配置文件的标识对应的通信子单元进行入呼叫屏蔽设置。
其中，被管理设备对与被管理配置文件的标识对应的通信子单元进行入呼叫屏蔽设置包括以下中的一项：
被管理设备使用来电过滤技术，进行对被管理配置文件的标识对应的通信子单元的入呼叫屏蔽设置。
在本发明实施例中，可以在被管理设备上安装用于实现来电过滤的过滤软件，并在过滤软件中预先配置好需要被过滤的入呼叫，即指向被管理设备中被管理配置文件的入呼叫事件都会被屏蔽，还可以使用操作系统提供的在入呼叫事件的处理流程中，对来电进行过滤的功能/系统服务来实现，比如安卓系统提供的call screening service。该功能导致的结果是使通信子单元能够不响应入呼叫事件。若被管理设备接收到入呼叫，且该入呼叫满足预先设置的屏蔽要求，则实现入呼叫屏蔽操作。当然，被管理设备中也可以被配置有来电过滤功能，也就意味着在不安装任何过滤软件的情况下，由被管理设备自身实现部分或是全部入呼叫的屏蔽操作。
或者，被管理设备为与被管理配置文件的标识对应的通信子单元设置空的来电接听白名单，以屏蔽不属于来电接听白名单中的MSISDN作为主叫号码发起的呼叫。
来电接听白名单用于记载用户允许呼入的主叫号码，比如，某用户向被管理设备发起入呼叫，而该某用户所使用的发起入呼叫的号码未被记载于来电接听白名单中，则被管理设备认为该某用户不具备向被管理设备发起呼叫的权限，或是认为被管理设备的用户不想接听到该某用户的来电，通信子单元检测到该某用户的主叫号码不在白名单内，则对该某用户的入呼叫事件进行拒接或忽略处理。由此可见，若来电接听白名单被设置为空，则表示来电接听白名单中未记载任何电话，也就意味着，任何电话的呼入都被视为无法被被管理配置文件对应的通信子单元接听的状态，或是被管理设备的用户不想接听到任何用户的来电，从而实现屏蔽不属于来电接听白名单中的MSISDN作为主叫号码发起的呼叫。比如，白名单中仅包括号码186XXXXXXXX，则只有号码186XXXXXXXX作为主叫号码时才能打入，而其他号码所发起的入呼叫事件会直接被拒接或忽略。因此，为一个通信子单元设置空的白名单，意味着所有指向被管理配置文件的入呼叫的主叫号码都不在该白名单内，从而实现了对配置文件对应的通信子单元的入呼叫屏蔽的效果。
或者，被管理设备为与被管理配置文件的标识对应的通信子单元增加指定标识，以使通信子单元在接收到入呼叫事件之后，检测到自身具有指定标识后，则触发对入呼叫事件进行入呼叫屏蔽操作，指定标识用于表示管理设备已执行过对通信子单元的入呼叫屏蔽设置。
比如，实现中可以为通信子单元添加一个状态位，在该状态位被设置为0时，则表示为该通信子单元被执行过入呼叫屏蔽设置。因此，远程控制指令用于将被管理配 置文件对应的通信子单元的状态位被设置为“0”。当入呼叫指向被管理配置文件时，通信子单元检查自身状态位为“0”则不响应入呼叫。
也就意味着，未添加指定标识的通信子单元仍然需要正常履行入呼叫的处理过程，而对于添加指定标识的通信子单元，则该通信子单元需要实现入呼叫屏蔽操作，即针对每个呼入的电话都不响应。
由此可见，若用户试图屏蔽被管理配置文件的标识对应的通信子单元所要处理的所有入呼叫，则需要预先根据ES发送的远程管理指令进行屏蔽设置。上述例举的几种可以采用的屏蔽设置及对应的屏蔽操作手段，仅作为一种可能的实现方式，在此不做限定。
例如，如图6所示，为管理设备通过ES发起入呼叫屏蔽设置的实现过程，包括步骤401至步骤409。
步骤401、管理设备向ES发送第一请求消息。
其中，第一请求消息用于指示ES向被管理设备发送第二请求消息；第二请求消息用于指示被管理设备进行指向被管理配置文件的通信子单元的入呼叫屏蔽设置，即屏蔽指向被管理配置文件的入呼叫事件的设置；指定电话包括以被管理配置文件对应MSISDN作为被叫用户号码的入呼叫事件。其中，MSISDN为管理配置文件一种可能的标识，当然管理配置文件还可以采用其他已有或是新增信息作为区分不同管理配置文件的标识，在此不做限定。
上述第一请求消息至少携带有被管理设备的标识和管理业务标识，其中，管理业务标识作为本次需要执行屏蔽设置的远程管理业务的标识，第二请求消息至少携带有被管理配置文件的标识和管理业务标识，即上述远程管理指令。
在本发明实施例中，第一请求消息可以被视为管理设备向ES发起的管理请求消息，可以由管理设备的一号多终端业务管理模块向ES发送，以告知该ES，管理设备试图调整被管理设备的功能，即限制被管理设备的部分功能的实现。
步骤402、ES接收管理设备发送的第一请求消息。
在ES接收到管理设备发送的第一请求消息后，对管理设备鉴权，确定管理设备身份后，查找到与被管理设备的标识对应的被管理配置文件的标识，之后生成第二请求消息。其中，第二请求消息中携带有查找到的被管理配置文件的标识，以及第一请求消息中携带的管理业务标识。
步骤403、ES向被管理设备发送第二请求消息。
步骤404、被管理设备接收ES发送的第二请求消息。
步骤405、被管理设备进行指向被管理配置文件的通信子单元的入呼叫屏蔽设置。
上述屏蔽设置过程可以包括：被管理设备根据第二请求消息中的被管理配置文件标识确定与被管理配置文件标识对应通信子单元，并对该通信子单元进行入呼叫屏蔽设置，具体事项方式可以参照步骤301和步骤302的描述内容。
步骤406、被管理设备向ES发送响应消息。
其中，响应消息用于表示被管理设备已完成入呼叫的屏蔽设置。
步骤407、ES接收被管理设备发送的响应消息。
步骤408、ES向管理设备发送响应消息。
步骤409、管理设备接收ES发送的响应消息。
本发明实施例提供一种一号多终端来电管理方法，如图7所示，该方法包括步骤501至步骤503。需要说明的是，初始状态下，若存在关联的至少两个设备中存在一个诸如智能手机的便携式终端，则可以默认由该便携式终端作为管理设备，而与该便携式终端存在关联关系的设备作为被管理设备。即除了预设条件外，用户还可以直接在终端中设置管理设备和被管理设备，或者，设备还可以通过协商或是查询的方式了解自身的身份以及与自身存在关联关系的其他设备的身份，具体实现过程请参照步骤204下方的描述，在此不再赘述。
步骤501、管理设备与被管理设备建立连接。
上述连接可以为蓝牙配对等对管理设备与被管理设备之间距离存在限制的连接方式，也可以为通过接入同一无线网络而建立的连接等，在此不做限定。
步骤502、当管理设备确定连接断开，则判断管理设备是否处于运动状态。
考虑到管理设备在与被管理设备建立连接后，管理设备与被管理设备均能感知到与自身存在连接关系的设备，因此，对于管理设备而言，若被管理设备与管理设备之间的连接断开，管理设备是可以识别到的，判断管理设备与被管理设备断开连接的方式为现有技术，在此不做赘述。
另外，设备是否处于运动状态的判断方式可以通过管理设备自带的各种传感器进行检测，设备是否处于运动状态的判断方法为现有技术，在此不做赘述。
步骤503、如果管理设备处于运动状态，则管理设备管理被管理设备屏蔽入呼叫。
比如，管理设备为手表，被管理设备为手机，当用户佩戴着手表出门倒垃圾时，通常由于出门时间较短，则会将手机放置在家中，这样作为管理设备的手表与作为被管理设备的手机之间距离较远后，就会断开连接。而此时，手表不仅检测到与手机断开连接，还检测到手表自身处于运动状态，则手表可以管理手机屏蔽入呼叫。这样，若有来电呼入，则用户可以直接通过手表接听，而位于家中的手机则不会感应到该来电。
进一步的，管理设备还可以判断运动状态的保持时长是否达到预设时长,如果管理设备处于运动状态，且运动状态保持预设时长，则管理设备管理被管理设备屏蔽入呼叫。
其中，预设时长可以由用户或是设备供应商根据经验值预先设置的，具体设置方式、预设时长的长短等，在此不做限定。
在管理设备的运动状态保持预设时长的情况下，可以确定管理设备当前处于使用状态，从而触发由管理设备发起的远程管理流程。其中，管理设备及被管理设备的身份确认方式可以参照步骤204下方的描述，在此不再赘述。
上述管理设备管理被管理设备屏蔽入呼叫的方法，可以为前述实施例中步骤401至步骤409的方法，在此不予赘述。
此外，当管理设备和被管理重新建立连接的场景下，可以自动通过相应的远程管理指令解除屏蔽操作。其中，管理设备与被管理设备重新建立连接的方式可以包括但不仅限于蓝牙等用于设备与设备之间建立连接的实现方式。
本发明实施例提供了一种一号多终端的来电管理方法，如图8所示，该方法至少 包括步骤601和步骤602。在本发明实施例中，还可以包括步骤603。
步骤601、服务器接收ES发送的远程管理指令。
其中，远程管理指令包括被管理设备中的被管理配置文件的标识。
在本发明实施例中，服务器可以包括HLR或HSS。
步骤602、服务器响应于远程管理指令，删除或冻结标识对应的路由信息。
这样就可以使被管理设备无法感知电话的呼入，也就不会出现误接。
需要说明的是，上述冻结标识对应的路由信息可以被视为暂时冻结，即在用户需要恢复被管理设备功能的时候，可以解除之前对路由信息的冻结，即恢复已冻结的路由信息。
对于入呼叫，除了可以采用上述删除或冻结标识对应的路由信息的方式，实现屏蔽设置，还可以通过响应于远程管理指令，自动为被管理设备上的被管理配置文件签约开通呼叫限制的补充业务，比如：
限制所有入呼叫(Barring of All Incoming Calls，BAIC)，指的是当用户与运营商签约了此业务后，任何人呼叫签约用户时，该用户都不会收到相关的入呼叫通知。也就意味着，该用户所使用的终端只能作为主叫终端发起呼叫，而不能接听电话，即只能打出，不能打进。同样的，也无法接收短消息，但可以发送短消息。
如图9所示，为实现屏蔽设置之后，MSC获取路由信息的实现过程。MSC向HLR/HSS发起被叫路由信息的查询请求，之后从HLR/HSS数据库中查找到MSISDN所对应的多条路由信息，比如，路由信息1和路由信息2。但由于IMSI2对应的业务数据集中被设置了入呼叫限制，和/或路由信息2被暂时冻结，那么MSC仅能获取到路由信息1。也就意味着，主叫终端发起的入呼叫，仅有管理设备会接收到，而被管理设备无法接收到该呼叫请求。
步骤603、在服务器接收到路由查询请求，且响应于路由查询请求，查询到已被冻结的标识对应的路由信息，则服务器不反馈已被冻结的标识对应的路由信息。
其中，步骤603中已被冻结的标识指的是被管理配置文件标识。
需要说明的是，对于已经被删除的路由信息而言，服务器接收到路由查询请求之后则无法再查找到已经被删除的路由信息，也就意味着，服务器无法反馈已经被删除的路由信息。
在本发明实施例中，服务器可以通过暂时冻结路由信息或者，服务器针对被管理配置文件，为被管理设备开通呼叫限制的补充业务的方式，确保在主叫终端发起呼叫后，由于被管理设备的路由信息被冻结而使被管理设备无法感知到电话的呼入。
例如，如图10所示，为管理设备通过ES发起入呼叫屏蔽设置的实现过程的另一种实现方式，包括步骤701至步骤705，之后根据实际情况选择性执行步骤707或步骤707，最后执行步骤708至步骤711。
步骤701、管理设备向ES发送第一请求消息。
其中，第一请求消息用于指示ES向服务器发送第二请求消息；第二请求消息用于指示服务器进行屏蔽把指定电话作为被叫用户的呼入设置。
上述第一请求消息至少携带有管理设备的IMSI、被管理设备的标识和管理业务标识，第二请求消息至少携带有管理设备的标识、被管理设备的标识和管理业务标识。
在本发明实施例中，第一请求消息可以被视为管理设备向ES发起的管理请求消息，可以由管理设备的一号多终端业务管理模块向ES发送，以告知该ES，管理设备试图调整被管理设备的功能，即限制被管理设备的部分功能的实现。
步骤702、ES接收管理设备发送的第一请求消息。
在ES接收到管理设备发送的第一请求消息后，根据第一请求消息中的管理设备与被管理设备标识，确定被管理设备的被管理配置文件标识。之后按照与服务器约定的数据格式，生成第二请求消息。其中，第二请求消息中携带有ES获取的管理设备的标识、被管理配置文件的标识，以及第一请求消息中携带的管理业务标识。
步骤703、ES向服务器发送第二请求消息，
步骤704、服务器接收ES发送的第二请求消息。
第二请求消息可以被视为ES向服务器发送的远程管理指令，该远程管理指令中携带有需要被管理的被管理配置文件标识。在服务器接收到该配置请求消息后，进行屏蔽设置。
步骤705、服务器确定管理设备与被管理设备关联的来电业务。
其中，在执行完步骤705之后，可以执行步骤706或步骤707，之后再执行步骤708。
步骤706、服务器将来电业务中被管理配置文件的IMSI对应的呼叫路由信息暂时冻结。
步骤707、服务器为被管理设备的被管理配置文件开通呼叫限制的补充业务。
步骤708、服务器向ES发送响应消息。
其中，响应消息用于表示服务器已完成屏蔽设置。
步骤709、ES接收服务器发送的响应消息。
步骤710、ES向管理设备发送响应消息。
步骤711、管理设备接收ES发送的响应消息。
其中，步骤708至步骤711与步骤406至步骤409类似，可以参考前文的描述内容，在此不再赘述。
再例如，如图11所示的方法流程与如图10所示的方法流程类似，区别在于，省略了ES替管理设备将消息转发给服务器，以及替服务器将消息转发给管理设备的操作流程。也就意味着，由管理设备与服务器之间通过消息交互，实现屏蔽操作。在图11中，方法流程包括步骤801至步骤805。
步骤801、管理设备向服务器发送第一请求消息。
步骤802、服务器接收管理设备发送的第一请求消息。
步骤803、服务器进行屏蔽设置。
需要说明的是，服务器实现屏蔽设置的过程可以参考步骤706或步骤707，在此不再赘述。
步骤804、服务器向管理设备发送响应消息。
步骤805、管理设备接收服务器发送的响应消息。
本发明实施例提供一种一号多终端来电管理方法，如图12所示，该方法包括步骤901至步骤903。需要说明的是，初始状态下，若存在关联的至少两个设备中存在一个 诸如智能手机的便携式终端，则可以默认由该便携式终端作为管理设备，而与该便携式终端存在关联关系的设备作为被管理设备。
步骤901、管理设备与被管理设备建立连接。
步骤902、当管理设备确定连接断开，则判断管理设备是否处于运动状态。
步骤903、如果管理设备处于运动状态，则管理设备管理服务器屏蔽入呼叫。
其中，管理设备管理服务器屏蔽入呼叫的方法，可以例如前面实施例步骤701至步骤711所述的方法，还可以为步骤801至步骤805的方法，在此不予赘述。
如图13所示，提供了一种可穿戴设备管理手机的应用场景示意图，其中，可穿戴设备由于可以随身携带，因此，接听电话的优先级较高，此时作为管理设备，手机为被管理设备。其中，可穿戴设备可以为手表、手环等便于用户随身携带的设备。在可穿戴设备在手机可连接范围内时，视为手机与可穿戴设备都在用户可操作的范围内，即在有电话呼入的情况下，用户可以通过手机或是可穿戴设备接听，不会出现误接的情况。而在可穿戴设备脱离手机可连接范围后，由于可穿戴设备已通过佩戴认证，因此，在本发明实施例中，可穿戴设备为满足预设条件的设备，会被视为管理设备，因此在该可穿戴设备脱离手机连接范围后，会触发被管理配置文件的入呼叫事件屏蔽过程，以确保在主叫终端发起呼叫后，用户可以通过随身佩戴的被视为管理设备的可穿戴设备接听电话。
需要说明的是，若作为被管理设备的手机处于未联网或是关机等无法实现来电接听的状态，那么考虑到当前被管理设备因无法接听电话也就无法引发电话误接的问题，则无需执行本发明实施例所提供的屏蔽入呼叫事件的操作流程。同样的，若作为管理设备的可穿戴设备处于未联网或是关机等无法实现来电接听的状态，考虑到用户此时只能通过被管理设备来完成电话的接听，因此，也无需触发上述屏蔽入呼叫事件的操作流程。
考虑到可穿戴设备中储存的电量往往较少，为了减少对可穿戴设备电量的消耗，在本发明实施例中，可以仅在可穿戴设备通过佩戴认证后才使可穿戴设备激活eSIM并附着网络，从而具备能够实现本发明实施例所示操作流程的条件。也正是因为通过佩戴认证的可穿戴设备的可随身携带性较高，因此，可以为经过认证的可穿戴设备配置较高的管理权限，即可穿戴设备为管理设备，而其他与该可穿戴设备关联且开通了一号多终端业务的设备则被视为被管理设备。
需要说明的是，除了用户主动通过可穿戴设备控制手机以外，在可穿戴设备脱离手机可连接范围后，可穿戴设备可以通过响铃、震动、呈现消息等提示方式，提醒用户触发本发明实施例的屏蔽入呼叫的操作流程。以呈现消息为例，在可穿戴设备的显示界面上，可以呈现如下内容“检测到已与手机断开连接，是否屏蔽其他设备通话？”并在可穿戴设备上提示用户完成指令的输入，比如，在可穿戴设备上设置用于表示“是”与“否”的按钮，或是在可穿戴设备的触摸屏幕上呈现供用户选择“是”与“否”的可触屏区域，或是提示用户通过语音的方式输入指令等，在此不一一例举。
如图14所示，提供了一种手机管理可穿戴的手表、平板电脑的应用场景示意图，其中，手机为管理设备，手表、平板电脑为被管理设备。在本发明实施例中，以双卡手机为例，在一号多卡(即一号多终端)的管理界面中，显示手机中插入的两张卡对 应的一号多卡信息，即图中卡1与卡2各自的一号多卡信息。用户可以通过触屏操作解绑卡1或是卡2下已经关联的其他设备(即被管理设备)，比如，手表1、平板电脑1。
在用户点击如图14所示的虚线框圈出的区域后，手机的显示界面会从一号多卡的管理界面跳转至卡1副卡管理界面(即与卡1具有一号多卡关系的其他profile)，在副卡管理界面中提供了多种功能选项，比如，通话功能、数据功能。用户可以通过触屏操作，选择开启或是关闭某一被管理设备的相应功能。为了便于用户管理，在本发明实施例中，在副卡管理界面中还可以显示各个被管理设备的当前状态，即离线或是在线。需要说明的是，图14仅为一种可能的实现方式的示意图，对于界面跳转的触发条件、管理内容的显示方式、副卡功能的种类等不进行限定。
在被管理设备开机且联网后，考虑到其他用户很可能通过被管理设备误接电话，即发生在被管理设备出现误接电话的场景，因此，管理设备可以在检测到被管理设备开机且联网后，通过响铃、震动、呈现消息等提示方式，提醒用户触发本发明实施例的远程管理中发送管理指令的操作流程，具体实现方式可以参考上述针对图13所提供的实现方式，在此不赘述。
在本发明实施例中，若手机处于解锁状态，则视为用户正在对该手机进行操作，即在主叫终端发起呼叫后，用户可以直接通过该手机进行电话接听，因此，会优先将该手机设置为管理设备供用户使用。
需要说明的是，结合上述图13、图14所示的示例可以得知，从管理设备和被管理设备的划分角度考虑，通常情况下，管理设备为用户试图接听电话所采用的设备。结合用户实际使用行为进行分析可以得出，设置管理设备的优先级从高到低可以依次为：已进行过佩戴认证且脱离手机范围的可穿戴设备、处于解锁状态的手机、平板电脑或车载设备等其他设备。当然，设置管理设备的方式不仅限于上述实现方式，还可以结合用户实际的使用场景，针对用户的需要进行调整，在此不限定。
本发明实施例提供一种一号多终端来电管理装置，该装置应用于被管理设备。该装置为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本发明能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本发明的范围。
本发明实施例可以根据上述方法示例对该装置进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本发明实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
如图15所示，为上述实施例中所涉及的一号多终端来电管理装置的一种可能的结构示意图。一号多终端来电管理装置10包括：处理模块11、通信模块12，在本发明实施例中，还可以包括存储模块13。其中，处理模块11用于支持一号多终端来电管理装 置10执行图4、图5中的步骤201至步骤204，图5中的步骤302；通信模块12用于支持一号多终端来电管理装置10执行图5中的步骤301，以及支持一号多终端来电管理装置10中各个模块之间进行数据交互，和/或支持该装置10所在管理设备与诸如服务器等其他设备之间的通信；存储模块13用于存储所需的程序代码和数据。
其中，处理模块11可以实现为处理器或控制器，例如可以为图1中的处理器101，其可以为是中央处理器(Central Processing Unit，CPU)，通用处理器，数字信号处理器(Digital Signal Processor，DSP)，专用集成电路(Application-Specific Integrated Circuit，ASIC)，现场可编程门阵列(Field Programmable Gate Array，FPGA)或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。其可以实现或执行结合本发明公开内容所描述的各种示例性的逻辑方框，模块和电路。所述处理器也可以是实现计算功能的组合，例如包含一个或多个微处理器组合，DSP和微处理器的组合等等。通信模块12可以实现为收发器、收发电路或通信接口等。存储模块13可以实现为存储器。
若处理模块11实现为处理器、通信模块12实现为收发器、存储模块13实现为存储器，则如图16所示，被管理设备20包括：处理器21、收发器22、存储器23，以及总线24。其中，处理器21、收发器22和存储器23通过总线24相互连接；总线24可以是外设部件互连标准(Peripheral Component Interconnect，PCI)总线或扩展工业标准结构(Extended Industry Standard Architecture，EISA)总线等。所述总线可以分为地址总线、数据总线、控制总线等。为便于表示，图16中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
本发明实施例提供一种一号多终端来电管理装置，该装置应用于服务器。该装置为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本发明能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本发明的范围。
本发明实施例可以根据上述方法示例对该装置进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本发明实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
如图17所示，为上述实施例中所涉及的一号多终端来电管理装置的一种可能的结构示意图。一号多终端来电管理装置30包括：处理模块31、通信模块32，在本发明实施例中，还可以包括存储模块33。其中，处理模块31用于支持一号多终端来电管理装置30执行图8中的步骤602和步骤603；通信模块32用于支持一号多终端来电管理装置30执行图8中的步骤601，以及支持一号多终端来电管理装置30中各个模块之间进行数据交互，和/或支持该装置30所在管理设备与诸如被管理设备等其他设备之间的通信；存储模块33用于存储所需的程序代码和数据。
其中，处理模块31可以实现为处理器或控制器，例如可以是CPU，通用处理器，DSP，ASIC，FPGA或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。其可以实现或执行结合本发明公开内容所描述的各种示例性的逻辑方框，模块和电路。所述处理器也可以是实现计算功能的组合，例如包含一个或多个微处理器组合，DSP和微处理器的组合等等。通信模块32可以实现为收发器、收发电路或通信接口等。存储模块33可以实现为存储器。
若处理模块31实现为处理器、通信模块32实现为通信接口、存储模块33实现为存储器，则如图18所示，服务器40包括：处理器41、通信接口42、存储器43，以及总线44。其中，处理器41、通信接口42和存储器43通过总线44相互连接；总线44可以是PCI总线或EISA总线等。所述总线可以分为地址总线、数据总线、控制总线等。为便于表示，图18中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
本发明实施例提供一种一号多终端来电管理系统50，如图19所示，该系统50包括管理设备51、ES52和被管理设备53。
其中，管理设备51通过ES52，向被管理设备53发送远程管理指令。其中，远程管理指令包括被管理设备中的被管理配置文件的标识；
被管理设备51接收远程管理指令，并确定与被管理配置文件的标识对应的通信子单元，且响应于远程管理指令，对与被管理配置文件的标识对应的通信子单元进行入呼叫屏蔽设置。
被管理设备53解析入呼叫，得到来电信息。其中，来电信息包括被叫标识。
若被管理设备53已执行过对被叫标识对应的通信子单元的入呼叫屏蔽设置，则不响应入呼叫事件。
在一种可能的实现方式中，管理设备51解析入呼叫，得到来电信息，若管理设备51未执行过对被叫标识对应的通信子单元的入呼叫屏蔽设置，则响应入呼叫事件。
本发明实施例提供一种一号多终端来电管理系统60，如图20所示，该系统60包括管理设备61、ES62和服务器63。
其中，管理设备61通过ES62，向服务器63发送远程管理指令。其中，远程管理指令包括被管理设备的被管理配置文件的标识。
服务器63接收远程管理指令，删除或冻结标识对应的路由信息，以使被管理设备中的标识对应的通信子单元无法响应入呼叫事件。
在一种可能的实现方式中，管理设备61解析入呼叫，得到来电信息。其中，来电信息包括被叫标识。若管理设备61未执行过对被叫标识对应的通信子单元的入呼叫屏蔽设置，则响应入呼叫事件。
需要说明的是，在本发明实施例中，管理设备61可以通过ES62实现在服务器63上，对被管理设备的管理，也可以不通过ES62，直接与服务器63进行通信，即直接在服务器63上实现对被管理设备的管理。
本发明实施例提供一种计算机程序产品，该计算机程序产品包括软件代码，该软件代码用于执行如图4、图5所示的方法流程。
本发明实施例提供一种计算机程序产品，该计算机程序产品包括软件代码，该软 件代码用于执行如图8所示的方法流程。
本发明实施例提供一种计算机存储介质，包括指令。当该指令在电子设备上运行时，使得该电子设备执行如图4、图5所示的方法流程。
本发明实施例提供一种计算机存储介质，包括指令。当该指令在电子设备上运行时，使得该电子设备执行如图8所示的方法流程。
本领域技术人员应该可以意识到，在上述一个或多个示例中，本发明实施例所描述的功能可以用硬件、软件、固件或它们的任意组合来实现。当使用软件实现时，可以将这些功能存储在计算机可读介质中或者作为计算机可读介质上的一个或多个指令或代码进行传输。计算机可读介质包括计算机存储介质和通信介质，其中通信介质包括便于从一个地方向另一个地方传送计算机程序的任何介质。存储介质可以是通用或专用计算机能够存取的任何可用介质。
以上所述的具体实施方式，对本发明实施例的目的、技术方案和有益效果进行了进一步详细说明，所应理解的是，以上所述仅为本发明的具体实施方式而已，并不用于限定本发明的保护范围，凡在本发明实施例的技术方案的基础之上，所做的任何修改、等同替换、改进等，均应包括在本发明实施例的保护范围之内。

Claims (34)

  1. 一种一号多终端来电管理方法，其特征在于，所述方法包括：
    被管理设备解析入呼叫，得到来电信息，所述来电信息包括被叫标识；
    所述被管理设备确定与所述被叫标识对应的通信子单元，所述通信子单元用于在所述被管理设备上实现对应于所述配置文件的通信功能，所述通信功能至少包括接听指向所述配置文件的入呼叫；
    若所述被管理设备响应于远程管理服务器ES发送的远程管理指令，已执行过对所述通信子单元的入呼叫屏蔽设置，则不响应入呼叫事件，所述远程管理指令包括所述被管理设备中的被管理配置文件的标识。
  2. 根据权利要求1所述的方法，其特征在于，在所述被管理设备不响应入呼叫事件之前，所述方法还包括：
    所述被管理设备接收ES发送的远程管理指令；
    所述被管理设备确定与所述被管理配置文件的标识对应的通信子单元，并响应于所述远程管理指令，对与所述被管理配置文件的标识对应的通信子单元进行入呼叫屏蔽设置。
  3. 根据权利要求2所述的方法，其特征在于，所述被管理设备对与所述被管理配置文件的标识对应的通信子单元进行入呼叫屏蔽设置包括：
    所述被管理设备使用来电过滤技术，进行对所述被管理配置文件的标识对应的通信子单元的入呼叫屏蔽设置；
    或者，
    所述被管理设备为所述与所述被管理配置文件的标识对应的通信子单元设置空的来电接听白名单，以屏蔽不属于所述来电接听白名单中的移动台综合业务数字网号码MSISDN作为主叫号码发起的呼叫；
    或者，
    所述被管理设备为所述与所述被管理配置文件的标识对应的通信子单元增加指定标识，以使所述通信子单元检测到自身具有指定标识后，触发对入呼叫事件进行入呼叫屏蔽操作，所述指定标识用于表示所述管理设备已执行过对所述通信子单元的入呼叫屏蔽设置。
  4. 根据权利要求1至3中任意一项所述的方法，其特征在于，所述不响应入呼叫事件包括：拒绝所述入呼叫事件或忽略所述入呼叫事件。
  5. 根据权利要求1至4中任意一项所述的方法，其特征在于，所述被叫标识包括临时移动用户标识TMSI、国际移动用户识别码IMSI、移动台综合业务数字网号码MSISDN中的一项。
  6. 根据权利要求1至5中任意一项所述的方法，其特征在于，在所述被管理设备确定与所述被叫标识对应的通信子单元之后，所述方法还包括：
    若所述通信子单元未进行过所述入呼叫屏蔽设置，则所述被管理设备提示用户响应入呼叫事件。
  7. 一种一号多终端来电管理方法，其特征在于，所述方法包括：
    管理设备通过远程管理服务器ES，向被管理设备发送远程管理指令，所述远程管理指令包括所述被管理设备中的被管理配置文件的标识；
    所述被管理设备接收所述远程管理指令，并确定与所述被管理配置文件的标识对应的通信子单元，且响应于所述远程管理指令，对与所述被管理配置文件的标识对应的通信子单元进行入呼叫屏蔽设置；
    所述被管理设备解析入呼叫，得到来电信息，所述来电信息包括被叫标识；
    若所述被管理设备已执行过对所述被叫标识对应的通信子单元的入呼叫屏蔽设置，则不响应入呼叫事件。
  8. 根据权利要求7所述的方法，其特征在于，所述方法包括；
    所述管理设备解析所述入呼叫，得到所述来电信息；
    若所述管理设备未执行过对所述被叫标识对应的通信子单元的入呼叫屏蔽设置，则响应所述入呼叫事件。
  9. 一种一号多终端来电管理方法，其特征在于，所述方法包括：
    管理设备与被管理设备建立连接，所述管理设备与所述被管理设备为具有相同移动台综合业务数字网号码MSISDN的终端；
    当所述管理设备确定所述连接断开，则判断所述管理设备是否处于运动状态；
    如果所述管理设备处于运动状态，则所述管理设备管理所述被管理设备屏蔽入呼叫。
  10. 根据权利要求9所述的方法，其特征在于，所述如果所述管理设备处于运动状态，则所述管理设备管理所述被管理设备屏蔽入呼叫，包括：
    如果所述管理设备处于运动状态，且所述运动状态保持预设时长，则所述管理设备管理所述被管理设备屏蔽入呼叫。
  11. 根据权利要求9或10所述的方法，其特征在于，所述管理设备管理所述被管理设备屏蔽入呼叫，包括：
    所述管理设备向所述被管理设备发送远程管理指令，所述远程管理指令包括被管理设备的被管理配置文件的标识；
    所述被管理设备接收所述远程管理指令，并确定与所述被管理配置文件的标识对应的通信子单元；
    所述被管理设备响应于所述远程管理指令，对所述通信子单元进行入呼叫屏蔽设置。
  12. 根据权利要求11所述的方法，其特征在于，在所述对所述通信子单元进行入呼叫屏蔽设置之后，所述方法包括：
    所述被管理设备解析入呼叫，得到来电信息，所述来电信息包括被叫标识；
    若所述被管理设备已执行过对所述被叫标识对应的通信子单元的入呼叫屏蔽设置，则不响应入呼叫事件；
    所述管理设备解析所述入呼叫，得到所述来电信息；
    若所述管理设备未执行过对所述被叫标识对应的通信子单元的入呼叫屏蔽设置，则响应所述入呼叫事件。
  13. 一种一号多终端来电管理方法，其特征在于，所述方法包括：
    服务器接收远程管理服务器ES发送的远程管理指令，所述远程管理指令包括被管理设备中的被管理配置文件的标识；
    所述服务器响应于所述远程管理指令，删除或冻结所述标识对应的路由信息，以使所述被管理设备中的所述标识对应的通信子单元无法响应入呼叫事件。
  14. 根据权利要求13所述的方法，其特征在于，在所述服务器响应于所述远程管理指令，删除或冻结所述标识对应的路由信息之后，所述方法还包括：
    在所述服务器接收到路由查询请求，且响应于所述路由查询请求，查询到已被冻结的所述标识对应的路由信息，则所述服务器不反馈所述已被冻结的所述标识对应的路由信息。
  15. 一种一号多终端来电管理方法，其特征在于，所述方法包括：
    管理设备通过远程管理服务器ES，向服务器发送远程管理指令，所述远程管理指令包括被管理设备的被管理配置文件的标识；
    所述服务器接收所述远程管理指令，删除或冻结所述标识对应的路由信息，以使所述被管理设备中的所述标识对应的通信子单元无法响应入呼叫事件。
  16. 根据权利要求15所述的方法，其特征在于，所述方法包括
    所述管理设备解析入呼叫，得到来电信息，所述来电信息包括被叫标识；
    若所述管理设备未执行过对所述被叫标识对应的通信子单元的入呼叫屏蔽设置，则响应入呼叫事件。
  17. 一种一号多终端来电管理方法，其特征在于，所述方法包括：
    管理设备与被管理设备建立连接，所述管理设备与所述被管理设备为具有相同移动台综合业务数字网号码MSISDN的终端；
    当所述管理设备确定所述连接断开，则判断所述管理设备是否处于运动状态；
    如果所述管理设备处于运动状态，则所述管理设备管理服务器屏蔽入呼叫。
  18. 根据权利要求17所述的方法，其特征在于，所述如果所述管理设备处于运动状态，则所述管理设备管理服务器屏蔽入呼叫，包括：
    如果所述管理设备处于运动状态，且所述运动状态保持预设时长，则所述管理设备管理服务器屏蔽入呼叫。
  19. 根据权利要求17或18所述的方法，其特征在于，所述管理设备管理服务器屏蔽入呼叫，包括：
    所述管理设备向所述服务器发送远程管理指令，所述远程管理指令包括被管理设备的被管理配置文件的标识；
    所述服务器接收所述远程管理指令，并响应于所述远程管理指令，删除或冻结所述标识对应的路由信息，以使所述被管理设备中的所述标识对应的通信子单元无法响应入呼叫事件。
  20. 根据权利要求19所述的方法，其特征在于，在所述删除或冻结所述标识对应 的路由信息之后，所述方法包括：
    所述管理设备解析所述入呼叫，得到所述来电信息，所述来电信息包括被叫标识；
    若所述管理设备未执行过对所述被叫标识对应的通信子单元的入呼叫屏蔽设置，则响应所述入呼叫事件；
    若所述被管理设备已执行过对所述被叫标识对应的通信子单元的入呼叫屏蔽设置，则不响应入呼叫事件。
  21. 一种一号多终端来电管理装置，其特征在于，所述装置包括：
    处理模块，用于解析入呼叫，得到来电信息，所述来电信息包括被叫标识；
    所述处理模块，还用于确定与所述被叫标识对应的通信子单元，所述通信子单元用于在所述装置上实现对应于所述配置文件的通信功能，所述通信功能至少包括接听指向所述配置文件的入呼叫；
    所述处理模块，还用于若所述装置响应于远程管理服务器ES发送的远程管理指令，已执行过对所述通信子单元的入呼叫屏蔽设置，则不响应入呼叫事件，所述远程管理指令包括所述装置中的被管理配置文件的标识。
  22. 根据权利要求21所述的装置，其特征在于，所述装置还包括：
    通信模块，用于接收ES发送的远程管理指令；
    所述处理模块，还用于确定与所述被管理配置文件的标识对应的通信子单元，并响应于所述通信模块接收到的所述远程管理指令，对与所述被管理配置文件的标识对应的通信子单元进行入呼叫屏蔽设置。
  23. 根据权利要求22所述的装置，其特征在于，所述处理模块，还用于：
    使用来电过滤技术，进行对所述被管理配置文件的标识对应的通信子单元的入呼叫屏蔽设置；
    或者，
    为所述与所述被管理配置文件的标识对应的通信子单元设置空的来电接听白名单，以屏蔽不属于所述来电接听白名单中的移动台综合业务数字网号码MSISDN作为主叫号码发起的呼叫；
    或者，
    为所述与所述被管理配置文件的标识对应的通信子单元增加指定标识，以使所述通信子单元检测到自身具有指定标识后，触发对入呼叫事件进行入呼叫屏蔽操作设置，所述指定标识用于表示所述管理设备已执行过对所述通信子单元的入呼叫屏蔽设置。
  24. 根据权利要求21至23中任意一项所述的装置，其特征在于，所述不响应入呼叫事件包括：拒绝所述入呼叫事件或忽略所述入呼叫事件。
  25. 根据权利要求21至24中任意一项所述的装置，其特征在于，所述被叫标识包括临时移动用户标识TMSI、国际移动用户识别码IMSI、移动台综合业务数字网号码MSISDN中的一项。
  26. 根据权利要求21至25中任意一项所述的装置，其特征在于，所述处理模块，还用于：
    若所述通信子单元未进行过所述入呼叫屏蔽设置，则提示用户响应入呼叫事件。
  27. 一种一号多终端来电管理装置，其特征在于，所述装置包括：
    通信模块，用于接收远程管理服务器ES发送的远程管理指令，所述远程管理指令包括被管理设备中的被管理配置文件的标识；
    处理模块，用于响应于所述通信模块接收到的所述远程管理指令，删除或冻结所述标识对应的路由信息，以使所述被管理设备中的所述标识对应的通信子单元无法响应入呼叫事件。
  28. 根据权利要求27所述的装置，其特征在于，所述处理模块，还用于：
    在所述服务器接收到路由查询请求，且响应于所述路由查询请求，查询到已被冻结的所述标识对应的路由信息，则不反馈所述已被冻结的所述标识对应的路由信息。
  29. 一种被管理设备，其特征在于，所述被管理设备至少包括处理器，所述处理器用于执行上述权利要求1至6中任意一项所述的方法。
  30. 一种服务器，其特征在于，所述服务器至少包括处理器，所述处理器用于执行上述权利要求13或14中任意一项所述的方法。
  31. 一种计算机程序产品，其特征在于，所述计算机程序产品包括软件代码，所述软件代码用于执行上述权利要求1-6中任意一项所述的方法。
  32. 一种计算机程序产品，其特征在于，所述计算机程序产品包括软件代码，所述软件代码用于执行上述权利要求13或14所述的方法。
  33. 一种计算机存储介质，包括指令，其特征在于，当所述指令在电子设备上运行时，使得所述电子设备执行如权利要求1-6中任意一项所述的方法。
  34. 一种计算机存储介质，包括指令，其特征在于，当所述指令在电子设备上运行时，使得所述电子设备执行如权利要求13或14所述的方法。
PCT/CN2017/107715 2017-06-26 2017-10-25 一号多终端的来电管理方法、装置、被管理设备及服务器 WO2019000738A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
EP17916138.5A EP3637947B1 (en) 2017-06-26 2017-10-25 Multi-sim incoming call management method, apparatus, managed device and server
CN201780012820.4A CN108702422B (zh) 2017-06-26 2017-10-25 一号多终端的来电管理方法、装置、被管理设备及服务器
US16/624,133 US10841422B2 (en) 2017-06-26 2017-10-25 Multi-SIM call management method and apparatus, managed device, and server

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710494840.1 2017-06-26
CN201710494840 2017-06-26

Publications (1)

Publication Number Publication Date
WO2019000738A1 true WO2019000738A1 (zh) 2019-01-03

Family

ID=64740964

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/107715 WO2019000738A1 (zh) 2017-06-26 2017-10-25 一号多终端的来电管理方法、装置、被管理设备及服务器

Country Status (3)

Country Link
US (1) US10841422B2 (zh)
EP (1) EP3637947B1 (zh)
WO (1) WO2019000738A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10999158B2 (en) * 2018-09-11 2021-05-04 Apple Inc. User interfaces for controlling or presenting information about multiple cellular identifiers on an electronic device

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1206156A2 (en) * 2000-11-10 2002-05-15 NTT DoCoMo, Inc. Mobile communication method and mobile communication system
CN102104652A (zh) * 2011-03-07 2011-06-22 华为技术有限公司 呼叫处理方法和呼叫服务器
CN102761853A (zh) * 2011-04-25 2012-10-31 中兴通讯股份有限公司 终端管理系统及方法
CN105682066A (zh) * 2016-03-30 2016-06-15 中国联合网络通信集团有限公司 终端呼叫转接方法、装置及系统
CN106717113A (zh) * 2014-09-22 2017-05-24 Sk电信有限公司 多终端通信服务装置及方法

Family Cites Families (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6700957B2 (en) 1998-12-07 2004-03-02 Curio, Ltd. Caller ID system with retransmitted caller ID information
US7983680B2 (en) 2005-08-10 2011-07-19 Nextel Communications Inc. System and method for converged network services
CN100479481C (zh) 2005-12-16 2009-04-15 北京邮电大学 “个人统一号码”业务的实现方法
CN101119532A (zh) 2007-06-18 2008-02-06 中兴通讯股份有限公司 一种多呼业务的实现方法
CN101267474B (zh) 2008-02-29 2012-05-09 中兴通讯股份有限公司 一种一号多机业务的实现方法
CN102469425B (zh) 2010-11-09 2015-08-12 中国移动通信集团北京有限公司 一种实现一号通业务的方法、装置及系统
CN102651860B (zh) 2011-02-24 2014-12-31 华为终端有限公司 一种设备管理方法及装置
KR102013942B1 (ko) 2012-07-19 2019-08-23 삼성전자주식회사 멀티 심 카드가 구비된 전자 장치 및 방법
US20150350146A1 (en) * 2014-05-29 2015-12-03 Apple Inc. Coordination of message alert presentations across devices based on device modes
KR102374740B1 (ko) * 2015-05-15 2022-03-16 삼성전자 주식회사 전자 장치 및 양방향 통신 운용 방법
US20190069162A1 (en) * 2016-03-09 2019-02-28 Telefonaktiebolaget Lm Ericsson (Publ) Methods providing service limitation and related communication devices and network nodes
CN105975847A (zh) 2016-05-26 2016-09-28 广东小天才科技有限公司 一种学生智能设备的多终端控制方法及系统
US9801158B1 (en) * 2016-06-14 2017-10-24 Verizon Patent And Licensing Inc. Selective call routing and notification for multi-endpoint terminals

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1206156A2 (en) * 2000-11-10 2002-05-15 NTT DoCoMo, Inc. Mobile communication method and mobile communication system
CN102104652A (zh) * 2011-03-07 2011-06-22 华为技术有限公司 呼叫处理方法和呼叫服务器
CN102761853A (zh) * 2011-04-25 2012-10-31 中兴通讯股份有限公司 终端管理系统及方法
CN106717113A (zh) * 2014-09-22 2017-05-24 Sk电信有限公司 多终端通信服务装置及方法
CN105682066A (zh) * 2016-03-30 2016-06-15 中国联合网络通信集团有限公司 终端呼叫转接方法、装置及系统

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3637947A4

Also Published As

Publication number Publication date
US10841422B2 (en) 2020-11-17
EP3637947A1 (en) 2020-04-15
US20200137229A1 (en) 2020-04-30
EP3637947A4 (en) 2020-05-20
EP3637947B1 (en) 2023-08-02

Similar Documents

Publication Publication Date Title
US10798552B2 (en) Emergency call-for-help method and system based on fingerprint identification for mobile terminal, and mobile terminal
WO2018000290A1 (zh) 管理蓝牙连接的方法、蓝牙主设备和装置
US9008298B2 (en) Automatic denial of call request
CN109618316B (zh) 网络共享方法、移动终端及存储介质
JP7245913B2 (ja) イベント処理方法、ロケーションアプリケーション機器、ユーザ機器、及びコンピュータプログラム
CN103379448A (zh) 在取消连接时减少等待时间的方法和电子设备
WO2019128191A1 (zh) 一种用于处理呼叫请求的方法、移动终端及可读存储介质
CN108810833B (zh) 手机号码绑定信息管理方法、装置及计算机可读存储介质
CN108702422B (zh) 一号多终端的来电管理方法、装置、被管理设备及服务器
CN106303085B (zh) 移动终端以及保密通话的方法和装置
CN106998553B (zh) 一种设备身份识别方法、计算机设备及存储介质
WO2015024393A1 (zh) 发送短信的方法、装置及终端
CN109104722B (zh) 终端访问方法、装置及计算机可读存储介质
WO2019000738A1 (zh) 一号多终端的来电管理方法、装置、被管理设备及服务器
CN108833820B (zh) 视频通话方法及相关产品
CN109257746A (zh) 通信建立方法、通信方法、终端及计算机可读存储介质
CN109660470A (zh) 一种数据流量管控方法、终端及计算机可读存储介质
CN106255117B (zh) 伪基站识别方法及装置
CN112887195B (zh) 语音呼叫方法、语音呼叫设备及计算机可读存储介质
WO2018082044A1 (zh) 一种网络热点控制的方法以及相关设备
EP3962174B1 (en) Network switching resource determining method and network switching resource configuration method
CN108668282B (zh) 一种信息处理方法、终端及计算机可读存储介质
JP6161213B2 (ja) 音声通知システム、音声管理サーバ、及び端末管理サーバ
CN107528973B (zh) 一种数据的处理方法、终端以及音频盾
CN111601300A (zh) 多卡的pdu会话建立方法及相关设备

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: 17916138

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2017916138

Country of ref document: EP

Effective date: 20191205

NENP Non-entry into the national phase

Ref country code: DE