MXPA99003562A - Telecommunications network with portability of mobile subscriber number - Google Patents

Abstract

A telecommunications network (10) comprises a set of service provider/operator domains (20), including mobile telecommunications domains (20A-20C). A call-originating domain (20F) accesses a mobile subscriber number portability database (30F) to obtain the address of the gateway node (GMSC) of the telecommunications domain which currently serves a called mobile subscriber having a mobile station (70), and optionally the address of the home location register (HLR) of the called mobile subscriber. The address of the gateway node obtained from the database (and optionally the address of the home location register) are included along with the directory number (MSISDN) or IMSI of the called mobile subscriber in a routing message for completing the call. When changing service providers (e.g., changing to a new domain), the mobile subscriber number portability database is updated to reflect the change. Access of the database and usage of the address of the gateway node of the new domain in the routing message permit the mobile subscriber to retain the same MSISDN when changing service providers.

Description

TELECOMMUNICATIONS NETWORK WITH MOBILE SUBSCRIBER NUMBER PORTABILITY This application is a continuation in part of the United States patent with serial number 08 / 739,930, made on October 18, 1996, entitled TELECOMMUNICATIONS NETWORK WITH SUBSCRIBER NUMBER RECOLATION, which is commonly assigned and incorporated herein by reference. This application relates to the United States patent application with serial number 80 /, (attorney's register 1410-252), entitled "PORTABILITY OF NON-GEOGRAPHIC TELEPHONE NUMBERS OF INTELLIGENT NETWORK SERVICES," presented simultaneously, which is incorporated herein by reference. 1. Field of the Invention This invention relates to telecommunications systems, and particularly to the routing of calls through a telecommunications system for a mobile subscriber. 2. Related Technology and Other Considerations A telecommunications network typically includes a number of physical nodes, often referred to as local exchanges, to which the subscribers in the telecommunications network are connected. Local exchanges are generally connected in the telecommunications network by other physical nodes, known as transit exchanges.

To simplify the routing of calls through the network and to have a good structure of the telephone numbering plan, each local exchange is assigned one or more groups of unique switching numbers. The telephone number of a subscriber typically includes both a group of switching number (typically a block of number 10,000) for the exchange to which the subscriber is connected, and a number in that group which is peculiar to the subscriber. For example, a subscriber that has a telephone number "881-1657" is connected to a local exchange that has a "881" switching number, and within that group the subscriber has a subscriber number of "1657". The subscriber's telephone number is published or circulated as his directory telephone number, for example, in a telephone directory or in a book.

A common way to route a call through a telecommunications network to a final destination is to use the telephone directory number of the called party (for example, the called subscriber). In particular, the directory telephone number of the called party occupies an address signal field of an ISUP parameter known as the "Called Person Number" parameter ("CdPN") being an address message or route used for purpose. of addressed. Using the directory telephone number of the called party for the purpose of addressing has numerous problems, particularly when the subscriber physically relocates or changes service provider. If the subscriber who relocates or changes the provider wishes to keep his original directory number, he must be connected by means of a special physical line to his own local exchange. This physical connection is quite expensive when the subscriber has moved away from the local exchange. If the relocation is such that the subscriber's connection to the telecommunications network changes from an old local exchange to a new local exchange, on the other hand, the telecommunications network provider can not accommodate the relocation of the subscriber without changing the number of subscribers. Subscriber directory.

Changing the telephone number of the subscriber's directory in the case of the relocation of the subscriber causes expenses and effort for both the subscriber and the telecommunications provider. For the provider, it is expensive to manage directory telephone number changes when the subscriber relocates from one area to another. The administration required by the provider includes efforts to define new numbers available in the new location (this being in the new plant) and update the published directory. The relocated subscriber incurs expenses by providing notice of the new directory number to potential users (friends and business contacts). If such notice is not given or retained by potential users, calls may not be made to the relocated subscriber. The loss of calls to a relocated subscriber may result in the loss of business or social opportunities.

The problem of the portability of the subscriber number is even more acute for mobile subscribers. At the present time, a call to a mobile station is addressed including an MSISDN - the directory number of the mobile subscriber - in the address field signal of the "Called Person Number" parameter ISUP ("CdPN"). As a result of the inclusion of the MSISDN in the Person Number Called "CdPN" parameter, the call is routed to a Mobile Switching Gate Center (GMSC). Where a Mobile Exchange (MSC) exchange "is a telephone exchange that has a mobile telephone subsystem (MTS), a Mobile Switching Gateway Center (GMSC) is an MSC which is linked to other (for example, not mobile) ) networks such as PSTN or ISDN networks All calls entering a mobile network are routed to a GMSC, which serves as an entry transit exchange The GMSC has an address call interrogation function for completed mobile calls which allows the system to address calls to mobile subscribers.The Mobile Switching Gate Center (GMSC) uses the MSISDN as "Global Title" to request that the subscriber's home location register (HLR) of the mobile station indicate the number of roaming of the MSC subscriber in which the mobile subscriber is located at that time.The request to the HLR for the subscriber roaming number is sometimes called information operation. shipping address (SRI). The SRI request can be routed to the HLR through one or more signal transfer points (STPs). The STPs have address tables which are used to direct the SRI request to a particular HLR which is appropriate for the called mobile subscriber. However, when mobile subscribers are allowed to retain their MSISDN after switching from one service provider to another, the routing tables for any intermediate STP would be huge and require updating for each mobile subscriber that changes service provider. Of course, mobile subscribers would change their service provider if their number can be retained, since subscribers can make provider choice decisions based on considerations of price, service, and characteristics other than the preservation of their number. In a mobile network, allowing mobile subscribers to watch their MSISDN numbers when they change their service provider causes considerable problems. The problems arise from, at least in part, the fact that the MSISDN is used both as the address of the GMSC of the called party and to locate the home location register (HLR) for the called party.

When the portability of MSISDN number is provided to mobile subscribers, any reorganization of the series of numbers served by the HLR becomes difficult. In this regard, it sometimes happens that, due to capacity or other reasons, the service provider wishes to divide the load of an HLR so that it is carried by two HLRs. Implementing such reorganization is problematic if mobile subscribers can change service providers and retain their original MSIDN. What is needed therefore, and an object of the present invention, is an efficient way to facilitate providing number portability for mobile subscribers, as occurs for example when a mobile subscriber changes service provider.

COMPENDIUM OF THE INVENTION A telecommunications network comprises a set of provider / operator domains, including mobile telecommunications domains. A calling originator domain accesses the portability database of the mobile subscriber number to obtain the address of the gateway node of the telecommunications domain which at that time serves a called mobile subscriber, and optionally the address of the location registration of the mobile subscriber. address of the mobile subscriber called. The address of the gate node obtained from the database (and optionally the address of the home address register) is included together with the directory number (MSISDN) or IMSI of the mobile subscriber called in a addressed message to complete the call . When changing service provider (for example, change to a new domain), The mobile subscriber number portability database is updated to reflect the change. Accessing the database and using the gateway address of the new domain of the addressed message allows the mobile subscriber to retain the same MSISDN when it changes service provider.

The call originating domain may be a fixed subscriber domain, for example, PSTN or ISDN, or a mobile telecommunications domain. The information obtained from the mobile subscriber number portability database is included as a parameter in a directional field of an industry standard of the called party number, parameter (CdPN). BRIEF DESCRIPTION OF THE DRAWINGS The foregoing and other objects, features and advantages of the invention will be apparent from the following particular description of the preferred embodiments as illustrated in the accompanying drawings in which the reference characters refer to the same parts in the drawings. different views. The drawings are not necessarily to scale, emphasis is made on the illustration of the principles of the invention. Figure IA is a schematic view of a telecommunications system according to an embodiment of the present invention with a mobile subscriber subscribing to a first service provider. Figure IB is a schematic view of a telecommunications system according to another embodiment of the present invention with a mobile subscriber subscribing to a first service provider. Figure 1C is a schematic view of the telecommunications system of the Figure showing that the mobile subscriber has changed the subscription of the first service provider to a second service provider. Figure 2A is a schematic view of the telecommunications system of Figure IB showing actions taken to call a mobile subscriber according to a first mode of the invention. Figure 2B is a schematic view of the telecommunications system of Figure IB showing actions taken to call a mobile subscriber according to a first mode of the invention. Figure 3 is a schematic view of the telecommunications system of Figure IA showing actions taken to call a mobile subscriber according to a second mode of the invention. Figure 4 is a schematic view of the telecommunications system of Figure IA showing actions taken to call a mobile subscriber according to a first mode of the invention. Figure 5 is a schematic view of an international telecommunications network showing actions performed during a location update registration / operation when a mobile subscriber of a service provider / operator in a first country is visiting in a second country. Figure 6 is a schematic view of an international telecommunications network and a way of connecting a call between two visiting subscribers in a foreign country, wherein a gate node is connected to a mobile subscriber number portability database. Figure 7 is a schematic view of an international telecommunications network in a mode of connecting a call between two visiting mobile subscribers in a foreign country, and wherein a gate node is not connected to the number portability database. mobile subscriber. Figure 8 is a schematic view of a plurality of domains maintained by different service providers, with one of the domains providing mobile telecommunications. Figure 8A and Figure 8B are schematic drawings illustrating the communication between NAPS of the invention and the Home Location Register (HLR) to allow a subscriber to use the same directory number for both landline and mobile telephones. Figure 9 is a schematic view of a plurality of domains maintained by different service providers and illustrating the applicability of the relocation number for Wireless Terminal Mobility (CTM) calls. Figure 9A and Figure 9B are schematic drawings illustrating the communication between NAPS of the invention and functions involved with CTM to enable a subscriber to use the same directory number for both fixed equipment and CTM. Figure 10 is a schematic view of transfer of information layers in the system of Figure IA according to an Open Interconnection System (OSI) model. Figure 11 is a schematic view of included entities is a Mobile Application Part of layer 7 of the OSI model of Figure 10. Figure 12 is a schematic view of a format of an industry standard called a staff number parameter who calls Figure 13 is a schematic view of a telecommunications system of Figure IA and showing actions taken to call a mobile subscriber according to a mode of the invention in which the database responds with the subscriber's mobile subscriber number International (IMSI). DETAILED DESCRIPTION OF THE DRAWINGS In the following description, for purposes of explanation and not limitation, specific data are indicated such as particular architectures, interfaces, techniques, etc. In order to provide a complete understanding of the present invention. However, it should be apparent to those skilled in the art that the present invention can be practiced in other embodiments that depart from these specific details. In other instances, detailed descriptions of known devices, circuits and methods are omitted so as not to obscure the description of the present invention with unnecessary details. Figure IA shows a telecommunication system or network 10 according to an embodiment of the invention. The network 10 includes a set of domains of service providers 20A to 20C and 20F. Three of the domains (particularly domains 20A to 20C) are mobile telecommunications domains serving mobile stations; domain 20F serves fixed stations. In the illustrated embodiment, the domain 20F may be of the network type such as a public switched telephone network (PSTN) or an integrated services digital network (ISDN), for example. At least some of the areas served by domains 20 can be, and surely are, geographically coextensive. In one mode of the invention, some of the domains 20 are served by different service providers, for example, different telecommunications operating companies. The fixed station domain 20F includes at least one local exchange 22F. The local exchange 22F is connected to a plurality of fixed subscriber stations, only one of which (subscriber 24) 'is shown in Figure IA. The local exchange 22F is connected either directly or lately (for example, by means of transit exchanges) to a gate central or gate node 26F. The gate node 26F is connected to a database 30F. The database 30F, in turn, is connected (for example, to update and for maintenance purposes) to a 32F service management system. The mobile telecommunication domains 20A to 20C each have respectively gate nodes 26A to 26C, each of which takes the form of a mobile service switching center (GMSC) and accordingly are respectively referred to as GMSCs 26A to 26C. Each gate node 26A to 26C and 26F is connected to a gate node of at least one other domain, all of the gate nodes being interconnected in the particular example shown in FIG. 1A. Each gateway node GMSC 26 serves as an interface to external domains 20 for one or more of the mobile services switching centers (MSVs) 40 which belong to the domain. Each MSC 40 includes a telephone exchange (such as an Ericsson AXE exchange) and a mobile telephone subsystem (MTS). Although any given domain probably has a plurality of MSCs 40, only one of the MSCs 40A is shown for domain 20A and a single domain 40C is shown for domain 20C. In order to illustrate, domain 20B is shown with two MSCs, particularly MSC 40B (1) and MSC 40B (2). Each GMSC 26 is connected to the MSC 40 in its domain; MSCs 40 generally also include or access the Visitor Location Register (VLR), each MSC 40 is labeled in Figure IA as MSC / VLR. For the particular modalities mentioned hereinafter, the reference to an MSC is for an MSC / VLR, particularly in the context of activities involving an HLR. Each MSC 40 in Figure IA is connected to serve at least one and preferably a plurality of base station controllers (BSCs) 50. For example, MSC 40 serves base station controllers 50 ^ -1 to 50A-m; MSC 40B (1) serves base station controllers 50B (1) -1 to 50B (l) -m; MSC 40B (2) serves base station controllers 50B (2) -1 to 50B (2) -m; MSC 40C serves base station controllers 50C-1 up to 50C-m. It should be understood that typically different MSCs 40 serve a different number of base station controllers 50. Each base station controller 50 is connected to one or more base receiving transmitter stations (BS) 60. For example, receiving transmitter stations (BS) 60A-1 to 60A-1 (q). It is the number of base receiving transmitter stations (BS) 60 per base station controller 50 may vary. Each base receiving transmitting station (BS) 60 transmits and receives radio frequency communications to and from a plurality of mobile subscribers (MS) 70 in the geographic areas served by the respective BSs 60. To illustrate simply, only one mobile station 70 is shown in Figure IA, although it should be understood that each domain 20 serves hundreds but thousands of mobile stations not illustrated. The particular mobile station 70 shown in Figure IA is, at that time, served by the base receiving transmitting station (BS) 60A-m (q). Each of the mobile telecommunications domains 20A a 20C also includes a plurality of Home Location Registries (HLRs) 80. Domain 20A has HLRs 80A (1) up to 80A (n); the domain 80C (1) to 80C (n). When a subscriber obtains a mobile station and purchases a subscription from a provider / operator of one of the domains 20A to 20C, the subscriber's mobile station is registered in an HLR 80 of that provider / operator. The HLR 80 contains, for each subscriber, subscriber information, such as supplementary services and authentication parameters. In addition, the HLR 80 includes updated information on the current location of the mobile station, this being, in which MSC area the mobile station resides at that time. This current location information in the HLR 80 changes as the mobile station moves, in a manner well known in the art. The mobile station sends location information (via MSC / VLR 40) to its HLR 80, thereby providing the means to receive a call. Each HLR 80 is typically connected to a gate node 26 in its domain, as well as to the MSC / VLR 40 in its domain. In addition to the previous one, the mobile telecommunications domains 20A to 20C each include respective databases 30A to 30C. The databases 30A to 30C are connected and maintained by a service management system 32A to 32C, respectively. Similarly, the service management systems 32A to 32C are connected to and maintain the HLRs 80A (1) to 80C (n). Service management systems 32A to 32C are connected to and supervised by a 32M master service management system. The databases 30 are subscriber location servers which are augmented with additional intelligence and therefore are known and named (e.g., in U.S. Patent No. 08 / 739,930, made October 18, 1996, incorporated herein by reference) as address and number portability servers (NAPS). The databases 30 include information which facilitates number portability for many types of subscribers in their respective domains, including mobile subscribers. Without ignoring the extensive use of databases 30, for convenience herein, databases 30 will sometimes be referenced as a subscriber number portability database 30 to emphasize the aspects thereof relating to the present invention. As will be more apparent below, the telecommunication domains 20A to 20C comprise a subscriber number portability domain. In the number portability domain, mobile subscribers can change service providers, for example, change one of the domains to another, for example, change from domain 20A to domain 20C, and keep their "directory" or MSISDN number. "Portability", when used in relation to a mobile subscriber, involves the relocation of the data storage location for a mobile subscriber. When a mobile subscriber changes from one service provider to another, the change involves moving the data for the subscriber to one of the home location registers (HLR) of the new service provider / operator. Figure IB shows another embodiment of the network of Figure IA, but additionally shows that the local exchange LE 22F is connected to and accesses the database 30F. In all other aspects, the modality of Figure IB is similar to that of Figure IA. The MSISDN of a subscriber is a number which uniquely identifies a mobile telephone subscription in the numbering plan of the public switched network. In accordance with the CCITT recommendations, the mobile phone number or catalog number is entered as follows: MSISDN = CC + NDC + SN CC = Country Code NDC = National Destination Code SN - Subscriber Number A Code National Destination is assigned to each domain (for example, to each GSM / PLMN [Global System for Public Communications / Public Land Mobile network]). In some countries, more than one NDC may be required for each domain 20. The international MSISDN number may be of variable length. The maximum length of the MSISDN number is 15 digits. The length of the MSISDN number depends on the structure of the numbering plan of each operator, such as an application of the CCITT recommendation E. 164. For example, when a Swedish PSTN subscriber calls a Swiss subscriber OSM PLMN, the following digits shown in the Table 1 are typed. In Table I, the digits 89 define 2 or 3 digits which identify the area code GSM PLMN; the digits 902147 define the 6 digits which identify the mobile subscriber. TABLE 1 Prefix Code Code International Destination Country Number of In Sweden National Subscriber 009 41 89 902147 Communications and signaling occur between domains 20 of Figure IA and its components. Telecommunications models have been created for standardized descriptions of different cases of information transfer in networks such as a network of Figure IA. One such model is the Open System Interconnection (OSI) model, which is structured in well-defined and specified layers which are each completely independent from the others. Like the OSI model, the CCITT Signaling System No. 7 is also structured in layers. The first layer is the physical level, which is the interface to the information carrier, the signaling network. The first layer converts the zeros and ones of a frame into pulses of the correct size and shape and transmits them on a line. The second layer concerns the handling of faults, and has functions to separate messages, fault detection and correction, detection of signal link faults, etc. The third layer concerns addressing and handling of messages (eg, distribution and addressing), and contains functions to ensure that the message arrives at the correct exchange, and functions to verify the network and to maintain the transmission characteristics. The fourth layer is the user part, and is designed so that several different users can use the same signaling network.

The CCITT Signaling System No. 7 includes a number of functional parts, including a Message Transfer Part (MTP) and a number of different user pairs. As shown in Figure 10, the Message Transfer Part (MTP) resides in the first three layers. The Message Transfer Part (MTP) serves as a common transport system for reliable transfer of message signaling between signaling points and is independent of the content of each message of the User Part. Therefore, the responsibility of the MTP is to transmit messages signaling from a User Part to another User Part reliably. Each user part contains the functions and procedures which are specific to a certain type of user of the signaling system. Examples of these user parts are the Telephone User Part (TUP), the Data User Part (DUP), the ISDN User Part (ISUP) and the Mobile Phone User Part (MTUP). In the OSI layer organization, CCITT 1984 introduced a Signaling Connection Control Part (SCCP) which "Provides additional functions to the Message Transfer Part (MTP) and which is located over MTP in the OSI layer scheme [see Figure 10]. The combination of MTP and SCCP is called Network Service Part (NSP). The Network Service Part (NSP) satisfies the requirements for layer 3 services as defined in the OSI Reference Model, CCITT Recommendation .X.200. The SCCP is described in Recommendation CCITT Q.711-Q.716. The SCCP makes it possible to transfer signaling related to circuits and not related to circuits and user information between exchanges and centers specialized in telecommunications networks by means of a CCITT network No. 7. Layers 4 to 6 of the OSI model of Figure 10 include the Intermediate Service Part (ISP). The Intermediate Service Part (ISP) is an element of the transaction capabilities which the Transaction Capability Application Part (TCAP) supports for connection oriented messages. The Transaction Capability Application Part (TCAP) resides in layer 7 of the OSI model. , Also provided in layer 7, resident on the Transaction Capabilities Application Part (TCAP), is the Mobile Application Part (MAP). The Mobile Application Part (MAP) provides the necessary signaling procedures required for information exchange between GSM networks (for example, domains 20 of network 10 of Figure IA). As shown in Figure 11, the Mobile Application Part (MAP) is divided into five application entities (Aes): MAP-MSC, MAP-VLR, MAP-HLR, MAP.EIR and MAP-AUC. The MSC is the Mobile Services Switching Center, which controls calls to and from other networks (eg, PSTN, ISDN, PLMN, public data networks and possibly several private networks). The VLR is the Visitor Location Registry which, as previously mentioned, is a database that contains information about all the visitor mobile stations located in the MSC area. The AUC is the Authentication Center which is connected to the HLR and which provides the HLR with authentication parameters and encryption keys for security purposes. The EIR is the Equipment Identity Record, which contains the hardware number of the equipment. All of these are assigned a Sub-System Number (SSN). The SSNs are used by the SCCP to address the corresponding domain network entity (AE). Examples of operations carried out in the Mobile Application Part (MAP) are the following: update of the mobile station location; cancellation location for a mobile station; provide a roaming number for a visiting mobile station; insert subscriber data; delete subscriber data; send parameters; Activate supplementary services and make deliveries. Mobile Switching exchanges (MSC) 40 and base station controllers 50 are connected by PCM links. Apart from a number of channels for voice / data, there are also reserved time segments for signaling. The data signaling in connection with call set-up, delivery, release, etc., normally uses this channel which can serve one or more base receiving transmit stations (BS) 60. The protocols used for signaling between MSC and BSS are BSSAP (Application Part BSS), SCCP and MTP. Figure 2A illustrates actions involved when the subscriber 24 in the fixed domain 20F makes a call to a mobile subscriber in one of the mobile telecommunications domains 20, particularly the mobile subscriber 70 in the mobile telecommunications domain 20A. The action 2-1 shows the subscriber 24 by dialing the directory number or MSISDN of the mobile station 70 and the dialed number is being routed to the local exchange 22F. Action 2-2 shows the local exchange 22F sending a addressed message to the gate node 26F. In the action 2-2, the MSISDN of the mobile subscriber 70 is included in a direction signal field of a addressed message such as an ISUP called person parameter (CdPN). In Figure 2A, the expression CdPN. { MSISDN} means that it indicates that the CdPN parameter includes the MSISDN value of the mobile subscriber 70 in its address signal field. Figure 12 shows the format of the caller's parameter (CdPN) of the ITU-T Rec. Q.763 standard, an industry standard. The called person parameter (CdPN) is used to address calls between exchanges of a telecommunications system. The CdPN format of Figure 12 includes a seven-bit Address Nature Indicator ("NAI") in the first byte; a Plan Number Indicator ("NAPI") in bits 5 to 7 of its second byte; and a Address Signal Field ("ASF") in its last n-3 bytes. The Plan Number Indicator ("NAPI") is a field that has one of 8 different values, and which indicates to what type of plan the subscribed subscriber subscribes (for example, ISDN or not). The Address Nature Indicator ("NAI") is an ISUP parameter that has one of 128 values, many of which are spare (being this not yet assigned). The NAI is conventionally used to indicate such things as if the number is a national number or an international number, etc. The Signal Direction Field ("ASF") has n-2 numbers of four-bit segments, each segment represents an address signal. The most significant address signal is sent first, subsequent address signals are sent in successive 4-bit segments. The gate node 26F receives the local central day address message 22F and, as indicated by the action 2-3, sends the addressed message with CdPN. { MSISDN} to the portability database of the mobile subscriber number 30F. The portability database of the mobile subscriber number 30F uses the MSISDN of the mobile subscriber 70 to determine that the mobile station 70 is currently served by GMSC 26A. Then, in action 2-4, the portability database of the mobile subscriber number 30F returns to the gateway node 26F a CdPN parameter which now includes both addresses of GMSC 26A (GMSC26Aaddr) and the MSISDN of the mobile subscriber 70, being this, CdPN. { GMSC26Aaddr, MSISDN} . In action 2-5 the gate node 26F formulates and sends to GMSC 26A an initial addressed message (IAM) which includes the CdPN parameter returned by the portability database of the mobile subscriber number 30F. Then, in action 2-6, GMSC 26A interrogates the database 30A using the MSISDN of the mobile subscriber 70 to obtain a "Global Title" to be used for communication to the appropriate Home Location Registration (HLR) 80A where data is stored for the called mobile subscriber 70. The Global Title or "GT" is an address in the SCCP part (see Figure 10 and Figure 11). Action 2-7 shows the HLR address being returned by database 30a to GMSC 26A. In action 2-8 the GMSC 26A issues an information submission operation (SRI) [which includes the address of the appropriate HLR obtained from the 30A database as the Global Title] to the appropriate HLR [eg, one of the HLR 80A (1) to 80A (n)] to obtain the necessary addressing information. Action 2-9 shows the HLR 80A (n) responding to the SRI operation with an SRI_response which returns the necessary addressing information, for example, the roaming number (MSRN) of the mobile subscriber called 70. As a result of reception of the MSRN obtained in action 2-9, additional actions are taken: action 2-10 shows the call being addressed to MSC 40A; action 2-11 shows the call being addressed to the base station controller 50A-m; action 2-12 shows the call being applied to a transmitter of the base receiving transmitting station (BS) 60A-m (q); action 2-13 shows the mobile subscriber 70 being called by BS 60A-m (q) with the call. It should be understood that, in the conventional manner, the determination by the HLR of the current MSC 40 which at that time controls the mobile subscriber 70 may involve other actions not specifically shown herein. In addition, it should be understood that one or more transfer points (STPs) may be included between GMSC 26A and the HLRs, and that these STPs use the Global Title in the SCCP message to route the SRI operation to the appropriate HLR. Figure 2B shows how the mode described above is carried out in the network shown in Figure IB where the local exchange 22F is connected to the data base 30F. After dialing the MSISDN of the mobile subscriber called in action 2-1, in Figure 2B the local exchange 22F inquires database 30F with the MSISDN as indicated by action 2B-2. The database 30F determines the address of the gateway node for the marked MSISDN, and in action 2B-3, a CdPN parameter that now includes both addresses of GMSC 26A (GMSC26Aaddr) and the MSOSDN of the mobile subscriber returns to the local exchange 22F. , being this, CdPN. { GMSC26Aaddr, MSISDN} . The returned CdPN is then transmitted to gate node 26F in action 2B-4. Henceforth the call is completed using the same actions 2-5 through 2-12 as shown in Figure 2A. Interrogating the local exchange such as local exchange 22f in the manner of Figure 2B has the advantage that the services and charges (eg billing) will have the correct destination information (which was valid when the call was initiated). In this respect, a function known as "Outgoing Call Saved" or "OCB" that has to know the actual destination of the call in order to filter the calls (this being, excluding the termination of the call). The OCB function is preferably carried out by analyzing the CdPN parameter in the local exchange, since the block number tells the destination network and geographical area of the call. With the modification of the CdPN by the database 30 of the present invention, the OCB function carried out in the local exchange needs to know the value of the CdPN returned from the database. Therefore, interrogating the database by the local exchange facilitates the precise operation of the OCB function.

As a variation of Figure 2B, it should be understood that any type of node in a call origination network can be connected to and query a database such as database 30. Although examples of gate nodes and local exchanges have been illustrated. , other nodes such as transit exchanges can also operate if they are properly connected to the database. Figure 3 shows another mode of the invention wherein the actions 2-1 through 2-3 are identical to the comparable actions with equal numbering described above with reference to Figure 2A. However, in the mode of Figure 3, upon receiving the CdPN parameter in action 2-3, the portability database of the mobile subscriber number 30F returns in action 2-4 not only the address of the GMSC for the mobile subscriber called 70 and the MSISDN for the mobile subscriber 70, but also the address of the HLR which serves the mobile subscriber 70, being this, HLR addr for HLR 80A (n). Therefore, in action 2-4 the parameter of the person called CdPN includes the values GMSC 26Aaddr, and MSISDN, for example, CdPN. { GMSC26Aaddr, HRLaddr, MSISDN} . As a result of the gate node 26F knowing the HLR address 80A (n) which serves the mobile subscriber 70, actions 2-6 and 2-7 of Figure 2A are ignored in the mode of Figure 3. Actions of the mode of Figure 3 continue in a similar manner as with actions 2-8 and following of Figure 2A, with the Global Title being sent in action 2-8 to HLR 80A (n) in the home HLR obtained from the message Initial addressed (IAM). Therefore, the mode of Figure 3 involves storage in the database 30F of not only the home of the GMSC serving the mobile subscriber 70, but also the storage of the home of the particular HLR which handles the mobile subscriber 70. The inclusion of the HLR address in the 30F database, and consequently in the initial addressed message (IAM) sent in action 2-5, allows faster access of the HLR. In some modalities the HLLR address is the INSI number that is attached to the IMSI number as explained further here-, but such need is not necessarily the case. , Figure 1C shows that mobile subscriber 70 has changed service provider. In particular, as seen in Figure 1C, the subscriber of the mobile subscriber 70 has changed its subscription from a provider which operates the domain 20A to the provider which operates the domain 20C. In fact, at the time shown in Figure 1C, the mobile subscriber 70 is served by MSC 40C and has its home location register as HLR 80C (1). At the subscription change shown in Figure 1C, the deletion of the subscriber (owner of mobile subscriber 70) of MSC 40A and HLR 80A (n) was communicated to the service administrator (SMS) system 32A, which advised the administration system of Master service (SMS) 32M. SMS 32M subsequently communicated the deletion of the subscriber to all SMSs 32, including SMSs 32B, 32C and 32F, which in turn updated their respective databases 30B, 30C and 32F. Then, when the subscriber joined the service provider which operates domain 20C, SMS 32C notified the SMS 32M master of the revenue. SMS 32M subsequently notified all SMSs 32 of the subscriber's 20C domain entry, including SMS 32A, 30B and 30F, in accordance. For the implementation of the second mode, the databases must be notified of the addressed Global Title information in which to find the correct HLR. Of importance, when changing service providers to domain 20C, the subscriber of mobile station 70 retains the same directory number or MSISDN which it had when it was a member of domain 20A. Figure 4 shows the placement of a call from the subscriber 24 in the fixed domain 20F to the mobile subscriber 70 (now in the domain 20C as shown in Figure 1C). The actions 2-1 through 2-3 as shown in Figure 4 are identical to numbered comparable actions described above with reference to Figure 2A. Nevertheless, in view of the updating of the database 30F to reflect the mobile subscriber 70 that has changed service providers, the called person parameter returned to the database 30F in action 2-4 includes the address of the new GSMC 26C, not the address of the old GMSC 26A. Hereinafter, the actions taken to place calls in Figure 4 are understood with reference to the actions already described above, it being understood that the subscriber of the mobile station 70 is now being served by GMSC 26C and particularly MSC 40C and BSC 50C-m . Although not expressly illustrated, it should be understood that a mode similar to that of Figure 3 can also be carried out with respect to Figure 4, so that the database 30F includes in the parameter of person called the address of the HLR appropriate [eg HLR 80C (1)] address, steps 2-6 and 2-7 are thus obviated as discussed above with reference to Figure 3. In the previous examples, for the purpose of illustration the basis 30F has returned the address GMSC and MSISDN, and in the second mode the address HLR, as part of the parameter of person called CdPN, particularly in the Address Signal Field (ASF) thereof. It should be understood, however, that an important aspect of the present invention is that the database 30F returns the address GMSC, the MSISDN, and (in the second mode) the address HLR in a manner usable by the gate node 26F. Therefore, the insertion of these addresses and MSISDN is not confined to the Address Signal Field (ASF) in the CdPN parameter. Instead, these addresses and the MSISDN can be applied to the gateway node 26F in other ways, such as in other parameters allowed by the particular protocol being implied. In another modality shown in Figure 13, the response of the subscriber number portability database (indicated by action 2-4 in Figure 13) is the address to the GMSC (an E.164 number) and the international mobile subscriber number (IMSI), being this, the MSISDN does not need to be transported later. As commonly understood, IMSI consists of three different parts: MCC, MNC, and MSIN. MCC is a Mobile Country Code (3 digits); MNC is a Network Code Mobile (2 digits); and MSIN a Mobile Station Identification Number (11 digits maximum). Since the IMSI is obtained from the database, the IMSI is then used in action 2-8 to direct the HLR of the GMSC, thereby obviating actions 2-6 and 2-7 shown in other modes. The GMSC address is carried in the CsPN as a prefix to IMSI or the IMSI ported is a separate ISUP parameter (optionally new) which the GMSC understands. In the modality of Figure 13, the receiving mobile network does not need to consult its NAPs to determine the HLR address. The returned IMSI number is then the same IMSI as the one used from the HLR location in the location update operation.

The above examples have shown a call originated by the subscriber 24 in the fixed domain 20F. It should be understood that actions similar to those described above occur when a mobile subscriber makes a call to another mobile subscriber. In such an instance, the gate node serving the originating mobile subscriber interrogates its database 30 to determine for example, the gateway node address (GMSC) for the called mobile subscriber, and which subsequent actions resemble those illustrated. above. It should be understood that the term "domicile", used for example with reference to the address GMSC and address HLR, may also be a node identifier. Where the mobile subscriber number portability databases 30 are illustrated as being separate and different from the gate nodes 26, in other embodiments the subscriber number portability databases 30 are included as components of the subscriber nodes. gate 26 and therefore do not involve any external signaling. Figure 5 shows an international telephone network which serves providers / operators in two countries. In particular, Figure 5 shows the provider / operator 0P1 and 0P2 serving domains 520 (1) and 520 (2), respectively, in Sweden, as well as service provider / operator OP3 and 0P4 serving respective domains 520 (3) and 520 (4) in England. In order to simplify, each domain is shown as having representative constituent elements including a signal transfer point (STP) 521; a gate node 523; a GMSC 526; an MSC / VLR 540; a base station 560; and a home location register (HLR) 580. For each domain, these representative constituent elements are labeled with suffixes in parentheses which correspond to the suffixes in parentheses of the domains, for example, STP 520 (1) for domain 520 ( 1), etc. For clarity, the representative constituent elements are shown in Figure 5, and it should be understood that pluralities of these elements and additional elements may reside in each domain. The service providers / operators OPl-OP4 of the network of Figure 5 may have several of their STPs 521 connected together. For example, STP 521 (1) is shown as being connected to STP (3) and ST0 (4), and similarly STP 521 (2) is shown as connected to STP (3) and STP (4). Although not shown in Figure 5, it should be further understood that the GW 523 gates of the various domains are also connected. GMSCs within a domain are also connected to each other. A Figure 5 further indicates that a mobile station MS-A, belonging to a subscriber of 0P2 which operates the domain 520 (2) in Sweden, has entered England and has just been activated. Figure 5 further shows actions involved in a registration / location update procedure for the MS-A mobile station. In action 5-1, the mobile station MS-A is viewed by sending its international mobile subscriber number (IMSI) to the base station 560 (4) of 0P4. As previously mentioned, IMSI consists of three different parts: MCC, MNC and MSIN. MCC is a Mobile Country Code (3 digits); MNC is a Mobile Network Code (2 digits); and MSIN a Mobile Station Identification Number (11 digits maximum). In the example shown in Figure 5, the mobile station MS-A has the particular number "4698750" as its IMSI. The MSC / VLR 540 (4) uses the IMSI sent from the mobile station MS-A as a global title (GT) and orders the SCCP to address a location update message to the HLR of the mobile subscriber. The MCC portion of the INSI indicates that the HLR is in Sweden; the MNC portion of the INSI indicates that the HLR is in OP2 (as opposed to the example, to OPl). Action 5-2 shows the location update message transmitted from MSC / VLR 540 (4) to STP 520 (4); action 5-3 shows the advance of STP 520 (4) from 0P4 to STP 520 (2) of OP2; action 5-4 shows the advance from STP 520 (2) to HLR 580 (2). Upon receiving the location update message, the HLR580 (2) uses the MSIN in the IMSI to determine the MSISDN for the mobile subscriber of the MS-A-HLR 580 (2) station, which serves the subscriber of the mobile station MS-A, responds with a message of "update of lease accepted". Action 5-5a shows the message "Accepted location update" being advanced to STP 521 (2); action 5-5b shows the message "Accepted location update" being advanced to STP 521 (4); action 5-5c displays the message "Accepted location update" being advanced to MSC / VLR 540 (4), additional communications between 0P4 and HLR may occur. For example, the VLR of MSC / VR 540 (4) takes the MSISDN of the subscriber which owns the mobile station MS-A. Once the registration has occurred, the registered mobile subscriber can make and receive calls. Ordinarily, the MSISDN of the registered mobile subscriber is used as a global title. However, the use of the MSISDN as a global title is not necessary if a portability database of the mobile subscriber according to the present invention is employed. For example, the MSISDN can be removed from the global title if, upon consulting the mobile subscriber number portability database, the IMSI of the registered mobile subscriber is included in the network address number (NRN) obtained from the base of NP data to address the HLR. Such replacement of MSISDN with OMSI can be either SCCP to HLR addressed and optionally also addressed to GMSC since the IMSI implicitly establishes the local network service. Figure 6 shows that domains 520 (1) and 520 (2) of Figure 5 further includes mobile subscriber number portability databases 530 (1) and 530 (2), respectively. Figure 6 shows domains 520 (3) and 520 (4), in contrast, as they do not have portable subscriber number portability databases. Further, in Figure 6 it is presumed that the mobile station MS-A of Figure 5 (which has MSISDN 4685431 and subscribed to OP2 in Sweden), after the registration / location update in the manner described with respect to Figure 5 , marks an MSISDN of: 468532 «in order to communicate to the mobile station MS-B. The mobile station MS-B, also traveling in England, previously subscribed to OP2 in Sweden but now subscribed to the Swedish operator OPl and which has already been registered to the Swedish operator OPl and which has already registered with its HRL and has a number of roaming known by MSC / VLR 540 (3). Figure 6 and Figure 7 show actions carried out in relation to a call from a first visitor mobile station in a foreign country (for example, the MS-A subscriber) to a second visitor mobile station in the foreign country (for example, example, it is a subscriber of MS-B), after the subscriber of the second mobile station called has changed from a first service provider / operator in his native country (OPl). In the particular mode shown in Figure 6, a gate 523 (2) of the first service provider / operator (0P2) is connected to the portability database of mobile subscriber number 530 (2); in the mode shown in Figure 7, gate 523 (2) of the first service provider / operator (0P2) is not connected to the mobile subscriber number portability database 530 (2). However, in the mode shown in Figure 7, GMSC 526 (2) is thus connected to the mobile subscriber number portability database 530 (2). As shown in Figure 6, when dialing in the mobile stations MS_A of the MSISDN of subscriber B (as reflected by action 6-1), the MSC / VLR 540 (4) determines that the MSISDN belongs to a Swedish subscriber ( for example, by the CC country code of the MSISDN) and that the series of historically marked digits belong to 0P2 in Sweden. However, unknown to MSC / VLR 540 ($), the subscriber with the marked MSISDN has changed from service provider / operator 0P2 to service provider / operator but retained the MSISDN originally assigned by OP2. Action 6-2 shows the call being digested from MSC / VLR 540 ($) to GMS 526 (4); action 6-3 shows the call being addressed from GMSC 526 (4) to gate node 523 (4); action 6-4 shows the call being addressed from gate node 523 (4) of service provider / operator OP4 to gate node 523 (2) of service provider / operator 0P2. By "call routing", it should be understood that the traditional addressing of messages is being used, and that those addressing messages include the MSISDN of the called subscriber B. Since gateway node 523 (2) is connected to database 530 (2), action 6-5 involves gateway node 523 (2) asking the question to database 530 (2) to determine which domain belongs to subscriber B called. Since, as indicated above, subscriber B has changed its subscription from 0P2 to OP1, action 6-6 shows database 530 (2) returning to network node 523 (2) a network addressing number ( NRN) which includes the address of GMSC which serves Subscriber B, particularly GMSC 526 (1). «Action 6-7 shows the call [for example, network addressing number (NRN) inclusive of the address of GMSC which serves Subscriber B and the MSISDN of Subscriber B] being sent from gate node 523 (2) of the domain 520 (2) to gate node 523 (1) of domain 520 (1). Action 6-8 shows the call being routed from gate node 523 (1) to GMSC 526 (1) of subscriber B. As indicated by action 6-7a, as an alternative to actions 6-7 and 6-8, the call can be addressed directly from the gate node 523 (2) of the domain 520 (2) to the GMSC 526 (1) of the subscriber B if the connections allow it, thereby obviating actions 6-7 and 6-8. Action 6-9 shows the 530 database (1) being interrogated by GMSC 526 (1), if necessary, to obtain the address of the HLR serving Subscriber B. Action 6-9 may not be necessary if the address HLR is detected before, for example, in the database 530 (2), and previously included in the network address number. Action 6-10 shows the address of the HLR which serves Subscriber B that is being returned to GMSC 526 (1). In action 6-11, GMSC 526 (1) interrogates the HLR of subscriber B [being this, HLR 580 (1)] to determine the location of subscriber B. When interrogated, the HLR 580 (1) in turn interrogates MSC / VLR 540 (3) of domain 520 (3), as indicated by action 6-lla. In response, MSC / VLR 540 (3) returns to HLR 580 (1) the necessary information (for example, the roaming number of mobile station MS-B of subscriber B). Action 6-12 shows the roaming number of Subscriber B being advanced to GMSC 526 (1). For simplicity, action 6-lla and action 6-llb are illustrated as if HLR 580 (1) were directly connected to MSC / VLR 540 (3), which is not the case. Instead, the search for the roaming number of Subscriber B and the roaming number return of Subscriber B is conducted through GMSC 526 (1), gate node 523 (1), gate node 523 (3) and GMSC 526 (3) in the manner understood by those skilled in the art. Actions 6-13 to 6-17 show the call being addressed to domain 540 (3) so that mobile station MS-B receives a call and sounds. In this regard, the call including the roaming number is advanced from GMSC 526 (1) to gate node 523 (1) [action 6-13]; from gate node 523 (1) to gate node 523 (3) [action 6-14]; from gate node 523 (3) to GMSC 526 (3) [action 6-15]; from GMSC 526 (3) to MSC / VLR 540 (3) [action 6-16]; and from MSC / VLR 540 (3) to base station 560 (3) [action 6-17]. The actions shown in Figure 7 differ from those shown in Figure 6 only in that the gate node 523 (2) can not interrogate the database 530 (2) directly. Actions identical to those shown in Figure 6 are shown in Figure 7 with the same corresponding reference numbers, including action 6-1 to action 6-4 and action 6-9, gate node 532 (2) , in action 7-5 the call is routed to GMSC 526 (2), since GMSC 526 (2) has access to the data base 530 (2). Action 7-6 shows the database 530 (2) being interrogated to determine which domain subscriber B currently belongs to and the address of the GMSC that manages subscriber B. One response, in this case pointing to domain 520 (1) having an address of GMSC 526 (1), it is returned by the database 530 (2) to GMSC 526 (2) in action 7-7. Action 7-8 shows the call to subscriber B being addressed to GMSC 526 (1). In the following, the actions of Figure 7 are identical to those of Figure 6, with the HLR address of subscriber B being determined, if necessary; the roaming number of subscriber B determining the HLR of subscriber B; and, the call being addressed to domain 520 (3) to MS-B. U.S. Patent No. 08 / 739,930, made October 18, 1996, which is incorporated herein by reference, shows the modalities of telecommunications networks which facilitate the portability of telephone subscriber numbers. . Where, several embodiments include a plurality of physical or central nodes between which the calls are connected and a subscriber location server which is connected to and accessed by each of the plurality of exchanges in the domain. Each plant has a unique plant identifier (ID). Generally, when a call is made to a subscriber in a portability domain, a first exchange which finds the call interrogates the subscriber location server. When interrogated, the subscriber location server returns a Network Address Number (NRN) which includes a Network Address Prefix (NRP). The Network Address Prefix (NRP) is a node identifier (NI) for the local exchange to which the called party is connected. The exchange to which the NRN is returned prepares a routing message for the call including the Network Address Prefix (NRP) in the Address Signal Field (ASF) of a addressed message and sets a relocatable marker number (NRF) in the addressed message. In a modality in which the addressed message is the standard of a loved industry parameter of the called person (CdPN), the central office fixes a relocable marker number and replaces the previous content of the ASF with a concatenation of the NRP and the previous content of the ASF (for example, the directory number of the called person). The subscriber location server has a switchable diagram of subscriber numbers and exchange identifiers. Subscriber directory numbers are not used to route calls through the domain. Instead, the node identifier (NI) in the form of a Network Address Prefix (NRP) is used to route calls to a terminal location exchange. A change of connection (for example, relocation) of a subscriber called from a first exchange to a second exchange involves the diagramming, in a database of the subscriber's location server, of the subscriber number of a exchange identifier of the first exchange. to a central identifier of the second central. The subscriber can move freely within the domain and keep the same directory number. The subscriber does not need to notify the public of a new directory number when the subscriber changes location. When desired for the purpose of redundancy, to share the load or for hierarchical structure, for example, a plurality of subscriber location servers may be employed. In some embodiments, a subscriber lease server enhanced with additional intelligence is known as a home portability and network number (NAPS) server. A NAPS is particularly effective in providing additional network services. For example, the NAPS can be easily and economically used to perform a "look ahead" function. Moreover, with NAPS it is possible to define the same subscriber number in several local exchanges and then, in the subscriber location server, make a determination about which local exchange the call of said subscriber number must be addressed. Such a determination can be made at any of a number of bases, such as the geography of the originator of the call, time of day, number of the caller, etc. It is also possible for the subscriber location server to route calls to different networks depending on the type of access used by the called party at a certain time, for example, if a cell phone is being used or a landline. Several Modalities also provide for number relocability when changing from one operator or service provider to another (for example, from a fixed service provider to GSM or vice versa) and when changing access service types (for example, from POTS). fixed to ISDN or GSM). Therefore, the relocability characteristics are not restricted to physical location relocability. In it respect to above, Figure 8 shows a plurality of domains 1020A, 1020B, 1020C. The domains 1020A, 1020B, 102OC each are maintained by a different service provider. The 102OB domain of Figure 8 provides a mobile telecommunications service. Domain 1020A has a GWA gate which connects to gate GWB (l) of domain 102OB and gateway GWC of domain 1020C; the domains 1020B and 1020C are connected between the GWB gates and the GWC gate. The domain 1020A has a local exchange 1022A which is connected to the gate GWA and the subscriber location server 1030A. The domain 1020B has gateways GWB (l) and GWB (2), the gateway GWB (l) is connected to the subscriber location server (NAPS) 1030B. For simplicity, no local exchange is shown in the 1020C domain, although one or more local exchanges are included. Connected for accessibility by all domains is the master subscriber lease server (NAPS) 1030C, and 1030M has an associated service management system. To facilitate mobile communications, the 102OB domain has a Mobile Gate Switching Center (GMSC) and a Mobile Switching Center with Visitor Location Registration (MSC / VLR). GMSC is connected by land lines to gate GWB (l) and to MSC / VLR, and to a Home Location Register HLR (l) and to the HLR Home Location Register (2). The MSC / VLR is also connected to both HLR (l) and HLR (2) by the ITU-T signaling system no. 7, and to the GMSC by land lines. In addition, the MSC / VLR is connected by land lines to the BSC / BSMC (Base Station Controller / Short Message Server Base Station). Figure 8 illustrates a call made from a sub-A fixed subscriber in domain 1020A to a GSM mobile subscriber which has been ported from service provider C (serving domain 102OC) to service provider B (serving domain 102OB). Action 8-1 shows the sub-A subscriber by dialing the sub-B subscriber's directory number. In action 8-2, the local exchange 1022A interrogates the subscriber location server 1030A to determine the network addressing prefix of the sub-B subscriber based on the dialed directory number. The subscriber location server 103OA determines that the directory number for the sub-B subscriber is not in the domain served by the server 103OA. Accordingly, as indicated by the action 8-3, the server 1030A sends the interrogation to the master server (NAPS) 1030M in order to determine the service provider serving the sub-B subscriber. Action 8-4 shows an address to the service provider of domain 1020B being returned to server 1030A, which in turn is advanced in action 8-5 to local exchange 1022A. Then, in action 8-6, the inclusive call of the home address of the 102OB domain service provider is routed by the local exchange 1022A to the GWA gateway. Action 8-7 shows the address or address message being transmitted between GWA and GWB gateways. Upon receiving the address message, in action 8-8 the gateway GWB interrogates the subscriber location server (NAPS) 103OB of the domain 1030B to determine the node in the domain 1020B to which the sub-B subscriber is connected. When the Subscriber Lease Server (NAPS) 1030B is interrogated, the server 1030B returns, in action 8-9, an NRN including a Network Address Prefix which is indicative of the Gate Mobile Switching Center (GMSC). The address message is transmitted to the GMSC as indicated by action 8-10. The GMSC translates the ISDN number of the mobile station (MSISDN) in the address message to a Global Title used to address the HLR (l). Normally the MSISDN is placed as the Global Title, but at this point a translation is needed to avoid updates at the intermediate signal transfer points (STPs). This translation can be carried out internally in the GMSC or an interrogation can be done to the database for the translation of MSISDN to an address number used to direct GT forward to the HLR (l). In action 8-11, the Home Location Register for the sub-B subscriber (being this, HLR (l)) is called by the GMSC. HLR (l) then calls the Mobile Switching Center with Visitor Location Registration- (MSC / VLR) [action 8-12], which selects and returns a roaming number to the HLR (l) [action 8-13] . Then the roaming number is, as reflected in action 8-14, passed to the GMSC. The GMSC uses «1 roaming number in the called person number parameter (CdPN) to address the MSC / VLR to where the sub-B subscriber resides [action 8-15]. Action 8-16 shows the sub-B subscriber being called using the international mobile subscriber number (IMSI). It should be understood that each of the gates in Figure 8 are connected to the subscriber location servers (NAPS) of their respective domains in order to process address messages that are calling to their respective domains. Additionally, it may happen that some ax calls outside a domain, such as calls made frequently, that the subscriber location server does not need to consult the master server (NAPS) 1030M if the master server 1030M downloads provider information to the domain server. In the example described, actions 8-3 and 8-4 can be performed internally by the server 103OA if the server 103OA has already stored an indication of the service provider for the sub-subscriber B. In addition, in a situation where the actions 8-3 and 8-4 do not involve querying the master server 1030M, it is possible for the master server 103OM to include in the address or address message the node in domain 1020B for sub-B subscriber. That is, master server 103OM may include, in the address message returned in action 8-4, the NRP of domain 1020B for sub-B subscriber if such is known by server 1030M. The inclusion of the receiver domain prefix will bypass actions 8-8 and 8-9 of Figure 8. The roaming number (mentioned above with respect to action 8-13, for example) may include a Network Address Prefix (NRP) ) suitable to locate to which HLR the subscriber belongs at that time. The assignment of MSISDN numbers within GSM has been done in a similar way as in a fixed network. For example, assignment of series of numbers by suppliers. However, when the mobile subscriber wishes to change their network and port provider (for example, relocate) their number, the MSISDN can no longer be used to locate the correct HLR. Instead, the NAPS must be consulted to obtain the NRP for the correct HLR. The HLR then communicates with the Visitor Location Register (VLR) which generates a roaming number consisting of an NRP and a temporary VLR number related to the subscriber in question. When the Mobile Switching Center with Visitor Location Registration (MSC / VLR) is accessed. The NRP is recognized as its own and the rest of the number is analyzed to obtain information of the VLR in which the Base Station Controller (BSC) resides at that moment the subscriber. It should be understood that the NRP / NRN used to locate the GMSC (as CdPN) may or may not be the same to locate the HLR (as a Global Title). In case the NRN is the IMSI number for the called MSISDN number, the address to the GMSC is increased and the GMSC can use this same IMSI number to locate the HLR and finally the HLR can use the IMSI number to recreate the MSISDN number . This requires an ISUP-based addressing to understand the IMSI numbering plan (not E.164 which is relevant to the MSISDN). The inclusion of the IMSI means that the MSISDN does not need to be transported in the network once the IMSI has been determined, this being, no additional data is transported.

Figure 8A and Figure 8B show that the home location register of the sub-B subscriber HLR (l) may be connected to the NAPS 1030B in a manner that the sub-B subscriber may use the same directory number for fixed or mobile Given such connection, as a result of commands initiated from the subscriber's mobile phone, the HLR (l) sends a "Register" message for the sub-B subscriber to the server (NAPS) 1030B. Upon receiving said "Registration" message, the server 1030B changes in its database the NRP associated with the subscriber directory number sub-B local central day serving the subscriber's fixed telephone number sub-B to GMSC. Otherwise, as illustrated by Figure 8B, a message of "deregistration" of the HLR (l) to server 1030B warns server 1030B to change its database so that the NRP associated with the sub-B subscriber directory number returns to the exchange identifier for the subscriber's sub-B landline. The HLR is addressed using TCAP; the HLR is likely to have a different destination than the GMSC since they usually reside in the same entity. Figure 9 illustrates the applicability of number portability for wireless terminal subscriber (CTM) mobility using a roaming approach to handle incoming (terminal) CTM calls. In Figure 9, domain 1020B '' provides CTM service and is illustrated as having an originating Service Switching Point (SSOo), Service Data Function Service logic (SDFsL) or Service Control Function logic. Service (SCFsL), mobility management of Service Data Functions (SDFmm) or mobility management of Service Control Functions (SCFmm) and a Terminal Service Switching Point SSPt. When a CTM subscriber changes service provider an International Portable User Identifier (IPUI) must be received (this being a new IPUI which is not portable), but the CTM number will be retained by the subscriber when it is ported. When a CTM subscriber is carried between service providers, it must be possible for a service provider network, in a relocability domain, to address a call to the subscriber ported based on a CTM number. To reach a terminal network, the same procedures are applied as discussed for Figure 8. That is, Figure 9 has actions 9-1 through 9-9 which are analogous to actions 8-1 through 8-9 of Figure 8, except that action 9-9 involves returning an NRN with a Network Address Prefix (NRP) to the sub-B Subscriber's SSPo. Action 9-10 shows the addressed message with the NRP being advanced to the SSPo and implicitly addressing the scpsl.

The SSPo translates the CTM number included in the addressed message into a Global Title (GT) used to address the SCFsl. Normally the CTM number is inserted as the Global Title, but now a translation is needed to avoid any update in the intermediate STPs. This translation can be done internally in the SSPo or an interrogation can be made to a database to obtain a translation of a CTM number to a number used for GT address to the SCPsl. Alternatively, the NRP delivered by the 103OB server can be used to address the correct SCPmm (which means that the NRP should not only point to the SSPo but also to the SCPmm). In action 9-11 the address SCPsl for sub-B subscriber is called. The CTM number is included in the initial DP sent from SSPo to SCPsl. The initial DP is the interrogation in ITU-T & ETSI standardized versions of the INAP protocol 1 & 2, and is the first operation sent from a service switching point to a service control point when an intelligence trigger ("IN") is detected at the service switching point. The SDFsl maintains an association between the CTM number and the identifier International Portable User Interface (IPUI). Action 9-2 shows the SCPsl of the Subscriber sub-B user (including the IPUI) to the SCPmm. In action 9-13 the SCPmm selects and returns a roaming number to SCPsl of sub-B subscriber. In action 9-14 it involves the SCPsl passing the roaming number to the SSPo. In action 9-15 the SSPo uses the roaming number in the address message (CdPN) to address the SSPt where the sub-B subscriber resides. In actions 9-16 the sub-B subscriber terminal is called using the international portable user identifier (IPUI). Action 9-17 shows a connection operation of the SCF m to the terminal service switching point of the person called CTM terminal (sub-B subscriber). It should be noted that if there is a fixed relationship with SSFo and SCFsl (which means that the addressing of SCFsl by SSFo is not based on the CTM number) then the SCFsl in the visiting network needs to translate the CTM number received in the SSFo interrogation to be able to recover an address which can be used as a Global Title to reach the SCFsl address of the named CTM subscriber. Alternatively, the visiting SCFsl can interrogate the NAPS by translating the CTM number to the SCFsl address for the called CTM subscriber. As a modification of the operation shown in Figure 9A, NAPS 103OA or NAPS 103OM can notify local exchange 1022A of the SSPo node address of domain 1020B »'. So that the call can be addressed as shown by the actions 9-6, 9-7 and 9-1Q. Then, the SSPo can interrogate the NAPS 103OB to find which SCFsl to invoke. After interrogation and detection of the appropriate SCFsl, actions 9-11 to 89-18 are performed as shown in Figure 9. This modification may occur when the operator domain 10220A and the operator domain 1020B have an agreement that a CTM subscriber can enter an area which is not served by the "own" operator of the CTM subscriber, and even the CTM subscriber can receive and originate calls, being this, using the visiting SSPo and the domiciliary SCFsl. Figure 9A and Figure 9B show that the SDFsl of the sub-B subscriber can be connected to the NAPS 103OB in a way that the sub-B subscriber can use the same directory number for CTM and fixed locations, similarly with the Figure 8A and Figure 8B described above. In this regard, as illustrated in Figure 9A, when a "Registration" message is received by the server (NAPS) 1030B of the SDFsl, the 103OB server associates in its database the NRP of the SDFsl of the sub-B subscriber with the sub-B subscriber's directory number, rather than the local exchange which serves the subscriber's sub-B landline. An opposite action of the "deregistration" is shown in Figure 9B. As an alternative to the above, it should also be understood that SCFsl can similarly carry out "registration" and "deregistration" actions. With respect to the portability of the subscriber number of a fixed location to a mobile location (for example, GSM or CTM), the originating local exchange must preferably always interrogate the NAPS since it is the NAPS that knows the type of Current access used by the called person. In a situation in which all calls do not automatically invoke a NAPS interrogation, the interrogation procedure can be initiated by setting a special category on the called line. This is to trap local calls to this subscriber also at the local exchange (since local calls can be made without an interrogation to NAPS as previously explained). In GSM and CTM applications, two addresses are usually required by a subscriber number. In GSM, the GMSC address and the HLR address (NRP) are required. In CTM the SSPo and the SCFsl or SDFsl (home address in CTM) are required. The fact that a subscriber number is "local" in a central also means that the subscriber number can be defined in several exchanges at the same time. The NAPD can be used to select which central address the calls, either randomly or by other criteria, such as time of day of the person called, time of day of call, number of the person called, blacklist of the person called, whitelist of a person called, teleservice type (for example, FAX, voice), Transmission Medium Request (TMR), type of station currently in use (GSM, CTM, ordinarily), considerations involving that the NAPS is in a different time zone than the person called, etc. As mentioned above, Figure 12 shows the format of a called person parameter (CdPN) of the Rec. ITU-T standard Q.763, an industry standard. The called person parameter (CdPN) is an address message used to address calls between exchanges in a telecommunications system. The present invention utilizes a NRF number relocability marker which is used to indicate whether the called number associated with a CdPN parameter has number relocability characteristics of the present invention. In a modality, the NRF is selected as one of the replacement values of the NAI. Hereinafter, the fixation of a NRF relocability marker is understood for said modality as a fixation of an appropriate value in the NAI as illustrated in Fig. 2. It should be understood that the present invention is not limited to the use of the industry standard of the person parameter called CdPN, instead other types of message addressing may be used. It also happens that Figure 8 and other figures referenced therein employ the Network Address Prefix (NRPs) that illustratively has three digits. The use of three digits in the figures is only for convenience for example, it is understood that the invention is not restricted to three digits and that a smaller number (or more likely) a greater number of digits can be employed as is allowed by the protocols implemented in each case. Neither the invention is specific to the lengths or order of other fields shown in Figure 12. The Network Addressing Prefix (NRP) of the present invention is an example of a node exchange or identifier which is included in the field of address signal (ASF) of the addressed message in such a way as to precede the directory number of the called party. It should be understood that the node identifier (NI) may be included in positions other than the initial bit positions of the ASF addressing message. The present invention therefore solves previously anticipated problems by providing MSIDN portability to a mobile subscriber. The invention faces the problem of the mobile subscriber who visits foreign countries, since the foreign network is visited by the mobile subscriber can interrogate the country of origin of the mobile station with the first STP found in the country of origin that sends a request to a database or NAPS that serves the STP, and with this the call is routed to the current service provider for the visiting mobile subscriber. In addition, when a service provider reorganizes a subscriber with respect to its HLR, only the database or NAP of the network needs to be updated, thus obviating any modification of global title analysis in the reorganization of the provider's network. service and other networks. While the invention has been particularly shown and described with reference to the preferred embodiments thereof, it will be understood by those skilled in the art that various alterations in form and detail can be made therein without departing either from spirit or from scope. of the invention. For example, it should be understood that the number (four) of domains shown in Figure A is for illustration purposes only, and that a greater or lesser number of domains may be employed.

Claims (1)

1. A telecommunications network comprising a set of domains, at least one of the domains in the set of domains is a mobile telecommunications domain serving mobile telecommunication stations, wherein a call originating domain included in the set of domains accesses a a subscriber number portability database for obtaining information to be included as a parameter in the addressing of a message to address a call made from a call originating domain to a called mobile station, and wherein the information includes a home address of a node in the telecommunications domain which at that time serves the called mobile subscriber. The network of claim 1, wherein a plurality of domains in the set are mobile telecommunications domains, and wherein when a portable mobile station changes membership of a first mobile telecommunications domain to a second mobile telecommunications domain, a in the mobile subscriber number portability database is updated to include an address of a node of the second mobile telecommunications domain. The network of claim 1, wherein the information to be included as a parameter in the addressed message is an address of a gate node in the telecommunications domain which at that time serves the called mobile subscriber. The network of claim 1, wherein the gateway node of the calling originator domain accesses the subscriber number portability database to obtain information to be included in the addressed message. The network of claim 4, wherein the number portability database of the mobile subscriber is included as part of the gate node which accesses the database. The network of claim 1, the local exchange node of the calling originating domain accesses the subscriber number portability database to obtain information to be included as a parameter in the addressed message. The network of claim 1, wherein the subscriber information of the mobile subscriber number portability database includes an address of a local location register which at that time serves the called mobile subscriber. The network of claim 1, wherein the information obtained from the mobile subscriber number portability database includes an international mobile subscriber number (IMSI) of the called mobile subscriber. The network of claim 8, wherein the node in the telecommunications domain which at that time serves the called mobile station uses the international mobile subscriber number (IMSI) of the called subscriber to address a home location register (HLR). ) which serves the called subscriber. . The network of claim 1, wherein the calling originating domain is one of a PSTN domain and an ISDN domain. . The network of claim 1, wherein the calling originating domain is one of a plurality of mobile telecommunications domains. . The network of claim 1, wherein at least two of the plurality of domains are served by different telecommunications service providers. . The network of claim 1, wherein - the information obtained from the mobile subscriber number portability database is included as a parameter in a routing signal field of an industry standard called a called person number parameter . . The network of claim 1, wherein a plurality of mobile telecommunications domains comprises mobile subscriber number portability databases, and wherein gate nodes of the plurality of mobile telecommunications domains comprising portability databases of mobile subscriber number access the portability database of corresponding mobile subscriber number. 15. The network of claim 14, wherein the network further includes a central administration system which updates mobile subscriber number portability databases when a mobile subscriber changes membership of a first mobile telecommunications domain to a second mobile telecommunications domain. 6. A method for directing calls through a telecommunications network, the telecommunications network has a set of domains, at least one of the domains in the set of domains is a mobile telecommunications domain serving mobile telecommunication stations, the method comprises; access, in the originating original call domain included in the set of domains, to a portability database of mobile subscriber number to obtain an address of a node of the telecommunications domain which at that time serves a mobile subscriber called; the inclusion of the address of the telecommunication domain node which at that time serves a mobile subscriber called as a parameter in a addressed message to address a call made from the calling originating domain to a called mobile subscriber. 17. The method of Claim 16, wherein the address included as a parameter in the addressed message is the address of a gateway node of the telecommunications domain "which at that time serves a called mobile subscriber. of Claim 16, wherein a plurality of domains in the set of domains are mobile telecommunication domains, and wherein the method further comprises: updating the portability database of mobile subscriber number when a subscriber changes membership from a first mobile telephone domain to a second mobile telecommunications domain where the home address of the second mobile telephone domain node is associated in the mobile subscriber number portability database with the mobile subscriber. Claim 16, further comprising the use of a gateway node of the calling originator domain to access the base of portability data of mobile subscriber number. The method of Claim 16, further comprising the use of a local exchange node of the calling originating domain to access the mobile subscriber number portability database. The method of Claim 16, further comprising: accessing, in the originator domain of call included in the set of domains, to the portability database of mobile subscriber number to obtain an address of an address register local which at that time serves a mobile subscriber called; the inclusion of the address of the local address register which at that time serves a mobile subscriber called as a parameter in the addressed message. The method of Claim 16, wherein the information obtained from the mobile subscriber number portability database includes an international mobile subscriber number (IMSI) of the called subscriber. 23. The method of Claim 22, further including the step of using the international mobile subscriber number (IMSI) of the called subscriber to address an address allocation register (HLR) which serves the called subscriber. 24. The method of Claim 16, wherein the calling originator domain is a PST domain and an ISDN domain. 25. The method of Claim 16, wherein the calling originating domain is one of a plurality of mobile telecommunications domains. . The method of Claim 16, wherein at least two of the plurality of domains are served by different telecommunications service providers. . The method of Claim 16, wherein the information obtained from the mobile subscriber number portability database is included as a parameter in an address signal field of an industry standard called the called party's parameter. . The method of Claim 16, wherein each of the plurality of mobile telecommunications domains comprises mobile subscriber number portability databases, and wherein the gate nodes of the plurality of mobile telecommunications domains comprise databases. of mobile subscriber number portability accessing the corresponding mobile subscriber number portability database, and wherein the method further comprises the use of a central administration system to update mobile subscriber number portability databases when a mobile subscriber changes membership of a first mobile telecommunications domain to a second mobile telecommunications domain.