(19) United States
`(12) Patent Application Publication (10) Pub. No.: US 2013/0295892 A1
`(43) Pub. Date:
`Nov. 7, 2013
`Backhaus et al.
`
`US 2013 O295892A1
`
`(54) SYSTEMAND METHOD FOR PROVISION OF
`A SECOND LINE SERVICE TO A
`TELECOMMUNICATIONS DEVICE USING
`MIXED PROTOCOLS
`
`(71)
`
`(72)
`
`(21)
`(22)
`
`(63)
`
`Applicants: George Backhaus, Suwanee, GA (US);
`Jignesh Gandhi, Duluth, GA (US);
`Julio Gonzalez, Tucker, GA (US); John
`Green, Roswell, GA (US); Philip
`Lowman, Ellijay, GA (US); Paul
`Rubenstein, Johns Creek, GA (US);
`Mike Speanburg, Lawrenceville, GA
`(US)
`Inventors: George Backhaus, Suwanee, GA (US);
`Jignesh Gandhi, Duluth, GA (US);
`Julio Gonzalez, Tucker, GA (US); John
`Green, Roswell, GA (US); Philip
`Lowman, Ellijay, GA (US); Paul
`Rubenstein, Johns Creek, GA (US);
`Mike Speanburg, Lawrenceville, GA
`(US)
`Appl. No.: 13/920,056
`Filed:
`Jun. 17, 2013
`Related U.S. Application Data
`Continuation-in-part of application No. 13/466,074,
`filed on May 7, 2012.
`
`(60) Provisional application No. 61/660,772, filed on Jun.
`17, 2012.
`
`Publication Classification
`
`(51) Int. Cl.
`H0474/6
`(52) U.S. Cl.
`CPC ....................................... H04W 4/16 (2013.01)
`USPC ....................................................... 455/414.1
`
`(2006.01)
`
`(57)
`
`ABSTRACT
`
`A method for routing calls between a third party telecommu
`nications device (“TD) and a subscriber TD associated with
`a primary service and a second line service (“SLS) involves
`associating the SLS number of the subscriber, the primary
`number of the subscriber and the primary number of a third
`party via a common relationship number. Calls directed from
`a third party to the SLS number of a subscriber are routed to
`an SLS platform and redirected to the subscriber TD. Calls
`directed from the subscriber TD to the third party use the
`relationship number to route the call to the SLS platform. The
`combination of the primary service number and the relation
`ship number identifies the third party number for call comple
`tion. Calls can be directed to and from an SLS number of a
`subscriber TD using a combination of protocols such as ISUP,
`CAP and SIP
`
`
`
`315
`Subscriber Relationship ID Table
`Subscriber Contact Relationship Number 3" Party Number
`1
`+ 1678.222.OOO1
`+1305,229.9999
`
`+1212.777.8888
`+1408,333.2222
`
`+ 1678.222.OOO2
`+ 1678.222.0003
`+ 1.678.222.0004
`+ 1678.222.0005
`
`+ 1678.222.9999
`
`LOCal SLS Database 106
`
`Page 1 of 29
`
`GOOGLE EXHIBIT 1005
`
`

`

`Patent Application Publication
`
`Nov. 7, 2013 Sheet 1 of 14
`
`US 2013/0295892 A1
`
`
`
`Page 2 of 29
`
`

`

`Patent Application Publication
`
`Nov. 7, 2013 Sheet 2 of 14
`
`US 2013/0295892 A1
`
`s-201
`
`202-1
`
`
`
`Subscriber TD
`
`3 Party TD
`
`Local SLS
`DBase
`
`SLS MOCdule E.
`
`FIG. 2
`
`Page 3 of 29
`
`

`

`Patent Application Publication
`
`Nov. 7, 2013 Sheet 3 of 14
`
`US 2013/0295892 A1
`
`
`
`305
`SeCond Line Service Master ID Table
`2" Line Number
`+1770.555.0001
`
`Primary Number
`+1408.544.1212
`
`SubSCriber
`
`1
`
`+1770.555.OOO2
`+1770.555.0003
`+1770.555.0004
`+1770.555.0005
`
`+1770.555.9999
`
`31 O
`Subscriber Relationship ID Table
`(Subscriber 1)
`SubSCriber Contact Relationship Number 3" Party Number
`+ 1678.222.0001
`+ 1.305.229.9999
`1
`
`+1678.222.0002
`+ 1678.222.0003
`
`+1-212.777,8888
`+1408,333.2222
`
`+1.678.222.0004
`+1.678.222.0005
`
`+ 1678.222.9999
`
`Central SLS Database 116
`
`FIG. 3A
`
`Page 4 of 29
`
`

`

`Patent Application Publication
`
`Nov. 7, 2013 Sheet 4 of 14
`
`US 2013/0295892 A1
`
`
`
`315
`Subscriber Relationship ID Table
`Subscriber Contact Relationship Number 3" Party Number
`1
`+ 1.678.222.0001
`+1.305.229.9999
`
`+1-212.7778888
`+1.408,333.2222
`
`+ 1678.222.OOO2
`+ 1678.222.OOO3
`+ 1.678.222.0004
`+ 1678.222.0005
`
`+ 1678.222.9999
`
`LOCal SLS Database 106
`
`FIG. 3B
`
`Page 5 of 29
`
`

`

`Patent Application Publication
`
`Nov. 7, 2013 Sheet 5 of 14
`
`US 2013/0295892 A1
`
`f Start Method for \
`|
`Routing Calls
`\
`f
`between a 3rd
`\
`(
`Party and a
`)
`A
`Subscriber of a
`\
`Second Line
`Service
`
`/
`
`Receive a
`- Communication at an
`SLS Platform
`
`a.
`
`a
`
`s
`
`"
`404-
`Ys
`y-
`rd
`1.
`- Call from a 3">
`party? -
`NO is
`r
`
`YES
`
`Query Central SLS
`406
`- Dbase for 3' Party
`CLID
`
`3"Party CLID
`s recognized? -
`-
`N
`-
`s
`Ys
`-
`
`
`
`410
`N
`
`ASSOCiate a dialable
`Relationship Number
`with the calling 3"
`Party CLID and the
`Subscriber's Primary
`Number and SLS No.
`
`GoTo
`Block
`432 Of
`Fig. 4C
`
`
`
`
`
`
`
`FIG. 4A
`
`412
`
`Create record in
`Central SLSDbase W/
`3 Party CLID and
`Subscriber Primary
`Number and SLS NO.
`mapped to
`Relationship Number
`
`|
`
`Redirect Call to
`Subscriber's Primary
`Number and populate
`Calling party field with
`Combination of
`Relationship Number
`and 3' Party CLID
`
`
`
`
`
`Receive Call at
`SubSCriber's TD and
`store Relationship
`Number and 3' Party
`CLID Combination in
`LOCal SLSDbase
`
`Display 3" Party CLID
`On TD and alert
`Subscriber to incoming -
`Call
`
`418
`
`Connect 3 Party call
`to SubSCriber TD
`
`Page 6 of 29
`
`

`

`Patent Application Publication
`
`Nov. 7, 2013 Sheet 6 of 14
`
`US 2013/0295892 A1
`
`From
`Block
`408 of
`Fig. 4A /
`
`^
`N
`/
`N
`N /
`
`422
`W
`
`Query Central SLS
`Dbase for Relationship
`Number mapped to 3"
`Party CLID and
`SubSCriber SLS
`Number
`
`424
`&
`
`Redirect Call to
`Subscriber's Primary
`Number and populate
`calling party field with
`COmbination Of
`Relationship Number
`and 3" Party CLID
`
`Receive Call at
`SubSCriber's TD and
`Display 3' Party CLID
`On TD
`
`428
`/
`
`430
`?
`
`Alert SubSCriber to
`Incoming Call
`
`Connect 3' Party call
`to SubSCriber TD
`
`(
`
`\
`
`End
`
`Y
`
`FIG. 4B
`
`Page 7 of 29
`
`

`

`Patent Application Publication
`
`Nov. 7, 2013 Sheet 7 of 14
`
`US 2013/0295892 A1
`
`
`
`Yx s
`
`s
`
`s
`
`s s
`
`NO
`
`-
`
`- - Call to a 's
`Relationship >
`Number?
`
`/
`
`Ys
`
`/
`
`2 ^
`
`-
`
`YES
`
`434
`'
`
`Query Central SLS
`Dbase for SubSCriber
`Primary Service
`Number and
`Relationship Number
`Combination
`
`436
`K
`
`Determine 3' Party
`Number associated
`with queried
`Subscriber Primary
`Service Number and
`Relationship Number
`
`
`
`Redirect call to 3"
`Party Number and
`populate Calling party
`field with Subscriber
`Second Line Number
`
`Connect Subscriber
`call to 3' Party TD
`
`/
`
`
`
`Page 8 of 29
`
`

`

`Patent Application Publication
`
`Nov. 7, 2013 Sheet 8 of 14
`
`US 2013/0295892 A1
`
`From
`Block
`432 of
`Fig. 4C
`
`444
`442
`w
`-Y
`— -- N A
`- Data is
`-
`-
`C COmmunication D
`NO is from an SLS -
`Cl ient? -
`
`T
`erminate
`Call
`
`/
`
`(
`
`End
`
`N
`
`)
`
`YES
`
`Query SLS Central
`Dbase for SubSCriber
`SeCOnd Line Number
`and determine next
`available Relationship
`Number
`
`Return next available
`Relationship Number
`- to SubSCriber TD
`
`Create record in
`Central SLS database
`wf 3" Party CLID and
`- Relationship Number
`aSSOCiated with
`SubSCriber's SLS and
`Primary Nos.
`
`GOTO
`Start
`
`FIG. 4D
`
`Page 9 of 29
`
`

`

`Patent Application Publication
`
`Nov. 7, 2013 Sheet 9 of 14
`
`US 2013/0295892 A1
`
`| | Start Method for using \
`| a Second Line Service
`to place a call to a 3rd
`)
`Party with a
`(
`|
`SubSCriber TD
`|
`aSSOciated with a
`\
`\ Primary Number and a |
`SeCOnd Line Number |
`
`502
`N
`
`Use SLS module to
`dial 3' party number
`
`4 50
`Query Local SLS
`- Dbase for 3"Party
`Number
`
`506
`N - N.
`- 3rd Party No.
`>
`{
`N recognized? -
`recognized
`N-
`YES
`
`NO
`
`Place Call to
`Relationship Number
`508
`N- and populate called
`party field with 3"
`Party Number for
`display to Subscriber
`
`OO
`
`510
`|
`Contact SLS Platform -
`
`
`
`ReCeive a next
`available Relationship
`Number
`
`514
`ASSOCiate the
`Relationship Number /
`with the 3' Party
`Number
`!
`
`Create record in Local 616
`SLSDbase w/ 3"
`/
`Party Number and
`Relationship Number
`
`FIG. 5
`
`Page 10 of 29
`
`

`

`Patent Application Publication
`
`Nov. 7, 2013 Sheet 10 of 14
`
`US 2013/0295892 A1
`
`6 O O
`
`8.
`
`| Start Method for using a
`| Second Line Service to
`receive a call from a 3" \
`|
`Party with a Subscriber
`(
`\ TD associated with a |
`\ Primary Number and a |
`\ Second Line Number
`
`Receive a Call at TD -
`
`- 606
`
`/
`
`L
`AnSWer Call W/
`Primary Number
`Service
`
`^
`-
`
`-604
`X
`Y A
`^
`N
`- Call directed to N.
`
`X.
`
`YES
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Query Local SLS
`Dbase for Relationship
`Number
`
`
`
`AnSWer Call and
`populate calling party 610
`field with 3"Party
`/
`Number aSSOCiated
`with Relationship
`Number
`
`FIG. 6
`
`Page 11 of 29
`
`

`

`Patent Application Publication
`
`Nov. 7, 2013
`
`Sheet 11 of 14
`
`US 2013/0295892 A1
`
`700
`
`^
`GOTO
`Block
`732 of
`Fig. 7C
`
`f
`
`f
`Start Method for
`?
`Providing a
`f
`Second Line
`(
`8. \ Service using SIP
`
`\
`
`\
`)
`
`702
`Receive a
`\
`- Communication at an
`SLS Platform
`
`704 --
`
`No
`
`- Call to an SLSN
`number? -
`N
`-
`
`ves
`
`Query Central SLS
`706
`- Dbase for Calling
`Party CLID
`
`-
`
`/
`T
`E.
`E - vs -
`A5, YES
`
`708
`s
`- .
`Calling Party
`CID D
`recognized?
`
`
`
`
`
`710
`
`
`
`ASSOciate a dialable
`Relationship Number
`with the Caling Party
`CLID and the Called
`Party's Primary
`Number and SLS No.
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Create record in
`Central SLSDbase w/ | 72
`Calling Party CLID and
`Called Party Primary -
`Number and SLS NO.
`mapped to
`Relationship Number
`
`-^
`
`Redirect Call to Called
`Party via SIP and
`714.
`populate calling party
`|
`field with COmbination -
`of Relationship
`Number and Calling
`Party CLID
`
`Receive Call at Called
`Party TD and store
`Relationship Number A
`and Calling Party CLID
`Combination in LOCal
`SLS Dbase
`
`Display Calling Party 718
`CLID on TD and alert
`/ -
`Subscriber to incoming
`Call
`
`720
`Connect Calling Party
`cal to Called Party Tb
`using SIP
`
`
`
`
`
`Page 12 of 29
`
`

`

`Patent Application Publication
`
`Nov. 7, 2013 Sheet 12 of 14
`
`US 2013/0295892 A1
`
`From
`Block
`708 of
`Fi 9 7 A /
`
`724
`
`Query Central SLS
`Dbase for Relationship
`Number mapped to
`Calling Party CLID and
`Called SLS Number
`
`l
`
`Redirect Call to Called
`Party via SIP and
`populate Calling party
`field with Combination
`of Relationship
`Number and Calling
`Party CLID
`
`Receive Call at Called
`Party's TD and Display
`Calling Party CLID on
`TD
`
`Alert Called Party to
`Incoming Call
`
`
`
`Connect Calling Party
`call to Called Party TD
`
`FIG. 7B
`
`Page 13 of 29
`
`

`

`Patent Application Publication
`
`Nov. 7, 2013 Sheet 13 of 14
`
`US 2013/0295892 A1
`
`From
`Block
`704 of
`Fig. 7A
`
`
`
`^
`GoTo
`Block
`420
`NFig. 7D
`
`-
`
`732- !
`c t
`a
`No Rip
`number
`ves
`
`734
`'
`
`Query Central SLS
`Dbase for Calling
`- Party Primary Numbe
`r
`and Relationship
`Number Combination
`
`- 737
`y
`t
`-
`YES - Called Party No.
`an SLS No.? -
`N -
`NO
`- 738
`
`L
`Redirect Call to Called
`Party Number and
`populate Calling party
`field with Calling Party
`Second Line Number
`
`739
`—
`Redirect Call to Called
`Party Number via SIP
`and populate Calling
`party field with Calling
`Party Second Line
`Number
`
`
`
`Connect Calling Party
`call to Called Party TD
`
`Determine Called
`Party Number
`aSSOCiated with
`queried Calling Party
`Primary Number and
`Relationship Number
`
`FIG. 7C
`
`Page 14 of 29
`
`

`

`Patent Application Publication
`
`Nov. 7, 2013 Sheet 14 of 14
`
`US 2013/0295892 A1
`
`From
`Block
`732 of
`Fig. 7C /
`
`742
`l
`- Data
`- communication s
`NO from a Second Line
`Client? -
`
`-
`
`744
`
`Terminate
`Call
`
`746
`
`Ys
`
`ves
`
`Query SLS Central
`Dbase for SLS NO.
`and determine next
`available Relationship
`Number
`
`!
`
`Return next available
`Relationship Number
`to Calling Party TD via
`SIP
`
`Create record in
`Central SLS database
`w/ 3"Party CLID and
`Relationship Number
`aSSOCiated With
`Subscriber's SLS and
`Primary Nos.
`
`GOTO
`Start
`
`FIG. 7D
`
`Page 15 of 29
`
`

`

`US 2013/0295892 A1
`
`Nov. 7, 2013
`
`SYSTEMAND METHOD FOR PROVISION OF
`A SECOND LINE SERVICE TO A
`TELECOMMUNICATIONS DEVICE USING
`MIXED PROTOCOLS
`
`CROSS-REFERENCE
`0001. This application is a Continuation-In-Part of the
`currently pending United States application for patent filed on
`May 7, 2012, entitled SYSTEMAND METHOD FOR PRO
`VISION OF A SECOND LINE SERVICE TOATELECOM
`MUNICATIONS DEVICE and assigned Ser. No. 13/466,
`074, the entire contents of which are hereby incorporated by
`reference. Priority is also hereby claimed under 35 U.S.C.
`S119(e) to U.S. provisional application entitled "CROSS
`CARRIER MOBILE DEVICE CLIENT USING DATA
`CHANNEL FOR SIP CALL filed on Jun. 17, 2012 and
`assigned application Ser. No. 61/660,772, the entire contents
`of which are hereby incorporated by reference.
`
`BACKGROUND
`0002. In simpler times, communication meant a face to
`face conversation, a hand written note or, perhaps, a phone
`call between two land lines. Times have changed. People
`today communicate constantly and simultaneously via
`myriad channels, most of which are mobile. Of all the means
`of communication available to today's users, the cellular
`telephone may be the most ubiquitous. It seems that every
`body has one and that everybody uses their mobile device to
`stay connected, keep their busy lives moving forward, and
`fulfill their endless responsibilities.
`0003 For many people, those endless responsibilities are
`of a personal and professional mix. Fielding phone calls and
`texts from family and friends on the same mobile device from
`which you endeavor to conduct business is a recipe for con
`fusion. When taking a call from your top client, its probably
`a good idea to avoid getting it mixed up with a call from your
`spouse. The greeting “Hey, Honey!' can undermine even the
`best of business relationships.
`0004 To keep the personal and business channels of com
`munication separated, many people simply carry two separate
`mobile devices, each with its own dedicated phone number
`and service options. If mobile device 'A' rings, the user
`knows its of a personal nature. If mobile device “B” rings, the
`user knows that it's a business related call. Although carrying
`two mobile devices with you is one solution for keeping
`personal and business demands separate, keeping track of two
`mobile devices and their related service plans, however, can
`be frustrating and expensive.
`0005 For many users, porting a second phone number to a
`single device makes more sense—in doing so, at least the
`number of devices that must be kept up with in order to keep
`personal and business matters segregated have been reduced.
`But current systems and methods for managing multiple
`numbers on a single device are not without issues. For
`example, adding a second line to a service plan often dictates
`that the user have a more expensive “family plan” established
`with the service provider and often there still is no good way
`to know which number a calling party has dialed. Using a
`dual-SIM ('subscriber identity module') phone is another
`solution, with each SIM card being dedicated to a separate
`line, but the cost of redundant service plans to accommodate
`the multiple SIM cards, not to mention the cost of the dual
`SIM phone itself, can be exorbitant.
`
`0006 Another solution is to offer a second line number in
`the form of a virtual number. Calls to the virtual number are
`intercepted and forwarded to the primary number of a sub
`scriber's mobile device. To distinguish that the incoming call
`was originally directed to the virtual number as opposed to the
`primary number associated with the device, virtual number
`services known in the art simply populate a calling party field
`with the virtual number. The user sees the virtual number on
`the caller ID display and knows that the incoming call was
`made to the virtual number. If the virtual number is being used
`for a business venture, for example, seeing the virtual number
`on the caller ID display prompts the user to answer the call
`with an appropriate greeting. Notably, however, in some Vir
`tual number services the user of the virtual number service
`has no way of identifying the source of the incoming call—he
`can only know that the incoming call was made to the virtual
`number.
`0007. In other virtual number services, the problem of
`identifying the call as an incoming call to the virtual number
`without sacrificing the ability to also know the source of the
`incoming call is solved with the addition of a dialable prefix
`to the incoming call identification (e.g., 88*770.283.5555).
`Notably, however, to provide such a solution the virtual num
`ber service must work in cooperation with the subscriber's
`primary service provider so that the dialable prefix is
`acknowledged as a trigger to forward the incoming call to the
`subscriber's device.
`0008 Accordingly, what is needed is a system and method
`for providing a plurality of dedicated phone numbers to a
`single telecommunications device in Such a manner that the
`user of the device can separate and manage communications
`on each. Further, what is needed is a system and method for
`providing a second line service to a device in Such a manner
`that only a single primary phone number is required from the
`device's primary service provider. Even further, what is
`needed is a system and method for providing a second line
`service to a device in Such a manner that the second line
`service can be provided to the subscriber without having to
`coordinate with the subscriber's primary service provider.
`
`SUMMARY OF THE DISCLOSURE
`0009. A method and system are described for routing calls
`between a third party telecommunications device (“TD) and
`a subscriber TD associated with a primary service and a
`second line service (“SLS). An exemplary method according
`to one aspect includes receiving a callatan SLS platform that
`is interposed between a network of a primary service provider
`to the subscriber TD and a network of a primary service
`provider to the third party TD. The call, although directed by
`the third party TD to the subscriber TD associated with the
`second line service, is routed to the SLS platform.
`0010. Upon receiving the call, the SLS platform queries a
`local database of the SLS platform to identify a relationship
`number that serves to map the subscriber's primary numberto
`the combination of the third party calling number and the
`subscriber's second line number. The call is then redirected to
`the primary number of the subscriber's TD and the call is
`completed. Notably, the relationship number and third party
`calling number combination may be forwarded to the sub
`scriber TD, thus enabling an application on the subscriber TD
`to save the combination in a local database of the subscriber
`TD.
`0011 Advantageously, the relationship number can be
`used at a later time should the subscriber desire to call the
`
`Page 16 of 29
`
`

`

`US 2013/0295892 A1
`
`Nov. 7, 2013
`
`third party. Dialing the third party number from the SLS
`application on the Subscriber TD causes the relationship num
`ber for the third party to be dialed. As such, the call is actually
`routed to the SLS platform which subsequently uses the sec
`ond line service number of the subscriber TD and the rela
`tionship number that routed the call to the SLS platform to
`determine the actual third party called number. Using the
`actual third party called number, the SLS platform completes
`the second leg of the call. In certain embodiments, a call leg
`between a subscriber device and the SLS platform may be
`completed using a session initiated protocol (“SIP) so that
`the data service provided by the primary service provider of
`the subscriber device is used in lieu of a voice channel.
`0012 Another exemplary method according to a second
`aspect includes receiving at an SLS platform a first-time call
`to a number associated with a third party TD, the SLS plat
`form being interposed between a network of a primary service
`provider to the subscriber TD and a network of a primary
`service provider to the third party TD. The call may be
`directed to the SLS platform via a new relationship number
`selected by the SLS client application running on the sub
`scriber TD. In such case, the relationship number routes to the
`SLS platform and the third party number is provided to the
`SLS platform from the subscriber TD. In other embodiments,
`the new SLS client number may be requested from the SLS
`platform before making the call and then used by the sub
`scriber TD to make the call to the third party via the SLS
`platform. In either case, a new relationship number is used to
`direct an SLS call from the subscriber TD to the SLS plat
`form.
`0013. In the databases located at the subscriber TD and the
`SLS platform, the new relationship number maps the sub
`scriber's primary number to the combination of the third
`party number and the subscriber's second line number. The
`call is redirected by the SLS platform to the number associ
`ated with the third party TD and the call is completed.
`0014 Advantageously, the new relationship number can
`be used at a later time should the subscriber desire to call the
`third party. Dialing the third party number from the SLS
`application on the Subscriber TD causes the relationship num
`ber for the third party to be dialed. As such, the call is actually
`routed to the SLS platform which subsequently uses the sec
`ond line service number of the subscriber TD and the rela
`tionship number that routed the call to the SLS platform to
`determine the actual third party called number. Using the
`actual third party called number, the SLS platform completes
`the second leg of the call. As mentioned above and described
`below, in certain embodiments a call leg between a subscriber
`device and the SLS platform may be completed using a ses
`sion initiated protocol (“SIP) so that the data service pro
`vided by the primary service provider of the subscriber device
`is used in lieu of a Voice channel.
`0015. By associating the SLS number of the subscriber,
`the primary number of the subscriber and the primary number
`of a third party via a common relationship number, calls can
`be directed to and from a second service line of a subscriber
`TD without having to provide the second line service through
`the subscriber's primary service provider. Even so, in some
`embodiments, the subscriber's primary service provider may
`also be the second line service provider.
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`0016. In the Figures, like reference numerals refer to like
`parts throughout the various views unless otherwise indi
`
`cated. For reference numerals with letter character designa
`tions such as “102A or “102B, the letter character designa
`tions may differentiate two like parts or elements present in
`the same figure. Letter character designations for reference
`numerals may be omitted when it is intended that a reference
`numeral encompass all parts having the same reference
`numeral in all figures.
`0017 FIG. 1 is a high level diagram illustrating exemplary
`components of a system for providing a second line service
`(“SLS) to a user of telecommunications device (“TD).
`0018 FIG. 2 is a diagram of an exemplary computer archi
`tecture for the system of FIG. 1.
`(0019 FIGS. 3A-3B illustrate exemplary data tables that
`may be leveraged by a redirection module of an SLS platform
`and an SLS module of a subscriber TD to provide a second
`line service to a user of the subscriber TD.
`0020 FIGS. 4A-4D collectively illustrate an exemplary
`method for routing calls between a third party TD and a
`Subscriber TD.
`0021
`FIG. 5 illustrates an exemplary method for routing
`calls from a subscriber TD associated with a primary number
`and a second line number to a third party TD.
`0022 FIG. 6 illustrates an exemplary method for routing
`calls from a third party TD to a subscriber TD associated with
`a primary number and a second line number.
`(0023 FIGS. 7A-7D collectively illustrate an exemplary
`method for routing calls with a session initiated protocol
`(“SIP) between a calling telecommunications device (which
`may or may not have its own second line service) and a called
`telecommunications device (which may or may not have its
`own second line service).
`
`DETAILED DESCRIPTION
`0024. The word “exemplary” is used hereinto mean “serv
`ing as an example, instance, or illustration.” Any aspect
`described herein as “exemplary' is not necessarily to be con
`Strued as preferred or advantageous over other aspects.
`0025. In this description, the terms “application' and
`“app' may also include files having executable content, Such
`as: object code, Scripts, byte code, markup language files, and
`patches. In addition, an “application” referred to herein, may
`also include files that are not executable in nature, Such as
`documents that may need to be opened or other data files that
`need to be accessed. Further, an 'application' may be a com
`plete program, a module, a routine, a library function, a driver,
`etc.
`0026. The term “content may also include files having
`executable content, such as: object code, Scripts, byte code,
`markup language files, and patches. In addition, "content
`referred to herein, may also include files that are not execut
`able in nature. Such as documents that may need to be opened
`or other data files that need to be accessed.
`0027. As used in this description, the terms “component.”
`“database.” “module.” “system.” and the like are intended to
`refer to a computer-related entity, either hardware, firmware,
`a combination of hardware and software, software, or soft
`ware in execution. For example, a component may be, but is
`not limited to being, a process running on a processor, a
`processor, an object, an executable, a thread of execution, a
`program, and/or a computer. By way of illustration, both an
`application running on a computing device and the comput
`ing device may be a component.
`0028. One or more components may reside within a pro
`cess and/or thread of execution, and a component may be
`
`Page 17 of 29
`
`

`

`US 2013/0295892 A1
`
`Nov. 7, 2013
`
`localized on one computer and/or distributed between two or
`more computers. In addition, these components may execute
`from various computer readable media having various data
`structures stored thereon. The components may communicate
`by way of local and/or remote processes Such as in accor
`dance with a signal having one or more data packets (e.g., data
`from one component interacting with another component in a
`local system, distributed system, and/or across a network
`Such as the Internet with other systems by way of the signal).
`0029. In this description, the terms “telecommunications
`device.” “communication device.” “wireless device.” “wire
`less telephone.” “wireless communication device' and “wire
`less handset’ are used interchangeably. With the advent of
`third generation (3G”) and fourth generation (“4G”) wire
`less technology, greater bandwidth availability has enabled
`more portable computing devices with a greater variety of
`wireless capabilities. Therefore, a telecommunications
`device (“TD) may include a cellular telephone, a pager, a
`PDA, a Smartphone, a navigation device, a tablet personal
`computer (“PC”), or a hand-held computer with a wireless
`connection or link.
`0030. In this description, the terms “call” and “communi
`cation in their noun forms, envision any data transmission
`routed across a network from one device to another including,
`but not limited to, a Voice transmission, a text message, a
`Video message, a page, a data transmission, etc.
`0031
`Referring to FIG.1, depicted is a high level diagram
`illustrating exemplary components of a system 100 for pro
`viding a second line service to a user of Subscriber Telecom
`munications Device (“TD) 110. TD 110 is also associated
`with a primary phone number assigned to it by a primary
`service provider, as is understood by one of ordinary skill in
`the art. A subscriber to a second line service (SLS) offered
`through exemplary system 100 may receive calls at TD 110
`that are directed to either of the primary phone number pro
`vided by the primary service provider or the secondary phone
`number (“SLS phone number) provided, serviced and or
`facilitated by the SLS platform 115. Notably, depending on
`the particular embodiment, the primary service provider and
`the SLS platform (i.e., the second line service provider) may
`be the same provider or different providers. In embodiments
`where the primary service provider and the second line ser
`vice provider are different providers, the subscriber may
`receive separate billing records from each provider. However,
`it is envisioned that certain embodiments where the primary
`service provider and the second line service provider are not
`one and the same may take advantage of session initiated
`protocols (“SIP) to simplify billing records for the user. A
`more detailed description of embodiments that use SIP pro
`tocols is provided below relative to FIG. 7.
`0032. In general, any call directed to either of the primary
`phone number or the SLS phone number are transmitted from
`a third party TD 120 to the subscriber TD 110 by way of
`communications network 125. Notably, communications net
`work 125 envisions any and all networks for transmitting and
`terminating communications between telecommunications
`devices such as, but not limited to, cellular networks, PSTNs,
`cable networks and the Internet. Methods for effecting the
`transmission of data across communications network 125
`from one device to another, including call setups, termina
`tions and the like are understood by those of ordinary skill in
`the art of data transmission and may include the use of pro
`tocols and standards such as, but not limited to, signaling
`system seven (“SS7) protocol suite, SIP customized appli
`
`cations for mobile networks enhanced logic (“CAMEL') or
`CAMEL Application Part (“CAP), remote operations ser
`vice element (“ROSE), Voice Over IP (“VOIP”), etc. Nota
`bly, while the use of any particular protocol or communica
`tions standard may be a novel aspect of a particular
`embodiment of the systems and methods, it will be under
`stood that the scope of the systems and methods disclosed
`herein is not limited to the use of any particular protocol or
`combination of protocols.
`0033. A call made from a third party TD120 to the primary
`number associated with subscriber TD 110 is transmitted
`across communications network 125 and routed to subscriber
`TD 110, as is understood in the art. The radio transceiver 104,
`if the TD 110 is a portable and wireless device, enables the
`receipt and transmission of signals to and from Subscriber TD
`110. The call signal may include the calling line identification
`(“CLID), i.e. the phone number, associated with third party
`TD 120 such that when the call is received at Subscriber TD
`110, the CLID may be displayed for the benefit of the sub
`scriber on display component 103. Notably, although the
`exemplary embodiments described in the present disclosure
`use the CLID as an example of data that may be displayed for
`the benefit of the user of a subscriber TD 110, it will be
`understood that any data associated with the third party TD
`120, subscriber TD 110, SLS platform 115 or the like may be
`rendered for the benefit of the user of the system 100 and, as
`such, only describing that the CLID is displayed will not limit
`the scope of what is envisioned by the disclosure. Moreover,
`it is envisioned that any data uniquely associated with a call to
`a primary number oran SLS number may be displayed for the
`benefit of a subscriber to the system 100.
`0034 Returning to the FIG.1 illustration, a call made from
`a third party TD 120 to an SLS number associated with
`subscriber TD 110 is transmitted across network 125. As one
`of ordinary skill in the art will be aware, the network 125
`recognizes where the call needs to be routed based on the
`called number (the SLS number associated with the sub
`scriber) and routes the call to SLS platform 115. SLS platform
`115 thus effectively intercepts the call, determines that the
`call was intended for subscriber TD 110 and then takes
`actions such that the call can be terminated at the subscriber
`TD 110. In this way, while a call directed to a primary number
`associated with subscriber TD 110 is routed directly to sub
`scriber TD 110, a call directed to a second line number asso
`ciated with subscriber TD 110 is routed to SLS platform 115
`instead. Once received at SLS platform 115, a query of central
`SLS database 116 by redirection module 117 may determine
`that the call from third party TD 120 was meant for the second
`line number associated with the subscriber associated with
`TD 110. Once the determination is made, redirection module
`117 may modify the call data to include data that reflects its
`identification as a call for the second line number and then
`cause the call to be available for termination at the primary
`number