Telefonaktiebolaget Lm Ericsson (publ)

Margaret Britt

Nadia Bishai

Jacques Bugnon

Binh Nguyen

Susan Anctil

Hanh Duy Vo

Pietro Fionda

Marco Antonio Vargas

Phat M Nguyen

Giuseppe Bruzzese

A method in a Wireless Intelligent Network (WIN) of handling subscriber services when a serving Mobile Switching Center (MSC) does not support all WIN triggers. The WIN includes a Home Location Register (HLR) having a subscriber profile that indicates the WIN triggers required to support a particular subscriber's active services. When an invoke message is sent from the MSC to the HLR, a WIN Capabilities (WINCAP) parameter is included and indicates the WIN triggers supported by the MSC. The HLR identifies a Service Control Point (SCP) for each subscriber service that requires a WIN trigger and is not supported by the MSC. The HLR then queries each identified SCP for call-treatment instructions. If an SCP determines that its service is essential, a response is returned to the HLR with an instruction to deny service to the subscriber. If an SCP determines that its service is not essential, a response is returned to the HLR with an instruction to skip the unsupported service and allow basic services to the subscriber. The HLR collates the responses and determines a call-treatment response to return to the MSC.

Method of handling subscriber services in a wireless intelligent network

A method of supporting functionality for roamer port calls in a radio telecommunications network in which Number Portability (NP) is implemented, the network having a plurality of mobile switching centers (MSCs) and home location registers (HLRs). The network includes a roamer port MSC having a roamer port which is shared with at least one neighboring MSC. A number portability database (NPDB) associates a location routing number (LRN) with each distinct MSC/HLR pair in the network. When a roamer port call, which includes the mobile directory number (MDN) of the called mobile station, is received in the roamer port MSC, the roamer port MSC determines whether the MDN falls within a ported range. If so, a request is sent to the NPDB to retrieve a LRN for the called mobile station. From the LRN, a HLR associated with the mobile station is identified. The roamer port MSC then sends a location request to the identified HLR which returns a routing number for the called mobile station, or indicates that a call-diversion type service is active. If no call-diversion type service is active, the roamer port MSC determines whether the called mobile station is located in a neighboring MSC to which the roamer port MSC allows routing of calls. If so, the call is routed locally to the neighboring MSC.

Method of supporting functionality for roamer port calls in a radio telecomminications network in which number portability is implemented

A system and method for implementing services in an intelligent network of a telecommunications system. Upon registration of a subscriber station in a mobile telecommunications network, a plurality of triggers associated with the subscriber are downloaded to a switch that is handling the call. Subsequently, a trigger condition is detected at the switch, and a query signal is sent to a server storing data for responding to the trigger condition. In response to the query signal, a bundle of platform independent code comprising instructions for executing a particular service is downloaded to the switch. The code is executed at the switch to implement the particular service, and appropriate actions are taken in accordance with the implemented service.

Use of platform-independent code for supporting services in an intelligent network

A home location register (HLR) and method of routing a call directed to a portable directory number in a radio telecommunications network. The network includes an originating mobile switching center (O-MSC) and a Number Portability Database (NPDB). The O-MSC first sends a Location Request (LOCREQ) message to the HLR requesting a routing number. The LOCREQ message includes a dialed directory number. The HLR determines whether a routing number is assigned to the dialed directory number. If not, the HLR sends a Number Portability Request (NPREQ) message to the NPDB and includes the dialed directory number. A location routing number (LRN) assigned to the dialed directory number is then retrieved from the NPDB and sent to the HLR. The HLR forwards the LRN to the O-MSC, which then routes the call to the LRN.

Home location register and method of routing calls to portable numbers in a radio telecommunications network

A method of routing a call directed to a portable directory number in a radio telecommunications network having an originating mobile switching center (O-MSC), a home location register (HLR), and a Number Portability Database (NPDB). The O-MSC determines whether to send a Location Request (LOCREQ) message to the HLR for a routing number, or to send a Number Portability Request (NPREQ) message to the NPDB for a location routing number (LRN). The determination may be based on operator preference, a default preference, or statistics indicating that either the HLR or the NPDB is more likely to return a routing number. The O-MSC then attempts to obtain a routing number from the determined destination. If an error message is returned, the O-MSC attempts to obtain a routing number from the alternate destination. Upon receipt of a routing number, the O-MSC routes the call. In an alternative embodiment, the O-MSC may send the LOCREQ message and the NPREQ message simultaneously, and utilize the first routing number received to route the call.

Method of routing calls to portable numbers in a radio

The package type identifier of 'conversation with permission' is utilized in certain ANSI-41 Mobile Application Part (MAP) messages to allow a node receiving the message to generate an appropriate response message necessary for MAP operation closure within a Transaction Capability Application Part (TCAP) transaction. In one implementation, an ANSI-41 MAP error or reject message includes a package type identifier of 'conversation with permission' instead of 'response' thus allowing the node receiving the error or reject message to appropriately respond in connection with the closure of an open MAP operation. In another implementation, the 'conversation with permission' package type identifier is specified for an ANSI-41 MAP instruction request message to support MAP operation closure in the event of an error or rejection in that operation.

Growing community of inventors

Pointe-Claire, Canada

Margaret Britt