Classifications

• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
  • H04W80/08—Upper layer protocols
  • H04W80/12—Application layer protocols, e.g. WAP [Wireless Application Protocol]
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
  • H04W88/14—Backbone network devices

Definitions

• the invention relates to a service user, often referred to in the standards as a Mobile Application Part-User (MAP- User) for a mobile telecommunications system.
• MAP-User is the equivalent of an application program in a data processing system in that it provides the top-level processing for a particular function. More often than not, it will interact with a signalling system of a mobile system via a MAP-Provider and a signalling system stack. It may, for example, form part of a network access processor (NAP) of a home location register (HLR) .
• NAP network access processor
• HLR home location register
• the applications are many and it may perform short message service centre (SMSC), visitor location register (VLR) , or authentication centre (AuC) processing.
• SMSSC short message service centre
• VLR visitor location register
• AuC authentication centre
• MAP-Users have been implemented as integrated code within a larger system, for example, a HLR as described in WO 95/28812 (L. M. Ericsson). While such a MAP-User generally operates quite effectively, they sometimes suffer from the problems of being difficult to modify or upgrade, and secondly there is a long lead time in development.
• a service user for a mobile telecommunications system comprising:-
• a core comprising means for processing transaction messages; and a plurality of handlers connected to the core for communication with external entities.
• the service user further comprises a signal interface connected between the core and each handler.
• said handlers include an API comprising means for connecting the core to a service provider which is in turn connected to a signalling system.
• the service user further comprises a management handler connected to the core for communication with a management system entity of the system, and preferably also comprises a database handler for connecting the core to a database system, and preferably further comprises an authentication centre handler for connecting the core to an authentication centre entity.
• the user comprises means for creating Inter-Process Communication binding the core to the handlers during operation of the service user.
• the core comprises means for creating a finite state machine instance for each transaction.
• the core comprises a finite state machine distributor instance which remains active throughout operation of the service user and comprises means for initiating a transaction.
• the distributor comprises means for activating a responde instance for receiving signals from a signalling system, and an initiator instance comprising means fo transmitting signals to the signalling system.
• the service user furthe comprises a threshold controller finite state machine instance which is created at start-up and remains active during operation of the service user and which comprises means for monitoring operation of the core.
• the distributor, the initiators, and the responders comprise means for updating the threshold controller with status information indicating operation of the core.
• the management handler comprises means for start-up and shut-down of the database and authentication centre handlers.
• the management handler comprises means for connecting and disconnecting the core from a service provider external entity.
• the management handler comprises means for initialisation and on-line configuration of the service user global parameters.
• Fig. 1 is a diagrammatic representation of a service user of the invention and the environment in which it is connected; 4 -
• Fig. 2 is a diagram illustrating construction of the service user
• Fig. 3 is a more detailed diagram illustrating construction of the service user.
• a service user hereinafter referred to as a MAP-User 1 is shown in a GSM environment.
• the GSM system comprises an SS7 signalling system 2 connected to various system entities including a VLR, an MSC and an SMSC.
• the system comprises an SS7 stack 3 which interfaces between the signalling system 2 and a MAP- Provider 4.
• the MAP-User 1 is connected to the MAP- Provider 4 and comprises a database 5.
• the MAP-User 1 is connected to user systems including an AuC 7 and a management system 6.
• MAP-User of the invention may be connected in a variety of different contexts, including providing some of the core control programs for a HLR.
• the MAP-User 1 comprises a core 10 connected on one side via a MAP-Provider -signal interface 15 and a MAP-Provider API 16 to the MAP-Provider 4.
• the core 10 is connected via a management signal interface 21 to a management handler 22, via a database signal interface 19 with a database handler 20, and via an AUC signal interface 17 with an AuC handler 18.
• the handlers 18, 20 and 22 are connected to an AuC system, a database system, and a management system, respectively.
• the core 10 does not store data or code relating to operation of the external entities - it simply interacts with the handlers so that operation of the external entities is transparent to it.
• the core 10 comprises a distributor 11, a threshold handler 12, a plurality of responders 13, and a plurality of initiators 14.
• the core 10 operates according to a finite state machine mechanism, whereby there is one instance of the finite state machine (FSM) for each transaction.
• the distributor 11 manages creation of an instance, whereas the threshold controller 12 manages the operational state of the core 10 and reports events regarding thresholds to the management handler 22.
• the responders 13 handle requests from the network, while the initiators 14 issue requests to the network.
• the distributor 11 is effectively the manager of the other handlers within the core 10 and it is an FSM instance which is created on start-up and remains in place throughout operation of the core 10.
• the distributor in effect creates the responder and initiator instances when a particular signal is received. For example, when the distributor 11 receives a request from the MAP-Provider, it creates an instance of a responder 13, which in turn sends a response to the MAP-Provider. All subsequent messages from the MAP-Provider 4 are then directed to that responder 13.
• the instances are implemented by SDL code routines. Operations initiated by the management handler 22 cause the creation of an initiator 14, which issues requests to the network.
• a responder or initiator 13 or 14 is responsible for a whole transaction or dialogue. They are programmed to receive, process, lock or shut down signals at any waiting state.
• a responder 13 can invoke one of the following routines or macros:-
• NetworkLocUpd handles location updating and data restoration operations
• LocInfoRetrieval handles requests for location information
• InfoRetrieval handles requests for authentication/subscriber details
• VLRReset handles receipt of resets from a VLR
• NetworkFunctionalSs- handles receipt of signalling system (SS) operations
• NetworkUnstructuredSs- handles receipt of unstructured SS operations
• ShortMsgGateway handles SMS routing requests
• MwdMgt - handles requests for message waiting data operations.
• the initiator 14 is programmed to invoke one of the following routines or macros:- LocationCancellation - handles issuing of cancel Locations;
• HLRReset handles the issuing of resets to VLRs at startup
• SubscriberDataMngt handles issuing of standalone ISDs/DSDs
• SubTracing - handles issuing of standalone tracing activation/deactivation
• ShortMsgAlert- handles issuing of SMS alerts.
• the threshold controller 12 keeps track of the number of transactions or dialogues and each time one is created or halts, an appropriate signal is sent to the threshold controller 22. If there are too many the dialogue is not allowed to be started.
• routines for receiving incoming messages with either ind or cnf, representing an indication (received request) or a confirmation (received response) respectively.
• routines for sending outgoing messages are postfixed with either req. or rsp. , representing request or response respectively.
• a system services function 23 handles the IPC sockets and ensures that they are not blocked.
• management handler 22 the implementation is dependent on the management entity but it is capable of interfacing with the core 10 using a protocol defined by the management signal interface 21.
• the management handler 22 provides the following functionality:-
• the signal interface 21 is defined using SDT signals and all signals sent by the handler 22 to the core 10 are handled by the distributor.
• the database handler 20 provides the core 10 and the other external handlers 18 and 22 with a means to access the database 5 shown in Fig. 1.
• the implementation is dependent on the nature of the database 5, but it must be capable of interfacing with the core 10 using the protocol defined in the database signal interface 19.
• An important aspect is the fact that the core 10 does not make specific decisions regarding locking of objects in the database 5 - it will simply request whatever data it needs for a particular operation. Accordingly, the core 10 is separated from the low-level database operations.
• the core Due to the size of some of the objects retrieved from the database (using db_access, the average subscriber occupies about 2K), it would be expensive to pass these structures in SDL signals. This is because when the core receives a DB_DATA signal from the database handler, its contents would generally be copied to a local variable (in order that it can be accessed for the remainder of the process, even though the signal is freed upon completion of the immediate transition) . Therefore the DB_DATA signal contains a pointer to an area of memory containing the information. This memory is maintained by the database handler. The core may access this as it pleases (but not change it) . When the core has finished with the memory, it uses the DB_FINISH signal to indicate this to the database handler.
• the database handler creates a separate process to handle each database request. This new process declares a local variable which will hold the retrieved data. It is the address of this local variable which is passed to the Core MAP User in the DB_DATA signal.
• this provides the core 10 with the ability to request authentication triplets from an authentication centre.
• the core 10 will request a set of five triplets each time it receives an authentication request.
• the invention provides a service user which is configured largely independently of external entities at a low level.
• the handlers and signal interfaces isolate the core from the external entity low- level operation.
• the MAP-User may be easily ported and quickly re-configured for different uses or for similar uses interacting with different external entities. For example, if the MAP-User is to be changed for use with a different AuC entity, it is only necessary to modify the AuC handler 18.
• the invention is not limited to the embodiments hereinbefore described, but may be varied within the scope of the claims in construction and detail.

Landscapes

• Engineering & Computer Science (AREA)
• Computer Networks & Wireless Communication (AREA)
• Signal Processing (AREA)
• Mobile Radio Communication Systems (AREA)

Applications Claiming Priority (7)

Publications (1)

Family

ID=27270505

Family Applications (1)

Country Status (4)

Families Citing this family (3)

• 1997
  • 1997-03-27 EP EP97916626A patent/EP0890276A1/de not_active Withdrawn
  • 1997-03-27 IE IE970241 patent/IES73870B2/en not_active IP Right Cessation
  • 1997-03-27 WO PCT/IE1997/000028 patent/WO1997036440A1/en not_active Ceased
  • 1997-03-27 AU AU25207/97A patent/AU2520797A/en not_active Abandoned
  • 1997-03-27 IE IE970240A patent/IE970240A1/en not_active IP Right Cessation

Non-Patent Citations (1)

Also Published As

Similar Documents

Legal Events