EP3210369A1 - Verfahren zur filterung von nachrichten zur bereitstellung einer bitte-nicht-stören-funktion - Google Patents

Verfahren zur filterung von nachrichten zur bereitstellung einer bitte-nicht-stören-funktion

Info

Publication number
EP3210369A1
EP3210369A1 EP15798157.2A EP15798157A EP3210369A1 EP 3210369 A1 EP3210369 A1 EP 3210369A1 EP 15798157 A EP15798157 A EP 15798157A EP 3210369 A1 EP3210369 A1 EP 3210369A1
Authority
EP
European Patent Office
Prior art keywords
message
terminal
server
identifier
database
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Withdrawn
Application number
EP15798157.2A
Other languages
English (en)
French (fr)
Inventor
Robin MARTINE
Richard Tucker
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Orange SA
Original Assignee
Orange SA
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Orange SA filed Critical Orange SA
Publication of EP3210369A1 publication Critical patent/EP3210369A1/de
Withdrawn legal-status Critical Current

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M3/00Automatic or semi-automatic exchanges
    • H04M3/42Systems providing special services or facilities to subscribers
    • H04M3/436Arrangements for screening incoming calls, i.e. evaluating the characteristics of a call before deciding whether to answer it
    • H04M3/4365Arrangements 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
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M3/00Automatic or semi-automatic exchanges
    • H04M3/42Systems providing special services or facilities to subscribers
    • H04M3/42025Calling or Called party identification service
    • H04M3/42034Calling party identification service
    • H04M3/42059Making use of the calling party identifier
    • H04M3/42068Making use of the calling party identifier where the identifier is used to access a profile
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M3/00Automatic or semi-automatic exchanges
    • H04M3/42Systems providing special services or facilities to subscribers
    • H04M3/436Arrangements for screening incoming calls, i.e. evaluating the characteristics of a call before deciding whether to answer it
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M3/00Automatic or semi-automatic exchanges
    • H04M3/42Systems providing special services or facilities to subscribers
    • H04M3/50Centralised arrangements for answering calls; Centralised arrangements for recording messages for absent or busy subscribers ; Centralised arrangements for recording messages
    • H04M3/53Centralised arrangements for recording incoming messages, i.e. mailbox systems
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/12Messaging; Mailboxes; Announcements
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/16Communication-related supplementary services, e.g. call-transfer or call-hold
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M2203/00Aspects of automatic or semi-automatic exchanges
    • H04M2203/20Aspects of automatic or semi-automatic exchanges related to features of supplementary services
    • H04M2203/2005Temporarily overriding a service configuration
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M3/00Automatic or semi-automatic exchanges
    • H04M3/42Systems providing special services or facilities to subscribers
    • H04M3/42382Text-based messaging services in telephone networks such as PSTN/ISDN, e.g. User-to-User Signalling or Short Message Service for fixed networks

Definitions

  • the present invention generally relates to the field of communications systems, and more specifically to the provision of a "do not disturb" type service.
  • US Patent 5,467,388 describes a system for providing a selective blocking of calls, which allows to provide a service "do not disturb".
  • the service offers a user the ability to configure a list of privileged contacts ("whitelist").
  • whitelist a list of privileged contacts
  • the user can also define access codes. A caller will then have to provide a valid access code to be put in contact with the user. The user thus gains some control over who can disturb him via the constitution of the whitelist or the possibility of providing access codes to certain people.
  • the invention proposes to remedy the disadvantages previously discussed by proposing a method of filtering messages sent by a first terminal, identified by a first identifier, to a second terminal, the terminals being connected via at least one communication network, the communication network comprising a server connected to a database, the database comprising at least a first predefined list of identifiers, the server executing the following steps: receiving a first message sent by the first terminal to the second terminal, registering the first message in the database, determining whether the first identifier belongs to the first list, and, if so, sending a second message to the first terminal, the second message comprising a sender field equal to a second identifier, or, if not, send a second message to the first terminal, the second message comprising a sender field equal to a third identifier.
  • the second terminal it is therefore possible to intercept and record a first message to the second terminal.
  • the user of the second terminal will not be disturbed by receiving the first message on the second terminal, the first message not being received by the second terminal but intercepted and recorded by the server.
  • the receipt of a message on a terminal is often accompanied by a ringing, vibration and / or visual effect on the terminal screen which can be considered as disturbing at certain times by the user of a terminal .
  • the second message makes it possible to warn the first terminal of the interception of the first message, and thus of its non-delivery to the second terminal.
  • the first identifier - typically a telephone number - belongs to the first list, the identifier of the sender of the second message will be different.
  • the first identifier belongs to the first list or to a third identifier if not.
  • the user of the first terminal chooses to respond to this second message, it will respond by sending a message to an identifier that will differ depending on the case.
  • the user of the second terminal can therefore, by the use of the first list of identifiers - that is to say for example of a first list of telephone numbers in a GSM / UMTS context -, choose a differentiated answer for the different users.
  • These users are identified by their telephone numbers, for example by putting the corresponding numbers to known or priority user terminals in the first list. These users will therefore receive a second message with as issuer identifier the second identifier.
  • the method comprises the following subsequent steps of receiving a third message sent by the second request terminal for deactivating the filter service provided by the present method and sending to the second terminal.
  • the user of the second terminal can therefore disable the message filtering service according to the present application by sending a third message.
  • the processing of messages sent to the second terminal will then be done normally, that is to say without interception or recording, once the service is disabled. All messages possibly received by the server to the second terminal and stored in the database are then sent to the second terminal.
  • the method comprises the following subsequent steps of receiving a fourth message sent by the first terminal, the recipient field of the fourth message comprising a fourth identifier, and if the fourth identifier is equal to the second identifier. or if the fourth identifier is equal to the third identifier, then a recorded message is found in the database and is sent to the second terminal, or, if not, the fourth message is ignored.
  • the user of the first terminal having received in response to his first message a second message, can unblock the sending of his first message by sending a fourth message, fourth message which has as identifier of destination the identifier corresponding to the sending field of the second message that it has received in return for the first message sent.
  • the first message is thus unlocked, that is to say that it is found in the database and sent to its recipient, that is to say the second terminal.
  • This method advantageously provides a "do not disturb" service to the second terminal while preserving the possibility of an unpredictable case. Indeed, any user of the first terminal that sends a first message to the second terminal receives in return a second message, whether previously known or not, or in other words, whether it is previously identified in a first list or not.
  • This user of the first terminal therefore retains the ability to respond to the second message - knowingly - to unblock the delivery of a first recorded message.
  • the user of the first terminal is therefore warned of the "do not disturb" status of the second terminal by the second message, and, according to his own judgment on the opportunity to still disturb the second user, can unlock the delivery of the first message.
  • the delivery of the first recorded message will be by a fifth message intended for second terminal. The possibility remains open to join a second terminal despite the status "do not disturb".
  • the retrieved message is the last of the recorded messages sent by the first terminal and destined for the second terminal, the method comprising a subsequent step of deleting this retrieved message from the database after its transmission to the second terminal. the second terminal.
  • the server sends the last first message sent by the first terminal to have been recorded in response to a fourth message received from the same terminal, on a principle comparable to a "first come, first out" operation.
  • the second message comprises a first reference identifying the first message stored in the database
  • the fourth message comprises a second reference corresponding to the first reference
  • the message sent to the second terminal is found in the database thanks to the second reference.
  • this allows a first user who has sent several first messages to select the first message to be unblocked - that is to say to find and send to the second terminal.
  • the selection is made by the indication in the fourth message of a reference, this reference having been provided in the second message.
  • the first messages recorded are therefore not released in a "first come, first out” mode but according to a selection by the first user, selection made thanks to the first reference provided in the second message.
  • the database comprises a second predefined list of identifiers, the method further comprising the following steps after receiving the first message: determining whether the first identifier belongs to the second list and, if so, transmit the first message to the second terminal without transmitting the second message.
  • the first messages received from a terminal whose identifier belongs to the second list are directly transmitted to the second terminal, even though the "do not disturb" service is active for this second terminal.
  • the identifiers of the second list are particular identifiers such as identifiers corresponding to emergency services (firefighters, hospitals, civil security, ...) or to certain identifiers previously identified by the user of the second terminal, messages from these identifiers not to be filtered.
  • the database comprises a third predefined list of identifiers, the method further comprising the following steps after receiving the first message: determining whether the first identifier belongs to the third predefined list, and, if yes, save the first message in the database without issuing the second message.
  • this embodiment makes it possible to record directly - without sending a second message in return - a first message received from a terminal whose identifier belongs to a third list. predefined. The possibility of deblocking by sending a fourth message is not proposed to the first terminal. This is particularly advantageous with regard to identifiers corresponding to "automata" type terminals or "automatic message sending servers".
  • controllers are unable to process a second message, and it is unnecessary to clutter the communications networks with second messages that would be intended.
  • these controllers often respond to messages sent to them by an automatic message specifying their status as an automaton and informing that the message will not be read or processed because addressed to a PLC.
  • an automatic message specifying their status as an automaton and informing that the message will not be read or processed because addressed to a PLC.
  • One could also be in a situation where the automatic response of a PLC to a second message corresponding to a fourth message, any first message sent by a PLC would therefore automatically - without validation step by a first user able to evaluate the urgency or the opportunity to disturb the second user - unblocked to the second terminal.
  • any controller would bypass the "do not disturb" service automatically. Placing the identifiers corresponding to PLCs in the third list overcomes this. The messages sent by these PLCs will therefore only be automatically delivered when the second user deactivates the "do not disturb" service. Note that identifiers corresponding to PLCs can also be placed in the second list, for example for a PLC corresponding to an emergency service.
  • At least one of the second and third identifiers corresponds to a value-added service number.
  • the second identifier, the third identifier, or both identifiers correspond to value-added service numbers, otherwise known as "premium-rate numbers". This generates a deterrent effect because there is then a real cost to disturb the second user, cost that materializes by sending the fourth message to a value-added service number.
  • the user of the second terminal can favor the users whose identifiers are included in the first predefined list.
  • terminal users whose identifiers are not included in the first predefined list can be given a cost of unblocking their first messages which is a strong deterrent by setting a high cost for the value-added service number corresponding to the third identifier. .
  • the messages are of short message type.
  • a message comprises at least one message of short type.
  • the method applies to the exchange of short messages of the type
  • SMS Short Message Service
  • MMS Multimedia Messaging Service
  • the invention also proposes a server implementing the method of filtering messages according to the various embodiments described above.
  • This server may be partly the second terminal. In other words, the method can be directly executed partly and locally by the second terminal. The interception of a message can be understood then by its non presentation to the user by the second terminal, or a more discrete presentation.
  • the first messages will be presented in the "discrete” mode (respectively not shown) when the fifth messages, corresponding to first unlocked messages, will be presented according to the "normal” mode (respectively in "discrete” mode).
  • the method for filtering messages sent by a first terminal to a second terminal can be implemented in the form of a computer program, this program being executed for example by one or multiple processors of a server connected to a database and at least one communication network. Therefore, according to a last aspect, the present invention relates to a computer program comprising program instructions for implementing all or part of the steps of the method for filtering messages sent by a first terminal to a destination. of a second terminal, when this program is executed by a processor.
  • a computer program according to the invention can use any programming language, and be in the form of source code, object code, or intermediate code between source code and object code, such as in a form partially compiled, or in any other desirable form.
  • the invention therefore also aims at a computer-readable information recording medium, comprising instructions of a computer program according to the invention.
  • a recording medium may be constituted by any entity or device capable of storing such a program.
  • the medium may comprise storage means, such as a ROM (Read Only Memory), for example a CD ROM or a microelectronic circuit ROM, or a removable recording means such as a USB key or magnetic recording means, such as a hard disk.
  • a software program or module according to the invention can in particular be downloaded to an Internet type network.
  • FIG. 1 A represents a server allowing the implementation of the method according to one embodiment of the invention
  • FIG. 1B is a schematic representation of a system according to an embodiment of the invention.
  • FIG. 2 is a flowchart illustrating the implementation of the invention according to one embodiment of the invention.
  • FIG. 1A represents a server allowing the implementation of the method according to an embodiment of the invention.
  • the server 100 may comprise a processor 101, a network module 102, a data storage space 103 and RAM (Random Acess Memory) 104.
  • the server 100 corresponds in this example to a physical device, that is, to say a hardware computing device.
  • the processor 101 may comprise one or more cores, or may correspond to more than one processor.
  • the network module 102 provides the connection means to at least one communication network. Since the server 100 is intended to be integrated in a communication network, the technology used by the network module 102 may vary according to the technology used in the communication network.
  • the network module may, for example, include an "Ethernet" type socket and offer Internet Protocol (IP) connectivity to the server 100.
  • IP Internet Protocol
  • the data storage space 103 may correspond to physical or virtual hard disks, accessible locally or via the network module 102.
  • the storage space 103 enables the server 100 to create, modify, manage databases, and therefore to save data, for example messages, in a database. These databases can be shared with other servers, ie create, manage or accessible from other servers.
  • the reference 103 will be used hereinafter to designate a database connected to the server 100.
  • This database 103 may therefore be local, that is to say included in FIG. server storage space 100, or remote, that is to say included in another server or plurality of servers.
  • the server 100 can therefore register in the database 103 messages received via the network module 102.
  • the server 100 can also find in the database 103 recorded messages and transmit these messages via the network module 102.
  • the server 100 can also record or find in the database 103 lists of identifiers.
  • the server 100 via the processor 101 can thus determine if an identifier of a message received via the network module 102 belongs to an identifier list.
  • FIG. 1B is a schematic representation of a system according to an embodiment of the invention. Is represented in this figure, a first terminal 1 10 connected to a communication network 150 and a second terminal 120 connected to a communication network 160.
  • the communication network 160 is possibly the same as the communication network 150.
  • the server 100 is here represented as included in the communication network 160.
  • the server 100 may also be a physical device independent of the communication network 160 and connected thereto.
  • the server 100 can also see its integrated functions and capabilities to another server already providing other services for the communication network 160.
  • These communication networks 150 and 160 are typically networks of the GSM / UMTS type, the terminals 1 10 and 120 being terminals of the type mobile phones, tablets, smartphones, etc.
  • the identifiers associated with the terminals 1 10 and 120 are also called telephone numbers (or "numbers").
  • the terminals 1 10 and 120 are therefore capable of establishing any type of communication as is known for GSM / UMTS communication networks.
  • the terminals 1 10 and 120 are likely to exchange messages of short message type, also called SMS (Short Message Service).
  • SMS Short Message Service
  • the server 100 is included in the communication network 160.
  • the server 100 may be included in the communication network 150 or in another communication network not shown in this FIG. 1 B. This will be particularly the case if the terminal 120 is roaming, that is to say, it is not connected to its usual communication network.
  • all the functions - or only certain functions - of the server 100 are integrated with a server providing other services.
  • the functions of the server 100 - or only certain functions - are performed by the terminal 120.
  • FIG. 2 is a flowchart illustrating the implementation of the invention according to one embodiment. This figure describes different message exchanges according to an implementation of the proposed method of filtering messages sent by the terminal 1 to the terminal 120.
  • This filtering method provides the user of the terminal 120 a service type "ne not disturb "(also called” DND “for” do not disturb ").
  • the server 100 conforms to the server 100 previously described.
  • the terminals 1 10 and 120 and the server 100 will be considered as included in the same communication network, for example GSM / UMTS type, without this being in any way limiting.
  • the operation of the terminals 1 10 and 120 is in accordance with the conventional operation of GSM type terminals.
  • these terminals can exchange SMS short messages.
  • a message sent by the terminal 1 10 will therefore be transmitted by the communication network and received by the terminal 120, which will signal the receipt of this message by vibrating, ringing or displaying a notification, potentially annoying the user of the terminal 120.
  • the Terminal user 120 who wishes to limit these disturbances can therefore activate a "do not disturb" type service, which will be provided by the implementation of the filtering method described in this document.
  • the user of the terminal 120 wishing to use the "do not disturb" service may have to install an application on its terminal 120 to use the service.
  • the installation of the application will be done according to the usual and known process, for example by going to recover this application on an application store such Play of Google, the App Store of Apple or the Windows Phone Store of Windows, for mention only the main shops used today.
  • the application will be preinstalled on the terminal 120 by the operator of the communication network or the manufacturer of the terminal 120, or directly integrated into the OS (Operating System) of the terminal.
  • the user of the terminal 120 may also recover the application on a site of a communication network operator.
  • a function of the application is in particular to enable or disable the "do not disturb" service, said activation or deactivation being done by sending a message to the server 100.
  • This message can be of any type , especially SMS or USSD (Unstructed Supplementary Service Data).
  • USSD Unstructed Supplementary Service Data
  • the messages exchanged between the second terminal 120 and the server 100 may be of any type, for example USSD or data messages transmitted by an Internet Protocol (IP) technology.
  • IP Internet Protocol
  • the user of the terminal 120 does not need to install or use a particular application and can activate the service by communicating with the server 100 by any type of method.
  • the user can indeed directly send SMS or USSD type messages without having to go through a particular application.
  • the user can also access the service, that is to say activate, deactivate or configure it, via a web interface.
  • the server 100 may or may not host the web server for configuring the service.
  • the installation of an application will be mandatory on the terminal 120, the application may include authentication mechanisms for communicating securely with the server 100 providing the message filtering service.
  • the message filtering service to the terminal 120 is activated.
  • the activation of the service is triggered by the receipt of a message 201 sent by the terminal 120.
  • the server 100 therefore receives a message 201 issued by the second activation terminal of the service.
  • the message 201 may be issued by another device and includes an identifier of the terminal 120.
  • the message 201 may include one or more activation request instructions of the filtering service.
  • the server 100 finds in the database 103 one or more predetermined lists associated with the terminal 120. These lists include identifiers and thus make it possible to customize the filtering of messages sent to the terminal 120 depending on the identifier of the sender of the messages. Alternatively, lists may be included in the received activation message. Lists can also be found on another remote server, for example a server operated by the service provider "do not disturb".
  • a first list of identifier can be formed.
  • the constitution of this green list can be done by the user of the terminal 120 or the operator of the service "do not disturb".
  • the advantage of this list is to define identifiers for which the delivery of messages to the terminal 120 will be immediate. Indeed, if the server 100 determines that an identifier of the sender of a message to the terminal 120 belongs to the green list, then this message will be transmitted directly to the terminal 120 without performing the subsequent steps of the filtering method . In other words, these messages coming from identifiers of the green list are not filtered.
  • This green list therefore corresponds to emergency service identifiers (firefighters, ...) or to identifiers added by the user of the terminal 120 according to his needs.
  • the user of the terminal 120 thus retains the possibility of adding identifiers for which the filtering will not be performed, even when the "do not disturb" service is active.
  • the part of the list corresponds to emergency service identifiers may be common to all users of the "do not disturb" service.
  • gray list Another list of identifiers, called “gray list”, can also be constituted.
  • This gray list may include identifiers type “short numbers” or “surcharges", or more generally identifiers corresponding to services.
  • This first source of identifiers for the gray list may be constituted by the operator of the "do not disturb" service, by the user of the terminal 120, or by the service operator and the user of the terminal 120.
  • a second source of identifiers for this list is the user of the terminal 120 who can add identifiers at his convenience. This list is intended to determine identifiers for which the filtering method will be partially achieved.
  • the messages from these identifiers will be recorded by the server 100 in the database 103 without being sent a message 207 in return. These messages will only be delivered when the user of the terminal 120 deactivates the "do not disturb" service.
  • the part of the gray list corresponding to service identifiers such as "short numbers” or “surcharges” may be common to all users of the "do not disturb” service.
  • white lists are a priori constituted by the user of the terminal 120 and correspond to identifiers that the user of the terminal 120 wishes to prioritize.
  • a different identifier NUM i can be associated with each whitelist i.
  • one or more predetermined lists for example of green, gray or white type, associated with the terminal 120 are obtained from the database 103
  • the filtering method allowing the provision of a "do not disturb” service is then started and will apply to the messages to the terminal 120 issued later.
  • This activation phase of the service may comprise a phase of modifying the routing of the messages to the terminal 120 within the communication network 160 so that, following the activation of the service, all the messages destined for this terminal 120 pass through the terminal.
  • the step of determining the membership of the identifier of the sender field (hereinafter, identifier of the sender) of a message destined for the terminal 120 to one of the predefined lists can be performed by another equipment of the communication network 160, only the messages requesting a particular treatment (recording for example) then passing through the server 100.
  • the determination of the membership of the identifier of the sending a message to the green list can be performed on a server other than the server 100.
  • the "do not disturb" service is therefore active for the terminal 120.
  • a message 203 confirming the proper activation of the service is sent to the terminal 120.
  • Step 206 corresponds to the receipt by the server 100 of a message 205 sent by a terminal 1 10 to the terminal 120, the identifier associated with the terminal 1 10 being NUM 1 10.
  • NUM 1 10 belongs to the green list. If this is the case, then, as previously seen, the message 205 will be directly transmitted to the terminal 120 without transmitting the second message 207. Similarly, if it is determined that NUM 1 10 belongs to the gray list associated with the terminal 120, then, as previously seen, the message 205 will be recorded in the database 103 without transmitting the second message 207.
  • These messages sent by a terminal 1 10 whose identifier belongs to a gray list and stored in the database 103 will be sent to the terminal 120 at the deactivation of the service.
  • the message 205 is stored in the database 103.
  • the server 100 determines the membership of NUM 1 10 to a predefined list associated with the terminal 120. If NUM 1 10 belongs to a list, for example a whitelist i, then the server sends a message 207 to the terminal 1 10, the message 207 having issuer identifier NUM i associated with the whitelist. In other words, the message 207 comprises a sender field equal to the identifier NUM i.
  • the server 100 sends a message 207 to the terminal 100, the message 207 having as issuer identifier a NUM d identifier.
  • the message 207 comprises a sender field equal to the identifier NUM d.
  • the message 207 includes a text informing the user of the terminal 1 10 that his message 205 has not been given to his correspondent because it has activated the service "do not disturb".
  • the user of the terminal 1 10 is therefore informed that the user of the terminal 120 does not wish to be disturbed.
  • the method of the present invention allows this as detailed below.
  • the assessment of the urgency of the situation is therefore based both on the user of the terminal 120 by the definition of the predefined lists, but also on the user of the terminal 1 10 who will decide alone whether to disturb or not the user of the terminal 120 after receiving a message 207.
  • His message 205 is stored in the database 103 and will be sent automatically by the server 100 to the terminal 120 when the "do not disturb" service will be disabled.
  • the service "do not disturb” can be disabled at the request by the user of the terminal 120, as will be seen, but also that the service can be disabled automatically.
  • a maximum duration of operation of the "do not disturb" service can be set. This duration may be common to all users or chosen by the user of the terminal 120 during the activation of the service, for example by indicating a maximum duration of operation of the service in the service activation message 201.
  • the terminal 1 10 sends the server 100 a message 210.
  • the sending of this message 210 is done by answering the message 207 received by the terminal 1 10.
  • the message 210 is sent to the sending identifier NUM i or NUM d of the message 207.
  • the messages at destination identifiers NUM i associated with the white lists or destination of the identifier NUM d are sent to the server 100.
  • Step 21 1 corresponds to the reception by the server 100 of a message 210 intended for NUM j and coming from NUM 1 10.
  • the destination field of the message 210 comprises a identifier NUM j.
  • the server determines the membership of NUM 1 10 to a predefined list, a predefined list associated with a NUM identifier k. If NUM k and NUM j correspond, that is to say are equal, then the server 100 finds in the database 103 a recorded message 212, sent by the terminal 1 10 to the terminal 120, and sends this message 212 at the terminal 120.
  • the message 212 corresponds to a message 205 previously recorded in the database 103.
  • NUM 1 10 does not belong to a predefined list, then the server 100 checks that NUM j corresponds to NUM d, that is to say that NUM j is equal to NUM d. If this is the case, then the server 100 finds in the database 103 a message 212 recorded, message sent by the terminal 1 10 to the terminal 120, and sends this message 212 to the terminal 120.
  • NUM identifier j does not correspond to the identifier associated with the list of identifiers to which belongs NUM 1 10, or if NUM 1 10 does not belong to a list, at NUM d, then the message 210 is ignored by the server 100.
  • This step of checking the consistency between NUM j and an expected identifier makes it possible to prevent a user of a list associated with an identifier from sending a message 210 to another identifier.
  • this makes it possible to prevent a user from sending a message 210 to a number other than the premium-rate number that he should use.
  • This is possible if this user does not respond to the message 207 - that is, reuses the number of the sender of the message 207 as the recipient - but edits a message 210 by choosing a recipient himself. Without this verification, a user of a terminal 1 10 could choose the least overtaxed premium number, weakening the effect of the method.
  • the step of checking the match between NUM j and respectively NUM k or NUM d is not performed. Indeed, in the hypothesis that the message sending rates to the second and third identifier would be different, and to prevent a first user sends a fourth message 210 only to the least expensive identifier, it is useful to verify that the destination identifier of the fourth message 210 corresponds to the issuer identifier of the second message 207. In other words, it is useful to check that the first user responds to the second message 207 by using the identifier contained in the sending field of the second message.
  • this verification step can be ignored. In other words, depending on the level of security sought, the step of verifying the correspondence of the identifiers may not be performed.
  • the server 100 determines whether the identifier NUM j is equal to a known identifier, that is to say an identifier associated with a predefined list or NUM d. If so, the server then finds in the database 103 a recorded message and which is intended for the second terminal 120 then sends this message found to the second terminal 120. If not, the message 210 is ignored.
  • a message 213 may be sent by the server 100 to the terminal 1 10 for confirmation of good reception of the message 210.
  • the message 213 is sent to indicate to the user of the terminal 1 10 that a message 212 has been sent to the terminal 120.
  • the message 212 sent to the terminal 120 can be found in the database 103 in different ways.
  • the message 212 recorded in the database 103 which is found and sent to the terminal 120 corresponds to the last message sent by the terminal 1 10 and to the terminal 120 to have been recorded in the database 103. otherwise, the retrieved message is the last of the recorded messages, sent by the first terminal 100 and to the second terminal 120.
  • This method therefore allows a "unlocking" of messages recorded on the principle of "last come first out”.
  • the message 212 found and sent may correspond instead to the first message sent by the terminal 1 10 and to the terminal 120 to have been recorded in the database 103, according to the principle of "first come, first out”.
  • the message 207 comprises a reference making it possible to identify the message 205 recorded in the database.
  • the message 210 includes the same reference, which allows the server to find in the database 103 the message 205 corresponding to this reference.
  • the message 212 sent then corresponds to the previously recorded message 205 which is referenced by the reference included in the message 210.
  • a message 205 received by the server 100 is therefore registered in the database 103 in association with a reference, the same reference being sent in the 207 message sent back.
  • the provision of this reference in a message 210 makes it possible to retrieve this message recorded in the database 103 and to send it to the second terminal 120.
  • this alternative method therefore allows to select which of these several messages will be found and sent following the receipt by the server 100 of a message 210.
  • the selection being made by the provision in the message 210 of the corresponding reference to the message stored in the database 103, reference received in a message 207.
  • a message 214 is sent by the terminal 120 to the terminal 1 10 to indicate the good reception of the message 212.
  • any message 205 sent by a terminal 1 10, to the terminal 120, and whose identifier is not included in an associated gray or green list at the terminal 120 will be recorded by the server 100 in a database 103.
  • the message 205 is not delivered to the terminal 120 at this stage.
  • a message 207 will be sent back to the terminal 1 10, the transmitting field of this message 207 will be dependent on the membership of the identifier of the terminal 1 10 to a predefined list associated with the terminal 120.
  • the user of the terminal 1 10 has the ability to respond to this message 207 by a message 210 to unblock the sending of a previously sent message 205.
  • Step 221 corresponds to the deactivation by the user of terminal 120 of the "do not disturb" service.
  • the deactivation can be automatic, for example after expiration of a predefined delay.
  • Other activation criteria or automatic deactivation of the service are possible.
  • a synchronization with a calendar-type application on the second terminal 120 can activate and terminate the service automatically at the beginning and at the end of a meeting.
  • the activation or deactivation of the service can also be triggered by the position of a sensor on the terminal 120, the face-down position on a table corresponding for example to the automatic activation of the service "do not disturb".
  • the user of the terminal 120 can also define time slots for activating the service.
  • a link with a geolocation-type application can also be used to activate or deactivate the service automatically when the terminal is in certain locations, possibly by adding time criteria.
  • the server 100 can automatically disable the service.
  • the server may need to receive a message 220 indicating the disabling the "do not disturb" service for the terminal 120.
  • the server 100 therefore receives a message 220 sent by the second terminal 120 request for deactivation of the service.
  • the server 100 finds all the messages 222 recorded in the database 103 and to the terminal 120 and sends them to the terminal 120. These messages 222 can then be deleted from the database 103.
  • the messages 222 as also the messages 212, have an issuer identifier corresponding to the original transmitter of the message, that is to say for example NUM 1 10 for a message 205 initially sent by the terminal 1 10.
  • the deactivation may include a step of modifying the routing of messages to the terminal 120.
  • the filtering method comprises a step 216, which can indifferently be executed when the service "do not disturb" is active or not, this step 216 corresponding to the update or configuration of one or more lists by the user of the terminal 120.
  • This predefined list update associated with the terminal 120 can be done by sending messages 215, including for example identifiers to be added to a list, the list being identified by a preset reference. The user of the terminal 120 can therefore customize and manage the lists.
  • the filtering method previously described has the particularity that the identifiers NUM i associated with the predefined lists or the identifier NUM d, used by default when sending the message 207 as issuer, and consequently used as identifier recipient of the message 210 sent by the terminal 1 10, correspond to surcharged numbers.
  • the user of the terminal 1 10 after receiving a type 207 message, in addition to the need for the user to have to evaluate whether or not he really wants to disturb the user of the terminal 120, and if so, to take the time to send a message 210, the user of the terminal 1 10 will have to decide whether he is ready to pay for it the cost corresponding to the surcharged number.
  • the user of the terminal 120 can thus constitute a white list of numbers corresponding to known user terminals, for which the surcharge will be low or even zero. Conversely, for numbers outside this list, or belonging to other lists, the surcharge will be higher. Note that the surcharge associated with the identifier NUM d, applied by default for an identifier not belonging to a list, is not necessarily the highest surcharge, the user of the terminal 120 can define a list of user for whom the surcharge is maximum.
  • all or part of the surcharge collected is paid back to the user of the service, or to any other organization or entity, possibly defined by the user of the service.
  • the same identifier or number can belong to only one list.
  • a list would be considered by the server 100 as a priority over the other lists.
  • this may mean that the described filtering method can roll out the process of determining an identifier to a list sequentially if there is more than one list, the priority lists being scanned first (for example, d first the green list, then the white lists, then the gray list, etc.). The sequence can be set by the service user.
  • the messages 207 and 210 comprise an indication of the identifier of the recipient of the message 205.
  • the server 100 may send to the sender of the message 205 a different message 207 per recipient having the service activated, the different messages 207 being distinguished by information on the particular recipient.
  • the user of the message 205 can then send a message 210 including a reference to the recipient number to unblock only this single message to this single recipient.
  • the server 100 can then unlock either the first message to have been recorded in the database 103, the last or a message identified by a particular reference.
  • a single message 207 is sent by the server 100 in response to a message 205 addressed to a plurality of terminals in "do not disturb" mode enabled. All that is required is a single message 210 to unblock the sending of the waiting message to the plurality of destination terminals.
  • the various steps of the method are carried out in part by the terminal 120, the service taking the form of an application executed on the terminal 120.
  • a server 100 connected with terminal 120 - for example by a IP data connection - is used to execute a few steps of the method.
  • the messages 201, 203, 212, 215, 217, 220 and 222 are internal messages to the application executed on the terminal 120.
  • the terminal 120 executing the application when the "do not disturb" mode is active, may not not react to the receipt of a message 205 so as not to disturb the user.
  • the message 205 is stored on the terminal 120.
  • the terminal 120 instructs the server 100 to send a message 207 to the terminal 1 10 indicating that the terminal 120 is in "do not disturb" mode.
  • the message 207 comprises, as before, a sender field corresponding to a possibly overtaxed identifier NUM i. If a message 210 is received by the server 100, the latter sends an instruction to the terminal 120 to unblock the corresponding message 205, that is to say that the message is found in the database 103 of the terminal and presented in such a way as to give the user of the terminal the illusion that he has just been received.
  • the message filtering method is applied to voice communications - or voice and video for video-to-video type communication - between the first and second terminals. More specifically, the message filtering method is applied to the filtering of messages corresponding to requests for setting up communications (for example voice or video) to the second terminal (in other words, voice or video calls to the second terminal 120 ).
  • FIG. 2 should be read like this:
  • the message 205 corresponds to a call setup request sent by the terminal 1 10 and to the terminal 120. It may be a voice, voice and video type of communication, etc.
  • step 206 corresponds to the interception by the server 100 of this request for establishing a communication with the terminal 120.
  • the information corresponding to this request is recorded in the database
  • a voice message can then be broadcast by the server 100 to the terminal 1 10, a message informing, for example, the user of the terminal 1 10 that the user of the terminal 120 does not wish to be disturbed.
  • the broadcast message can be adapted according to the membership of the identifier of the terminal
  • the call can be redirected - directly or after broadcasting the voice message, therefore - to the voice mail of the user of the terminal 1 20,
  • the message 207 corresponds to a message, for example an SMS message, which is sent to the terminal 1 10 by the server 100, message sent with a sender field comprising a identifier NUM i depending on the membership of the identifier of the terminal 1 to a predefined list, as seen before.
  • This message informs the user of the terminal 1 10 that the user of the terminal 120 does not wish to be disturbed, but it is possible to reach the user of the terminal 120 to the number corresponding to the identifier NUM i, this identifier possibly corresponding to a premium rate number.
  • the server 100 will then communicate the terminal 1 10 with the terminal 120. For this, the server 100 will itself issue a call to the terminal 120. the call will be billed to the user of the terminal 1 10 according to the corresponding cost to the premium rate number NUM i.
  • the terminal 120 When the user of the terminal 120 terminates the service (step 221), the information concerning the requests to establish communications with the terminal 120 will be found in the database 103 and sent to the terminal 120. In other words, the terminal 120 will receive the deactivation of the "do not disturb" service a filtered call log. Alternatively, the terminal 120 may be sent by the server 100 updates - in real time or deferred - the call log filtered.
  • the communication network comprising a server (100) connected to a database (103), the database (103) comprising at least a first predefined list of identifiers, the server (100) executing the steps following:
  • the second message (207) comprising a sender field equal to a third identifier.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Telephonic Communication Services (AREA)
EP15798157.2A 2014-10-23 2015-10-16 Verfahren zur filterung von nachrichten zur bereitstellung einer bitte-nicht-stören-funktion Withdrawn EP3210369A1 (de)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
FR1460201A FR3027759A1 (fr) 2014-10-23 2014-10-23 Methode de filtrage de messages pour fournir une fonction de type " ne pas deranger "
PCT/FR2015/052789 WO2016062947A1 (fr) 2014-10-23 2015-10-16 Methode de filtrage de messages pour fournir une fonction de type"ne pas deranger"

Publications (1)

Publication Number Publication Date
EP3210369A1 true EP3210369A1 (de) 2017-08-30

Family

ID=52130446

Family Applications (1)

Application Number Title Priority Date Filing Date
EP15798157.2A Withdrawn EP3210369A1 (de) 2014-10-23 2015-10-16 Verfahren zur filterung von nachrichten zur bereitstellung einer bitte-nicht-stören-funktion

Country Status (4)

Country Link
US (1) US20170353604A1 (de)
EP (1) EP3210369A1 (de)
FR (1) FR3027759A1 (de)
WO (1) WO2016062947A1 (de)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108351938B (zh) * 2015-10-29 2022-02-08 惠普发展公司,有限责任合伙企业 校验针对程序代码的一部分所计算的安全值的装置、系统和方法
US20190045045A1 (en) * 2017-08-01 2019-02-07 Meir Dahan System for Managing Incoming Messages in Messaging Applications
US20190044904A1 (en) * 2017-08-01 2019-02-07 Eliahu Antopolsky Method for Managing Incoming Text Messages in Mobile Devices
US11758043B2 (en) * 2021-10-21 2023-09-12 International Business Machines Corporation Identifying caller details for promotional voice communication

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5467388A (en) 1994-01-31 1995-11-14 Bell Atlantic Network Services, Inc. Method and apparatus for selectively blocking incoming telephone calls
US5872840A (en) * 1997-03-19 1999-02-16 Ericsson Inc. Enhancement do not disturb subscriber feature within a telecommunications network
WO2001061978A2 (en) 2000-02-17 2001-08-23 Bellsouth Intellectual Property Corporation Call screening that prompts caller for an access code
US20050186974A1 (en) * 2004-02-05 2005-08-25 Yigang Cai Short message service (SMS), multimedia message service (MMS), call screening and filtering
EP1613102A1 (de) * 2004-06-29 2006-01-04 BMD Wireless AG Verfahren und Telekommunikationssystem, das kontrollierte Anlieferung der kurzen Nachrichten (SMS) erlaubt
US8620362B2 (en) * 2009-12-18 2013-12-31 Alcatel Lucent Method and apparatus for selective message service blocking

Non-Patent Citations (2)

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

Also Published As

Publication number Publication date
WO2016062947A1 (fr) 2016-04-28
FR3027759A1 (fr) 2016-04-29
US20170353604A1 (en) 2017-12-07

Similar Documents

Publication Publication Date Title
US11689656B2 (en) Computing device and system for rendering contact information that is retrieved from a network service
KR101881058B1 (ko) 음성 검증 방법, 장치 및 시스템
US8577341B2 (en) Methods and apparatus for providing messaging using voicemail
US20150079967A1 (en) Systems and methods to remotely restrict the use of mobile device
US10187528B2 (en) Universal ring free
US9258172B2 (en) Calling an unready terminal
US20070190983A1 (en) Personalization content sharing system and method
WO2016062947A1 (fr) Methode de filtrage de messages pour fournir une fonction de type"ne pas deranger"
US20140378104A1 (en) Method and device for processing short messages
FR2890270A1 (fr) Unite de serveur, unite de client, procede d'exploitation d'une unite de serveur et procede d'exploitation d'une unite de client
US9894113B2 (en) Method and device for suggesting applications
EP3688974B1 (de) Verfahren zur verwaltung des scheiterns des aufbaus einer kommunikation zwischen einem ersten und einem zweiten endgerät
EP3391680B1 (de) Verfahren zur verwaltung von mindestens einer kommunikation, entsprechende vorrichtung und softwaremodulprogramm
EP3516851B1 (de) Verfahren zum austausch von nachrichten und zur verwaltung von nachrichten, endgerät und nachrichtenserver
EP2273774B1 (de) Verbindungswunschbenachrichtigungsverfahren
US8875231B1 (en) Communication privacy services
FR2955682A1 (fr) Procede de fourniture d'un code dynamique par l'intermediaire d'un telephone
EP4248637A1 (de) Optimierte auslösung von telefonkommunikationen
WO2012098165A1 (en) Blocking of application initiated calls
KR20160084413A (ko) 통신 시스템
FR3020539A1 (fr) Procede et dispositif d'etablissement d'une communication
FR2978004A1 (fr) Procede et dispositif de controle d'appels pour telephones
EP3262827A1 (de) Vorrichtung zur verwendung von automatischer kommunikationsverwaltung, verfahren und vorrichtung zur automatischen kommunikationsverwaltung und endgerät mit verwendung davon
EP2334033A1 (de) Verfahren und Vorrichtung für die Meldung von einem rufenden Endgerät

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20170522

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

AX Request for extension of the european patent

Extension state: BA ME

DAV Request for validation of the european patent (deleted)
DAX Request for extension of the european patent (deleted)
GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

INTG Intention to grant announced

Effective date: 20180228

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION IS DEEMED TO BE WITHDRAWN

18D Application deemed to be withdrawn

Effective date: 20180711