WO1998020687A1 - A method and system for extending the directory number of a terminal - Google Patents
A method and system for extending the directory number of a terminal Download PDFInfo
- Publication number
- WO1998020687A1 WO1998020687A1 PCT/CA1997/000822 CA9700822W WO9820687A1 WO 1998020687 A1 WO1998020687 A1 WO 1998020687A1 CA 9700822 W CA9700822 W CA 9700822W WO 9820687 A1 WO9820687 A1 WO 9820687A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- call
- subscriber
- terminals
- incoming call
- terminal
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q3/00—Selecting arrangements
- H04Q3/0016—Arrangements providing connection between exchanges
- H04Q3/0029—Provisions for intelligent networking
- H04Q3/005—Personal communication services, e.g. provisions for portability of subscriber numbers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
- H04Q2213/13097—Numbering, addressing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
- H04Q2213/13098—Mobile subscriber
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
- H04Q2213/13345—Intelligent networks, SCP
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
- H04Q2213/13399—Virtual channel/circuits
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/16—Communication-related supplementary services, e.g. call-transfer or call-hold
Definitions
- This invention generally relates to telephony services and more particularly to a method and system for extending a directory number of one terminal to include one or more terminals each of which has a different directory number.
- the service allows a subscriber to inform a respective service provider which terminals, each of which has a unique directory number (DN) , the subscriber wishes to be alerted simultaneously in response to an incoming call to the subscribers 1-500 number.
- a directory number is a number which has a direct association with a line appearance on a physical switch and to which a physical terminal is associated.
- Switch translations are capable of directly translating a DN into a line port or line appearance on a switch within a Wireline or wireless network.
- the service providers network will correspondingly alert those terminals corresponding to DN's provided by the subscriber and contained in a customer lookup table or profile.
- the alerted terminal which first responds by going off hook for example is connected to the calling party associated with the incoming call. Incoming calls however, to any of the individual DN's contained in the lookup table or profile rather than the special 1-500 number will however only be routed by the network to the individual terminal corresponding to that DN. Callers who wish to contact a subscriber to the 1-500 service may not be able to if they are unaware of the 1-500 number and the subscriber happens not to be in the physical location corresponding to the individual terminal being called.
- the 1-500 service is hardly transparent to the subscriber as it requires a separate and additional number. Other service providers provide their subscribers with substantially the same service by providing a new separate personal telephone number and associate a customer profile to that personal number.
- the customer profile is used by the service providers network to assist in the routing of an incoming call to the subscribers personal number.
- a caller who is aware of the 'personal number' can attempt to reach the subscriber by dialing their personal telephone number and in much the same way as for the 1-500 service an incoming call to the personal number will be routed according to the subscribers profile to one or more of the subscribers terminals, each of which would have their own DN.
- the shortfalls of this method are substantially the same as for the 1-500 service. Numbers such as the '1-500' and the 'personal number' described herein are not considered to be directory numbers as defined in this specification.
- PCS Personal Communications System
- Some of the challenges facing the service providers are how to best implement the service from a cost perspective; how to provide the service such that it is transparent to the subscriber; and how to implement the service such that it is also capable of allowing subscribers to extend a DN associated with one network (wireline or wireless) to include a DN on the other network.
- the invention seeks to provide an improved method and system for extending a directory number of one terminal to include another terminal having a different directory number.
- a method of extending a subscriber directory number to one or more terminals each of which have different network directory numbers comprising the steps of: a) in response to an incoming call from a calling party to the subscriber directory number associated with a switch, flagging at said switch that the incoming call to the subscriber directory- number requires special treatment and temporarily suspending regular call processing; b) determining that the subscriber DN is one which is to be extended to include one or more terminals, each having different network directory numbers; c) determining the DN of all terminals the subscriber DN is to be extended to; and d) initiating call setups to the subscriber directory number and to each DN determined in step 'C and alerting the terminal associated with the subscriber DN along with the terminals associated with the DN's determined in step 'C.
- a method of extending a subscriber directory number to one or more terminals each of which have different network directory numbers comprising the steps of: a) in response to an incoming call from a calling party to the subscriber directory number associated with a switch, flagging at said switch that the incoming call to the subscriber directory number requires special treatment; b) determining that the subscriber DN is one which is to be extended to include one or more terminals, each having different network directory numbers; c) determining the DN of all terminals the subscriber DN is to be extended to; and d) initiating call set ups to the subscriber directory number and to each DN determined in step 'C .
- a system for extending a subscriber directory number to one or more terminals each of which have different network directory numbers comprising ; means for flagging at a switch that an incoming call to the subscriber directory number requires special treatment and temporarily suspending regular call processing of the incoming call; means for determining that the subscriber DN is one which is to be extended to include one or more terminals, each having different network directory numbers; means for determining the DN of all terminals the subscriber DN is to be extended to; and means for initiating substantially simultaneoulsy call set ups to the subscriber directory number and to each DN determined in 'C .
- the invention allows service providers to provide a service which uses an existing subscriber directory number and effectively extends it to include one or more other directory numbers.
- the terminals associated with the other directory numbers effectively look like virtual extensions.
- the method and system provide this flexibility without requiring any additional personal numbers being assigned to the subscriber.
- the benefits are significant in that the subscriber can choose to have all incoming calls to a DN of one of their existing terminals alert or ring one or more other terminals having a different DN.
- the terminals may for example be on the same network (e.g. all on the wireline network) or they may be on different networks (e.g. one on the wireline network and one on the wireless network) .
- the method and service are substantially transparent to subscribers and calling parties as no additional numbers or new DN's of any sort are required.
- the method and system allow a wireline carrier or service provider to transparently provide an integrated service with wireless or cellular mobility.
- wireless or cellular service providers it allows for the opportunity to integrate their wireless service offering with a subscriber's existing wired residence or business service.
- Fig. 1 illustrates a communications network system in accordance with an embodiment of the invention.
- Fig. 2 illustrates a general call flow within the system of Fig. 1 for extending the directory number of a terminal .
- Fig. 3 illustrates three initial call legs set up within the network of Fig. 1 for the general call flow of Fig. 2.
- Fig. 4 illustrates a service node connecting two call legs of Fig 3.
- Fig. 5 illustrates an alternative network configuration for connecting two parties associated with the call legs shown in Fig. 4.
- Fig. 6 illustrates how the call flow of Fig. 2 would change if a wireless terminal answers the incoming call.
- Fig. 7 is representative of a califlow through the network of Fig. 1 where a wireless terminal represents the Extended Directory number.
- Fig. 8 is a more detailed version of the call flow of Fig. 2 and showing a first method of detecting a second termination attempt (TAT) trigger.
- TAT termination attempt
- Fig. 9 is a more detailed version of the call flow of Fig. 2 and showing a second method of detecting the second TAT trigger.
- Fig. 10 is a more detailed version of the call flow of Fig. 2 and showing a third method of detecting the second TAT trigger.
- Fig. 11 is a more detailed version of the call flow of Fig. 2 and showing a fourth method of detecting the second TAT trigger.
- Fig. 12 is a more detailed version of the call flow of Fig. 2 and showing a fifth method of detecting the second TAT trigger.
- the Intelligent Network (IN) architecture has been evolved through the efforts of various groups, in particular Bellcore, European Telecommunications Standards Institute (ETSI) , International Telecommunications Union (ITU-T) , and American National standards Institute (ANSI) . These groups have issued respective documentation defining the general Intelligent Network architecture along with the various entities found within the Network.
- Advanced Intelligent Network (AIN) is another industry term for the Intelligent Network (IN) .
- AIN Generally known telecommunication intelligent network entities in existence today along with other terms used in the detailed description are briefly described in general terms below:
- a SSP is generally a central office enhanced with CCS7 messaging links and AIN software which permit it to communicate with application data bases such as Service Control Points (SCP's).
- SCP's Service Control Points
- Pre-defined Call Processing Triggers in the SSP AIN software result in the SSP initiating queries to network SCP's for information regarding completing call processing of a particular call.
- STP - Signal Transfer Point
- CCS7 Common Channel Signaling No. 7
- SCP - Service Control Point
- the SCP is the intelligence center in an CCS7 AIN network which processes queries for information and returns a response to the originator of the query.
- a Service Node is a network node that provides service circuits and generally supports Call Processing type services as well as Operation, Administration & Maintenance type (OA&M) services.
- OA&M Operation, Administration & Maintenance type
- a SN can provide phone type services such as Advanced Messaging Services, Automatic Call Distribution and Customized Announcements.
- Service Nodes may also provide OA&M support for SN based services such as customized billing reports, service usage reports and Subscriber changeable service parameters .
- IP - Intelligent Peripheral
- IP - Intelligent Peripheral
- MSC Mobile Switching Center
- HLR - Home Location Register
- Information in the HLR generally includes the subscribers profile and where the subscriber's mobile terminal is currently located.
- VLR - Visit Location Register
- the entity in a cellular network generally co-located with a MTSO and is used by the cellular network to update a subscriber's HLR with the whereabouts of the subscriber's mobile terminal and is also involved in call delivery to the mobile terminal .
- Wireline terminals today have individual directory numbers and are directly linked to switching offices within the wireline network. Wireless or cellular terminals, even though allowed to roam still have individual directory numbers which are directly linked to the terminal's Home Mobile Switching Center (Home MSC), i.e. the MSC in the cellular or Wireless Network to which the public switched telephone network (PSTN) routes the cellular terminals calls. Incoming calls on the wireline network and destined for a wireless terminal are switched or routed to the wireless network. In a similar manner incoming calls on the wireless network and destined for a wireline terminal are routed to the wireline network for delivery to the wireline terminal.
- Home MSC Home Mobile Switching Center
- PSTN public switched telephone network
- SSP Service Switching Points 12
- Figure 1 interconnected over interoffice trucks 14.
- SSP Service Switching Points 12
- a wireless network 20 having multiple Mobile Switching Centers (MSC) 22, each having an integral Visiting Location Register database (VLR) are interconnected in conventional manner over interoffice trucks (not shown) .
- a centralized Home Location Register (HLR) database 26 is connected over data links 28 to each of the MSC's and is thus capable of being accessed by each MSC 22 in the wireless network 20. All wireless terminal directory numbers in this description terminate on a MSC 22 within the wireless network 20.
- the wireless network 20 is connected to the wireline network 10 over for example a Feature Group D trunk which interconnects one MSC 22 of the wireless network 20 with one SSP 12 of the wireline Network 10.
- AIN Network elements in the preferred embodiment which assist in providing the functionality to extend a DN and to integrate the two Networks 10,20 are provided by a Service Control Point (SCP) 24 and a Service Node or adjunct processor 42.
- the SCP 24 in this embodiment is centralized and accessed by individual SSP's 12 over Bellcore defined AIN 0.1 signaling links.
- the Service Node 42 in Fig. 1 is shown centralized but may be distributed (i.e. one SN per switch) .
- the SN 42 is connected to each SSP 12 over a separate Feature Group D trunk 34 (for clarity only one connection is actually shown) .
- Fig. 2 illustrates a general call flow associated with the system of Fig. 1 for a basic incoming call to a DN of a terminal on a wireline network and the simultaneous alerting (ringing) of the wireline terminal and one cellular terminal. Also in this call flow the wireline terminal goes off hook or answers before the wireless terminal and is thus connected to the calling party originating the incoming call. More detailed call flows showing specific messaging and respective parameters will follow. Network elements shown along the top of all call flows will carry the same numeric designation to identical network elements shown in Fig. 1. Within current day signaling networks Signal Transfer Points (STP) 40 (Fig. 2) may be found between SSP's and SCP's and this interface is shown as a dotted line in the call flow of Fig. 2 and subsequent call flows.
- STP Signal Transfer Points
- the subscriber of the wireline terminal subscribes to an Extended Directory Number service in accordance with an embodiment of the present invention and hence the wireline DN will become the DN to which this service is associated with or anchored to and will be referred to as the Extended Directory Number (Ext-DN) .
- the Extended Directory service will therefore key off of any incoming call to the Ext-DN. It is expected that the subscriber associated with the Ext-DN will be billed accordingly for the service by their respective Service Provider (SP) .
- SP Service Provider
- the wireline subscriber wishing to subscribe to the Extended DN service would notify their respective service provider.
- the service provider then is provided with the directory number (s) of those additional terminals which the subscriber wishes to be alerted simultaneously with the subscriber's existing wireline terminal, now identified as being the Ext-DN.
- These additional terminals may be for example, pagers, wireless or other wireline terminals or combinations thereof.
- the DN of their existing wireline terminal becomes the Ext-DN and the terms CallEd DN of an incoming call and Ext-DN become essentially interchangeable as both terms refer to the same physical terminal.
- the service provider of the Ext-DN then provisions or datafills the - Ir ⁇
- point 'A' in the call flow indicates a calling party initiating a call to the wireline DN which in actual fact has been provisioned by the SP of SSP 12 to be the Ext-DN.
- the incoming call has been routed to the respective SSP 12 at point 'B' in the call flow.
- the SSP 12 temporarily suspends call processing of the incoming call at the point in the call processing where the a 'termination attempt' to the Ext-DN is normally made (i.e. before alerting or call connection is made to the Ext-DN) .
- the SSP 12 sends ('B') a switch event message, in this particular case a 'termination attempt' message to the SCP 24 to request how to continue with the call processing of this incoming call (Cl) .
- the SCP 24 after looking up the user profile associated with the Ext-DN (the CallEd DN) determines that the DN is one which is associated with the Extended DN service and returns (C2) an AIN 'forward Call' message to the SSP 12 with routing instructions to forward the call to Service Node 42.
- the SSP 12 complies by initiating a Call SetUp which routes the incoming call to the SN 42.
- the SN 42 examines a user profile associated with the Ext-DN which happens to also be the CallEd DN, to determine which additional DN's have been identified by the subscriber of the service as being virtual extensions to the Ext-DN.
- the SN 42 initiates a Call SetUp via SSP 12 to the wireline Ext-DN and virtually at the same time, at point 'J', also initiates Call SetUp to a wireless DN.
- the SSP 12 again detects a termination attempt to the Ext-DN and for the second time in the call processing of the incoming call, sends (at 'F') a 'termination attempt' switch event message, to the SCP 24 to request how to continue with the call processing of the incoming call.
- the SCP 24 upon detecting (at Gl) that this is the second TAT, i.e. the second call attempt to the Ext-DN during the call processing of the incoming call, at G2 responds by returning to the SSP 12 an 'Authorized Termination' message to instruct the SSP 12 to deliver (at 'H') the incoming call to the wireline Ext-DN.
- the wireline terminal associated with the Ext-DN is alerted in a conventional manner to the incoming call at ' I ' .
- Various methods of how the SCP 24 determines the second TAT will be discussed in detail later in the specification.
- the SN 42 at point 'J' also initiates Call SetUp to the wireless DN found in the user profile.
- the SSP 12 at 'K' proceeds with Call SetUp to the wireless DN over the network via 'Feature Group D' trunk 30 and the Mobile Switching Center (MSC) 22 of Fig. 1.
- MSC Mobile Switching Center
- the MSC initiates delivery of the call to the wireless terminal and at point 'L' the wireless terminal is alerted to the incoming call.
- the wireline terminal goes off hook at 'N', before the wireless terminal and the call is answered on call Leg B as shown in Fig. 2 at points 'O-P'.
- the SN 42 at 'P' connects Call Leg A to Call Leg B to complete the call 'Q' and drops Call Leg C as is best illustrated in Fig. 4.
- the SN 42 is still involved in the call and when either party in the call goes on hook the SSP 12 and the SN 42 proceed to take down call legs A and B.
- Service nodes 42 which have release trunking capabilities may send a release trunk message to the SSP 12 requesting it to connect the calling party to the Ext-DN terminal at the SSP (see Fig. 5) thus allowing the SN 42 to drop out of the call once the call is completed.
- Fig. 6 illustrates how the call flow of Fig. 2 would change if the wireless terminal answered the call before the wireline terminal.
- the call flow of Fig. 6 is substantially the same as that of Fig. 2 with differences occurring at Nl,01, Pi and Ql .
- the incoming call is established at Ql and is connected to a wireless terminal.
- Fig. 7 is representative of a call flow where the Extended DN Service method anchors the Ext-DN to an existing wireless DN.
- TAT Termination Attempt Trigger
- AIN trigger terminology e.g. Termination Attempt Trigger has been used in the call flow of Fig. 7.
- the call flow follows from the description of the call flow of Fig. 2 except for the incoming call now arrives at the MSC 22 and it is the MSC 22 that interacts with the SCP 24 an SN 42 in the same way as the SSP 12 did in the embodiment of Fig. 2.
- the call flow is substantially identical to that of Fig. 2, the reader is asked to refer to the detailed description for Fig. 2.
- Termination Attempt Trigger is made in the embodiments of the invention illustrated in call flows of Figs. 2 & 6 and similarly for Fig. 7.
- the TAT is sent twice by the SSP 12 to the SCP 24; the first time when the incoming call initially arrives at the SSP 12 (point B of Figs. 2 & 6) and the second time when the Service Node 42 sets up a call to the wireline DN at point F of Fig. 2 & 6.
- the SCP 24 must distinguish therefore between the arrival of the first and second TAT since different processing by the SCP 24, is required for each. It is also expected that Service Providers will bill the DN to which this service is anchored to, i.e.
- the Ext-DN in the example embodiment of Figs. 2 & 6 the Ext-DN is the wireline DN and in Fig. 7 the Ext-DN is the wireless DN. Delivery of the correct billing information, therefore, for call legs to and from the SN 42 is desirable. Service Providers are as well expected to want to present the originating party DN to the CallEd wireline or wireless telephone .
- Figs. 8 through 12 are substantially identical to Fig. 2 and respectively illustrate in further detail, five advantageous methods of handling the SSP 12 to SCP 24 AIN messaging and FGD trunk signaling used for the proper delivery of the basic incoming call.
- identical network elements to Fig. 2 will carry the same feature number.
- Service Providers will choose among these methods based on a variety of considerations and tradeoffs. For example, the method illustrated in Figs. 8,9 & 10 require the use of a single AIN trigger but do not facilitate presentation of the calling (originating) DN to the wireless telephone.
- the methods illustrated in Figs. 11 & 12 however provide the additional value of being able to present the originating party DN to the wireless telephone but require an additional AIN trigger.
- a control block including a timer is invoked and used by the SCP 24 to store an incoming call history for a pre-determined amount of time.
- the SCP 24 includes logic to differentiate between the first and second TAT's (1A & IG) and then uses the call history to facilitate the passing on of the stored originating DN to, in this case, the wireless telephone.
- the Ext- DN is anchored to the wireline DN and hence the AIN TAT is provisioned for the wireline DN at SSP 12.
- the SSP 12 sends a TAT message 1A to the SCP 24.
- the SCP 24 When a TAT message (1A or IG) is received at the SCP 24, the SCP 24 first determines from the user profile associated with this CallEd DN, if the DN is associated with the Extended DN Service (and hence to be extended) and if so proceeds to check the TAT message to determine if the value found in the Calling field equals the value found in the CallEd field. This situation would normally not be expected as it indicates a party effectively attempting to call themselves. If the two fields are different, the SCP 24 creates a new control block IB to store the originating or Calling DN and the CallEd DN (wireline DN in this example) .
- the SCP 24 returns an AIN 'Forward Call' message to SCP 12, instructing the SSP 12 to forward the call to the SN 42.
- the SSP 12 complies by initiating call set up ID to SN 42 and creates call leg 'A' .
- billing data is preserved on call leg 'A' between SSP 12 and SN 42 by setting the 'Charge Number Parameter' within the 'Forward Call' message to contain the CallEd (Wireline/Ext-DN) DN.
- the SN 42 looks up all device DN's (two in this example) in a user profile associated with the CallEd DN (Wireline/Ext-DN) and initiates call setup to each one.
- SN 42 sets up call leg B (IF) to the Wireline DN and call leg C (IK) to the Wireless DN.
- the Wireline DN (Ext-DN) is used as the ANI field on the FGD or equivalent trunk.
- Call set up to the Wireline DN IF again initiates a TAT with a corresponding TAT message IG being sent to the SCP 24.
- the SSP 12 creates the TAT message, tansparently passing on the WireLine DN in the CallEd DN field and also passes on the WireLine DN it received in the ANI field (IF), in the Calling DN field.
- this TAT message (IG) is received at the SCP 24, the SCP 24 again determines from the user profile associated with this CallEd DN that the DN is associated with the Extended DN Service and this time also determines that within the TAT message the Calling DN field equals the value found in the CallEd DN field.
- This special situation indicates a second call attempt to the Ext-DN and causes SCP 24 to look for the associated control block.
- the SCP having determined that this is the second TAT or call attempt, instructs SSP 12 to proceed to deliver the call to the Wireline telephone by returning an
- the presentation of the true originating party's DN to the Wireline telephone is made possible by the SCP 24 modifying certain parameters within the returned Authorize Termination' AIN message II.
- the SCP 12 normally would place the calling DN it receives in the TAT message IG into the calling DN parameter field in the Authorize Termination' message II. However, in this embodiment the SCP 12 inserts into the calling DN parameter field in the Authorize Termination' message II, the originating DN it received and recorded in the first TAT message 1A.
- the true originating party DN will be presented to the Wireline telephone if the wireline subscriber subscribes to the Caller Identification (CLID) service.
- the SCP 24 then releases or deletes the control block.
- CLID Caller Identification
- Fig. 9 illustrates substantially the same call flow as for Fig. 8 with a variation on the mechanism used to detect the second TAT.
- the second TAT 2G is distinguished from the first TAT 2A by the presence of a CallEd Party Station Type (CPST) field in the second TAT message 2A having a predetermined value assigned only to the Ext-DN service.
- CPST CallEd Party Station Type
- a CPST value of 40 has been used in the Call flow of Fig. 9 as it currently has unrestricted use and can be locally determined by a Service Provider.
- the SSP 12 places an ANI Information Index (ANI_II) parameter in the FGD trunk signaling data and sets its value to 40.
- ANI_II ANI Information Index
- the SSP 12 places the value of the ANI_II parameter in the CPST field of the TAT message 2G it sends to the SCP 24.
- the originating party DN is sent over the FGD trunk in the ANI signaling field thus enabling the SSP 12 to present the correct DN to the Wireline telephone if the Wireline customer subscribes to the Calling Identification (CLID) service.
- CLID Calling Identification
- the SCP 24 In order to correctly charge the Ext-DN (Wireline) subscriber for call legs A & B, the SCP 24 intervenes.
- the SCP 24 returns the Forward Call message 2C, directing the SSP 12 to forward the call to the SN 42, the Wireline DN is provided as the Charge Number parameter for call leg A.
- the Wireline DN is placed in the Charge Number field of the returned Authorize Termination message 21.
- Correct billing information is preserved in call leg C from the SN 42 to the Wireless DN by having the SN 42 place the CallEd Wireline DN it received on call leg A, into the ANI field for call leg C (2k, 2L) .
- Fig. 10 is a more detailed version of the call flow of Fig. 2 and showing a third method of detecting the second TAT.
- Service providers prior to using the mechanism described in this embodiment need to provide a dedicated trunk between the SN 42 and the SSP 12 and as well to configure the SCP 24 to recognize the dedicated trunk ID for this configuration.
- call flow steps 3A to 3E of Fig. 10 follow the call flow steps 2A to 2E of Fig. 9.
- the SN 42 initiates call setup 3F to the Wireline DN on SSP 12 over the dedicated trunk between the SSP 12 and itself (SN 42) .
- TAT messages in general to an SCP 24 may provide trunk ID information for a particular incoming call.
- the second TAT message 3G sent by the SSP 12 includes the trunk ID associated with the incoming call to the wireline DN.
- the trunk ID for calls setup by the SN 42 will always be the same and hence the SCP 24 upon receiving the second TAT can identify it as such by the fact that the trunk ID in the TAT message matches one of the dedicated or reserved trunks between the SN 42 and the SSP 12.
- the SSP 12 delivers the correct calling party DN (caller ID (CLID) service) to the Wireline terminal is achieved by having the SSP 12 send the originating party DN in the ANI field 3D on the FGD trunk (call leg A) between the SSP 12 and the SN 42 and then to have the SN 42 include the originating party DN in the ANI field 3F on call leg B between the SN 42 and the SSP 12.
- the SCP 24 includes the Wireline DN (the Ext-DN) in the charge number field of the Forward Call message 3C sent to the SSP 12.
- the Wireline DN is then included in the charge number field of the Authorize Termination message on the call leg 31 between the SCP 24 and the SSP 12. Correct billing information is preserved on the call legs 3K & 3L from the SN 42 to the WireLess DN by including the Wireline DN (Ext-DN) in the ANI field of each call leg 3K & 3L.
- Fig. 11 is a more detailed version of the call flow of Fig. 2 and showing a fourth method of detecting the second TAT trigger.
- the call flow depicted in Fig. 11 is substantially identical to the call flow of Fig. 9 apart from the treatment of the call legs (4K, 4L, 4N, 40) from the SN 42 to the WireLess DN.
- a Public Office Dialing Plan (PODP) trigger is used to facilitate delivery of the originating party CLID information to the WireLess Terminal, while still preserving the correct billing DN (i.e. the Ext-DN in this example) .
- PODP Public Office Dialing Plan
- a PODP trigger is provisioned for the trunk group (s) used for call legs (4K, 4L, 4N, 40) from the SN 42 to the SSP 12 for the call to the WireLess Terminal.
- the originating party DN is used as the calling party DN to preserve the CLID information to the WireLess terminal.
- a special PODP DN is used as the CallEd DN on the call leg 4K.
- the PODP DN is effectively a transformation of the WireLess DN, i.e. the WireLess DN ( ⁇ actual NPA ⁇ -NXX-XXXX) is mapped to a PODP DN ( ⁇ special PODP NPA ⁇ -NXX-XXXX) .
- the SCP 24 receives an Info_Analyzed (PODP) message 4L containing a PODP DN it uses the NXX-XXX of this number to retrieve 4M the charge number and the actual area code for the WireLess DN from a subscriber profile within the SCP 24.
- PODP Info_Analyzed
- the SCP 24 then replaces the PDOP DN with the actual retrieved WireLess DN in an Analyze_Route message (4N) sent to the SSP 12.
- an Analyze_Route message (4N) sent to the SSP 12.
- the AMA Alternate Billing Number is set to the WireLine DN (Ext-DN) and included in the Analyze_Route message (4N) .
- Fig. 12 is a more detailed version of the call flow of Fig. 2 and showing a fifth method of detecting the second TAT trigger.
- the call flow depicted in Fig. 12 is substantially identical to the call flow of Fig. 9 as well, apart from the treatment of the call legs (5K, 5L, 5N, 50) from the SN 42 to the WireLess DN.
- an Off-Hook Delay (OHD) trigger is used (instead of the PODP trigger used in the call flow of Fig. 11) to facilitate delivery of the originating party CLID information to the WireLess Terminal, while still preserving the correct billing DN (i.e. the Ext-DN in this example) .
- ODD Off-Hook Delay
- a OHD trigger is provisioned for the trunk group (s) used for call legs (5K, 5L, 5N, 50) from the SN 42 to the SSP 12 for the call to the WireLess Terminal.
- the originating party DN is used as the calling party DN to preserve the CLID information to the WireLess terminal.
- a special OHD DN is used as the CallEd DN on the call leg 5K.
- the OHD DN is effectively a transformation of the WireLess DN, i.e. the WireLess DN ( ⁇ actual NPA ⁇ -NXX-XXXX) is mapped to a OHD DN ( ⁇ special OHD NPA ⁇ -NXX-XXXX) .
- OHD Info_Collected
- the SCP 24 then replaces the OHD DN with the actual retrieved WireLess DN in an Analyze_Route message (5N) sent to the SSP 12.
- an Analyze_Route message (5N) sent to the SSP 12.
- the AMA Alternate Billing Number parameter is set to the WireLine DN (Ext-DN) and included in the Analyze_Route message (5N) .
- Service providers of either a wireless or wired network may provide this service for their own respective customers or subscribers irrespective of the other network.
- a wired network SP may have a subscriber of their network identify a wired DN as the Ext-DN and provide one or more other wired DN's for the SP to alert simultaneously in response to incoming calls to Ext-DN.
- trunk connections to a wireless network are not a requirement.
- a wireless network SP may have a subscriber of their network identify a wireless DN as the Ext-DN and provide one or more other wireless DN's for the wireless SP to alert simultaneously in response to incoming calls to the (wireless) Ext-DN irrespective of any internetwork trunk connections.
- a subscriber to such an Ext-DN service may desire the added flexibility of being able to select a sub group of terminals listed in a profile to be alerted in response to an incoming call, which may or may not include the Ext-DN being alerted.
- a subscribers residence phone is the DN to which the service is anchored, i.e. the residence DN becomes the Ext-DN, and that subscriber knows that for the next few hours they will be traveling in their car, they may wish to have only their wireless DN alerted in response to an incoming call to their residence DN (the Ext-DN) .
- a subscriber profile may also be configured to contain a list of DN's and to associate a field with each DN which is modifyable by a subscriber at will to identify which DN's in the list are active (to be alerted) or not active (not to be alerted) .
- Yet a further way in which to provide this flexibility would be to provide a subscriber with a plurality of profiles and the subscriber would then identify either through an operator or an interactive dialing interface, identify which one of the profiles is to be the active profile.
- a further extension of this would be to allow a subscriber to pre-select which one of a plurality of profiles is to be the active profile at different points in the day, thus minimizing the number of times a subscriber would need to interac with a profile management system.
Abstract
Description
Claims
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP97911087A EP0872123A1 (en) | 1996-11-04 | 1997-11-04 | A method and system for extending the directory number of a terminal |
JP10520901A JPH11504794A (en) | 1996-11-04 | 1997-11-04 | Method and system for extending terminal registration number |
Applications Claiming Priority (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US3031496P | 1996-11-04 | 1996-11-04 | |
US60/030,314 | 1996-11-04 | ||
US08/912,812 US6094478A (en) | 1996-11-04 | 1997-08-19 | Method and system for extending the directory number of a terminal |
US08/912,812 | 1997-08-19 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO1998020687A1 true WO1998020687A1 (en) | 1998-05-14 |
Family
ID=26705899
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CA1997/000822 WO1998020687A1 (en) | 1996-11-04 | 1997-11-04 | A method and system for extending the directory number of a terminal |
Country Status (4)
Country | Link |
---|---|
US (1) | US6094478A (en) |
EP (1) | EP0872123A1 (en) |
CA (1) | CA2238759A1 (en) |
WO (1) | WO1998020687A1 (en) |
Families Citing this family (37)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CA2254393C (en) * | 1997-12-16 | 2002-02-26 | David R. Glass | Method and apparatus for providing calling number identification alias in a communications system |
US20010016036A1 (en) * | 1998-07-24 | 2001-08-23 | Teresa Farias Latter | Method and system for providing enhanced caller identification |
US8416932B2 (en) | 1998-07-24 | 2013-04-09 | At&T Intellectual Property I, L.P. | Convenience features in a method and system for providing enhanced caller identification |
US7292858B2 (en) | 1999-06-14 | 2007-11-06 | Ascendent Telecommunications, Inc. | Method and apparatus for communicating with one of plural devices associated with a single telephone number during a disaster and disaster recovery |
US7162020B1 (en) * | 1999-06-14 | 2007-01-09 | Ascendent Telecommunications, Inc. | Method and apparatus for selectively establishing communication with one of plural devices associated with a single telephone number |
ES2684505T3 (en) | 1999-06-14 | 2018-10-03 | Blackberry Corporation | Method and apparatus for communicating through virtual office telephone extensions |
ES2322543T3 (en) * | 1999-12-17 | 2009-06-23 | NOKIA SIEMENS NETWORKS GMBH & CO. KG | PROCEDURE TO SIGN A CALL ENTRATE. |
US6404880B1 (en) * | 1999-12-24 | 2002-06-11 | Alcatel Usa Sourcing, L.P. | Method and apparatus for delivering critical information |
US6505245B1 (en) | 2000-04-13 | 2003-01-07 | Tecsys Development, Inc. | System and method for managing computing devices within a data communications network from a remotely located console |
US7324635B2 (en) | 2000-05-04 | 2008-01-29 | Telemaze Llc | Branch calling and caller ID based call routing telephone features |
US6873686B1 (en) * | 2000-08-09 | 2005-03-29 | Bellsouth Intellectual Property Corporation | Network and method for providing a calling name telecommunications service with automatic speech recognition capability |
US6907111B1 (en) | 2000-08-09 | 2005-06-14 | Bellsouth Intellectual Property Corporation | Network and method for providing a name and number delivery telecommunications services with automatic speech recognition capability |
US6993119B1 (en) | 2000-08-09 | 2006-01-31 | Bellsouth Intellectual Property Corporation | Network and method for providing a flexible call forwarding telecommunications service with automatic speech recognition capability |
US6826529B1 (en) | 2000-08-09 | 2004-11-30 | Bellsouth Intellectual Property Corporation | Network and method for providing a call screening telecommunications service with automatic speech recognition capability |
US6778640B1 (en) * | 2000-08-09 | 2004-08-17 | Bellsouth Intellectual Property Corporation | Network and method for providing a user interface for a simultaneous ring telecommunications service with automatic speech recognition capability |
AU2001293077A1 (en) * | 2000-09-22 | 2002-07-01 | Santera Systems, Inc. | System and method for distributed multi-party call control |
US7388949B2 (en) * | 2000-12-28 | 2008-06-17 | At&T Delaware Intellectual Property, Inc. | System and method for audio caller identification service |
US7254226B1 (en) * | 2001-05-08 | 2007-08-07 | At&T Intellectual Property, Inc. | Call waiting priority alert |
US7260077B2 (en) * | 2001-06-18 | 2007-08-21 | Nortel Networks Limited | Adaptive scheduling for multi-carrier systems |
US7085358B2 (en) | 2001-06-25 | 2006-08-01 | Bellsouth Intellectual Property Corporation | Visual caller identification |
US7315614B2 (en) | 2001-08-14 | 2008-01-01 | At&T Delaware Intellectual Property, Inc. | Remote notification of communications |
US7269249B2 (en) | 2001-09-28 | 2007-09-11 | At&T Bls Intellectual Property, Inc. | Systems and methods for providing user profile information in conjunction with an enhanced caller information system |
US7315618B1 (en) | 2001-12-27 | 2008-01-01 | At&T Bls Intellectual Property, Inc. | Voice caller ID |
US7139374B1 (en) | 2002-07-23 | 2006-11-21 | Bellsouth Intellectual Property Corp. | System and method for gathering information related to a geographical location of a callee in a public switched telephone network |
US7623645B1 (en) | 2002-07-23 | 2009-11-24 | At&T Intellectual Property, I, L.P. | System and method for gathering information related to a geographical location of a caller in a public switched telephone network |
WO2004028118A2 (en) * | 2002-09-17 | 2004-04-01 | Bellsouth Intellectual Property Corporation | System and method for providing usage monitoring telephony services |
US7127051B2 (en) * | 2002-09-17 | 2006-10-24 | Bellsouth Intellectual Property Corporation | System and method for providing advanced telephony services using a virtual telephone number |
US7035390B2 (en) | 2003-03-07 | 2006-04-25 | Nortel Networks Limited | User controlled call routing for multiple telephony devices |
US7443964B2 (en) | 2003-04-18 | 2008-10-28 | At&T Intellectual Property, I,L.P. | Caller ID messaging |
US7978833B2 (en) | 2003-04-18 | 2011-07-12 | At&T Intellectual Property I, L.P. | Private caller ID messaging |
US6978003B1 (en) | 2003-05-22 | 2005-12-20 | Nortel Networks Limited | Adaptive call routing for multiple telephony terminals |
US7623849B2 (en) | 2003-11-13 | 2009-11-24 | At&T Intellectual Property, I, L.P. | Method, system, and storage medium for providing comprehensive originator identification services |
US7672444B2 (en) | 2003-12-24 | 2010-03-02 | At&T Intellectual Property, I, L.P. | Client survey systems and methods using caller identification information |
US8195136B2 (en) | 2004-07-15 | 2012-06-05 | At&T Intellectual Property I, L.P. | Methods of providing caller identification information and related registries and radiotelephone networks |
WO2009008085A1 (en) * | 2007-07-12 | 2009-01-15 | Fujitsu Limited | Interaction device, interaction system, and computer program |
US8160226B2 (en) | 2007-08-22 | 2012-04-17 | At&T Intellectual Property I, L.P. | Key word programmable caller ID |
US8243909B2 (en) | 2007-08-22 | 2012-08-14 | At&T Intellectual Property I, L.P. | Programmable caller ID |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5206901A (en) * | 1991-12-23 | 1993-04-27 | At&T Bell Laboratories | Method and apparatus for alerting multiple telephones for an incoming call |
EP0588646A2 (en) * | 1992-09-18 | 1994-03-23 | Boston Technology Inc. | Automatic telephone system |
GB2274758A (en) * | 1993-01-29 | 1994-08-03 | Mitel Corp | Telephone systems and method of operation |
US5392342A (en) * | 1993-10-27 | 1995-02-21 | At&T Corp. | Technique for use in sequentially routing personal telephone calls |
Family Cites Families (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP3064627B2 (en) * | 1992-01-28 | 2000-07-12 | 富士通株式会社 | Service control device |
US5329578A (en) * | 1992-05-26 | 1994-07-12 | Northern Telecom Limited | Personal communication service with mobility manager |
US5430791A (en) * | 1993-02-26 | 1995-07-04 | At&T Corp. | Technique for administering personal telephone numbers |
EP0711485B1 (en) * | 1993-06-11 | 1997-04-16 | Nortel Networks Corporation | Method for providing user controlled call management services |
US5487111A (en) * | 1993-07-29 | 1996-01-23 | At&T Ipm Corp. | Telecommunications system sequence calling |
US5530931A (en) * | 1994-10-20 | 1996-06-25 | Telefonaktiebolaget L M Ericsson | Method and apparatus for providing a look ahead feature for enhanced call forwarding in a telecommunications system |
US5706339A (en) * | 1994-11-30 | 1998-01-06 | At&T | Technique for use in processing personal telephone calls |
US5802160A (en) * | 1996-01-19 | 1998-09-01 | Pilgrim Telephone, Inc. | Multi-ring telephone method and system |
-
1997
- 1997-08-19 US US08/912,812 patent/US6094478A/en not_active Expired - Lifetime
- 1997-11-04 WO PCT/CA1997/000822 patent/WO1998020687A1/en not_active Application Discontinuation
- 1997-11-04 CA CA002238759A patent/CA2238759A1/en not_active Abandoned
- 1997-11-04 EP EP97911087A patent/EP0872123A1/en not_active Withdrawn
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5206901A (en) * | 1991-12-23 | 1993-04-27 | At&T Bell Laboratories | Method and apparatus for alerting multiple telephones for an incoming call |
EP0588646A2 (en) * | 1992-09-18 | 1994-03-23 | Boston Technology Inc. | Automatic telephone system |
GB2274758A (en) * | 1993-01-29 | 1994-08-03 | Mitel Corp | Telephone systems and method of operation |
US5392342A (en) * | 1993-10-27 | 1995-02-21 | At&T Corp. | Technique for use in sequentially routing personal telephone calls |
Also Published As
Publication number | Publication date |
---|---|
EP0872123A1 (en) | 1998-10-21 |
US6094478A (en) | 2000-07-25 |
CA2238759A1 (en) | 1998-05-14 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US6094478A (en) | Method and system for extending the directory number of a terminal | |
US7616747B2 (en) | Telephone network control system and method | |
AU754836B2 (en) | Communications system | |
EP1969862B1 (en) | Intelligent network services | |
US7181201B2 (en) | System and method for routing a call to a called party's landline or wireless communication unit | |
US5963864A (en) | Method and system for automatically connecting telephone calls to multiple devices having different directory numbers | |
US6560327B1 (en) | Method and system for providing telecommunications services using mediated service logic | |
US6014379A (en) | Telecommunications custom calling services | |
US5566235A (en) | Customer controlled service mediation management | |
US6584178B2 (en) | Method and system for termination blocking of message delivery service in a switch-based telecommunication system | |
US5757894A (en) | Virtual foreign exchange service | |
US7106846B2 (en) | System and method for caller control of a distinctive ring | |
US5729598A (en) | Telephone network with telecommuting features | |
US20020080751A1 (en) | System and method for routing calls in a wireless communication network | |
AU709864B2 (en) | Enhanced efficient telephone number portability | |
AU7161498A (en) | Intercepting call communications within an intelligent network | |
JPH11284736A (en) | Method and device for providing caller control | |
EP1131918A1 (en) | Triggering of intelligent network service | |
US6081590A (en) | Call treatment in portable number networks | |
US7221739B1 (en) | Callback function for messaging platform in public telephone system | |
US7649862B2 (en) | Flexible through-connection process in a mobile switch center when multiple outgoing call legs involved | |
CN100488298C (en) | Method for displaying short number of calling user for incoming number display | |
US6813348B1 (en) | Method and system of call origination using a service circuit node in an advanced intelligent network | |
US6968051B1 (en) | Programmable feature queues | |
US20080019487A1 (en) | Method and system for termination blocking of message delivery service in a swtich-based telecommunication system |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AK | Designated states |
Kind code of ref document: A1 Designated state(s): CA JP |
|
AL | Designated countries for regional patents |
Kind code of ref document: A1 Designated state(s): AT BE CH DE DK ES FI FR GB GR IE IT LU MC NL PT SE |
|
ENP | Entry into the national phase |
Ref document number: 2238759 Country of ref document: CA Kind code of ref document: A Ref document number: 2238759 Country of ref document: CA |
|
ENP | Entry into the national phase |
Ref document number: 1998 520901 Country of ref document: JP Kind code of ref document: A |
|
WWE | Wipo information: entry into national phase |
Ref document number: 1997911087 Country of ref document: EP |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
WWP | Wipo information: published in national office |
Ref document number: 1997911087 Country of ref document: EP |
|
WWW | Wipo information: withdrawn in national office |
Ref document number: 1997911087 Country of ref document: EP |