CN113973154A

CN113973154A - Electronic device, method, computer-readable medium, and information processing apparatus

Info

Publication number: CN113973154A
Application number: CN202010710261.8A
Authority: CN
Inventors: 王鑫
Original assignee: Arris Enterprises LLC
Current assignee: Arris Enterprises LLC
Priority date: 2020-07-22
Filing date: 2020-07-22
Publication date: 2022-01-25

Abstract

Provided are an electronic device, a method, a computer-readable medium, and an information processing apparatus. The electronic device includes: a memory having instructions stored thereon; a processor configured to execute instructions stored on the memory to cause the electronic device to perform operations comprising: monitoring the number of times a call by a calling party is rejected by a called party, the calling party having a calling number; comparing the number of rejections to a predetermined threshold; and determining that the calling number of the calling party is to be set into a blacklist if the number of rejections exceeds the predetermined threshold.

Description

Electronic device, method, computer-readable medium, and information processing apparatus

Technical Field

The present disclosure relates to the field of communications, and in particular, to an electronic device, a method, a computer-readable medium, and an information processing apparatus.

Background

In the field of communications, users often receive some nuisance calls. To avoid being disturbed by a crank call, the user may set the crank call number to a blacklist.

In the prior art, in order to set the harassing phone numbers in the blacklist, a user is generally required to manually input the harassing phone numbers in the blacklist in turn, which is too complicated for the user to operate, low in efficiency and very inconvenient.

Disclosure of Invention

Some aspects of the present disclosure relate to an electronic device for use with a client device, the electronic device comprising: a memory having instructions stored thereon; a processor configured to execute instructions stored on the memory to cause the electronic device to perform operations comprising: monitoring the number of times a call by a calling party is rejected by a called party, the calling party having a calling number; comparing the number of rejections to a predetermined threshold; and determining that the calling number of the calling party is to be set into a blacklist if the number of rejections exceeds the predetermined threshold.

In some embodiments, said monitoring the number of times a call by the calling party is rejected by the called party comprises: monitoring whether a called party presses a particular key on a client device or a combination of two or more keys on the client device when called by a calling party; and in the event that the called party presses a particular key on the client device or a combination of two or more keys on the client device while being called by the calling party, determining that the call of the calling party is rejected by the called party and increasing the number of times the call of the calling party is rejected by the called party by 1.

In some embodiments, the operations further comprise: in case it is determined that the calling number of the calling party is to be set to the blacklist, the called party is notified of the calling number to be set to the blacklist via at least one of an indicator light, a ring tone, and voice.

In some embodiments, in case of notification to the called party via voice, detailed information of the calling number to be set to the blacklist is broadcasted to the called party via voice.

In some embodiments, the operations further comprise: in case of receiving confirmation from a called party that the calling number of the calling party is to be set to a blacklist, or in case of default, automatically setting the calling number of the calling party to a blacklist.

In some embodiments, the operations further comprise: enabling or disabling setting of a calling number of the calling party into a blacklist via at least one of a Graphical User Interface (GUI), an Application (APP) and protocol signaling.

In some embodiments, the protocol signaling includes at least one of Simple Network Management Protocol (SNMP) and technical report 069(TR 069).

Other aspects of the present disclosure relate to a method for use with an electronic device and a client device, the method comprising: monitoring the number of times a call by a calling party is rejected by a called party, the calling party having a calling number; comparing the number of rejections to a predetermined threshold; and determining that the calling number of the calling party is to be set into a blacklist if the number of rejections exceeds the predetermined threshold.

In some embodiments of the method, the monitoring the number of times the call of the calling party is rejected by the called party comprises: monitoring whether a called party presses a particular key on a client device or a combination of two or more keys on the client device when called by a calling party; and in the event that the called party presses a particular key on the client device or a combination of two or more keys on the client device while being called by the calling party, determining that the call of the calling party is rejected by the called party and increasing the number of times the call of the calling party is rejected by the called party by 1.

In some embodiments, the method further comprises: in case it is determined that the calling number of the calling party is to be set to the blacklist, the called party is notified of the calling number to be set to the blacklist via at least one of an indicator light, a ring tone, and voice.

In some embodiments of the method, in case of notification to the called party via voice, detailed information of the calling number to be set to the blacklist is broadcasted to the called party via voice.

In some embodiments, the method further comprises: in case of receiving confirmation from a called party that the calling number of the calling party is to be set to a blacklist, or in case of default, automatically setting the calling number of the calling party to a blacklist.

In some embodiments, the method further comprises: enabling or disabling setting of a calling number of the calling party into a blacklist via at least one of a Graphical User Interface (GUI), an Application (APP) and protocol signaling.

In some embodiments of the method, the protocol signaling comprises at least one of Simple Network Management Protocol (SNMP) and technical report 069(TR 069).

Other aspects of the disclosure relate to a non-transitory computer readable medium for use with a processor and a client device, the non-transitory computer readable medium having instructions stored thereon, which when executed by the processor, cause the processor to perform a method as in any one of the preceding embodiments.

Other aspects of the disclosure relate to an information processing apparatus comprising means for performing the method as set forth in any of the preceding embodiments.

Drawings

For a better understanding of the present disclosure, and to show how the same may be carried into effect, reference will now be made, by way of example, to the accompanying drawings, in which:

fig. 1 is a block diagram that schematically illustrates a network environment, in accordance with an embodiment of the present disclosure.

Fig. 2 is a schematic block diagram schematically illustrating an information processing apparatus that may be used to implement a method according to an embodiment of the present disclosure.

Fig. 3 is a flow diagram that schematically illustrates a method for use with an electronic device and a client device, in accordance with an embodiment of the present disclosure.

Fig. 4 is a flow chart schematically illustrating a process for monitoring the number of times a call of a calling party is rejected by a called party, according to an embodiment of the present disclosure.

Fig. 5 is a flow diagram that schematically illustrates a method for use with an electronic device and a client device, in accordance with an embodiment of the present disclosure.

Fig. 6 is a flow diagram that schematically illustrates a method for use with an electronic device and a client device, in accordance with an embodiment of the present disclosure.

Fig. 7 is a flow diagram that schematically illustrates a method for use with an electronic device and a client device, in accordance with an embodiment of the present disclosure.

Note that like reference numerals refer to corresponding parts throughout the drawings. Further, multiple instances of the same part are specified by a common prefix separated from the instance number by a dash.

Detailed Description

The following detailed description is made with reference to the accompanying drawings and is provided to assist in a comprehensive understanding of various exemplary embodiments of the disclosure. The following description includes various details to aid understanding, but these details are to be regarded as examples only and are not intended to limit the disclosure, which is defined by the appended claims and their equivalents. The words and phrases used in the following description are used only to provide a clear and consistent understanding of the disclosure. In addition, descriptions of well-known structures, functions, and configurations may be omitted for clarity and conciseness. Those of ordinary skill in the art will recognize that various changes and modifications of the examples described herein can be made without departing from the spirit and scope of the disclosure.

As described above, in the prior art, in order to set the crank call numbers in the blacklist, the user is usually required to manually input the crank call numbers in turn into the blacklist, which is too complicated for the user to operate, low in efficiency and very inconvenient.

According to the embodiments of the present disclosure, since whether to automatically set the calling number of the calling party to the blacklist can be determined by monitoring whether the number of times the calling party is rejected by the called party reaches a predetermined number of times, efficiency of the user in setting the calling number to the blacklist can be improved, and convenience of the user in setting the calling number to the blacklist can be improved.

Fig. 1 is a block diagram that schematically illustrates a network environment 100, in accordance with an embodiment of the present disclosure. In embodiments, the electronic device 103 may transmit communications to and from one or more client devices 101. For example, one or more client devices 101 may be provided to receive one or more voice services, one or more data services, one or more video services, and/or other services through one or more electronic devices 103. Note that although only one client device 101 and one electronic device 103 are shown in fig. 1, the client device 101 and the electronic device 103 may be any number, and the present disclosure is not limited thereto.

In embodiments, the client devices 101 may include various devices, such as Digital Enhanced Cordless Telecommunications (DECT) telephones or other telephones similar to or compatible with DECT telephones, computers, and any other device capable of sending and/or receiving communications using DECT telephones or otherwise. Additionally, in embodiments, the electronic device 103 may include a Media Terminal Adapter (MTA), a modem, and any access point or other device that may transfer communications to and from the client device 101. Note that the present disclosure does not specifically limit the types of the client device 101 and the electronic device 103.

In an embodiment, the electronic device 103 may transmit communications between the client device 101 and the communication network 105. In embodiments, the communication network 105 may include various networks, such as a Public Switched Telephone Network (PSTN), coaxial cable, fiber optics, and so forth. Note that the present disclosure does not specifically limit the type of communication network 105.

We now describe embodiments of an information processing apparatus that may perform at least some operations in communication technology. Fig. 2 is a schematic block diagram schematically illustrating an information processing apparatus 700 that may be used to implement a method according to an embodiment of the present disclosure. For example, information processing apparatus 700 may include components in network environment 100, such as one of: one or more client devices 101 and/or one or more electronic devices 103. This information processing apparatus 700 includes a processing subsystem 710, a memory subsystem 712, and a networking subsystem 714. Processing subsystem 710 includes one or more devices configured to perform computing operations. For example, processing subsystems 710 may include one or more microprocessors, ASICs, microcontrollers, programmable logic devices, Graphics Processor Units (GPUs), and/or one or more Digital Signal Processors (DSPs).

Memory subsystem 712 includes one or more devices for storing data and/or instructions for processing subsystem 710 and networking subsystem 714. For example, memory subsystem 712 may include Dynamic Random Access Memory (DRAM), Static Random Access Memory (SRAM), and/or other types of memory (sometimes collectively or individually referred to as "computer-readable storage media"). In some embodiments, instructions for use in memory subsystem 712 of processing subsystem 710 include: one or more program modules or sets of instructions (such as program instructions 722 or operating system 724) that may be executed by processing subsystem 710. Note that one or more computer programs may constitute a computer program mechanism. Further, instructions in the various modules in memory subsystem 712 may be implemented as follows: a high-level programming language, an object-oriented programming language, and/or in assembly or machine language. Further, the programming language may be compiled or interpreted, e.g., configurable or configured (used interchangeably in this discussion), for execution by the processing subsystem 710.

Additionally, memory subsystem 712 may include mechanisms for controlling access to memory. In some embodiments, memory subsystem 712 includes a memory hierarchy that includes one or more caches coupled to memory in information processing device 700. In some of these embodiments, one or more of the caches are located in processing subsystem 710.

In some embodiments, memory subsystem 712 is coupled to one or more high capacity mass storage devices (not shown). For example, the memory subsystem 712 may be coupled to a magnetic or optical drive, a solid state drive, or another type of mass storage device. In these embodiments, information handling apparatus 700 may use memory subsystem 712 for fast-access storage of frequently used data, while mass storage devices are used to store infrequently used data.

Networking subsystem 714 includes one or more devices configured to couple to and communicate over a wired and/or wireless network (i.e., to perform network operations), including: control logic 716, interface circuitry 718, and one or more antennas 720 (or antenna elements). Although fig. 2 includes one or more antennas 720, in some embodiments, information-handling device 700 includes one or more nodes, such as node 708, e.g., a pad, that may be coupled to one or more antennas 720. Thus, information processing apparatus 700 may or may not include one or more antennas 720. For example, networking subsystem 714 may include a bluetooth networking system, a cellular networking system (e.g., a 3G/4G/5G network such as UMTS, LTE, etc.), a USB networking system, a networking system based on the standards described in IEEE 802.11 (e.g., a Wi-Fi networking system), an ethernet networking system, and/or another networking system.

In some embodiments, the transmit antenna radiation pattern of the information processing device 700 may be adapted or changed using a pattern shaper (such as a reflector) in one or more antennas 720 (or antenna elements), which one or more antennas 720 may be independently and selectively electrically coupled to ground to direct the transmit antenna radiation pattern in different directions. Thus, if one or more antennas 720 include N antenna radiation pattern shapers, one or more antennas 720 may have 2N different antenna radiation pattern configurations. More generally, a given antenna radiation pattern may include the amplitude and/or phase of a signal specifying the direction of the main lobe or main lobe of the given antenna radiation pattern, as well as so-called "exclusion zones" or "exclusion zones" (sometimes referred to as "gaps" or "nulls"). Note that the exclusion zone for a given antenna radiation pattern includes a low intensity region of the given antenna radiation pattern. Although the intensity is not necessarily zero in the exclusion zone, the intensity may be below a threshold, such as 4dB or below the peak gain of a given antenna radiation pattern. Thus, a given antenna radiation pattern may include a local maximum (e.g., a main beam) that points the maximum in gain in the direction of the information processing device of interest, and one or more local minima that reduce gain in the direction of other information processing devices that are not of interest. In this manner, a given antenna radiation pattern may be selected such that undesirable communications (such as communications with other information processing devices) are avoided to reduce or eliminate adverse effects, such as interference or crosstalk.

Networking subsystem 714 includes a processor, controller, radio/antenna, jack/plug, and/or other devices for coupling to, communicating over, and processing data and events for each supported network system. Note that the mechanisms sometimes used to couple to, communicate over, and process data and events on the network for each network system are collectively referred to as the "network interfaces" of the network systems. Further, in some embodiments, a "network" or "connection" between information processing devices does not yet exist. Thus, the information processing apparatus 700 can use mechanisms in the networking subsystem 714 to perform simple wireless communication between information processing apparatuses, for example, to transmit frames and/or scan frames transmitted by other information processing apparatuses.

Within information handling device 700, processing subsystem 710, memory subsystem 712, and networking subsystem 714 are coupled together using bus 728. Bus 728 may include electrical, optical, and/or electro-optical connections that subsystems may be used to communicate commands, data, and the like. Although only one bus 728 is shown for clarity, different embodiments may include different numbers or configurations of electrical, optical, and/or electro-optical connections among the subsystems.

In some embodiments, information handling device 700 includes a display subsystem 726 for displaying information on a display, which may include a display driver and a display, such as a liquid crystal display, multi-touch screen, or the like.

The information processing apparatus 700 may be (or may be included in) any client device 101 and/or any electronic device 103 having at least one network interface as shown in fig. 1. For example, information processing device 700 may be (or may be included in): desktop computers, laptop computers, sub-notebooks/netbooks, servers, computers, mainframe computers, cloud-based computers, tablet computers, smart phones, cellular phones, smart watches, wearable devices, consumer electronics, portable computing devices, access points, transceivers, controllers, radio nodes, routers, switches, communication devices, access points, test devices, and/or other electronic devices.

Although information handling device 700 is described using specific components, in alternative embodiments, different components and/or subsystems may be present in information handling device 700. For example, information processing apparatus 700 may include one or more additional processing subsystems, memory subsystems, networking subsystems, and/or display subsystems. In addition, one or more of the subsystems may not be present in the information processing apparatus 700. Further, in some embodiments, information processing apparatus 700 may include one or more additional subsystems not shown in fig. 2. Additionally, although separate subsystems are shown in fig. 2, in some embodiments, some or all of a given subsystem or component may be integrated into one or more of the other subsystems or components in information processing device 700. For example, in some embodiments, the program instructions 722 are included in the operating system 724 and/or the control logic 716 is included in the interface circuitry 718.

Further, any combination of analog and/or digital circuits may be used to implement the circuits and components in information processing device 700, including: bipolar, PMOS and/or NMOS gates or transistors. Further, the signals in these embodiments may include digital signals having approximately discrete values and/or analog signals having continuous values. In addition, the components and circuits may be single ended or differential, and the power supply may be unipolar or bipolar.

An integrated circuit (sometimes referred to as a "communication circuit" or "means for communicating") may implement some or all of the functionality of networking subsystem 714. The integrated circuit may include hardware and/or software mechanisms that are used to transmit wireless signals from the information processing device 700 and to receive signals from other information processing devices at the information processing device 700. Radios are generally known in the art, other than the mechanisms described herein, and therefore are not described in detail. In general, networking subsystem 714 and/or the integrated circuit may include any number of radios. Note that the radios in the multiple radio embodiments function in a similar manner to the single radio embodiment described.

In some embodiments, networking subsystem 714 and/or the integrated circuit includes a configuration mechanism (such as one or more hardware and/or software mechanisms) that configures the radio to transmit and/or receive on a given communication channel (e.g., a given carrier frequency). For example, in some embodiments, a configuration mechanism may be used to switch a radio from monitoring and/or transmitting on a given communication channel to monitoring and/or transmitting on a different communication channel. Note that "monitoring" as used herein includes receiving signals from other information processing apparatuses and possibly performing one or more processing operations on the received signals.

An exemplary flow of a method for use with an electronic device and a client device according to an embodiment of the disclosure is described below in conjunction with fig. 3. Fig. 3 is a flow diagram schematically illustrating a method 200 for use with an electronic device and a client device, in accordance with an embodiment of the present disclosure. Note that the electronic device here may be the electronic device 103 shown in fig. 1, and the client device here may be the client device 101 shown in fig. 1.

As shown in fig. 3, in step S201, the number of times a call of a calling party is rejected by a called party, the calling party having a calling number, may be monitored.

In some embodiments, for example, the electronic device 103 may monitor the number of times the calling party's call is rejected by the called party. For example, when the called party receives a call from a calling party on its client device 101, the called party may not want to answer the calling party's call, but rather reject the calling party's call. In this case, since the called party rejects the call of the calling party, the called party is likely to intend to set the calling number of the calling party to a blacklist, which is stored in the memory. Further, the more times the called party rejects the call of the calling party, the greater the likelihood that the called party intends to place the calling number of the calling party in a blacklist. That is, whether the calling number of the calling party needs to be automatically set to the blacklist may be determined according to the number of times the called party rejects the call of the calling party.

According to some embodiments of the present disclosure, the monitoring of the number of times the call of the calling party is rejected by the called party may comprise: monitoring whether a called party presses a particular key on a client device or a combination of two or more keys on the client device when called by a calling party; and in the event that the called party presses a particular key on the client device or a combination of two or more keys on the client device while being called by the calling party, determining that the call of the calling party is rejected by the called party and increasing the number of times the call of the calling party is rejected by the called party by 1.

An exemplary flow of a process for monitoring the number of times a call by a calling party is rejected by a called party is described below in connection with fig. 4. Fig. 4 is a flow chart schematically illustrating a process 300 for monitoring the number of times a call by a calling party is rejected by a called party, in accordance with an embodiment of the present disclosure.

As shown in fig. 4, in step S301, it may be monitored whether the called party presses a specific key on the client device or a combination of two or more keys on the client device when called by the calling party.

In some embodiments, when the called party receives the calling party's call on its client device 101, if the called party does not want to answer the calling party's call, i.e., if the called party wants to reject the calling party's call, the called party may press a specific key on its client device 101 or a combination of two or more keys on its client device 101 to reject the calling party's call. For example, a specific key (e.g., an "+" key, "#" key, etc.) in the client device 101 may be previously defined as a reject key. When the called party presses the reject key on his client device 101, this indicates that the called party has rejected the calling party's call. Additionally, for example, a combination of two or more keys (e.g., a combination of an "# key with one or more numeric keys, a combination of a" # "key with one or more numeric keys, a combination of an" # key with a "#" key and/or one or more numeric keys, etc.) on client device 101 may be predefined as a rejection instruction. When the called party presses a combination of two or more keys on his client device 101 to issue a rejection instruction, it indicates that the called party has rejected the calling party. Note that the present disclosure is not particularly limited to a particular key and a combination of two or more keys on the client device 101.

If the monitoring called party presses a particular key on the client device or a combination of two or more keys on the client device while being called by the calling party ("yes" at step S301), the process 300 for monitoring the number of times the calling party is rejected by the called party may proceed to step S303. In step S303, it may be determined that the call of the calling party is rejected by the called party, and the number of times the call of the calling party is rejected by the called party may be increased by 1.

In some embodiments, for example, a counter may be set for each calling party's calling number to count the number of times the called party rejects the calling of the calling party. The initial value of the counter may be set to 0. In case it is determined that the call of the calling party is rejected by the called party, the value of the counter may be increased by 1. Note that the present disclosure does not specifically limit the method of how to count the number of times the call of the calling party is rejected by the called party.

In addition, if the monitoring called party does not press a particular key on the client device or a combination of two or more keys on the client device while being called by the calling party ("no" in step S301), the process 300 for monitoring the number of times the call by the calling party is rejected by the called party may end.

Referring back to fig. 3, after step S201, the method 200 for use with an electronic device and a client device may proceed to step S203. In step S203, the number of rejections may be compared to a predetermined threshold.

In some embodiments, the predetermined threshold may be set according to experience in the field, or may be set by counting past historical data, which is not specifically limited by the present disclosure.

After step S203, the method 200 for use with the electronic device and the client device may proceed to step S205. In step S205, it may be determined that the calling number of the calling party is to be set into a blacklist in case the number of rejections exceeds the predetermined threshold.

In some embodiments, if the number of rejections exceeds a predetermined threshold, it indicates that the called party most likely wants to place the calling number of the calling party on a blacklist. In addition, if the number of rejections does not exceed the predetermined threshold, it is not yet determined whether the called party wants to place the calling number of the calling party in the blacklist.

An exemplary flow of a method for use with an electronic device and a client device according to an embodiment of the present disclosure is described below in conjunction with fig. 5. Fig. 5 is a flow diagram schematically illustrating a method 400 for use with an electronic device and a client device, in accordance with an embodiment of the present disclosure.

According to an embodiment of the present disclosure, in case that it is determined that the calling number of the calling party is to be set to the blacklist, the called party may be notified of the calling number to be set to the blacklist via at least one of an indicator lamp, a ring tone, and voice.

Steps S401 to S405 shown in fig. 5 are the same as steps S201 to S205 shown in fig. 3, and therefore are not described herein again for brevity.

As shown in fig. 5, in step S407, in case that it is determined that the calling number of the calling party is to be set into the blacklist, the called party may be notified that the calling number is to be set into the blacklist via at least one of an indicator lamp, a ring tone, and voice.

In some embodiments, if the electronic device 103 determines that the calling number of the calling party is to be set into the blacklist, the electronic device 103 may notify the called party that the calling number is to be set into the blacklist in various ways. In some embodiments, the electronic device 103 may notify the called party through an indicator light. For example, the electronic device 103 may send an instruction to the client device 101 of the called party to cause an indicator light (e.g., an LED indicator light, etc.) on the client device 101 to light up or flash. In other embodiments, the electronic device 103 may notify the called party by ringing. For example, the electronic device 103 may send an instruction to the client device 101 of the called party to cause the client device 101 to ring a particular ring tone or combination thereof. In still other embodiments, the electronic device 103 may notify the called party by voice. For example, the electronic device 103 may send specific voice information to the client device 101 of the called party to enable the client device 101 to listen to the specific voice information. Note that the present application does not specifically limit the manner of notification.

According to an embodiment of the present disclosure, in the case of notification to a called party via voice, detailed information of a calling number to be set into a blacklist may be broadcasted to the called party via voice.

In some embodiments, if the electronic device 103 notifies the called party via voice, the electronic device 103 may send specific voice information to the client device 101 of the called party. When the called party listens to the specific voice information on his client device 101 (e.g. by off-hook), the called party may be announced via voice details of the calling numbers to be set to the blacklist, e.g. which calling number or numbers are to be set to the blacklist, etc.

An exemplary flow of a method for use with an electronic device and a client device according to an embodiment of the disclosure is described below in conjunction with fig. 6. Fig. 6 is a flow diagram schematically illustrating a method 500 for use with an electronic device and a client device, in accordance with an embodiment of the present disclosure.

Steps S501 to S507 shown in fig. 6 are the same as steps S401 to S407 shown in fig. 5, and therefore, for brevity, are not described again here.

In step S509, in case of receiving confirmation of a called party that the calling number of the calling party is to be set into a blacklist, or in case of default, the calling number of the calling party may be automatically set into a blacklist.

In some embodiments, in the event that the called party receives a notification from the electronic device that the calling number is to be placed in the blacklist, the called party may respond to whether the calling number is to be placed in the blacklist. In some embodiments, the called party may confirm or agree that the calling number is to be placed on the blacklist. For example, the called party may indicate confirmation or consent by pressing a particular key or a combination of two or more keys on his client 101. Note that the present disclosure does not specifically limit the specific key or the combination of two or more keys used to indicate confirmation or agreement. In some embodiments, said calling number of the calling party may be automatically set to a blacklist in case the electronic device 103 receives an acknowledgement or consent of the called party. In other embodiments, if the electronic device 103 does not receive a called party response to whether the calling number is to be placed on the blacklist (e.g., within a predetermined time period), the electronic device 103 may default to the called party confirming or agreeing to place the calling number on the blacklist. Thus, in this case, the calling number of the calling party may also be automatically set to the blacklist.

An exemplary flow of a method for use with an electronic device and a client device according to an embodiment of the disclosure is described below in conjunction with fig. 7. Fig. 7 is a flow diagram that schematically illustrates a method 600 for use with an electronic device and a client device, in accordance with an embodiment of the present disclosure.

Steps S601 to S605 shown in fig. 7 are the same as steps S201 to S205 shown in fig. 3, and therefore, for brevity, are not described again here.

In step S607, setting the calling number of the calling party into a blacklist may be enabled or disabled via at least one of a Graphical User Interface (GUI), an Application (APP) and protocol signaling.

In some embodiments, the functionality described herein to automatically set the calling number of a calling party into a blacklist may be enabled or disabled in various ways. For example, a function configuration page of the electronic device 103 may be logged in, and the above-mentioned function of automatically setting the calling number of the calling party to the blacklist may be enabled or disabled through a graphical user interface GUI on the function configuration page. Also for example, the above-described function of automatically setting the calling number of the calling party into a blacklist may be turned on or off via an application APP installed on the portable computing device. As another example, the above-described functionality of automatically setting the calling number of the calling party to a blacklist may be enabled or disabled via any of a variety of protocol signaling.

According to some embodiments of the present disclosure, the protocol signaling includes at least one of a Simple Network Management Protocol (SNMP) and a technical report 069(TR 069). Note that the present disclosure does not specifically limit the type of protocol signaling.

According to the above-described embodiments of the present disclosure, since whether to automatically set the calling number of the calling party to the blacklist can be determined by monitoring whether the number of times the calling party is rejected by the called party reaches a predetermined number of times, efficiency of the user in setting the calling number to the blacklist can be improved, and convenience of the user in setting the calling number to the blacklist can be improved.

Although the foregoing discussion uses Wi-Fi and/or ethernet communication protocols as illustrative examples, in other embodiments a wide variety of communication protocols, and more generally, communication technologies may be used. Thus, communication techniques may be used in various network interfaces. Further, while some of the operations in the foregoing embodiments are implemented in hardware or software, in general, the operations in the foregoing embodiments may be implemented in a variety of configurations and architectures. Accordingly, some or all of the operations in the foregoing embodiments may be performed in hardware, software, or both. For example, at least some of the operations in the communication techniques may be implemented using program instructions 722, an operating system 724 (such as a driver for interface circuit 718), or in firmware in interface circuit 718. Alternatively or additionally, at least some operations in the communication techniques may be implemented in hardware in a physical layer, such as the interface circuit 718.

The present disclosure may be implemented as any combination of apparatus, systems, integrated circuits, and computer programs on non-transitory computer readable media. One or more processors may be implemented as an Integrated Circuit (IC), an Application Specific Integrated Circuit (ASIC), or a large scale integrated circuit (LSI), a system LSI, or a super LSI, or as an ultra LSI package that performs some or all of the functions described in this disclosure.

The present disclosure includes the use of software, applications, computer programs or algorithms. Software, applications, computer programs, or algorithms may be stored on a non-transitory computer readable medium to cause a computer, such as one or more processors, to perform the steps described above and depicted in the figures. For example, the one or more memories store software or algorithms in executable instructions and the one or more processors may associate a set of instructions to execute the software or algorithms to provide for automatically setting a calling number of a calling party into a blacklist in any number of wireless networks according to embodiments described in the present disclosure.

Software and computer programs (which may also be referred to as programs, software applications, components, or code) include machine instructions for a programmable processor, and may be implemented in a high-level procedural, object-oriented, functional, logical, or assembly or machine language. The term "computer-readable medium" refers to any computer program product, apparatus or device, such as magnetic disks, optical disks, solid state storage devices, memories, and Programmable Logic Devices (PLDs), used to provide machine instructions or data to a programmable data processor, including a computer-readable medium that receives machine instructions as a computer-readable signal.

By way of example, computer-readable media can comprise Dynamic Random Access Memory (DRAM), Random Access Memory (RAM), Read Only Memory (ROM), electrically erasable read only memory (EEPROM), compact disk read only memory (CD-ROM) or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to carry or store desired computer-readable program code in the form of instructions or data structures and which can be accessed by a general-purpose or special-purpose computer or a general-purpose or special-purpose processor. Disk or disc, as used herein, includes Compact Disc (CD), laser disc, optical disc, Digital Versatile Disc (DVD), floppy disk and blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media.

In one or more embodiments, use of the terms "can," "operable" or "configured" refer to some apparatus, logic, hardware, and/or element that is designed to be used in a specified manner. The subject matter of the present disclosure is provided as examples of apparatus, systems, methods, and programs for performing the features described in the present disclosure. However, other features or variations are contemplated in addition to the features described above. It is contemplated that the implementation of the components and functions of the present disclosure may be accomplished with any emerging technology that may replace the technology of any of the implementations described above.

Additionally, the above description provides examples, and does not limit the scope, applicability, or configuration set forth in the claims. Changes may be made in the function and arrangement of elements discussed without departing from the spirit and scope of the disclosure. Various embodiments may omit, substitute, or add various procedures or components as appropriate. For example, features described with respect to certain embodiments may be combined in other embodiments.

Similarly, while operations are depicted in the drawings in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In some cases, multitasking and parallel processing may be advantageous.

Claims

1. An electronic device for use with a client device, the electronic device comprising:

a memory having instructions stored thereon;

a processor configured to execute instructions stored on the memory to cause the electronic device to perform operations comprising:

monitoring the number of times a call by a calling party is rejected by a called party, the calling party having a calling number;

comparing the number of rejections to a predetermined threshold; and

determining to set the calling number of the calling party into a blacklist in case the number of rejections exceeds the predetermined threshold.

2. The electronic device of claim 1, wherein the monitoring of the number of times a call by a calling party is rejected by a called party comprises:

monitoring whether a called party presses a particular key on a client device or a combination of two or more keys on the client device when called by a calling party; and

in the case where the called party presses a specific key on the client device or a combination of two or more keys on the client device while being called by the calling party, it is determined that the call of the calling party is rejected by the called party, and the number of times the call of the calling party is rejected by the called party is increased by 1.

3. The electronic device of claim 1, wherein the operations further comprise:

in case it is determined that the calling number of the calling party is to be set to the blacklist, the called party is notified of the calling number to be set to the blacklist via at least one of an indicator light, a ring tone, and voice.

4. The electronic device according to claim 3, wherein in the case of notifying the called party via voice, detailed information of the calling number to be set into the blacklist is broadcasted to the called party via voice.

5. The electronic device of claim 3, wherein the operations further comprise:

in case of receiving confirmation from a called party that the calling number of the calling party is to be set to a blacklist, or in case of default, automatically setting the calling number of the calling party to a blacklist.

6. The electronic device of any of claims 1-5, wherein the operations further comprise:

enabling or disabling setting of a calling number of the calling party into a blacklist via at least one of a Graphical User Interface (GUI), an Application (APP) and protocol signaling.

7. The electronic device of claim 6, wherein the protocol signaling comprises at least one of Simple Network Management Protocol (SNMP) and technical report 069(TR 069).

8. A method for use with an electronic device and a client device, the method comprising:

comparing the number of rejections to a predetermined threshold; and

9. The method of claim 8, wherein the monitoring a number of times a call by a calling party is rejected by a called party comprises:

10. The method of claim 8, further comprising:

11. The method of claim 10, wherein in case of notifying the called party via voice, detailed information of the calling number to be set to the blacklist is broadcasted to the called party via voice.

12. The method of claim 10, further comprising:

13. The method of claim 8, further comprising:

14. The method of claim 13, wherein the protocol signaling comprises at least one of Simple Network Management Protocol (SNMP) and technical report 069(TR 069).

15. A non-transitory computer readable medium for use with a processor and a client device, the non-transitory computer readable medium having instructions stored thereon, which when executed by the processor, cause the processor to perform the method of any of claims 8-14.

16. An information processing apparatus comprising means for performing the method of any one of claims 8-14.