WO1999027723A1 - Multiple subscriber service profiles per mobile station in a cellular communications system - Google Patents

Multiple subscriber service profiles per mobile station in a cellular communications system Download PDF

Info

Publication number
WO1999027723A1
WO1999027723A1 PCT/SE1998/002111 SE9802111W WO9927723A1 WO 1999027723 A1 WO1999027723 A1 WO 1999027723A1 SE 9802111 W SE9802111 W SE 9802111W WO 9927723 A1 WO9927723 A1 WO 9927723A1
Authority
WO
WIPO (PCT)
Prior art keywords
service
plural
service profiles
call
profiles
Prior art date
Application number
PCT/SE1998/002111
Other languages
French (fr)
Inventor
Binh Nguyen
James Murray
Andre Poulin
Angelo Ioculano
John Stroud
Original Assignee
Telefonaktiebolaget Lm Ericsson (Publ)
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Telefonaktiebolaget Lm Ericsson (Publ) filed Critical Telefonaktiebolaget Lm Ericsson (Publ)
Priority to BR9815427-3A priority Critical patent/BR9815427A/en
Priority to AU13577/99A priority patent/AU1357799A/en
Priority to CA002311367A priority patent/CA2311367A1/en
Publication of WO1999027723A1 publication Critical patent/WO1999027723A1/en

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/24Accounting or billing
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M15/00Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M15/00Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/44Augmented, consolidated or itemized billing statement or bill presentation
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M15/00Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/49Connection to several service providers
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M2215/00Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/01Details of billing arrangements
    • H04M2215/0104Augmented, consolidated or itemised billing statement, e.g. additional billing information, bill presentation, layout, format, e-mail, fax, printout, itemised bill per service or per account, cumulative billing, consolidated billing
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M2215/00Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/32Involving wireless systems
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M2215/00Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/46Connection to several service providers
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W8/00Network data management
    • H04W8/18Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W8/00Network data management
    • H04W8/18Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
    • H04W8/20Transfer of user or subscriber data
    • H04W8/205Transfer to or from user equipment or user record carrier

Definitions

  • the present invention relates to cellular communications systems and, in particular, to the maintaining of multiple subscriber service profiles for a given mobile station operating within a cellular communications system.
  • Description of Related Art In a conventional cellular communications system, a one-to-one relationship is typically maintained between the mobile station and the subscription for that mobile station.
  • the "subscription" refers to the contract entered into by a user (also referred to as the "subscriber") with a cellular service provider.
  • the subscription defines not only to whom billing for cellular services should be charged, but also sets forth the particular types of cellular calling services and features that are to be provided to the subscriber.
  • this data is collected in a subscriber service profile that is stored and maintained in a database.
  • the service profile is linked in that database to an identification of the mobile station for the subscriber.
  • the conventional system also maintains a one-to-one relationship between each mobile station and the service profile that defines the cellular services and features provided to that mobile station.
  • a subscription for cellular service is associated with plural service profiles.
  • a one-to-many relationship is established between a mobile station and its associated subscription/service profiles.
  • Different billing statements for use of the same mobile station are then generated for each service profile to allow for segregated billing of service charges incurred for mobile station use.
  • the home location register (HLR) of the cellular network stores plural service profiles for such subscripted mobile stations. Each of the service profiles is associated with a different billing identification to allow service charges incurred for use of the single mobile station to be properly allocated between the different profiles.
  • the user selects in the mobile station (MS) a particular one of the profiles to be active. At each registration, an identification of this selected service profile is sent to the serving cellular network, and the selected service profile is down- loaded from the home location register. Alternatively, the user selects the active service profile to be down-loaded from the home location register by sending a feature code to the cellular network. Furthermore, selection of the active service profile for down-loading may be made by the network in accordance with a stored schedule maintained by the home location register.
  • Charging on a per service profile basis is made for both in-coming and outgoing calls.
  • appropriate toll tickets are generated by the network. These toll tickets identify not only the subscription for the mobile station involved in the call, but also the particular active one of the plural service profiles for that mobile station to which the service charges should be applied.
  • a billing center may segregate the billing of service charges incurred for mobile station use against each of the plural service profiles.
  • FIGURE 1 is a schematic diagram of a cellular telephone network of the present invention
  • FIGURE 2 is a node operation and signal flow diagram illustrating selection at mobile station registration between plural available service profiles
  • FIGURE 3 is a node operation and signal flow diagram illustrating selection using a feature code transmission between plural available service profiles
  • FIGURE 4 is anode operation and signal flow diagram illustrating selection according to a schedule between plural available service profiles
  • FIGURE 5 is a node operation and signal flow diagram illustrating a first embodiment for effectuating a call set up and delivery
  • FIGURE 6 is a node operation and signal flow diagram illustrating a second embodiment for effectuating a call set up and delivery
  • FIGURE 7 is a flow diagram illustrating handling of an outgoing call from a mobile station associated with plural service profiles
  • FIGURE 8 is a flow diagram illustrating handling of an incoming call to a mobile station associated with plural service profiles.
  • FIGURE 1 wherein there is shown a schematic diagram of a cellular telephone network 10 including a plurality of interconnected switching nodes (SN) 12. Although only two switching nodes 12 are shown, it will be understood that the network 10 likely includes many more interconnected nodes.
  • the first and second switching nodes 12(1) and 12(2) may comprise any one of a number of known telecommunications switching devices, including those commonly used and known in the art for providing either digital or analog cellular telephone service to a plurality of mobile stations (MS) 14.
  • MS mobile stations
  • the switching nodes 12 are interconnected with each other for communication via both voice trunks 18 (illustrated with broken lines) and signaling links 16 (illustrated with solid lines) providing a known ISUP (or Rl or R2) type connection.
  • the voice trunks 18 provide voice and data communications paths used to carry subscriber communications between the switching nodes 12.
  • the signaling links 16 carry command signals between the switching nodes 12. These signals may be used, for example, in setting up and tearing down voice and data communications links over the voice trunks 18 and controlling the provision of calling services to the mobile stations 14.
  • the switching nodes 12 are also connected to a home location register
  • the home location register 20 stores information relating to the mobile stations 14 and their subscriptions comprising location information and service profile information. In connection with the present invention, as will be described in more detail below, the home location register 20 in particular stores plural service profiles for at least one of the mobile stations.
  • the switching node 12 is further connected to at least one associated base station controller (BSC) 24 via both a signaling link 26 and a voice trunk 28. Only one base station controller 24 is shown connected to switching node 12(2) in order to simplify the illustration.
  • the voice trunk 28 provides a voice and data communications path used to carry subscriber communications between the second switching node 12(2) and its base station controller 24.
  • the signaling link 26 carries command signals between the node 12 and its associated base station controller 24.
  • the signaling link 26 and trunk 28 are collectively commonly referred to in the art as the "A interface".
  • the base station controller 24 is then connected to a plurality of base stations (BS) 30 which operate to effectuate radio frequency communications with proximately located mobile stations 14 over an air interface 32.
  • the base station controller 24 functions in a well known manner to control this radio frequency communications operation.
  • the switching node 12(1) is further connected to a plurality of base stations (BS) 30 which operate to effectuate radio frequency communications with proximately located mobile stations 14 over the air interface 32.
  • BS base stations
  • the functionality provided by the base station controller 24 is instead provided by the switching node 12(1).
  • FIGURE 1 Although direct communications links (signaling and/or trunk) are illustrated in FIGURE 1, it is understood by those skilled in the art that the links are not necessarily direct between the illustrated nodes, and may instead pass through many other communications nodes (not shown) of the mobile network, and perhaps even utilize other communications networks (such as the public switched telephone network - PSTN). Illustration of the links in a "virtual" manner as shown in FIGURE 1 is therefore by way of simplification of the drawing and the communications relationship between the various included nodes within the network 10.
  • the home location register 20 For each cellular service subscription associated with a served mobile station 14, the home location register 20 stores service profile information 34 relating to cellular services and features subscripted to by the subscriber for that served mobile station. If conventional service is provided to a mobile station 14, the service profile information 34 associated with that mobile station subscription comprises a single service profile 36 per subscription. Conversely, and in accordance with the present invention, plural service profiles 38(n), where n>l, may comprise the service profile information 34 associated with a single mobile station 14. For mobile stations 14 having subscriptions that support plural service profiles 38(n), any one of those plural profiles may be selected, either by the system or by the subscriber (with some restrictions), for use at a specific time or in connection with a specific call.
  • a mobile station 14 When a mobile station 14 makes an initial registration with the system through a particular switching node 12, that switching node requests a subscriber service profile 36 or 38(n) relating to that mobile station, and its corresponding subscription, from the home location register 20.
  • This subscriber service profile 36 or 38(n) information is downloaded from the home location register 20 for storage in a visitor location register (VLR) 40 associated with the switching node 12.
  • VLR visitor location register
  • Service for both in-coming and out-going calls is then provided to the mobile station 14 by the serving switching node 12 in accordance with the downloaded service profile 36 or 38(n).
  • the subscriber enters a service profile selection code into the mobile station 14, and this selection information is conveyed by the serving switching node 12 to the home location register 20 at each registration.
  • the home location register 20 processes the selection information to identify the proper one of the n available service profiles 38(n) for the mobile station 14. This profile is then downloaded to the visitor location register 40.
  • the subscriber sends a feature code through the mobile station 14.
  • This feature code is indicative of the activation of a certain one of the n available service profiles 38(n) for the mobile station 14. Responsive to receipt of the feature code, the proper service profile
  • the home location register 20 In response to any subsequent registration of the mobile station, the home location register 20 automatically retrieves the active one of the service profiles 38(n) for a visitor location register 40 download.
  • Deactivation of the currently activated service profile occurs when the mobile station powers-off or when the mobile station has been idle for longer than a predetermined time period.
  • the selected service profile 38(n) continues to remain active until such time as a new selection is made through feature code entry.
  • the activation of a certain one of the n available service profiles 38(n) depends on a subscriber or service provider defined schedule 42 for the mobile station 14.
  • This schedule may, for example, designate that a business related one of the service profiles 38(n) be active during weekday business hours, while a personal related one of the service profiles be active at all other times.
  • the schedule may designate that a first employee related service profile 38(n) be active during a first weekday time shift, a second employee related service profile be active during a second weekday time shift, a third employee related service profile be active during a third weekday time shift, and that no service profile be active on weekends.
  • the home location register 20 identifies (based on the schedule 42) the proper active one of the n available service profiles 38(n) for the mobile station 14. This profile is then downloaded to the visitor location register 40.
  • a different billing identification 44(n) is provided for each of the n available service profiles 38(n) for the mobile station 14.
  • a billing center 46 for the service provider receives toll tickets (TTs) relating to calling charges, processes the toll tickets with respect to the mobile station and particular active service profile thereof, and then accordingly generates a separate billing statement for each identification 44(n) effectively allocating cellular service costs properly among various usages and subscribers.
  • TTs toll tickets
  • a business service profile 38(n) and personal service profile are provided for a single mobile station 14
  • one business billing statement and one personal billing statement are generated by the billing center 46. This allows the subscriber to account between business and personal calling expenses.
  • each toll ticket generated by the network 10 during a call and communicated to the billing center 46 must included information identifying the mobile station/subscription at issue, and further include information identifying, or allowing the billing center to identify, the particular one of the service profiles 38(n) that is active for the call.
  • each of the plural service profiles 38(n) may be associated with a different directory number.
  • a single mobile station may also be accessed by a caller through the dialing of any one of a number of different directory numbers.
  • This allows each one of a number of potential users of the mobile station to have a unique telephone directory number for in-coming calls.
  • a number of billing options are available.
  • an in-coming call dialed to a certain directory number may be delivered to the mobile station regardless of whether the service profile associated with that number is currently active. Billing is made either to the service profile for the called number, or the service profile that is currently active.
  • FIGURE 2 wherein there is shown a node operation and signal flow diagram illustrating selection at mobile station registration between plural available service profiles.
  • the subscriber selects (action 200) a particular one of plural available service profiles 38(n) for use by making an appropriate entry into the mobile station 14. This selection is stored (action 202) by the mobile station.
  • the mobile station 14 then makes a registration with the cellular telephone network by transmitting a registration message 204 to the serving switching node 12 through the serving base station 30 (and perhaps the serving base station controller 24).
  • This registration message 204 includes information, perhaps stored in an included parameter, identifying the subscriber selected one of plural available service profiles 38(n).
  • the switching node 12 sends a registration notification message 206 to the home location register 20 through the visitor location register 40 requesting the selected one of the service profiles 38(n) associated with the registering mobile station 14.
  • the home location register 20 retrieves the selected one of the service profiles 38(n), and sends that information in message 208 back for storage (action 210) in the visitor location register 40 associated with the requesting switching node 12.
  • In-coming and outgoing calling service is thereafter provided to the mobile station in accordance with the down-loaded service profile. If desired, the selected 200 service profile remains active until the mobile station has been idle for longer than a predetermined time period (action 212).
  • FIGURE 3 wherein there is shown a node operation and signal flow diagram illustrating selection using a feature code transmission between plural available service profiles.
  • a feature request is dialed (action 220) by a subscriber into their mobile station 14. This feature request (perhaps in the form of an appropriately formatted star code) identifies a subscriber selected one of plural available service profiles 38(n) for activation, and may further present a personal identification number (PIN) indicating authorization for the selection.
  • PIN personal identification number
  • the switching node 12 sends a feature request message 224, including the dialed feature code, to the home location register 20.
  • the home location register 20 processes the message 224 to determine whether the subscriber is authorized to use the feature (action 226), and if so, what actions need to be taken in response to the request (action 228) and what instructions, if any, need to be presented to the mobile switching center to effectuate the feature (action 230).
  • the home location register 20 marks the subscriber selected one of plural available service profiles 38(n) as being active.
  • a feature request return result message 232 confirming activation of the selected service profile 38(n), is then sent by the home location register 20 back to the mobile station 14 through the switching node 12.
  • the home location register 20 also retrieves the selected one of the service profiles 38(n), and sends that information in message 234 back for storage (action 236) in the visitor location register 40 associated with the switching node 12. In-coming and out-going calling service is thereafter provided to the mobile station in accordance with the downloaded service profile.
  • a subscriber selected one of plural available service profiles 38(n) has been marked as being active, it remains active until the mobile station powers-off 5 (action 238), the mobile station has been idle for longer than a predetermined time period (action 240), or a new selection is made by the subscriber through feature code entry (action 220).
  • the feature code entry (action 220) may alternatively simply de-activate the currently active service profile (taken in actions 228), with activation of a service profile requiring the entry of another feature code.
  • the mobile station 14 makes a registration with the cellular telephone network by transmitting a registration message 242 to the serving switching node 12 through the serving base station 30 (and perhaps the serving base station controller 24). Responsive thereto, the switching node 12 sends a 5 registration notification message 244 to the home location register 20 through the visitor location register 40 requesting the currently active one of the service profiles 38(n) associated with the registering mobile station 14. The home location register 20 retrieves the active one of the service profiles 38(n), and sends that information in message 246 back for storage (action 248) in the visitor location register 40 associated with the requesting switching node 12. In the event that none of the service profiles 38(n) is currently active, the home location register 20 returns a registration denied message 250 back the switching node 12.
  • the reason for denial is conveyed to the mobile station in message 252.
  • This prompts the subscriber to activate one of the plural service profiles 38(n) through feature code entry (action 220), resulting in a down-loading of the selected one of the service profiles 38(n) in message 234 for storage (action 236) in the visitor location register 40 associated with the switching node 12.
  • FIGURE 4 wherein there is shown a node operation and signal flow diagram illustrating selection according to a schedule between plural available service profiles.
  • a schedule 42 designating the activation periods for each of plural available service profiles 38(n) of a mobile station 14 is stored (action 260) in the home location register 20.
  • the schedule 42 may be either service provider or subscriber defined.
  • the mobile station 14 subsequently makes a registration with the cellular telephone network by transmitting a registration message 262 to the serving switching node 12 through the serving base station 30 (and perhaps the serving base station controller 24).
  • the switching node 12 sends a registration notification message 264 to the home location register 20 through the visitor location register 40 requesting the schedule 42 defined active one of the service profiles 38(n) associated with the registering mobile station 14.
  • the home location register 20 retrieves the service profile 38(n) identified by the schedule as being active, and sends that information in message 266 back for storage (action 268) in the visitor location register 40 associated with the requesting switching node 12. In-coming and out-going calling service is thereafter provided to the mobile station in accordance with the down-loaded service profile.
  • the cellular telephone network 10 is preferably implemented as a wireless intelligent network (IN) and thus further includes at least one service control point (SCP) 48.
  • the switching nodes 12 also referred to as service switching points (SSPs) in this configuration
  • SSPs service switching points
  • MAP Mobile Application Part
  • INP Intelligent Network Application Part
  • INP Intelligent Network Application Part
  • the home location register 20 is preferably implemented in conjunction with the service control point 48.
  • the service control point 48 provides a centralized processing platform for implementing the "intelligence" of the network 10.
  • this intelligence comprises the administration over the plural service profiles 38(n) available to certain ones of the mobile stations 14.
  • This administration primarily involves the operations described herein for selecting which one of the service profiles 38(n) is to be active at any one time (either in response to subscriber selection, feature code selection, or scheduling selection).
  • a separate combined service switching point/service control point (SSP/SCP or SSCP) 50 is provided for handling of calls implicating multiple service profile 38(n) selection.
  • This combined service switching point/service control point 50 is connected to the switching nodes 12 via both voice trunks 18 (illustrated with broken lines) and signaling links 16 (illustrated with solid lines) providing a known ISUP (or Rl or R2) type connection, and is connected to the home location register by means of the signaling links 22 which utilize protocols such as Mobile Application Part (MAP), IS-41, Intelligent Network Application
  • MAP Mobile Application Part
  • IS-41 Intelligent Network Application
  • FIGURE 5 wherein there is shown a node operation and signal flow diagram illustrating a first embodiment for effectuating a call set up and delivery.
  • a call 300 dialed to the directory number (B-number) of a mobile station 14 originates from another cellular subscriber or the public switched telephone network (PSTN), and is received at a first (originating or gateway) switching node 12(1).
  • the originating switching node 12(1) determines whether the calling party is entitled to receive any intelligent network services (action 302).
  • One such service may comprise the plural service profile 38(n) service of the present invention. If so, the originating switching node 12(1) sends an originating access message 304 to the home location register 20 (service control point 48). This message 304 requests an identification of each intelligent network service to which either the calling party is entitled. The list of such services (including, for example, the plural service profile 38(n) service) is returned to the originating switching node 12(1) in message 306. The identified services in the returned list are then evaluated and organized (action 308) for implementation in connection with the call 300.
  • the call is routed 310 to the particular combined service switching point/service control point 50 supporting that service (assuming the home location register 20 cannot provide all necessary support, including billing).
  • the combined service switching point/service control point 50 has knowledge (perhaps down-loaded from, or accessed from the home location register 20) of the plural service profiles 38(n) associated with the calling/called party.
  • the active one of the plural service profiles 38(n) is then implemented (action 312) in connection with the call, and a toll ticket for billing is generated 314 specifically identifying the active profile of a given subscription be charged.
  • the call is then routed 316 back to the originating switching node 12(1).
  • the call leg routings are then routed 316 back to the originating switching node 12(1).
  • 310 and 316 may be dropped (if desired), as generally indicated with "X" markings, from the call 300 once generation 314 of the toll ticket associating the call with the proper service profile is completed.
  • Another toll ticket for billing is then generated 318 by the originating switching node 12(1) identifying that the given subscription be charged.
  • These toll tickets are processed by the billing center 46 to generate a charge for the call, with that charge being assessed against the currently active one of the service profiles 38(n) of the calling party subscription.
  • the billing information relating to the active service profile 38(n) is sent to the originating switching node 12(1) to be included in its generated 318 toll ticket, thus obviating the need for a separate toll ticket generated 314 by the service switching point/service control point 50.
  • the originating switching node 12(1) interrogates the home location register 20 with a location request (send routing) message 320.
  • the location request (send routing) message 320 is processed by the home location register 20 to determine the location (i.e., second or serving switching node 12(2)) within the cellular network 10 of the called mobile station 14. Responsive to this interrogation, the home location register 20 messages the serving switching node 12(2) for the called mobile station 14 with a routing request (provide roaming) message 322 to prepare for the call.
  • the serving switching node 12(2) determines in action 324, to some selected degree of granularity, the location (for example, location area) of the called mobile station 14. This location may be identified, for example, based on information resulting from a most recent registration (not shown) of the called mobile station 14 as stored in the visitor location register (not shown) associated with the serving switching node 12(2). Alternatively, the serving switching node 12(2) may page (not shown) the called mobile station 14, and process the page response (not shown) to make a more precise location determination. In accordance with this determined location, the serving switching node 12(2) selects in action 326 an appropriate routing number (for example, a temporary location directory number (TLDN) or a roaming number) for that location.
  • TLDN temporary location directory number
  • the routing number is selected from a plurality of such numbers associated with the serving switching node 12(2).
  • the selected routing number is then returned 328 to the originating switching node 12(1) via the home location register 20.
  • the incoming call is then delivered (through connected) 330 to the serving switching node 12(2) using the routing number for attempted completion to the called mobile station 14.
  • Completion of the call involves further routing 332 the incoming call to the currently serving base station 30 (perhaps through the base station controller 24), and then to the called mobile station 14 over the air interface 32.
  • the serving switching node 12(2) handles the call in accordance with the down-loaded, visitor location register stored, service profile of the called mobile station.
  • this down-loaded service profile may comprise one of a number of service profiles 38(n) assigned to the called mobile station 14 subscriber and currently designated as active (see, FIGURES 2, 3 and 4).
  • a toll ticket (TT) is accordingly generated (action 334) against the active one of the service profiles for the called mobile station.
  • Toll ticket processing enables the billing center 46 to properly generate a charge for the call, with that charge being assessed against the currently active one of the service profiles 38(n) of the called party subscription.
  • FIGURE 6 wherein there is shown a node operation and signal flow diagram illustrating a second embodiment for effectuating a call set up and delivery.
  • B-number of a mobile station 14 originates from another cellular subscriber or the public switched telephone network (PSTN), and is received at a first (originating or gateway) switching node 12(1).
  • the originating switching node 12(1) determines whether the calling party is entitled to receive any intelligent network services (action 302).
  • One such service may comprise the plural service profile
  • the originating switching node 12(1) sends an originating access message 304 to the home location register 20 (service control point 48).
  • This message 304 requests an identification of each intelligent network service to which either the calling party is entitled.
  • the list of such services (including, for example, the plural service profile 38(n) service) is returned to the originating switching node 12(1) in message 306.
  • the identified services in the returned list are then evaluated and organized (action 308) for implementation in connection with the call 300.
  • Routing of the call to a service switching point/service control point 50 is not required in this embodiment as the home location register 20 (service control point 48) support all aspects (including billing) for the plural service profile 38(n) service of the present invention.
  • the active one of the plural service profiles 38(n) is then implemented (action 312') in connection with the call, and a toll ticket for billing is generated 314' specifically identifying that the specific active profile of a subscription be charged.
  • Another toll ticket for billing is then generated 318 by the originating switching node 12(1) identifying that the subscription be charged.
  • toll tickets are processed by the billing center 46 to generate a charge for the call, with that charge being assessed against the currently active one of the service profiles 38(n) of the identified calling party subscription.
  • the billing information relating to the active service profile 38(n) is sent to the originating switching node 12(1) to be included in its generated 318 toll ticket, thus obviating the need for a separate toll ticket generated 314' by the home location register 20.
  • the originating switching node 12(1) interrogates the home location register 20 with a location request (send routing) message 320.
  • the location request (send routing) message 320 is processed by the home location register 20 to determine the location (i.e., second or serving switching node 12(2)) within the cellular network 10 of the called mobile station 14. Responsive to this interrogation, the home location register 20 messages the serving switching node 12(2) for the called mobile station 14 with a routing request (provide roaming) message 322 to prepare for the call.
  • the serving switching node 12(2) determines in action 324, to some selected degree of granularity, the location (for example, location area) of the called mobile station 14.
  • This location may be identified, for example, based on information resulting from a most recent registration (not shown) of the called mobile station 14 as stored in the visitor location register (not shown) associated with the serving switching node 12(2).
  • the serving switching node 12(2) may page (not shown) the called mobile station 14, and process the page response (not shown) to make a more precise location determination.
  • the serving switching node 12(2) selects in action 326 an appropriate routing number (for example, a temporary location directory number (TLDN) or a roaming number) for that location.
  • TLDN temporary location directory number
  • the routing number is selected from a plurality of such numbers associated with the serving switching node 12(2).
  • the selected routing number is then returned 328 to the originating switching node 12(1) via the home location register 20.
  • the incoming call is then delivered (through connected)
  • Completion of the call involves further routing 332 the incoming call to the currently serving base station 30 (perhaps through the base station controller 24), and then to the called mobile station 14 over the air interface 32.
  • the serving switching node 12(2) handles the call in accordance with the down-loaded, visitor location register stored, service profile of the called mobile station. It is recognized that this down-loaded service profile may comprise one of a number of service profiles 38(n) assigned to the called mobile station 14 subscriber and currently designated as active (see, the process of FIGURES 2, 3 and 4).
  • a toll ticket (TT) is accordingly generated (action 334) against the active one of the service profiles for the called mobile station.
  • Toll ticket processing enables the billing center 46 to properly generate a charge for the call, with that charge being assessed against the currently active one of the service profiles 38(n) of the called party subscription.
  • FIGURE 7 wherein there is shown a flow diagram illustrating handling of an outgoing call from a mobile station associated with plural service profiles.
  • a call origination is received by the process.
  • This received call origination 100 includes an identification of digits dialed for an outgoing call and/or code dialings.
  • a determination is then made in step 102 as to whether the received call concerns a user designated and transmitted activation (feature) code. If yes, an appropriate action is taken in step 104 in response to the code.
  • the sent code may identify a subscriber selected one of plural available service profiles 38(n) for activation (see, FIGURE 3).
  • Other actions relevant to the plural service profile 38(n) service of the present invention and involving a feature code selection are presented below.
  • a specific feature code may be recognized that would prevent unauthorized entry of feature codes to specify certain actions and changes.
  • An appropriate confirming announcement with respect to the action (such as confirming the selection of a certain service profile) is then sent back to the mobile station in step 106, and the call is terminated. If no, a determination is then made in step 108 as to whether the received call concerns a user designated and transmitted escape code. This escape code signals the process to switch between available service profiles 38(n) for a current call only.
  • step 102 This differs from the activation code of step 102 where a semi-permanent switch of service profiles may be made. Accordingly, if yes, a toggle is set in step 110. Thereafter, or if no in step 108, a determination is made in step 114 as to whether a scheduling feature (42, FIGURE 1) for the user is currently enabled.
  • the scheduling feature enables the user (or the subscriber, if different) to select based on time of day, and day of week parameters, which of the plural service profiles 38(n) is to be active. If the scheduling feature is enabled, then the appropriate one of the service profiles based on the schedule is selected in step 116 to be implemented in connection with the call.
  • step 102 the user may selectively choose not to have an established schedule be activated and followed. In the event the schedule designates the current time of day and day of week are black-out periods for user originated calls, an appropriate confirming announcement with respect to the black-out is then sent back to the mobile station in step 106, and the call is terminated. If no (in step 114), the default one of the plural service profiles 38(n) for the user, or the user activated one of the plural service profiles (step 104), is selected in step 118 to be implemented in connection with the call. Following selection of a service profile (116 or 118), a determination is made in step 120 as to whether the toggle was previously set in step 110.
  • the service profile effective for the call is switched in step 122 from that selected in steps 116 or 118, to one of the other service profiles for the duration of the current call only. Thereafter, or if no in step 120, the call is screened in step 124 according to the active service profile in order to determine if call completion is permitted.
  • the first is an outgoing allowed list.
  • step 100 If the dialed digits (step 100) meet the parameters of the allowed list, call completion is permitted. Charging for the call is then made against the active service profile in step 126 and the call is completed 128. The second is an outgoing restricted list. If the dialed digits (step 100) meet the parameters of the restricted list, call completion is rejected in step 130. An appropriate confirming announcement with respect to the restriction is then sent back to the mobile station in step 106, and the call is terminated.
  • FIGURE 8 a flow diagram illustrating handling of an incoming call to a mobile station associated with plural service profiles.
  • an incoming call is received dialed to a particular directory number (i.e., the B number).
  • a determination is then made in step 202 as to which of a number of available profiles is currently in effect. This determination may be made by having a different profile 38 associated with each B number, and thus selecting the profile for the dialed B number.
  • the determination is made by having multiple profiles 38(n) associated with each individual B number, and then selecting that profile which is either currently selected by the called subscriber as being active or is active based on a schedule. The process then selects the proper profile 38(n) in step 204.
  • the process next screens against the calling party telephone number (i.e., the A number) in step 206.
  • This screening process is performed against a list of A number from which it is permissible for the called mobile station to receive an incoming call.
  • the list can be as specific as including particular numbers, or a general as including broad source indications (like prefixes and area codes). If the A number is not authorized by the list, the incoming call is rejected in step 208. If the A number is on the list, the incoming call is next processed through a diversion selection function in step
  • the process may implement location based diversion in step 212.
  • location base diversion the incoming call is diverted for call delivery based on called mobile station location.
  • a number of different diversion options are available contingent on mobile station roaming status.
  • the subscriber may, for example, specify delivery of the call to the mobile station, or alternatively delivery to a forwarding directory number (C number).
  • C number forwarding directory number
  • the selection of one delivery option over another option depends upon the current roaming status (public or private network) of the mobile station in combination with the options specifically assigned by the subscriber for that status.
  • the process of diversion selection may further implement a mobile status based diversion in step 214.
  • the incoming call is diverted for call delivery based on called mobile station operational status.
  • a number of different diversion options are available contingent on mobile station operational status.
  • the subscriber may, for example, designate the mobile station itself as the first point of contact as long as the mobile station is currently in active operational mode. If the mobile station is currently in inactive operational mode, however, the incoming call is instead routed in accordance with a diversion routing in step 216. Furthermore, if the mobile station is currently active, but is busy or there is no answer to the incoming call alert, the incoming call is again instead routed in accordance with the diversion routing of step 216.
  • the diversion routing of step 216 specifies the manner with which call delivery is be accomplished. As a general rule, this manner of accomplishing call delivery is specified by the subscriber based on the currently effective operation status of the called mobile station at the time of delivery. For example, if the current status of the mobile station is either inactive, busy or no answer, diversion routing may specify forwarding of the incoming call to a certain directory number (perhaps, comprising a voice mail box for the subscriber or other selected C number).
  • a certain directory number perhaps, comprising a voice mail box for the subscriber or other selected C number.
  • other delivery mechanisms may be employed. Examples of these mechanisms include sequential paging, sequential time based paging, or called party controlled completion (CPCC) services.
  • CPCC called party controlled completion
  • Sequential paging refers to a delivery mechanism where a list of forwarding numbers to be sequentially tried is maintained to handling step 216 diversion routing instances. If one of the numbers on the list is busy, the call is routed to an identified end of list destination (typically comprising a voice mail box). If the last number on the list is reached without completing a successful call set-up, then the call is also routed to an identified end of list destination. Furthermore, if a time out occurs without making a successful call set-up, then the call is also routed to an identified end of list destination. Sequential time based paging refers to a delivery mechanism use of certain one or more of the numbers on the list is restricted in time.
  • Called party controlled completion refers to a delivery mechanism where the called party exercises control over how an incoming call is to be handled (such as, for example, transfer to voice mail, forward to alternate number, and the like).
  • the process moves to charge for the incoming call against the active service profile in step 218 and the call is completed 220. It is recognized that in some instances completion of the call will not occur, the process accordingly returns (also dotted path 222) back to the diversion function 210 for further handling.
  • handling may, for example, comprise retrieving a different forward to number in the case of the sequential call delivery mechanism.

Abstract

The conventional one-to-one relationship between a mobile station (14) and its associated service profile (38) is broken to allow for plural service profiles to be selectively activated for use in connection with a single mobile station. These plural service profiles are stored in the home location register HLR (20) of the cellular network (10). A separate billing identification (44) is maintained for each service profile in order to allow for segregated billing of service charges incurred with respect to use of the mobile station. Selection of a certain one of the plural service profiles to be active for a mobile station is made through, for example, a default choice, a user selected choice, a feature code selected choice, or a schedule driven selected choice. The active one of the plural service profiles is down-loaded from the home location register, and applied in connection with both in-coming and out-going calls.

Description

MULTIPLE SUBSCRIBER SERVICE PROFILES PER MOBILE STATION IN A CELLULAR COMMUNICATIONS SYSTEM
BACKGROUND OF THE INVENTION Technical Field of the Invention
The present invention relates to cellular communications systems and, in particular, to the maintaining of multiple subscriber service profiles for a given mobile station operating within a cellular communications system. Description of Related Art In a conventional cellular communications system, a one-to-one relationship is typically maintained between the mobile station and the subscription for that mobile station. In this regard, the "subscription" refers to the contract entered into by a user (also referred to as the "subscriber") with a cellular service provider. The subscription defines not only to whom billing for cellular services should be charged, but also sets forth the particular types of cellular calling services and features that are to be provided to the subscriber. Once the subscripted to cellular calling services and features have been defined, this data is collected in a subscriber service profile that is stored and maintained in a database. The service profile is linked in that database to an identification of the mobile station for the subscriber. Thus, the conventional system also maintains a one-to-one relationship between each mobile station and the service profile that defines the cellular services and features provided to that mobile station.
In most cases, there are no difficulties experienced with maintaining this one-to-one relationship between a mobile station and its associated subscription/service profile. However, situations do arise where the provision of a single subscription/service profile presents a problem. For example, many individual subscribers utilize their mobile stations for both business and personal calls. Often times the charges incurred by the subscriber for business cellular calls may be reimbursed by their employer. As only one bill is generated for the associated subscription, the subscriber must carefully review each billing statement, excise out the charges for business related calls, and submit those charges for employer reimbursement. In an analogous situation, a corporate subscriber may maintain a cellular telephone for employee use during business hours for business purposes. At the same time, however, the corporate subscriber may desire to give the using employee the privilege of access to cellular service for personal calls.
Again, as only one bill is generated, some segregation of cellular service charges must be made, and a corresponding deduction from employee pay applied for the cost of personal calls.
There is a need then for a technique that would not only enable a mobile station user to differentiate between business and personal calls, but also separately account for such calls in service billings.
SUMMARY OF THE INVENTION
To address the foregoing needs, a subscription for cellular service is associated with plural service profiles. Thus, a one-to-many relationship is established between a mobile station and its associated subscription/service profiles. Different billing statements for use of the same mobile station are then generated for each service profile to allow for segregated billing of service charges incurred for mobile station use.
The home location register (HLR) of the cellular network stores plural service profiles for such subscripted mobile stations. Each of the service profiles is associated with a different billing identification to allow service charges incurred for use of the single mobile station to be properly allocated between the different profiles. The user selects in the mobile station (MS) a particular one of the profiles to be active. At each registration, an identification of this selected service profile is sent to the serving cellular network, and the selected service profile is down- loaded from the home location register. Alternatively, the user selects the active service profile to be down-loaded from the home location register by sending a feature code to the cellular network. Furthermore, selection of the active service profile for down-loading may be made by the network in accordance with a stored schedule maintained by the home location register. Charging on a per service profile basis is made for both in-coming and outgoing calls. In each case, appropriate toll tickets are generated by the network. These toll tickets identify not only the subscription for the mobile station involved in the call, but also the particular active one of the plural service profiles for that mobile station to which the service charges should be applied. By processing these toll tickets, a billing center may segregate the billing of service charges incurred for mobile station use against each of the plural service profiles.
BRIEF DESCRIPTION OF THE DRAWINGS
A more complete understanding of the method and apparatus of the present invention may be acquired by reference to the following Detailed Description when taken in conjunction with the accompanying Drawings wherein: FIGURE 1 is a schematic diagram of a cellular telephone network of the present invention;
FIGURE 2 is a node operation and signal flow diagram illustrating selection at mobile station registration between plural available service profiles; FIGURE 3 is a node operation and signal flow diagram illustrating selection using a feature code transmission between plural available service profiles;
FIGURE 4 is anode operation and signal flow diagram illustrating selection according to a schedule between plural available service profiles;
FIGURE 5 is a node operation and signal flow diagram illustrating a first embodiment for effectuating a call set up and delivery;
FIGURE 6 is a node operation and signal flow diagram illustrating a second embodiment for effectuating a call set up and delivery;
FIGURE 7 is a flow diagram illustrating handling of an outgoing call from a mobile station associated with plural service profiles; and FIGURE 8 is a flow diagram illustrating handling of an incoming call to a mobile station associated with plural service profiles.
DETAILED DESCRIPTION OF THE DRAWINGS
Reference is now made to FIGURE 1 wherein there is shown a schematic diagram of a cellular telephone network 10 including a plurality of interconnected switching nodes (SN) 12. Although only two switching nodes 12 are shown, it will be understood that the network 10 likely includes many more interconnected nodes. The first and second switching nodes 12(1) and 12(2) may comprise any one of a number of known telecommunications switching devices, including those commonly used and known in the art for providing either digital or analog cellular telephone service to a plurality of mobile stations (MS) 14. The switching nodes
12 are interconnected with each other for communication via both voice trunks 18 (illustrated with broken lines) and signaling links 16 (illustrated with solid lines) providing a known ISUP (or Rl or R2) type connection. The voice trunks 18 provide voice and data communications paths used to carry subscriber communications between the switching nodes 12. The signaling links 16 carry command signals between the switching nodes 12. These signals may be used, for example, in setting up and tearing down voice and data communications links over the voice trunks 18 and controlling the provision of calling services to the mobile stations 14. The switching nodes 12 are also connected to a home location register
(HLR) 20 through their associated visitor location register (VLR) 40 by means of signaling links 22 providing a known Mobile Application Part (MAP) or IS-41 type connection. The home location register 20 stores information relating to the mobile stations 14 and their subscriptions comprising location information and service profile information. In connection with the present invention, as will be described in more detail below, the home location register 20 in particular stores plural service profiles for at least one of the mobile stations.
In one cellular system implementation, illustrated generally at 23, the switching node 12 is further connected to at least one associated base station controller (BSC) 24 via both a signaling link 26 and a voice trunk 28. Only one base station controller 24 is shown connected to switching node 12(2) in order to simplify the illustration. The voice trunk 28 provides a voice and data communications path used to carry subscriber communications between the second switching node 12(2) and its base station controller 24. The signaling link 26 carries command signals between the node 12 and its associated base station controller 24. The signaling link 26 and trunk 28 are collectively commonly referred to in the art as the "A interface". The base station controller 24 is then connected to a plurality of base stations (BS) 30 which operate to effectuate radio frequency communications with proximately located mobile stations 14 over an air interface 32. The base station controller 24 functions in a well known manner to control this radio frequency communications operation.
In another cellular system implementation, illustrated generally at 25, the switching node 12(1) is further connected to a plurality of base stations (BS) 30 which operate to effectuate radio frequency communications with proximately located mobile stations 14 over the air interface 32. In this implementation, the functionality provided by the base station controller 24 (see, generally at 23) is instead provided by the switching node 12(1).
Although direct communications links (signaling and/or trunk) are illustrated in FIGURE 1, it is understood by those skilled in the art that the links are not necessarily direct between the illustrated nodes, and may instead pass through many other communications nodes (not shown) of the mobile network, and perhaps even utilize other communications networks (such as the public switched telephone network - PSTN). Illustration of the links in a "virtual" manner as shown in FIGURE 1 is therefore by way of simplification of the drawing and the communications relationship between the various included nodes within the network 10.
For each cellular service subscription associated with a served mobile station 14, the home location register 20 stores service profile information 34 relating to cellular services and features subscripted to by the subscriber for that served mobile station. If conventional service is provided to a mobile station 14, the service profile information 34 associated with that mobile station subscription comprises a single service profile 36 per subscription. Conversely, and in accordance with the present invention, plural service profiles 38(n), where n>l, may comprise the service profile information 34 associated with a single mobile station 14. For mobile stations 14 having subscriptions that support plural service profiles 38(n), any one of those plural profiles may be selected, either by the system or by the subscriber (with some restrictions), for use at a specific time or in connection with a specific call.
When a mobile station 14 makes an initial registration with the system through a particular switching node 12, that switching node requests a subscriber service profile 36 or 38(n) relating to that mobile station, and its corresponding subscription, from the home location register 20. This subscriber service profile 36 or 38(n) information is downloaded from the home location register 20 for storage in a visitor location register (VLR) 40 associated with the switching node 12. Service for both in-coming and out-going calls is then provided to the mobile station 14 by the serving switching node 12 in accordance with the downloaded service profile 36 or 38(n). In accordance with one embodiment of the present invention, the subscriber enters a service profile selection code into the mobile station 14, and this selection information is conveyed by the serving switching node 12 to the home location register 20 at each registration. The home location register 20 processes the selection information to identify the proper one of the n available service profiles 38(n) for the mobile station 14. This profile is then downloaded to the visitor location register 40.
In another embodiment of the present invention, the subscriber sends a feature code through the mobile station 14. This feature code is indicative of the activation of a certain one of the n available service profiles 38(n) for the mobile station 14. Responsive to receipt of the feature code, the proper service profile
38(n) is identified by the home location register 20 and downloaded to the visitor location register 40. That particular service profile 38(n) is further marked as being active by the home location register 20. In response to any subsequent registration of the mobile station, the home location register 20 automatically retrieves the active one of the service profiles 38(n) for a visitor location register 40 download.
Deactivation of the currently activated service profile occurs when the mobile station powers-off or when the mobile station has been idle for longer than a predetermined time period. Alternatively, the selected service profile 38(n) continues to remain active until such time as a new selection is made through feature code entry.
In yet another embodiment of the present invention, the activation of a certain one of the n available service profiles 38(n) depends on a subscriber or service provider defined schedule 42 for the mobile station 14. This schedule may, for example, designate that a business related one of the service profiles 38(n) be active during weekday business hours, while a personal related one of the service profiles be active at all other times. As another application, the schedule may designate that a first employee related service profile 38(n) be active during a first weekday time shift, a second employee related service profile be active during a second weekday time shift, a third employee related service profile be active during a third weekday time shift, and that no service profile be active on weekends. No matter what the particular schedule that is established, in response to a registration, the home location register 20 identifies (based on the schedule 42) the proper active one of the n available service profiles 38(n) for the mobile station 14. This profile is then downloaded to the visitor location register 40.
In each case, a different billing identification 44(n) is provided for each of the n available service profiles 38(n) for the mobile station 14. A billing center 46 for the service provider receives toll tickets (TTs) relating to calling charges, processes the toll tickets with respect to the mobile station and particular active service profile thereof, and then accordingly generates a separate billing statement for each identification 44(n) effectively allocating cellular service costs properly among various usages and subscribers. Taking, for example, the previous scenario where a business service profile 38(n) and personal service profile are provided for a single mobile station 14, one business billing statement and one personal billing statement are generated by the billing center 46. This allows the subscriber to account between business and personal calling expenses. Similarly, for the previous multi-shift related service profiles 38(n), one billing statement is generated for each weekday time shift. This allows an employer to allocate business calling expenses by shift and/or the assigned personnel. In order to generate this billing information, properly allocated to the plural service profiles, each toll ticket generated by the network 10 during a call and communicated to the billing center 46 must included information identifying the mobile station/subscription at issue, and further include information identifying, or allowing the billing center to identify, the particular one of the service profiles 38(n) that is active for the call. Furthermore, if needed or desired, each of the plural service profiles 38(n) may be associated with a different directory number. Thus, not only is a single mobile station associated with different service profiles, but it may also be accessed by a caller through the dialing of any one of a number of different directory numbers. This allows each one of a number of potential users of the mobile station to have a unique telephone directory number for in-coming calls. In connection with the handling of such calls, a number of billing options are available. First, an in-coming call dialed to a certain directory number may be delivered to the mobile station regardless of whether the service profile associated with that number is currently active. Billing is made either to the service profile for the called number, or the service profile that is currently active. Second, the alternative holds true: no call delivery occurs unless the service profile associated with the dialed number is currently active. Billing is made to the active service profile of the called number.
Reference is now made to FIGURE 2 wherein there is shown a node operation and signal flow diagram illustrating selection at mobile station registration between plural available service profiles. The subscriber selects (action 200) a particular one of plural available service profiles 38(n) for use by making an appropriate entry into the mobile station 14. This selection is stored (action 202) by the mobile station. The mobile station 14 then makes a registration with the cellular telephone network by transmitting a registration message 204 to the serving switching node 12 through the serving base station 30 (and perhaps the serving base station controller 24). This registration message 204 includes information, perhaps stored in an included parameter, identifying the subscriber selected one of plural available service profiles 38(n). Responsive thereto, the switching node 12 sends a registration notification message 206 to the home location register 20 through the visitor location register 40 requesting the selected one of the service profiles 38(n) associated with the registering mobile station 14. The home location register 20 retrieves the selected one of the service profiles 38(n), and sends that information in message 208 back for storage (action 210) in the visitor location register 40 associated with the requesting switching node 12. In-coming and outgoing calling service is thereafter provided to the mobile station in accordance with the down-loaded service profile. If desired, the selected 200 service profile remains active until the mobile station has been idle for longer than a predetermined time period (action 212). Reference is now made to FIGURE 3 wherein there is shown a node operation and signal flow diagram illustrating selection using a feature code transmission between plural available service profiles. A feature request is dialed (action 220) by a subscriber into their mobile station 14. This feature request (perhaps in the form of an appropriately formatted star code) identifies a subscriber selected one of plural available service profiles 38(n) for activation, and may further present a personal identification number (PIN) indicating authorization for the selection. A feature origination message 222 is then sent by the mobile station
14 (over the air interface and through the base station) to the switching node 12. In response thereto, the switching node 12 sends a feature request message 224, including the dialed feature code, to the home location register 20. The home location register 20 then processes the message 224 to determine whether the subscriber is authorized to use the feature (action 226), and if so, what actions need to be taken in response to the request (action 228) and what instructions, if any, need to be presented to the mobile switching center to effectuate the feature (action 230). In particular, with respect to the actions 228 taken, the home location register 20 marks the subscriber selected one of plural available service profiles 38(n) as being active. A feature request return result message 232, confirming activation of the selected service profile 38(n), is then sent by the home location register 20 back to the mobile station 14 through the switching node 12. The home location register 20 also retrieves the selected one of the service profiles 38(n), and sends that information in message 234 back for storage (action 236) in the visitor location register 40 associated with the switching node 12. In-coming and out-going calling service is thereafter provided to the mobile station in accordance with the downloaded service profile.
Once a subscriber selected one of plural available service profiles 38(n) has been marked as being active, it remains active until the mobile station powers-off 5 (action 238), the mobile station has been idle for longer than a predetermined time period (action 240), or a new selection is made by the subscriber through feature code entry (action 220). The feature code entry (action 220) may alternatively simply de-activate the currently active service profile (taken in actions 228), with activation of a service profile requiring the entry of another feature code. o Once a service profile 38(n) is activated, it is made available at each time the mobile station 14 registers. The mobile station 14 makes a registration with the cellular telephone network by transmitting a registration message 242 to the serving switching node 12 through the serving base station 30 (and perhaps the serving base station controller 24). Responsive thereto, the switching node 12 sends a 5 registration notification message 244 to the home location register 20 through the visitor location register 40 requesting the currently active one of the service profiles 38(n) associated with the registering mobile station 14. The home location register 20 retrieves the active one of the service profiles 38(n), and sends that information in message 246 back for storage (action 248) in the visitor location register 40 associated with the requesting switching node 12. In the event that none of the service profiles 38(n) is currently active, the home location register 20 returns a registration denied message 250 back the switching node 12. If possible, the reason for denial is conveyed to the mobile station in message 252. This prompts the subscriber to activate one of the plural service profiles 38(n) through feature code entry (action 220), resulting in a down-loading of the selected one of the service profiles 38(n) in message 234 for storage (action 236) in the visitor location register 40 associated with the switching node 12.
Reference is now made to FIGURE 4 wherein there is shown a node operation and signal flow diagram illustrating selection according to a schedule between plural available service profiles. A schedule 42 designating the activation periods for each of plural available service profiles 38(n) of a mobile station 14 is stored (action 260) in the home location register 20. The schedule 42 may be either service provider or subscriber defined. The mobile station 14 subsequently makes a registration with the cellular telephone network by transmitting a registration message 262 to the serving switching node 12 through the serving base station 30 (and perhaps the serving base station controller 24). Responsive thereto, the switching node 12 sends a registration notification message 264 to the home location register 20 through the visitor location register 40 requesting the schedule 42 defined active one of the service profiles 38(n) associated with the registering mobile station 14. The home location register 20 retrieves the service profile 38(n) identified by the schedule as being active, and sends that information in message 266 back for storage (action 268) in the visitor location register 40 associated with the requesting switching node 12. In-coming and out-going calling service is thereafter provided to the mobile station in accordance with the down-loaded service profile.
Reference is now once again made to FIGURE 1. Although not necessarily a requirement, the cellular telephone network 10 is preferably implemented as a wireless intelligent network (IN) and thus further includes at least one service control point (SCP) 48. The switching nodes 12 (also referred to as service switching points (SSPs) in this configuration) are connected to the service control point 48 by means of the signaling links 22 which utilize protocols such as Mobile Application Part (MAP), IS-41 , Intelligent Network Application Part (INAP), or
Transaction Capability Application Part (TCAP). The home location register 20 is preferably implemented in conjunction with the service control point 48. The service control point 48 provides a centralized processing platform for implementing the "intelligence" of the network 10. In the context of the present invention, this intelligence comprises the administration over the plural service profiles 38(n) available to certain ones of the mobile stations 14. This administration primarily involves the operations described herein for selecting which one of the service profiles 38(n) is to be active at any one time (either in response to subscriber selection, feature code selection, or scheduling selection). Alternatively, a separate combined service switching point/service control point (SSP/SCP or SSCP) 50 is provided for handling of calls implicating multiple service profile 38(n) selection. This combined service switching point/service control point 50 is connected to the switching nodes 12 via both voice trunks 18 (illustrated with broken lines) and signaling links 16 (illustrated with solid lines) providing a known ISUP (or Rl or R2) type connection, and is connected to the home location register by means of the signaling links 22 which utilize protocols such as Mobile Application Part (MAP), IS-41, Intelligent Network Application
Part (INAP), or Transaction Capability Application Part (TCAP). Although not specifically illustrated, it is understood that the intelligent network further includes intelligent peripherals (IPs) and other nodes as needed to implement in a known manner any desired intelligent network services. Reference is now made to FIGURE 5 wherein there is shown a node operation and signal flow diagram illustrating a first embodiment for effectuating a call set up and delivery. A call 300 dialed to the directory number (B-number) of a mobile station 14 originates from another cellular subscriber or the public switched telephone network (PSTN), and is received at a first (originating or gateway) switching node 12(1). The originating switching node 12(1) determines whether the calling party is entitled to receive any intelligent network services (action 302). One such service may comprise the plural service profile 38(n) service of the present invention. If so, the originating switching node 12(1) sends an originating access message 304 to the home location register 20 (service control point 48). This message 304 requests an identification of each intelligent network service to which either the calling party is entitled. The list of such services (including, for example, the plural service profile 38(n) service) is returned to the originating switching node 12(1) in message 306. The identified services in the returned list are then evaluated and organized (action 308) for implementation in connection with the call 300.
With respect to call handling in the context of the plural service profile 38(n) service of the present invention, the call is routed 310 to the particular combined service switching point/service control point 50 supporting that service (assuming the home location register 20 cannot provide all necessary support, including billing). In this regard, the combined service switching point/service control point 50 has knowledge (perhaps down-loaded from, or accessed from the home location register 20) of the plural service profiles 38(n) associated with the calling/called party. The active one of the plural service profiles 38(n) is then implemented (action 312) in connection with the call, and a toll ticket for billing is generated 314 specifically identifying the active profile of a given subscription be charged. The call is then routed 316 back to the originating switching node 12(1). As a further refinement of the call handling process, the call leg routings
310 and 316 may be dropped (if desired), as generally indicated with "X" markings, from the call 300 once generation 314 of the toll ticket associating the call with the proper service profile is completed. Another toll ticket for billing is then generated 318 by the originating switching node 12(1) identifying that the given subscription be charged. These toll tickets are processed by the billing center 46 to generate a charge for the call, with that charge being assessed against the currently active one of the service profiles 38(n) of the calling party subscription. As another refinement, the billing information relating to the active service profile 38(n) is sent to the originating switching node 12(1) to be included in its generated 318 toll ticket, thus obviating the need for a separate toll ticket generated 314 by the service switching point/service control point 50.
Now that the appropriate one of the plural service profiles 38(n) has been associated with the call, and following the actuation of any other appropriate intelligent network services in connection with the call, the originating switching node 12(1) interrogates the home location register 20 with a location request (send routing) message 320. The location request (send routing) message 320 is processed by the home location register 20 to determine the location (i.e., second or serving switching node 12(2)) within the cellular network 10 of the called mobile station 14. Responsive to this interrogation, the home location register 20 messages the serving switching node 12(2) for the called mobile station 14 with a routing request (provide roaming) message 322 to prepare for the call. The serving switching node 12(2) then determines in action 324, to some selected degree of granularity, the location (for example, location area) of the called mobile station 14. This location may be identified, for example, based on information resulting from a most recent registration (not shown) of the called mobile station 14 as stored in the visitor location register (not shown) associated with the serving switching node 12(2). Alternatively, the serving switching node 12(2) may page (not shown) the called mobile station 14, and process the page response (not shown) to make a more precise location determination. In accordance with this determined location, the serving switching node 12(2) selects in action 326 an appropriate routing number (for example, a temporary location directory number (TLDN) or a roaming number) for that location. In this instance, the routing number is selected from a plurality of such numbers associated with the serving switching node 12(2). The selected routing number is then returned 328 to the originating switching node 12(1) via the home location register 20. The incoming call is then delivered (through connected) 330 to the serving switching node 12(2) using the routing number for attempted completion to the called mobile station 14. Completion of the call involves further routing 332 the incoming call to the currently serving base station 30 (perhaps through the base station controller 24), and then to the called mobile station 14 over the air interface 32. The serving switching node 12(2) handles the call in accordance with the down-loaded, visitor location register stored, service profile of the called mobile station. It is recognized that this down-loaded service profile may comprise one of a number of service profiles 38(n) assigned to the called mobile station 14 subscriber and currently designated as active (see, FIGURES 2, 3 and 4). A toll ticket (TT) is accordingly generated (action 334) against the active one of the service profiles for the called mobile station. Toll ticket processing enables the billing center 46 to properly generate a charge for the call, with that charge being assessed against the currently active one of the service profiles 38(n) of the called party subscription.
Reference is now made to FIGURE 6 wherein there is shown a node operation and signal flow diagram illustrating a second embodiment for effectuating a call set up and delivery. A call 300 dialed to the directory number
(B-number) of a mobile station 14 originates from another cellular subscriber or the public switched telephone network (PSTN), and is received at a first (originating or gateway) switching node 12(1). The originating switching node 12(1) determines whether the calling party is entitled to receive any intelligent network services (action 302). One such service may comprise the plural service profile
38(n) service of the present invention. If so, the originating switching node 12(1) sends an originating access message 304 to the home location register 20 (service control point 48). This message 304 requests an identification of each intelligent network service to which either the calling party is entitled. The list of such services (including, for example, the plural service profile 38(n) service) is returned to the originating switching node 12(1) in message 306. The identified services in the returned list are then evaluated and organized (action 308) for implementation in connection with the call 300.
Routing of the call to a service switching point/service control point 50 is not required in this embodiment as the home location register 20 (service control point 48) support all aspects (including billing) for the plural service profile 38(n) service of the present invention. Thus, responsive to the originating access message 304, the active one of the plural service profiles 38(n) is then implemented (action 312') in connection with the call, and a toll ticket for billing is generated 314' specifically identifying that the specific active profile of a subscription be charged. Another toll ticket for billing is then generated 318 by the originating switching node 12(1) identifying that the subscription be charged. These toll tickets are processed by the billing center 46 to generate a charge for the call, with that charge being assessed against the currently active one of the service profiles 38(n) of the identified calling party subscription. As a refinement to the process, the billing information relating to the active service profile 38(n) is sent to the originating switching node 12(1) to be included in its generated 318 toll ticket, thus obviating the need for a separate toll ticket generated 314' by the home location register 20.
Now that the appropriate one of the plural service profiles 38(n) has been associated with the call, and following the actuation of any other appropriate intelligent network services in connection with the call, the originating switching node 12(1) interrogates the home location register 20 with a location request (send routing) message 320. The location request (send routing) message 320 is processed by the home location register 20 to determine the location (i.e., second or serving switching node 12(2)) within the cellular network 10 of the called mobile station 14. Responsive to this interrogation, the home location register 20 messages the serving switching node 12(2) for the called mobile station 14 with a routing request (provide roaming) message 322 to prepare for the call. The serving switching node 12(2) then determines in action 324, to some selected degree of granularity, the location (for example, location area) of the called mobile station 14.
This location may be identified, for example, based on information resulting from a most recent registration (not shown) of the called mobile station 14 as stored in the visitor location register (not shown) associated with the serving switching node 12(2). Alternatively, the serving switching node 12(2) may page (not shown) the called mobile station 14, and process the page response (not shown) to make a more precise location determination. In accordance with this determined location, the serving switching node 12(2) selects in action 326 an appropriate routing number (for example, a temporary location directory number (TLDN) or a roaming number) for that location. In this instance, the routing number is selected from a plurality of such numbers associated with the serving switching node 12(2). The selected routing number is then returned 328 to the originating switching node 12(1) via the home location register 20. The incoming call is then delivered (through connected)
330 to the serving switching node 12(2) using the routing number for attempted completion to the called mobile station 14. Completion of the call involves further routing 332 the incoming call to the currently serving base station 30 (perhaps through the base station controller 24), and then to the called mobile station 14 over the air interface 32. The serving switching node 12(2) handles the call in accordance with the down-loaded, visitor location register stored, service profile of the called mobile station. It is recognized that this down-loaded service profile may comprise one of a number of service profiles 38(n) assigned to the called mobile station 14 subscriber and currently designated as active (see, the process of FIGURES 2, 3 and 4). A toll ticket (TT) is accordingly generated (action 334) against the active one of the service profiles for the called mobile station. Toll ticket processing enables the billing center 46 to properly generate a charge for the call, with that charge being assessed against the currently active one of the service profiles 38(n) of the called party subscription. Reference is now made to FIGURE 7 wherein there is shown a flow diagram illustrating handling of an outgoing call from a mobile station associated with plural service profiles. In step 100, a call origination is received by the process. This received call origination 100 includes an identification of digits dialed for an outgoing call and/or code dialings. A determination is then made in step 102 as to whether the received call concerns a user designated and transmitted activation (feature) code. If yes, an appropriate action is taken in step 104 in response to the code. For example, the sent code may identify a subscriber selected one of plural available service profiles 38(n) for activation (see, FIGURE 3). Other actions relevant to the plural service profile 38(n) service of the present invention and involving a feature code selection are presented below. It should further be noted that a specific feature code may be recognized that would prevent unauthorized entry of feature codes to specify certain actions and changes. An appropriate confirming announcement with respect to the action (such as confirming the selection of a certain service profile) is then sent back to the mobile station in step 106, and the call is terminated. If no, a determination is then made in step 108 as to whether the received call concerns a user designated and transmitted escape code. This escape code signals the process to switch between available service profiles 38(n) for a current call only. This differs from the activation code of step 102 where a semi-permanent switch of service profiles may be made. Accordingly, if yes, a toggle is set in step 110. Thereafter, or if no in step 108, a determination is made in step 114 as to whether a scheduling feature (42, FIGURE 1) for the user is currently enabled. The scheduling feature enables the user (or the subscriber, if different) to select based on time of day, and day of week parameters, which of the plural service profiles 38(n) is to be active. If the scheduling feature is enabled, then the appropriate one of the service profiles based on the schedule is selected in step 116 to be implemented in connection with the call. Through the use of an appropriate activation (feature) code (step 102), the user may selectively choose not to have an established schedule be activated and followed. In the event the schedule designates the current time of day and day of week are black-out periods for user originated calls, an appropriate confirming announcement with respect to the black-out is then sent back to the mobile station in step 106, and the call is terminated. If no (in step 114), the default one of the plural service profiles 38(n) for the user, or the user activated one of the plural service profiles (step 104), is selected in step 118 to be implemented in connection with the call. Following selection of a service profile (116 or 118), a determination is made in step 120 as to whether the toggle was previously set in step 110. If yes, the service profile effective for the call is switched in step 122 from that selected in steps 116 or 118, to one of the other service profiles for the duration of the current call only. Thereafter, or if no in step 120, the call is screened in step 124 according to the active service profile in order to determine if call completion is permitted. In this regard, there are two kinds of screening lists that are implemented for each of the service profiles. The first is an outgoing allowed list.
If the dialed digits (step 100) meet the parameters of the allowed list, call completion is permitted. Charging for the call is then made against the active service profile in step 126 and the call is completed 128. The second is an outgoing restricted list. If the dialed digits (step 100) meet the parameters of the restricted list, call completion is rejected in step 130. An appropriate confirming announcement with respect to the restriction is then sent back to the mobile station in step 106, and the call is terminated.
Reference is now made to FIGURE 8 wherein there is shown a flow diagram illustrating handling of an incoming call to a mobile station associated with plural service profiles. In step 200, an incoming call is received dialed to a particular directory number (i.e., the B number). A determination is then made in step 202 as to which of a number of available profiles is currently in effect. This determination may be made by having a different profile 38 associated with each B number, and thus selecting the profile for the dialed B number. In accordance with the present invention, the determination is made by having multiple profiles 38(n) associated with each individual B number, and then selecting that profile which is either currently selected by the called subscriber as being active or is active based on a schedule. The process then selects the proper profile 38(n) in step 204.
Once the proper profile 38(n) has been determined and selected, the process next screens against the calling party telephone number (i.e., the A number) in step 206. This screening process is performed against a list of A number from which it is permissible for the called mobile station to receive an incoming call. The list can be as specific as including particular numbers, or a general as including broad source indications (like prefixes and area codes). If the A number is not authorized by the list, the incoming call is rejected in step 208. If the A number is on the list, the incoming call is next processed through a diversion selection function in step
210.
With respect to the diversion selection function, the process may implement location based diversion in step 212. In accordance with location base diversion, the incoming call is diverted for call delivery based on called mobile station location. A number of different diversion options are available contingent on mobile station roaming status. The subscriber may, for example, specify delivery of the call to the mobile station, or alternatively delivery to a forwarding directory number (C number). The selection of one delivery option over another option depends upon the current roaming status (public or private network) of the mobile station in combination with the options specifically assigned by the subscriber for that status.
The process of diversion selection may further implement a mobile status based diversion in step 214. In accordance with mobile status based diversion, the incoming call is diverted for call delivery based on called mobile station operational status. A number of different diversion options are available contingent on mobile station operational status. The subscriber may, for example, designate the mobile station itself as the first point of contact as long as the mobile station is currently in active operational mode. If the mobile station is currently in inactive operational mode, however, the incoming call is instead routed in accordance with a diversion routing in step 216. Furthermore, if the mobile station is currently active, but is busy or there is no answer to the incoming call alert, the incoming call is again instead routed in accordance with the diversion routing of step 216. The diversion routing of step 216 specifies the manner with which call delivery is be accomplished. As a general rule, this manner of accomplishing call delivery is specified by the subscriber based on the currently effective operation status of the called mobile station at the time of delivery. For example, if the current status of the mobile station is either inactive, busy or no answer, diversion routing may specify forwarding of the incoming call to a certain directory number (perhaps, comprising a voice mail box for the subscriber or other selected C number). Optionally, other delivery mechanisms may be employed. Examples of these mechanisms include sequential paging, sequential time based paging, or called party controlled completion (CPCC) services. Sequential paging refers to a delivery mechanism where a list of forwarding numbers to be sequentially tried is maintained to handling step 216 diversion routing instances. If one of the numbers on the list is busy, the call is routed to an identified end of list destination (typically comprising a voice mail box). If the last number on the list is reached without completing a successful call set-up, then the call is also routed to an identified end of list destination. Furthermore, if a time out occurs without making a successful call set-up, then the call is also routed to an identified end of list destination. Sequential time based paging refers to a delivery mechanism use of certain one or more of the numbers on the list is restricted in time. For example, a business hours dialing list and a non-business hours dialing list may be maintained. Thus, certain numbers are effective only at certain times of the day (or perhaps day of the week), and those effective numbers are sequentially tried during step 216 diversion routing. Called party controlled completion refers to a delivery mechanism where the called party exercises control over how an incoming call is to be handled (such as, for example, transfer to voice mail, forward to alternate number, and the like).
Once A number screening and diversion function have been performed, the process moves to charge for the incoming call against the active service profile in step 218 and the call is completed 220. It is recognized that in some instances completion of the call will not occur, the process accordingly returns (also dotted path 222) back to the diversion function 210 for further handling. Such handling may, for example, comprise retrieving a different forward to number in the case of the sequential call delivery mechanism.
Although preferred embodiments of the method and apparatus of the present invention have been illustrated in the accompanying Drawings and described in the foregoing Detailed Description, it will be understood that the invention is not limited to the embodiments disclosed, but is capable of numerous rearrangements, modifications and substitutions without departing from the spirit of the invention as set forth and defined by the following claims.

Claims

WHAT IS CLAIMED IS:
1. A cellular telephone system serving a plurality of mobile stations, comprising: at least one home location register storing service profile information for each of the served mobile stations, wherein the stored service profile information comprises plural different service profiles maintained for each of certain ones of the mobile stations.
2. The system as in claim 1 wherein each of the plural different service profiles maintained for each of the certain ones of the mobile stations has a billing identification in order to allow for segregated billing by service profile of service charges incurred with respect to use of the certain mobile stations.
3. The system as in claim 1 further comprising means for selecting an active one of the plural different service profiles for application in providing cellular telephone service to the certain mobile station.
4. The system as in claim 3 wherein the means for selecting comprises a schedule that identifies which of the plural different service profiles is to be active at any given time.
5. The system as in claim 3 wherein the means for selecting comprises a feature code selection that identifies which of the plural different service profiles is to be active at any given time.
6. The system as in claim 3 wherein the means for selecting comprises a default selection that identifies which of the plural different service profiles is to be active.
7. A method for providing cellular telephone service to a mobile station, comprising the steps of: storing for that mobile station a plurality of different service profiles; and activating a certain one of the plurality of different service profiles for application in providing cellular telephone service to the certain mobile station.
8. The method as in claim 7 wherein the step of storing comprises the step of maintaining a billing identification for each of the plural service profiles in order to allow for segregated billing by service profile of service charges incurred with respect to use of the mobile station.
9. The method as in claim 7 wherein the step of activating comprises the steps of: establishing an activation schedule defining times when each of the plural service profiles is to be active for application in providing cellular telephone service to the certain mobile station; and activating ones of the plural service profiles in accordance with the established schedule.
10. The method as in claim 7 wherein the step of activating comprises the steps of: selecting by a user of the mobile station of a certain one of the plural service profiles to be active for application in providing cellular telephone service; and communicating that selection at mobile station registration to activate the certain service profile.
11. The method as in claim 10 wherein the step of activating further comprises the step of maintaining the certain service profile as active until the expiration of a predetermined time period.
12. The method as in claim 7 wherein the step of activating comprises the steps of: making a feature code selection identifying a certain one of the plural service profiles to be active for application in providing cellular telephone service; and sending that feature code to activate the certain service profile.
13. The method as in claim 12 wherein the step of activating further comprises the step of maintaining the certain service profile as active until the expiration of a predetermined time period.
14. The method as in claim 7 wherein the step of activating comprises the step of activating a designated default one of the plural service profiles for application in providing cellular telephone service.
15. A method for handling a call origination in a cellular telephone system, comprising the steps of: determining if a calling party is entitled to utilize a plural service profiles per subscriber service; if yes, determining which one of the plural service profiles for the calling party is currently active; applying the currently active one of the plural service profiles to the call origination; and billing service charges for the call origination against the currently active service profile.
16. The method as in claim 15 wherein the step of determining comprises the step of choosing the one of the plural service profiles selected by the calling party.
17. The method as in claim 15 wherein the step of determining comprises the step of choosing the one of the plural service profiles dictated by a schedule.
18. The method as in claim 17 further including the step of rej ecting the call origination if the schedule indicates that a call black-out period is currently in effect.
19. The method as in claim 15 wherein the step of determining comprises the step of choosing a default one of the plural service profiles.
20. The method as in claim 15 wherein the step of billing comprises the step of generating at least one toll ticket for the call origination that identifies not only the calling party but also the active one of the plural service profiles for that calling party.
21. The method as in claim 15 further including the steps of: screening a called number for the call origination against a screening list associated with the active one of the plural subscriber profiles; and permitting the call origination if the step of screening is passed.
22. A method for handling a call delivery in a cellular telephone system, comprising the steps of: determining if a called party is entitled to utilize a plural service profiles per subscriber service; if yes, determining which one of the plural service profiles for the called party is currently active; applying the currently active one of the plural service profiles to the call delivery; and billing service charges for the call delivery against the currently active service profile.
23. The method as in claim 22 wherein the step of determining comprises the step of choosing the one of the plural service profiles selected by the called party.
24. The method as in claim 22 wherein the step of determining comprises the step of choosing the one of the plural service profiles dictated by a schedule.
25. The method as in claim 22 further including the step of applying diversion in connection with delivery of the call to a particular forward to number based on current called mobile station location.
26. The method as in claim 22 further including the step of applying diversion in connection with delivery of the call to a particular forward to number based on called mobile station status.
27. The method as in claim 22 further including the step of completing the call.
28. An intelligent network implementation for a cellular telephone system, comprising: an originating switching node receiving a call from a calling party, the originating node detecting whether the calling party is subscripted to a plural service profiles per subscriber service; and a service switching point/service control point (SSCP) through which the call is routed by the originating switching node if the calling party is subscripted to the plural service profiles per subscriber service, the service switching point/service control point determining which one of the plural service profiles for the calling party is currently active, and generating a toll ticket for the call to be applied against the currently active service profile for the calling party.
29. The system as in claim 28 further including: a home location register connected to the originating switching node, the home location register storing information concerning the plural service profiles for the calling party; wherein the originating switching node determines whether the calling party is subscripted by querying the home location register storing the plural service profiles information.
30. The system as in claim 28 further including a billing center for collecting toll tickets for calls and generating segregated billing of service charges incurred with respect to use of each service profile for the calling party.
31. The system as in claim 28 further including a destination switching node serving a called party for the call, wherein the called party is subscripted to the plural service profiles per subscriber service, and the destination switching node serving the called party in accordance with a currently active one of the plural service profiles for the called party, and generating a toll ticket for the call to be applied against the currently active service profile for the called party.
32. The system as in claim 31 further including: a visitor location register connected to the destination switching node, the visitor location register storing information concerning the currently active one of the plural service profiles for the called party.
33. An intelligent network implementation for a cellular telephone system, comprising: an originating switching node receiving a call from a calling party, the originating node detecting whether the calling party is subscripted to a plural service profiles per subscriber service; and a home location register/service control point (HLR/SCP) connected to the originating switching node, the home location register storing information concerning the plural service profiles for the calling party, the home location register/service control point further being queried by the originating switching node to detect the calling party subscription to the plural service profiles per subscriber service, the home location register/service control point still further determining which one of the plural service profiles for the calling party is currently active, and generating a toll ticket for the call to be applied against the currently active service profile for the calling party.
34. The system as in claim 33 further including a billing center for collecting toll tickets for calls and generating segregated billing of service charges incurred with respect to use of each service profile for the calling party.
35. The system as in claim 33 further including a destination switching node serving a called party for the call, wherein the called party is subscripted to the plural service profiles per subscriber service, and the destination switching node serving the called party in accordance with a currently active one of the plural service profiles for the called party, and generating a toll ticket for the call to be applied against the currently active service profile for the called party.
36. The system as in claim 35 further including: a visitor location register connected to the destination switching node, the visitor location register storing information concerning the currently active one of the plural service profiles for the called party.
PCT/SE1998/002111 1997-11-24 1998-11-20 Multiple subscriber service profiles per mobile station in a cellular communications system WO1999027723A1 (en)

Priority Applications (3)

Application Number Priority Date Filing Date Title
BR9815427-3A BR9815427A (en) 1997-11-24 1998-11-20 Cell phone system, processes for providing cell phone service and for handling a call source and destination in a cell phone system and smart grid implementation system for a cell phone system
AU13577/99A AU1357799A (en) 1997-11-24 1998-11-20 Multiple subscriber service profiles per mobile station in cellular communications system
CA002311367A CA2311367A1 (en) 1997-11-24 1998-11-20 Multiple subscriber service profiles per mobile station in a cellular communications system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US97745597A 1997-11-24 1997-11-24
US08/977,455 1997-11-24

Publications (1)

Publication Number Publication Date
WO1999027723A1 true WO1999027723A1 (en) 1999-06-03

Family

ID=25525139

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/SE1998/002111 WO1999027723A1 (en) 1997-11-24 1998-11-20 Multiple subscriber service profiles per mobile station in a cellular communications system

Country Status (4)

Country Link
AU (1) AU1357799A (en)
BR (1) BR9815427A (en)
CA (1) CA2311367A1 (en)
WO (1) WO1999027723A1 (en)

Cited By (70)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2000041409A2 (en) * 1998-12-30 2000-07-13 Nokia Networks Oy Management of multiple subscriber identities
EP1071301A2 (en) * 1999-07-21 2001-01-24 Siemens Aktiengesellschaft Method for handling mobile services
DE19947077A1 (en) * 1999-09-30 2001-05-10 Siemens Ag Method for operating a communication terminal
WO2001037584A1 (en) * 1999-11-19 2001-05-25 Ericsson Inc. Remote access to telephony service profile
WO2001039483A2 (en) * 1999-11-22 2001-05-31 Nokia Corporation Improving charging efficiency
EP1122967A2 (en) * 2000-02-02 2001-08-08 Lucent Technologies Inc. Flexible access authorization feature to enable mobile users to access services in 3G wireless networks
EP1128695A1 (en) * 2000-02-25 2001-08-29 Alcatel Telecommunication system for managing user-service relationships, as well as method, as well as loadable computer program product, as well as stored computer program product
WO2001063901A1 (en) * 2000-02-24 2001-08-30 Telefonaktiebolaget Lm Ericsson (Publ) Event recording reporting designation downloaded with subscriber profile
GB2365680A (en) * 2000-03-21 2002-02-20 Ericsson Telefon Ab L M Call detail record generation in a telecommunication system
DE10109908A1 (en) * 2001-02-20 2002-08-29 Siemens Ag Method and account management system for billing services performed in a telecommunications network
WO2003017636A1 (en) * 2001-08-14 2003-02-27 Teligent Ab Method of connecting to a data or tele net with a subscription that includes at least two different payment categories
EP1344324A2 (en) * 2000-12-11 2003-09-17 MOTOROLA INC., A Corporation of the state of Delaware Wireless multimode communication with timed affiliation
DE102004038833A1 (en) * 2004-08-10 2006-03-02 Vodafone Holding Gmbh Method and system for managing communication links in a communication network
US7346154B1 (en) 1999-09-02 2008-03-18 Nokia Corporation Customizing prepaid service
WO2009033249A1 (en) * 2007-09-13 2009-03-19 Redknee Inc. Billing profile manager
WO2011136764A1 (en) * 2010-04-28 2011-11-03 Mino Wireless Usa, Inc. System and method for dynamically providing communication profiles for mobile devices
US8160961B1 (en) 1999-09-02 2012-04-17 Nokia Corporation Charging for prepaid subscribers in a telecommunications system
US8553679B2 (en) 2005-11-04 2013-10-08 At&T Intellectual Property I, L.P. Enabling multiple service profiles on a single device
US8634425B2 (en) 2005-11-04 2014-01-21 At&T Intellectual Property I, L.P. Profile sharing across persona
US8788661B2 (en) 2009-01-28 2014-07-22 Headwater Partners I Llc Device assisted CDR creation, aggregation, mediation and billing
US8797908B2 (en) 2009-01-28 2014-08-05 Headwater Partners I Llc Automated device provisioning and activation
US8832777B2 (en) 2009-03-02 2014-09-09 Headwater Partners I Llc Adapting network policies based on device service processor configuration
US8893009B2 (en) 2009-01-28 2014-11-18 Headwater Partners I Llc End user device that secures an association of application to service policy with an application certificate check
US8898293B2 (en) 2009-01-28 2014-11-25 Headwater Partners I Llc Service offer set publishing to device agent with on-device service selection
US8924543B2 (en) 2009-01-28 2014-12-30 Headwater Partners I Llc Service design center for device assisted services
US8924469B2 (en) 2008-06-05 2014-12-30 Headwater Partners I Llc Enterprise access control and accounting allocation for access networks
US9026079B2 (en) 2009-01-28 2015-05-05 Headwater Partners I Llc Wireless network service interfaces
US9094311B2 (en) 2009-01-28 2015-07-28 Headwater Partners I, Llc Techniques for attribution of mobile device data traffic to initiating end-user application
US9137701B2 (en) 2009-01-28 2015-09-15 Headwater Partners I Llc Wireless end-user device with differentiated network access for background and foreground device applications
US9154826B2 (en) 2011-04-06 2015-10-06 Headwater Partners Ii Llc Distributing content and service launch objects to mobile devices
US9198042B2 (en) 2009-01-28 2015-11-24 Headwater Partners I Llc Security techniques for device assisted services
US9204282B2 (en) 2009-01-28 2015-12-01 Headwater Partners I Llc Enhanced roaming services and converged carrier networks with device assisted services and a proxy
US9225797B2 (en) 2009-01-28 2015-12-29 Headwater Partners I Llc System for providing an adaptive wireless ambient service to a mobile device
US9247450B2 (en) 2009-01-28 2016-01-26 Headwater Partners I Llc Quality of service for device assisted services
US9253663B2 (en) 2009-01-28 2016-02-02 Headwater Partners I Llc Controlling mobile device communications on a roaming network based on device state
US9351193B2 (en) 2009-01-28 2016-05-24 Headwater Partners I Llc Intermediate networking devices
US9392462B2 (en) 2009-01-28 2016-07-12 Headwater Partners I Llc Mobile end-user device with agent limiting wireless data communication for specified background applications based on a stored policy
US9491199B2 (en) 2009-01-28 2016-11-08 Headwater Partners I Llc Security, fraud detection, and fraud mitigation in device-assisted services systems
US9532261B2 (en) 2009-01-28 2016-12-27 Headwater Partners I Llc System and method for wireless network offloading
US9557889B2 (en) 2009-01-28 2017-01-31 Headwater Partners I Llc Service plan design, user interfaces, application programming interfaces, and device management
US9565707B2 (en) 2009-01-28 2017-02-07 Headwater Partners I Llc Wireless end-user device with wireless data attribution to multiple personas
US9565543B2 (en) 2009-01-28 2017-02-07 Headwater Partners I Llc Device group partitions and settlement platform
US9572019B2 (en) 2009-01-28 2017-02-14 Headwater Partners LLC Service selection set published to device agent with on-device service selection
US9571559B2 (en) 2009-01-28 2017-02-14 Headwater Partners I Llc Enhanced curfew and protection associated with a device group
US9578182B2 (en) 2009-01-28 2017-02-21 Headwater Partners I Llc Mobile device and service management
US9609510B2 (en) 2009-01-28 2017-03-28 Headwater Research Llc Automated credential porting for mobile devices
US9647918B2 (en) 2009-01-28 2017-05-09 Headwater Research Llc Mobile device and method attributing media services network usage to requesting application
US9706061B2 (en) 2009-01-28 2017-07-11 Headwater Partners I Llc Service design center for device assisted services
US9755842B2 (en) 2009-01-28 2017-09-05 Headwater Research Llc Managing service user discovery and service launch object placement on a device
US9858559B2 (en) 2009-01-28 2018-01-02 Headwater Research Llc Network service plan design
US9954975B2 (en) 2009-01-28 2018-04-24 Headwater Research Llc Enhanced curfew and protection associated with a device group
US9955332B2 (en) 2009-01-28 2018-04-24 Headwater Research Llc Method for child wireless device activation to subscriber account of a master wireless device
US9980146B2 (en) 2009-01-28 2018-05-22 Headwater Research Llc Communications device with secure data path processing agents
US10057775B2 (en) 2009-01-28 2018-08-21 Headwater Research Llc Virtualized policy and charging system
US10064055B2 (en) 2009-01-28 2018-08-28 Headwater Research Llc Security, fraud detection, and fraud mitigation in device-assisted services systems
US10070305B2 (en) 2009-01-28 2018-09-04 Headwater Research Llc Device assisted services install
US10200541B2 (en) 2009-01-28 2019-02-05 Headwater Research Llc Wireless end-user device with divided user space/kernel space traffic policy system
US10237757B2 (en) 2009-01-28 2019-03-19 Headwater Research Llc System and method for wireless network offloading
US10248996B2 (en) 2009-01-28 2019-04-02 Headwater Research Llc Method for operating a wireless end-user device mobile payment agent
US10264138B2 (en) 2009-01-28 2019-04-16 Headwater Research Llc Mobile device and service management
US10326800B2 (en) 2009-01-28 2019-06-18 Headwater Research Llc Wireless network service interfaces
US10492102B2 (en) 2009-01-28 2019-11-26 Headwater Research Llc Intermediate networking devices
US10715342B2 (en) 2009-01-28 2020-07-14 Headwater Research Llc Managing service user discovery and service launch object placement on a device
US10779177B2 (en) 2009-01-28 2020-09-15 Headwater Research Llc Device group partitions and settlement platform
US10783581B2 (en) 2009-01-28 2020-09-22 Headwater Research Llc Wireless end-user device providing ambient or sponsored services
US10798252B2 (en) 2009-01-28 2020-10-06 Headwater Research Llc System and method for providing user notifications
US10841839B2 (en) 2009-01-28 2020-11-17 Headwater Research Llc Security, fraud detection, and fraud mitigation in device-assisted services systems
US11218854B2 (en) 2009-01-28 2022-01-04 Headwater Research Llc Service plan design, user interfaces, application programming interfaces, and device management
US11412366B2 (en) 2009-01-28 2022-08-09 Headwater Research Llc Enhanced roaming services and converged carrier networks with device assisted services and a proxy
US11968234B2 (en) 2021-11-29 2024-04-23 Headwater Research Llc Wireless network service interfaces

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5561706A (en) * 1992-09-29 1996-10-01 Fenner; Peter R. System for managing access by mobile users to an interconnected communications network where a billing authority is identified by a billing code from the user
WO1997030559A1 (en) * 1996-02-20 1997-08-21 Ericsson Inc. Location based screening in a mobile telecommunications system

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5561706A (en) * 1992-09-29 1996-10-01 Fenner; Peter R. System for managing access by mobile users to an interconnected communications network where a billing authority is identified by a billing code from the user
WO1997030559A1 (en) * 1996-02-20 1997-08-21 Ericsson Inc. Location based screening in a mobile telecommunications system

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
SHERBURNE T J ET AL: "TIME ACTIVATED SUBSCRIBER PRIVILEGES", MOTOROLA TECHNICAL DEVELOPMENTS, vol. 25, 1 July 1995 (1995-07-01), pages 59, XP000524341 *

Cited By (196)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2000041409A3 (en) * 1998-12-30 2000-11-02 Nokia Networks Oy Management of multiple subscriber identities
WO2000041409A2 (en) * 1998-12-30 2000-07-13 Nokia Networks Oy Management of multiple subscriber identities
EP1071301A2 (en) * 1999-07-21 2001-01-24 Siemens Aktiengesellschaft Method for handling mobile services
EP1071301A3 (en) * 1999-07-21 2001-08-29 Siemens Aktiengesellschaft Method for handling mobile services
US7346154B1 (en) 1999-09-02 2008-03-18 Nokia Corporation Customizing prepaid service
US8160961B1 (en) 1999-09-02 2012-04-17 Nokia Corporation Charging for prepaid subscribers in a telecommunications system
DE19947077A1 (en) * 1999-09-30 2001-05-10 Siemens Ag Method for operating a communication terminal
DE19947077C2 (en) * 1999-09-30 2002-01-10 Siemens Ag Method for operating a communication terminal
EP1091604A3 (en) * 1999-09-30 2002-03-06 Siemens Aktiengesellschaft Method for operating a communication terminal
WO2001037584A1 (en) * 1999-11-19 2001-05-25 Ericsson Inc. Remote access to telephony service profile
WO2001039483A2 (en) * 1999-11-22 2001-05-31 Nokia Corporation Improving charging efficiency
CN100375493C (en) * 1999-11-22 2008-03-12 诺基亚公司 Improving charging efficiency
US8406731B2 (en) 1999-11-22 2013-03-26 Nokia Corporation Charging efficiency for a mobile subscriber based on pre-paid or flat-rate billing arrangements
WO2001039483A3 (en) * 1999-11-22 2002-04-18 Nokia Networks Oy Improving charging efficiency
US7970376B2 (en) 1999-11-22 2011-06-28 Nokia Corporation Charging efficiency
US7565134B2 (en) 1999-11-22 2009-07-21 Nokia Corporation Charging efficiency
US6975850B1 (en) 1999-11-22 2005-12-13 Nokia Corporation Charging efficiency
EP1122967A3 (en) * 2000-02-02 2002-07-24 Lucent Technologies Inc. Flexible access authorization feature to enable mobile users to access services in 3G wireless networks
US6754482B1 (en) 2000-02-02 2004-06-22 Lucent Technologies Inc. Flexible access authorization feature to enable mobile users to access services in 3G wireless networks
EP1122967A2 (en) * 2000-02-02 2001-08-08 Lucent Technologies Inc. Flexible access authorization feature to enable mobile users to access services in 3G wireless networks
WO2001063901A1 (en) * 2000-02-24 2001-08-30 Telefonaktiebolaget Lm Ericsson (Publ) Event recording reporting designation downloaded with subscriber profile
EP1128695A1 (en) * 2000-02-25 2001-08-29 Alcatel Telecommunication system for managing user-service relationships, as well as method, as well as loadable computer program product, as well as stored computer program product
US7546113B2 (en) 2000-03-21 2009-06-09 Telefonaktiebolaget L M Ericsson (Publ) Transmission of call detail records in a telecommunications system
GB2365680B (en) * 2000-03-21 2004-01-28 Ericsson Telefon Ab L M Transmission of call detail records in a telecommunications system
GB2365680A (en) * 2000-03-21 2002-02-20 Ericsson Telefon Ab L M Call detail record generation in a telecommunication system
EP1344324A4 (en) * 2000-12-11 2005-10-05 Motorola Inc Wireless multimode communication with timed affiliation
EP1344324A2 (en) * 2000-12-11 2003-09-17 MOTOROLA INC., A Corporation of the state of Delaware Wireless multimode communication with timed affiliation
DE10109908A1 (en) * 2001-02-20 2002-08-29 Siemens Ag Method and account management system for billing services performed in a telecommunications network
WO2003017636A1 (en) * 2001-08-14 2003-02-27 Teligent Ab Method of connecting to a data or tele net with a subscription that includes at least two different payment categories
DE102004038833A1 (en) * 2004-08-10 2006-03-02 Vodafone Holding Gmbh Method and system for managing communication links in a communication network
US8553679B2 (en) 2005-11-04 2013-10-08 At&T Intellectual Property I, L.P. Enabling multiple service profiles on a single device
US8634425B2 (en) 2005-11-04 2014-01-21 At&T Intellectual Property I, L.P. Profile sharing across persona
WO2009033249A1 (en) * 2007-09-13 2009-03-19 Redknee Inc. Billing profile manager
US8924469B2 (en) 2008-06-05 2014-12-30 Headwater Partners I Llc Enterprise access control and accounting allocation for access networks
US9609459B2 (en) 2009-01-28 2017-03-28 Headwater Research Llc Network tools for analysis, design, testing, and production of services
US9954975B2 (en) 2009-01-28 2018-04-24 Headwater Research Llc Enhanced curfew and protection associated with a device group
US11923995B2 (en) 2009-01-28 2024-03-05 Headwater Research Llc Device-assisted services for protecting network capacity
US8839387B2 (en) 2009-01-28 2014-09-16 Headwater Partners I Llc Roaming services network and overlay networks
US8839388B2 (en) 2009-01-28 2014-09-16 Headwater Partners I Llc Automated device provisioning and activation
US8886162B2 (en) 2009-01-28 2014-11-11 Headwater Partners I Llc Restricting end-user device communications over a wireless access network associated with a cost
US8893009B2 (en) 2009-01-28 2014-11-18 Headwater Partners I Llc End user device that secures an association of application to service policy with an application certificate check
US8898293B2 (en) 2009-01-28 2014-11-25 Headwater Partners I Llc Service offer set publishing to device agent with on-device service selection
US8897744B2 (en) 2009-01-28 2014-11-25 Headwater Partners I Llc Device assisted ambient services
US8897743B2 (en) 2009-01-28 2014-11-25 Headwater Partners I Llc Verifiable device assisted service usage billing with integrated accounting, mediation accounting, and multi-account
US8898079B2 (en) 2009-01-28 2014-11-25 Headwater Partners I Llc Network based ambient services
US8903452B2 (en) 2009-01-28 2014-12-02 Headwater Partners I Llc Device assisted ambient services
US8924543B2 (en) 2009-01-28 2014-12-30 Headwater Partners I Llc Service design center for device assisted services
US8788661B2 (en) 2009-01-28 2014-07-22 Headwater Partners I Llc Device assisted CDR creation, aggregation, mediation and billing
US8924549B2 (en) 2009-01-28 2014-12-30 Headwater Partners I Llc Network based ambient services
US9014026B2 (en) 2009-01-28 2015-04-21 Headwater Partners I Llc Network based service profile management with user preference, adaptive policy, network neutrality, and user privacy
US9026079B2 (en) 2009-01-28 2015-05-05 Headwater Partners I Llc Wireless network service interfaces
US9037127B2 (en) 2009-01-28 2015-05-19 Headwater Partners I Llc Device agent for remote user configuration of wireless network access
US9094311B2 (en) 2009-01-28 2015-07-28 Headwater Partners I, Llc Techniques for attribution of mobile device data traffic to initiating end-user application
US9137739B2 (en) 2009-01-28 2015-09-15 Headwater Partners I Llc Network based service policy implementation with network neutrality and user privacy
US9137701B2 (en) 2009-01-28 2015-09-15 Headwater Partners I Llc Wireless end-user device with differentiated network access for background and foreground device applications
US9143976B2 (en) 2009-01-28 2015-09-22 Headwater Partners I Llc Wireless end-user device with differentiated network access and access status for background and foreground device applications
US9154428B2 (en) 2009-01-28 2015-10-06 Headwater Partners I Llc Wireless end-user device with differentiated network access selectively applied to different applications
US11757943B2 (en) 2009-01-28 2023-09-12 Headwater Research Llc Automated device provisioning and activation
US9173104B2 (en) 2009-01-28 2015-10-27 Headwater Partners I Llc Mobile device with device agents to detect a disallowed access to a requested mobile data service and guide a multi-carrier selection and activation sequence
US9179316B2 (en) 2009-01-28 2015-11-03 Headwater Partners I Llc Mobile device with user controls and policy agent to control application access to device location data
US9179315B2 (en) 2009-01-28 2015-11-03 Headwater Partners I Llc Mobile device with data service monitoring, categorization, and display for different applications and networks
US9179308B2 (en) 2009-01-28 2015-11-03 Headwater Partners I Llc Network tools for analysis, design, testing, and production of services
US9179359B2 (en) 2009-01-28 2015-11-03 Headwater Partners I Llc Wireless end-user device with differentiated network access status for different device applications
US9198042B2 (en) 2009-01-28 2015-11-24 Headwater Partners I Llc Security techniques for device assisted services
US9198074B2 (en) 2009-01-28 2015-11-24 Headwater Partners I Llc Wireless end-user device with differential traffic control policy list and applying foreground classification to roaming wireless data service
US9198075B2 (en) 2009-01-28 2015-11-24 Headwater Partners I Llc Wireless end-user device with differential traffic control policy list applicable to one of several wireless modems
US9198117B2 (en) 2009-01-28 2015-11-24 Headwater Partners I Llc Network system with common secure wireless message service serving multiple applications on multiple wireless devices
US9198076B2 (en) 2009-01-28 2015-11-24 Headwater Partners I Llc Wireless end-user device with power-control-state-based wireless network access policy for background applications
US9204282B2 (en) 2009-01-28 2015-12-01 Headwater Partners I Llc Enhanced roaming services and converged carrier networks with device assisted services and a proxy
US9204374B2 (en) 2009-01-28 2015-12-01 Headwater Partners I Llc Multicarrier over-the-air cellular network activation server
US9215159B2 (en) 2009-01-28 2015-12-15 Headwater Partners I Llc Data usage monitoring for media data services used by applications
US9215613B2 (en) 2009-01-28 2015-12-15 Headwater Partners I Llc Wireless end-user device with differential traffic control policy list having limited user control
US9220027B1 (en) 2009-01-28 2015-12-22 Headwater Partners I Llc Wireless end-user device with policy-based controls for WWAN network usage and modem state changes requested by specific applications
US9225797B2 (en) 2009-01-28 2015-12-29 Headwater Partners I Llc System for providing an adaptive wireless ambient service to a mobile device
US9232403B2 (en) 2009-01-28 2016-01-05 Headwater Partners I Llc Mobile device with common secure wireless message service serving multiple applications
US9247450B2 (en) 2009-01-28 2016-01-26 Headwater Partners I Llc Quality of service for device assisted services
US9253663B2 (en) 2009-01-28 2016-02-02 Headwater Partners I Llc Controlling mobile device communications on a roaming network based on device state
US9258735B2 (en) 2009-01-28 2016-02-09 Headwater Partners I Llc Device-assisted services for protecting network capacity
US9270559B2 (en) 2009-01-28 2016-02-23 Headwater Partners I Llc Service policy implementation for an end-user device having a control application or a proxy agent for routing an application traffic flow
US9271184B2 (en) 2009-01-28 2016-02-23 Headwater Partners I Llc Wireless end-user device with per-application data limit and traffic control policy list limiting background application traffic
US9277445B2 (en) 2009-01-28 2016-03-01 Headwater Partners I Llc Wireless end-user device with differential traffic control policy list and applying foreground classification to wireless data service
US9277433B2 (en) 2009-01-28 2016-03-01 Headwater Partners I Llc Wireless end-user device with policy-based aggregation of network activity requested by applications
US9319913B2 (en) 2009-01-28 2016-04-19 Headwater Partners I Llc Wireless end-user device with secure network-provided differential traffic control policy list
US9351193B2 (en) 2009-01-28 2016-05-24 Headwater Partners I Llc Intermediate networking devices
US9386121B2 (en) 2009-01-28 2016-07-05 Headwater Partners I Llc Method for providing an adaptive wireless ambient service to a mobile device
US9392462B2 (en) 2009-01-28 2016-07-12 Headwater Partners I Llc Mobile end-user device with agent limiting wireless data communication for specified background applications based on a stored policy
US9491564B1 (en) 2009-01-28 2016-11-08 Headwater Partners I Llc Mobile device and method with secure network messaging for authorized components
US9491199B2 (en) 2009-01-28 2016-11-08 Headwater Partners I Llc Security, fraud detection, and fraud mitigation in device-assisted services systems
US9521578B2 (en) 2009-01-28 2016-12-13 Headwater Partners I Llc Wireless end-user device with application program interface to allow applications to access application-specific aspects of a wireless network access policy
US9532261B2 (en) 2009-01-28 2016-12-27 Headwater Partners I Llc System and method for wireless network offloading
US9544397B2 (en) 2009-01-28 2017-01-10 Headwater Partners I Llc Proxy server for providing an adaptive wireless ambient service to a mobile device
US9557889B2 (en) 2009-01-28 2017-01-31 Headwater Partners I Llc Service plan design, user interfaces, application programming interfaces, and device management
US9565707B2 (en) 2009-01-28 2017-02-07 Headwater Partners I Llc Wireless end-user device with wireless data attribution to multiple personas
US9565543B2 (en) 2009-01-28 2017-02-07 Headwater Partners I Llc Device group partitions and settlement platform
US9572019B2 (en) 2009-01-28 2017-02-14 Headwater Partners LLC Service selection set published to device agent with on-device service selection
US9571559B2 (en) 2009-01-28 2017-02-14 Headwater Partners I Llc Enhanced curfew and protection associated with a device group
US9578182B2 (en) 2009-01-28 2017-02-21 Headwater Partners I Llc Mobile device and service management
US9591474B2 (en) 2009-01-28 2017-03-07 Headwater Partners I Llc Adapting network policies based on device service processor configuration
US11750477B2 (en) 2009-01-28 2023-09-05 Headwater Research Llc Adaptive ambient services
US9609544B2 (en) 2009-01-28 2017-03-28 Headwater Research Llc Device-assisted services for protecting network capacity
US9609510B2 (en) 2009-01-28 2017-03-28 Headwater Research Llc Automated credential porting for mobile devices
US9615192B2 (en) 2009-01-28 2017-04-04 Headwater Research Llc Message link server with plural message delivery triggers
US9641957B2 (en) 2009-01-28 2017-05-02 Headwater Research Llc Automated device provisioning and activation
US9647918B2 (en) 2009-01-28 2017-05-09 Headwater Research Llc Mobile device and method attributing media services network usage to requesting application
US9674731B2 (en) 2009-01-28 2017-06-06 Headwater Research Llc Wireless device applying different background data traffic policies to different device applications
US9705771B2 (en) 2009-01-28 2017-07-11 Headwater Partners I Llc Attribution of mobile device data traffic to end-user application based on socket flows
US9706061B2 (en) 2009-01-28 2017-07-11 Headwater Partners I Llc Service design center for device assisted services
US9749898B2 (en) 2009-01-28 2017-08-29 Headwater Research Llc Wireless end-user device with differential traffic control policy list applicable to one of several wireless modems
US9749899B2 (en) 2009-01-28 2017-08-29 Headwater Research Llc Wireless end-user device with network traffic API to indicate unavailability of roaming wireless connection to background applications
US9755842B2 (en) 2009-01-28 2017-09-05 Headwater Research Llc Managing service user discovery and service launch object placement on a device
US9769207B2 (en) 2009-01-28 2017-09-19 Headwater Research Llc Wireless network service interfaces
US9819808B2 (en) 2009-01-28 2017-11-14 Headwater Research Llc Hierarchical service policies for creating service usage data records for a wireless end-user device
US9858559B2 (en) 2009-01-28 2018-01-02 Headwater Research Llc Network service plan design
US9866642B2 (en) 2009-01-28 2018-01-09 Headwater Research Llc Wireless end-user device with wireless modem power state control policy for background applications
US9942796B2 (en) 2009-01-28 2018-04-10 Headwater Research Llc Quality of service for device assisted services
US8797908B2 (en) 2009-01-28 2014-08-05 Headwater Partners I Llc Automated device provisioning and activation
US9955332B2 (en) 2009-01-28 2018-04-24 Headwater Research Llc Method for child wireless device activation to subscriber account of a master wireless device
US9973930B2 (en) 2009-01-28 2018-05-15 Headwater Research Llc End user device that secures an association of application to service policy with an application certificate check
US9980146B2 (en) 2009-01-28 2018-05-22 Headwater Research Llc Communications device with secure data path processing agents
US10028144B2 (en) 2009-01-28 2018-07-17 Headwater Research Llc Security techniques for device assisted services
US10057775B2 (en) 2009-01-28 2018-08-21 Headwater Research Llc Virtualized policy and charging system
US10057141B2 (en) 2009-01-28 2018-08-21 Headwater Research Llc Proxy system and method for adaptive ambient services
US10064055B2 (en) 2009-01-28 2018-08-28 Headwater Research Llc Security, fraud detection, and fraud mitigation in device-assisted services systems
US10064033B2 (en) 2009-01-28 2018-08-28 Headwater Research Llc Device group partitions and settlement platform
US10070305B2 (en) 2009-01-28 2018-09-04 Headwater Research Llc Device assisted services install
US10080250B2 (en) 2009-01-28 2018-09-18 Headwater Research Llc Enterprise access control and accounting allocation for access networks
US10165447B2 (en) 2009-01-28 2018-12-25 Headwater Research Llc Network service plan design
US10171681B2 (en) 2009-01-28 2019-01-01 Headwater Research Llc Service design center for device assisted services
US10171988B2 (en) 2009-01-28 2019-01-01 Headwater Research Llc Adapting network policies based on device service processor configuration
US11665186B2 (en) 2009-01-28 2023-05-30 Headwater Research Llc Communications device with secure data path processing agents
US10200541B2 (en) 2009-01-28 2019-02-05 Headwater Research Llc Wireless end-user device with divided user space/kernel space traffic policy system
US10237773B2 (en) 2009-01-28 2019-03-19 Headwater Research Llc Device-assisted services for protecting network capacity
US10237146B2 (en) 2009-01-28 2019-03-19 Headwater Research Llc Adaptive ambient services
US10237757B2 (en) 2009-01-28 2019-03-19 Headwater Research Llc System and method for wireless network offloading
US10248996B2 (en) 2009-01-28 2019-04-02 Headwater Research Llc Method for operating a wireless end-user device mobile payment agent
US10264138B2 (en) 2009-01-28 2019-04-16 Headwater Research Llc Mobile device and service management
US10321320B2 (en) 2009-01-28 2019-06-11 Headwater Research Llc Wireless network buffered message system
US10320990B2 (en) 2009-01-28 2019-06-11 Headwater Research Llc Device assisted CDR creation, aggregation, mediation and billing
US10326800B2 (en) 2009-01-28 2019-06-18 Headwater Research Llc Wireless network service interfaces
US10326675B2 (en) 2009-01-28 2019-06-18 Headwater Research Llc Flow tagging for service policy implementation
US10462627B2 (en) 2009-01-28 2019-10-29 Headwater Research Llc Service plan design, user interfaces, application programming interfaces, and device management
US10492102B2 (en) 2009-01-28 2019-11-26 Headwater Research Llc Intermediate networking devices
US10536983B2 (en) 2009-01-28 2020-01-14 Headwater Research Llc Enterprise access control and accounting allocation for access networks
US10582375B2 (en) 2009-01-28 2020-03-03 Headwater Research Llc Device assisted services install
US10681179B2 (en) 2009-01-28 2020-06-09 Headwater Research Llc Enhanced curfew and protection associated with a device group
US10694385B2 (en) 2009-01-28 2020-06-23 Headwater Research Llc Security techniques for device assisted services
US10716006B2 (en) 2009-01-28 2020-07-14 Headwater Research Llc End user device that secures an association of application to service policy with an application certificate check
US10715342B2 (en) 2009-01-28 2020-07-14 Headwater Research Llc Managing service user discovery and service launch object placement on a device
US10749700B2 (en) 2009-01-28 2020-08-18 Headwater Research Llc Device-assisted services for protecting network capacity
US10771980B2 (en) 2009-01-28 2020-09-08 Headwater Research Llc Communications device with secure data path processing agents
US10779177B2 (en) 2009-01-28 2020-09-15 Headwater Research Llc Device group partitions and settlement platform
US10783581B2 (en) 2009-01-28 2020-09-22 Headwater Research Llc Wireless end-user device providing ambient or sponsored services
US10791471B2 (en) 2009-01-28 2020-09-29 Headwater Research Llc System and method for wireless network offloading
US10798252B2 (en) 2009-01-28 2020-10-06 Headwater Research Llc System and method for providing user notifications
US10798558B2 (en) 2009-01-28 2020-10-06 Headwater Research Llc Adapting network policies based on device service processor configuration
US10798254B2 (en) 2009-01-28 2020-10-06 Headwater Research Llc Service design center for device assisted services
US10803518B2 (en) 2009-01-28 2020-10-13 Headwater Research Llc Virtualized policy and charging system
US10834577B2 (en) 2009-01-28 2020-11-10 Headwater Research Llc Service offer set publishing to device agent with on-device service selection
US11665592B2 (en) 2009-01-28 2023-05-30 Headwater Research Llc Security, fraud detection, and fraud mitigation in device-assisted services systems
US10841839B2 (en) 2009-01-28 2020-11-17 Headwater Research Llc Security, fraud detection, and fraud mitigation in device-assisted services systems
US10848330B2 (en) 2009-01-28 2020-11-24 Headwater Research Llc Device-assisted services for protecting network capacity
US10855559B2 (en) 2009-01-28 2020-12-01 Headwater Research Llc Adaptive ambient services
US10869199B2 (en) 2009-01-28 2020-12-15 Headwater Research Llc Network service plan design
US10985977B2 (en) 2009-01-28 2021-04-20 Headwater Research Llc Quality of service for device assisted services
US11039020B2 (en) 2009-01-28 2021-06-15 Headwater Research Llc Mobile device and service management
US11096055B2 (en) 2009-01-28 2021-08-17 Headwater Research Llc Automated device provisioning and activation
US11134102B2 (en) 2009-01-28 2021-09-28 Headwater Research Llc Verifiable device assisted service usage monitoring with reporting, synchronization, and notification
US11190645B2 (en) 2009-01-28 2021-11-30 Headwater Research Llc Device assisted CDR creation, aggregation, mediation and billing
US11190545B2 (en) 2009-01-28 2021-11-30 Headwater Research Llc Wireless network service interfaces
US11190427B2 (en) 2009-01-28 2021-11-30 Headwater Research Llc Flow tagging for service policy implementation
US11219074B2 (en) 2009-01-28 2022-01-04 Headwater Research Llc Enterprise access control and accounting allocation for access networks
US11218854B2 (en) 2009-01-28 2022-01-04 Headwater Research Llc Service plan design, user interfaces, application programming interfaces, and device management
US11228617B2 (en) 2009-01-28 2022-01-18 Headwater Research Llc Automated device provisioning and activation
US11337059B2 (en) 2009-01-28 2022-05-17 Headwater Research Llc Device assisted services install
US11363496B2 (en) 2009-01-28 2022-06-14 Headwater Research Llc Intermediate networking devices
US11405429B2 (en) 2009-01-28 2022-08-02 Headwater Research Llc Security techniques for device assisted services
US11405224B2 (en) 2009-01-28 2022-08-02 Headwater Research Llc Device-assisted services for protecting network capacity
US11412366B2 (en) 2009-01-28 2022-08-09 Headwater Research Llc Enhanced roaming services and converged carrier networks with device assisted services and a proxy
US11425580B2 (en) 2009-01-28 2022-08-23 Headwater Research Llc System and method for wireless network offloading
US11477246B2 (en) 2009-01-28 2022-10-18 Headwater Research Llc Network service plan design
US11494837B2 (en) 2009-01-28 2022-11-08 Headwater Research Llc Virtualized policy and charging system
US11516301B2 (en) 2009-01-28 2022-11-29 Headwater Research Llc Enhanced curfew and protection associated with a device group
US11533642B2 (en) 2009-01-28 2022-12-20 Headwater Research Llc Device group partitions and settlement platform
US11538106B2 (en) 2009-01-28 2022-12-27 Headwater Research Llc Wireless end-user device providing ambient or sponsored services
US11563592B2 (en) 2009-01-28 2023-01-24 Headwater Research Llc Managing service user discovery and service launch object placement on a device
US11570309B2 (en) 2009-01-28 2023-01-31 Headwater Research Llc Service design center for device assisted services
US11582593B2 (en) 2009-01-28 2023-02-14 Head Water Research Llc Adapting network policies based on device service processor configuration
US11589216B2 (en) 2009-01-28 2023-02-21 Headwater Research Llc Service selection set publishing to device agent with on-device service selection
US8832777B2 (en) 2009-03-02 2014-09-09 Headwater Partners I Llc Adapting network policies based on device service processor configuration
WO2011136764A1 (en) * 2010-04-28 2011-11-03 Mino Wireless Usa, Inc. System and method for dynamically providing communication profiles for mobile devices
US9154826B2 (en) 2011-04-06 2015-10-06 Headwater Partners Ii Llc Distributing content and service launch objects to mobile devices
US10834583B2 (en) 2013-03-14 2020-11-10 Headwater Research Llc Automated credential porting for mobile devices
US10171995B2 (en) 2013-03-14 2019-01-01 Headwater Research Llc Automated credential porting for mobile devices
US11743717B2 (en) 2013-03-14 2023-08-29 Headwater Research Llc Automated credential porting for mobile devices
US11968234B2 (en) 2021-11-29 2024-04-23 Headwater Research Llc Wireless network service interfaces
US11966464B2 (en) 2022-07-18 2024-04-23 Headwater Research Llc Security techniques for device assisted services

Also Published As

Publication number Publication date
BR9815427A (en) 2001-12-26
CA2311367A1 (en) 1999-06-03
AU1357799A (en) 1999-06-15

Similar Documents

Publication Publication Date Title
WO1999027723A1 (en) Multiple subscriber service profiles per mobile station in a cellular communications system
US5953673A (en) Method of establishing a connection between a calling subscriber of a telecommunications network and a called mobile target subscriber of a mobile radio network
EP0926910B1 (en) Method and apparatus for providing calling number identification alias in a communications system
US5774533A (en) Method and system for providing a billing directed communication service
CA2274821C (en) Providing location-based call forwarding within a mobile telecommunications network
FI111676B (en) Company transport system
US5729598A (en) Telephone network with telecommuting features
IL135420A (en) Method for arranging transaction based billing for telephone services
US6032043A (en) Home location register feature dispatching and arbitration in a wireless intelligent network
KR19990081935A (en) Combined home location registers and service control points for cellular networks
US6654599B1 (en) Call charges in a telecommunications network
JP3993767B2 (en) Feature interaction
WO1998025390A2 (en) Network operator controlled usage of long distance carriers
EP1040697A1 (en) Procedure and system for setting up a telecommunication connection
EP0872107B1 (en) Procedure and system for the setting up of calls
US6366660B1 (en) Apparatus, method and system for providing variable alerting patterns for multiple leg telecommunication sessions
WO2001022657A1 (en) Triggering of intelligent network service
CA2519807C (en) Method for determining charges in real time for value-added services in a telecommunication network
US7903799B1 (en) Method and apparatus for providing a communications service feature for a communication through a network
FI109388B (en) A method for providing and communicating abnormally charged calls
CA2241107C (en) Procedure and system for the setting up of calls
Ashitey et al. Intelligent personal communication system
CA2179792A1 (en) System and method for shared billing of telephone calls
JPH06339176A (en) Public digital cordless telephone system

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AL AM AT AU AZ BA BB BG BR BY CA CH CN CU CZ DE DK EE ES FI GB GD GE GH GM HR HU ID IL IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MD MG MK MN MW MX NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT UA UG UZ VN YU ZW

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): GH GM KE LS MW SD SZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
ENP Entry into the national phase

Ref document number: 2311367

Country of ref document: CA

Ref country code: CA

Ref document number: 2311367

Kind code of ref document: A

Format of ref document f/p: F

NENP Non-entry into the national phase

Ref country code: KR

REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

122 Ep: pct application non-entry in european phase