Method and apparatus for establishing and modifying traffic path on basis of service data flow in mobile communication system
US-2024406834-A1 · Dec 5, 2024 · US
US9344949B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-9344949-B2 |
| Application number | US-201313831170-A |
| Country | US |
| Kind code | B2 |
| Filing date | Mar 14, 2013 |
| Priority date | Mar 14, 2013 |
| Publication date | May 17, 2016 |
| Grant date | May 17, 2016 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
A system and method to allow call traffic localization within a mobile switching center server pool (MSS pool) or between MSS pools, provides a trunk group identifier mapped to an originating media gateway. An originating mobile switching center server (MSC server) initiates a call session with a terminating MSC server by sending a session initiation protocol (SIP) message that includes a trunk group identifier mapped to an originating media gateway identity. The terminating MSC server examines the mapping received in the SIP message, and uses the trunk group identifier to select a terminating media gateway for call routing to realize call traffic localization.
Opening claim text (preview).
I claim: 1. A method for selecting a terminating media gateway from multiple media gateways in a first mobile switching center server (MSS) pool, the method comprising: receiving, by a terminating control node that is located within the first MSS pool, an invitation to initiate a session initiation protocol (SIP) session that includes an originating media gateway trunk group identifier and a trunk context, wherein the invitation is a SIP INVITE message that is transmitted by an originating control node in response to a signal from the originating media gateway, and wherein the trunk context includes a domain name or a sub-domain name that is associated with the first MSS pool; obtaining, by the terminating control node, a geographic location of each media gateway of the multiple media gateways, wherein each geographic location corresponds to a physical locality in which the corresponding media gateway resides; selecting, by the terminating control node, a target media gateway from the multiple media gateways using the originating media gateway trunk group identifier and/or the trunk context to localize user plane traffic, wherein the selected target media gateway is one of the multiple media gateways that is geographically nearest to an originating media gateway, and wherein the selected target media gateway is the originating media gateway, such that the user plane traffic is localized within the originating media gateway; and, routing the user plane traffic from the originating media gateway via the target media gateway. 2. The method of claim 1 , wherein the originating media gateway trunk group identifier includes a trunk group identifier that is mapped to an identifier corresponding to the originating media gateway. 3. The method of claim 1 , wherein the user plane traffic is routed using Real-time Transport Protocol (RTP). 4. The method of claim 1 , wherein the originating and the terminating control nodes are both media gateway controller functions (MGCF). 5. The method of claim 4 , wherein the originating and the terminating control nodes are members of the first MSS pool. 6. The method of claim 4 , wherein the originating control node and the originating media gateway are associated with a second MSS pool different from the first MSS pool associated with the terminating control node and the terminating media gateway. 7. The method of claim 1 , wherein the SIP session is a two-party call or a multi-party conference call and the user plane traffic is routed over real-time transport protocol (RTP). 8. A system for optimizing routing of a call in a mobile switch center (MSC) pool, comprising: a terminating mobile switching center (MSC) server that is located within the MSC pool, wherein the MSC server has at least one processor and wherein the MSC server is configured to: receive a session in protocol (SIP) message to initiate a SIP session, wherein the SIP message includes an originating media gateway trunk group identifier, wherein the SIP message further includes a trunk context that includes a domain or sub-domain name associated with the MSC pool, and wherein the SIP message is a SIP INVITE message that is transmitted by an originating MSC server in response to a signal from the originating media gateway; obtain a geographic location of each of multiple media gateways, wherein each geographic location corresponds to a physical locality in which the corresponding media gateway resides; select a target media gateway from the multiple media gateways to localize user plane traffic, wherein the selected target media gateway is one of the multiple media gateways that is geographically nearest to an originating media gateway, wherein the selected target media gateway is mapped to the originating media gateway trunk group identifier and/or the trunk context, and wherein the selected target media gateway is the originating media gateway, such that the user plane traffic is localized to the originating media gateway; and route the user plane traffic via the target media gateway. 9. The system of claim 8 , wherein the originating media gateway trunk group identifier includes a trunk group identifier that is mapped to an identifier corresponding to the originating media gateway. 10. The system of claim 9 , wherein the originating and the terminating MSC servers are both media gateway controller functions (MGCF). 11. The system of claim 10 , wherein the originating and the terminating MSC servers are members of a first MSS pool. 12. The system of claim 10 , wherein the originating MSC server and the originating media gateway are associated with a second MSS pool different from a first MSS pool associated with the terminating MSC server and the target media gateway. 13. The system of claim 8 , wherein the SIP session is a two-party call or a multi-party conference call and the user plane traffic is routed over real-time transport protocol (RTP). 14. At least one non-transitory computer-readable medium carrying instructions that when executed by at least one data processing device performs the steps of: receiving, by a terminating control node that is located within a first MSS pool, an invitation to initiate a session initiation protocol (SIP) session that includes an originating media gateway trunk group identifier and a trunk context, the trunk context comprising a domain name or a sub-domain name that is associated with the first MSS pool, the invitation being a SIP INVITE message that is transmitted by an originating control node in response to a signal from the originating media gateway, and; obtaining, by the terminating control node, a geographic location of each of multiple media gateways, wherein each geographic location corresponds to a physical locality in which the corresponding media gateway resides; selecting, by the terminating control node, a target media gateway from the multiple media gateways using the originating media gateway trunk group identifier and/or the trunk context to localize user plane traffic, wherein the selected target media gateway is one of the multiple media gateways that is geographically nearest to an originating media gateway, and wherein the selected target media gateway is the originating media gateway, such that the user plane traffic is localized within the originating media gateway; and, routing the user plane traffic from the originating media gateway via the target media gateway. 15. The non-transitory computer-readable medium of claim 14 , wherein the SIP session is a two-party call or a multi-party conference call and the user plane traffic is routed over real-time transport protocol (RTP).
Selecting a data network PoA [Point of Attachment] · CPC title
in the network · CPC title
minimising geographical or physical path length · CPC title
Communication route or path selection, e.g. power-based or shortest path routing · CPC title
Session establishment or de-establishment · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.