WO2018034605A1 - Method and device for enhancing voip security by selectively scrutinizing caller's geographical location - Google Patents
Method and device for enhancing voip security by selectively scrutinizing caller's geographical location Download PDFInfo
- Publication number
- WO2018034605A1 WO2018034605A1 PCT/SE2016/050771 SE2016050771W WO2018034605A1 WO 2018034605 A1 WO2018034605 A1 WO 2018034605A1 SE 2016050771 W SE2016050771 W SE 2016050771W WO 2018034605 A1 WO2018034605 A1 WO 2018034605A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- caller
- geographical location
- scrutiny
- network operator
- call
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/06—Authentication
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/1066—Session management
- H04L65/1076—Screening of IP real time communications, e.g. spam over Internet telephony [SPIT]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/22—Parsing or analysis of headers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M1/00—Substation equipment, e.g. for use by subscribers
- H04M1/253—Telephone sets using digital voice transmission
- H04M1/2535—Telephone sets using digital voice transmission adapted for voice communication over an Internet Protocol [IP] network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M11/00—Telephonic communication systems specially adapted for combination with other electrical systems
- H04M11/04—Telephonic communication systems specially adapted for combination with other electrical systems with alarm systems, e.g. fire, police or burglar alarm systems
-
- 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/42042—Notifying the called party of information on the calling party
-
- 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/42348—Location-based services which utilize the location information of a target
-
- 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
- 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
- H04M3/4365—Arrangements for screening incoming calls, i.e. evaluating the characteristics of a call before deciding whether to answer it based on information specified by the calling party, e.g. priority or subject
-
- 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/50—Centralised arrangements for answering calls; Centralised arrangements for recording messages for absent or busy subscribers ; Centralised arrangements for recording messages
- H04M3/51—Centralised call answering arrangements requiring operator intervention, e.g. call or contact centers for telemarketing
- H04M3/5116—Centralised call answering arrangements requiring operator intervention, e.g. call or contact centers for telemarketing for emergency applications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M7/00—Arrangements for interconnection between switching centres
- H04M7/006—Networks other than PSTN/ISDN providing telephone service, e.g. Voice over Internet Protocol (VoIP), including next generation networks with a packet-switched transport layer
- H04M7/0078—Security; Fraud detection; Fraud prevention
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/02—Services making use of location information
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/1066—Session management
- H04L65/1101—Session protocols
- H04L65/1104—Session initiation protocol [SIP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M1/00—Substation equipment, e.g. for use by subscribers
- H04M1/66—Substation equipment, e.g. for use by subscribers with means for preventing unauthorised or fraudulent calling
- H04M1/663—Preventing unauthorised calls to a telephone set
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M2203/00—Aspects of automatic or semi-automatic exchanges
- H04M2203/55—Aspects of automatic or semi-automatic exchanges related to network data storage and management
- H04M2203/551—Call history
-
- 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/42085—Called party identification service
- H04M3/42102—Making use of the called party identifier
- H04M3/4211—Making use of the called party identifier where the identifier is used to access a profile
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M7/00—Arrangements for interconnection between switching centres
- H04M7/006—Networks other than PSTN/ISDN providing telephone service, e.g. Voice over Internet Protocol (VoIP), including next generation networks with a packet-switched transport layer
Definitions
- Embodiments of the subject matter disclosed herein generally relate to methods and devices for enhancing Voice Over Internet Protocol (VOIP) security, using callers location information.
- VOIP Voice Over Internet Protocol
- SIP Session Initiation Protocol
- P-Visited-Network-IDs which may reveal the caller's location.
- a P- Visited-Network-ID indicates a visited network device, which is an intermediate device transmitting messages between the caller and the home network device (i.e., the network device that connects the call to the callee user equipment, UE).
- any visited network device inserts an identifier (i.e., a P-Visited-Network-ID) known by the home network device, in the P-Header.
- identifiers should be globally unique, and may be a quoted text string or a token.
- the home network device may use the identifiers to verify the existence of roaming agreements with the visited network devices, and to authorize the caller's registration.
- This P-Visited-Network-ID approach has a number of drawbacks and limitations.
- the granularity of the location information is coarse, the P-Visited- Network-ID indicating location at a country level, instead of a province, city or even smaller divisions of a geographical area.
- the P-Visited-Network-ID approach assumes that there are trust relationships between the home network device and visited network devices. This is not always the case, since the P-header can be modified by a malicious visited network device. In other words, the malicious visited network device modifies one or more P-Visited-Network-IDs in the P-header.
- a mandatory header is implemented in the transmission protocol. This mandatory header cannot be stripped from the associated message, and is added by a trusted network element (e.g., the first network node that the message traverses).
- a trusted network element e.g., the first network node that the message traverses.
- this network node may be the P-CSCF (proxy Call Session Control Function) of the user on the user's initial REGISTER request.
- a method performed by a network operator for enhancing security of VOIP calls.
- the method includes determining whether a scrutiny of a caller is required when a call is initiated.
- the method further includes, requesting the caller's geographical location information, if determined that the scrutiny is required, and checking veracity of the caller's geographical location information to determine whether the caller is suspicious.
- network operator device configured to enhance security of VOIP calls having a communication interface and a processing unit.
- the communication interface is configured to exchange messages with other devices in a communication network.
- the processing unit which includes at least one processor and is connected to the communication interface, is configured to determine whether a scrutiny of a caller is required when a call is initiated, to control the communication interface to request a caller's geographical location if the scrutiny is required, and to check veracity of the caller's geographical location in order to determine whether the caller is suspicious.
- a network operator device configured to enhance security of VOIP calls having a logic module, an information demand module and a verification module.
- the logic module determined whether a scrutiny of a caller is required.
- the information demand module requests caller's geographical location information when the logic module has determined that the scrutiny is required.
- the verification module checks veracity of the caller's geographical location information to determine whether the caller is suspicious.
- the communication network having a communication interface configured to send and receive messages from other devices in the communication network, and a data processing unit.
- the data processing unit which includes at least one processor and is connected to the communication interface, is configured to control the communication interface to send a message with an unmodifiable header including geographical location information of the client device, upon request.
- Figure 1 is a flowchart of a method according to an embodiment
- FIG. 2 is a schematic diagram illustrating communications between a caller user equipment (UE), a network device, and a callee UE, according to an embodiment
- Figure 3 is a schematic diagram of a network device according to an embodiment
- Figure 4 is a block diagram of a network device according to another embodiment.
- Figure 5 is a schematic representation of a client device according to an embodiment.
- the security of VOIP calls is enhanced by using the caller's geographical information obtained in a reliable manner.
- the network device that connects the call to the callee and/or the callee are enabled to better decide whether to forward, reject or answer the call.
- the network device may first evaluate whether the callee is vulnerable. This evaluation may be a default service for everyone (since anyone may be a target of a spoofing attack) or an optional service.
- the level of scrutiny employed in this evaluation may be varied from a low scrutiny (e.g., triggered by a default service) to a higher scrutiny based on the callee's profile (i.e., the callee's profile may include an indication that a higher level of scrutiny has been set). Old and/or disabled people are usually more vulnerable to spoofing attacks.
- a callee or his/her relatives can request that the network operator to insert an indication that the callee is vulnerable into the callee's profile.
- the network device If determined that the callee is vulnerable, the network device then requests the caller's geographical location information via an additional header that cannot be modified by intermediate devices. Upon receiving the additional header, the network device checks veracity of the caller's geographical location information. If the result of the veracity check is that the geographical location information is trustworthy, the network device may or may not present the geographical location information to the callee. If the result of the veracity check is that the geographical location information is not trustworthy, the network device warns the callee that the caller is suspicious. [0023] The caller being suspicious is indicated to the callee's user equipment (UE) in order to reach the callee.
- UE user equipment
- a warning and/or the caller's geographical location information can be displayed on the UE's screen.
- a voice announcement and/or ringtone may be used to indicate a suspicious caller.
- the voice announcement may announce the caller's geographical location information.
- Figure 1 is a flowchart of a method 100 performed by a network operator, for enhancing security of VOIP calls, according to an embodiment.
- Method 100 includes determining whether a scrutiny of the caller is required when a call is initiated at S1 10.
- Method 100 further includes requesting a caller's geographical location information, when determined that the scrutiny is required at S120, and checking veracity of the caller's geographical location information to determine whether the caller is suspicious, at S130. These steps may be performed by a same physical device, or by two or more intermediate devices, between the caller and the callee.
- steps 81 10 and S120 can easily be performed by any of the intermediate nodes, it seems favorable to perform S130 at the first node on the caller side.
- S130 is performed by another node that obtains information about the first node's location to enable the veracity check.
- the scrutiny may be required if the callee's profile includes an indication for enhanced VOIP security service. This indication may be included in the callee's profile upon receiving an enhanced VOIP security service request.
- the CDR is a data record that documents details related to a UE's communications. For example, the CDR includes time, duration, completion status, source number, and destination number for each call of the UE. Since the network operator owns CDR, network devices can analyze it. The result of the CDR analysis can be stored and/or shared.
- Such CDR analysis may determine that scrutiny is required if callers calls have often been rejected by other ca!lees and/or the callers calls frequently lasted less than a predetermined time interval (e.g. , 30 s). Alternatively or additionally, the CDR analysis may determine that the scrutiny is not required if the average duration of prior calls between the caller and the caliee is longer than a predetermined threshold (e.g., 30 s).
- Requesting the caller's geographical location information may trigger receiving a reply message with the caller's geographical location information included in an unmodifiable header.
- the network device may then inform the caliee before connecting the call, or may not connect the call to the caliee. Informing the caliee may be achieved by forwarding the caller's geographical location information to the caliee, sending an audio message to the caliee prior to connecting the call, and/or activating a warning signal detectable by the caliee.
- Step S130 may include evaluating whether the caller's geographical location is in the same geographical area as a location of a first network operator node accessed to initiate the call. If the caller's geographical location is not in the same geographical area as the first network operator node's location, then the caller is suspicious.
- a network operator device may acquire the first operator node's geographical location. For example, a node's geographical location may be using device's Location Area Identity (LAI).
- LAI is a unique number that identifies a particular location on Earth.
- Figure 2 illustrates communications between a caller UE 210, a network device 220, and a callee UE 230 (time order of the illustrated operations is from up to down), in a SIP environment.
- a new optional but un-modifiable header is enabled (i.e., to be generated and transmitted) in this SIP environment.
- This new header named, for example, "P-Origination-Location," carries the caller's geographical location information.
- This header may include a text string and may be generated by the caller's UE upon receiving a request from its first network node. The first network node may perform a veracity check of this text string.
- the caller UE 210 sends an SIP INVITE message to initiate a VOIP call with the callee.
- SIP INVITE message to initiate a VOIP call with the callee.
- no visited devices are illustrated between the caller UE 210 and the network device 220, such other devices may be present.
- the callee UE and the network device may pertain to a different network than the caller UE.
- the network device 220 Upon receiving the SIP INVITE message, the network device 220 determines whether the callee is vulnerable at 2. Steps 3-1 1 , which are labeled A1 , follow if determined that the callee is vulnerable, and steps 12-14, which are labeled A2, follow if determined that the callee is not vulnerable. Determining that the callee is vulnerable triggers requesting, generating and transmitting the P- Origination-Location header in the network. Thus, if the callee is vulnerable (A1 ), the network device 220 sends SIP response 1xx to caller UE 210 requesting the caller UE to provide P- Origination-Location header, at 3. Then, at 4, the caller UE 210 sends an SIP UPDATE message including the P-Origination-Location header to the network device 220.
- the network device 220 verifies the P-Origination-Location header's veracity at 5. Steps 6-9, which are labeled B1 , follow if veracity is confirmed, and steps 10 and 1 1 , which are labeled B2, follow if veracity is not confirmed. If the P-Origination- Location header's veracity is confirmed (B1 ), the network device 220 replies by sending a "200 UPDATE" SIP message to the caller UE 210 at 6, and then responds to the initial SIP INVITE received at 1 , by sending a "1xx INVITE" message to the caller UE 210 at 7.
- the network device 220 then sends a "SIP INVITE" message including the "P-Origination-Location" header to the callee UE 230 at 8.
- the callee UE 230 Upon receiving this "SIP INVITE" message, the callee UE 230 conveys the caller's location information from the P-Origination-Location header to the callee, using the ringtone, a voice message and/or displaying this information at 9.
- the known flow of the VOIP call then follows.
- the network device 220 determines that the P-Origination-Location header's veracity is not confirmed (B2), then the call is rejected by the network device that sends a "4xx UPDATE" reject message at 10, and a "4xx INVITE" reject message at 1 1 , to the caller UE 210.
- the network device 220 may transmit an indication (e.g., a 0 value instead of a valid location) in the P-Origination-Location header if it has already determined that the caller is suspicious.
- the network device 220 determines that the callee is not vulnerable (A2), then the network device 220 sends a "1xx INVITE" message to the caller UE 210 at 12, and a "SIP INVITE" message to the callee UE 230 at 13. Upon receiving the "SIP INVITE" message at 13, the callee UE 230 produces the regular ringtone at 14.
- the network device may perform an integrity check of the P-Origination- Location header received from the caller UE. For example, the network device may verify whether the geographical location information provided by caller UE is in the same geographical area (like city, or region) of the first traversed network node. The geographical coordinates of the first network node may be correlated to a specific area of the city and country.
- callee UE is a smart phone
- the geographical location information can be displayed directly on the screen with the phone number.
- This type of callee UE may also indicate that the caller is suspicious if instead of the location information it has been received an indication that the caller is suspiciou (e.g., a "0" value).
- the smart phones may also use a special ring tone to signal a suspicious caller. If callee UE is an older phone, then the network device may translate the geographical location information into an audio message causing the phone to play it either as a ringtone or a voice
- the network device requests additional geographical location information of the caller to check if caller is suspicious;
- network device provides the geographical location information to the callee.
- Figure 3 is a block diagram of a network device 300 including a communication interface 310 and a processing unit 320.
- the communication interface is configured to exchange messages with other devices in a communication network 312.
- the communication interface may receive a message including the caller's geographical location information in an unmodifiable header.
- the processing unit includes at least one processor and is connected to the communication interface.
- the processing unit is configured to determine whether a scrutiny of a caller is required when a call is initiated, to control the communication interface to request a caller's geographical location information if the scrutiny is required, and to check veracity of the caller's geographical location information to determine whether the caller is suspicious.
- the processing unit may determine that the scrutiny is required if a cailee's profile includes an indication that an enhanced VOIP security is required.
- the data processing unit may have added this indication in the cailee's profile upon receiving a request.
- the processing unit may determine that the scrutiny is required if analyzing the CDR reveals that caller's calls have often been rejected by other callees, or that the callers calls have lasted frequently less than a predetermined time interval. Additionally, the processing unit may determine that the scrutiny is not required if analyzing the CDR reveals that prior calls between the caller and the cailee lasted in average longer than a predetermined duration.
- the processing unit may control the communication interface to inform the cailee before connecting the call, or not connecting the call to the cailee, if the caller is suspicious.
- the communication interface may inform the cailee that the caller is suspicious by forwarding the caller's geographical location to the cailee, triggering an audio message prior to connecting the call, or activating a warning signal (e.g., a specific ringtone) detectable by the cailee.
- a warning signal e.g., a specific ringtone
- the processing unit may check the veracity by evaluating whether the caller's geographical location is in a same geographical area as a location of a first network operator node accessed to initiate the call.
- Network operator device 300 may also include a memory 340 and an operator interface 330.
- the memory may store executable codes which, when executed by the processing unit make the processing unit to determine whether the scrutiny is required, to control the communication interface, and to check the veracity of the caller's geographical location information.
- a network operator device 400 is illustrated in Figure 4.
- This device is configured to enhance security of VOIP calls and includes a logic module 410, an information demand module 420 and a verification module 430.
- Logic module 410 determines whether a scrutiny of a caller is required, when a call is initiated.
- Information demand module 420 requests caller's geographical location information when the logic module has determined that the scrutiny is required.
- Verification module 430 checks veracity of the caller's geographical location information to determine whether the caller is suspicious.
- Figure 5 illustrates a client device 500, which may operate as the callers phone.
- Device 500 includes a communication interface 510 configured to send and receive messages from other devices in a communication network, and a data processing unit 520.
- Data processing unit 520 which includes at least one processor and is connected to the communication interface, is configured to control the
- an unmodifiable header e.g., a P- Origination-Location header
- geographical location information of the client device upon request.
- a network node configured to serve client devices in a predetermined area.
- the network node may have the same structure as the device illustrated in Figure 3.
- the network node according to this embodiment is enabled to obtain its location and a range of an area it covers (i.e., the node is configured to provide network connectivity to devices within the covered area).
- the network node may have a Global Positioning Satellite (GPS) module, which enables it to identify its location.
- GPS Global Positioning Satellite
- the network node's location may be a parameter provided by the network when setting up the network node.
- the network may additionally also inform the network node about its coverage (for example, a circle whose center is the network node's location and radius is 100 km).
- the coverage may also be a configurable parameter.
- this network node upon receiving a connection request from a device, this network node (the processing unit thereof) verifies if the device's location information included in a P-Origination-Location header is within its service range. If the device's location information in the P-Origination-Location header is not within the network node's service range, the network node may either reject the connection request, or forward the request with the P-Origination-Location header and an indication that the caller is suspicious.
- the methods and devices described in this section enhance VOIP security using reliable caller geographic location information.
- the caller has to reveal its geographical location information. Having this information makes it more likely that a vulnerable person is warned to be cautious. For example, if a caller pretending to be your local bank is located in a different country, the callee is on notice.
- the caller's geographical location information may be transmitted using an SIP header that once associated with a message cannot be modified by visited network devices.
- the embodiments disclosed in this section provide methods and network devices that enhance security of VOIP calls based on reliable location information for the caller. It should be understood that this description is not intended to limit the invention. On the contrary, the exemplary embodiments are intended to cover alternatives, modifications and equivalents, which are included in the spirit and scope of the invention. Further, in the detailed description of the exemplary embodiments, numerous specific details are set forth in order to provide a comprehensive system.
Abstract
The VOIP call security is enhanced using the caller's geographical location information, which is transmitted to the home network device using an unmodifiable header. The home network device checks the veracity of the caller's geographical location information to determine whether the caller is suspicious.
Description
METHOD AND DEVICE FOR ENHANCING VOIP SECURITY BY SELECTIVELY SCRUTINIZING CALLER'S GEOGRAPHICAL LOCATION
TECHNICAL FIELD
[0001] Embodiments of the subject matter disclosed herein generally relate to methods and devices for enhancing Voice Over Internet Protocol (VOIP) security, using callers location information.
BACKGROUND
[0002] In the last couple of decades, the proliferation of mobile phones and digital communications led to a spectacular increase in the number of calls.
Simultaneously, fraudulent calls by various scammers have also increased and became more sophisticated. We are all vulnerable, but some people (e.g., older persons or persons with disabilities) are more vulnerable than others.
[0003] Today, when receiving a call, a phone number is displayed on the callee's phone. If the caller is a known contact, then the caller's name is displayed in addition to or instead of the phone number. Situations in which scammers deceivingly appear to be legitimate calls are known as spoofing attacks. For example, the caller appears to be callee's bank when in fact it is not. Such calls often originate from unlikely locations, inconsistent with the alleged identity. Currently, there are no reliable techniques for ensuring or confirming that the caller is who he/she pretends to be.
[0004] The most common transmission protocol, SIP (Session Initiation Protocol) offers a mechanism to track the path of a call across the network. In SIP, there is a header named "via", which is used to track the visited nodes along the call's path.
Since this header is optional and can be anonymized, it is not possible to rely that the caller's location is correctly identified using the "via" header.
[0005] A recently discussed Private Header (P-Header) extension to SIP
(described in RFC7315 document of Internet Engineering Task Force, IETF, from July 2014) includes P-Visited-Network-IDs, which may reveal the caller's location. A P- Visited-Network-ID indicates a visited network device, which is an intermediate device transmitting messages between the caller and the home network device (i.e., the network device that connects the call to the callee user equipment, UE). According to RFC7315, any visited network device inserts an identifier (i.e., a P-Visited-Network-ID) known by the home network device, in the P-Header. These identifiers should be globally unique, and may be a quoted text string or a token. The home network device may use the identifiers to verify the existence of roaming agreements with the visited network devices, and to authorize the caller's registration.
[0006] This P-Visited-Network-ID approach has a number of drawbacks and limitations. First, the granularity of the location information is coarse, the P-Visited- Network-ID indicating location at a country level, instead of a province, city or even smaller divisions of a geographical area. Second, the P-Visited-Network-ID approach assumes that there are trust relationships between the home network device and visited network devices. This is not always the case, since the P-header can be modified by a malicious visited network device. In other words, the malicious visited network device modifies one or more P-Visited-Network-IDs in the P-header. In order to prevent such modifications, all visited devices should apply a hop-by-hop integrity protection mechanism such as IPsec, or other available mechanisms. Given these drawbacks and
limitations, this P-header based mechanism does not effectively provide the caller's location information in a way that is usable to identifying spoofing attacks.
[0007] It is desirable to find mechanisms for effectively enhancing VOIP security by using accurate and reliable caller's location information.
SUMMARY
[0008] In order to enable a network to reject or to signal suspicious calls, a mandatory header is implemented in the transmission protocol. This mandatory header cannot be stripped from the associated message, and is added by a trusted network element (e.g., the first network node that the message traverses). For example, in IMS SIP, this network node may be the P-CSCF (proxy Call Session Control Function) of the user on the user's initial REGISTER request.
[0009] According to an embodiment, there is a method performed by a network operator, for enhancing security of VOIP calls. The method includes determining whether a scrutiny of a caller is required when a call is initiated. The method further includes, requesting the caller's geographical location information, if determined that the scrutiny is required, and checking veracity of the caller's geographical location information to determine whether the caller is suspicious.
[0010] According to another embodiment there is network operator device configured to enhance security of VOIP calls having a communication interface and a processing unit. The communication interface is configured to exchange messages with other devices in a communication network. The processing unit, which includes at least one processor and is connected to the communication interface, is configured to determine whether a scrutiny of a caller is required when a call is initiated, to control the
communication interface to request a caller's geographical location if the scrutiny is required, and to check veracity of the caller's geographical location in order to determine whether the caller is suspicious.
[0011] According to yet another embodiment there is a network operator device configured to enhance security of VOIP calls having a logic module, an information demand module and a verification module. The logic module determined whether a scrutiny of a caller is required. The information demand module requests caller's geographical location information when the logic module has determined that the scrutiny is required. The verification module checks veracity of the caller's geographical location information to determine whether the caller is suspicious.
[0012] According to another embodiment, there is a client device in a
communication network having a communication interface configured to send and receive messages from other devices in the communication network, and a data processing unit. The data processing unit, which includes at least one processor and is connected to the communication interface, is configured to control the communication interface to send a message with an unmodifiable header including geographical location information of the client device, upon request.
BRIEF DESCRIPTION OF THE DRAWINGS
[0013] The accompanying drawings, which are incorporated in and constitute a part of the specification, illustrate one or more embodiments and, together with the description, explain these embodiments. In the drawings:
[0014] Figure 1 is a flowchart of a method according to an embodiment;
[0015] Figure 2 is a schematic diagram illustrating communications between a caller user equipment (UE), a network device, and a callee UE, according to an embodiment;
[0016] Figure 3 is a schematic diagram of a network device according to an embodiment;
[0017] Figure 4 is a block diagram of a network device according to another embodiment; and
[0018] Figure 5 is a schematic representation of a client device according to an embodiment.
DETAILED DESCRIPTION
[0019] The following description of the embodiments refers to the accompanying drawings. The same reference numbers in different drawings identify the same or similar elements. The following detailed description does not limit the invention.
Instead, the scope of the invention is defined by the appended claims.
[0020] Reference throughout the specification to "one embodiment" or "an embodiment" means that a particular feature, structure or characteristic described in connection with an embodiment is included in at least one embodiment of the subject matter disclosed. Thus, the appearance of the phrases "in one embodiment" or "in an
embodiment" in various places throughout the specification is not necessarily referring to the same embodiment. Further, the particular features, structures or characteristics may be combined in any suitable manner in one or more embodiments.
[0021] In some embodiments set forth below, the security of VOIP calls is enhanced by using the caller's geographical information obtained in a reliable manner. The network device that connects the call to the callee and/or the callee are enabled to better decide whether to forward, reject or answer the call. The network device may first evaluate whether the callee is vulnerable. This evaluation may be a default service for everyone (since anyone may be a target of a spoofing attack) or an optional service. The level of scrutiny employed in this evaluation may be varied from a low scrutiny (e.g., triggered by a default service) to a higher scrutiny based on the callee's profile (i.e., the callee's profile may include an indication that a higher level of scrutiny has been set). Old and/or disabled people are usually more vulnerable to spoofing attacks. A callee or his/her relatives can request that the network operator to insert an indication that the callee is vulnerable into the callee's profile.
[0022] If determined that the callee is vulnerable, the network device then requests the caller's geographical location information via an additional header that cannot be modified by intermediate devices. Upon receiving the additional header, the network device checks veracity of the caller's geographical location information. If the result of the veracity check is that the geographical location information is trustworthy, the network device may or may not present the geographical location information to the callee. If the result of the veracity check is that the geographical location information is not trustworthy, the network device warns the callee that the caller is suspicious.
[0023] The caller being suspicious is indicated to the callee's user equipment (UE) in order to reach the callee. If callee's UE is a modern UE, a warning and/or the caller's geographical location information can be displayed on the UE's screen. For older devices, a voice announcement and/or ringtone may be used to indicate a suspicious caller. In one embodiment, the voice announcement may announce the caller's geographical location information.
[0024] In view of the above-discussed aspects, Figure 1 is a flowchart of a method 100 performed by a network operator, for enhancing security of VOIP calls, according to an embodiment. Method 100 includes determining whether a scrutiny of the caller is required when a call is initiated at S1 10. Method 100 further includes requesting a caller's geographical location information, when determined that the scrutiny is required at S120, and checking veracity of the caller's geographical location information to determine whether the caller is suspicious, at S130. These steps may be performed by a same physical device, or by two or more intermediate devices, between the caller and the callee. While steps 81 10 and S120 can easily be performed by any of the intermediate nodes, it seems favorable to perform S130 at the first node on the caller side. Alternatively, S130 is performed by another node that obtains information about the first node's location to enable the veracity check.
[0025] The scrutiny may be required if the callee's profile includes an indication for enhanced VOIP security service. This indication may be included in the callee's profile upon receiving an enhanced VOIP security service request.
[0026] The scrutiny being required may alternatively or additionally be
determined by analyzing a call detail record (CDR) of the caller. The CDR is a data
record that documents details related to a UE's communications. For example, the CDR includes time, duration, completion status, source number, and destination number for each call of the UE. Since the network operator owns CDR, network devices can analyze it. The result of the CDR analysis can be stored and/or shared.
[0027] Such CDR analysis may determine that scrutiny is required if callers calls have often been rejected by other ca!lees and/or the callers calls frequently lasted less than a predetermined time interval (e.g. , 30 s). Alternatively or additionally, the CDR analysis may determine that the scrutiny is not required if the average duration of prior calls between the caller and the caliee is longer than a predetermined threshold (e.g., 30 s).
[0028] Requesting the caller's geographical location information may trigger receiving a reply message with the caller's geographical location information included in an unmodifiable header.
[0029] If determined that the caller is suspicious at S130, the network device may then inform the caliee before connecting the call, or may not connect the call to the caliee. Informing the caliee may be achieved by forwarding the caller's geographical location information to the caliee, sending an audio message to the caliee prior to connecting the call, and/or activating a warning signal detectable by the caliee.
[0030] Step S130, may include evaluating whether the caller's geographical location is in the same geographical area as a location of a first network operator node accessed to initiate the call. If the caller's geographical location is not in the same geographical area as the first network operator node's location, then the caller is suspicious. There are various sources from which a network operator device may
acquire the first operator node's geographical location. For example, a node's geographical location may be using device's Location Area Identity (LAI). LAI is a unique number that identifies a particular location on Earth.
[0031] Figure 2 illustrates communications between a caller UE 210, a network device 220, and a callee UE 230 (time order of the illustrated operations is from up to down), in a SIP environment. A new optional but un-modifiable header is enabled (i.e., to be generated and transmitted) in this SIP environment. This new header named, for example, "P-Origination-Location," carries the caller's geographical location information. This header may include a text string and may be generated by the caller's UE upon receiving a request from its first network node. The first network node may perform a veracity check of this text string.
[0032] As illustrated in Figure 2, first (at 1 ), the caller UE 210 sends an SIP INVITE message to initiate a VOIP call with the callee. Although in Figure 2, no visited devices are illustrated between the caller UE 210 and the network device 220, such other devices may be present. The callee UE and the network device may pertain to a different network than the caller UE.
[0033] Upon receiving the SIP INVITE message, the network device 220 determines whether the callee is vulnerable at 2. Steps 3-1 1 , which are labeled A1 , follow if determined that the callee is vulnerable, and steps 12-14, which are labeled A2, follow if determined that the callee is not vulnerable. Determining that the callee is vulnerable triggers requesting, generating and transmitting the P- Origination-Location header in the network. Thus, if the callee is vulnerable (A1 ), the network device 220 sends SIP response 1xx to caller UE 210 requesting the caller UE to provide P-
Origination-Location header, at 3. Then, at 4, the caller UE 210 sends an SIP UPDATE message including the P-Origination-Location header to the network device 220.
[0034] The network device 220 verifies the P-Origination-Location header's veracity at 5. Steps 6-9, which are labeled B1 , follow if veracity is confirmed, and steps 10 and 1 1 , which are labeled B2, follow if veracity is not confirmed. If the P-Origination- Location header's veracity is confirmed (B1 ), the network device 220 replies by sending a "200 UPDATE" SIP message to the caller UE 210 at 6, and then responds to the initial SIP INVITE received at 1 , by sending a "1xx INVITE" message to the caller UE 210 at 7.
[0035] The network device 220 then sends a "SIP INVITE" message including the "P-Origination-Location" header to the callee UE 230 at 8. Upon receiving this "SIP INVITE" message, the callee UE 230 conveys the caller's location information from the P-Origination-Location header to the callee, using the ringtone, a voice message and/or displaying this information at 9. The known flow of the VOIP call then follows.
[0036] If the network device 220 determines that the P-Origination-Location header's veracity is not confirmed (B2), then the call is rejected by the network device that sends a "4xx UPDATE" reject message at 10, and a "4xx INVITE" reject message at 1 1 , to the caller UE 210. The network device 220 may transmit an indication (e.g., a 0 value instead of a valid location) in the P-Origination-Location header if it has already determined that the caller is suspicious.
[0037] If at 2, the network device 220 determined that the callee is not vulnerable (A2), then the network device 220 sends a "1xx INVITE" message to the caller UE 210 at 12, and a "SIP INVITE" message to the callee UE 230 at 13. Upon receiving the "SIP INVITE" message at 13, the callee UE 230 produces the regular ringtone at 14.
[0038] The network device may perform an integrity check of the P-Origination- Location header received from the caller UE. For example, the network device may verify whether the geographical location information provided by caller UE is in the same geographical area (like city, or region) of the first traversed network node. The geographical coordinates of the first network node may be correlated to a specific area of the city and country.
[0039] If callee UE is a smart phone, the geographical location information can be displayed directly on the screen with the phone number. This type of callee UE may also indicate that the caller is suspicious if instead of the location information it has been received an indication that the caller is suspiciou (e.g., a "0" value). The smart phones may also use a special ring tone to signal a suspicious caller. If callee UE is an older phone, then the network device may translate the geographical location information into an audio message causing the phone to play it either as a ringtone or a voice
announcement when the callee picks up the call.
[0040] To summarize, the features that enable an enhanced VOIP security are:
• an additional network header that is optional but non-modifiable for VOIP
applications;
• the network device evaluates if the callee is vulnerable;
• if determined that the callee is vulnerable, the network device requests additional geographical location information of the caller to check if caller is suspicious;
• network device performs an integrity check of the geographical location
information
• if integrity is confirmed, network device provides the geographical location information to the callee.
• if integrity is not confirmed, then the callee is informed that the caller is
suspicious.
[0041] Figure 3 is a block diagram of a network device 300 including a communication interface 310 and a processing unit 320. The communication interface is configured to exchange messages with other devices in a communication network 312. The communication interface may receive a message including the caller's geographical location information in an unmodifiable header.
[0042] The processing unit includes at least one processor and is connected to the communication interface. The processing unit is configured to determine whether a scrutiny of a caller is required when a call is initiated, to control the communication interface to request a caller's geographical location information if the scrutiny is required, and to check veracity of the caller's geographical location information to determine whether the caller is suspicious.
[0043] The processing unit may determine that the scrutiny is required if a cailee's profile includes an indication that an enhanced VOIP security is required. The data processing unit may have added this indication in the cailee's profile upon receiving a request. The processing unit may determine that the scrutiny is required if analyzing the CDR reveals that caller's calls have often been rejected by other callees, or that the callers calls have lasted frequently less than a predetermined time interval. Additionally, the processing unit may determine that the scrutiny is not required if
analyzing the CDR reveals that prior calls between the caller and the cailee lasted in average longer than a predetermined duration.
[0044] The processing unit may control the communication interface to inform the cailee before connecting the call, or not connecting the call to the cailee, if the caller is suspicious. The communication interface may inform the cailee that the caller is suspicious by forwarding the caller's geographical location to the cailee, triggering an audio message prior to connecting the call, or activating a warning signal (e.g., a specific ringtone) detectable by the cailee.
[0045] The processing unit may check the veracity by evaluating whether the caller's geographical location is in a same geographical area as a location of a first network operator node accessed to initiate the call.
[0046] Network operator device 300 may also include a memory 340 and an operator interface 330. The memory may store executable codes which, when executed by the processing unit make the processing unit to determine whether the scrutiny is required, to control the communication interface, and to check the veracity of the caller's geographical location information.
[0047] According to another embodiment, a network operator device 400 is illustrated in Figure 4. This device is configured to enhance security of VOIP calls and includes a logic module 410, an information demand module 420 and a verification module 430. Logic module 410 determines whether a scrutiny of a caller is required, when a call is initiated. Information demand module 420 requests caller's geographical location information when the logic module has determined that the scrutiny is required.
Verification module 430 checks veracity of the caller's geographical location information to determine whether the caller is suspicious.
[0048] Figure 5 illustrates a client device 500, which may operate as the callers phone. Device 500 includes a communication interface 510 configured to send and receive messages from other devices in a communication network, and a data processing unit 520. Data processing unit 520, which includes at least one processor and is connected to the communication interface, is configured to control the
communication interface to send a message with an unmodifiable header (e.g., a P- Origination-Location header) including geographical location information of the client device, upon request.
[0049] According to yet another embodiment, there is a network node configured to serve client devices in a predetermined area. The network node may have the same structure as the device illustrated in Figure 3. The network node according to this embodiment is enabled to obtain its location and a range of an area it covers (i.e., the node is configured to provide network connectivity to devices within the covered area). The network node may have a Global Positioning Satellite (GPS) module, which enables it to identify its location. Alternatively, the network node's location may be a parameter provided by the network when setting up the network node. The network may additionally also inform the network node about its coverage (for example, a circle whose center is the network node's location and radius is 100 km). The coverage may also be a configurable parameter.
[0050] Unlike conventional network nodes, upon receiving a connection request from a device, this network node (the processing unit thereof) verifies if the device's
location information included in a P-Origination-Location header is within its service range. If the device's location information in the P-Origination-Location header is not within the network node's service range, the network node may either reject the connection request, or forward the request with the P-Origination-Location header and an indication that the caller is suspicious.
[0051] The methods and devices described in this section enhance VOIP security using reliable caller geographic location information. The caller has to reveal its geographical location information. Having this information makes it more likely that a vulnerable person is warned to be cautious. For example, if a caller pretending to be your local bank is located in a different country, the callee is on notice. The caller's geographical location information may be transmitted using an SIP header that once associated with a message cannot be modified by visited network devices.
[0052] Thus, the embodiments disclosed in this section provide methods and network devices that enhance security of VOIP calls based on reliable location information for the caller. It should be understood that this description is not intended to limit the invention. On the contrary, the exemplary embodiments are intended to cover alternatives, modifications and equivalents, which are included in the spirit and scope of the invention. Further, in the detailed description of the exemplary embodiments, numerous specific details are set forth in order to provide a comprehensive
understanding of the invention. However, one skilled in the art would understand that various embodiments may be practiced without such specific details.
[0053] Although the features and elements of the present exemplary
embodiments are described in the embodiments in particular combinations, each
feature or element can be used alone without the other features and elements of the embodiments or in various combinations with or without other features and elements disclosed herein. The methods or flowcharts provided in the present application may be implemented in a computer program, software or firmware tangibly embodied in a computer-readable storage medium for execution by a computer or a processor.
[0054] This written description uses examples of the subject matter disclosed to enable any person skilled in the art to practice the same, including making and using any devices or systems and performing any incorporated methods. The patentable scope of the subject matter is defined by the claims, and may include other examples that occur to those skilled in the art. Such other examples are intended to be within the scope of the claims.
Claims
1. A method (100) performed by a network operator, for enhancing security of Voice Over Internet Protocol, VOIP, calls, the method comprising:
determining (S1 10) whether a scrutiny of a caller is required when a call is initiated;
if the scrutiny is required, requesting (S120) a caller's geographical location information; and
checking (S130) veracity of the caller's geographical location to determine whether the caller is suspicious.
2. The method of claim 1 , wherein the scrutiny is required if a callee's profile includes an indication for enhanced VOIP security service,
3. The method of claim 2, further including:
receiving a request to include the indication for enhanced VOIP security in the callee's profile.
4. The method of claims 1 or 2, wherein whether the scrutiny is required is determined by analyzing a call detail record, CDR, of the caller.
5. The method of claim 4, wherein the analyzing of the CDR determines that the scrutiny is required if caller's calls have often been rejected by other callees and/or if the caller's calls lasted frequently less than a predetermined time interval.
8. The method of claims 4 or 5, wherein the analyzing of the CDR determines that the scrutiny is not required if prior calls between the caller and the cailee lasted longer than a predetermined duration.
7. The method according to any of claims 1 to 6, wherein the requesting includes receiving a reply message with the caller's geographical location included in an unmodifiable header.
8. The method according to any of claims 1 to 7, further comprising:
if the caller is suspicious, informing the cailee before connecting the call, or rejecting the call.
9. The method of claim 8, wherein the informing is achieved by at least one of;
forwarding the caller's geographical location to the cailee;
sending an audio message to the cailee prior to connecting the call; and activating a warning signal detectable by the cailee.
10. The method according to any of claims 1 to 9, wherein the checking includes evaluating whether the caller's geographical location is in a same geographical area as a location of a first network operator node accessed to initiate the call.
1 1 . A network operator device (300) configured to enhance security of Voice Over IP, VOIP, calls, the network operator device comprising:
a communication interface (310) configured to exchange messages with other devices in a communication network; and
a processing unit (320) that includes at least one processor, is connected to the communication interface and is configured
to determine whether a scrutiny of a caller is required when a call is initiated,
to control the communication interface to request a caller's geographical location if the scrutiny is required, and
to check veracity of the caller's geographical location to determine whether the caller is suspicious.
12. The network operator device of claim 1 1 , wherein the scrutiny is required if a callee's profile includes an indication that an enhanced VOIP security is required.
13. The network operator device of claim 12, wherein the processing unit adds the indication in the callee's profile upon receiving a request.
14. The network operator device of claims 1 1 or 12, wherein the processing unit determines whether the scrutiny is required based on analyzing a call detail record, CDR, of the caller.
15. The network operator device of claim 14, wherein the processing unit determines that the scrutiny is required if analyzing the CDR reveals that
caller's calls have often been rejected by other callees, or
the caller's calls have lasted frequently less than a predetermined time interval.
16. The network operator device of claims 14 or 15, wherein the processing unit determines that the scrutiny is required if analyzing the CDR reveals that prior calls between the caller and the caliee lasted in average longer than a predetermined duration.
17. The network operator device according to any of claims 1 1 to 16, wherein the communication interface receives a message including the caller's geographical location information in an unmodifiable header.
18. The network operator device according to any of claims 1 1 to 16, wherein if the caller is suspicious, the processing unit controls the communication interface to inform the cailee before connecting the call, or not connecting the call to the cailee.
19. The network operator device of claim 18, wherein the communication interface informs the cailee that the caller is suspicious by at least one of;
forwarding the caller's geographical location to the cailee;
triggering an audio message prior to connecting the call; and
activating a warning signal detectable by the cailee.
20. The network operator device according to any of claims 1 1 to 19, wherein the processing unit checks the veracity by evaluating whether the caller's geographical location is in a same geographical area as a location of a first network operator node accessed to initiate the call.
21 . The network operator device according to any of claims 1 1 to 20, further comprising:
a non-transitory computer readable medium storing executable codes which, when executed by the processing unit make the processing unit to determine whether the scrutiny is required, to control the communication interface, and to check the veracity of the caller's geographical location information.
22. A network operator device (400) configured to enhance security of Voice Over IP, VOIP, calls, the network operator device comprising:
a logic module (410) determining whether a scrutiny of a caller is required, when a call is initiated;
an information demand module (420) requesting caller's geographical location information when the logic module has determined that the scrutiny is required; and a verification module (430) checking veracity of the caller's geographical location information to determine whether the caller is suspicious.
23. A client device (500) in a communication network, the client device comprising:
a communication interface (510) configured to send and receive messages from other devices in the communication network; and
a data processing unit (520) that includes at least one processor, is connected to the communication interface and is configured to control the communication interface to send a message with an unmodifiable header including geographical location information of the client device, upon request.
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP16758300.4A EP3501192B1 (en) | 2016-08-18 | 2016-08-18 | Method and device for enhancing voip security by selectively scrutinizing caller's geographical location |
US16/325,861 US11330430B2 (en) | 2016-08-18 | 2016-08-18 | Method and device for enhancing VOIP security by selectively scrutinizing caller's geographical location |
CN201680090210.1A CN109845236A (en) | 2016-08-18 | 2016-08-18 | For enhancing the method and apparatus of VOIP safety by selectively examining the geographical location of calling party |
PCT/SE2016/050771 WO2018034605A1 (en) | 2016-08-18 | 2016-08-18 | Method and device for enhancing voip security by selectively scrutinizing caller's geographical location |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/SE2016/050771 WO2018034605A1 (en) | 2016-08-18 | 2016-08-18 | Method and device for enhancing voip security by selectively scrutinizing caller's geographical location |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2018034605A1 true WO2018034605A1 (en) | 2018-02-22 |
Family
ID=56851668
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/SE2016/050771 WO2018034605A1 (en) | 2016-08-18 | 2016-08-18 | Method and device for enhancing voip security by selectively scrutinizing caller's geographical location |
Country Status (4)
Country | Link |
---|---|
US (1) | US11330430B2 (en) |
EP (1) | EP3501192B1 (en) |
CN (1) | CN109845236A (en) |
WO (1) | WO2018034605A1 (en) |
Families Citing this family (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11330430B2 (en) * | 2016-08-18 | 2022-05-10 | Telefonaktiebolaget Lm Ericsson (Publ) | Method and device for enhancing VOIP security by selectively scrutinizing caller's geographical location |
US10542137B1 (en) * | 2018-08-10 | 2020-01-21 | T-Mobile Usa, Inc. | Scam call back protection |
US10750000B1 (en) * | 2019-01-28 | 2020-08-18 | Blackberry Limited | Opportunistic initiation of voice or video calls between smart speaker devices |
US10827338B1 (en) * | 2019-08-01 | 2020-11-03 | T-Mobile Usa, Inc. | Scam mitigation back-off |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20070041513A1 (en) * | 2005-02-08 | 2007-02-22 | Gende Michael F | Emergency call identification, location and routing method and system |
US20120213082A1 (en) * | 2011-02-18 | 2012-08-23 | Verizon Patent And Licensing Inc. | PREVENTION OF CALL SPOOFING IN A VOICE OVER INTERNET PROTOCOL (VoIP) NETWORK |
US20140137199A1 (en) * | 2005-04-26 | 2014-05-15 | Guy Hefetz | Method and system for authenticating internet users |
Family Cites Families (87)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5001710A (en) * | 1989-10-24 | 1991-03-19 | At&T Bell Laboratories | Customer programmable automated integrated voice/data technique for communication systems |
US7149296B2 (en) * | 2001-12-17 | 2006-12-12 | International Business Machines Corporation | Providing account usage fraud protection |
DE602004016115D1 (en) * | 2004-04-08 | 2008-10-09 | Accenture Global Services Gmbh | Method and device for remote monitoring of a measuring device |
US7940746B2 (en) * | 2004-08-24 | 2011-05-10 | Comcast Cable Holdings, Llc | Method and system for locating a voice over internet protocol (VoIP) device connected to a network |
US8903859B2 (en) * | 2005-04-21 | 2014-12-02 | Verint Americas Inc. | Systems, methods, and media for generating hierarchical fused risk scores |
US10521786B2 (en) * | 2005-04-26 | 2019-12-31 | Spriv Llc | Method of reducing fraud in on-line transactions |
WO2007061790A2 (en) * | 2005-11-18 | 2007-05-31 | Telecommunication Systems, Inc. | Voice over internet protocol (voip) mobility detection |
US9635172B2 (en) * | 2006-04-13 | 2017-04-25 | Tp Lab Inc. | Selective voice communication among multiple services |
US8036356B1 (en) * | 2006-08-08 | 2011-10-11 | Avaya Inc. | System and method of identifying geographic location for the source of a call |
US8340711B1 (en) * | 2006-08-18 | 2012-12-25 | At&T Mobility Ii Llc | Dual mode service WiFi access control |
US8270588B2 (en) * | 2006-10-04 | 2012-09-18 | Ronald Schwartz | Method and system for incoming call management |
US8548447B1 (en) * | 2006-10-06 | 2013-10-01 | Callwave Communications, Llc | Methods and systems for blocking unwanted telecommunications |
US20080086226A1 (en) * | 2006-10-10 | 2008-04-10 | Gene Fein | Internet enabled voice communication |
ATE476049T1 (en) * | 2006-12-08 | 2010-08-15 | Ubs Ag | METHOD AND DEVICE FOR DETECTING THE IP ADDRESS OF A COMPUTER AND ASSOCIATED LOCATION INFORMATION |
US20080170672A1 (en) * | 2007-01-16 | 2008-07-17 | Lucent Technologies, Inc. | Enhanced telecommunications greeting system |
WO2009076971A1 (en) * | 2007-12-14 | 2009-06-25 | Telefonaktiebolaget Lm Ericsson (Publ) | A method of and an arrangement for call establishment between an internet communication environment and a mobile communication environment |
WO2009131505A1 (en) * | 2008-04-25 | 2009-10-29 | Telefonaktiebolaget Lm Ericsson (Publ.) | Methods and arrangements for interactive caller information services in a communication network |
US9036812B2 (en) * | 2008-05-01 | 2015-05-19 | At&T Intellectual Property I, Lp | Method and apparatus for selecting communication identifiers |
US8312660B1 (en) * | 2008-05-09 | 2012-11-20 | Iwao Fujisaki | Firearm |
US8229812B2 (en) * | 2009-01-28 | 2012-07-24 | Headwater Partners I, Llc | Open transaction central billing system |
US9264856B1 (en) * | 2008-09-10 | 2016-02-16 | Dominic M. Kotab | Geographical applications for mobile devices and backend systems |
GB0820447D0 (en) * | 2008-11-07 | 2008-12-17 | Skype Ltd | Location information in a communications system |
IL195506A (en) * | 2008-11-25 | 2015-06-30 | Verint Systems Ltd | Systems and methods for correlating multiple location sources |
US8195817B2 (en) * | 2009-02-11 | 2012-06-05 | Sprint Communications Company L.P. | Authentication of the geographic location of wireless communication devices |
US8145274B2 (en) * | 2009-05-14 | 2012-03-27 | International Business Machines Corporation | Automatic setting of reminders in telephony using speech recognition |
US8391859B1 (en) * | 2009-08-12 | 2013-03-05 | Sprint Spectrum L.P. | Redirection of a roaming wireless communication device and nearby home base station to achieve home carrier service |
US8457651B2 (en) * | 2009-10-02 | 2013-06-04 | Qualcomm Incorporated | Device movement user interface gestures for file sharing functionality |
US8601146B2 (en) * | 2009-10-21 | 2013-12-03 | Tekelec, Inc. | Methods, systems, and computer readable media for session initiation protocol (SIP) identity verification |
US9148376B2 (en) * | 2010-12-08 | 2015-09-29 | AT&T Intellectual Property I, L.L.P. | Method and system for dynamic traffic prioritization |
US8752174B2 (en) * | 2010-12-27 | 2014-06-10 | Avaya Inc. | System and method for VoIP honeypot for converged VoIP services |
US9258264B1 (en) * | 2011-03-30 | 2016-02-09 | Google Inc. | Processing socially networked entities |
EP2700019B1 (en) * | 2011-04-19 | 2019-03-27 | Seven Networks, LLC | Social caching for device resource sharing and management |
KR101830732B1 (en) * | 2011-09-30 | 2018-04-05 | 삼성전자 주식회사 | Method and apparatus for controlling system overload in wireless communication |
US8811183B1 (en) * | 2011-10-04 | 2014-08-19 | Juniper Networks, Inc. | Methods and apparatus for multi-path flow control within a multi-stage switch fabric |
EP2771715B1 (en) * | 2011-10-24 | 2017-07-19 | Helmholtz Zentrum München - Deutsches Forschungszentrum für Gesundheit und Umwelt (GmbH) | Method for measuring radiation by means of an electronic terminal having a digital camera |
US8705490B2 (en) * | 2011-12-23 | 2014-04-22 | Verizon Patent And Licensing Inc. | Handing over a user device from one technology to another |
US8428052B1 (en) * | 2012-05-14 | 2013-04-23 | Metropcs Wireless, Inc. | System and method for enhanced domain availability notification |
WO2012126422A2 (en) * | 2012-05-15 | 2012-09-27 | 华为技术有限公司 | Method, device and system for controlling account management operation |
US9959513B2 (en) * | 2012-05-29 | 2018-05-01 | Ophio Software, Inc. | Systems and methods involving features of sales force processing and/or productivity |
US8774369B2 (en) * | 2012-10-23 | 2014-07-08 | Telefonaktiebolaget L M Ericsson (Publ) | Method and system to provide priority indicating calls |
KR101487874B1 (en) * | 2012-12-20 | 2015-02-03 | 주식회사 팬택 | Terminal and method for transmission of user information |
US8634520B1 (en) * | 2013-01-31 | 2014-01-21 | Marchex, Inc. | Call tracking system utilizing an automated filtering function |
US9852416B2 (en) * | 2013-03-14 | 2017-12-26 | Lookout, Inc. | System and method for authorizing a payment transaction |
US8983047B2 (en) * | 2013-03-20 | 2015-03-17 | Telecommunication Systems, Inc. | Index of suspicion determination for communications request |
US20140379911A1 (en) * | 2013-06-21 | 2014-12-25 | Gfi Software Ip S.A.R.L. | Network Activity Association System and Method |
ITMI20131081A1 (en) * | 2013-06-28 | 2014-12-29 | Athonet S R L | RADIO ACCESS NETWORK CONTROL OF MEDIA SESSION |
US9501776B2 (en) * | 2013-09-09 | 2016-11-22 | Capital One Financial Corporation | System and method for automatically authenticating a caller |
US9350717B1 (en) * | 2013-09-23 | 2016-05-24 | Amazon Technologies, Inc. | Location service for user authentication |
US9148522B2 (en) * | 2013-09-27 | 2015-09-29 | Oracle International Corporation | Methods, systems, and computer readable media for determining policy information associated with an emergency call |
US9769317B2 (en) * | 2013-10-16 | 2017-09-19 | At&T Intellectual Property I, L.P. | Conference system with enhanced security and authentication |
WO2015061628A1 (en) * | 2013-10-26 | 2015-04-30 | Uva Mobile, Inc. | Systems and methods for creating and managing mobile phone services |
US9088560B1 (en) * | 2014-03-05 | 2015-07-21 | Symantec Corporation | Systems and methods for validating login attempts based on user location |
US9961543B2 (en) * | 2014-03-27 | 2018-05-01 | Beijing Nanbao Technology Co. Ltd. | Method and apparatus for wireless network authentication and authorization |
US9432965B2 (en) * | 2014-04-22 | 2016-08-30 | Comcast Cable Communications, Llc | Determining wireless coverage information using wireless access points |
US20170155767A1 (en) * | 2014-06-19 | 2017-06-01 | David Cohen | Methods circuits devices systems and associated computer executable code for providing digital services |
CN104093153B (en) * | 2014-06-25 | 2017-10-10 | 东方通信股份有限公司 | It is a kind of that the method and its system realized pseudo number call screening and intercepted are analyzed based on signalling route |
US10834592B2 (en) * | 2014-07-17 | 2020-11-10 | Cirrent, Inc. | Securing credential distribution |
US9203954B1 (en) * | 2014-07-31 | 2015-12-01 | Ringcentral, Inc. | Enhanced caller-ID information selection and delivery |
US9717017B2 (en) * | 2014-08-22 | 2017-07-25 | Seven Networks, Llc | Mobile device equipped with mobile network congestion recognition to make intelligent decisions regarding connecting to an operator network for optimize user experience |
US9509821B2 (en) * | 2014-09-01 | 2016-11-29 | Stanislav Zhekov | Method to mute automatically phone calls on mobile communication device |
US9672020B2 (en) * | 2014-09-19 | 2017-06-06 | Microsoft Technology Licensing, Llc | Selectively loading precompiled header(s) and/or portion(s) thereof |
CN105450617B (en) * | 2014-09-24 | 2019-07-09 | 阿里巴巴集团控股有限公司 | A kind of payment verification method, apparatus and system |
US9762683B2 (en) * | 2014-09-30 | 2017-09-12 | A 10 Networks, Incorporated | Use of packet header extension for geolocation/geotargeting |
US20160148332A1 (en) * | 2014-11-20 | 2016-05-26 | Blue Sun Technologies, Inc. | Identity Protection |
US9769312B1 (en) * | 2014-12-19 | 2017-09-19 | 8×8, Inc. | User-configurable recording of VoIP calls |
US20160189159A1 (en) * | 2014-12-29 | 2016-06-30 | Ebay Nc. | Peer location detection to determine an identity of a user |
US20160241676A1 (en) * | 2015-02-18 | 2016-08-18 | Dashcube LLC | Method and apparatus for storing, accessing and displaying past application states |
US9660954B2 (en) * | 2015-03-05 | 2017-05-23 | Algoblu Holdings Limited | VOIP routing based on RTP server-to-server routing |
US10755364B2 (en) * | 2015-03-23 | 2020-08-25 | Gloriam Technologies Pty Ltd. | Method and system for providing a social network for creating, sharing and accessing content based upon location and mobility-related profiles of users |
US9641680B1 (en) * | 2015-04-21 | 2017-05-02 | Eric Wold | Cross-linking call metadata |
CN104766014B (en) * | 2015-04-30 | 2017-12-01 | 安一恒通(北京)科技有限公司 | For detecting the method and system of malice network address |
US9779271B2 (en) * | 2015-06-08 | 2017-10-03 | Juniper Networks, Inc. | Apparatus, system, and method for detecting theft of network devices |
US9872148B2 (en) * | 2015-06-10 | 2018-01-16 | Voalte, Inc. | Adaptive mobile wireless call rescue |
US10075807B2 (en) * | 2015-06-30 | 2018-09-11 | Qualcomm Incorporated | Ground-based location systems and methods |
US20170010783A1 (en) * | 2015-07-07 | 2017-01-12 | The John Avery Company | Emergency call smart phone application |
US9898321B2 (en) * | 2015-07-23 | 2018-02-20 | At&T Intellectual Property I, L.P. | Data-driven feedback control system for real-time application support in virtualized networks |
WO2017023860A1 (en) * | 2015-07-31 | 2017-02-09 | Modulus Technology Solutions Corp. | Estimating wireless network load and adjusting applications to minimize network overload probability and maximize successful application operation |
US10375082B2 (en) * | 2015-08-20 | 2019-08-06 | Averon Us, Inc. | Method and apparatus for geographic location based electronic security management |
US9985945B2 (en) * | 2015-10-22 | 2018-05-29 | Sap Se | Spoofing protection protocol for network-connected things |
US10334111B2 (en) * | 2015-11-23 | 2019-06-25 | Tracfone Wireless, Inc. | Device, system, and process for providing emergency calling service for a wireless device using voice over data |
US9961194B1 (en) * | 2016-04-05 | 2018-05-01 | State Farm Mutual Automobile Insurance Company | Systems and methods for authenticating a caller at a call center |
US10038793B2 (en) * | 2016-04-06 | 2018-07-31 | T-Mobile Usa, Inc. | VoIP adapter for connecting landline phones to IP routers |
WO2017204053A1 (en) * | 2016-05-23 | 2017-11-30 | 日本電気株式会社 | Service provision device, service provision method, and program recording medium |
US10257591B2 (en) * | 2016-08-02 | 2019-04-09 | Pindrop Security, Inc. | Call classification through analysis of DTMF events |
CA2975044A1 (en) * | 2016-08-02 | 2018-02-02 | Capital One Services, Llc | Systems and methods for proximity identity verification |
US11330430B2 (en) * | 2016-08-18 | 2022-05-10 | Telefonaktiebolaget Lm Ericsson (Publ) | Method and device for enhancing VOIP security by selectively scrutinizing caller's geographical location |
US9774726B1 (en) * | 2016-12-22 | 2017-09-26 | Microsoft Technology Licensing, Llc | Detecting and preventing fraud and abuse in real time |
-
2016
- 2016-08-18 US US16/325,861 patent/US11330430B2/en active Active
- 2016-08-18 CN CN201680090210.1A patent/CN109845236A/en active Pending
- 2016-08-18 EP EP16758300.4A patent/EP3501192B1/en active Active
- 2016-08-18 WO PCT/SE2016/050771 patent/WO2018034605A1/en unknown
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20070041513A1 (en) * | 2005-02-08 | 2007-02-22 | Gende Michael F | Emergency call identification, location and routing method and system |
US20140137199A1 (en) * | 2005-04-26 | 2014-05-15 | Guy Hefetz | Method and system for authenticating internet users |
US20120213082A1 (en) * | 2011-02-18 | 2012-08-23 | Verizon Patent And Licensing Inc. | PREVENTION OF CALL SPOOFING IN A VOICE OVER INTERNET PROTOCOL (VoIP) NETWORK |
Also Published As
Publication number | Publication date |
---|---|
US20190215346A1 (en) | 2019-07-11 |
US11330430B2 (en) | 2022-05-10 |
EP3501192B1 (en) | 2021-03-31 |
CN109845236A (en) | 2019-06-04 |
EP3501192A1 (en) | 2019-06-26 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US11146939B2 (en) | IMS emergency calls for roaming UEs | |
KR101243488B1 (en) | Coding and behavior when receiving an ims emergency session indicator from authorized source | |
EP2375629B1 (en) | Method and apparatus for transmitting/receiving in emergency services | |
US11330430B2 (en) | Method and device for enhancing VOIP security by selectively scrutinizing caller's geographical location | |
US8744053B2 (en) | Methods, apparatus, and computer program products for providing dynamic replacement communication identification service | |
US10681556B2 (en) | Mitigation of spoof communications within a telecommunications network | |
EP3162104B1 (en) | A method to authenticate calls in a telecommunication system | |
CN103155608A (en) | Enhanced registration messages in internet protocol multimedia subsystems | |
EP2426907B1 (en) | Malicious call detection apparatus, malicious call detecting method and computer program for detecting malicious calls | |
US10893140B2 (en) | Method, system and device for an enhanced call setup with verification of a user equipment in a telecommunications network | |
Mustafa et al. | End-to-end detection of caller ID spoofing attacks | |
WO2011161185A1 (en) | System and method for validating a user equipment location in a telecommunication network | |
US10778732B2 (en) | Method of detecting a spoofing of identity belonging to a domain | |
EP3758323A1 (en) | Call processing unit, method and computer program | |
EP4254863A1 (en) | Method for network-centric call verification and scam protection | |
KR101547994B1 (en) | System for Authentication a Caller based Authentication Contents | |
KR20160031342A (en) | System for Authentication a Caller and a Recipient based Authentication Contents | |
KR20160029650A (en) | System for Authentication a Caller based Authentication Contents | |
KR20160031343A (en) | System for Authentication a Caller and a Recipient based Authentication Contents |
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: 16758300 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
ENP | Entry into the national phase |
Ref document number: 2016758300 Country of ref document: EP Effective date: 20190318 |