Classifications

• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04Q—SELECTING
  • H04Q1/00—Details of selecting apparatus or arrangements
  • H04Q1/02—Constructional details
  • H04Q1/10—Exchange station construction
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04Q—SELECTING
  • H04Q3/00—Selecting arrangements
  • H04Q3/42—Circuit arrangements for indirect selecting controlled by common circuits, e.g. register controller, marker
  • H04Q3/54—Circuit arrangements for indirect selecting controlled by common circuits, e.g. register controller, marker in which the logic circuitry controlling the exchange is centralised
  • H04Q3/545—Circuit arrangements for indirect selecting controlled by common circuits, e.g. register controller, marker in which the logic circuitry controlling the exchange is centralised using a stored programme
  • H04Q3/54508—Configuration, initialisation
  • H04Q3/54525—Features introduction
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04Q—SELECTING
  • H04Q3/00—Selecting arrangements
  • H04Q3/0016—Arrangements providing connection between exchanges
  • H04Q3/0029—Provisions for intelligent networking
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04Q—SELECTING
  • H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
  • H04Q2213/13517—SLEE - service logic execution
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04Q—SELECTING
  • H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
  • H04Q2213/13532—Indexing scheme relating to selecting arrangements in general and for multiplex systems mobile networks

Definitions

• the present invention relates generally to communication systems, and more particularly, to switching systems for radiotelephone communication systems and to a method of providing services in a radiotelephone communication system.
• Communication systems are well known and consist of many types including land mobile radio, cellular radiotelephone, personal communication system (PCS), and other communication system types.
• PCS personal communication system
• a number of communication cells serviced by base transceiver stations (BTS), are typically linked to a base station controller (BSC).
• BSCs are, in turn, linked to mobile switching centers (MSCs) which provide a connection between the cellular radiotelephone communication system and the public switched telephone network (PSTN) as well as interconnection of various cellular radiotelephone communication systems.
• MSCs mobile switching centers
• PSTN public switched telephone network
• BTS BTS, BSC and MSC to complete a communication transaction with a land line telephone user connected to the PSTN or to another mobile.
• the MSC of a radiotelephone communication system is typically a complex system integrating telephony switching elements with radiotelephone communication system specific aspects such as signaling, control, etc. These systems are complex to build, to maintain and to upgrade.
• the hardware and software architecture of such radiotelephone switching systems require subscribers services functionally integrated into the proprietary operating software of the MSC.
• To add to, upgrade or otherwise change the ability of the MSC to provide subscriber services requires changes in the MSC operating software, usually at considerable expense and development time. Because of this, the addition of software features for providing enhanced services to the system subscribers is severely limited.
• SCP service control point
• SLM service logic modules
• SCP i.e., a stable platform that seldom changes.
• SLMs i.e., a stable platform that seldom changes.
• IPs intelligent peripherals
• FIG. 1 is block diagram of an exemplary cellular radiotelephone communication system which may incorporate the present invention
• FIG. 2 is block diagram of a radiotelephone switching system in accordance with a preferred embodiment of the present invention
• FIG. 3 is, in accordance with a preferred embodiment of the present invention, a functional block diagram of the service control point processor of FIG. 2;
• FIG. 4 is a bubble diagram illustrating the functional inter- relationship of elements in accordance with a preferred embodiment of the present invention of the service control point processor of FIG. 2;
• FIG. 5 is a block diagram illustrating service action trigger dispatching in accordance with a preferred embodiment of the present invention
• FIG. 6 is a block diagram illustrating effective subscriber service provisioning determination in accordance with a preferred embodiment of the present invention
• FIG. 7 is a block diagram illustrating effective subscriber service status determination in accordance with a preferred embodiment of the present invention.
• FIG. 8 is a block diagram illustrating digit pre-translation in accordance with a preferred embodiment of the present invention.
• FIG. 9 is a bubble diagram illustrating functional inter ⁇ relationship of elements of the service control point processor of FIG. 2 in accordance with a preferred embodiment of the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT(S)
• the present invention provides a radiotelephone switching system and a method of providing subscriber services within a radiotelephone communication system.
• a switch typical of switches presently used in a telephone communication systems, is coupled to a processing platform for enhancing its functional capabilities.
• the processing platform includes a trigger manager for accessing a plurality of service modules designed to provide services, typically provided within proprietary processing software of the MSC, to the subscribers /users of the radiotelephone communication system.
• the trigger manager provides for provisioning of services and intelligent dispatch of triggers within the switching system. Additional services and features may be added to the radiotelephone communication system at any time by simply adding additional service modules.
• numerous service modules may be developed and implemented independent of any proprietary processing associated with the switch. Moreover, redundant provisioning of services in multiple systems is not required to provide seamless services to roaming subscribers.
• the radiotelephone communication system 100 includes a plurality of BTSs 21 - 23 serviced by BSCs 31 - 33 as shown which makes up the base station system (BSS) 50.
• BSCs 31 - 33 are coupled to an MSC 60 which in turn is coupled to the PSTN 70.
• Mobile communication units (one of which is shown as mobile 80) operate in communication cells serviced by BTSs 21 - 23 and communicate with BTSs 21 - 23 via radio links in a known manner. Calls originating with or terminating at mobile 80 are processed through MSC 60 to either a wireline telephone customer linked to
• MSC 60 includes a switching system (switch) 110 coupled to a service control point (SCP) processing platform 112 via signaling links 114.
• Switch 110 may consist of a switching system commonly employed in radiotelephone communication systems, or may comprise a Class 5 telephony switch incorporating intelligent networking (IN) capabilities.
• SCP 112 may be any suitable processing platform. Signaling between SCP 112 and switch 110 is preferably according to a standard protocol such as Interim Standard (IS - 41) published by EIA/TIA, or the distributed mobile exchange (DMX) protocol and enhanced versions thereof available from Motorola, Inc., Cellular Infrastructure Group, 1501 W. Shure Drive, Arlington Heights, Illinois 60004.
• IS - 41 Interim Standard
• DMX distributed mobile exchange
• IPs 130 are also linked to switching system 110 via voice/data trunk 116 and to processing platform 112 via signaling link 118.
• Signaling link 118 in a preferred embodiment is a transmission control protocol /internet protocol (TCP/IP) based voice response interface (VRI) protocol, while voice/data trunk 116 is any voice/data trunk including Tl, fiber optic, etc.
• TCP/IP transmission control protocol /internet protocol
• VRI voice response interface
• SCP 112 the elements of SCP 112 are shown, generally in hierarchical relationship, to include a core processor 120 coupled to a call model processor 122 and an interface 124.
• SCP 112 further includes a trigger manager 126 coupled to both call model processor 122 and interface 124. Coupled to both trigger manager 126 and interface 124 are a plurality of service modules 128 which provide the functions for implementing subscriber services in radiotelephone communication system 100.
• core processor 120 is coupled directly to a plurality of IPs one of which is shown at 130 via signaling link 118 and by voice/data trunk 116 to switch 110.
• Core processor 120 is also coupled to a database system 132 which stores, among other things, the radiotelephone communication system and subscriber provisioning and status information as will be described.
• core processor In addition to interfacing with IPs 130, switch 110 and database 132, core processor
• TCAP transaction context management and transactions capabilities applications part
• SS7 signaling system 7
• Call model processor 122 in the preferred embodiment, is a finite state machine which maps the interface protocol on link 118, i.e., DMX call processing messages, into the Bellcore Advanced Intelligent Network (AIN) call model. At certain states, processing is suspended by call model processor 122 and trigger manager 124 is activated for providing specialized services or features. Trigger manager 124 provides for implementing subscriber services through intelligent instruction and dispatch of event triggers and service action triggers to the SLMs 128.
• FIG. 4 shows the inter- relationship of functional elements within switching system 110 for providing call processing.
• Central is the call process related function 200 which as noted above in a preferred embodiment is the Bellcore AIN call model.
• the Bellcore AIN call model is the Bellcore AIN call model.
• trigger enhancements to the Bellcore call model are made possible through implementation of the present invention and are described below.
• Additional elements are the digit pre-translation function 202 and non- call process related function 204.
• Trigger dispatch event function 206 is responsible for converting an event trigger into a prioritized list of potential service actions.
• the service action list is generated from the service definition table 214 which is accessed in an associative manner with an event trigger identification (ID) and is communicated to service action dispatch function 208.
• service action dispatch function 208 provides for dispatching service action triggers, i.e. dispatching triggers to SLMs, based upon the service action list, information in the service switch table 216 and effective subscriber service indicators.
• This information provides service action dispatch function 208 with a basis for determining whether a service action trigger should be dispatched, i.e., whether the service is provisioned, its status is active and the service action is invoked.
• service action triggers are dispatched according to the criteria contained in Table I below.
• the effective subscriber service indicators include effective subscriber provisioning indicators and effective subscriber service status indicators which are generated by determine service status function 210.
• Service action dispatch function 208 also utilizes service scope, service ID and service action ID information for identifying SLM triggers within service switch table 216. Service action dispatch function 208 continues to dispatch service actions, i.e., SLM triggers, until the service action list is exhausted or an SLM returns a trigger response other than continue.
• service dispatch function Upon exhausting the service action list or receiving an other than continue trigger response from an SLM, service dispatch function provides a trigger response to call process function 202. This trigger response is either continue, if all service actions on service action list are exhausted or the non-continue trigger response from an SLM.
• the service definition table contains service scope, service ID, service name, service mnemonic, service priority, service state handling, and trigger event list fields.
• the service scope field defines the level at which the service is provisioned. That is, if
• the service is a system level service applicable to all subscribers or a subscriber level service provisioned individually to all subscribers.
• the service ID, service name and service mnemonic fields provide means for identifying a particular service.
• the service priority field contains data which provides for determining an order in which service actions are dispatched in response to a common event trigger.
• the service state handling field contains data used to specify the type of state handling the service employs, either active or variable.
• the trigger event list contains the trigger events which a particular service need for operation.
• the trigger event list also contains the event ID and service action ID which may be one of the following: Activation, Deactivation, Registration, Erasure, Interrogation, Invocation, Service Specific 1 or Service Specific 2.
• trigger dispatch function 206 uses the event trigger ID to identify the service actions associated with a particular event trigger.
• the service priority data is then used to order, in a prioritized fashion, the service actions into the potential service actions list which is then communicated to the service action dispatcher 208.
• Determine service status function 210 calculates the effective subscriber service provisioning and status indicators which are required for proper support of SLM execution and call processing.
• feature provisioning information is combined from a field of the system profile 230 and a field of the subscriber profile 232 to determine an effective subscriber service provisioning indicator 240.
• duplicate provisioning of subscriber features in both subscriber profile 232 and in a feature package table 234 allows for continued use of feature packages.
• System profile 230 provides a centralized means for provisioning services on a system wide basis, while subscriber profile 232 and feature package table 234 provide means for provisioning services on a per subscriber basis.
• Exemplary effective subscriber provisioning indicators are indicated in Table II above.
• subscriber service status information is combined to provide an effective subscriber service status indicator 242.
• such information includes subscriber service status information from a field in the system profile 232, per call subscriber service status information from a field in the subscriber profile 234, subscriber service status handling information from a call occurrence field 236 and subscriber service status indicators from service definition table 214.
• Exemplary effective subscriber service status indicators are indicated in Table III.
• the SLMs In response to a service action trigger from service action dispatch function 208, the SLMs perform various functions in support of subscriber services and features. These include causing a forward or a redirect of a terminating call, paging a mobile subscriber, initiating call waiting, etc. Under normal conditions an SLM will provide a trigger response of continue, which indicates that the call process function 202 should continue without regard to the SLM processing, or another response instructing the call process function 202 to take some action with respect to the current call. A failure response may also be returned indicating that a general failure occurred during processing of the service action.
• Pre-translation function 202 is also provided within switching system 110.
• Pre-translation function 202 converts the subscriber originating class of service (OCOS) to a dialing plan 252 through the use of an OCOS conversion table 254.
• the subscriber OCOS is retrieved from a field within subscriber profile 232.
• the dialing plan ID and any collected digits, i.e., digits input by the subscriber in addition to the requesting a service, are matched to an entry in the pre- translation/dialing plan table 252.
• the entry in the table identifies either a trigger event ID which is communicated to trigger event dispatch function 206 or a service action which is communicated to service action dispatch function 208 for appropriate action.
• SCP 112 through trigger manager 126 further provides for maintaining statistics on services used 260, and one messaging with switch 110. This is accomplished through dispatch of appropriate triggers to statistic SLMs for updating theses statistics.
• Triggers 1202 and 2202 provide for call origination and termination, respectively, in accordance with the Bellcore call model.
• Trigger 3202 provides for autonomous registration of the mobile subscriber in radiotelephone communication system 100.
• call process function Upon receipt of a I_ROAM_UPDATE message, call process function generates an autonomous registration trigger event which is communicated to trigger event dispatch function 206 of trigger manager 124.
• trigger manager 124 will cause the dispatch of service actions to the appropriate SLM for registering the mobile subscriber in radiotelephone system 100. If registration is successful, the mobile subscribers status is updated in the subscriber status table 238 by the SLM and a continue is returned as the trigger response. Similarly, such additional services as feature update 4202 and remote feature update 5202 are implemented via the addition of appropriate triggers within call process function 202 and SLMs.
• Trigger manager 124 provides for prioritization and provisioning of subscriber services on a per subscriber basis and without requiring redundant provisioning in multiple systems. Moreover, subscriber features and services are easily added to a system without extensive costs and delays for development.

Landscapes

• Engineering & Computer Science (AREA)
• Computer Networks & Wireless Communication (AREA)
• Mobile Radio Communication Systems (AREA)
• Circuits Of Receivers In General (AREA)

Applications Claiming Priority (3)

Publications (1)

Family

ID=23796474

Family Applications (1)

Country Status (9)

Families Citing this family (4)

Family Cites Families (1)

• 1996
  • 1996-04-18 AU AU60221/96A patent/AU6022196A/en not_active Abandoned
  • 1996-04-18 CN CN96190396A patent/CN1152388A/zh active Pending
  • 1996-04-18 CA CA002194785A patent/CA2194785A1/en not_active Abandoned
  • 1996-04-18 EP EP96917805A patent/EP0776578A1/en not_active Withdrawn
  • 1996-04-18 JP JP8535652A patent/JPH10503638A/ja active Pending
  • 1996-04-18 WO PCT/US1996/005347 patent/WO1996038009A1/en not_active Application Discontinuation
  • 1996-04-18 KR KR1019970700510A patent/KR970705311A/ko not_active Application Discontinuation
  • 1996-05-03 IL IL11814596A patent/IL118145A0/xx unknown
  • 1996-12-30 FI FI965256A patent/FI965256A/sv not_active Application Discontinuation

Non-Patent Citations (1)

Also Published As

Similar Documents

Legal Events