GB2528479A - Session handling in a communications network - Google Patents

Session handling in a communications network Download PDF

Info

Publication number
GB2528479A
GB2528479A GB1413048.8A GB201413048A GB2528479A GB 2528479 A GB2528479 A GB 2528479A GB 201413048 A GB201413048 A GB 201413048A GB 2528479 A GB2528479 A GB 2528479A
Authority
GB
United Kingdom
Prior art keywords
rule
session handling
rules
database
session
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
GB1413048.8A
Other versions
GB201413048D0 (en
Inventor
Gabor Morvay
Mihaly Zachar
Oszkar Kmetti
Sandor Szabo
Balint Kovacs
Viktor Kondor
Otto Ursinyi
Balazs Vendeg
Szabolcs Grof
Karako Csinsi
Robert Szokovacs
Tibor Velencei
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.)
GAMMA TELECOM Ltd
Original Assignee
GAMMA TELECOM Ltd
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 GAMMA TELECOM Ltd filed Critical GAMMA TELECOM Ltd
Priority to GB1413048.8A priority Critical patent/GB2528479A/en
Publication of GB201413048D0 publication Critical patent/GB201413048D0/en
Priority to GB1512929.9A priority patent/GB2531109B/en
Publication of GB2528479A publication Critical patent/GB2528479A/en
Withdrawn legal-status Critical Current

Links

Classifications

    • 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/1096—Supplementary features, e.g. call forwarding or call holding
    • 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
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/21—Design, administration or maintenance of databases
    • 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/10—Architectures or entities
    • H04L65/1046—Call controllers; Call servers
    • 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/1069—Session establishment or de-establishment
    • 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/1073—Registration or de-registration
    • 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
    • H04M—TELEPHONIC COMMUNICATION
    • H04M3/00—Automatic or semi-automatic exchanges
    • H04M3/42—Systems providing special services or facilities to subscribers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M3/00—Automatic or semi-automatic exchanges
    • H04M3/42—Systems providing special services or facilities to subscribers
    • H04M3/42136—Administration or customisation of services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M3/00—Automatic or semi-automatic exchanges
    • H04M3/42—Systems providing special services or facilities to subscribers
    • H04M3/42136—Administration or customisation of services
    • H04M3/42153—Administration or customisation of services by subscriber

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Databases & Information Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Data Mining & Analysis (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Telephonic Communication Services (AREA)

Abstract

A session handling database provisioning device receives an electronic file from a remote node, the electronic file comprising a plurality of rules for session handling relating to a communications subscription identifier, e.g. an E.164 number or SIP identifier. The electronic file is parsed to identify each rule of the plurality of rules. Each rule is categorized according to a rule type and each rule is then provisioned in the database according to the rule type. A check may be performed prior to provisioning the rules to determine that each rule is valid. The file may comprise rules relating to several subscription identifiers. The file may be an Extensible Markup Language (XML) file. Each session handling rule category may relate to any of session routing, voicemail, announcement playing, call queuing, time control, geographic control, call recording, busy notification, email notification, call whisper and Interactive Voice Response.

Description

Session Handling in a Communications Network
TECHNICAL FIELD
The present invention relates to the field of session handling in a communications network, and in particular to provisioning a session handling database with session handling rules.
BACKGROUND
In a communications network, a user has a subscription that is associated with an identifier. For example, an E.164 number is an identifier that is associated with a subscription. A communications service provider might allow the owner (the subscriber) of a subscription to set rules that can be applied to both incoming and outgoing sessions. In many cases, a session may be a voice call, but it will be realised that other types of session (such as video calls) require the application of rules. Rules might relate to, for example, call routing, voicemail, announcement playing, call queuing, time control, geographic control, call recording, busy notification, email notification, call whisper (in which one of the parties may be given information about the other party) and Interactive Voice Response.
Taking the example of call routing, a subscriber may have more than one device on which a call can be received. If one device is a fixed line telephone, and the other device s a mobile telephone, a rule may be set up so that an incoming call will ring first on the fixed line telephone and, if it is not answered within a predetermined time, is then transferred to the mobile telephone. This is a very simple example of call routing.
More complex rules can be set up that take into account factors such as the time of day, the date, whether the subscriber is engaged in another call, whether the subscriber's calendar shows that the subscriber is in a meeting and so on. The call routing rule is triggered when an incoming call is associated with the subscription identity. The database is queried to determine if any rules are present that are associated with the subscription and, if so, the rules are extracted and applied to the call. Of course, it will be appreciated that call handling rules may be similarly applied to outgoing calls and these are obtained from the database in the same way when an outgoing call is associated with a subscription identifier that has corresponding rules.
In order for a rule to be applied it must first be provisioned in the database and associated with the subscription identifier. Rules are typically provisioned manually by an operator. For example, a list of rules to be applied to a subscription identifier is sent to a provider that handles the subscription, and a human operative at the provider enters the rules into a database and validates the rules to ensure that they do not contain contradictions, loops or other errors. This is a slow, time consuming process and is prone to errors.
SUMMARY
It is an object to provide a more efficient way of provisioning a session handling rules database.
According to a first aspect, there is provided a method of provisioning a database for storing session handling rules in a communication network. A session handling database provisioning device receives an electronic file from a remote node. The electronic file comprises a plurality of rules for session handling relating to a communications subscription identifier. The electronic file is parsed to identify each rule of the plurality of rules. Each rule is categorized according to a rule type and each rule is then provisioned in the database according to the rule type.
An advantage of the method described above is that large numbers of complex rules can be provided in a single document and easily provisioned in a session handling rules database with little or no input requred from a human operative.
Optional examples of the identifier of a communications subscription include any of an E.164 number, a Session Initiation Protocol Identifier and a proprietary subscription identifier. For example, a call to an E.1 64 number may be forked to one of a number of devices according to the rules currently in place, but the E.164 number s associated with the subscription.
The electronic file optionally comprises a plurality of rules for session handling relating to a plurality of communications subscription identifiers, the rules for session handling to be applied to each communicatons device identified by the plurality of communications subscription identifiers. An advantage of this is that a number of subscription identifiers may be provisioned with the same session handling rules.
As an option, the session handling database provisioning device, prior to provisioning each rule in the session handling database, performs a check to determne that each rule is valid. This may be, for example. in a sandbox environment, and ensures that rules that will not work cannot be provisioned in the session handling database.
As an option, the session handling database provisioning device, prior to provisioning each rule in the session handling database, perlorms a check to determine that the plurality rules when executed are valid. This allows a check to ensure that the rules, when executed run together, do not cause loops or other undesirable effects.
In the event that a rule or the plurality of rules is not valid, an error response is optionally sent to the remote node.
Optional examples of session handling rule categories include any of call routing, voicemail, announcement playing, call queuing, time control, geographic control, call recording, busy notification, email notification, call whisper and Interactive Voice Response. It will be appreciated that other types of category may be used.
As an option the electronic file is an Extensible Markup Language electronic file.
According to a second aspect, there is provided a session handling database provisioning device for use in a communication network. The session handling database provisioning device is provided with an in/out device arranged to receive an electronic file, the electronic tile comprsing a plurality of rules for session handling relating to a communications subscription identifier. A processor is arranged to parse the electronic file to identify each rule of the plurality of rules. The processor is further arranged to categorize each rule according to a rule type and provision each rule in a session handling database according to the rule type.
The session handling database provisioning device optionally further comprises the session handling database.
As an alternative option, the session handling database provisioning device is provided with a transmitter arranged to send each rule to a remote session handling database.
As a further option, the processor is arranged to select the remote session handling database from a plurality of remote session handling databases. This allows a plurality of databases to be used, allowing more efficient network architectures to be built and also providing some redundancy in the system.
The identifier of a communications device optionally includes any of an E.164 number, a Session Initiation Protocol Identifier, and a proprietary subscription identifier, The electronic file optionally comprises a plurality of rules for session handling relating to a plurality of communications subscription identifiers, the rules for session handling to be applied to each communications subscription identified by the plurality of communications subscription identifiers. This allows many subscription identifiers to be provisioned using a single electronic file.
As an option, the processor is further arranged to, prior to provisioning each rule in the session handling database, perform a check to determine that each rule is valid. This ensures that rules that will not work or are invalid cannot be provisioned in the session handling database.
As a further option, the processor is arranged to, prior to provisioning each rule in the database, perform a check to determine that the plurality rules when executed are valid. This allows a check to ensure that the rules, when executed run together, do not cause loops or other undesirable effects.
The session handling database provisioning device is optionally provided with a response transmitter arranged to, in the event that a rule or the plurality of rules is not valid, send an error response to a remote node.
According to a third aspect, there is provided a computer program comprising computer readable code which, when run from a computer readable medium in the form of a memory in a processor on a session handling database provisioning device, causes the session handling database provisioning device to perform the method as described above in the first aspect.
According to a fourth aspect, there is provided a computer program product comprising a computer readable medium and a computer program as described above in the third aspect, wherein the computer program is stored on the computer readable medium.
BRIEF DESCRIPTION OF DRAWINGS
Figure 1 illustrates schematically an exemplary network architecture; Figure 2 is a flow diagram showing steps of an exemplary embodiment; Figure 3 illustrates schematically in a block diagram an exemplary session handling database provisioning device 1; and Figure 4 illustrates schematically in a block diagram an exemplary subscriber device.
DETAILED DESCRIPTION
Figure 1 shows an exemplary network architecture. A session handling database provisioning device 1 is provided that is capable of receiving an electronic document that contains rules relating to session handling. The rules are associated with a subscription identifier. The session handling database provisioning device 1 provisions these rules in a database 2. When a call is subsequently received, the call is associated with the subscription identifier. A function 3 that handles the call uses the subscription identifier to query the database and determine whether any rules should be applied to the call. It will be appreciated that many such functions may be present, and the rules may be applied to outgoing calls identified by the originating subscription identifier.
In a typical network that uses Session Initiation Protocol (SIP) signalling, calls are handled by a Back-to-back User Agent (B2BUA). The B2BUA acts as a User Agent server (UAS) from the point of view of incoming calls and the User Agent client (UAC) for outgoing calls. The B2BUA not only handles SIP signalling but also prepares and tears down the media path between the caller and an application component as required by any call handling rules, or between the caller and the destination. The B2BUA also handles inbound dialog establishment, provides call management, allows network interworking and can provide a hiding function for network intervals to, for example, hide network topology. For more information on SIP and the B2BUA, see RFC 3261.
When the B2BUA receives an incoming call, it signals other entities in turn that may need to have some involvement with the call. The first entity that the B2BUA contacts is a Call Control application, which processes furTher routing of the call, plays announcement, implements diversion logic, plays ring tones and error announcements and so on. The Call Control application may use call handling rules that have been provisioned in the database 2.
Other entities that may need to obtain call handling rules from the database include, for example, a call control function, a call queue function, a voicemail recording function, and a whisper function. Of course, it wil be appreciated that this list is not exhaustive.
For the sake of simplicity, Figure 1 shows a function 3 that requires a call handling rule from the database 2 to apply to a call.
In order to provision the rule, rather than an operative entering rules manually for a subscription identifier, the provisioning device receives a single electronic file, for example in an Extensible Markup Language (XML) format. The electronic file is parsed to identify each rule and to categorize the rules. The rules are then provisioned in the database 2 and associated with the subscription identifier.
The network operator provides the subscriber (or more typically, the administrator of the subscription) with instructions on the format for writing rules in the XML file. The subscriber then determines the required rules for handling calls relating to a subscription and writes the XML file according to the instructions. Where the rules are identical to those already provided for another subscription, the XML document for the other subscription may be re-used with correct the information identifying the subscription. It is also possible that a single XML file may be used to identify more than one subscription, to reduce the number of XML files that need to be sent where several subscriptions are provided with the same rules.
Of course, the electronic file may be in any suitable format, but the use of a non-proprietary format such as XML ensures that the subscriber can generate the XML file regardless of the type of device that the subscriber is using to generate the XML file.
The XML file containing a plurality of rules relating to the subscription identifier is sent to the session handling database provisioning device 1. The session handling database provisioning device 1 parses the information contained in the XML file. The session handling database has knowledge of the format for writing rules, so it can is able to identity each rule in the XML file, categorize it and provision the rules in the session handling database.
The session handling database provisioning device 1 may also perform checks on the rules to ensure that they are valid. Individual rules can be checked to determine that they will operate in the way expected. Groups of rules may also be checked to ensure that the rules will operate together without causing, for example, loops or other undesirable outcomes. There are various ways of preforming checking. For example, checking may be performed by checking the rules individually to ensure that no flows are left with an uncompleted branch, and that a terminating node does not generate a route back to the start of the rule set and hence establish a loop. Some checking may additionally or alternatively be performed in a sandbox environment.
Figure 2 is a flow diagram that shows exemplary steps occurring at a session handling database provisioning device 1. The following numbering corresponds to that of Figure 2: Si. The session handling database provisioning device 1 receives an XML (or other format) file that contains a plurality of rules associated with a subscription identifier.
The rules define a call plan (where the session relates to a call) to be used for calls to and from any devices associated with the subscription identifier.
S2. The XML file is parsed to identify each rule of the plurality of rules and convert each rule into a format usable by the database 2.
S3. The rules are categorized according to rule type in order to ensure that the rules are correctly provisioned in the session handling database.
S4. Checks are performed to determine if the rules, either individually in groups, are valid. Examples of invalid rules are those which cause loops, do not work, or are not compatible with other rules. Multiple checks may be made on different groups of rules.
If the rules are determined to be invalid, then the method proceeds to step S5, if the rules are determined to be valid, then the method proceeds to step S6.
55. As the rules received in the XML file are invalid, an error message is sent to the originator of the XML file. The error message may include some guidance as to which rules are invalid, or which groups of rules are invalid. The error message may also offer a suggestion on how to fix any invalid rules.
56. More than one session handling database may be available, for example to build redundancy or scalability into a network. In this case, the session handling database provisioning device 1 selects the database (or more than one database) 2 to be used.
57. The rules are sent to the selected database 2 in a format usable by the database and provisioned in the database 2 associated with the subscription identifier.
The rules can subsequently be applied to any call that uses the associated subscription identifier when a session handling function queries the database 2.
The session handling database provisioning device 1, when parsing the XML file, effectively identifies individual rules in the file and translates them into a form suitable for storing in the database 2. This allows a subscriber to write a set of rules in a user-friendly format without having to learn the network operator's system. It also ensures that the network operator does not need to disclose potentially confidential information about the topography of the network operator's backend.
Turning now to Figure 3, there is illustrated schematically in a block diagram an exemplary session handling database provisioning device 1. The session handling database provisioning device 1 is provided with an in/out device to receive an electronic file such as an XML file from a subscriber. Examples of an in/out device include a DVD drive, a Universal Serial Bus (USB) port, and a receiver. Typically a receiver will be used allowing a subscriber to use a remote node to upload the XML file containing the rules relating to the subscription identifier.
A processor 5 is provided that parses the XML file to identify each rule and to translate the rule into a format usable by the database 2. Parsing may be performed using a set of parsing rules 6 stored in a non-transitory computer readable medium in the form of a memory 7. The parsing rules may also include rules of checking the validity of the rules in the XML file. If so, then the processor uses these rules to check whether the rules are valid. In the event that the rules are invalid, then an error message may be sent using a transmitter (not shown for all examples, but an example is the in/out device 4) to a remote node that sent the XML file. The processor 5 may generate an error message that includes information dentifying the nature of any error and possible suggestions to fix the error.
In an embodiment, the session handling database provisioning device 1 is provided with the database 2. However, in a typical network it is much more likely that the database 2 is located remotely from the session handling database provisioning device 1. In this case, the session handling database provisioning device 1 is provided with a transmitter 8 for sending the rules associated with the subscription identifier to the database 2, in a format usable by the database 2. In many networks, more than one database 2 may be available in order to provide scalability, redundancy and more efficient communication. In this case, the processor 5 is arranged to select which database 2 is to be used.
The memory 7 may be used for storing a computer program 9 which, when executed by the processor 5, causes the session handling database provisioning device 1 to behave as described above and perform the steps shown in Figure 2. Note that the computer program 9 may be provided from an external medium 10, such as a carrier wave, a flash drive, a CD-ROM or any other suitable form.
Figure 4 illustrates schematically in a block diagram a subscriber device for providing a set of rules in an electronic file to a session handling database provisioning device 11.
Examples of a subscriber device include a personal computer, a tablet, a laptop, a smartphone and so on.
The subscriber device 11 is provided with a data entry device such as a keyboard, mouse, or other means for entering data. This allows a user to enter data relating to the subscription identifier and the rules to be applied to the subscription identifier.
A processor 13 is provided to use entered data to generate an electronic file (such as an XML file) in a suitable format for sending to the session handling database provisioning device 1.
A transmitter 14 is provided for sending the generated electronic file towards the session handling database provisioning device 1.
A non-transitory computer readable medium in the form of a memory 15 is provided for storing a computer program 16 which, when executed by the processor 13, causes the subscriber device to behave as described above. Note that the computer program 16 may be provided from an external medium 17, such as a carrier wave, a flash drive, a CD-ROM or any other suitable form.
In use, a user with the subscriber device 11 may be presented with one of several ways of establishing a call plan. For example, a Graphical User Interface (GUI) may be provided. The user can drag and position icons relating to different aspects of the call plan and how they relate to one another. The information entered by the user is translated to the electronic file (as described above, it may be written as an XML file.
Before the call plan is finalised, the XML file may be sent to the session handling database provisioning device 1 or to an associated computer device which performs checks on the XML tile to ensure that the rules are valid and do not create any loops.
Information is exchanged between the session handling database provisioning device 1 and the subscriber device 11. This is a dynamic process which allows the session handling database provisioning device to send a message to the subscriber device 11 and alert the user about any errors in the call plan as the call plan is being constructed.
An advantage of this is that the user does not need to finalise the call plan until he knows that it is valid, and there is no need for manual checks by a human operator at the backend to determine it the call plan submitted using the XML file is valid or will cause problems when executed. The session handling database provisioning device 1 may not accept an XML file detailing a call plan until it is satisfied that the the XML file is error-free and that executing the call plan will not cause problems.
Note that in the description above, the rules are associated with a subscription identifier rather than a device identifier. This is because, in practice, the rules are applied to a subscriber rather than an individual device, and a subscriber may have more than one device. However, any type of subscripton identitier may be used. Examples include an E.164 number, a SIP identifier or a proprietary identifier. It will be appreciated that a device identifier may be associated with a subscriber identifier in which case a device identifier could be used provided that it can uniquely identify the subscription.
It will be appreciated by a person of skill in the art that various modifications may be made to the embodiments described above without departing from the scope of the present disclosure as defined in the claims. For example, the examples above relate to a call plan and describe call routing, but it will be appreciated that a call is an example of a session and that the techniques equally apply to an type of session handling, for example where the session is a video cal.
The following abbreviations have been used in the above description: B2BUA Back-to-back User Agent SIP Session Initiation Protocol UAC User Agent client UAS User Agent server USB Universal Serial Bus XML Extensible Markup Language

Claims (17)

  1. CLAIMS: 1. A method of provisioning a database for storing session handling rules in a communication network, the method comprising, at a session handling database provisioning device: receiving from a remote node an electronic file, the electronic file comprising a plurality of rules for session handling relating to a communications subscription identifier; parsing the electronic file to identify each rule of the plurality of rules; categorizing each rule according to a rule type; and provisioning each rule in the database according to the rule type.
  2. 2. The method according to claim 1, wherein the identifier of a communications subscription includes any of an E.164 number, a Session Initiation Protocol Identifier and a proprietary subscription identifier.
  3. 3. The method according to claim 1 or 2, wherein the electronic file comprises a plurality of rules for session handling relating to a plurality of communications subscription identifiers, the rules for session handling to be appled to each communications device identified by the plurality of communications subscription identifiers.
  4. 4. The method according to any one of claims 1, 2, or 3, further comprising, prior to provisioning each rule in the session handling database, performing a check to determine that each rule is valid.
  5. 5. The method according to any one of claims 1 to 4, further comprsing, prior to provisioning each rule in the session handling database, performing a check to determine that the plurality rules when executed are valid.
  6. 6. The method according to any one of claims 4 or 5, further comprising, in the event that a rule or the plurality of rules is not valid, sending an error response to the remote node.
  7. 7. The method according to any one of claims 1 to 6, wherein each session handling rule category relates to any of session routing, voicemail, announcement playing, call queuing, time control, geographic control, call recording, busy notification, email notification, call whisper and Interactive Voice Response.
  8. 8. The method according to any one of claims 1 to 7, wherein the electronic file is an [xtensible Markup Language electronic file.
  9. 9. A session handling database provisioning device for use in a communication network, the session handling database provisioning device comprising: An in/out device arranged to receive an electronic file, the electronic file comprising a plurality of rules for session handling relating to a communications subscription identifier; a processor arranged to parse the electronic file to identify each rule of the plurality of rules; the processor being further arranged to categorizing each rule according to a rule type; and the processor being further arranged to provision each rule in a session handling database according to the rule type.
  10. 10. The session handling database provisioning device according to claim 9, further comprising the session handling database.
  11. 11. The session handling database provisioning device according to claim 9, further comprising a transmitter arranged to send each rule to a remote session handling database.
  12. 12. The session handling database provisioning device according to claim 11, wherein the processor is arranged to select the remote session handling database from a plurality of remote session handling databases.
  13. 13. The session handling database provisioning device according to any one of claims 9 to 12, wherein the identifier of a communications device includes any of an E.164 number, a Session Initiation Protocol Identifier, and a proprietary subscription identifier, 14. The session handling database provisioning device according to any one of claims 9 to 13, wherein the electronic file comprises a plurality of rules for session handling relating to a plurality of communications subscription identifiers, the rules for session handling to be applied to each communications subscription identified by the plurality of communications subscription dentifiers.15. The session handling database provisioning device according to any one of claims 9 to 14, wherein the processor is further arranged to, prior to provsioning each rule in the session handling database, perform a check to determine that each rule is valid.16. The session handling database provisioning device according to any one of claims 9 to 15, wherein the processor is arranged to, prior to provisioning each rule in the database, perform a check to determine that the plurality rules when executed are valid.17. The session handling database provisioning device according to any one of claims 15 or 16, further comprising a response transmitter arranged to, in the event that a rule or the plurality of rules is not valid, send an error response to a remote node.18. A computer program comprising computer readable code which, when run from a computer readable medium in the form of a memory in a processor on a session handling database provisioning device, causes the session handling database provisioning device to perform the method as claimed in any of claims 1 to9.19. A computer program product comprising a computer readable medium and a computer program as claimed in claim 18, wherein the computer program is stored on the computer readable medium.Amendments to the claims have been filed as follows CLAIMS: 1. A method of provisioning a database for storing session handling rules in a communication network, the method comprising, at a session handling database provisioning device: receiving from a remote node an electronic file, the electronic file comprising a plurality of rules for session handling relating to a communications subscription identifier; parsing the electronic file to identify each rule of the plurality of rules; categorizing each rule according to a rule type; performing a check to determine that each rule is valid; and provisioning each rule in the database according to the rule type if the rule is determined to be valid.2. The method according to claim 1, wherein the identifier of a communications LI') subscription includes any of an E.164 number, a Session Initiation Protocol Identifier and a proprietary subscription identifier.0 3. The method according to claim 1 or 2, wherein the electronic file comprises a plurality of rules for session handling relating to a plurality of communications subscription identifiers, the rules for session handling to be appled to each communications device identified by the plurality of communications subscription identifiers.4. The method according to any one of claims 1 to 3, further comprsing, prior to provisioning each rule in the session handling database, performing a check to determine that the plurality rules when executed are valid.5. The method according to any one of claims 1 to 4, further comprising, in the event that a rule or the plurality of rules is not valid, sending an error response to the remote node.6. The method according to any one of claims 1 to 5, wherein each session handling rule category relates to any of session routing, voicemail, announcement playing, call queuing, time control, geographic control, call recording, busy notification, email notification, call whisper and Interactive Voice Response.7. The method according to any one of claims 1 to 6, wherein the electronic file is an Extensible Markup Language electronic file.8. A session handling database provisioning device for use in a communication network, the session handling database provisioning device comprising: An in/out device arranged to receive an electronic file, the electronic file comprising a plurality of rules for session handling relating to a communications subscription identifier; a processor arranged to parse the electronic file to identify each rule of the plurality of rules; the processor being further arranged to categorize each rule according to a rule type; the processor being further arranged to perform a check to determine that each rule is valid; and LI') the processor being further arranged to provision each rule in a session handling database according to the rule type if the rule is determined to be valid.0 9. The session handling database provisioning device according to claim 8, further comprising the session handling database. r10. The session handling database provisioning device according to claim 8, further comprising a transmitter arranged to send each rule to a remote session handling database.11. The session handling database provisioning device according to claim 10, wherein the processor is arranged to select the remote session handling database from a plurality of remote session handling databases.12. The session handling database provisioning device according to any one of claims 8 to 11, wherein the identifier of a communications device includes any of an E.164 number, a Session Initiation Protocol Identifier, and a proprietary subscription identifier, 13. The session handling database provisioning device according to any one of claims 8 to 12, wherein the electronic file comprises a plurality of rules for session handling relating to a plurality of communications subscription identifiers, the rules for session handling to be applied to each communications subscription identified by the plurality of communications subscription dentifiers.
  14. 14. The session handling database provisioning device according to any one of claims 8 to 13, wherein the processor is arranged to, prior to provisioning each rule in the database, perform a check to determine that the plurality rules when executed are valid.
  15. 15. The session handling database provisioning device according to any one of claims 1 to 14, further comprising a response transmitter arranged to, in the event that a rule or the plurality of rules is not valid, send an error response to a remote node.
  16. 16. A computer program comprising computer readable code which, when run from a computer readable medium in the form of a memory in a processor on a session IC) handling database provisioning device, causes the session handling database provisioning device to perform the method as claimed in any of claims ito 8.0
  17. 17. A computer program product comprising a computer readable medium and a computer program as claimed in claim 16, wherein the computer program is stored on the computer readable medium.
GB1413048.8A 2014-07-23 2014-07-23 Session handling in a communications network Withdrawn GB2528479A (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
GB1413048.8A GB2528479A (en) 2014-07-23 2014-07-23 Session handling in a communications network
GB1512929.9A GB2531109B (en) 2014-07-23 2015-07-22 Session handling in a communications network

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
GB1413048.8A GB2528479A (en) 2014-07-23 2014-07-23 Session handling in a communications network

Publications (2)

Publication Number Publication Date
GB201413048D0 GB201413048D0 (en) 2014-09-03
GB2528479A true GB2528479A (en) 2016-01-27

Family

ID=51495000

Family Applications (2)

Application Number Title Priority Date Filing Date
GB1413048.8A Withdrawn GB2528479A (en) 2014-07-23 2014-07-23 Session handling in a communications network
GB1512929.9A Active GB2531109B (en) 2014-07-23 2015-07-22 Session handling in a communications network

Family Applications After (1)

Application Number Title Priority Date Filing Date
GB1512929.9A Active GB2531109B (en) 2014-07-23 2015-07-22 Session handling in a communications network

Country Status (1)

Country Link
GB (2) GB2528479A (en)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP0948181A2 (en) * 1998-04-02 1999-10-06 Lucent Technologies Inc. Method for creating and modifying similar and dissimilar databases for use in operator services configurations for telecommunication system
US20020186827A1 (en) * 2001-06-12 2002-12-12 Griffiths Michael A. Method and system for implementing call administration in a public switched telephone network
US20040034716A1 (en) * 2002-08-19 2004-02-19 Siemens Westinghouse Power Corporation Dynamic file-based routing in a broadband communications system
US20040225679A1 (en) * 2003-05-05 2004-11-11 Cisco Technology, Inc. Managing contacts in a communication network
WO2008052133A2 (en) * 2006-10-25 2008-05-02 Arcsight, Inc. Tracking changing state data to assist in computer network security
WO2010077131A1 (en) * 2008-12-30 2010-07-08 Telefonaktiebolaget Lm Ericsson (Publ) Expression conflict resolution in communication network tailoring

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CA2299639C (en) * 1999-03-05 2005-11-01 Mitel Corporation Adaptive rule-based mechanism and method for feature interaction resolution
US8234360B2 (en) * 2002-04-23 2012-07-31 Microsoft Corporation System for processing messages to support network telephony services
GB0218712D0 (en) * 2002-08-12 2002-09-18 Mitel Knowledge Corp Context aware call handling system
US7142657B2 (en) * 2002-09-27 2006-11-28 Sprint Spectrum L.P. Method and system for preventing call forward looping
US20060218268A1 (en) * 2005-03-28 2006-09-28 Andre Beck Method and apparatus for extending service mediation to intelligent voice-over-IP endpoint terminals
US9942407B2 (en) * 2013-07-24 2018-04-10 Xcast Labs, Inc. Prevention of call loops for wholesale VoIP traffic termination

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP0948181A2 (en) * 1998-04-02 1999-10-06 Lucent Technologies Inc. Method for creating and modifying similar and dissimilar databases for use in operator services configurations for telecommunication system
US20020186827A1 (en) * 2001-06-12 2002-12-12 Griffiths Michael A. Method and system for implementing call administration in a public switched telephone network
US20040034716A1 (en) * 2002-08-19 2004-02-19 Siemens Westinghouse Power Corporation Dynamic file-based routing in a broadband communications system
US20040225679A1 (en) * 2003-05-05 2004-11-11 Cisco Technology, Inc. Managing contacts in a communication network
WO2008052133A2 (en) * 2006-10-25 2008-05-02 Arcsight, Inc. Tracking changing state data to assist in computer network security
WO2010077131A1 (en) * 2008-12-30 2010-07-08 Telefonaktiebolaget Lm Ericsson (Publ) Expression conflict resolution in communication network tailoring

Also Published As

Publication number Publication date
GB201413048D0 (en) 2014-09-03
GB201512929D0 (en) 2015-09-02
GB2531109B (en) 2021-09-01
GB2531109A (en) 2016-04-13

Similar Documents

Publication Publication Date Title
AU2018241117B2 (en) Hybrid bot framework for enterprises
US9420097B2 (en) Automated traversal of interactive voice response systems
CN104202491A (en) Method for handling customer service telephone call and device thereof
US11379183B2 (en) System and method for providing a response to a user query using a visual assistant
US20140064463A1 (en) Visual selection of call path through an interactive voice response map
CA2947242C (en) Voice call diversion to alternate communication method
US10498894B1 (en) System, device, and method for routing communications in an emergency service network
US20160036686A1 (en) System and method for processing service requests using logical environments
US11838446B2 (en) Action limitations for items of a shared voicemail inbox
US9742911B2 (en) Dialing method and device
EP2727325B1 (en) Aggregating voicemail messages from multiple sources
US9560207B2 (en) Conference call alerts
US8311547B2 (en) Method and system for maintaining response center information
US11271975B2 (en) Enriched calling based call type notification
US11563782B2 (en) Enriched calling based call routing
GB2528479A (en) Session handling in a communications network
US20220150355A1 (en) Content coded zip tones for agents and conference call participants, and user-adjustable tone attribute
US9883017B2 (en) Categorized handling of electronic communications
US20210029245A1 (en) Managing Telephone Based Channel Communication In A Group-Based Communication System
US20230247139A1 (en) Mapping A Universal Contact Center Service Access Point To A Service Access Point Specific To A Determined Modality
GB2527144A (en) Session Handling in a Communications Network
US9648472B1 (en) Voicemail transmission utilizing signals associated with radio band frequencies
CN114553740A (en) Method, system, readable storage medium and device for cross-network monitoring
CN110798577A (en) Voice verification method, device, computing equipment and medium

Legal Events

Date Code Title Description
WAP Application withdrawn, taken to be withdrawn or refused ** after publication under section 16(1)