WO2008150264A1 - Agent de signalisation transparent - Google Patents

Agent de signalisation transparent Download PDF

Info

Publication number
WO2008150264A1
WO2008150264A1 PCT/US2007/013555 US2007013555W WO2008150264A1 WO 2008150264 A1 WO2008150264 A1 WO 2008150264A1 US 2007013555 W US2007013555 W US 2007013555W WO 2008150264 A1 WO2008150264 A1 WO 2008150264A1
Authority
WO
WIPO (PCT)
Prior art keywords
bearer
signal
flows
control plane
media processing
Prior art date
Application number
PCT/US2007/013555
Other languages
English (en)
Inventor
Jeff Hawbaker
Robert J. Laidlaw
Jonathan B. Sadler
Dale Scholtens
Original Assignee
Tellabs Operations, Inc.
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 Tellabs Operations, Inc. filed Critical Tellabs Operations, Inc.
Priority to PCT/US2007/013555 priority Critical patent/WO2008150264A1/fr
Priority to US12/012,208 priority patent/US20090003231A1/en
Publication of WO2008150264A1 publication Critical patent/WO2008150264A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/80—Responding to QoS
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/102—Gateways
    • H04L65/1023—Media gateways
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1101—Session protocols
    • H04L65/1104—Session initiation protocol [SIP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/60—Network streaming of media packets
    • H04L65/75—Media network packet handling
    • H04L65/765—Media network packet handling intermediate
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/22—Parsing or analysis of headers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/18—Information format or content conversion, e.g. adaptation by the network of the transmitted or received information for the purpose of wireless delivery to users or terminals

Definitions

  • an end-to-end connection bearing various media services may be transmitted in the data plane (i.e. the packet-based or circuit-based network used to transport service-bearing traffic between nodes) by one or more bearer flows, also referred to herein as composite bearer flows, each of which is composed of a packet stream.
  • bearer flows also referred to herein as composite bearer flows, each of which is composed of a packet stream.
  • Collectively, these bearer flows define this end-to-end connection.
  • packet switching elements located along a connection path utilize standard packet switching protocols within the data plane to interconnect these composite bearer flows.
  • an end-to-end connection along with its composite bearer flows are established in accordance with standard signaling protocols (e.g., Session Initiation Protocol (SIP)) conveyed across the control plane (i.e., the packet-based signaling network used to set up, maintain, and terminate data plane connections) between the connection endpoints.
  • SIP Session Initiation Protocol
  • a connection controller typically acts as an intermediate signaling agent in directing the establishment of the data plane resident bearer flows supporting the requested connection.
  • connection set up message e.g., a SIP INVITE message
  • connection attributes typically include the originating node's selection of various call parameters along with its selection of the originating node's address parameters to be utilized by subsequent bearer flows.
  • This connection set up message is propagated through one or more intermediary signaling agents via the control plane's underlying packet switching network (again using standard packet switching protocols), and ultimately to the addressed destination node.
  • the destination node may signal its response to the originating node to the connection set up message indicating its preferred selection of various call parameters inclusive of the destination node's selection of address parameters to be utilized by data plane resident bearer flows to be subsequently sent to it.
  • the originating and terminating nodes along with intervening signaling agents communicate within the context of the control plane to not only negotiate various call parameters but to establish the composite bearer flows that will subsequently transport the end-to-end connection's media within the data plane.
  • VQE Voice Quality Enhancement
  • a method or corresponding apparatus in an example embodiment of the invention transparently monitors signaling messages traversing the control plane for the establishment of prospective data plane resident connections bearing media types which are to be targeted for intermediate media processing between the connection end nodes.
  • the method or corresponding apparatus utilizes Policy Based Routing to direct signaling messages from a routing point within the control plane to a signaling monitoring point, also within the control plane.
  • This signaling monitoring point acts as an intermediate signaling agent which first identifies the connection setup signaling pursuant to the establishment of data plane connections with the media types targeted for media processing. Once so identified, this signaling agent will substitute for the bearer flow address information contained in the signaling messages with bearer flow address information of media processing points in the data plane network such that subsequent bearer flows will be directed to the selected media processing points.
  • the modified signaling message will be presented by the signaling agent back to the control plane's packet switching network at which point the modified signaling message will be forwarded to its original destination by destination based routing capabilities inherent to the control plane network.
  • Fig. l is a network diagram of a network in which example embodiments of the invention may be employed.
  • Fig. 2 A is a flow diagram of example operations occurring in an network to transparently monitor targeted signal flows.
  • Fig. 2B is a signal diagram illustrating an example signal flow occurring at a router and monitoring point.
  • Fig. 3 A is a packet diagram illustrating example Session Initiation Protocol (SIP) packets sent between a source mobile switching center (MSC) and a destination MSC.
  • SIP Session Initiation Protocol
  • Fig. 3B is a packet diagram illustrating a bearer channel packet sent between a source MSC and a destination MSC.
  • Fig. 4 is a network diagram illustrating the session initiation protocol dialog flows and the bearer channel flows through a multilayer switching device.
  • Fig. 5 is a network diagram of a system for transparently monitoring targeted signal flows according to an example embodiment of the invention
  • Fig. 6 is a network diagram illustrating a network including a system in which an example embodiment of the invention may be deployed in an inter-Mobile Telephone Switching Office (inter-MTSO) data path.
  • Fig. 7 is a network diagram of an inter-MTSO Session Initiation Protocol (SIP) packet flow in accordance with an example embodiment of the invention.
  • SIP Session Initiation Protocol
  • Fig. 8 is a network diagram of an inter-MTSO bearer plane packet flow in accordance with an example embodiment of the invention.
  • Fig. 9 is a network diagram illustrating a network including a system in which an example embodiment of the invention may be deployed in an intra-Mobile Telephone Switching Office (intra-MTSO) data path.
  • intra-MTSO intra-Mobile Telephone Switching Office
  • Fig. 10 is a network diagram of an intra-MTSO Session Initiation Protocol (SIP) packet flow in accordance with an example embodiment of the invention.
  • Fig. 11 is a network diagram of an intra-MTSO bearer plane packet flow in accordance with an example embodiment of the invention.
  • SIP Session Initiation Protocol
  • control plane signaling is intercepted and transparently monitored using policy based routing to direct connection control signals from a routing point in the control plane to a monitoring point also residing in the control plane.
  • connection control protocol e.g., SIP
  • fields contained in the headers of protocols e.g., at layers 2, 3, & 4
  • the subject connection control protocol e.g., SIP
  • the signaling monitoring point While at the signaling monitoring point, addressing parameters of a selected media processing point residing in the data plane is substituted for the data plane addressing parameters originally contained in the connection setup signal. This will cause subsequent bearer flows to be directed to the selected media processing point from a routing point within the data plane by destination based routing once the connection is established.
  • the signaling monitoring point will also notify the selected media processing point of the original data plane address parameters that were substituted for. This is so that the media processing point, once it has processed the media contained in a redirected bearer flow, may forward the enhanced media in bearer flow to its original destination as specified in the original signaling message. Once the signaling monitoring point is through with the connection control signal, the signal (containing its pertinent bearer flow addressing substitutions) will be forwarded to it original destination.
  • bearer flows may be directed (as described above) to a media processing point to process encoded media on the bearer flows to monitor metrics associated with the media and / or bearer flows.
  • bearer flows may be directed to a media processing point (again as described above) to apply media enhancement
  • the bearer flows may be selectively directed to a media processing point depending on the identity of either the sending or receiving party, their service subscriptions, or specific media types.
  • the invention may be used either within or outside of a single Mobile Telephone Switching Office (MTSO) in Local Access, Backhaul, or Wide Area networking applications.
  • MTSO Mobile Telephone Switching Office
  • FIG. 1 illustrates a communications network 100 in which example embodiments of the invention may be employed.
  • end-to-end connections may originate from, or terminate at devices, such as computer terminals 166 or host server 167 (e.g. a video server), connected to the IP WAN 165.
  • Originating or destination devices may also include calling devices, such as mobile devices 121a and 121b, or telephones 176 connected to the public switch telephone network 175.
  • base transceiver stations 110a and 110b provide network access to mobile devices 121a and 121b. ).
  • base transceiver sites are typically connected to a Mobile Telephone Switching Office 101 (MTSO) through a TDM backhaul network 115 consisting of copper facilities, optical fiber, or microwave.
  • Copper facilities deliver either T-carrier 1 (Tl), sometimes referred to as Digital Signal 1 (DSl), or E-carrier 1 (El), while microwave and optical fiber can offer T3s or Ethernet in addition to Tl or El.
  • base transceiver stations 110b may connect to the MTSO 101 through an Ethernet backhaul 185.
  • Tl T-carrier 1
  • DSl Digital Signal 1
  • El E-carrier 1
  • base transceiver stations 110b may connect to the MTSO 101 through an Ethernet backhaul 185.
  • transport technologies or other intermediate network elements may be used to connect base transceiver stations 110a, 110b with the MTSO 101.
  • the MTSO 101 may include a number of typical networking elements, including cross connect switches 120, aggregation routers 130, and Ethernet switches 140 by which traffic transmitted across multiple backhaul networks 115 and 185 is aggregated towards or distributed from a mobile switching center 150 (MSC). Connections from a mobile device served by the local MTSO can be made through the MSC 150 to another mobile device served by the same MTSO 101, to a mobile device served by another MSC in another MTSO 170, or to a landline through the public switched telephone network 175 (PSTN).
  • PSTN public switched telephone network 175
  • the MSC 150 may provide a number of services, including mobility management for subscribers (e.g., registration, authentication, authorization for services), media conversion (TDM to packet gateway, media transcoding), and signaling (signaling gateway, signaling transport, connection control).
  • Connection control services determine how connections are set-up and and supporting bearer flows routed to carry the media traffic within the same MTSO 101, to another MTSO 170, or to the PSTN 175. As shown, the PSTN may connect with any number of different MTSOs 170.
  • Bearer flow 102 illustrates a connection between mobile devices on base transceivers 110 served by the same MTSO 101 , also referred to as an intra-MTSO signal flow.
  • the bearer flow is sent through the base transceiver 110 through the Tl backhaul 115 to a cross connect 120 in the MTSO 101.
  • the bearer flow is directed by a router 130 to an Ethernet switch 140 to the MSC 150.
  • the MSC 150 sends the connection to a multilayer switching (MLS) device 160.
  • MLS multilayer switching
  • the Intra-MTSO bearer flow is routed back to the MSC 150 from which the bearer flow traverses the reverse direction across the Ethernet switch 140, router 130, cross connect 120, across the Tl backhaul 115 and on to the destination base transceiver 110 corresponding to the destination mobile device (not shown in Fig. 1).
  • Bearer flow 104 illustrates a connection between mobile devices on base transceivers served by the different Mobile Telephone Switching Offices, MTSO 101 and MTSO 170, also referred to as an inter-MTSO connection.
  • the bearer flow is similar to the intra-MTSO flow up until the signal reaches the MLS 160.
  • the bearer flow is routed through an external network, such as IP WAN 165, to an MSC (not shown) in another MTSO 170 on which the destination mobile device (not shown) is associated.
  • IP WAN 165 an external network
  • MSC Mobility Service provider may be motivated to offer differentiating services requiring additional processing on various media types (e.g., voice, video).
  • intermediate network elements may be introduced to (1) monitor connection control signaling operating in the control plane for the establishment of connections bearing targeted media types and (2) to direct the bearer flows transporting these targeted connections to media processing points in the network where differentiated services can be applied.
  • Figs. 2A and 2B illustrate example network operation flows whereby (1) signaling messages in the control planes are transparently monitored to identify the setup of connections as candidates for the application of media enhancement services and (20 the redirection of targeted bearer flows in the data plane of said candidate connections to a media processing point where media enhancement services can be applied.
  • Fig. 2A illustrates the operations flow in a call set-up to re-direct bearer flows underlying targeted candidate connections whereby:
  • a control plane signal (e.g. SIP signal) is sent (210) through the network to establish a new end-to end connection.
  • the control plane signals are intercepted and directed (220) to a signaling monitoring point according to policies associated with the control plane signals.
  • data plane addressing parameters of a selected media processing point are substituted for the data plane addressing parameters of the connection destination contained in the connection set up signal. This will cause subsequent bearer flows to be directed (240)to the selected media processing point from a routing point within the data plane by destination based routing once the connection is established.
  • the signaling monitoring point will also notify (924)the selected media processing point of the original data plane address parameters of the connection destination that were substituted for. This is so that the media processing point, once it has processed the media contained in a redirected bearer flow, may forward the enhanced media in bearer flow to its original connection destination as specified in the original signaling message. Once the signaling monitoring point is through with the connection control signal, the signal (containing its pertinent bearer flow addressing substitutions) will be forwarded (926) to it original destination.
  • associated bearer flows will be routed (930) directly to the selected media processing point at which point media enhancement services will be applied to the encoded media. Subsequently, the enhanced encoded media will be re-packetized into associated bearer flows for transmission to the connection destination whose data plane addressing parameters have previously been stored bye the media processing point (per 924).
  • Fig. 2B further illustrates an example signal flow between a router 260 and a monitoring point 270 in accordance with example embodiments of the invention.
  • a control plane signal 281 (e.g. SIP signal) is sent through the network to establish bearer plane channel flow, and arrives at the router 260.
  • the router 260 forwards the control plane signal 282 using policy based routing to the monitoring point 270.
  • address information of the monitoring point is substituted for control plane address information in the control plane signal.
  • the monitoring point 270 For SDP-laden SIP Request (i.e., INVITE) messages, the monitoring point 270 locally stores and replaces the call source's IP Address and User Datagram Protocol (UDP) Port Number contained in the Session Descriptor with the monitoring point's 270 IP Address UDP Port Number. The monitoring point then outputs the modified control plane signal 283 to the router 260, which forward the signal 284 its intended recipient (not shown in Fig. 2B).
  • UDP User Datagram Protocol
  • the recipient will provide an acknowledgement 285 of the call set-up request.
  • the acknowledgment 285 is received at the router 260, and the router 260 forwards the signal 286 to the monitoring point 270.
  • the monitoring point 270 first verifies that the negotiated media-subtype indicates a target session. If so, IP Address and UDP Port Number swapping similar to the INVITE message is performed for the call destination.
  • the monitoring point then outputs the modified control plane signal 287 to the router 260, which forward the signal 288 to the originating caller (not shown in Fig. 2B). After call set-up has been established, incoming signals 289 on the bearer channel arrive at the router 260.
  • Fig. 3A is a high level packet diagram illustrating example Session Initiation
  • SIP Session Initiation Protocol
  • the source device 360 sends a SlP packet 365 through a network flow 362.
  • the signal packet has layer 2 header information 365A, layer 3 internet protocol (IP) header information 365B, and layer 4 User Datagram Protocol UDP header information 365C. Included in these headers are source and destination information.
  • the application layer includes both a SIP header 365D, and the SIP payload 365E containing session description protocol (SDP) information.
  • SDP session description protocol
  • the payload provides the "return address" IP address and port number to which a destination should respond.
  • a router may apply policy based routing to layers 2 through 4 (or a subset thereof) to the packet 365.
  • the monitoring point 370 processes the incoming packet 365 and sends out a modified SIP packet 375.
  • the monitoring point locally stores the session descriptor information and replaces the source's IP Address and User Datagram Protocol (UDP) Port Number contained in the session descriptor of the payload with the monitoring point's 370 address.
  • UDP User Datagram Protocol
  • the SIP payload 375 of sent from the monitoring point 370 through a network flow 372 will provide the destination 380 with the monitoring point's 370 IP Address and UDP port number for a response.
  • the layer 2 header 375A, layer 3 IP header 375B, layer 4 UDP header 375C, and SIP header 375D all remain unmodified.
  • the packet may be routed to the destination 380 using destination based routing in the event the monitoring point 370 should fail or if it should have a fault, such as congestion fault.
  • the destination 380 receives and processes the modified SIP packet 375, and subsequently sends a response SIP packet 385 to acknowledge the SIP invitation and set-up the connection.
  • the response SIP packet 385 includes a layer 2 header 385A, a layer 3 IP header 385B, a Layer 4 UDP header 385C, and a SIP header 385D.
  • the SIP payload 385E includes session descriptor information as well.
  • the monitoring point will similarly process the packet 385 to determine and modify the "return address" in the SIP payload 385E.
  • Fig. 3B is a packet diagram illustrating a bearer channel packet sent between a source device and a destination.
  • bearer channel packets 395 are sent between a source and destination.
  • the bearer channel packet 395 includes a layer 2 header 395A, a layer 3 IP header 395B, a layer 4 UDP header 395C, and a Real-time Transport Protocol payload 395D.
  • Fig. 4 is a network diagram illustrating session initiation protocol dialog flows and the bearer channel flows through a multilayer switching device (MLS) 470 according to an example embodiment of the invention.
  • Source device 460 transmits a SIP packet 462 along a SIP dialog flow 465.
  • a policy based routing module 470a routes the SIP packet 462 up to a session manager 490 of a monitoring device (not shown).
  • the session manager 490a modifies the SIP descriptor information as discussed above with respect to the monitoring point of Fig. 3 A and sends the modified packet 472 along the SIP dialog flow through the MLS to be routed to the destination device 480.
  • the destination device 480 likewise sends a SIP packet 482 through the MLS 470 to the session manager 490a.
  • the session manager will process the packet 482 accordingly, and pass it through the MLS 470 to back to the source device 460.
  • the source 460 sends data packets 464 to the destination device 480 along bearer channel flows 475 through the MLS 470.
  • a destination based routing module 470b routes the data packet 464 to a media processing server 490b in the monitoring point.
  • the information about the data packet 464 may be extracted, or the packet 1 164 may be altered prior to sending a modified data packet 474 to the destination device 480.
  • the destination device 480 may likewise send data packets through the bearer channel flow 475.
  • the destination device 480 transmits a data packet 486 along the bearer channel flow 475.
  • the destination based routing module 470b routes the data packet 486 to a media processing server 490b.
  • the media processing server module 490b of the monitoring point passes the modified data packet 488 along to the source device 460.
  • Figs. 5 through 1 1 illustrate example embodiments of the invention involving mobile communications. In will be understood to one skilled in the art that principles and example embodiments of the invention may be applied to various communications network connections.
  • VQE Voice Quality Enhancement
  • PCM Pulse Code Modulation
  • A-law and ⁇ -law are also forms of compression (i.e., encoding), but they fall into a category of waveform encoders.
  • VQE in a coded domain is source-model encoding, which is a basis of most low bit rate, speech coding.
  • VQE voice quality enhancement
  • FIG. 5 through 1 1 illustrates a single media server 595 that includes both a media processing point 591 and a signaling monitoring point 590, it will be understood by one of skill in the art that the media processing point 591 and a signaling monitoring point 590 may be located in separate housings and connected via a network connection.
  • Fig. 5 illustrates an example system 500 that provides both a Signaling Monitoring Point 590 and a Media Processing Point 591 in association with connections between mobile devices served by the MTSO's 101, 170 of Fig. 1.
  • an MSC 550 sends and receives packets 516, 521 to and from an MLS device 560 that routes both signaling messages 516 in the control plane and bearer flows 521 in the data plane between the MSC 550 and IP WAN 565.
  • the MLS device 560 may be configured as a redundant pair of MLS devices.
  • the MLS device 560 may also route packets 516, 521 to and from a signaling monitoring point 590 as well as a media processing point 591 both of which in an embodiment of the present invention may be contained within the same element, the Media Server 595.
  • Policy Based Routing (PBR) functions on the MLS's 560 can be configured to cause signaling messages 516 to be intercepted from passing directly between the MSC 550 and IP WAN 565 via the MLS's 560 and instead to be intercepted 515 to the Signaling Monitoring Point 590 residing on the Media Server 595.
  • Signaling messages 515 arriving at the Signaling Monitoring Point 590 will be scanned for connections being established whose bearer flows carry media types to be targeted for subsequent media processing.
  • the subsequent bearer flows 521 which would normally traverse within the data plane directly between the MSC 550 and IP WAN 565 via the MLS's 560, will instead be directly routed 520 to the Media Processing Point 591 residing on the Media Server 595 via standard Destination Based Routing inherent to the MLS's 560.
  • the bearer processing point 591 offers the opportunity to apply differentiating services to enhance the media contained in the bearer flows 520.
  • the bearer processing point 591 may perform Coded Domain- Voice Quality Enhancement (CD-VQE) services on the encoded media carried with the bearer flows 520 to produce an enhanced media.
  • CD-VQE Coded Domain- Voice Quality Enhancement
  • Fig. 6 is a network diagram illustrating a network 600 including a MTSO network 601 in which an example embodiment of the invention may be deployed in an inter-MTSO communications path.
  • the flow 604 that begins at the base transceiver station 610 travels through a Tl backhaul 615 to a cross connect 620 in the MTSO 601.
  • the signal flow606 is directed by a router 630 to an Ethernet switch 640 to the MSC 650.
  • Signaling traffic directed from or towards the MSC 650 are routed to/from the monitoring point 690 using policy based routing functions on the MLS device 660.
  • policy based routing at the MLS device 660, the MLS device 660 avoids the need for destination based routing through the monitoring point (or "monitoring device") 690.
  • policies may be employed by the MLS device(s) 660 to act autonomously on the SIP traffic to integrate the monitoring point 690 into a flow path of later bearer flows (or "bearer channel flows") being set-up by the SIP traffic.
  • the use of policies thus allows services to be applied to bearer flows between two nodes communicating with each other (e.g.
  • the monitoring point 690 monitors SIP traffic for certain session set-ups, such as an Enhanced Variable Rate CODEC (EVRC) setup, in order to modify Session Description Protocols (SDP) to "draw" subsequent target Real-time Transport Protocol (RTP)/Real-time Transport Control Protocol (RTCP) traffic flows to itself.
  • SDP Session Description Protocol
  • RTP Real-time Transport Protocol
  • RTCP Real-time Transport Control Protocol
  • Subsequent targeted RTP packet flows are directly routed to the monitoring point 690 where they are processed and then sent via the MLS 660 from which the monitoring point 690 received the RTP packet flows, to their original destination as specified during SIP session set-up proceedings.
  • any failure of the monitoring point 690 should not affect the reliability of the endpoint-to-endpoint signal transmission.
  • the MLS device 660 may simply bypass the policy based routing to the failed monitoring point, and default to destination based routing of the signal flows to the destination device address.
  • the system may be configured to direct targeted signal flows (SIP flows, and subsequently bearer channel flows) selectively to the monitoring point 690 or to simply bypass the monitoring point 690 altogether, using policy based routing. This policy may depend on the originating subscriber, destination subscriber, or subscription features.
  • the signal 604 is processed by the monitoring point and is sent through the MLS 660, through an external network 665, to an MSC (not shown) in another MTSO 670 on which the destination mobile device (not shown) is associated.
  • calls initiated from a mobile device associated with the MTSO 670 may travel along signal flow 604 to a mobile device associated with a base transceiver station 610 through the MTSO 601.
  • Fig. 7 provides a more detailed illustration of a network 700 for transparently monitoring targeted signal flows within a MTSO, with particular focus on an inter- MTSO Session Initiation Protocol (SIP) packet flow in accordance with an example embodiment of the invention.
  • SIP Session Initiation Protocol
  • the calling device In order to initiate an end-to-end call, the calling device (not shown) typically transmits a Session Initiation Protocol (SIP) packet flow (i.e., a "call set-up" message) indicating the destination address to the network.
  • SIP Session Initiation Protocol
  • the call set-up message can be propagated through the network to a destination device (or "called" device) associated with the destination address using conventional routing techniques.
  • a request message path 712 illustrates a request message
  • SPP Signaling Plane Packet
  • SIP SlP message packet
  • An MLS device 760 forwards (761a) the SIP using policy based routing to a packet processor (e.g. a session manager) 792 of the monitoring point 790.
  • the SIP may arrive (762a) at the packet processor 792 over a Gigabit Ethernet (GbE) connection.
  • GbE Gigabit Ethernet
  • the packet processor 792 For Session Description Protocol (SDP) laden SIP Request (i.e., INVITE) messages, the packet processor 792 locally stores and replaces (763) the call source's IP Address and User Datagram Protocol (UDP) Port Number contained in the Session Descriptor with the monitoring point's 790 IP Address UDP Port Number. The node processing 792 unit then outputs (step 765a) the modified SIP message to its intended SIP User Agent recipient.
  • An MLS device 760 forwards SIP message to its intended SIP User Agent recipient.
  • a SIP status message path 714 illustrates the SIP flow back to the MSC 750 from a device (not shown) outside the network 700.
  • An MLS device 760 forwards (761b) the SIP using policy based routing to the packet processor 492 of the monitoring point 790.
  • the SIP status message arrives (762b) at the packet processor 792.
  • SDP-laden SIP Status i.e., SESSION PROGRESS
  • the packet processor 792 first verifies that the negotiated media-subtype indicates a target session. If so, IP Address and UDP Port Number swapping similar to the INVITE message is performed (764) for the call destination.
  • an UPDATE SIP request is issued to the call destination with the call source's original IP Address and UDP Port Number parameters restored.
  • the node processing 792 unit then outputs (765b) the modified SIP message to its intended SIP User Agent recipient.
  • An MLS device 760 forwards (766b) the Signaling Plane Packet (i.e., SIP ) to the MSC 750 using destination based routing.
  • SIP message bypass paths 716a, 716b illustrate the SIP flow when the monitoring point has failed.
  • the MLS device 760 forwards the Signaling Plane Packet (i.e., SIP) to its intended destination using destination based routing.
  • SIP Signaling Plane Packet
  • Fig. 8 provides a more detailed illustration of various inter-MTSO bearer plane packet flows through a network 800 in accordance with an example embodiment of the invention.
  • Processed target packet path 814 illustrates the bearer plane packet flow originating from the MSC 850 for connections in which packets are to be monitored or processed.
  • An MLS device 860 forwards (861a)target the bearer plane packet (i.e., monitoring point addressed RTP or RTCP packet ) to the monitoring point 890.
  • the bearer plane packet arrives (862a) at a packet processor 892 over a Gigabit Ethernet (GbE) connection.
  • GbE Gigabit Ethernet
  • the packet processor 892 de-packetizes (863) payload from target packets to be processed and passes the de-packetized payload to a media processor 896 for processing.
  • the packet processor 892 may pass other parameters in the internal packet as well.
  • the media processor 896 processes (864) payload passed to it by packet processor 892 and then returns processed payload to packet processor 892.
  • the media processor 896 in the monitoring point 890 may provide different features, such as monitoring the various metrics of the connection (e.g. length of connection, signal to noise ratio, data throughput) for the benefit of the service provider, or for providing signal enhancement, such as voice quality enhancement (VQE).
  • VQE voice quality enhancement
  • the particular features may be assigned based on the nature of the monitoring or processing required by the system. The monitoring or processing required may, among other factors, depend on the identify of the originating subscriber, the identify of the destination subscriber or selected VQE subscription features of either of the parties.
  • Echo cancellation represents an important network VQE function. While wireless networks do not suffer from electronic (or hybrid) echoes, they do suffer from acoustic echoes due to an acoustic coupling between the earpiece and microphone on an end user terminal. Therefore, acoustic echo suppression is useful in the network.
  • VQE functions include reduction of background noise, adaptive level control to adjust a level of the speech signal to a predetermined level that the network operator deems to be optimal for its subscribers, and adaptive gain control, which reduces listening effort on the part of a user and improves intelligibility by adjusting a level of the signal received by the user according to his or her background noise level.
  • Example VQE methods and devices that may be used in connection with the invention are disclosed in U.S. Patent Publication No. US-2006-0217972-A1, entitled “Method and Apparatus For Modifying An Encoded Signal," filed January 27, 2006 and incorporated herein by reference.
  • the packet processor 892 re-packetizes (865) (i.e., into RTP / UDP / IP) the processed payload handed back to packet processor 892 by media processor 896.
  • the packet processor 892 looks up (866a) destination's IP address and UDP port number previously stored during session set-up and outputs the packet on the appropriate GbE connection.
  • the MLS device 860 forwards (867a) addressed packets through the IP WAN 865.
  • the non-processed target data path 812 illustrates the packet flow of targeted packets that pass through, but are not monitored or processed by, the monitoring point. This may apply to a particular subscriber that has not yet opted to subscribe to enhanced features provided by the service provider. Further, targeted connections may be established in order to provide some flexibility in monitoring or providing additional processing mid-connection.
  • the non-processed target data path 812 begins much like the processed target datapath 814. An MLS device forwards
  • the bearer plane packet (i.e., monitoring point addressed RTP or RTCP packet ) to the monitoring point 890.
  • the bearer plane packet arrives (862b) at a packet processor 892. Instead of de-packeting payload and passing it to the media processor 896, the packet processor 892 looks up (866b) destination's IP address and UDP port number previously stored during session set-up and outputs the packet back on the appropriate GbE connection.
  • the MLS device 860 forwards (867b)addressed packets through the IP WAN 865.
  • the non-target packet data path 816 illustrates the packet flow of packets that have not been selected for transparent monitoring.
  • the MLS device 860 simply forwards addressed packets through the IP WAN 865
  • Fig. 9 is a network diagram illustrating a network 900 including a MTSO network 901 in which an example embodiment of the invention may be deployed in an intra-MTSO signal path.
  • the signal flow 906 travels via a path that begins at a base transceiver station 610 and travels through a Tl backhaul 915 to a cross connect 920 in the MTSO 901.
  • the signal flow 606 is directed by a router 930 to an Ethernet switch 940 to the MSC 950.
  • Signaling traffic e.g., SIP
  • SIP Session Initiation Protocol
  • the monitoring point 990 monitors SIP traffic for certain session set-ups, such as an Enhanced Variable Rate CODEC (EVRC) set- up, in order to modify Session Description Protocols (SDP) to "draw" subsequent target Real-time Transport Protocol (RTP)/Real-time Transport Control Protocol (RTCP) traffic flows to itself. Subsequent targeted RTP packet flows are directly routed to the monitoring point 990 where they are processed and then sent on to their original destination as specified during SIP session set-up proceedings.
  • EVRC Enhanced Variable Rate CODEC
  • the system may be configured to direct targeted signal flows (SIP flows, and subsequently bearer channel flows) selectively to the monitoring point 990 based on a subscriber policy, or simply bypass the monitoring point 990 altogether.
  • SIP flows targeted signal flows
  • the signal is processed by the monitoring point and is sent through the MLS 960 back to the originating MSC 950, back through the devices of the MTSO 901 to a destination mobile device (not shown) associated with a base transceiver stations 910 or 980 in communication with the MTSO 901.
  • a request message path 1012 illustrates a Signaling Plane Packet (SPP) (e.g, an SIP message packet ("SIP")) originating from the MSC 1050.
  • SPP Signaling Plane Packet
  • An MLS device 1060 forwards (1061a) the SIP using policy based routing to a packet processor 1092 of the monitoring point 1090.
  • the SIP may arrive (1062a) at the packet processor 1092 over a Gigabit Ethernet (GbE) connection.
  • GbE Gigabit Ethernet
  • the packet processor 1092 For SDP-laden SIP Request (i.e., INVITE) messages, the packet processor 1092 locally stores and replaces (1063) the call source's IP Address and User Datagram Protocol (UDP) Port Number contained in the Session Descriptor with the monitoring point's 1090 IP Address UDP Port Number. The node processing 1092 unit then outputs (1065a) the modified SIP message to its intended SIP User Agent recipient.
  • An MLS device 1060 forwards (1066a) the Signaling Plane Packet (i.e., SIP ) to its intended destination using destination based routing back to the MSC 1050.
  • a SIP status message path 1014 illustrates the SIP flow from a destination device (not shown) on the MSC 1050 sending a SIP status message back to the originating device on the same MSC 1050.
  • An MLS device 1060 forwards (1061a) the SIP using policy based routing to the packet processor 1092 of the monitoring point 1090.
  • the SIP status message arrives (1062b) at the packet processor 1092.
  • SDP-laden SIP Status i.e., SESSION PROGRESS
  • the packet processor 1092 first verifies that the negotiated media-subtype indicates a target session. If so, IP Address and UDP Port Number swapping similar to the INVITE message is performed (1064) for the call destination.
  • an UPDATE SIP request is issued to the call destination with the call source's original IP Address and UDP Port Number parameters restored.
  • the node processing 1092 unit then outputs (1065b) the modified SIP message to its intended SIP User Agent recipient.
  • An MLS device 1060 forwards (1066b) the Signaling Plane Packet (i.e., SIP) to the MSC 1050 using destination based routing.
  • a SIP message bypass path 1016 illustrates the SIP flow when the monitoring point has failed.
  • the MLS device 1060 forwards the Signaling Plane Packet (i.e., SIP) to its intended destination on the shared MSC 1050, using destination based routing.
  • SIP Signaling Plane Packet
  • FIG. 11 provides a detailed illustration of various intra-MTSO bearer plane packet flows through a network 1100 in accordance with an example embodiment of the invention.
  • Processed target packet path 1114 iil ⁇ stra ⁇ e_s the bearer plane packet flow originating from the MSC 1150 for connections til' which packets are to be monitored or processed.
  • An MLS device 1160 forwards (1161a) target the bearer plane packet (i.e., monitoring point addressed RTP or RTCP packet ) to the monitoring point 1190.
  • the bearer plane packet arrives (1162a) at a packet processor 1192 over a GbE connection.
  • the packet processor 1192 de-packetizes (1163) payload from target packets to be processed and passes the de-packetized payload to a media processor 1196 for processing.
  • the media processor 1196 may provide different services, such as monitoring the various metrics of the connection for the benefit of the service provider, or for providing signal enhancement, such as echo cancellation.
  • the monitoring or processing required may, among other factors, depend on the identify of originating subscriber, the identify of the destination subscriber or subscription features of the parties.
  • the media processor 1196 processes (1164) payload passed to it by packet processor 1 192 and then returns processed payload to packet processor 1192.
  • the packet processor 1192 re-packetizes (1165) (i.e., into RTP / UDP / IP) the processed payload handed back to packet processor 1192 by media processor 1 196.
  • the packet processor 1192 looks up (1166a) destination's IP address and UDP port number previously stored during session set-up and outputs the packet on the appropriate GbE connection.
  • the MLS device 1160 forwards (1 167a) addressed packets back to the MSC 1 150.
  • the non-processed target data path 1 1 12 illustrates the packet flow of targeted packets that pass through, but are not monitored or processed by, the monitoring point.
  • the non-processed target data path 11 12 is similar to the non- processed target data path 812 described in connection with Fig. 8, and begins like the processed target data path 1114.
  • An MLS device forwards (1161b) target the bearer plane packet (i.e., monitoring point addressed RTP or RTCP packet ) to the monitoring point 1190.
  • the bearer plane packet arrives (1162b) at a packet processor 1 192.
  • the packet processor 1192 looks up (1166b) the destination's IP address and UDP port number previously stored during session set-up and outputs the packet back on the appropriate GbE connection.
  • the MLS device 1160 forwards (1 167b,) addressed packets back to the MSC 1150.
  • the non-target packet data path 1 1 16 illustrates the packet flow of packets that have not been selected for transparent monitoring. In this data path, the MLS device 1160 simply forwards addressed packets back to the MSC 1 150.
  • Certain aspects of the example embodiments of the invention may be implemented in a form of software, firmware, or hardware. If implemented in software, the software may be written in any language suitable to support operations consistent with those described herein.
  • the software may be stored as computer readable instruction on any form of computer-readable medium, loaded by a processor, and executed by the processor on multiple processors in a manner understood in the art.
  • the processor(s) may be any form of general purpose or custom designed processor(s) suitable to perform operations illustrated by way of examples herein.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Computer Security & Cryptography (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

Dans le réseau d'aujourd'hui, l'amélioration ou sinon la modification des signaux dans des flux de canaux de support dans ou au niveau d'un équipement déjà déployé dans un réseau peut être effectuée en modifiant ou en mettant à jour l'équipement existant, ou sinon en acheminant des signaux de façon invasive par le biais d'éléments de réseau identifiés. Un procédé ou un appareil correspondant dans un mode de réalisation exemplaire de l'invention contrôle de façon transparente des messages de signalisation traversant le plan de commande pour l'établissement de connexions résidentes éventuelles d'un plan de données supportant des types de multimédia qui doivent être ciblés pour un traitement multimédia intermédiaire entre les nœuds d'extrémité de la connexion. Dans un mode de réalisation exemplaire, le procédé ou l'appareil correspondant utilise un routage basé sur des règles pour diriger les messages de signalisation depuis un point de routage dans le plan de commande à un point de contrôle de signalisation, également dans le plan de commande. Ce point de contrôle de signalisation agit comme un agent de signalisation intermédiaire qui identifie d'abord la signalisation de l'établissement de la connexion conformément à l'établissement des connexions du plan de données avec les types de multimédia ciblés pour le traitement multimédia. Une fois ainsi identifié, cet agent de signalisation remplacera les informations d'adresse du flux de support contenues dans les messages de signalisation par des informations d'adresse du flux de support des points de traitement multimédia dans le réseau du plan de données de telle sorte que les flux de support ultérieurs soient dirigés vers les points de traitement multimédia sélectionnés. Une fois que ces informations d'adresse du flux de support ont été remplacées dans le message de signalisation d'origine, le message de signalisation modifié sera présenté par l'agent de signalisation de nouveau au réseau de commutation de paquets du plan de commande, auquel point le message de signalisation modifié sera transmis à sa destination d'origine par des capacités de routage basées sur la destination inhérentes au réseau du plan de commande.
PCT/US2007/013555 2007-06-06 2007-06-06 Agent de signalisation transparent WO2008150264A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/US2007/013555 WO2008150264A1 (fr) 2007-06-06 2007-06-06 Agent de signalisation transparent
US12/012,208 US20090003231A1 (en) 2007-06-06 2008-01-31 Transparent signaling agent

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/US2007/013555 WO2008150264A1 (fr) 2007-06-06 2007-06-06 Agent de signalisation transparent

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US12/012,208 Continuation US20090003231A1 (en) 2007-06-06 2008-01-31 Transparent signaling agent

Publications (1)

Publication Number Publication Date
WO2008150264A1 true WO2008150264A1 (fr) 2008-12-11

Family

ID=39295988

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2007/013555 WO2008150264A1 (fr) 2007-06-06 2007-06-06 Agent de signalisation transparent

Country Status (1)

Country Link
WO (1) WO2008150264A1 (fr)

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2862411A4 (fr) * 2012-06-13 2016-03-30 All Purpose Networks LLC Procédés et systèmes d'un réseau large bande tout usage
US9743310B2 (en) 2012-06-13 2017-08-22 All Purpose Networks LLC Network migration queuing service in a wireless network
US9843973B2 (en) 2012-06-13 2017-12-12 All Purpose Networks LLC Real-time services across a publish-subscribe network with active-hot standby redundancy
US9882950B2 (en) 2012-06-13 2018-01-30 All Purpose Networks LLC Methods and systems of an all purpose broadband network
US9974091B2 (en) 2012-06-13 2018-05-15 All Purpose Networks LLC Multiple-use wireless network
US10116455B2 (en) 2012-06-13 2018-10-30 All Purpose Networks, Inc. Systems and methods for reporting mobile transceiver device communications in an LTE network
US10827019B2 (en) 2018-01-08 2020-11-03 All Purpose Networks, Inc. Publish-subscribe broker network overlay system
US11026090B2 (en) 2018-01-08 2021-06-01 All Purpose Networks, Inc. Internet of things system with efficient and secure communications network

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7006494B1 (en) * 2000-01-04 2006-02-28 Cisco Technology, Inc. System and method for a virtual telephony intermediary
US20070064896A1 (en) * 2005-08-23 2007-03-22 Su-Yuan Chang System and method for sharing SIP sessions

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7006494B1 (en) * 2000-01-04 2006-02-28 Cisco Technology, Inc. System and method for a virtual telephony intermediary
US20070064896A1 (en) * 2005-08-23 2007-03-22 Su-Yuan Chang System and method for sharing SIP sessions

Cited By (19)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10341921B2 (en) 2012-06-13 2019-07-02 All Purpose Networks, Inc. Active hot standby redundancy for broadband wireless network
US11711741B2 (en) 2012-06-13 2023-07-25 All Purpose Networks, Inc. Methods and systems of an all purpose broadband network with publish subscribe broker network
EP2862411A4 (fr) * 2012-06-13 2016-03-30 All Purpose Networks LLC Procédés et systèmes d'un réseau large bande tout usage
US9882950B2 (en) 2012-06-13 2018-01-30 All Purpose Networks LLC Methods and systems of an all purpose broadband network
US9942792B2 (en) 2012-06-13 2018-04-10 All Purpose Networks LLC Network migration queuing service in a wireless network
US9974091B2 (en) 2012-06-13 2018-05-15 All Purpose Networks LLC Multiple-use wireless network
US10116455B2 (en) 2012-06-13 2018-10-30 All Purpose Networks, Inc. Systems and methods for reporting mobile transceiver device communications in an LTE network
US10320871B2 (en) 2012-06-13 2019-06-11 All Purpose Networks, Inc. Providing handover capability to distributed sensor applications across wireless networks
US9843973B2 (en) 2012-06-13 2017-12-12 All Purpose Networks LLC Real-time services across a publish-subscribe network with active-hot standby redundancy
US9743310B2 (en) 2012-06-13 2017-08-22 All Purpose Networks LLC Network migration queuing service in a wireless network
US10841851B2 (en) 2012-06-13 2020-11-17 All Purpose Networks, Inc. Methods and systems of an all purpose broadband network with publish subscribe broker network
US10383133B2 (en) 2012-06-13 2019-08-13 All Purpose Networks, Inc. Multiple-use wireless network
US10884883B2 (en) 2012-06-13 2021-01-05 All Purpose Networks, Inc. Methods and systems of an all purpose broadband network with publish-subscribe broker network
US11647440B2 (en) 2012-06-13 2023-05-09 All Purpose Networks, Inc. Methods and systems of an all purpose broadband network with publish subscribe broker network
US11422906B2 (en) 2012-06-13 2022-08-23 All Purpose Networks, Inc. Methods and systems of an all purpose broadband network with publish-subscribe broker network
US11490311B2 (en) 2012-06-13 2022-11-01 All Purpose Networks, Inc. Methods and systems of an all purpose broadband network with publish subscribe broker network
US11026090B2 (en) 2018-01-08 2021-06-01 All Purpose Networks, Inc. Internet of things system with efficient and secure communications network
US11683390B2 (en) 2018-01-08 2023-06-20 All Purpose Networks, Inc. Publish-subscribe broker network overlay system
US10827019B2 (en) 2018-01-08 2020-11-03 All Purpose Networks, Inc. Publish-subscribe broker network overlay system

Similar Documents

Publication Publication Date Title
CN112640372B (zh) 提供移动设备连接性的方法、系统和计算机可读介质
KR101129264B1 (ko) 네트워크 자원들을 최적화하면서 최종 사용자로부터의 요청시 회의 오퍼레이션들을 위한 고속 네트워크 ｓｉｐ/ｓｄｐ 절차들
KR100954512B1 (ko) 상이한 네트워크 타입의 액세스 포인트에 대한 무선ＶｏＩＰ/ＶＩＰ 로밍
KR101311588B1 (ko) 인터넷 프로토콜 멀티미디어 서브시스템 기반 통신 시스템에서의 베어러 경로의 라우팅을 위한 방법 및 장치
KR101458336B1 (ko) Ｓｉｐ를 이용하는 기업 네트워크의 생존성을 위한 백업 ｓｉｐ 서버
US8213418B2 (en) Providing packet-based multimedia services via a circuit breaker
US10091256B2 (en) Access change for re-routing a connection
WO2008150264A1 (fr) Agent de signalisation transparent
US20040202295A1 (en) Lawful interception for VoIP calls in IP based networks
US20020064164A1 (en) Protocol header construction and/or removal for messages in wireless communications
US20090161590A1 (en) Multicast data stream selection in a communication system
US7263095B1 (en) Method and apparatus for providing quality of service through multiple carrier IP networks
US20090003570A1 (en) Method, system and apparatus for providing endpoint-to-endpoint transcoding free connection
CN102035813B (zh) 端到端呼叫的实现方法、端到端呼叫终端及系统
JP5118757B2 (ja) 遠隔通信ネットワークにおける機能ネゴシエーション
US7886349B2 (en) State-full perimeter security for data networks
CN1630411B (zh) 漫游方法、进行漫游的移动通信系统、利于漫游的系统
CN101114985B (zh) 编解码转换系统及方法
KR101606142B1 (ko) 음성패킷망에서 네트워크 주소 번역 통과를 지원하기 위한 장치 및 방법
JP4795027B2 (ja) 通信装置及び通信システム
US20090003231A1 (en) Transparent signaling agent
CN112653661B (zh) 一种VoIP网络限制下的媒体恢复方法和系统
RU2260253C2 (ru) Способ и система активизации контекста пакетных данных абонента для пакетных данных
Bale Voice and Internet multimedia in UMTS networks
KR100741379B1 (ko) 둘 이상의 가입자 회선을 이용한 ｓｉｐ 통신을 제어하는어플리케이션 스위치 및 그의 동작 방법

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: 07795917

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: 07795917

Country of ref document: EP

Kind code of ref document: A1