APPLICATION
`NUMBER
`61/660,772
`
`FILING or
`37l(c)DATE
`06/17/2012
`
`GRPART
`UNIT
`
`FIL FEE REC'D
`125
`
`35856
`SMITH RISLEY TEMPEL SANTOS LLC
`Two Ravinia Drive
`Suite 700
`ATLANTA, GA 30346
`
`Ul\TfED STATES DEPA RTME'IT OF COMMERCE
`United States Patent and Trademark Office
`Adiliess. COMMISSIO'JER FOR PATENTS
`PO Box 1450
`Alexandria, Virgmia 22313-1450
`\VVi\V.USpto.gov
`
`ATTY.DOCKET.NO
`07001.1560
`
`TOT CLAIMS IND CLAIMS
`
`CONFIRMATION NO. 8616
`FILING RECEIPT
`
`11111111111111111 lllll ll]~!l]!~l!~l!~H!~!il!ljll 111111111111111 IIII IIII
`
`Date Mailed: 06/25/2012
`
`Receipt is acknowledged of this provisional patent application. It will not be examined for patentability and will
`become abandoned not later than twelve months after its filing date. Any correspondence concerning the application
`must include the following identification information: the U.S. APPLICATION NUMBER, FILING DATE, NAME OF
`APPLICANT, and TITLE OF INVENTION. Fees transmitted by check or draft are subject to collection. Please verify
`the accuracy of the data presented on this receipt. If an error is noted on this Filing Receipt, please submit
`a written request for a Filing Receipt Correction. Please provide a copy of this Filing Receipt with the
`changes noted thereon. If you received a "Notice to File Missing Parts" for this application, please submit
`any corrections to this Filing Receipt with your reply to the Notice. When the USPTO processes the reply
`to the Notice, the USPTO will generate another Filing Receipt incorporating the requested corrections
`
`Applicant( s)
`
`George Backhaus, Atlanta, GA;
`Romero Jose, Atlanta, GA;
`Paul Rubenstein, Atlanta, GA;
`John Green, Atlanta, GA;
`Power of Attorney:
`Matthew Hoots--67778
`
`If Required, Foreign Filing License Granted: 06/21/2012
`The country code and number of your priority application, to be used for filing abroad under the Paris Convention,
`is US 61/660,772
`Projected Publication Date: None, application is not eligible for pre-grant publication
`Non-Publication Request: No
`Early Publication Request: No
`** SMALL ENTITY **
`Title
`
`Cross Carrier Mobile Device Client Using Data Channel for SIP Call
`
`PROTECTING YOUR INVENTION OUTSIDE THE UNITED STATES
`
`Since the rights granted by a U.S. patent extend only throughout the territory of the United States and have no
`effect in a foreign country, an inventor who wishes patent protection in another country must apply for a patent
`in a specific country or in regional patent offices. Applicants may wish to consider the filing of an international
`application under the Patent Cooperation Treaty (PCT). An international (PCT) application generally has the same
`page 1 of 3
`
`Page 1 of 93
`
`GOOGLE EXHIBIT 1006
`
`

`

`effect as a regular national patent application in each PCT-member country. The PCT process simplifies the filing
`of patent applications on the same invention in member countries, but does not result in a grant of "an international
`patent" and does not eliminate the need of applicants to file additional documents and fees in countries where patent
`protection is desired.
`
`Almost every country has its own patent law, and a person desiring a patent in a particular country must make an
`application for patent in that country in accordance with its particular laws. Since the laws of many countries differ
`in various respects from the patent law of the United States, applicants are advised to seek guidance from specific
`foreign countries to ensure that patent rights are not lost prematurely.
`
`Applicants also are advised that in the case of inventions made in the United States, the Director of the US PTO must
`issue a license before applicants can apply for a patent in a foreign country. The filing of a U.S. patent application
`serves as a request for a foreign filing license. The application's filing receipt contains further information and
`guidance as to the status of applicant's license for foreign filing.
`
`Applicants may wish to consult the USPTO booklet, "General Information Concerning Patents" (specifically, the
`section entitled "Treaties and Foreign Patents") for more information on timeframes and deadlines for filing foreign
`patent applications. The guide is available either by contacting the USPTO Contact Center at 800-786-9199, or it
`can be viewed on the USPTO website at http://www.uspto.gov/web/offices/pac/doc/general/index.html.
`
`For information on preventing theft of your intellectual property (patents, trademarks and copyrights), you may wish
`to consult the U.S. Government website, http://www.stopfakes.gov. Part of a Department of Commerce initiative,
`this website includes self-help "toolkits" giving innovators guidance on how to protect intellectual property in specific
`countries such as China, Korea and Mexico. For questions regarding patent enforcement issues, applicants may
`call the U.S. Government hotline at 1-866-999-HAL T (1-866-999-4158).
`
`LICENSE FOR FOREIGN FILING UNDER
`
`Title 35, United States Code, Section 184
`
`Title 37, Code of Federal Regulations, 5.11 & 5.15
`
`GRANTED
`
`The applicant has been granted a license under 35 U.S.C. 184, if the phrase "IF REQUIRED, FOREIGN FILING
`LICENSE GRANTED" followed by a date appears on this form. Such licenses are issued in all applications where
`the conditions for issuance of a license have been met, regardless of whether or not a license may be required as
`set forth in 37 CFR 5.15. The scope and limitations of this license are set forth in 37 CFR 5.15(a) unless an earlier
`license has been issued under 37 CFR 5.15(b). The license is subject to revocation upon written notification. The
`date indicated is the effective date of the license, unless an earlier license of similar scope has been granted under
`37 CFR 5.13 or 5.14.
`
`This license is to be retained by the licensee and may be used at any time on or after the effective date thereof unless
`it is revoked. This license is automatically transferred to any related applications(s) filed under 37 CFR 1.53(d). This
`license is not retroactive.
`
`The grant of a license does not in any way lessen the responsibility of a licensee for the security of the subject matter
`as imposed by any Government contract or the provisions of existing laws relating to espionage and the national
`security or the export of technical data. Licensees should apprise themselves of current regulations especially with
`page 2 of 3
`
`Page 2 of 93
`
`

`

`respect to certain countries, of other agencies, particularly the Office of Defense Trade Controls, Department of
`State (with respect to Arms, Munitions and Implements of War (22 CFR 121-128)); the Bureau of Industry and
`Security, Department of Commerce (15 CFR parts 730-774); the Office of Foreign AssetsControl, Department of
`Treasury (31 CFR Parts 500+) and the Department of Energy.
`
`NOT GRANTED
`
`No license under 35 U.S.C. 184 has been granted at this time, if the phrase "IF REQUIRED, FOREIGN FILING
`LICENSE GRANTED" DOES NOT appear on this form. Applicant may still petition for a license under 37 CFR 5.12,
`if a license is desired before the expiration of 6 months from the filing date of the application. If 6 months has lapsed
`from the filing date of this application and the licensee has not received any indication of a secrecy order under 35
`U.S.C. 181, the licensee may foreign file the application pursuant to 37 CFR 5.15(b).
`
`Select USA
`
`The United States represents the largest, most dynamic marketplace in the world and is an unparalleled location
`for business investment, innovation and commercialization of new technologies. The USA offers tremendous
`resources and advantages for those who invest and manufacture goods here. Through SelectUSA, our nation
`works to encourage, facilitate, and accelerate business investment. To learn more about why the USA is the best
`country in the world to develop technology, manufacture products, and grow your business, visit SelectUSA.gov.
`
`page 3 of 3
`
`Page 3 of 93
`
`

`

`Doc Code: TR.PROV
`Document Description: Provisional Cover Sheet (SB16)
`
`PTO/SB/16 (11-08)
`Approved for use through 01/31/2014 0MB 0651-0032
`U.S. Patent and Trademark Office: U.S. DEPARTMENT OF COMMERCE
`Under the Paperwork Reduction Act of 1995, no persons are required to respond to a collection of information unless it displays a valid 0MB control number
`Provisional Application for Patent Cover Sheet
`This is a request for filing a PROVISIONAL APPLICATION FOR PATENT under 37 CFR 1.53(c)
`
`lnventor(s)
`
`Inventor 1
`
`Given Name
`
`Middle Name
`
`Family Name
`
`City
`
`State
`
`George
`
`Inventor 2
`
`Backhaus
`
`Atlanta
`
`GA
`
`Given Name
`
`Middle Name
`
`Family Name
`
`City
`
`State
`
`Romero
`
`Inventor 3
`
`Jose
`
`Atlanta
`
`GA
`
`Given Name
`
`Middle Name
`
`Family Name
`
`City
`
`State
`
`Paul
`
`Inventor 4
`
`Rubenstein
`
`Atlanta
`
`GA
`
`Given Name
`
`Middle Name
`
`Family Name
`
`City
`
`State
`
`John
`
`Green
`
`Atlanta
`
`GA
`
`Remove
`
`Country
`
`i
`
`us
`
`Remove
`
`Country
`
`i
`
`us
`
`Remove
`
`Country
`
`i
`
`us
`
`Remove
`
`Country
`
`i
`
`us
`
`All Inventors Must Be Listed -Additional Inventor Information blocks may be
`generated within this form by selecting the Add button.
`
`I Add
`
`I
`
`Title of Invention
`
`Cross Carrier Mobile Device Client Using Data Channel for SIP Call
`
`Attorney Docket Number (if applicable)
`
`07001.1560
`
`Correspondence Address
`
`Direct all correspondence to (select one):
`
`(!) The address corresponding to Customer Number
`
`0 Firm or Individual Name
`
`Customer Number
`
`35856
`
`The invention was made by an agency of the United States Government or under a contract with an agency of the United
`States Government.
`
`(!) No.
`0 Yes, the name of the U.S. Government agency and the Government contract number are:
`
`EFS - Web 1.0.1
`
`Page 4 of 93
`
`

`

`Doc Code: TR.PROV
`Document Description: Provisional Cover Sheet (SB16)
`
`PTO/SB/16 (11-08)
`Approved for use through 01/31/2014 0MB 0651-0032
`U.S. Patent and Trademark Office: U.S. DEPARTMENT OF COMMERCE
`Under the Paperwork Reduction Act of 1995, no persons are required to respond to a collection of information unless it displays a valid 0MB control number
`
`Entity Status
`Applicant claims small entity status under 37 CFR 1.27
`
`(!) Yes, applicant qualifies for small entity status under 37 CFR 1.27
`0 No
`Warning
`
`Petitioner/applicant is cautioned to avoid submitting personal information in documents filed in a patent application that may
`contribute to identity theft. Personal information such as social security numbers, bank account numbers, or credit card
`numbers (other than a check or credit card authorization form PTO-2038 submitted for payment purposes) is never required
`by the USPTO to support a petition or an application. If this type of personal information is included in documents submitted
`to the USPTO, petitioners/applicants should consider redacting such personal information from the documents before
`submitting them to USPTO. Petitioner/applicant is advised that the record of a patent application is available to the public
`after publication of the application (unless a non-publication request in compliance with 37 CFR 1.213(a) is made in the
`application) or issuance of a patent. Furthermore, the record from an abandoned application may also be available to the
`public if the application is referenced in a published application or an issued patent (see 37 CFR1 .14). Checks and credit
`card authorization forms PT0-2038 submitted for payment purposes are not retained in the application file and therefore are
`not publicly available.
`
`Signature
`
`Please see 37 CFR 1.4(d} for the form of the signature.
`
`Signature
`
`/Matthew T. Hoots/
`
`Date (YYYY-MM-DD}
`
`2012-06-17
`
`First Name
`
`Matthew
`
`Last Name
`
`Hoots
`
`Registration Number
`(If appropriate)
`
`67778
`
`This collection of information is required by 37 CFR 1.51. The information is required to obtain or retain a benefit by the public which is to
`file (and by the USPTO to process) an application. Confidentiality is governed by 35 U.S.C. 122 and 37 CFR 1.11 and 1.14. This collection
`is estimated to take 8 hours to complete, including gathering, preparing, and submitting the completed application form to the USPTO.
`Time will vary depending upon the individual case. Any comments on the amount of time you require to complete this form and/or
`suggestions for reducing this burden, should be sent to the Chief Information Officer, U.S. Patent and Trademark Office, U.S. Department
`of Commerce, P.O. Box 1450, Alexandria, VA 22313-1450. DO NOT SEND FEES OR COMPLETED FORMS TO THIS ADDRESS. This
`form can only be used when in conjunction with EFS-Web. If this form is mailed to the USPTO, it may cause delays in handling
`the provisional application.
`
`EFS - Web 1.0.1
`
`Page 5 of 93
`
`

`

`Privacy Act Statement
`
`The Privacy Act of 1974 (P.L. 93-579) requires that you be given certain information in connection with your submission of
`the attached form related to a patent application or paten. Accordingly, pursuant to the requirements of the Act, please be
`advised that : (1) the general authority for the collection of this information is 35 U.S.C. 2(b)(2}; (2) furnishing of the
`information solicited is voluntary; and (3) the principal purpose for which the information is used by the U.S. Patent and
`Trademark Office is to process and/or examine your submission related to a patent application or patent. If you do not
`furnish the requested information, the U.S. Patent and Trademark Office may not be able to process and/or examine your
`submission, which may result in termination of proceedings or abandonment of the application or expiration of the patent.
`
`The information provided by you in this form will be subject to the following routine uses:
`
`1.
`
`2.
`
`3.
`
`4.
`
`5.
`
`6.
`
`7.
`
`8.
`
`9.
`
`The information on this form will be treated confidentially to the extent allowed under the Freedom of Information
`Act (5 U.S.C. 552) and the Privacy Act (5 U.S.C 552a). Records from this system of records may be disclosed to the
`Department of Justice to determine whether disclosure of these records is required by the Freedom of Information
`Act.
`A record from this system of records may be disclosed, as a routine use, in the course of presenting evidence to
`a court, magistrate, or administrative tribunal, including disclosures to opposing counsel in the course of settlement
`negotiations.
`A record in this system of records may be disclosed, as a routine use, to a Member of Congress submitting a
`request involving an individual, to whom the record pertains, when the individual has requested assistance from the
`Member with respect to the subject matter of the record.
`A record in this system of records may be disclosed, as a routine use, to a contractor of the Agency having need
`for the information in order to perform a contract. Recipients of information shall be required to comply with the
`requirements of the Privacy Act of 1974, as amended, pursuant to 5 U.S.C. 552a(m}.
`A record related to an International Application filed under the Patent Cooperation Treaty in this system of
`records may be disclosed, as a routine use, to the International Bureau of the World Intellectual Property
`Organization, pursuant to the Patent Cooperation Treaty.
`A record in this system of records may be disclosed, as a routine use, to a n other federal agency for purposes
`of National Security review (35 U.S.C. 181) and for review pursuant to the Atomic Energy Act (42 U.S.C. 218(c)).
`A record from this system of records may be disclosed, as a routine use, to the Administrator, General Services,
`or his/her designee, during an inspection of records conducted by GSA as part of that agency's responsibility to
`recommend improvements in records management practices and programs, under authority of 44 U.S.C. 2904 and
`2906. Such disclosure shall be made in accordance with the GSA regulations governing inspection of records for this
`purpose, and any other relevant (i.e., GSA or Commerce) directive. Such disclosure shall not be used to make
`determinations about individuals.
`A record from this system of records may be disclosed, as a routine use, to the public after either publication of
`the application pursuant to 35 U.S.C. 122(b} or issuance of a patent pursuant to 35 U.S.C. 151. Further, a record
`may be disclosed, subject to the limitations of 37 CFR 1.14, as a routine use, to the public if the record was filed in an
`application which became abandoned or in which the proceedings were terminated and which application is
`referenced by either a published application, an application open to public inspection or an
`issued patent.
`A record from this system of records may be disclosed, as a routine use, to a Federal, State, or local law
`enforcement agency, if the USPTO becomes aware of a violation or potential violation of law or regulation.
`
`Page 6 of 93
`
`

`

`Attorney Docket No. 07001.1550
`
`SYSTEM AND METHOD FOR PROVISION OF A SECOND LINE
`SERVICE TO A TELECOMMUNICATIONS DEVICE
`
`[0001]
`
`The Appendix attached hereto is a part of the specification.
`
`CROSS-REFERENCE
`
`[0002]
`
`In simpler times, communication meant a face to face conversation, a hand written note
`
`BACKGROUND
`
`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 everybody 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 confusion. When taking a call
`
`from your top client, it's 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 communication 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 it's 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.
`
`L ooos J
`
`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. Out 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
`
`1
`
`Page 7 of 93
`
`

`

`Attorney Docket No. 07001.1550
`
`fool proof 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
`
`subscriber'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 userto answer the call with an appropriate greeting. Notably,
`
`however, in some virtual 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 directed 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 number 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 the provisioning through the
`
`subscriber's primary service provider.
`
`2
`
`Page 8 of 93
`
`

`

`Attorney Docket No. 07001.1550
`
`[0009] A method and system are described for routing calls between a third paiiy
`
`SUMMARY OP TIIE DISCLOSURE
`
`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 call at an 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 to identify a
`
`relationship number that serves to map the subscriber's primary number to 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, receipt of the call at the subscriber TD includes transmission of the
`
`relationship number and third party calling number combination, thus enabling an
`
`application on the subscriber TD to save the combination in a local database.
`
`[OOll] Advantageously, the 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 number for the third party to be
`
`dialed. As such, the call is actually routed to the SLS platform which subsequently uses
`
`the second line service number of the subscriber TD and the relationship 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 platfom1 completes the second leg
`
`of the call.
`
`[0012] 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.
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`
`[0013]
`
`In the Figures, like reference numerals refer to like parts throughout the various views
`
`unless otherwise indicated. For reference numerals with letter character designations
`
`such as "102A" or "102B", the letter character designations may differentiate two like
`
`parts or elements present in the same figure. Letter character designations for reference
`
`3
`
`Page 9 of 93
`
`

`

`Attorney Docket No. 07001.1550
`
`numerals may be omitted when it is intended that a reference numeral encompass all
`
`paits having the same reference numeral in all figures.
`
`[0014]
`
`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").
`
`[0015]
`
`FIG. 2 is a diagram of an exemplary computer architecture for the system of FIG. 1.
`
`[0016]
`
`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.
`
`[0017]
`
`FIGS. 4A-4D collectively illustrate an exemplary method for routing calls between a
`
`third party TD and a subscriber TD.
`
`[0018]
`
`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.
`
`[0019]
`
`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.
`
`DETAILED DESCRIPTION
`
`[0020]
`
`The word "exemplary" is used herein to mean "serving as an example, instance, or
`
`illustration." Any aspect described herein as "exemplary" is not necessarily to be
`
`construed as preferred or advantageous over other aspects.
`
`L0021J
`
`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 complete program, a
`
`module, a routine, a library function, a driver, etc.
`
`[0022]
`
`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 executable in nature, such as
`
`documents that may need to be opened or other data files that need to be accessed.
`
`[0023]
`
`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 software 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,
`
`4
`
`Page 10 of 93
`
`

`

`Attorney Docket No. 07001.1550
`
`and/or a computer. Dy way of illustration, both an application rmming on a computing
`
`device and the computing device may be a component.
`
`[0024]
`
`One or more components may reside within a process and/or thread of execution, and a
`
`component may be 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 accordance 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).
`
`[0025]
`
`In this description, the terms "telecommunications device," "communication device,"
`
`"wireless device," "wireless telephone," "wireless conununication device" and
`
`"wireless handset" are used interchangeably. With the advent of third generation
`
`("3G") and fourth generation ("4G") wireless 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.
`
`[0026]
`
`In this description, the terms "call" and "communication," 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 tex1: message, a video message, a page, a data
`
`transmission, etc.
`
`[0027]
`
`Referring to FIG. 1, depicted is a high level diagram illustrating exemplary components
`
`of a system 100 for providing a second line service to a user of 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 provided by the primary service provider
`
`or the secondary phone number ("SLS phone number") provided by the SLS platform
`
`115.
`
`[0028]
`
`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
`
`communications network 125. Notably, communications network 125 envisions any
`
`and all networks for transmitting and terminating communications between
`
`5
`
`Page 11 of 93
`
`

`

`Attorney Docket No. 07001.1550
`
`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,
`
`terminations and the like are understood by those of ordinary skill in the art of data
`
`transmission.
`
`[0029] A call made from a third party TD 120 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. 'lhe call signal may include the calling line identification ("CUD"),
`
`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
`
`subscriber on display component 103. Notably, although the exemplary embodiments
`
`described in the present disclosure use the CLID as an example of data that may
`
`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 or an SLS number may be displayed for the benefit of a
`
`subscriber to the system 100.
`
`[0030] Retuming 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. The
`
`network 125 recognizes where the call needs to be routed based on the called number
`
`(the SLS number associated with the subscriber) 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 forwards the call to subscriber TD 110. In this
`
`way, while a call directed to a primary number associated with subscriber TD 110 is
`
`routed directly to subscriber TD 110, a call directed to a second line number associated
`
`with subscriber