USOO83596.38B2
`
`(12) United States Patent
`Shaw
`
`(10) Patent No.:
`(45) Date of Patent:
`
`US 8,359,638 B2
`*Jan. 22, 2013
`
`(54) APPLICATION OF DYNAMIC PROFILESTO
`THE ALLOCATION AND CONFIGURATION
`OF NETWORK RESOURCES
`
`(75) Inventor: Venson M Shaw, Kirkland, WA (US)
`(73) Assignee: AT&T Mobility II LLC, Atlanta, GA
`(US)
`
`(*) Notice:
`
`Subject to any disclaimer, the term of this
`patent is extended or adjusted under 35
`U.S.C. 154(b) by 83 days.
`This patent is subject to a terminal dis-
`p
`claimer.
`
`(21) Appl. No.: 12/854,453
`(22) Filed:
`Aug. 11, 2010
`
`(65)
`
`Prior Publication Data
`US 2010/0323690 A1
`Dec. 23, 2010
`
`Related U.S. Application Data
`(63) Continuation of application No. 10/462.948, filed on
`Jun. 16, 2003, now Pat. No. 7,802,292.
`(60) Provisional application No. 60/446,129, filed on Feb.
`10, 2003.
`
`(51) Int. Cl.
`(2006.01)
`H04L 29/06
`(52) U.S. Cl. ............ 726/4; 380/247; 380/250; 709/225;
`709/226
`(58) Field of Classification Search ........................ None
`See application file for complete search history.
`
`(56)
`
`References Cited
`
`U.S. PATENT DOCUMENTS
`709,229
`6,088,732 A * 7, 2000 Smith etal
`723,909 B2 * 10/2006 Nakamura et al. .455.432.3
`7,802,292 B2 * 9/2010 Shaw ................................ T26/4
`2003/0167329 A1* 9, 2003 Kurakakeet al. ............. TO9,226
`* cited by examiner
`Primary Examiner — Kaveh Abrishamkar
`(74) Attorney, Agent, or Firm — Moazzam & Associates,
`LLC
`
`ABSTRACT
`(57)
`A service request is received and associated with a Subscriber
`id. Profile information is accessed for the source of the service
`request. A copy of the profile information is stored in a net
`work element employed by the source of the service request
`to access the network.
`
`20 Claims, 9 Drawing Sheets
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Receive service
`request
`902
`
`ASSOCiate
`Subscriber id With
`Service request
`904
`
`Locate Subscriber
`profile
`906
`
`Verify that
`requested service
`is available under
`Subscriber
`subscription plan
`908
`
`Locate Service
`profile
`910
`
`Compare Service requirements from
`service profile with network availability
`from network profile
`912
`
`
`
`
`
`
`
`
`
`Service requirements
`availabile in network?
`914
`
`
`
`Determine new Service
`requirements?
`916
`
`Y
`
`
`
`
`
`
`
`
`
`Allocate and
`configure network
`resources to respon
`d
`to service request
`918
`
`Configure terminal to
`receive Service
`920
`
`ERICSSON EXHIBIT 1009, Page 1
`
`

`

`U.S. Patent
`U.S. Patent
`
`Jan. 22, 2013
`
`Sheet 1 of 9
`
`US 8,359,638 B2
`US 8,359,638 B2
`
`OL
`
`L
`
`NI
`wt
`
`OQ
`co
`
`NS
`©
`
`©
`
`oS
`
`S
`
`>
`
`oO
`
`wco
`
`(0)
`
`(CC
`“a (FR
`9 OP
`2
`©
`=
`
`ERICSSON EXHIBIT 1009, Page 2
`
`28
`
`110
`
`a
`—!
`=
`
`a
`—
`S
`
`9
`oA
`N
`
`
`
`=
`—
`
`2
`_-
`—
`
`3
`
`mo
`
`=
`
`a
`
`
`
`c
`_ Ss
`ae
`EO
`oS
`~ £@
`Ers
`oO
`
`®
`:
`>
`e
`=
`
`=
`
`9
`ea}|%
`a &
`
`o +5
`
`>
`
`nN
`N
`
`
`
`.
`3
`
`S9o
`
`O
`
`ERICSSON EXHIBIT 1009, Page 2
`
`

`

`U.S. Patent
`
`Jan. 22, 2013
`
`Sheet 2 of 9
`
`US 8,359,638 B2
`
`
`
`
`
`
`
`Y
`CO
`
`%
`
`ERICSSON EXHIBIT 1009, Page 3
`
`

`

`U.S. Patent
`
`Jan. 22, 2013
`
`Sheet 3 of 9
`
`US 8,359,638 B2
`
`
`[Bula||SoyIsINbal-1S0qjeulwte|;IS!uonemnByuos.
`
`
`
`soysinbal-el¢sonyiqedeojeulwua|!suoOYyp!
`80WUeWEHeueWjeuUILUIS)/Loo-jeesBunes
`
`
`josjuoossao0epueAWWNoas
`
`
`seouajaudAJSAl|apBIDS
`UONBWJOJU]BOUBSAd|sesh|UOleWWOJUL
`SSeUIPeay
`
`UONELUJOJU!UCBO07
`ss9ooepueAjunoas
`
`
`
`jO4}U09
`
` ZOEJaq\osqns
`‘yIOMJauUSSadoY‘JueWAaaSpueBuljjig‘AJ@AI|9PSdIAJaS‘UOISIAOIdaalAas‘SiajolUesedJUaWAEY‘pI
`
`
`
`
`
`
`
`
`
`
`
`\Bd!AIASJoAyendIiI||III|1\I
`
`JUsWaJINDSsSOUBLUIOLSd
`
`sjuswauInbelso1Alas
`
`P|
`
`ed,
`
`uondusseg
`
`
`
`
`
`\uol}e}iuu!]SosnosalYIOMJSN
`
`
`
`
`
`judaWesINbaWOMENs.uNosay
`
`
`
`i|O1JUODsseazepueAWUNDeS
`
`
`
`
`
`SOUBMOJ/EJOINOSIYIOMJON
`
`
`
`uoneuojulabesp
`
`
`
`sisAjeuepual|soiyudeiBowag
`
`uonenossy
`
`UCI}EZHEUOSIAd
`
`
`
`90€
`
`ERICSSON EXHIBIT 1009, Page 4
`
`ERICSSON EXHIBIT 1009, Page 4
`
`
`

`

`U.S. Patent
`
`Jan. 22, 2013
`
`Sheet 4 of 9
`
`US 8,359,638 B2
`
`
`
`ERICSSON EXHIBIT 1009, Page 5
`
`

`

`U.S. Patent
`
`Jan. 22, 2013
`
`Sheet 5 of 9
`
`US 8,359,638 B2
`
`GS‘Sls
`
`Sseloy
`BulLUeOY 80SUOHEWOJU!
`Burweoy POSWOMISUHulleOsO}UOHeOYIUSpP!
`OLSUOHeWIOjUIajyosdSauc]syIomjoU
`
`
`
`
`UONBWJOJU!a]yoOsdyiomjeusysanbes
`
`
`
`BPIAD
`DUE0]Ss900eSEZLOYINEYIOMJSUBLUOH
`
`
`
`
`e]yo1dseplAoid
`
`ZOSYOMeuUHulLUBO!
`
`90S
`
`ERICSSON EXHIBIT 1009, Page 6
`
`ERICSSON EXHIBIT 1009, Page 6
`
`
`

`

`U.S. Patent
`
`Jan. 22, 2013
`
`Sheet 6 of 9
`
`US 8,359,638 B2
`
`
`
`
`
`
`
`
`
`ZOg edÅ? ?senbeu eolaues K??u ºp|
`
`
`
`
`
`
`
`ERICSSON EXHIBIT 1009, Page 7
`
`

`

`U.S. Patent
`
`Jan. 22, 2013
`
`Sheet 7 Of 9
`
`US 8,359,638 B2
`
`
`
`ERICSSON EXHIBIT 1009, Page 8
`
`

`

`U.S. Patent
`
`Jan. 22, 2013
`
`Sheet 8 of 9
`
`US 8,359,638 B2
`
`
`
`ERICSSON EXHIBIT 1009, Page 9
`
`

`

`U.S. Patent
`
`Jan. 22, 2013
`
`Sheet 9 of 9
`
`US 8,359,638 B2
`
`
`
`
`
`(sued)JSanbalBDIAIBS0}
`
`gl6
`
`
`
`SOIAIOSMOUSUILUE}EC]
`
`éEsquewenbe
`
`916
`
`
`
`S]OdyIOMJSUWO)
`
`zi6
`
`
`
`SJUSUGJINDOBdIAIBS
`
`
`
`EJOMJOUUlO'GBEAe
`
`vi
`
`
`
`WOMeUaunByU0s
`
`puee1eo0]ry
`
`Apuodsa0}seounosel
`
`
`
`BAIODEL6‘OlO}|BUILS}SuNnByuod
`
`SDIAIES
`
`026
`
`
`
`
`
`
`
`AIGefeAeyJompouYjeajyoudaarrnies
`
`
`
`WO)SJUSLUSIINDaedizuasaiedWwoy
`
`
`
`
`
`
`
`SO}AIaSsAlIsooy
`
`ysenbai
`
`206
`
`
`
`UJIMP|Jequosqns
`
`
`
`jsenba.saies
`
`sjelossy
`
`¥06
`
`
`
`Jaquosqns912907
`
`eyyold
`
`906
`
`
`
`aolwaspesenbe.
`
`
`
`JOPUNSIQEHEAESI
`
`yeu}AoA
`
`Jaquosqns
`
`upduojduosqns
`
`206
`
`
`
`BOIAIGSB}E507
`
`ayyoud
`
`O16
`
`ERICSSON EXHIBIT 1009, Page 10
`
`ERICSSON EXHIBIT 1009, Page 10
`
`
`
`
`
`
`
`
`
`
`
`
`

`

`US 8,359,638 B2
`
`2
`SUMMARY
`
`1.
`APPLICATION OF DYNAMIC PROFILESTO
`THE ALLOCATION AND CONFIGURATION
`OF NETWORK RESOURCES
`
`This application is a continuation of U.S. patent applica
`tion Ser. No. 10/462,948, filed Jun. 16, 2003, now U.S. Pat.
`No. 7.802,292, which claims priority to U.S. Provisional
`Patent Application Ser. No. 60/446,129, filed Feb. 10, 2003,
`the contents of which are hereby incorporated by reference
`herein in their entirety into this disclosure.
`
`10
`
`FIELD
`
`The invention relates to communications, and, more par
`ticularly, to communication via a network.
`
`15
`
`BACKGROUND
`
`In one embodiment, a method includes accessing profile
`information of a subscriber to identify services to which the
`Subscriber has access, Verifying that the Subscriber is autho
`rized to access a requested service, comparing requirements
`for delivering the service with available network resources,
`and, when sufficient network resources are available to
`deliver the service, allocating network resources in accor
`dance with the requirements for delivering the service.
`In another embodiment, a network includes an HLR com
`prising profile information for subscribers of the network, and
`an MSC comprising logic to access the profile information
`upon receiving a service request, and to identify a Subscriber
`that is the source of the service request, and to access the
`profile information to verify that the subscriber is authorized
`to receive a requested service, and to access from the HLR a
`service profile for the requested service and to allocate net
`work resources according to the service profile to deliver the
`service to a terminal of the subscriber.
`In another embodiment, a method includes detecting an
`error condition on a terminal device, accessing terminal infor
`mation for the terminal device, and applying the terminal
`information to remove the error condition.
`In another embodiment, a method includes receiving a
`service request, associating a Subscriber id with the service
`request, accessing profile information for the Source of the
`service request, and allocating network resources according
`to profile information for the source of the service request and
`profile information of the service requested.
`In another embodiment, a network element includes a
`router to route communications in a communication network,
`and logic access a service profile in response to a service
`request and to allocate network resources to fulfill the service
`request according to service requirements of the service pro
`file.
`
`FIGURES
`
`The invention may be better understood with reference to
`the following figures in light of the accompanying descrip
`tion. The present invention, however, is limited only by the
`Scope of the claims at the concluding portion of the specifi
`cation.
`FIG. 1 is a block diagram of an embodiment of a commu
`nication network.
`FIG. 2 is a block diagram of an embodiment of a commu
`nication network.
`FIG. 3 is a block diagram of an embodiment of profile
`information.
`FIG. 4 is a flow chart of an embodiment of a method to
`respond to a service request.
`FIG. 5 is a flow chart of an embodiment of a method to
`access profile information.
`FIG. 6 is a flow chart of an embodiment of a method to
`respond to a service request.
`FIG. 7 is a block diagram of an embodiment of a commu
`nication network.
`FIG. 8 is a block diagram of an embodiment of profile
`information distributed in a wireless communication net
`work.
`FIG. 9 is a flow chart of an embodiment of a method to
`respond to a service request.
`
`DESCRIPTION
`
`In the following description, references to “one embodi
`ment” or “an embodiment” do not necessarily refer to the
`
`25
`
`Wireless telephones are popular, ubiquitous devices. It is
`now possible to make and receive phone calls from almost
`any place in the world. Communication is even possible from
`remote and undeveloped areas using wireless satellite tele
`phones. Herein, the term wireless telephone refers to any
`device capable of transmitting and receiving voice and/or
`data (non-voice) information to and from a network without
`the use of wires, cables, or other tangible transmission media.
`So-called cellular telephones are a common example of wire
`less phones.
`Wireless telephones and the networks by which they com
`municate operate according to various technologies, includ
`30
`ing analog mobile phone service (AMPS), circuit Switching,
`packet switching, wireless local area network (WLAN) pro
`tocols, code division multiple access (CDMA), time division
`multiple access (TDMA), frequency-division multiplexing
`(FDM), spread-spectrum, global system for mobile commu
`35
`nications (GSM), high-speed circuit-switched data (HCSD),
`general packet radio system (GPRS), enhanced data GSM
`environment (EDGE), and universal mobile telecommunica
`tions service (UMTS). Of course, these are only examples,
`and other technologies may be employed in wireless commu
`40
`nication as well.
`Herein, the term 'wireless device is meant to include wire
`less telephones (including cellular, mobile, and satellite tele
`phones), and also to include a variety of other wireless
`devices, including wireless web-access telephones, automo
`bile, laptop, and desktop computers that communicate wire
`lessly, and wireless personal digital assistants (PDAs). In
`general, the term wireless device refers to any device with
`wireless communication capabilities.
`Many companies produce wireless telephones and other
`wireless devices. Among the more well-known producers are
`Nokia R, Ericsson(R), Motorola R, Panasonic(R), Palm R. Com
`puter, and Handspring R A variety of producers also provide
`wireless devices comprising versions of the Microsoft(R) Win
`dows(R operating Software.
`55
`Third generation (3G) wireless devices provide high-band
`width wireless access to communication networks. With such
`devices it may be possible to provide services to wireless
`devices such as streaming video, multimedia messaging, and
`so forth. Users of the network may, at different times, employ
`different devices to access the network. The quality and avail
`ability of services may vary according to the capabilities of
`the device employed for access (terminal device), the access
`device's present operating environment, and other dynamic
`parameters. The greater variety of services and terminal
`devices presents a challenge for allocating and managing
`network resources.
`
`45
`
`50
`
`60
`
`65
`
`ERICSSON EXHIBIT 1009, Page 11
`
`

`

`US 8,359,638 B2
`
`10
`
`15
`
`25
`
`35
`
`3
`same embodiment, although they may. In the figures, like
`numbers refer to like elements.
`Herein, “logic' refers to any information having the form
`of instruction signals and/or data that may be applied to affect
`the operation of a processing device. Examples of processing
`devices are computer processors (processing units), micro
`processors, digital signal processors, controllers and micro
`controllers, and so on. Logic may be formed from signals
`stored in a device memory. Software is one example of Such
`logic. Examples of device memories that may comprise logic
`include RAM (random access memory), flash memories,
`ROMS (read-only memories), EPROMS (erasable program
`mable read-only memories), and EEPROMS. Logic may also
`be comprised by digital and/or analog hardware circuits, for
`example, hardware circuits comprising logical AND, OR,
`XOR, NAND, NOR, and other logical operations. Logic may
`be formed from combinations of software and hardware.
`“Terminal device' refers to any device employed by a user
`(typically a person but also possibly an autonomous or semi
`autonomous device system) to access the network environ
`ment.
`“User” refers to any person (or, conceivably, autonomous
`or semi-autonomous logic) with access privileges to the net
`work. Typically the user is the operator of a terminal device,
`although a user could also be the operator of a device or
`devices that provide services via the network.
`A “subscriber' represents one or more persons or entities
`(corporations, partnerships, agents, operators, etc.) with
`access privileges to the network. A Subscriber may be or
`represent a single user, or may represent one or more users.
`30
`A “service provider' is any device or combination of
`devices that provides information via the network environ
`ment. Typically, a service provider provides information
`delivery to terminal devices, and/or performs network actions
`in response to requests from terminal devices. A service pro
`vider may also provide information delivery and/or network
`actions on behalf of another service provider.
`A 'service request' is a communication to the network to
`cause the network to perform one or more acts. Often, the
`service request involves a request for the network to commu
`40
`nicate information from or deliver information to a terminal
`device or service provider.
`A "network element' is any one or more devices of a
`communication network, e.g. devices that participate at least
`occasionally in the operation of the network.
`Typically, a Subscriber will enter into contractual arrange
`ments with a network operator for access rights to the opera
`tor's network(s). Networks of this operator for which the
`subscriber has access rights are the subscriber’s “home net
`works.” Networks other than the home networks of the sub
`scriber are “roaming networks.’
`FIG. 1 is a block diagram of an embodiment of a wireless
`network environment. A base station controller (BSC) 104
`network element is coupled to an antennae 108, typically via
`a Base Transceiver Station (BTS, not shown). The network
`may comprise multiple BSCs, each coupled with multiple
`BTSS and antennae. A single user may, at different times,
`access the network using a plurality of terminal devices. Such
`as a wireless telephone 133, a wireless personal digital assis
`tant (PDA) 135, and a wireless automotive computer (a pro
`cessor coupled to logic) within an automobile 137. The anten
`nae 108 may receive wireless signals from each of these
`devices.
`Different terminal devices may employ different wireless
`technologies to access the network. For example, a wireless
`telephone or automotive computer may employ analog
`mobile phone service (AMPS), circuit switching, packet
`
`45
`
`50
`
`55
`
`60
`
`65
`
`4
`switching, code division multiple access (CDMA), time divi
`sion multiple access (TDMA), frequency-division multiplex
`ing (FDM), spread-spectrum, global system for mobile com
`munications (GSM), high-speed circuit-switched data
`(HCSD), general packet radio system (GPRS), enhanced data
`GSM environment (EDGE), and/or universal mobile tele
`communications service (UMTS). APDA may employ wire
`less local area network (WLAN) and/or Bluetooth technol
`ogy (technology defined by the Bluetooth Special Interest
`Group, such as but not limited to versions of the Bluetooth
`Core Specification and addendums and revisions thereof).
`The BSC 104 is coupled to a mobile switching center
`(MSC) 116 network element that is responsible, among other
`things, for routing calls and communications to their appro
`priate destination. In GPRS networks, a Serving GPRS Sup
`port Node (SGSN) may perform functions similar to those
`provided by the MSC. Herein, the term “MSC' shall be used
`in reference to a mobile switching center, a serving GPRS
`Support Node, or any device or combination of devices per
`forming similar functions.
`Other components included in a typical MSC 116, such as
`memory, routing circuits, and various input/output devices,
`have been omitted for clarity of discussion. The MSC 116 is
`coupled to a terrestrial (non-wireless) communication net
`work 114 to enable, among other things, communication with
`wired devices such as home and business telephones. The
`MSC 116 is coupled by way of the terrestrial communication
`network 114 to a second wireless communication network
`comprising a second MSC 126. Each network may comprise
`multiple MSCs.
`A service provider 160 is coupled to MSC 116 to provide
`services such as streaming video, multimedia messaging (for
`example, to help enable the Multimedia Messaging Service,
`or MMS, which provides for the communication of video and
`other advanced multimedia formats), and so on. A similar
`service provider 142 is coupled to MSC 126.
`A Home Location Registry (HLR) 120 stores records (col
`lections of data) for Subscribers to the network comprising
`MSC 116. A second HLR128 performs a similar function for
`the network comprising MSC 126.
`The access privileges of a service provider may be obtained
`by way of paid Subscriptions (monthly fees, prepaid amounts,
`etc.) to the network operator. The access privileges may
`enable access to services available by way of the network. For
`example, a subscriber of the network comprising MSC 116
`may access the services of the service provider 160. In some
`embodiments, a Subscriber may also have access privileges to
`services of a roaming network. This may be accomplished in
`various ways, for example, by way of the Subscription plan to
`the subscriber's home network, or dynamically by way of a
`pay-as-you-go Scheme. For example, a Subscriber of the net
`work comprising MSC 116 may access the services of the
`service provider 142 on a pay-as-you-go transaction basis.
`When a device is roaming on the network (e.g. the user of
`the device is subscribed to a network other than the one that
`the device is accessing). Subscriber information for a user of
`the device may be stored in a Visitor Location Registry (VLR)
`122. The network comprising MSC 126 also comprises a
`VLR 110.
`In another embodiment, the subscriber information may be
`stored by a network element such as a Home Subscriber
`Server (HSS) that is shared by one or more networks of the
`network environment.
`An access control network element 144 controls access to
`the subscriberinformation stored by the HLR120. The access
`control 144 ensures that only those network elements of the
`network environment which are authorized to access the sub
`
`ERICSSON EXHIBIT 1009, Page 12
`
`

`

`US 8,359,638 B2
`
`15
`
`25
`
`30
`
`35
`
`40
`
`5
`scriber information may do so. In one embodiment access
`control is provided according to an id/password Scheme. The
`access control 144 is shown as a stand-alone network element
`for clarity of explanation. In practice, it may be a stand-alone
`device or functionally incorporated into one or more other
`network elements, such as the HLR 120.
`FIG. 2 is a block diagram of a wireless network wherein
`service requests originate from terminal devices, users, and
`service providers. A service request is a communication to the
`10
`network to cause the network to perform one or more acts. A
`terminal device 133 may originate a terminal service request
`(TSR), for example, in order to activate service so that the
`network recognizes and authorizes access by the terminal
`device 133. A user 141 of a terminal device 133 may originate
`a user service request (USR) in order to access a service
`(stock quotes, instant messaging, etc.) with the terminal
`device 133. A service provider 160 may originate a service
`provider service request (SSR) in order to access the services
`of another service provider. For example, in order to respond
`to a request to communicate a message including a video clip,
`a service provider to provide multi-media messaging may
`request the services of a streaming video provider.
`Some common types of network service requests are Sub
`Scription management service requests, multimedia messag
`ing service requests, and terminal management service
`requests. A Subscription management (SM) service request
`pertains to creating, updating, and maintaining a Subscriber's
`access privileges to the network. A multimedia messaging
`(MM) service request pertains to the communication of text,
`graphics, voice and non-voice audio, video, and other infor
`mation types. A terminal management (TM) service request
`pertains to errors involving the use and configuration ofter
`minal devices.
`Logic (e.g. Software) may be communicated from the net
`work to a memory of a terminal device. The logic may operate
`to enable the terminal device to better receive a service of the
`network. For example, some services such as instant messag
`ing may include a "client’ Software application that operates
`on the terminal device in cooperation with the service pro
`vider to enable instant messaging using the terminal device.
`Such software may not always operate properly on the termi
`nal device, producing errors due to incompatible configura
`tion of the terminal device, and resulting in a TM service
`request.
`Service providers and network elements may act to alter
`the configuration of the terminal device in order to remove the
`error condition. Information about the terminal device's con
`figuration and settings may assist in this process and may be
`stored by the network in a terminal profile.
`Information about a terminal device's configuration and
`settings may also enable the network operator to provide new
`services to the terminal device without involving the user in
`reconfiguration of the terminal device.
`55
`FIG. 3 is a block diagram illustrating an embodiment of
`subscriber, user, terminal, and service profiles. The subscriber
`profile comprises information about a Subscriber to a net
`work. A user profile comprises information about a user of the
`network. A terminal device profile comprises information
`about a terminal device. A service profile comprises informa
`tion about a service available via the network. Information of
`each type of profiles may be stored in a device memory, Such
`as a memory of an HLR or VLR, and/or in the memories of
`other network elements.
`In one embodiment, a subscriber profile 302 may comprise
`a Subscriberid, payment parameters, service provision infor
`
`45
`
`50
`
`60
`
`65
`
`6
`mation, service delivery information, billing and settlement
`information, access network information, and security and
`access control information.
`The subscriber id identifies a subscriber from among sub
`scribers to the network.
`Payment parameters describe the manner and terms of
`payment. Examples are monthly Subscription charges, flat
`fee arrangements, per-use arrangements, pre-paid amounts,
`and so on.
`Service provision information describes a level or package
`of services available to the subscriber. Examples are pre
`mium, standard, and basic.
`Service delivery information describes a level of service
`available to the subscriber from the network. Examples
`include 100Mbps (megabit per second) service, and guaran
`teed information delivery.
`Billing information describes how the subscriber is to be
`charged. This information may include the subscriber's bill
`ing address, credit or debit card information, and/or account
`numbers.
`Settlement information describes information about cur
`rent charges to the Subscriber. Examples include information
`about the Subscriber's current charges, and due and past-due
`charges.
`Access network information describes the manners of net
`work access the Subscriber may employ. Examples include
`GPRS, 2G, 3G, and circuit switching.
`Security information describes how the subscriber may
`protect information communicated to or from the network.
`Examples are digital signature and encryption key informa
`tion.
`Access control information describes how the subscriber
`may access information and/or acts available via the network.
`Examples include id and password information.
`In one embodiment, a subscriber profile 302 may be asso
`ciated with one or more user profiles 304. For example, a
`subscriber may represent multiple users when the subscriber
`is a corporation, partnership or other legal entity. The profile
`of such a subscriber may be associated with multiple user
`profiles, each representing a user represented by the Sub
`scriber. A subscriber profile 302 may also be associated with
`no user profiles, as when the subscriber is a service provider.
`However, in some cases even when the subscriber is a service
`provider, a user profile representing an operator of the service
`provider may be associated with the subscriber profile 302.
`In one embodiment, a user profile of the user profiles 304
`may comprise a user id, media delivery preferences, presence
`information, usage information, demographic information,
`association information, and personalization information.
`The user id identifies a user from among users of the
`network.
`Media delivery preferences include information about the
`manner in which information should be communicated to the
`user. Examples include frame rate, color schemes, visual
`quality, and visual layout.
`Usage information comprises information about the user's
`access to the network environment, possibly including how,
`when, how often, and for what purpose the user accessed the
`network environment.
`Usage information may include information about which
`services a user accesses and/or how often, and/or the most
`recently used and/or most frequently accessed services. The
`usage information may also comprise information about
`trends and patterns in the users usage behavior. In one
`embodiment, this information or portions thereof is collected
`by the MSC 116 associated with the HLR 120. Where an HSS
`or other central storage location is employed by multiple
`
`ERICSSON EXHIBIT 1009, Page 13
`
`

`

`US 8,359,638 B2
`
`10
`
`15
`
`25
`
`35
`
`40
`
`7
`networks, multiple MSCs may contribute to collection and
`storage of the usage information for terminals and/or users,
`and access control may be provided according to which MSC
`collected the information, and/or which MSC is comprised by
`a home network for the user and/or terminal.
`Personal information describes a user. Examples are the
`user's name and address, as well as a user's privacy informa
`tion (such as restrictions on distribution of the user profile
`information).
`Demographic information may be used to classify a user
`for statistical, marketing, or other purposes. Examples
`include the users age, race, and gender.
`Association information describes other users and/or Sub
`scribers that have an association with the user. The associa
`tion information may also describe the nature of the associa
`tion. Examples include associates, family members, and
`patrons.
`Personalization information describes a user's preferred,
`most recent, and/or most frequent settings for services that the
`user may access. Examples include a user's preferred type of
`news information (sports, local events, etc.) and a user's most
`frequent and/or most recent search queries.
`Security information describes how the user may protect
`information communicated to or from the network. Examples
`are digital signature and encryption key information. In vari
`ous embodiments the subscriber security information may be
`applied to protect the communications of the users associated
`with the subscriber. Alternatively, or in addition, the user
`security information may be applied to protect the commu
`nications of the users associated with the Subscriber, indepen
`30
`dent of one another.
`Access control information describes how the user may
`access information and/or acts available via the network.
`Examples include id and password information. In various
`embodiments the Subscriber access information may be
`applied to provide the users associated with the subscriber
`access to restricted information. Alternatively, or in addition,
`the user access control information may be applied to provide
`the users associated with the Subscriberindependent access to
`the restricted information.
`Each user profile may have Zero or more associated termi
`nal profiles 306. When the user represents an operator of a
`service provider, there may be no associated terminal profile.
`In one embodiment, a terminal profile may comprise a
`terminal identifier, terminal capabilities, readiness informa
`tion, presence information, location information, terminal
`configuration information, terminal settings, and security and
`access control information.
`The terminal identifier identifies the terminal from among
`terminals that access the network. Examples of Such identi
`fiers are the Mobile Identification Number (MIN), the Mobile
`Station Identifier (MSID), Mobile Station Number (MSN),
`and International Mobile Station Identifier (IMSI).
`Terminal capabilities comprises information about the ter
`minal device's capabilities to receive, process, and display
`55
`information. For example, terminal capabilities may com
`prise information about the terminals graphic display capa
`bilities, communication bandwidth, and processor speed.
`Readiness information comprises information about the
`terminal device's readiness to receive information from the
`network, for example, if the device is ready, not ready, sleep
`ing, on standby, and so on.
`Presence information comprises information about
`whether or not the user of the terminal device is currently
`present to operate and/or receive information via the terminal
`device. The readiness information and the presence informa
`tion together may establish whether the terminal equipment is
`
`45
`
`50
`
`60
`
`65
`
`8
`ready to receive, process, and display information, and
`whether the user of the terminal device is present to operate
`and/or receive information via the terminal.
`Location information comprises information about the
`location of the device. Such information may be useful in
`determining the type of information to deliver, the quality and
`quantity of information to deliver, and so on. Location infor
`mation may be literal, e.g. a geographic address or location,
`or logical, e.g. “In a Meeting”, “In Transit, and so on.
`Terminal configuration information may include informa
`tion about the terminal device model, the version(s) of logic
`comprised by the terminal device (e.g. BIOS version, oper
`ating system version, etc.), the last know error to occur during
`the operation of the device, installed Software applications,
`and language settings, among other things.
`Terminal settings may comprise information about how the
`BIOS, operating system, installed software applications, and
`other components of the terminal device are configured to
`operate.
`Security information describes how the terminal may pro
`tect information communicated to or from the network.
`Examples are digital signature and encryption key informa
`tion. In various embodiments the subscriber security infor
`mation and/or the user security information may be applied to
`protect the communications of the terminals associated with
`the subscriber and user. Alternatively, or in addition, the ter
`minal Security information may be applied to protect the
`communications of the terminals associated with a user inde
`pendently of one another.
`Access control information describes how the terminal
`may access information and/or acts available via the network
`to which access is controlled. Examples include id and pass
`word information. In various embodiments the subscriber
`access control information and/or user access control infor
`mation may be applied to provide the terminals associated
`with a user access to restricted information. Alternatively, or
`in addition, the terminal access control information may be
`applied to pro