WO2000051324A1 - Procedes et systemes de determination d'acheminement de messages en fonction des elements d'un numero de repertoire - Google Patents

Procedes et systemes de determination d'acheminement de messages en fonction des elements d'un numero de repertoire Download PDF

Info

Publication number
WO2000051324A1
WO2000051324A1 PCT/US1999/029491 US9929491W WO0051324A1 WO 2000051324 A1 WO2000051324 A1 WO 2000051324A1 US 9929491 W US9929491 W US 9929491W WO 0051324 A1 WO0051324 A1 WO 0051324A1
Authority
WO
WIPO (PCT)
Prior art keywords
directory
npa
mailboxes
messaging
address
Prior art date
Application number
PCT/US1999/029491
Other languages
English (en)
Other versions
WO2000051324A9 (fr
Inventor
Navneet Patel
James Carlton Bedingfield
Original Assignee
Bellsouth Intellectual Property Corporation
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 Bellsouth Intellectual Property Corporation filed Critical Bellsouth Intellectual Property Corporation
Priority to AU21773/00A priority Critical patent/AU2177300A/en
Publication of WO2000051324A1 publication Critical patent/WO2000051324A1/fr
Publication of WO2000051324A9 publication Critical patent/WO2000051324A9/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M3/00—Automatic or semi-automatic exchanges
    • H04M3/42—Systems providing special services or facilities to subscribers
    • H04M3/50—Centralised arrangements for answering calls; Centralised arrangements for recording messages for absent or busy subscribers ; Centralised arrangements for recording messages
    • H04M3/53—Centralised arrangements for recording incoming messages, i.e. mailbox systems
    • H04M3/533—Voice mail systems
    • H04M3/53325—Interconnection arrangements between voice mail systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M2207/00—Type of exchange or network, i.e. telephonic medium, in which the telephonic communication takes place
    • H04M2207/12—Type of exchange or network, i.e. telephonic medium, in which the telephonic communication takes place intelligent networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M7/00—Arrangements for interconnection between switching centres
    • H04M7/12—Arrangements for interconnection between switching centres for working between exchanges having different types of switching equipment, e.g. power-driven and step by step or decimal and non-decimal
    • H04M7/1205—Arrangements for interconnection between switching centres for working between exchanges having different types of switching equipment, e.g. power-driven and step by step or decimal and non-decimal where the types of switching equipement comprises PSTN/ISDN equipment and switching equipment of networks other than PSTN/ISDN, e.g. Internet Protocol networks
    • H04M7/126—Interworking of session control protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M7/00—Arrangements for interconnection between switching centres
    • H04M7/12—Arrangements for interconnection between switching centres for working between exchanges having different types of switching equipment, e.g. power-driven and step by step or decimal and non-decimal
    • H04M7/1205—Arrangements for interconnection between switching centres for working between exchanges having different types of switching equipment, e.g. power-driven and step by step or decimal and non-decimal where the types of switching equipement comprises PSTN/ISDN equipment and switching equipment of networks other than PSTN/ISDN, e.g. Internet Protocol networks
    • H04M7/128—Details of addressing, directories or routing tables

Definitions

  • the present invention relates to messaging systems, and particularly, relates to methods and systems for obtaining and/or providing information for the routing of messages between or among messaging platforms in a messaging system.
  • an RWM system includes a directory to provide information with respect to the routing of a message between or among the messaging platforms of the RWM system.
  • a directory typically includes a record or an entry for each subscriber of the RWM system.
  • a subscriber's record may include information about the subscriber in the fields of the record. For example, a subscriber's record may include his or her mailbox address.
  • a mailbox address may be, may be composed of, or may include a directory number or other identifier such as the subscriber's name, address, and/or personal identification number (PIN), or other code.
  • the subscriber's record includes a field with an address for the messaging platform serving the mailbox of the subscriber. With the information from this record, the directory may provide information with respect to the routing of a message addressed to the subscriber's mailbox address. For example, assume a subscriber ("messaging subscriber") creates a message at a first messaging platform (VMS#1). Also assume the subscriber desires the message to be transmitted so the message is made available for retrieval by a recipient ("receiving subscriber") from his or her mailbox. The message created by the subscriber typically includes the mailbox address of the recipient.
  • VMS#2 the message, as created by the subscriber, typically does not include the address of the messaging platform serving the recipient (VMS#2).
  • VMS#1 To obtain the address of VMS#2, VMS#1 provides the directory with the mailbox address of the message. In response, the directory provides VMS#1 with the address of VMS#2. VMS#1 then uses the address to route the message to VMS#2 where VMS#2 makes the message available in the recipient's mailbox.
  • a single directory to provide information with respect to the routing of a message between or among the messaging platforms of the RWM system may be satisfactory while the number of subscribers in the RWM system is within the capacity of the single directory. But as the number of subscribers exceeds the capacity of the directory, problems are presented.
  • a first set of problems presented by a directory that has reached its capacity relates to the need for additional capacity for more subscriber records. Is there a way to obtain more capacity for subscriber records without negatively affecting the performance of the RWM system? Is there a way to obtain more capacity for subscriber records that has a positive effect on the performance of the RWM system?
  • One way to obtain capacity in the single directory is to eliminate some of the records or to shorten the records.
  • the records in the directory may be culled for subscribers who are no longer active, for redundant information, and so on. This culling may obtain some capacity in the single directory. But if records are simply eliminated or shortened without careful consideration to the operations of the RWM system, important information relating to subscribers may be lost, messages may not be correctly or efficiently routed, etc. The result of this inconsiderate culling may be a net gain in capacity, but unfortunately, the gain in capacity may be due to the loss of (dissatisfied) subscribers and their records from the database.
  • Another way to obtain capacity for subscriber records is to add one or more directories to the RWM system. Yet, the solution of adding one or more directories poses another set of problems. These problems include the determination of the most appropriate organizational scheme for the respective directories with respect to the records included in each directory.
  • the dynamic nature of messaging systems must be taken into account.
  • the respective assignment of subscribers to messaging platforms may change over time in efforts to load balance the overall RWM system.
  • the respective assignment of subscribers to messaging platforms may change over time based on movement or other changes instituted by the subscriber.
  • LNP local number portability
  • the subscriber may retain his or her directory number, but be served by a different messaging platform of the RWM system.
  • the record for the subscriber in the directory needs to reflect the change in messaging platform address so that messages for the subscriber are routed correctly and efficiently to the different messaging platform.
  • the present inventions relate to systems and methods for routing of a message from a subscriber to a recipient in a messaging system.
  • Exemplary embodiments of the present inventions include a plurality of directories and a network element.
  • Each directory includes a file containing subscriber records.
  • Each record contains fields correlating at least a portion of a subscriber's mailbox address to the messaging platform serving the subscriber.
  • the network element also includes a file. But the network element's file is used to determine which directory of the plurality of directories includes records with fields containing data about the messaging platform serving a group of subscribers including a particular subscriber.
  • Data about the messaging platform of a recipient of a message is obtained in a two- action process: (1) the network element is consulted to obtain the identity of the appropriate directory to consult; and (2) the directory (identified by the network element) is consulted to obtain an indicator of the messaging platform serving the recipient of the message.
  • exemplary embodiments of the present inventions obtain additional capacity for subscriber records in a messaging system in at least two ways: (1) by adding one or more directories to the messaging system pursuant to an organizational scheme that takes into account the dynamic nature of messaging systems; and (2) by efficiently using the capacity of a directory as a result of the organizational scheme.
  • the exemplary directories of the messaging system of the present inventions do not include a record for each subscriber of the messaging system. Rather, the records in each of the directories are organized pursuant to a scheme that allows for routing information to be obtained regarding the subscribers of the messaging system without having to have a record for each subscriber.
  • a network element is used to keep track of and provide information as to which directory in the messaging system is to be consulted to obtain an indicator for a message platform serving a calling line number.
  • the organizational scheme of the directories and the network element is based on the elements of a calling line number: NPA- NXX-XXX.
  • the general-to-less-general or common-to-less-common organizational scheme is based on the left-to-right hierarchy of the elements of the calling line numbers served in the messaging system.
  • the network element makes use of the general aspects of the organizational scheme while the directories make use of the less general aspects.
  • the- network element includes a file that keeps track of which directory of the plurality of directories serves which groups or supergroups (or other sizes of groups) of calling line numbers in the messaging system.
  • the network element's file keeps track based on the hierarchy of the elements of a calling line number.
  • the records of a network element's file typically reference the most or more common elements of a calling line number such as an NPA element or an NPA-NXX element.
  • the NPA element may be referred to herein as the area code or area code element.
  • the NPA-NXX element may be referred to as a full exchange description.
  • a directory's file keeps track of which messaging platform of the plurality of messaging platforms serves which groups or subgroups (or other sizes of groups) of calling line numbers in the messaging system.
  • the directory's file keeps track based on the left-to-right hierarchy of the elements of a calling line number. But the records of the directory's file reference the less or least common elements (ranges) of a calling line number such as an NPA-NXX or a NPA-NXX-Xrange.
  • the left-to-right hierarchy of a calling line number is advantageously used in the exemplary embodiments as the organizational scheme for directories and for the network element for several reasons.
  • An important reason is that typically calling line numbers having common NPA-NXXs and sometimes even having common NPA-NXX- Xranges may be served by the same messaging platform.
  • the inventors have discovered that an efficient use may be made of the capacity of a directory by having only a single record in a directory or in a network element correspond to a designated hierarchy.
  • a messaging platform in the messaging system interacts with the network element and at least one of the directories to obtain an address for a messaging platform that serves the recipient of a message to be sent through the system.
  • the messaging platform serving the subscriber who created the message queries the network element.
  • the network element checks its file for a record that contains the appropriate identifier based on at least part of the calling line number of the recipient. If found, the network element provides the messaging platform with the identity of the directory containing the address information about the messaging platform serving the group of subscribers including the recipient.
  • the messaging platform serving the messaging subscriber uses the identifier to query the directory.
  • the query is sent to obtain an indicator or other address information for the messaging platform serving the recipient of the message.
  • the directory 42 uses at least part of the calling line number of the mailbox address of the recipient to find a record including an indicator for the address of the messaging platform serving the recipient.
  • the directory provides the indicator or other information related to the messaging platform serving the messaging subscriber.
  • the messaging platform serving the messaging subscriber uses the indicator to transmit the message to the messaging platform serving the recipient.
  • the messaging platform serving the recipient saves the message as appropriate in association with the mailbox for the recipient so that the message may be retrieved by the recipient.
  • Fig. 1 is a block diagram of an exemplary messaging system such as a region-wide messaging system that may be used in connection with the present inventions.
  • Fig. 2A is a block diagram of an exemplary directory as may be used in the exemplary messaging system illustrated in Fig. 1.
  • Fig. 2B is a block diagram of an exemplary network element as may be used in the exemplary messaging system illustrated in Fig. 1.
  • Fig. 3 is a block diagram illustrating an exemplary method and/or system for obtaining and/or providing information for the routing of a message between or among messaging platforms in an exemplary messaging system such as illustrated in Fig. 1.
  • the exemplary embodiments of the present inventions provide methods and systems for obtaining and/or providing information for the routing of a message between or among messaging platforms in an exemplary messaging system.
  • the exemplary embodiments of the present inventions are used, preferably, with a region-wide messaging (RWM) system, as described in greater detail below. Nevertheless, the present inventions may be used with any type of messaging system with the appropriate functionality.
  • RWM region-wide messaging
  • the RWM system described herein allows a subscriber to the messaging system within the region of the service provider to send, receive, forward, and reply to messages, including voice mail messages, faxes, Internet data (including voice-over-Internet messages), and other electronic data. Subscribers may receive messages from other subscribers and non-subscribers. Subscriber-to-subscriber messaging, however, illustrates the advanced features of the RWM system such as: (1) each subscriber may send a message to another subscriber; (2) each subscriber may reply to a message received from another subscriber; (3) each subscriber may reply to a telephone message received from a non-subscriber by implementing a feature that dials the non-- subscriber; and (4) each subscriber may receive and reply to Internet voice messages or fax messages.
  • Fig. 1 is a block diagram of an exemplary RWM system 10 (also referred to as a telecommunications messaging network).
  • the network 10 includes a variety of interconnected network elements.
  • a group of such elements includes the plurality of end offices which are indicated as service switching points (SSPs or switches) 12a, 12b, 12c.
  • An SSP typically includes switch functionality, but also includes other functionality so as to communicate with other network elements, and in particular, with Advanced Intelligent Network (AIN) elements.
  • SSP 12a and SSP 12c are each coupled to a subscriber line, which also may be referred to as a line.
  • Each SSP 12a, 12b, 12c serves a designated group of lines, and thus, the SSP that serves a particular line may be referred to as its serving switch.
  • the line is typically connected to a piece of terminating equipment including a telephone 14.
  • terminating equipment including a telephone 14.
  • terminating equipment may include other telecommunication devices including, but not limited to, facsimile machines, computers, modems, etc.
  • End offices may further be coupled through a tandem office (not illustrated), which may be used to connect and switch circuits between and among end offices.
  • SSP 12b is connected by trunks (Signaling System 7 (SS7)) to a voice mail system (VMS) (messaging platform) 15. (These trunks use SS7 signals for call set-up and other actions and are referred to herein as SS7 trunks.)
  • SSP 12c is connected by SS7 trunks to a voice mail system (VMS) (messaging platform) 17.
  • SSPs 12a, 12b, 12c are interconnected by a plurality of trunk circuits 18.
  • Each of the SSPs is connected to another type of AIN element referred to as a local signal transfer point (STP) 20 via respective data links.
  • STP local signal transfer point
  • SS7 Signaling System 7
  • Much of the intelligence of the AIN resides in yet another type of element referred to as a service control point (SCP) 22 that is connected to STP 20 over an SS7 data link.
  • SCP 22 service control point
  • the functions performed by the SCP 22 is the maintenance of network databases and subscriber databases as represented collectively by databases (subscriber data) 24.
  • a trigger in the AIN is an event associated with a particular call that generates a packet to be sent to an SCP.
  • the SCP queries its databases or service package applications (SPAs) for processing instructions with respect to the particular call.
  • the results are sent back to the SSP in response from the SCP 22 through STP 20.
  • the return packet includes instructions to the SSP as to how to process the call.
  • the instructions may be to take some special action as a result of a customized calling service or an enhanced feature.
  • the SSP moves through the remaining call states, may encounter further triggers, and generates further packets that are used to set up and route the call.
  • Similar devices for routing calls among various local exchange carriers are provided by regional STP (not illustrated) and by regional SCP (not illustrated) which may be connected to STP 20, SCP 22, and/or to the elements described herein through the public switched telephone network (PSTN) 26.
  • PSTN public switched telephone network
  • Each VMS 15, 17 includes subscriber administration, message retrieval, send, reply, forward, and mailbox maintenance functions, among others.
  • Each VMS 15, 17 includes or is functionally connected respectively to a subscriber profile database 28, 30 (subscriber data).
  • Each subscriber profile database stores subscriber-specific profile information (subscriber information) for retrieval by VMS functions.
  • the VMS 15,17 are elements of the messaging system or service. To the protected TCP/IP network(s) 32 described below, the messaging platform looks like a valid electronic mail (e-mail) destination.
  • the VMS 15, 17 may be assigned a TCP/IP (or IP) address and/or a domain name.
  • IP IP
  • the IP or other address or domain name of the VMS 15, 17 may be stored in a region-wide messaging directory (RMD) 40, 42 discussed below, or may be stored on some domain name server (not illustrated) in the protected TCP/IP network(s) 32, or some other element.
  • the VMS 15, 17 may also provide operations access to, two standard Internet mail administrative destinations, in addition to subscriber messaging mailbox destinations. These destinations may include 404@rwm.bellsouth.com.
  • each VMS is an SS7 network element and as such is assigned a destination point code (DPC).
  • DPC destination point code
  • the VMS 15, 17 communicates with the SSP and the SCP according to the AIN 0.2 Switch - Intelligent Peripheral Interface Generic Requirements - 1129-CORE Specification, AINGR: Switch -Intelligent Peripheral Interface (IPI) (A module of AINGR, FR-15); Document Number: GR-1 129; Issue Number: 03; Updates: REV01 - Oct. 1998; Issue Date: Sept. 1997; Product Type: Industry Requirements and Standards (RS); Component of FR-15, which is incorporated herein by reference.
  • IPI Switch -Intelligent Peripheral Interface
  • This 1129 Spec describes the use of a Remote Operations parameter for indicating the invocation of a supplementary service.
  • the service is identified by an operation value.
  • the Remote Operations Parameter may be used to allow the SCP and the VMS to share information regarding a subscriber to the messaging service.
  • Internet messaging is allowed via a private Transmission Control Protocol/Internet Protocol (TCP/IP) network (protected TCP/IP network(s)) 32.
  • TCP/IP Transmission Control Protocol/Internet Protocol
  • the VMS 15, 17 through the network 32 initiates Light-weight Directory Access Protocol (LDAP) queries so as to obtain information with respect to the proper destination/recipient of a message that may have been received.
  • LDAP Light-weight Directory Access Protocol
  • the routing scheme may be based on a combination of the area code (NPA), other elements of a directory number, and/or the service provider.
  • NPA area code
  • a VMS may send an LDAP query to the SCP (and/or to a messaging directory associated with the SCP) with a destination address of 404@rwm.bellsouth.com.
  • a domain name server (not illustrated) (DNS, name server, or domain server) associated with the TCP/IP network 32 routes the LDAP query to an SCP 22 including a messaging directory 40 or a messaging directory 42 associated with the SCP 22 for processing and returns a response.
  • DNS domain name server
  • the TCP/IP network 32 using addresses from an LDAP query, transports Voice Profile for Internet Mail (VPIM) encoded messages between VMS 15, 17 and other VMS within the network 10.
  • the LDAP query is used to determine routing for a message.
  • VPIM Voice Profile for Internet Mail
  • An Internet gateway 34 provides secure access between the private TCP/IP network 32 and the Internet 36.
  • the gateway 34 limits the access of VPIM traffic to and from the Internet 36.
  • the gateway 34 performs authorized LDAP messaging directory lookups to route messages received from- the Internet 36, as is explained in greater detail below.
  • a subscriber's line number generally is the subscriber's mailbox number associated with a messaging platform rendering service to the subscriber in the RWM system.
  • a message addressed to the subscriber includes the subscriber's line number which is also the subscriber's mailbox number.
  • the subscriber's address may be based on the ten digit directory number (DN) using an International Telecommunications Union (ITV) Standard E.164 compliant address. The following syntax may be used for the subscriber's address:
  • the ⁇ + ⁇ indicates the number is an E.164 compliant address; the ⁇ 1 ⁇ indicates the North American country code; and the ⁇ DN ⁇ indicates the ten digit subscriber number (also known as directory number, calling line number, line number, telephone number, or destination number).
  • the exemplary subscriber's address includes a submailbox number, but the use of a submailbox and hence, a submailbox number is optional. It is described herein for completeness.
  • the [+] is an optional indicator to separate the DN and submailbox number. This [+] optional indicator may be used in addressing a VPIM message.
  • the [+] optional indicator typically is not included in the LDAP query /response.
  • the ⁇ 0 ⁇ is the prefix to the SubMailbox number; and the ⁇ SubMailbox ⁇ is the SubMailbox number. If there is no SubMailbox, the VMS may fill the SubMailbox number field with zeros while performing an LDAP query. In case the SubMailbox number field stored at the VMS is shorter than two digits, an LDAP and VPIM message originated from the VMS fills the SubMailbox field with zeros.
  • Fig. 1 also illustrates the exemplary use of two region-wide messaging directories 40, 42 (RMD or directory) in the messaging system 10.
  • the RMDs 40, 42 are functionally connected to the other elements of the messaging system 10 through inclusion in or a connection to SCP 22. Nonetheless, the respective RMDs 40,42 may otherwise be functionally connected to the messaging system 10, and/or may be incorporated as part of other elements in the system 10.
  • An RMD provides high-speed directory look-up for messaging subscribers. Generally, an RMD stores information so as to determine which messaging platform of the RWM system serves which subscriber. Additional information on the manner in which the RMDs of the messaging system 10 store information on messaging platforms and subscribers and how RMDs interact with a network element 51 is provided below in connection with Figs. 2A, 2B, and 3.
  • an RMD may keep track of other information relating to subscribers of the RWM system.
  • the RMD may act as both a client and a server with respect to the Light-weight Directory Access Protocol (LDAP).
  • LDAP Light-weight Directory Access Protocol
  • the RMD stores subscriber, service, and other messaging data.
  • the RMD supports the LDAP attributes field for LDAP clients to choose the fields that they desire to retrieve from the server. Clients may retrieve the subscriber profile from the RMD.
  • the RMD also acts as an LDAP client to retrieve name announcements from a messaging platform.
  • Subscriber data may be stored in the RMD in the following exemplary fashion:
  • Subscriber data is used to look up subscribers in the RMD.
  • the data is also used for the purposes of routing and billing a subscriber's calls and messages to and from the messaging platforms.
  • Service data may be stored in the RMD in the following exemplary fashion:
  • the service data contains messaging platform-specific information to perform certain checks during directory look-up and call/message routing.
  • the RMD may also store service provider data to ensure that a service provider has access to only its authorized subscribers' information.
  • Exemplary Use of Additional Directory and Explanation of Organizational Scheme As explained in the background, as messaging systems gain subscribers, often a single directory does not provide enough capacity for subscriber records.
  • the present inventions include the use of an additional or more RMDs in the messaging system 10.
  • exemplary embodiments of the present inventions obtain additional capacity for subscriber records in at least two ways: (1) by adding one or more directories to the messaging system pursuant to an organizational scheme that takes into account the dynamic nature of messaging systems; and (2) by efficiently using the capacity of a directory as a result of the organizational scheme.
  • the exemplary RMDs 40, 42 do not include a record for each subscriber of the messaging system. Rather, the records in each of the RMDs 40, 42 are organized pursuant to a scheme that allows for routing information to be obtained regarding the subscribers of the messaging system without having to have a record for each subscriber.
  • a network element is used to keep track of and provide information as to which directory in the messaging system is to be consulted to obtain an indicator for a message platform serving a line number.
  • the organizational scheme of the directories and the network element is based on the elements of a line number: NPA-NXX- XXX.
  • the organizational scheme is based on a left-to-right hierarchy of the elements of a line number. For ease of reference, this hierarchy is referred to herein as the left-to-right hierarchy.
  • the left-to-right hierarchy is explained as follows. As used herein, there are three elements of a line number: (1) the NPA or area code element; (2) the NXX, NPA-NXX, or full exchange designation element; and (3) the XXXX or NPA-NXX-XXXX element.
  • the "NPA" (Numbering Plan Area, also known as the area code) element is considered herein to be at the top of the hierarchy of the digits in a line number.
  • the NPA element is at the top because it is typically the element common to the greatest number of line numbers served by the messaging system.
  • the commonality of the NPA element is based on the fact that, generally, line numbers within a designated geographic area share a common NPA.
  • the "NXX" (full exchange designation, branch exchange, or exchange) element is in the middle of the hierarchy. After the NPA element, the NXX element is the element common to the greatest number of line numbers served by the messaging system. The commonality of the NXX element is based on the fact that, typically, all the line numbers having a common NXX are served by the same central office (end office, switch, SSP, branch office).
  • the "XXXX" element is at the bottom of the hierarchy because these last four digits generally designate a particular line and are not common to any other line.
  • a group of line numbers may have the first digit of the XXXX in common, such as "6” to provide a range referred to herein as “6XXX” or “orange”.
  • a smaller group of line numbers may have the first and second digits of the XXXX in common such as "63” to provide a range referred to herein as "63XX” or "63range”.
  • a yet smaller group of the numbers may have the first, second, and third digits of the XXXX in common such as "631" to provide a range referred to herein as "63 IX".
  • the use of four digits in the XXXX element refers to a single line.
  • the range may be indicated by: (1) “Xrange” where the first digit of XXXX is common; (2) “XXrange” where the first and second digits of XXXX are common; and (3) “XXXrange” where the first, second, and third digits of the XXXX are common.
  • the organizational scheme of the directories and the network element is based on the left-to-right hierarchy of the elements of the NPA- NXX-XXX of a line number.
  • the line number of a subscriber is used in the exemplary embodiments as the mailbox address of the subscriber.
  • the organizational scheme of the present inventions is based on the hierarchy of the elements of the NPA-NXX-XXXX as the mailbox address of a subscriber.
  • such organization avoids the necessity of having a record for each subscriber or mailbox number of the system.
  • the organizational scheme is a general-to-less-general or common-to-less-common organizational scheme based on the left-to-right hierarchy of the elements of the line numbers served in the messaging system 10.
  • the network element makes use of the general aspects of the organization scheme while the directories make use of the less general aspects of the organization.
  • the general aspects of the organizational scheme include the use of a network element (such as an intelligent peripheral, DNS, other element in the messaging system, an SCP, or other device) in the messaging system 10.
  • the network element includes a file (also referred to herein as information or information of a network element).
  • the file may be a table, chart, database, or the like.
  • the file keeps track of which directory of the plurality of directories serves which groups or supergroups (or other size groups) of line numbers in the messaging system.
  • the network element's file keeps track based on the hierarchy of the elements of a line number.
  • the network element's file typically references the most or more common elements of a line number such as an NPA element or an NPA-NXX element.
  • the network element's file keeps track of the largest or larger groups of line numbers as grouped according to the left-to-right hierarchy.
  • the network element's file does not generally reference the most specific elements of a line number (such as NPA-NXX-XXXX). Such specific reference is not made because to do so would be to reference a particular line number rather than reference a group or supergroup of calling line numbers.
  • the network element's file is used efficiently so as to allow for increased capacity with respect to records in the file.
  • the less general aspects of the organizational scheme include the use of a plurality of directories in the messaging system 10.
  • a directory includes a file
  • the file may be a table, chart, database, or the like.
  • the file keeps track of which messaging platform of the plurality of messaging platforms serves which groups or subgroups (or other size groups) of line numbers in the messaging system.
  • the directory's file keeps track based on the left-to-right hierarchy of the elements of a line number.
  • the directory's file references the less or least common elements (ranges) of a line number such as an NPA-NXX or a
  • the directory's file keeps track of the smaller groups of line numbers as grouped according to the left-to-right hierarchy.
  • the directory's file does not generally reference the most specific elements of a line number (such as NPA-NXX-XXXX) because to do so would be to reference a particular line number rather than reference a group or subgroup of line numbers.
  • the directory's file is used efficiently so as to allow for increased capacity.
  • Fig. 2A - An Exemplary Directory of the Messaging System Figs. 2A and 2B are used to further explain the organizational scheme as used by the directories and the network element and the use of the left-to-right hierarchy of a line number.
  • a directory 40 may be or may include a file 44 (also referred to as data or data of the directory in this example).
  • the file 44 includes records 46A-46N.
  • Each record 46A-46N includes at least two corresponding fields (also referred to as parts or elements): (1) a mailbox address field 48A-48N (MA field); and (2) a messaging platform field 50A-50N (MP field).
  • the MA field 48A-48N includes information or data such as the common elements corresponding to a group or sub-group (or other group) of calling line numbers.
  • the group or sub-group is defined by the elements (ranges) that the line numbers served by the messaging system- have in common.
  • the common elements may be used in the MA field to identify the group or sub-group (or other group). For example, assume a group #1 of line numbers has an NPA-NXX in common. Then, the MA field for this group # 1 may include NPA-NXX # 1. This field then references all of the line numbers served by the messaging system having the NPA-NXX #1 in common.
  • the MP field 50A-50N includes an indicator of a messaging platform serving the group or sub-group (or other group) of line numbers identified in the corresponding MA field 48A-48N.
  • the MP field indicates which messaging platform serves the line numbers belonging to the group or sub-group (or other group) having the elements found in the MA field in common.
  • this correspondence assumes that all of the line numbers having the common elements are served by the same messaging platform (at least with respect to messaging system 10).
  • FIG. 2B An Exemplary Network Element of the Messaging System
  • a network element 51 may be or may include a file 52 (also referred to as information or information of the network element in this example).
  • the file 52 includes records 54A-54N (referred to as super-records in this example).
  • Each super-record 54A-54N includes at least two corresponding fields (also referred to as parts or elements): (1) an address field 56A-56N (sometimes referred to as A field); and (2) a directory field 58A- 58N (sometimes referred to as D field).
  • the address field 56A-56N includes information or data such as the common element(s) corresponding to a group or super-group (or other group) of line numbers.
  • the group or super-group is defined by the element(s) that the line numbers that are served by the messaging system have in common.
  • the common element(s) may be used in the address field to identify the group or super- group. For example, assume a super-group # 1 of line numbers has an NPA element in common. Then, the A field for this group #1 may include NPA #1. This field then references all of the line numbers served by the messaging system having the NPA #1 in common.
  • the directory field 58A-58N includes an identifier of a directory serving the group or super-group of line numbers identified in the corresponding address field 54A-54N of the record.
  • the directory field indicates which directory includes the information on which messaging platforms serve the line numbers belonging to the group or super-group having the element(s) found in the address field in common.
  • FIG. 3 illustrates a simplified version of the messaging system 10 of Fig.
  • a first directory (RMD #1) 40 serves six groups of line numbers.
  • Each group is represented in the file (also referred to herein as the data or the data of the directory) of the directory 40 with a respective record 60A-60F.
  • Each record includes two corresponding fields: the mailbox address field (MA field); and the messaging platform field (MP field).
  • the MP field includes an indicator for the messaging platform serving the line numbers of the group.
  • the MA field is indicated as (404) 332, which means that the group of line numbers associated with this record includes those line numbers in the messaging system having (404) 332 as a common NPA-NXX.
  • the MP field includes VMS 1, which means that the voice mail system #1 15 serves the line numbers of the group (404) 332.
  • the other records 60B-60F in the file 44 follow a similar pattern to that of record 60A.
  • the records 60B-60F include MA fields for a number of different branch exchanges (NXXs) within a particular area code or NPA.
  • NXXs branch exchanges
  • (404) is the common NPA in the data 44 of the directory 40.
  • the directory 40 does not necessarily include a record for every branch exchange (NXX) for the designated hierarchy.
  • data 44 does not include a record for the designated hierarchy of (404) 377.
  • This branch exchange may be inactive, or not covered in this directory #1 for other reasons such as the system not having any subscribers with (404) 377 as their NPA-NXXs.
  • the records 60A-60F in file 44 of RMD #1 40 include MA fields for a number of different branch exchanges (NXXs) within a particular area code or NPA.
  • NXXs branch exchanges
  • each of the records 60A-60F represents a group of line numbers having an NPA-NXX in common.
  • each of the NXX elements in the NPA-NXX of the MA fields is different so as to represent respectively different exchanges.
  • the records of a file 44 in a directory need not have MA fields of the same format or designated hierarchy such as the records 60A-60F, which all have the NPA- NXX as the common format or designated hierarchy in the MA fields.
  • the MA fields of the records of a file may represent different combinations of elements and ranges of line numbers so long as the NPA (or other super-group as defined pursuant to the adopted organizational scheme) is common to all of the MA fields in the records of the file 44.
  • An example is provided that is referred to herein as the "414" example relating to a directory including records for line numbers having 414 as the NPA in common.
  • a first record may have an MA field with NPA-NXX (such as 414-481) as the common elements of the line numbers corresponding to the first record.
  • a second record may correspond to a sub- group of line numbers within an NPA-NXX- Xrange (such as the 414-428- 6range).
  • the MA field includes the 414-428-6range.
  • a third record may correspond to a sub-group of line numbers with a different NPA-NXX-Xrange (such as the 414-428-7range).
  • the MA field includes the 414-428-7range.
  • a reason for the variance in the constituent elements or ranges in the MA fields of records in a file of the 414 directory may be the relative number of subscribers having elements, or elements and ranges of their respective line numbers in common. Referring to the 414 example, the group of subscribers associated with the first record (i.e., those having 414-481 as the NPA-NXX in common) may amount to a 1,000 subscribers. But the group of subscribers having 414-428 as the NPA-NXX in common may amount to 2,000- subscribers.
  • the exemplary embodiment allows the messaging system to divide the group of 2,000 subscribers having 414-428 in common into smaller or sub-groups, if the distribution of the line numbers within the 414-428 group allows.
  • the group having 414-428 in common divides into (1) a sub-group associated with the second record and having 414-428-6range in common; and (2) a sub-group associated with the third record and having 414-428-7range in common.
  • sub-groups into sub-sub groups may be made with respect to other records in the file as appropriate based on the distribution of the line numbers of subscribers and the organizational scheme adopted by the messaging system.
  • the line numbers having a common NPA of 414 constitute the super-group of the groups and sub-groups mentioned in the 414 example.
  • the 414 directory including the records of this example includes indicators of messaging platforms serving all of the line numbers in the messaging system having the NPA of 414 in common.
  • FIG. 3 also illustrates that RMD #2 (directory #2) 42 contains data 45 including six illustrative records 62A-62F for six groups of line numbers.
  • each record 62A-62F includes two corresponding fields: the MA field; and the MP field.
  • the MP field includes an indicator for the messaging platform serving the line numbers of the group.
  • the MA field is indicated as (770) 662, which means that the group of line numbers includes those line numbers in the messaging system having (770) 662 as a common NPA-NXX.
  • the MP field is indicated as VMS 1, which means that the voice mail system #1 15 serves the line numbers of the group (770) 662.
  • the other records 62B-62F in the file follow a similar pattern to that of record 62A. Particularly, the records 62B-62F in the file follow a similar pattern to that of record 62A. Particularly, the records 62B-62F in the file follow a similar pattern to that of record 62A. Particularly, the records
  • 62B-62F include MA fields for a number of different branch exchanges
  • (NXXs) within a particular area code or NPA within a particular area code or NPA.
  • (770) is the common NPA in the data 45 of the directory 42.
  • the left-to- right hierarchy of a line number is advantageously used in the exemplary embodiments as the organizational scheme for directories for several reasons.
  • An important reason is that typically line numbers having common NPA-NXXs and sometimes even having common NPA-NXX-Xranges may be served by the same messaging platform.
  • all of the mailbox addresses (line numbers) having in common (770) 925 as a designated hierarchy are served by VMS #2 17 in Fig. 3.
  • the inventors have discovered that an efficient use may be made of the capacity of a directory by having only a single record corresponding to this designated hierarchy.
  • all of the mailbox numbers having (770) 925 as an NPA-NXX are served by the same messaging platform, and therefore, a directory that provides information as to the address of the messaging platform serving a mailbox having (770) 925 as its NPA- NXX in its mailbox address need not include a record for every active line number having (770) 925 in its mailbox address. Rather, a single record including only the common (770) 925 covers all of the active mailbox addresses having the designated hierarchy of 770 925.
  • network element 51 is used to keep track of and provide information as to which directory (as between directory 40 and directory 42) is to be consulted to obtain an indicator or other address of a messaging platform serving a line number.
  • the network element 51 includes a file 52 (referred to herein as information or information of the network element) with records (referred to herein as super- records or supergroup records).
  • Each super-record in the network element 51 corresponds to a respective supergroup of mailboxes.
  • a supergroup of mailboxes is defined by each mailbox of the supergroup having a common NPA (or other more common elements such as NPA-NXX) in its mailbox address.
  • NPA or other more common elements such as NPA-NXX
  • the records of a file in a network element need not have address fields of the same format or designated hierarchy such as the records 64A-64B, which all have the NPA as the common format or designated hierarchy in the address fields.
  • supergroups may be organized based on common inclusion of lesser elements (such as the NXX or even the NXX- Xrange) in the line numbers of subscribers in the messaging system.
  • the file 52 includes two super-records 64A- 64B.
  • Each super-record 64A-64B includes two respectively corresponding fields: an address field; and a directory field.
  • the address field includes the common element(s) shared by calling line numbers of the supergroup.
  • the directory field includes an identifier for the directory serving the line members of the supergroup of the record. Referring to record 64A, the address field is indicated as (404), which means that the supergroup of line numbers includes those line numbers in the messaging system having (404) as the common NPA.
  • the D field is identified as RMD # 1 , which means that RMD # 1 40 is the directory that is to be consulted to obtain an indicator or other address of a messaging platform serving a line number.
  • the address field is indicated as (770), which means that the supergroup of line numbers includes those line numbers in the messaging system having (770) as the common NPA.
  • the directory field is identified as RMD #2, which means that RMD #2 42 is the directory that is to be consulted to obtain an indicator or other address of a messaging platform serving a line number.
  • the recipient's line number and mailbox address is (770) 925-7666.-
  • the messaging subscriber creates a message for the recipient and provides the recipient's mailbox address ((770) 925-7666) through interaction with the VMS #1 15 serving the messaging subscriber 14 (see arrow 1).
  • the VMS #1 15 queries the network element 51 (see arrow 2). The query includes at least the NPA of the line number and mailbox address of the recipient.
  • the VMS #1 15 is seeking an indicator or other address for the messaging platform serving the recipient 38. But the first action in obtaining such an indicator is to find which directory in the messaging system has information on the indicator.
  • the network element 51 looks for the appropriate identifier, and if found, provides the VMS #1 with the information related to the directory.
  • the network element 51 uses the NPA of the mailbox address of (770) 925-7666 to find a directory (or an identifier for the directory) including the indicator for the messaging platform for delivery of the message.
  • the network element 51 uses the (770) of the mailbox address to find record 64B, which includes (770) in the address field.
  • This record 64A includes a directory field corresponding to the address field.
  • the directory field includes the identifier for the directory (RMD #2 42) serving the particular group of mailboxes including the recipient's mailbox.
  • the network element 51 then responds to the VMS #1 with the identifier or other information for the directory (RMD #2 42) (see arrow 3).
  • the VMS #1 15 is provided with the identifier or other information for the directory including the indicator for the messaging platform for delivery of the message.
  • the VMS #1 uses the identifier or other information to query the directory (RMD #2 42) for the indicator or other information of the messaging platform (see arrow 4).
  • the query includes at least the NPA-NXX of the line number and mailbox address of the recipient.
  • the directory 42 uses the NPA-NXX of the mailbox address of (770) 925-7666 to find a record including the indicator for the messaging platform for the delivery of the message.
  • the directory 42 uses the (770) 925 of the mailbox address to find record 62C, which includes (770) 925 in the MA field of the record.
  • This record 62C includes an MP field corresponding to the MA field.
  • the MP field includes the indicator for the messaging platform (VMS #2 17) serving the particular group of mailboxes including the recipient's mailbox.
  • the directory 42 then responds to the VMS #1 15 with the indicator or other information related to the messaging platform (VMS #2 17) (see arrow 5).
  • the VMS #1 15 is provided with the indicator or other information for the messaging platform for delivery of the message.
  • the VMS #1 uses the indicator or other information to transmit the message to VMS #2 17 (see arrow 6).
  • the VMS #2 17 stores the message as appropriate in association with the mailbox for (770) 925-7666 from where the message may be retrieved by the recipient 38 (see arrow 7).

Abstract

L'invention concerne des procédés et des systèmes d'un système de messagerie pour l'identification d'une plate-forme de messagerie à utiliser dans la remise d'une message adressé à une adresse de boîte aux lettre desservie par la plate-forme de messagerie. Le système de messagerie comprend un élément de réseau et plusieurs répertoires. A l'aide au moins du NPA de l'adresse de boîte aux lettres, l'élément de réseau détermine le répertoire qui contient l'indicateur de la plate-forme de messagerie pour la remise du message. A l'aide d'au moins le NPA-NXX de l'adresse de boîte aux lettres, le répertoire obtient et produit l'indicateur de la plate-forme de messagerie pour la remise du message.
PCT/US1999/029491 1999-02-26 1999-12-13 Procedes et systemes de determination d'acheminement de messages en fonction des elements d'un numero de repertoire WO2000051324A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU21773/00A AU2177300A (en) 1999-02-26 1999-12-13 Methods and systems for determining message routing based on elements of a directory number

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US12189299P 1999-02-26 1999-02-26
US60/121,892 1999-02-26

Publications (2)

Publication Number Publication Date
WO2000051324A1 true WO2000051324A1 (fr) 2000-08-31
WO2000051324A9 WO2000051324A9 (fr) 2002-04-25

Family

ID=22399399

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US1999/029491 WO2000051324A1 (fr) 1999-02-26 1999-12-13 Procedes et systemes de determination d'acheminement de messages en fonction des elements d'un numero de repertoire

Country Status (2)

Country Link
AU (1) AU2177300A (fr)
WO (1) WO2000051324A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE10044555A1 (de) * 2000-09-06 2002-03-14 Siemens Ag Verfahren und Anordnung zum Übertragen einer schriftlichen Kurzinformation an ein Kommunikationsendgerät

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4933967A (en) * 1989-06-01 1990-06-12 At&T Company Automatically-effected move of a subscriber between electronic message service systems in a network
EP0412799A2 (fr) * 1989-08-10 1991-02-13 Boston Technology Système de communication téléphonique
EP0507125A2 (fr) * 1991-04-02 1992-10-07 Siemens Rolm Communications Inc. (a Delaware corp.) Méthode et appareil pour adresser des usagers dans un réseau
EP0662762A2 (fr) * 1994-01-06 1995-07-12 AT&T Corp. Réseau d'audio-messagerie
US5680442A (en) * 1994-12-05 1997-10-21 Bell Atlantic Network Services, Inc. Voice mail communication with call blocking

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4933967A (en) * 1989-06-01 1990-06-12 At&T Company Automatically-effected move of a subscriber between electronic message service systems in a network
EP0412799A2 (fr) * 1989-08-10 1991-02-13 Boston Technology Système de communication téléphonique
EP0507125A2 (fr) * 1991-04-02 1992-10-07 Siemens Rolm Communications Inc. (a Delaware corp.) Méthode et appareil pour adresser des usagers dans un réseau
EP0662762A2 (fr) * 1994-01-06 1995-07-12 AT&T Corp. Réseau d'audio-messagerie
US5680442A (en) * 1994-12-05 1997-10-21 Bell Atlantic Network Services, Inc. Voice mail communication with call blocking

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE10044555A1 (de) * 2000-09-06 2002-03-14 Siemens Ag Verfahren und Anordnung zum Übertragen einer schriftlichen Kurzinformation an ein Kommunikationsendgerät

Also Published As

Publication number Publication date
AU2177300A (en) 2000-09-14

Similar Documents

Publication Publication Date Title
US6243374B1 (en) Telecommunications custom calling services using voice mail
US6014379A (en) Telecommunications custom calling services
US6608888B2 (en) Methods and systems to provide a message in a messaging system without revealing an identity of the sending party
US6681257B1 (en) Methods and system for determining message routing based on elements of a directory number
US6021126A (en) Telecommunication number portability
JP4308911B2 (ja) 加入者番号を再配置できる通信ネットワーク
US5903636A (en) System and method for providing caller identification in conjunction with calling card calls
US7664244B2 (en) Method and system for providing calling number restoral
US7983409B2 (en) Geographical call routing for a non-emergency calling service
US7409211B2 (en) Methods and systems for implementation of the calling name delivery service feature through use of a location register in a network element in a wireless network
US8144843B2 (en) System and method for accessing a messaging service using a short dialing sequence
CA2240696C (fr) Methode utilisant un reseau intelligent perfectionne accessible par l'intermediaire d'un reseau telephonique commute public pour livrer visuellement a un demandeur des renseigements selectionnes relies a un numero de telephone
US6628761B1 (en) Methods and systems allowing access to a messaging platform through a visited messaging platform
US6714639B1 (en) System and method for providing calling name services with local number portability
US7580513B2 (en) Telephone call log email
US8175250B2 (en) Dialed number service routing in a telephone network by reference to a database
US7945038B2 (en) Methods and systems for releasing a voice mail system from a communication and further processing the communication
US6707901B1 (en) Subscriber profile extension (SPEX)
US6678364B2 (en) System and method for cost estimation of a long distance call
US6810113B1 (en) Methods and systems to make spoken name data available
US6427010B1 (en) Systems and methods for providing voice mail services to ported numbers by supplying routing information via signaling network
WO2000051324A1 (fr) Procedes et systemes de determination d'acheminement de messages en fonction des elements d'un numero de repertoire
US6654453B1 (en) Method and system for minimizing database structure overhead in handling large volume advanced intelligent network services
EP1155558A1 (fr) Procedes et systemes pour liberer une communication d'un systeme de messagerie vocale et continuer a traiter cette communication
Farris et al. Systems and methods for providing voice mail services to ported numbers by supplying routing information via signaling network

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AE AL AM AT AU AZ BA BB BG BR BY CA CH CN CR CU CZ DE DK DM EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ UA UG US UZ VN YU ZA ZW

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): GH GM KE LS MW SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

122 Ep: pct application non-entry in european phase