WO2016137387A1 - Procédés et nœuds de passerelle pour desservir une pluralité de plmn - Google Patents

Procédés et nœuds de passerelle pour desservir une pluralité de plmn Download PDF

Info

Publication number
WO2016137387A1
WO2016137387A1 PCT/SE2016/050152 SE2016050152W WO2016137387A1 WO 2016137387 A1 WO2016137387 A1 WO 2016137387A1 SE 2016050152 W SE2016050152 W SE 2016050152W WO 2016137387 A1 WO2016137387 A1 WO 2016137387A1
Authority
WO
WIPO (PCT)
Prior art keywords
query
subscriber
network domain
serving
information
Prior art date
Application number
PCT/SE2016/050152
Other languages
English (en)
Inventor
Åke BUSIN
Original Assignee
Telefonaktiebolaget Lm Ericsson (Publ)
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Telefonaktiebolaget Lm Ericsson (Publ) filed Critical Telefonaktiebolaget Lm Ericsson (Publ)
Publication of WO2016137387A1 publication Critical patent/WO2016137387A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W68/00—User notification, e.g. alerting and paging, for incoming communication, change of service or the like
    • H04W68/12—Inter-network notification
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/26—Network addressing or numbering for mobility support
    • H04W8/28—Number portability ; Network address portability

Definitions

  • the present disclosure relates to gateway nodes, methods, a computer program and a carrier, e.g. a gateway node that serves multiple Public Land Mobile Networks (PLMNs).
  • PLMNs Public Land Mobile Networks
  • a Gateway Mobile Location Center supports location-based services.
  • a GMLC may for example receive a request for the geographic location of a subscriber, and obtain an estimate of that location for responding to the request.
  • the GMLC may obtain this estimate in part by querying a subscriber database (e.g., Home Location Register, HLR) for the Public Land Mobile Network (PLMN) to which the subscriber is subscribed.
  • a subscriber database e.g., Home Location Register, HLR
  • PLMN Public Land Mobile Network
  • a GMLC may support multiple Public Land Mobile Networks (PLMNs) for certain wireless technologies (e.g., Global System for Mobile Communications, GSM, and Wideband Code Division Multiple Access, WCDMA).
  • PLMNs Public Land Mobile Networks
  • the GMLC may do so for instance using Global Title routing in a Signaling System No. 7 (SS7) network.
  • SS7 network can determine an appropriate PLMN to which to route a message (e.g., query) by analyzing leading parts of the MSISDN.
  • a GMLC under some circumstances also supports multiple PLMNs even when mobile number portability (MNP) is deployed.
  • MNP mobile number portability
  • the SS7 network includes a number portability function (e.g., a mobile number portability signaling relay function, MNP-SRF).
  • MNP-SRF mobile number portability signaling relay function
  • a number portability function is aware of ported numbers and routes queries to the appropriate HLR. The number portability function may for instance route a query from the GMLC to the HLR in the subscription PLMN.
  • the subscription PLMN is the PLMN holding the subscription corresponding to the subscriber's MSISDN and may be different from the PLMN owning the MSISDN number range if the MSISDN has been ported to the new PLMN (e.g. , if a customer switched carriers but kept their phone number) (see also 3GPP TS 23.066 V12.0.0).
  • a GMLC may not support multiple PLMNs when MNP is deployed under other circumstances.
  • LTE Long Term Evolution
  • the route to the HSS in the subscription PLMN may be configured in GMLC based on MISDN number ranges. This implies that MNP cannot be supported.
  • the assumption is that Diameter networks via which queries are routed to the HSS do not support MNP.
  • a gateway node e.g., a GMLC exploits the number portability function that serves a first network domain (e.g., a GSM/WCDMA domain) in order to address a subscriber database query to be sent towards a second network domain (e.g., an LTE domain) not served by a number portability function. That is, the gateway node exploits the first network domain's resolution of number portability in order to address a query towards a second network domain that is incapable of such resolution.
  • a first network domain e.g., a GSM/WCDMA domain
  • LTE domain an LTE domain
  • the gateway node does so when a subscriber is attached to both the first and second network domains, e.g., simultaneously.
  • one or more embodiments herein include a method performed by a gateway node serving multiple Public Land Mobile Networks, PLMNS, that each includes a first network domain and a second network domain.
  • the method includes obtaining information from which a subscription PLMN of a subscriber is identifiable, in response to sending a first subscriber database query towards a first network domain that is served by a number portability function.
  • the method also includes addressing a second subscriber database query based on the obtained information, and sending the second subscriber database query towards a second network domain that is not served by a number portability function.
  • this obtained information comprises an International Mobile Subscriber Identity, IMSI, of the subscriber.
  • IMSI International Mobile Subscriber Identity
  • addressing the second subscriber database query may comprises identifying the subscription PLMN from the IMSI and addressing the second subscriber database query based on that identifying.
  • addressing the second subscriber database query may comprises extracting information from the IMSI and addressing the second subscriber database query using the extracted information.
  • addressing the second subscriber database query comprises including the IMSI in the second subscriber database query.
  • sending the second subscriber database query may comprise sending the second subscriber database query towards a Diameter network configured to route the second subscriber database query to a Home Subscriber Server, HSS, in accordance with the addressing.
  • Still other embodiments herein include a method performed by a gateway node serving multiple Public Land Mobile Networks, PLMNS, that each includes a first network domain and a second network domain.
  • the method comprises receiving a request for a location of a subscriber.
  • the method also comprises, responsive to the request, generating a first query requesting information about a serving node that is serving the subscriber in the first network domain, and sending the first query towards a number portability function serving the first network domain.
  • the number portability function routes queries, on an individual number by number basis, to subscriber databases associated with PLMNs to which subscriber identifier numbers have been respectively ported (e.g., at least for those numbers that have been ported).
  • the method further comprises receiving a response to the first query.
  • the response includes information indicating a subscription PLMN to which the subscriber is subscribed.
  • the method also comprises generating a second query to a subscriber database for the second network domain of the subscription PLMN, by addressing the second query using the response.
  • the second query requests information about a serving node that is serving the subscriber in the second network domain and that has information on the location of the subscriber.
  • the second network domain is not served by a number portability function.
  • the method further comprises sending the second query to the subscriber database for the second network domain of the subscription PLMN, and requesting the location of the subscriber from the serving node in the second network domain.
  • the first query includes a Mobile Subscriber Integrated Services Digital Network Number, MSISDN, of the subscriber.
  • MSISDN Mobile Subscriber Integrated Services Digital Network Number
  • the response includes an International Mobile Subscriber Identity, IMSI, of the subscriber, and addressing may comprise addressing the second query using the IMSI of the subscriber.
  • addressing the second query using the response may comprise including the IMSI in the second query.
  • addressing the second query using the response may comprise addressing the second query using information extracted from the IMSI. This extracted information may comprise a Mobile Country Code, MCC, and a Mobile Network Code, MNC.
  • the first network domain is a Global Systems for Mobile Communications, GSM, or Wideband Code Division Multiple Access, WCDMA, domain
  • the second network domain is a Long Term Evolution, LTE, domain
  • the subscriber database of the second network may be a Home Subscriber Server, HSS.
  • the number portability function serving the first network domain resides in a Signaling System No. 7, SS7, network
  • the number portability function is a Mobile Number Portability Signaling Relay Function, MNP-SRF
  • the second query is sent to the subscriber database for the second network domain via a Diameter network.
  • the gateway node is a Gateway Mobile Location Center, GMLC.
  • the serving node that is serving the subscriber in the first network domain is a Mobile Subscription Center, MSC, or Serving General Packet Radio Service Support Node, SGSN.
  • the first query is a Mobile Application Part, MAP, Send Routing
  • SRI, message, and the second query is a Diameter Routing Information Request, RIR, message.
  • Still other embodiments herein include a gateway node configured to serve multiple Public Land Mobile Networks, PLMNS, that each includes a first network domain and a second network domain, the gateway node is configured to receive a request for a location of a subscriber. Responsive to the request, the gateway node is configured to generate a first query requesting information about a serving node that is serving the subscriber in the first network domain, and send the first query towards a number portability function serving the first network domain. The gateway node is also configured to receive a response to the first query. The response includes information indicating a subscription PLMN to which the subscriber is subscribed.
  • the gateway node is further configured to generate a second query to a subscriber database for the second network domain of the subscription PLMN, by addressing the query using the response.
  • the second query requests information about a serving node that is serving the subscriber in the second network domain and that has information on the location of the subscriber.
  • the second network domain is not served by a number portability function.
  • the gateway node is also configured to send the second query to the subscriber database for the second network domain of the subscription PLMN, and request the location of the subscriber from the serving node in the second network domain.
  • Embodiments further include a computer program comprising instructions which, when executed by at least one processor of a gateway node, causes the gateway node to carry out any of the methods described herein.
  • This carrier may be one of an electronic signal, optical signal, radio signal, or computer readable storage medium.
  • Yet another embodiment relates to a gateway node for serving multiple PLMNs that each includes a first network domain and a second network domain.
  • the gateway node of that embodiment comprises:
  • a request receiving module for receiving a request for a location of a subscriber
  • a first query generating module for, responsive to said request, generating a first query requesting information about a serving node that is serving the subscriber in the first network domain, and sending the first query towards a number portability function serving the first network domain;
  • a response receiving module for receiving a response to the first query, wherein the response includes information indicating a subscription PLMN to which the subscriber is subscribed;
  • a second query generating module for generating a second query to a subscriber
  • the database for the second network domain of the subscription PLMN, by addressing the query using the response, wherein the second query requests information about a serving node that is serving the subscriber in the second network domain and that has information on the location of the subscriber , wherein the second network domain is not served by a number portability function;
  • a query sending module for sending the second query to the subscriber database for the second network domain of the subscription PLMN
  • a location requesting module for requesting the location of the subscriber from the
  • Figure 1 is a block diagram of a wireless communication system that includes a gateway node according to one or more embodiments.
  • Figure 2 is a logic flow diagram of a method performed by a gateway node according to one or more embodiments.
  • Figure 3 is a logic flow diagram of a method performed by a gateway node according to one or more other embodiments.
  • FIG. 4 is a block diagram of a wireless communication system that include a GMLC as the gateway node according to some embodiments.
  • Figure 5 is a signaling diagram for obtaining location information according to one or more embodiments.
  • Figure 6 is a block diagram illustrating communication interfaces of a GMLC according to some embodiments.
  • Figure 7 is a logic flow diagram of a method performed by a gateway node according to still other one or more embodiments.
  • Figure 8 is a block diagram of a gateway node according to one or more embodiments.
  • FIG. 9 is a block diagram of a gateway node according to one or more other embodiments.
  • FIG. 1 illustrates a wireless communication system 10 according to one or more embodiments.
  • the system 10 includes a gateway node 12.
  • the gateway node 12 serves multiple Public Land Mobile Networks, PLMNs. As shown, for instance, the gateway node 12 serves PLMN 1 and PLMN 2.
  • Each PLMN includes a first network domain 14 (e.g., a GSM or WCDMA domain) and a second network domain 16 (e.g., an LTE domain).
  • Each PLMN is associated with (e.g., owns or uses) a subscriber database in each of the first and second network domains 14, 16.
  • PLMN 1 is associated with a subscriber database (DB) 18A in the first network domain 14 and a subscriber database 18B in the second network domain 16.
  • DB subscriber database
  • subscriber database 18B may for instance be Home Location Registers (HLRs).
  • PLMN 2 is associated with a subscriber database 18C in the first network domain 14 and a subscriber database 18D in the second network domain 16.
  • These subscriber databases 18C-18D may be Home
  • HSSs Subscriber Servers
  • the gateway node 12 is communicatively connected to these subscriber databases 18A-D via different signaling networks 20A-B.
  • Signaling network 20A may for instance be a Signaling System No. 7 (SS7) network while signaling network 20B may be a Diameter network.
  • the gateway node 12 is configured to send subscriber database queries to the subscriber databases 18A-D in the first and second network domains 14, 16 via the signaling networks 20A-B.
  • SS7 Signaling System No. 7
  • a number portability function 22 in signaling network 20A serves the first network domain 14.
  • the number portability function 22 routes a query from the gateway node 12 to a particular one of the subscriber databases 18A-18B for the first network domain 14. Where the query is associated with a particular subscriber 24, for example, the number portability function 22 routes the query to whichever of the subscriber databases 18A-18B is associated with the PLMN 1 or 2 to which the subscriber 24 is subscribed (i.e., the subscription PLMN).
  • the number portability function 22 does so even if the subscriber's identifier number (e.g., MSISDN) has been ported; that is, even if the subscription PLMN is different from the PLMN owning the
  • the number portability function 22 may route queries, on an individual number by number basis, to subscriber databases associated with PLMNs to which subscriber number identifier numbers have been respectively ported, i.e., at least for those numbers that have in fact been ported.
  • the gateway node 12 need simply address a subscriber database query using a subscriber's MSISDN and send the query towards the number portability function, which will in turn relay the query on to the subscriber database associated with the subscription PLMN.
  • the gateway node 12 in such a case need not have any information regarding the subscription PLMN in order to send a subscriber database query to the first network domain 14.
  • the second network domain 16 is not served by a number portability function. That is, signaling network 20B lacks a number portability function similar to that in signaling network 20A. This means that signaling network 20B is incapable of routing queries, on an individual number by number basis, to subscriber databases associated with PLMNs to which subscriber number identifier numbers have been respectively ported.
  • the gateway node 12 in some embodiments exploits the number portability function 22 that serves the first network domain 14 in order to address a subscriber database query to be sent towards the second network domain 14. That is, the gateway node 12 exploits the first network domain's resolution of number portability in order to address a query towards a second network domain that is incapable of such resolution. In one embodiment, the gateway node 12 does so when the subscriber 24 is attached to both the first and second network domains 14, 16. In any event, Figure 2 illustrates a method 100 performed by the gateway node 12 according to one or more embodiments in this regard.
  • the method 100 comprises obtaining information from which a subscription PLMN of a subscriber 24 is identifiable, in response to sending a first subscriber database query towards a first network domain 14 that is served by a number portability function 22 (Block 102).
  • the method 100 further comprises addressing a second subscriber database query based on the obtained information (Block 104). With the second query addressed in this way, the method 100 also entails sending the second subscriber database query towards a second network domain 16 that is not served by a number portability function (Block 106).
  • the obtained information includes an International Mobile Subscriber Identity, IMSI, of the subscriber 24.
  • IMSI International Mobile Subscriber Identity
  • the IMSI may for instance be included in a response that the gateway node 12 receives to the first subscriber database query.
  • the gateway node 12 may extract information from the IMSI and address the second subscriber database query using that extracted information.
  • the extracted information may for instance include a Mobile Country Code (MCC) and a Mobile Network Code (MNC).
  • MCC Mobile Country Code
  • MNC Mobile Network Code
  • a PLMN identifier in some embodiments is a function of the MCC and MNC, meaning that the subscription PLMN for the subscriber 24 is identifiable or otherwise determinable from the MCC and MNC (and thereby the IMSI).
  • the gateway node 12 identifies the subscription PLMN from the IMSI and addresses the second subscriber database query based on that identifying, e.g., by addressing the query with a PLMN identifier derived from the MCC and MNC.
  • signaling network 20B is configured to simply route a query to whichever PLMN the query is addressed. The signaling network 20 may be configured to do so because the signaling network 20B lacks a number portability function with the ability to distinguish the addressed PLMN from a potentially different subscription PLMN to which the subscriber has ported his or her mobile number.
  • the gateway node 12 may include the IMSI in the query.
  • the signaling network 20B may be configured to perform query routing based on the IMSI, e.g., as opposed to PLMN identity. No matter the particular addressing approach, though, the gateway node 12 in some embodiments performs this addressing by populating certain elements in a message
  • the gateway node 12 extracts the MCC and MNC from the IMSI and creates the "mnc ⁇ MNC>.mcc ⁇ MCC>.3gppnetwork.org" domain name to which the query is addressed.
  • the gateway node 12 performs method 100 as part of a process for obtaining a location of the subscriber 24, e.g., in response to a request for that location from a location client 26 (e.g., a LBS client).
  • the gateway node 12 may generate the first and second queries in order to obtain information about the nodes 28A, 28B serving the subscriber 24 in the first and second network domains 14, 16, respectively.
  • these serving nodes 28A, 28B have information on the location of the subscriber 24 with respect to the first and second network domains 14, 16.
  • Figure 3 illustrates a method 200 performed by the gateway node 200 according to one or more of these embodiments.
  • the method 200 includes receiving a request for a location of a subscriber 24 (Block 202).
  • the method 200 also includes, responsive to the request, generating a first query (Block 204).
  • the first query requests information about a serving node 28A that is serving the subscriber 24 in the first network domain 14.
  • the requested information may for instance include an identity of an MSC or SGSN serving the subscriber 24 in the first network domain 14. Regardless, this first query is sent towards the number portability function 22 serving the first network domain 14.
  • the first query may include the subscriber's MSISDN.
  • the method 200 further includes receiving a response to the first query (Block 206).
  • This response includes information (e.g., IMSI) indicating a subscription PLMN to which the subscriber 24 is subscribed.
  • the method 200 also entails generating a second query to a subscriber database for the second network domain 16 of the subscription PLMN, by addressing the second query using the response (e.g., using the information such as IMSI included in the response) (Block 208).
  • This second query requests information about a serving node 28B that is serving the subscriber 24 in the second network domain 16 and that has information on the location of the subscriber 24.
  • This second network domain 16 is not served by a number portability function.
  • the response includes an IMSI of the subscriber.
  • Addressing in Block 208 may therefore entail in some embodiments addressing the query using the subscriber's IMSI. Addressing may for instance comprise including the IMSI in the second query or addressing the second query using information extracted from the IMSI (e.g., MCC and MNC).
  • the method 200 further includes sending the second query to the subscriber database for the second network domain 16 of the subscription PLMN (Block 210).
  • the gateway node 12 in this regard may send the second query towards signaling network 20B, which routes the second query to the subscriber database for addressed PLMN.
  • the method 200 may finally include requesting the location of the subscriber 24 from the serving node 28B in the second network domain 16 (Block 212).
  • the gateway node 12 may for instance receive in response to the second query the identity of serving node 28B, and then send a location request to that serving node 28B.
  • Figure 4 illustrates some embodiments herein in a context where the first network domain 14 is a GSM or WCDMA domain 30, and the second network domain 16 is an LTE domain 32.
  • the subscriber databases 18A-18B comprise Home Location Registers (HLRs) 34A-34B in the GSM / WCDMA domain 30 for PLMN 1 and 2, respectively.
  • subscriber databases 18C-18D comprise Home Subscriber Servers (HSSs) 34C-34D in the LTE domain 32 for PLMN 1 and 2, respectively.
  • HLRs Home Location Registers
  • HSSs Home Subscriber Servers
  • Figure 4 illustrates signaling network 20A as an SS7 network 36A that includes a Mobile Number Portability Signaling Relay Function (MNP-SRF) 38, and signaling network 20B as a Diameter network 36B that lacks such an MNP-SRF.
  • MNP-SRF 38 in the SS7 network 36A may be connected to or otherwise associated with an MNP-DB 40.
  • the gateway node 12 herein is shown as a GMLC 42.
  • a GSM/WCDMA network domain 30 supports MNP by incorporating an MNP-SRF node 38 in a SS7 network 36A connecting the GMLC 42 and the HLRs 34A-B.
  • the MNP-SRF 38 routes queries, on an individual number by number basis, to subscriber databases associated with PLMNs to which subscriber identifier numbers have been respectively ported.
  • the MNP-SRF 38 is able to determine routing information for the new PLMN.
  • the GMLC 42 assumes messages to the HLRs 34A-B will be routed to a HLR at a correct PLMN (i.e., a subscription PLMN) based on the MSISDN provided in the message.
  • a correct PLMN i.e., a subscription PLMN
  • the MNP-SRF 38 retrieves the subscription PLMN from an internal or external DB 40.
  • the response will include the IMSI of the subscriber 24.
  • the MNP-SRF 38 communicates with the MNP database (MNP-DB) 40 that is either internal or external to the MNP-SRF 38.
  • MNP-DB 40 stores information about ported subscriber information (e.g., relating to which PLMN a MSISDN has been ported to).
  • the Diameter network 36B (e.g., as used in connection with LTE networks) does not include a MNP-DB and is therefore unable to determine a PLMN for a ported MSISDN.
  • MNP-DB may use various protocols & procedures to interface with it e.g. INAP, MAP SRI, MAP ATI, and ENUM. Together with potential customer specific variations, the number of protocols and variants to support may get large and costly. Also, the MNP-DB may be integrated with the MNP-SRF and thus not have an external interface.
  • the GMLC may need to query both HLR and HSS for the serving node of the UE concurrently or in sequence.
  • the GMLC heretofore may not know which HSS to query because it does not know which PLMN a subscriber is currently subscribed to.
  • One or more embodiments herein enable the gateway node 12 (e.g., the GMLC 42) to determine routing information for a ported MSISDN.
  • the GMLC 42 queries an HLR in the GSM / WCDMA domain 30 using the MNP-SRF 38 in the SS7 network 36A to resolve any porting. Then, the IMSI of the subscriber 24 returned in response from the HLR is used to determine which is the subscription PLMN. Then, the GMLC 42 gives the query to the HSS in the LTE domain 32 corresponding routing information. From received HLR
  • the IMSI can be retrieved and/or information can be extracted from the IMSI to enable routing to an HSS when also number portability is deployed. Consequently, MNP can be supported for LTE without adding any new interfaces.
  • a location procedure is started in which a location request is received from a location client.
  • the GMLC 42 first retrieves information about a serving node (e.g., an identifier) from the HLR, by sending a Send Routing Information (SRI) query to the HLR via the MNP-SRF 38.
  • SRI Send Routing Information
  • the GMLC 42 gets the IMSI of the subscriber's UE in the response from the HLR.
  • the GMLC 42 extracts the MCC and MNC from the IMSI to determine the subscription PLMN.
  • the knowledge of the subscription PLMN is used to populate elements in the message that allows the Diameter network to route the message to the correct HSS. Examples of such elements are
  • the GMLC 42 inserts the IMSI into the message to the HSS.
  • the Diameter network 36B is configured such it can route to correct HSS based on the IMSI.
  • Figure 5 is a signaling diagram illustrating one example of this alternative instantiation.
  • Step A of Figure 5 the GMLC 42 starts a location procedure and needs to retrieve serving node information for the target UE from both HLR and HSS as UE may be attached to both GSM/WCDMA and HSS.
  • the UE may have a ported MSISDN.
  • the GMLC 42 first sends a Send Routing Information (SRI) including the MSISDN towards the HLR 34A via the MNP-SRF 38.
  • the MNP-SRF checks if the MSISDN is ported and if applicable adds routing information and forward the SRI to the HLR 34A.
  • the HLR 34A responds in Step D with a SRI response that includes the IMSI of the subscriber's UE.
  • Step E the GMLC 42 analyzes the received IMSI to determine the subscription PLMN.
  • Step F the GMLC 42 retrieves serving node information from the HSS 34C by sending a Routing Information Request (RIR) message via the Diameter network 36B.
  • RIR Routing Information Request
  • the RIR message is populated with (e.g., based on configurable tables in the GMLC 42) message element(s) that allow the Diameter network 36B to route the RIR message to the correct HSS. Examples of such message elements are Destination-Realm, Destination-Host and IMSI.
  • Step G the Diameter network 36B transports the RI R message to the correct HSS 34C.
  • Step H the HSS 34C returns information to the GMLC 42 by sending a Routing Information Answer (RIA) message.
  • RIA Routing Information Answer
  • Step “C” The "routing information" in Step “C” above helps the SS7 network 36A route the SRI message to the correct HLR 34A.
  • the MNP-SRF 38 querying the MNP- DB 40 to determine if the MSISDN has been ported. This would occur between Steps B and C in Figure 5 and would enable the MNP-SRF 38 to determine whether the MSISDN has been ported. If the MSISDN has not been ported, the MNP-SRF 38 would still send the SRI message to the HLR 34A (Step C in Figure 5) but would not add the routing information described above in Step C.
  • Figure 6 illustrates various interfaces between the different nodes in Figure 5 according to some embodiments.
  • the GMLC interfaces the diameter network 36B via the SLh interface, and interfaces the MNP-SRF 38 via the Lh interface.
  • the GMLC 42 interfaces an MCS/SGSN 42A via the Lg interface, and interfaces an MME 42B via the SLg interface.
  • FIG. 7 illustrates still another example method 300 implemented by a gateway node 12 (e.g., a GMLC 42) serving multiple PLMNS that each include a first network domain 14 (e.g., GSM / WCDMA) and a second network domain 16 (e.g., LTE).
  • the gateway node 12 receives a request for a location of a subscriber (block 302). Responsive to the request, the gateway node 12 generates (block 304) a first query requesting routing information that identifies a PLMN to which the subscriber 24 is subscribed, and sends the first query towards a number portability function 22 (e.g., a MNP-SRF 38) serving the first network domain 14.
  • a number portability function 22 e.g., a MNP-SRF 38
  • a number portability function 22 routes queries, on an individual number by number basis, to subscriber databases 18A-18D owned by PLMNs to which subscriber identifier numbers (e.g., MSISDNs) have been respectively ported, i.e., at least when those numbers have in fact been ported.
  • the gateway node 12 generates (block 306) a second query to a subscriber database (e.g., a HSS) for the second network domain 16 of the identified PLMN, by addressing the query using the routing information.
  • the second query requests address information identifying an address of a serving node 28B that is serving the subscriber 24 in the second network domain 16 and that has information on the location of the subscriber 24.
  • the second network domain 16 is not served by a number portability function.
  • the gateway node 12 sends the second query to the subscriber database for the second network domain 16 of the identified PLMN (block 308), and requests the location of the subscriber 24 from the serving node 28B using said address information (block 310).
  • the first query in some embodiments includes a MSISDN of the subscriber 24 (see Step B in Figure 5).
  • the gateway node 12 is a GMLC 42.
  • the number portability function 22 is a MNP-SRF 38.
  • the number portability function 22 serving the first network domain 14 resides in a SS7 network 36A, and the second query is sent to the subscriber database for the second network domain 16 via a Diameter network 36B.
  • the first network domain 14 is a GSM or WCDMA domain 30, and the second network domain 16 is an LTE domain 32.
  • the subscriber database of the second network domain 16 is a HSS 34C, D.
  • a serving node 28A serving the subscriber 24 in the first network domain 14 is a MSC or a SGSN, and/or a serving node 28B serving the subscriber 24 in the second network domain 14 is a MME.
  • the first query is a SRI message
  • the second query is a RIR message.
  • the requested routing information comprises an IMSI of the subscriber 24 (see Step D of Figure 5).
  • addressing the query using the routing information comprises either: including the IMSI in the second query (as shown in Step F of Figure 5), or including a MCC and MNC extracted from the IMSI in the second query.
  • method 100 is performed as part of supporting a Voice over LTE (VoLTE deployment) with one MSISDN number range served by multiple LTE PLMNs. That is, within a VoLTE deployment it is possible for one IP Multimedia Subsystem (IMS) owning one or more MSISDN number ranges to be served by multiple LTE PLMNs having separate HSSs that do not have correlation to the MSISDN number ranges. Without knowing the IMSI it is not possible for the gateway node 12 to determine which is the correct HSS to use. Accordingly, the gateway node 12 in some embodiments employs the first subscriber database query to retrieve the IMSI, in order to determine how to address the second subscriber database query to the correct HSS.
  • VoIP Voice over LTE
  • IMS IP Multimedia Subsystem
  • the gateway node 12 may be configured to perform any of the methods 100, 200, 300 or other processing herein by any functional means or units.
  • Figure 8 illustrates one or more embodiments where the gateway node 12 is realized as a gateway node 400 that comprises a processing module 405.
  • the processing module 405 may be a means, one or more hardware modules and/or one or more software modules for performing the methods described herein.
  • Figure 8 shows the processing module 405 as comprising in some embodiments a obtaining module 410, an addressing module 415, and a sending module 420, e.g., for implementing the method in Figure 2.
  • the obtaining module 410 is for obtaining information from which a subscription PLMN of a subscriber 24 is identifiable, in response to sending a first subscriber database query towards a first network domain 14 that is served by a number portability function 22.
  • the addressing module 415 is for addressing a second subscriber database query based on the obtained information.
  • the sending module 420 is for sending the second subscriber database query towards a second network domain 16 that is not served by a number portability function.
  • Figure 8 also shows the processing module 405 as comprising in other embodiments a request receiving module 425, a first query generating module 430, a request receiving module 435, a second query generating module 440, a sending module 445, and a location requesting module 450 e.g., for implementing the method in Figure 3.
  • the request receiving module 425 is for receiving a request for a location of a subscriber.
  • the first query generating module 430 is for, responsive to said request, generating a first query requesting information about a serving node 28A that is serving the subscriber 24 in the first network domain 14, and sending the first query towards a number portability function 22 serving the first network domain 14.
  • a number portability function 22 routes queries, on an individual number by number basis, to subscriber databases associated with PLMNs to which subscriber identifier numbers have been respectively ported, i.e., at least when those numbers have in fact been ported.
  • the response receiving module 435 is for receiving a response to the first query.
  • the response includes information indicating a subscription PLMN to which the subscriber 24 is subscribed.
  • the second query generating module 440 is for generating a second query to a subscriber database for the second network domain 16 of the subscription PLMN, by addressing the second query using the response.
  • the second query requests information about a serving node 28B that is serving the subscriber 24 in the second network domain 16 and that has information on the location of the subscriber 24.
  • the second network domain 16 is not served by a number portability function.
  • the query sending module 445 is for sending the second query to the subscriber database for the second network domain 16 of the subscription PLMN.
  • the location requesting module 450 is for requesting the location of the subscriber 24 from the serving node 28B in the second network domain 16.
  • the gateway node 400 may comprise a computer readable storage medium 455, such as a memory.
  • the computer readable storage medium 455 may comprise, such as contain or store, a computer program 460.
  • the processing module 405 comprises, e.g. 'is embodied in the form of or 'realized by', a processing circuit 465 as an exemplifying hardware module.
  • the computer readable storage medium 455 may comprise the computer program 460, comprising computer readable code units executable by the processing circuit 465, whereby the gateway node 400 is operative to perform the methods of e.g. Figure 2 and/or 3.
  • Figure 8 further illustrates a carrier 470, that may comprise the computer program 460 described directly above.
  • the carrier 470 may be one of an electronic signal, an optical signal, a radio signal, and a computer readable storage medium (e.g., computer readable storage medium 455).
  • the gateway node 12 comprises respective circuits or circuitry configured to perform the steps shown in Figures 2, 3, or 7.
  • the circuits or circuitry in this regard may comprise circuits dedicated to performing certain functional processing and/or one or more microprocessors in conjunction with memory.
  • FIG. 9 in this regard illustrates some embodiments where the gateway node 12 is embodied in the form of a gateway node 500 that comprises one or more processing circuits
  • the processing circuit(s) 502 are operatively connected to a memory circuit 504 and a communication interface 506.
  • the memory circuit 504 stores program instruction and data used by the one or more processing circuits 502 to perform its functions.
  • the gateway node 12 may be a GMLC, for example.
  • the one or more processing circuits 502 may include, for example, one or more microprocessors, microcontrollers, digital signal processors, ASICs, or the like, configured with appropriate software and/or firmware to carry out one or more of the techniques discussed above.
  • the memory circuit 504 may comprise one or several types of memory such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc.
  • the memory circuit 504 may include program instructions for obtaining the location of a subscriber according to one or more of the techniques described herein.
  • the one or more processing circuits 502 are configured to receive a request for a location of a subscriber 24.
  • the one or more processing circuits 502 are further configured to, responsive to the request, generate a first query requesting routing information that identifies a PLMN to which the subscriber 24 is subscribed, and to send the first query towards a number portability function 22 serving the first network domain 14.
  • a number portability function 22 routes queries, on an individual number by number basis, to subscriber databases owned by PLMNs to which subscriber identifier numbers have been respectively ported, i.e., at least when those numbers have in fact been ported.
  • the one or more processing circuits 502 are further configured to generate a second query to a subscriber database for the second network domain 16 of the identified PLMN, by addressing the query using the routing information.
  • the second query requests address information identifying an address of a serving node 28B that is serving the subscriber 24 in the second network domain 16 and that has information on the location of the subscriber 24.
  • the second network domain 16 is not served by a number portability function.
  • the one or more processing circuits 502 are further configured to send the second query to the subscriber database for the second network domain 16 of the identified PLMN, and to request the location of the subscriber 24 from the serving node 28B using the address information.

Landscapes

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

Abstract

Un nœud de passerelle (12) dessert une pluralité de PLMN qui comprennent chacun un premier domaine de réseau (14) et un second domaine de réseau (16). Le nœud de passerelle (12) reçoit une demande concernant la position de l'abonné. Le nœud de passerelle (12) génère une première requête sollicitant des informations concernant un nœud de desserte (28A) qui dessert l'abonné (24) dans le premier domaine (14), et envoie la première requête à une fonction de portabilité de numéro (22) qui dessert le premier domaine (14). Le nœud de passerelle (12) génère une seconde requête à destination d'une base de données d'abonné pour le second domaine (16) en traitant la seconde requête au moyen d'une réponse à la première requête. La seconde requête sollicite des informations concernant un nœud de desserte (28B) qui dessert l'abonné (24) dans le second domaine (16). Le second domaine (16) n'est pas desservi par une fonction de portabilité de numéro. Le nœud de passerelle (12) envoie la seconde requête à la base de données d'abonné pour le second domaine (16), et demande la position de l'abonné à partir du nœud de desserte (28B) dans le second domaine (16).
PCT/SE2016/050152 2015-02-27 2016-02-26 Procédés et nœuds de passerelle pour desservir une pluralité de plmn WO2016137387A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201562126006P 2015-02-27 2015-02-27
US62/126,006 2015-02-27

Publications (1)

Publication Number Publication Date
WO2016137387A1 true WO2016137387A1 (fr) 2016-09-01

Family

ID=56788982

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/SE2016/050152 WO2016137387A1 (fr) 2015-02-27 2016-02-26 Procédés et nœuds de passerelle pour desservir une pluralité de plmn

Country Status (1)

Country Link
WO (1) WO2016137387A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1997036450A1 (fr) * 1996-03-26 1997-10-02 Ericsson Inc. Acheminement d'un signal de donnees vers une station mobile transportee appartenant a un reseau de telecommunications
WO2000054484A1 (fr) * 1999-03-05 2000-09-14 Telefonaktiebolaget Lm Ericsson (Publ) Systeme et procede d'amelioration du routage dans un reseau a portabilite de numero locale
WO2005125251A1 (fr) * 2004-06-18 2005-12-29 Ralph Eric Kunz Procede d'obtention d'informations accessibles sur plusieurs reseaux pour un systeme de communication mobile
CN101656930A (zh) * 2008-08-20 2010-02-24 华为技术有限公司 一种号码携带业务的实现方法、装置和系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1997036450A1 (fr) * 1996-03-26 1997-10-02 Ericsson Inc. Acheminement d'un signal de donnees vers une station mobile transportee appartenant a un reseau de telecommunications
WO2000054484A1 (fr) * 1999-03-05 2000-09-14 Telefonaktiebolaget Lm Ericsson (Publ) Systeme et procede d'amelioration du routage dans un reseau a portabilite de numero locale
WO2005125251A1 (fr) * 2004-06-18 2005-12-29 Ralph Eric Kunz Procede d'obtention d'informations accessibles sur plusieurs reseaux pour un systeme de communication mobile
CN101656930A (zh) * 2008-08-20 2010-02-24 华为技术有限公司 一种号码携带业务的实现方法、装置和系统

Similar Documents

Publication Publication Date Title
EP2681940B1 (fr) Procédés, systèmes et support lisible par ordinateur pour enrichir un message de signalisation diameter
US8626157B2 (en) Methods, systems, and computer readable media for dynamic subscriber profile adaptation
US11218519B2 (en) Service based P-CSCF discovery
US20080233931A1 (en) Location Service Method and System
US9021014B2 (en) Methods, systems, and computer readable media for providing home subscriber server (HSS) proxy
US9451594B2 (en) Method and apparatus for associating service provider network identifiers with access network identifiers
US20140086144A1 (en) Automatic Transfer of Machine-to-Machine Device Identifier to Network-External Service Providers
JP7398466B2 (ja) ＳＣＥＦ（Ｓｅｒｖｉｃｅ Ｃａｐａｂｉｌｉｔｙ Ｅｘｐｏｓｕｒｅ Ｆｕｎｃｔｉｏｎ）またはＮＥＦ（Ｎｅｔｗｏｒｋ Ｅｘｐｏｓｕｒｅ Ｆｕｎｃｔｉｏｎ）におけるＰＬＭＮ（Ｐｕｂｌｉｃ Ｌａｎｄ Ｍｏｂｉｌｅ Ｎｅｔｗｏｒｋ）ロケーションマッピングを動的にプロビジョニングおよび使用するための方法、システム、およびコンピュータ可読媒体
EP3871397A1 (fr) Procédé et noeuds de découverte de services dans un réseau de télécommunication mis en oeuvre par une fonction de réseau (nf) d'un réseau de télécommunication basé sur une architecture de services (sba)
EP3152934B1 (fr) Fourniture de profile d'abonné au mme en cas d'itinérance
US7583646B2 (en) Method and apparatus for facilitating interaction between a home subscriber server (HSS) and a home location register (HLR) in a legacy network
US20140086143A1 (en) Selection of M2M Devices by External Triggering
US9713071B2 (en) Provisioning external identifiers
US9313759B2 (en) Methods, systems, and computer readable media for providing triggerless equipment identity register (EIR) service in a diameter network
EP1846832A2 (fr) Procedes, systemes et programmes informatiques de regroupement et de communication entre des entites de sous-systemes multimedia (ims ) de protocole internet
US8452325B2 (en) Methods, systems, and computer readable media for providing scalable number portability (NP) home location register (HLR)
TW201225599A (en) A method and device for initiating one-to-many communication process by a network in a communication system
CN103067857A (zh) 一种通过用户承载标识获取用户位置的系统和方法
EP2362690B1 (fr) Procédé, système et dispositif pour établire la relation de commande de l'association
CN103079266B (zh) 一种获取用户位置信息的方法、装置及系统
US8855654B2 (en) Methods, systems, and computer readable media for tracking and communicating long term evolution (LTE) handset communication capability
JP2007531387A (ja) ハードウェア部分をアドレス指定することにより移動機へメッセージを送信するための方法及び装置
US20130124710A1 (en) Mediation server, control method therefor, communication device, control method therefor, account provisioning server, and control method therefor
WO2016137387A1 (fr) Procédés et nœuds de passerelle pour desservir une pluralité de plmn
US9191819B2 (en) Security method for the verification of an information retrieval request

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 16755984

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16755984

Country of ref document: EP

Kind code of ref document: A1