Software HLR architecture

• US 6,351,646 B1
• Filed: 04/20/1998
• Issued: 02/26/2002
• Est. Priority Date: 06/23/1997
• Status: Expired due to Term

• Current Assignee: Telefonaktiebolaget LM Ericsson
• Original Assignee: Telefonaktiebolaget LM Ericsson
• Inventors: Nguyen, Viet, Tom, Wayne, Jellema, Bart
• Primary Examiner(s): Vo, Nguyen T.
• Assistant Examiner(s): Nguyen, Duc
• Application Number:
  US09/062,713
• Time in Patent Office: 1,408 Days
• Field of Search: 455/461, 455/426, 455/433, 455/435, 455/422, 455/560, 455/462, 455/465, 455/459, 455/414, 379/211, 379/201, 379/207, 379/208
• US Class Current: 455/461
• CPC Class Codes: H04Q 2213/1305 Software aspects
• CPC Class Codes: H04Q 2213/13098 Mobile subscriber
• CPC Class Codes: H04Q 2213/13136 Collect call information service H04Q2213/13376
• CPC Class Codes: H04Q 2213/13176 Common channel signaling, CCS7
• CPC Class Codes: H04Q 2213/13204 Protocols
• CPC Class Codes: H04Q 2213/13256 Call screening
• CPC Class Codes: H04Q 2213/13331 Abbreviated dialling
• CPC Class Codes: H04Q 2213/13345 Intelligent networks, SCP
• CPC Class Codes: H04Q 3/0058 using service-independent building blocks (SIBBs) or "primitives"

Abstract

A service control point for a mobile telecommunication network is disclosed. In contrast to traditional networks employing a home location register and a service control function, in which traditionally home registration functions reside in the home register entity and intelligent network service functions reside in the service control functional entity, the present invention at least somewhat consolidates these entities and divides their functional activities in accordance with the efficiencies provided by flexible logic structures versus fixed logic structures.

Claims

1. A node on a mobile radio communication network, comprising:

a single service logic functional entity to provide both service control and mobility management functions to said mobile radio communication network, said service logic functional entity comprising a fixed software program, a flexible software program different from the fixed software program, and a dispatcher to route service requests to one of the fixed or flexible software programs based on a predefined configuration table, said flexible software identifying messages received by the single service logic functional entity as preferably executed by one or the other of said flexible and fixed software programs, program including a service logic execution environment which retrieves building blocks of service logic routines from a building block library in said single service logic functional entity and executes said routines on service require signals;

a network interface functional entity to provide communication interconnection between the single service logic functional entity and the remainder of the mobile radio communication network; and

a database access functional entity to provide data values to both said fixed logic entity and said flexible logic entity.

2. A node on a mobile radio communication network according to claim 1, wherein:

the flexible logic entity further includes mobility management service logic routines.

3. A node on a mobile radio communication network according to claim 2, wherein:

the fixed logic entity also includes mobility management service logic routines different from those of said flexible logic entity.

4. A method of providing intelligent network services in a mobile radio communication network, comprising the steps of:

1) providing service logic for executing mobility management functions and service control functions, said service logic divided into fixed logic and flexible logic, said flexible logic employing service logic building blocks of predefined logic routines;

2) configuring service types into a table identifying said service types as either fixed logic types or flexible logic types;

3) retrieving a service request at a single node having both said fixed logic and said flexible logic;

4) identifying the retrieved service request as either a fixed logic type or a flexible logic type based on said table of step

     2);

5) routing said retrieved service request to said fixed logic if said retrieved service request is identified as a fixed logic type in step

     4) or to said flexible logic if said retrieved service request is identified as a flexible logic type in step

     4);

6) identifying any data variables required by said service logic to which said retrieved service request is routed in step

     5) and retrieving any said data variable from a commnon database functional entity;

7) executing said service logic to which said retrieved service request is routed in step

     5); and

8) providing call handling information to said mobile radio communication network based on the outcome of step

     7).