Case: 1:21-cv-00482 Document #: 1-2 Filed: 01/27/21 Page 1 of 17 PageID #:22
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Exhibit A
`
`
`
`
`
`
`
`
`
`
`
`
`

`

`Case: 1:21-cv-00482 Document #: 1-2 Filed: 01/27/21 Page 2 of 17 PageID #:23
`
`(12)
`
`United States Patent
`Stockhusen
`
`(*) Notice:
`
`(54) CONTROL OF A MULTI-MODE,
`MULTI-BAND MOBILE TELEPHONE VIA A
`SINGLE HARDWARE AND SOFTWARE MAN
`MACHINE INTERFACE
`(75) Inventor: Dirk Stockhusen, San Diego, CA (US)
`O
`O
`(73) Assignee: Siemens Communications, Inc., Boca
`Raton, FL (US)
`Subject to any disclaimer, the term of this
`patent is extended or adjusted under 35
`U.S.C. 154(b) by 913 days.
`(21) Appl. No.: 09/923,633
`(22) Filed:
`Aug. 6, 2001
`(65)
`Prior Publication Data
`US 2002/0132636 A1
`Sep. 19, 2002
`(51) Int. Cl.
`(2006.01)
`H04O 700
`(52) U.S. Cl. ................ 455/552.1; 455/433; $55,352.
`455/436; 709/230
`(58) Field of Classification Search ............. 455/552.1,
`455/553, 557, 406, 435.2, 426.1, 412.1, 556.2,
`455/433,436, 73, 90.3; 370/352: 340/5.53;
`439/66
`See application file for complete search history.
`References Cited
`U.S. PATENT DOCUMENTS
`5,923,761 A * 7/1999 Lodenius ..................... 455,73
`5,943,333 A * 8/1999 Whinnett et al. ........... 370,345
`5,946,634 A * 8/1999 Korpela ................... 455,552.1
`
`(56)
`
`US007 181237B2
`
`(10) Patent No.:
`(45) Date of Patent:
`
`US 7,181.237 B2
`Feb. 20, 2007
`
`6,035,212 A * 3/2000 Rostoker et al. ......... 455,552.1
`6,138,010 A 10/2000 Rabe et al.
`6,173,316 B1
`1/2001 De Boor et al.
`... 340,553
`6,633.223 B1 * 10/2003 Schenker et al. .....
`... 370,352
`6,697.355 B1* 2/2004 Lim .................
`... 455,557
`6,785,556 B2 * 8/2004 Souissi .............
`6,865,186 B1* 3/2005 Jackson et al. ............. 370/419
`6,934,558 B1* 8/2005 Sainton et al. ........... 455/552.1
`6,961,583 B2 * 11/2005 Moles et al. ...
`... 455,552.1
`2002/0086702 A1* 7/2002 Lai et al. .................... 455,556
`2003/0181168 A1* 9, 2003 Herrod et al. ....
`... 455/90.3
`2003/0224792 A1* 12/2003 Verma et al. ............... 455,436
`FOREIGN PATENT DOCUMENTS
`O 852 448 A1
`7, 1998
`EP
`WOOOf7794.0 A1 12/2000
`WO
`* cited by examiner
`Primary Examiner—Fan Tsang
`Assistant Examiner SA Elahee
`(57)
`ABSTRACT
`A system for controlling a multi-mode mobile telephone via
`a single hardware and Software man machine interface
`(MMI) includes a mode manager for managing Switching of
`the system between two or more modes utilizing different air
`interface standards Supported by different protocol stacks. A
`user interface communicates information and commands
`between the protocol stacks and a user. An application layer
`reduces the functional interface between the protocol stacks
`to layers of the protocol stacks Subsequent to the user
`interface, allowing control of the mobile telephone to be
`provided via a single MMI that is substantially consistent
`across the all modes.
`23 Claims, 8 Drawing Sheets
`
`
`
`5OO
`
`Lay R AM
`
`
`
`

`

`Case: 1:21-cv-00482 Document #: 1-2 Filed: 01/27/21 Page 3 of 17 PageID #:24
`
`U.S. Patent
`
`Feb. 20, 2007
`
`Sheet 1 of 8
`
`US 7,181.237 B2
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`1OO
`
`11O
`
`
`
`
`
`TRANSCETMEA
`
`MMAM
`65/A 4 TDMA)
`
`
`
`122
`
`Ada AdWaAE
`
`
`
`126
`
`118
`
`MMMM
`(6SM & TDMA)
`
`TRAWSCEIVER
`
`Afa ADM/AARE
`AEATL/RES
`
`
`
`6SAM 4 TDMA
`
`SEAZaA.
`
`SOLARCE
`
`Ate 1A
`
`

`

`am
`
`DF
`
`22#BD7a3
`
`VC
`Case: 1:21-cv-00482 Document #: 1-2 Filed: 01/27/21 Page 4 of 17 PageID #:25
`4egaP
`2
`2
`5
`b
`
`tPmS.8mCU
`
`1.002.mt
`
`2.w1,TNWHKpmN7,mww
`fS:5$8$3:$3...0U
` §WLmSWmMWZHKYQMQNVQYQQ4%e2,_mm.mwwmw$33fix.328K5.3%:
`
`i22FS2i2%Em3mmwm
`
`1—2m“mmvmmQmmzfimmfiwbolmzfimmfimssl
`2)\8adMmuENEZN«mg
`
`
`
`1..m35c.3“:meEmmi3%»fitmxm.§wm§
`1..E3855kmwfiqmmwflqm$83%own
`”In.7NNN:QLWXM
`
`
`

`

`Case: 1:21-cv-00482 Document #: 1-2 Filed: 01/27/21 Page 5 of 17 PageID #:26
`
`U.S. Patent
`
`Feb. 20, 2007
`
`Sheet 3 of 8
`
`US 7,181.237 B2
`
`21 O -
`
`236
`233
`
`214
`
`
`
`AMSSM/Sys7 EM
`
`6LOBaL OPERATINet
`5t/PORT
`sysre
`LEBRAAy
`22O
`24O
`MF
`AY
`21
`
`ASEANTERFACE
`234
`AAPL4
`AlaaTiOW Layer
`AMODEMANaer
`as/M/TDMA COAEF
`230
`
`AfoLASEKEEPLW6
`252
`
`AAAD/AAE Sys EMM
`223
`MW
`
`Aze. 2A
`
`

`

`Case: 1:21-cv-00482 Document #: 1-2 Filed: 01/27/21 Page 6 of 17 PageID #:27
`
`U.S. Patent
`
`Feb. 20, 2007
`
`Sheet 4 of 8
`
`US 7,181.237 B2
`
`N
`
`
`
`
`
`3O6
`
`
`
`OTHER AL
`
`SMS AL
`
`3.14
`/
`<Ns are
`
`3O4.
`
`AMSAM AL
`
`as
`
`31 O
`
`512
`
`AMMM
`MaWA6ER
`
`aSMA
`ALASER t12/
`
`Afte. 34
`
`TDMA
`
`316
`
`32. 3.
`
`TDMA
`MMANaer
`33O
`
`TDMA
`LEFM.E. 1/2/3
`
`TDMA
`
`316
`
`6SAM
`
`522
`
`3OO N
`
`OTHER AL
`
`
`
`
`
`6SMM
`AAyER 1/2/,
`
`A.Te. 3B
`
`TDMA
`stral
`
`323
`
`TDMA
`AAAAWales
`
`
`
`
`
`33O
`
`
`
`BRDeF
`
`TDMMA
`LEVEL 1/2/3
`
`

`

`Case: 1:21-cv-00482 Document #: 1-2 Filed: 01/27/21 Page 7 of 17 PageID #:28
`
`U.S. Patent
`
`Feb. 20, 2007
`
`Sheet S of 8
`
`US 7,181.237 B2
`
`
`
`
`
`ALA y2R 1/2/
`
`
`
`A76. 36
`
`TOMMA
`
`3.16
`
`523
`
`TDMA
`AAAWaer
`
`33O
`
`TDMMA
`
`AACA TOM Alayas
`
`N 4O2
`
`
`
`
`
`4O4.
`
`4t
`
`41
`
`4O6
`
`40
`
`AORM/4AD
`sEatZOW 4
`
`serov
`
`AEMERSE
`SECTION 1
`
`serow.
`
`SECTION 1
`
`SECTIOW 4
`
`44
`
`416
`
`413
`
`42O
`
`A Tie. 4
`
`BRZD6E
`
`

`

`Case: 1:21-cv-00482 Document #: 1-2 Filed: 01/27/21 Page 8 of 17 PageID #:29
`
`U.S. Patent
`
`Feb. 20, 2007
`
`Sheet 6 of 8
`
`US 7,181,237 B2
`
`
`
`
`
`AET/ORK
`aHaNeF
`WEEssa Ay?
`
`Atte. 6
`
`IWFORMM
`LASER
`
`

`

`Case: 1:21-cv-00482 Document #: 1-2 Filed: 01/27/21 Page 9 of 17 PageID #:30
`
`U.S. Patent
`
`Feb. 20, 2007
`
`Sheet 7 of 8
`
`US 7,181.237 B2
`
`
`
`MMI eSM
`714
`
`
`
`7O2
`N
`
`7OO
`MMI TDMAy18 /
`COMMAM
`7O4
`
`
`
`
`
`
`
`SERIAL
`LARTVER
`
`
`
`
`
`7O6
`SERIAL /
`DARTMEA
`
`A76, 7
`
`71O
`
`3OO
`
`AWTZTy A
`INFORMATION/
`ARIAMTTTMEs
`
`Layar n-1
`
`AWTTTy A
`INFORMATIOW/
`ARIAMITIVE6
`
`Alayar in
`
`
`
`TaSKA
`7 OOLS
`
`PROTOCOL
`
`amaume-
`
`aire-eeee
`
`AROTOCOL
`
`TaSKS
`7 OOLS
`
`PROTOCOL
`
`Lay R n-1
`
`TWFORMATIOW/
`ARIAMITIVES
`
`INFORMATION/
`ARIAMITT/E.6
`
`AT6. 3
`
`

`

`Case: 1:21-cv-00482 Document #: 1-2 Filed: 01/27/21 Page 10 of 17 PageID #:31
`
`U.S. Patent
`
`Feb. 20, 2007
`
`Sheet 8 of 8
`
`US 7,181.237 B2
`
`
`
`AIT WLMMAER
`5
`4.
`MESSAéE TyPEF
`AOTOOOL D56A7AMTWATOR
`
`WFORAMATOW ELEMMENTS
`"MMAWDATORy" FIXED LENeTH
`
`INFORMATIOWELEMEWTs
`"MMAWDATORy" /AARIAALE LAMeTy
`
`TNFORMATIOWELEMEWTs
`"OPTIOWAL" AIXED LEWeTH
`
`IMFORAMATOWELEMENTS
`''OptOWAL" VaAAALA LEWeTA/
`
`AT6.. 9
`
`

`

`Case: 1:21-cv-00482 Document #: 1-2 Filed: 01/27/21 Page 11 of 17 PageID #:32
`
`10
`
`15
`
`25
`
`30
`
`40
`
`1.
`CONTROL OF A MULTI-MODE,
`MULTI-BAND MOBILE TELEPHONE VIA A
`SINGLE HARDWARE AND SOFTWARE MAN
`MACHINE INTERFACE
`BACKGROUND OF THE INVENTION
`The present invention relates generally to mobile tele
`phones, and more specifically to a system for controlling a
`multi-mode, multi-band mobile telephone via a single hard
`ware and software man machine interface (MMI).
`Mobile telephone air interface standards such as Telecom
`munications Industry Association/Electronics Industry Alli
`ance Interim Standards 54 and 136 (TIA/EIA54 and TIA/
`EIA-136), Global System for Mobile communication
`(GSM), Advanced Mobile Phone Service (AMPS), Tele
`communications Industry Association Code Division Mul
`tiple Access Interim Standard 95 (CDMA IS-95 or CDMA),
`GSM/ANSI-41 Interoperability Trial Standard TIA/EIA-41
`(GAIT), and the like require Support by specific operating
`systems or protocol stacks, each presenting a functionality
`specific to the corresponding standard and the technologies
`applied within those standards. This functionality finds its
`final representation in the MMI software employed by the
`telephone, which presents the functionality to the user.
`Different scopes of functionality typically induce different
`behavior, and often require the use of different software in
`the MMI. Where such specific software is used for different
`standards or modes, specific hardware (e.g. specific hard
`keys, displays, and the like) may be required. Alternately,
`redundant MMI software may be provided, increasing the
`need for added general hardware (e.g. memory, processors,
`and the like) and increasing complexity to the user. More
`over, since mobile telephones are increasingly providing
`MMIS providing applications such as organizers, email
`35
`clients, Internet browsers, and the like, such MMIs can
`occupy a substantial portion of the telephone's memory
`compared with other of the telephone's software modules.
`Thus, in order to provide a multiple mode mobile telephone
`capable using multiple standards, a Substantial portion of the
`telephone's memory must be dedicated to storage of Soft
`ware providing multiple MMIs. Further, it is normally
`desirable that only one instance of a particular application be
`provided by the MMI of the telephone.
`Consequently, it is desirable to provide a mobile tele
`phone Supporting multiple air interface standards, each
`capable of Supporting multiple bands, through a single MMI.
`thus abstracting the complexity of the system from the user
`and enabling the use of a single hardware interface.
`SUMMARY OF THE INVENTION
`Accordingly, the present invention is directed to a system
`for controlling a multi-mode mobile telephone via a single
`hardware and software MMI (MMI). In exemplary embodi
`ments of the invention, the multi-mode mobile telephone is
`comprised of a hardware system and a software system. The
`hardware system includes at least one chipset and an inter
`face for controlling the mobile telephone. The software
`system includes a mode manager for managing Switching of
`the system between two or more modes utilizing different air
`interface standards Supported by different protocol stacks. A
`user interface communicates information and commands
`between the protocol stacks and a user. An application layer
`65
`reduces the functional interface between the protocol stacks
`to layers of the protocol stacks Subsequent to the user
`
`US 7,181,237 B2
`2
`interface, allowing control of the mobile telephone to be
`provided via a single MMI that is substantially consistent
`across the all modes.
`It is to be understood that both the foregoing general
`description and the following detailed description are exem
`plary and explanatory only and are not restrictive of the
`invention claimed. The accompanying drawings, which are
`incorporated in and constitute a part of the specification,
`illustrate an embodiment of the invention and together with
`the general description, serve to explain the principles of the
`invention.
`BRIEF DESCRIPTION OF THE DRAWINGS
`The numerous objects and advantages of the present
`invention may be better understood by those skilled in the art
`by reference to the accompanying figures in which:
`FIGS. 1A and 1B are block diagrams illustrating multi
`mode mobile telephones in accordance with exemplary
`embodiments of the present invention, wherein FIG. 1A
`illustrates a mobile telephone having a dual core and FIG.
`1B illustrates a mobile telephone having a single core;
`FIGS. 2A and 2B are block illustrating exemplary system
`architectures for controlling multi-mode mobile telephones,
`Such as the dual and single core mobile telephones shown in
`FIGS. 1A and 1B, via a single hardware and software MMI;
`FIGS. 3A, 3B and 3C are block diagrams further illus
`trating the interface of software modules of the system
`architecture shown in FIG. 2A in accordance with exem
`plary embodiments of the present invention;
`FIG. 4 is a block diagram illustrating an exemplary MMI
`manager suitable for use within the system architectures
`shown in FIGS. 3A, 3B and 3C:
`FIG. 5 is a schematic diagram illustrating a menu screen
`of a user interface in accordance with the present invention,
`wherein the menu screen is suitable for allowing a user to
`select between network modes supported by the mobile
`telephone;
`FIG. 6 is a flow diagram illustrating a for switching
`between network modes supported by the mobile telephone:
`FIG. 7 is a block diagram illustrating an exemplary
`structure of a serial bridge Suitable for communicating data
`between hardware systems of the mobile telephone;
`FIG. 8 is a block diagram illustrating layered functionality
`provided by the Open Systems Interconnect (OSI) model
`employed in the serial bridge structure shown in FIG. 7; and
`FIG. 9 is a schematic diagram illustrating an exemplary
`inter-processor communication (IPC) message format in
`accordance with an exemplary embodiment of the present
`invention.
`DETAILED DESCRIPTION OF THE
`INVENTION
`Reference will now be made in detail to the presently
`preferred embodiments of the invention, examples of which
`are illustrated in the accompanying drawings.
`FIGS. 1A and 1B illustrate mobile telephones in accor
`dance with exemplary embodiments of the present inven
`tion. Mobile telephones 100 & 110 support dual mode
`operation wherein each mode employs a different air inter
`face standard. In FIG. 1A, mobile telephone 100 comprises
`a dual-core mobile telephone capable of Supporting the
`Global System for Mobile communication (GSM) and Tele
`communications Industry Association/Electronics Industry
`Alliance Interim Standard 136 (TIA/EIA-136) (TDMA) air
`interface standards via mobile station software (MSSW)
`
`45
`
`50
`
`55
`
`60
`
`

`

`Case: 1:21-cv-00482 Document #: 1-2 Filed: 01/27/21 Page 12 of 17 PageID #:33
`
`10
`
`15
`
`25
`
`30
`
`35
`
`US 7,181,237 B2
`3
`4
`protocol stacks running on separate independent hardware
`may be different grades of integration between technologies
`employed (e.g., an integrated baseband chipset and two
`systems or chipsets 112 & 114. In FIG. 1B, on the other
`hand, mobile telephone 110 comprises a single-core mobile
`cores, or the like).
`Referring now to FIGS. 2A and 2B, exemplary software
`telephone having a common chipset 116 capable of Support
`architectures for mobile telephones 100 & 110 shown in
`ing both the GSM and TDMA protocol stacks.
`FIGS. 1A & 1B are described. Architecture 200, shown in
`Mobile telephones 100 & 110 may switch, or alternately,
`FIG. 2A is multiple-core (i.e., dual-core) while architecture
`be switched by the user, between a first mode (“GSM
`210, shown in FIG. 2B is single core. Both architectures are
`mode’) and a second mode (“TDMA mode’) for commu
`comprised of two or more MSSW protocol stacks supporting
`nication with wireless telephone networks employing either
`different air interface standards. For instance, in the embodi
`GSM or TDMA air interface standards. In the dual-core
`ments shown, architectures 200 & 210 include a first soft
`embodiment shown in FIG. 1A, mobile telephone 100
`ware system protocol stack (“MSSW SYSTEM (GSM)”)
`utilizes GSM protocol supported by the protocol stack
`212 supporting the GSM air interface standard and a second
`running on chipset 112 in the GSM mode. The chipset 114
`software system protocol stack (“MSSW SYSTEM
`on which the protocol stack supporting the TDMA air
`(TDMA)') 214 supporting the TDMA air interface standard.
`interface standard may be shut down completely since that
`In architecture 200 (FIG. 2A), each MSSW protocol stack
`212 & 214 is Supported by a core processing system (e.g.,
`protocol stack is not utilized. In the TDMA mode, mobile
`telephone 100 utilizes TDMA protocol supported by the
`“GSM CORE 216 and “TDMA CORE 218) and utilizes
`an operating system 220 & 222 appropriate to the processor
`protocol stack running on chipset 114. The processor of
`of the chipset employed (e.g., operating system 220 may be
`chipset 112 continues to control the MMI 118 of mobile
`a GSM Betriebs System (GBS) and operating system 222
`telephone 100 and any additional hardware related features
`may be a Nudeus+system). In exemplary embodiments,
`120 Such as battery measurement and charging, microphone
`GSM core 216 may include GSM Layers 1/2/3, a Subscriber
`Volume, loudspeaker Volume, control of address books
`Identity Module (SIM), or, alternately, User Identity Module
`memory, or the like. Thus, there is only one instance of the
`(UIM) card, a data services module for Supporting data
`MMI and database.
`services provided by the GSM air interface, and the like.
`As shown in FIG. 1A, chipsets 112 & 114 communicate
`TDMA core 218 may likewise include a suitable hardware
`with one another via a serial connection 122. In exemplary
`abstraction layer and associated control software for the
`embodiments of the invention, one or more processes run
`baseband processor employed. For instance, in one embodi
`ning within the mobile station software (MSSW) systems
`ment, TDMA core 218 may employ a PC3610 baseband
`running on each chipset 112 & 114 provide for transfer of
`processor manufactured by PrairieCom, Inc. employing
`man machine interface (MMI) related information. These
`Wireless Hardware Abstraction Layer (WHAL) software
`processes establish a communication channel between the
`and suitable control software. Each protocol stack 212 &
`GSM and TDMA protocol stacks allowing communication
`214 further includes suitable “housekeeping software mod
`there between for the display of TDMA call specific user
`ules 224 & 226 for providing system input/output (I/O),
`data by the display driver of the processor of chipset 112,
`service, and identification and security for interfacing the
`and for sending user requests from the processor of chipset
`MSSW protocol stacks 212 & 214 with components of the
`112 to the TDMA protocol stack of chipset 114. Chipset 112
`mobile telephone's hardware system 228.
`may further communicate data with an external source 124
`In architecture 210 (FIG. 2B), both MSSW protocol
`via serial connection 126. For instance, external source 124
`stacks 212 & 214 are Supported by a common core process
`may communicate software providing enhanced functional
`ing system (e.g., “GSM/TDMA CORE 230) using a suit
`ity (e.g. organizers, browsers, user interfaces, etc.), address
`able operating system 220. GSM/TDMA core 230 may
`book information, messages, email or the like.
`include GSM Layers 1/2/3, a Subscriber Identity Module
`In the single-core embodiment shown in FIG. 1B, both the
`(SIM), or, alternately, User Identity Module (UIM) card, a
`GSM protocol stack TDMA protocol stacks run on chipset
`data services module for Supporting data services provided
`116. Thus, serial connection 122 (FIG. 1A is not required.
`by the GSM air interface, and the like, and a suitable TDMA
`The processor of chipset 116 controls the MMI 118 and
`hardware abstraction layer and associated control software.
`Because protocol stacks 212 & 214 are supported by a
`additional hardware related features 120 of the mobile
`telephone 110 and provides communication of data with
`common core 230, only one housekeeping software module
`external source 124 via serial connection 126. However,
`232 is utilized for interfacing the MSSW protocol stacks 212
`there may be only one instance of the serial communication
`& 214 with components of the mobile telephone's hardware
`system 228.
`software or driver for serial connections 122 & 126.
`It will be appreciated that protocol stacks may be pro
`In accordance with the present invention, GSM MSSW
`vided for mobile telephones 100 & 110 that support air
`protocol stack 212 includes a user interface 234 for provid
`ing the software MMI for mobile telephone 100 (FIG. 1).
`interface standards other than GSM and TDMA. Such air
`55
`interface standards include Advanced Mobile Phone Service
`User interface 234 communicates information and com
`mands between the first and second protocol stacks and a
`(AMPS), Narrow Band AMPS (NAMPS), Digital AMPS
`(D-AMPS), Digital European Cordless Telephone System
`user via a hardware user interface. For instance, user inter
`face 234 may control display of command options by the
`(DECT), Telecommunications Industry Association Code
`display of the mobile telephone, display of messages (e.g.,
`Division Multiple Access Interim Standard 95 (CDMA
`60
`Short Message Service (SMS) messages), ring volume con
`IS-95 or CDMA), and the like. Further, while implementa
`trol, ring type control, acceptance of command from the
`tion of the present invention in a dual-mode mobile tele
`telephone keypad, and the like. In embodiments of the
`phone 100 is discussed herein in the description of FIG. 1A,
`it is contemplated that the present invention may also be
`invention, user interface 234 may include applications such
`utilized by multiple-mode telephones Supporting three or
`as organizers, electronic mail (email) clients, network (e.g.,
`more air interface standards without departing from the
`Internet) browsers, and the like. User interface 234 may
`Scope and spirit of the present invention. Additionally, there
`further provide for remote control of the mobile telephone,
`
`40
`
`45
`
`50
`
`65
`
`

`

`Case: 1:21-cv-00482 Document #: 1-2 Filed: 01/27/21 Page 13 of 17 PageID #:34
`
`10
`
`45
`
`US 7,181,237 B2
`6
`5
`for example, by the wireless communication network with
`library (“GLOBAL SUPPORT LIBRARY) 240 contains
`which the telephone is communicating.
`Software modules (e.g., math.c or the like) utilized in
`Application layer 236 reduces the functional interface
`different software entities of architectures 200 & 210.
`As shown in FIG. 2A, TDMA MSSW protocol stack 214
`between the first and second protocol stacks 212 & 214 to
`layers of the first and second protocol stacks Subsequent to
`may include a router 242 for routing information and
`messages within the TDMA protocol stack 214 and for
`the user interface (i.e., below user interface 234). In this
`manner, the differences in technologies employed by the
`routing messages from the TDMA protocol stack 214 to the
`different air interface standards are made substantially trans
`GSM MSSW protocol stack 212. This router 242 is not
`parent to the user of the mobile telephone. Further, by
`needed in single core architecture 210 (FIG. 2B).
`abstracting the functionality of the different air interface
`In dual core architecture 200 (FIG. 2A), a bridge 244 may
`be provided for enabling routing of information and mes
`standards to other levels of the respective protocol stacks
`212 & 214, applications (e.g., organizers, email clients,
`sages between GSM MSSW protocol stack 212 and TDMA
`network browsers, and the like) may be more easily added
`MSSW protocol stack 214 via serial connection 122 since
`protocol stacks 212 & 214 are running on different hardware
`to, removed from, or modified within the user interface 234
`systems, i.e., different chipsets 112 & 114 as shown in FIG.
`without modification of the different protocol stacks 212 &
`15
`214 So that the applications may support each air interface
`1A. Bridge 244 may include one or more processes 246 &
`248 running within each MSSW protocol stack 212 & 214
`standard without special modification. This greatly reduces
`the complexity of the MMI, making the mobile telephone
`which provide for transfer of MMI related information and
`easier to use than would be a telephone employing different
`GSM Layer 1 commands. Processes 246 & 248 establish a
`MMIs for each mode, or a telephone employing a MMI that
`communication channel between the GSM and TDMA pro
`is modified with redundant software for supporting both air
`tocol stacks 212 & 214 allowing communication there
`between for the display of TDMA call specific user infor
`interface standards. In this manner, the present invention
`mation, and for sending user requests from the GSM pro
`allows control of the mobile telephone to be provided via a
`single hardware and software MMI that is substantially
`tocol stack 212 to the TDMA protocol stack 214. Wherein
`the MSSW protocol stacks 212 & 214 are integrated into a
`consistent across all modes (e.g., across GSM and TDMA
`25
`single hardware system, as in single core architecture 210
`modes).
`Mode manager 238 manages Switching of mobile tele
`shown in FIG. 2B, bridge 244 is not required since messages
`may be routed directly to the appropriate protocol stack 212
`phone operation between air interfaces supported by MSSW
`protocol stacks 212 & 214. For example, in the embodiment
`or 214.
`shown, mode manager 238 controls Switching between a
`Referring now to FIGS. 3A, 3B and 3C, interfaces
`30
`first mode utilizing the GSM air interface standard supported
`between the mode manager 238 (FIG. 2A) to and from
`higher level modules of application layer 236 and user
`by first protocol stack 212 (“GSM mode”) and a second
`mode utilizing the TDMA air interface standard supported
`interface 234, and the lower level bridge 244 for a dual mode
`by a second protocol stack 214 (“TDMA mode'). Mode
`mobile telephone are described. In the architecture 300
`shown, the flow of messages for call-related functionality
`manager 238 may further include a routing mechanism
`35
`involves user interface (UI) 302, application layers includ
`(“Router) for routing of information and messages to the
`ing MSM application layer 304, GSM SMS application
`selected protocol stack 212 or 214, and a translator (“MMI
`layer 306, other application layers 308, and the GSM layers
`Manager) for translation of information between the dif
`ferent air interface standards, optionally, including mapping
`1/2/3310. Architecture 300 facilitates reading and writing of
`of differences in format of the parameters used by the
`call-related data to the CNI (Call Number Information) area
`different technologies and making adaptations for different
`of the GSM core 216 (FIG. 2A), and sending of messages
`handling of those parameters. Translation of information
`with associated structures between the various layers (e.g.,
`the user interface 302 to application layers 304,306, & 308
`between the different air interface standards may alternately
`be provided by application layer 236.
`and application layers 304,306 & 308 to GSM layer 1/2/3
`In FIGS. 2A and 2B, mode manager 238 is shown as being
`310). For TDMA air interface specification related func
`tions, MMI manager 312, which is functionally part of mode
`integrated in GSM MSSW protocol stack 212. However, it
`manager 238 (FIG. 2A), provides some functionality previ
`is contemplated that mode manager 238, which is preferably
`a single entity, may alternately be implemented as part of
`ously furnished by the GSM Layer 1/2/3 in GSM single
`mode telephones relating to reading and writing data to the
`TDMA MSSW protocol stack 214. Further, it will be appre
`ciated that in mobile telephones employing multiple core
`CNI as well as passing structures to and from the application
`architectures, mode manager 238 may be in implemented in
`layers. In exemplary embodiments of the invention, MMI
`any of the various protocol stacks Supporting a given stan
`manager 312 performs functional actions based on the
`message it is processing. Such actions include reading data
`dard.
`The Software system or protocol stack 212 Supporting
`from or writing data to the CNI and a corresponding TDMA
`structure, followed by sending of the appropriate message to
`mode manager 238 may control a database providing storage
`an application layer or the bridge.
`of all user relevant data for use by both software systems.
`Such user relevant data may include, but is not limited to,
`In the embodiment of architecture 300 shown in FIG. 3A,
`address book and phone book entries, short messages (e.g.,
`common MSM and SMS application layers 304 & 306 are
`an SMS message, or the like), emails, ringing tones, and
`employed for both GSM and TDMA modes instead of using
`pictures. Additionally, a second database may be provided
`separate TDMA MSM and SMS application layers, as in the
`for storing call-related data. In exemplary embodiments, this
`embodiments illustrated in FIGS. 3A and 3B. MMI Manager
`second database may be implemented as an entity with mode
`312 writes data to the CNI, and passes the current GSM
`structures to MSM and SMS application layers 304 & 306
`manager 238. However, Such a second database may be
`when calling the existing message passing functions imple
`implemented as multiple entities in each MSSW protocol
`stack 212 & 214, depending on the requirements of the
`mented in MSM application layer. The data written by the
`Software system design. The Software system or protocol
`MSM application layer to the CNI, and the structures that
`stack 212 Supporting mode manager 238 further include a
`are passed with those messages are not modified.
`
`40
`
`50
`
`55
`
`60
`
`65
`
`

`

`Case: 1:21-cv-00482 Document #: 1-2 Filed: 01/27/21 Page 14 of 17 PageID #:35
`
`10
`
`15
`
`US 7,181,237 B2
`8
`7
`and SMS application layers 320 & 324, provides mapping of
`Alternately, in the embodiments of architecture 300
`the data needed for call control and messaging features.
`shown in FIGS. 3B and 3C, reverse MSM messages from the
`Turning now to FIG. 4, an exemplary MMI Manager is
`user interface 302 (i.e., messages from GSM protocol stack
`described. MMI manager 400 may be logically divided into
`314 to TDMA protocol stack 316) may be directed to either
`two components 402 & 404: a first component 402 dealing
`the GSM MSM application layer 304 or a TDMA MSM
`with forward messages (i.e., messages from the GSM pro
`application layer 320 through a routing mechanism 322.
`tocol stack to the TDMA protocol stack), and a second
`Similarly, reverse SMS (Short Message Service) messages
`component 404 dealing with reverse messages (i.e., mes
`from MMI 302 are directed to either the GSM SMS appli
`sages from the TDMA protocol stack to the GSM protocol
`cation layer 304 or a TDMA SMS application layer 324 via
`stack). Each component 402 & 404 may have an interface to
`routing mechanism 322. Forward MSM messages from the
`and/or from one or more application layers and the bridge,
`MMI manager 312 (i.e., messages from TDMA protocol
`as well as facilities for translating information between
`stack 316 to GSM protocol stack 314) are sent to TDMA
`GSM and TDMA formats.
`MSM application layer 320, which communicates the mes
`The forward component of MMI manager 400 may fur
`sages to the user interface 302. Forward messages from the
`ther be divided into four sections 406-412. The first section
`GSM MSM application layer 306 are communicated directly
`406 provides a function interface serving as the link to the
`to the MMI 302.
`serial bridge. The first section 406 is called by the bridge to
`As shown in FIG. 3B, TDMA MSM application layer 320
`pass messages to MMI manager 400, passing the TDMA
`and TDMA SMS application layer 324 may further provide
`structure corresponding to Such messages. The second sec
`tion 408 processes forward messages based on the TDMA
`conversion of data between GSM and TDMA formats
`required by the respective GSM and TDMA system soft
`message structure passed to the function interface of first
`ware. For instance, wherein forward messages are passed
`section 406. The second section 408 may be implemented as
`from TDMA protocol stack 316 to GSM protocol stack 314,
`a function that, in turn, calls a second function correspond
`MMI manager 312 may call a function in TDMA MSM
`ing to the TDMA message passed. The third section 410
`application layer 320 and pass the TDMA data structure it
`provides implementation of the functions called by first and
`25
`receives from bridge 326, which in one embodiment may be
`second sections 406 & 408 for handling the forward mes
`a serial interface bridge between TDMA and GSM. The
`sages. Preferably, a unique function for each forward mes
`TDMA MSM application layer 320 then fills in fields in the
`sage may be implemented that will write data to the CNI and
`CNI based on data in this structure, and performs MSM
`assemble any relevant GSM structure based on data in the
`functionality. When reverse messages are passed from GSM
`TDMA structure passed to it. The fourth section 412 inter
`30
`protocol stack 314 to TDMA protocol stack 316, TDMA
`faces with the application layers. In exemplary embodi
`MSM application layer 320 converts data from the CNI to
`ments, the fourth section 412 calls functions in application
`assemble a TDMA structure. This structure is then passed
`layers appropriate for the GSM message passed.
`through a function interface to MMI manger 312. MMI
`The reverse component 404 of MMI manager 400 may
`manager 312 then sends the appropriate message corre
`similarly be divided into four sections 414–420. The first
`35
`sponding to the structure to bridge 326, which communi
`section 414 provides a function interface with upper appli
`cates the message to TDMAMMI manager 328 (i.e., router
`cation layers sending messages to the MMI manger 400. In
`242 (FIG. 2A)). TDMAMMI manager 328 then provides the
`exemplary embodiments, first section 414 is implemented as
`message to TDMA level 2/3330. Because mapping between
`a single function in MM