HK1167952A - Intelligent ims sip session setup optimization - Google Patents

Description

Intelligent IMS SIP session establishment optimization

Background

The Internet Protocol (IP) multimedia subsystem (IMS), defined by the third generation partnership project (3GPP), is an architectural framework for implementing IP-based telephony and multimedia services. IMS defines a set of specifications that enable convergence of voice, video, data and mobile technologies over all IP-based network infrastructures. In particular, IMS fills the gap between the two most successful communication paradigms, cellular and internet technologies, by providing internet services everywhere using cellular technologies in a more efficient manner. The Session Initiation Protocol (SIP) is the primary protocol for IMS. The purpose of IMS is to ensure that IMS applications work consistently across different network infrastructures.

Current IMS SIP call flow systems provide continuous and lengthy steps to establish or tear down a SIP session between caller a and caller B. These IMS SIP sessions may originate at an IMS-capable device and terminate at another IMS-capable device, a Public Switched Telephone Network (PSTN) or a non-IMS wireless device. SIP setup and/or teardown procedures are typically streaming continuously, where IMS network elements send similar and redundant SIP message commands to each other. These similar and redundant SIP message commands increase the number of SIP message steps performed and, in turn, increase the time to establish and tear down SIP sessions.

Drawings

FIG. 1 is a diagram of an exemplary network in which systems and methods described herein may be implemented;

fig. 2 is a diagram depicting further details of the exemplary IMS network of fig. 1;

fig. 3 illustrates exemplary components of an IMS SIP optimization server and/or network elements of the network depicted in fig. 2;

fig. 4 depicts a diagram of exemplary functional components of the IMS SIP optimization server of fig. 2;

FIG. 5 depicts a diagram of exemplary interactions between components of the exemplary portion of the networks illustrated in FIGS. 1 and 2;

fig. 6 is a flow diagram illustrating an exemplary procedure for setting up an IMS SIP session; and

fig. 7 is a diagram illustrating an exemplary SIP call flow associated with the exemplary process of fig. 6.

Detailed Description

The following detailed description refers to the accompanying drawings. The same reference numbers in different drawings may identify the same or similar elements. The following detailed description does not limit the invention.

The systems and/or methods described herein can optimize message traffic and reduce latency of SIP session setup and teardown without requiring that each individual network element be involved in the SIP session call flow in the procedures required to set up a SIP connection. The IMS SIP optimization server may identify and store customized SIP session messages for each network element within the IMS network. The IMS SIP optimization server may also collect historical SIP session data and identify patterns to predict SIP session activity. As further described herein, previously stored information may be used to enable parallel signaling during a single SIP setup and/or teardown session for a terminal device and an intermediate network element.

Fig. 1 provides a diagram of an exemplary network 100 in which systems and/or methods described herein may be implemented. More particularly, network 100 may implement intelligent IMS SIP session establishment optimization. As shown in fig. 1, network 100 may include a wired access network 105 and a wireless network 110, both connected to an IMS network 115. Originating user equipment 120 and terminating user equipment 125-1 through 125-n (commonly referred to as "terminating user equipment 125") may be connected to the wired access network 105 and/or the wireless network 110 to facilitate communication between the originating user equipment 120 and one or more terminating user equipment 125. For simplicity, one wired access network 105, one wireless network 110 and one IMS network 115, and several user equipments 120/125 have been illustrated in fig. 1. In practice there may be more wired access networks, wireless networks and IMS networks and user equipment.

Wired network 105 may include one or more wire-based networks, such as a Local Area Network (LAN); a Wide Area Network (WAN); metropolitan Area Networks (MANs); telephone networks, such as the Public Switched Telephone Network (PSTN); an intranet; and/or the internet.

Wireless network 110 may include one or more wireless-based networks, such as a wireless satellite network and/or a wireless Public Land Mobile Network (PLMN). Wireless network 110 may include a plurality of access technologies available to originating user equipment 120 and/or terminating user equipment 125. For example, wireless network 110 may include a wireless global system for mobile communications (GSM) network and/or a Code Division Multiple Access (CDMA) network, or any third generation partnership project (3GPP) compliant cellular network (e.g., 3GPP or 3GPP 2).

IMS network 115 may include a network that may interact with networks 105 and 110 to implement IP-based telephony and multimedia services. IMS network 115 may generally be operable according to standards defined by 3GPP to allow service providers to manage a variety of services that can be delivered over any network type via IP, which is used to transport both bearer traffic and Session Initiation Protocol (SIP) based signaling traffic. IMS network 115 may include multiple layers (e.g., a service/application layer, an IMS layer, and a transport layer) that include various network elements that deliver applications and/or services for use by user device 120/125. Exemplary services include caller ID related services, call waiting, call hold, push-to-talk (push-to-talk), conference call server, voice mail, instant messaging, call restriction, and call forwarding. Further details of IMS network 115 are described below with reference to fig. 2.

In general, the originating user equipment 120 and terminating user equipment 125-1 through 125-n may use services provided by the IMS network 115. Originating user equipment 120 may include wireless communication devices that access IMS network 115 via wireless network 110. For example, the originating user equipment 120 may include a personal computer (e.g., a laptop, palmtop, or handheld computing device) equipped with an appropriate wireless modem; a mobile communication device (e.g., a cellular radiotelephone or a handheld device having data capabilities capable of receiving and sending messages, web browsing, etc.); a portable gaming system; or any enhanced PDA device or integrated information appliance capable of email, video mail, internet access, messaging, scheduling, information management, etc.

Terminating user devices 125-1 through 125-n may include wired or wireless communication devices. Thus, in one embodiment, the terminating user equipment 125 may be configured similar to the originating user equipment 120 described above. In other embodiments, terminating user device 125 may comprise another device configured to receive information over wired network 110, such as a PSTN.

Fig. 2 depicts further details of IMS network 115. As shown, IMS network 115 may include an IMS SIP optimization server 210 and a plurality of network elements 215-1 through 215-n (collectively referred to as "network elements 215" and generically "network elements 215").

IMS SIP optimization server 210 may include one or more servers or other types of computing or communication devices that gather, process, search, and/or provide information in the manner described herein. In one embodiment, IMS SIP optimization server 210 may comprise a server (e.g., a computer system) with a plurality of modules that optimize the establishment and teardown of SIP sessions. As further described herein, IMS SIP optimization server 210 can use previous SIP session data to quickly set up a SIP session between an originating user equipment (e.g., originating user equipment 120) and a terminating user equipment (terminating user equipment 125) and facilitate parallel transactions with multiple network elements 215 to conform to SIP call flow standards. IMS SIP optimization server 210 is described in more detail with reference to fig. 3 and 4.

Network elements 215 may include one or more IMS servers, such AS a proxy call/session control function (P-CSCF) server, a serving CSCF (S-CSCF) server, an interrogating CSCF (I-CSCF), a SIP application server (SIP AS), and/or a Home Subscriber Server (HSS). For example, network element 215-1 may be a P-CSCF server that serves as the first point of contact between an originating user equipment (e.g., originating user equipment 120) and IMS network 115. P-CSCF server 215-1 may act as an outbound/inbound SIP proxy server where requests initiated by originating user equipment 120 may traverse to P-CSCF server 215-1. As a first point of contact within IMS network 115, P-CSCF server 215-1 (or any other network element 215 acting as a first point of contact) may provide a request initiated by originating user equipment 120 to IMS SIP optimization server 210.

The other network elements 215 may further facilitate session establishment and provide multimedia services to the originating user equipment 120. For example, another network element (e.g., network element 215-2) may be an S-CSCF server. The S-CSCF server may comprise a SIP server acting as a central node in the SIP signaling plane. The S-CSCF server may perform session control. Another network element (e.g., network element 215-n) may be an I-CSCF server. The I-CSCF servers may include SIP servers that may be located at the edge of the administrative domain. The I-CSCF server may publish its IP address in a Domain Name System (DNS) record of the domain in which the I-CSCF resides so that a remote server can find the I-CSCF and use it as a forwarding point for SIP packets in that domain. In addition to the SIP proxy function, the I-CSCF may include an interface for the HSS (another of network elements 215) to retrieve user information and route messages to the appropriate destination (e.g., an S-CSCF). Another network element (e.g., network element 215-3) may be a SIP AS. A SIP AS may include SIP entities that host and execute services and interface with S-CSCFs. The HSS may include a primary user database that supports the IMS network 115 and contains subscription-related information. The HSS can perform authentication and authorization of the user and can provide information about the location of the subscriber and IP information.

In one example, certain network elements 215 may be owned and/or managed by a particular operator that is different from the operator that owns and/or manages other certain network elements 215. The network element 215 may further include one or more gateways. For example, network element 215 may include a gateway that interfaces IMS network 115 with components of wireline network 105, such as the PSTN.

Fig. 3 is an exemplary diagram of a device 300 that may interface with IMS SIP optimization server 210 and/or network element 215. As shown, device 300 may include a bus 310, a processor 320, a main memory 330, a Read Only Memory (ROM)340, a storage device 350, an input device 360, an output device 370, and/or a communication interface 380. Bus 310 may include a path that permits communication among the components of device 300.

Processor 320 may include one or more processors, microprocessors, or other types of processing devices that may interpret and execute instructions. Main memory 330 may include one or more Random Access Memories (RAMs) or another type of dynamic storage device that may store information and instructions for execution by processor 320. ROM 340 may include one or more ROM devices or another type of static storage device that may store static information and/or instructions for use by processor 320. Storage device 350 may include one or more magnetic and/or optical recording media and its corresponding drive.

Input device 360 may include one or more mechanisms that allow an operator to input information to device 300, such as a keyboard, mouse, pen, microphone, voice recognition and/or biometric mechanisms, and the like. Output device 370 may include one or more mechanisms that output information to the operator, including a display, a printer, a speaker, and the like. Communication interface 380 may include any transceiver-like mechanism that enables device 300 to communicate with other devices and/or systems. For example, communication interface 380 may include mechanisms for communicating with another device or system via a network, such as network 150.

As described herein, device 300 may perform certain operations in response to processor 320 executing software instructions contained in a computer-readable medium, such as main memory 330. A computer-readable medium may be defined as a physical or logical memory device. Logical memory devices may include memory space that is spread within a single physical memory device or across multiple physical memory devices. The software instructions may be read into main memory 330 from another computer-readable medium, such as storage device 350, or from another device via communication interface 380. The software instructions contained in main memory 330 may cause processor 320 to perform processes described herein. Alternatively, hardwired circuitry may be used in place of or in combination with software instructions to implement processes described herein. Thus, embodiments described herein are not limited to any specific combination of hardware circuitry and software.

Although fig. 3 shows exemplary components of device 300, in other implementations, device 300 may contain fewer, different arrangements, or additional components than depicted in fig. 3. In other embodiments, one or more components of device 300 may perform one or more other tasks described as being performed by one or more other components of device 300.

Fig. 4 depicts a diagram of exemplary functional components of IMS SIP optimization server 210. As shown in fig. 4, IMS SIP optimization server 210 may include a pattern data collection and classification module (PDGCM)410, a SIP Session Pattern Analysis Manager Module (SSPAMM)420, an adaptive random controller module (ASCM)430, a SIP Session Activation Manager Module (SSAMM)440, a client logging network module (CRNM)450, and an adaptive interface module 460.

The PDGCM410 can collect SIP session data for callers of originating devices (e.g., originating user equipment 120) and organize the data into major categories. The session data may include, for example, a source address, a destination address (e.g., of terminating user equipment 125), a call time (e.g., a timestamp), a call duration, and so forth. In addition, information about the access network of the originating user equipment and any visited (e.g., roaming) networks may be collected. The pdgfm 410 may further collect IMS SIP extension information for how to negotiate quality of service (QoS), security, and other call behavior for each SIP session between the originating device (originating user equipment 120) and the endpoint (e.g., terminating user equipment 125).

The main categories used by the pdgfm 410 for SIP session data may include, for example, distinguishing between calls to wired networks and calls to wireless networks. For example, for each originating device, the PDGCM410 can distinguish between SIP sessions using the terminating user equipment 125 of the wired network (e.g., the terminating user equipment wired network 105) and SIP sessions using the wireless network (e.g., the wireless network 115). In one embodiment, the pdgfm 410 may be implemented within the processor 320 of the IMS SIP optimization server 210. The data collected by the pdgfm 410 may be stored, for example, in the main memory 330 and/or the storage device 350 of the IMS SIP optimization server 210.

The SSPAMM 420 may determine the call mode and identify the subcategory of data from the pdgfm 410. For example, the SSPAMM 420 may analyze the source and destination addresses, the frequency of calls to the destination, the duration of the calls, and other relevant data associated with each call to build and manage the subcategories. In one embodiment, the SSPAMM 420 may further classify the wireless network SIP session data about the caller into subcategories based on the type of wireless protocol used for the session (e.g., CDMA, GSM, 3G LTE, etc.).

The SSPAMM 420 may rearrange the priority and queuing systems for managing the sub-categories. For example, call mode may be used to allocate resources to facilitate a predicted SIP session. In one embodiment, the SSPAMM 420 may be implemented within the processor 320 of the IMS SIP optimization server 210. The mode data of the SSPAMM 420 may be stored separately from the pdgfm 410 data, for example in the main memory 330 and/or the storage device 350 of the IMS SIP optimization server 210.

The ASCM 430 may apply a control theory approach to measure the accuracy of the patterns in the SSPAMM 420. For example, the ASCM 430 may apply one or more stochastic control methodologies based on the nature and changes of the data sets of the managed sub-categories (e.g., obtained from the SSPAMM 420). In one embodiment, ASCM 430 may calculate three parameters to gauge the quality and accuracy of the pattern. ASCM 430 may then reconcile these results with the appropriate destination and timestamp for the SIP session. In addition, ASCM 430 may feed this data into SSAMM440 and keep track of which random methodology is optimal for producing the most accurate SIP session establishment. In one embodiment, ASCM 430 may be implemented within processor 320 of IMS SIP optimization server 210.

SSAMM440 may use input from ASCM 430 to initiate a SIP session between two or more devices (e.g., an originating device and one or more terminating devices). For example, based on data and pattern analysis from ASCM 430, SSAMM440 may initiate a SIP session between two devices (e.g., one of originating user equipment 120 and terminating device 125) without the two devices having to wait for all intermediate network elements 215 participating in the SIP session to process their associated SIP messages or steps. When establishing a SIP session, SSAMM440 may concurrently feed appropriate SIP messages and other related data to other network elements 215 that will participate in the conventional establishment of a SIP session. The appropriate SIP messages for each network element may be predetermined, for example, based on information collected by the adaptive interface module 460 described below. In one embodiment, SSAMM440 may be implemented within processor 320 of IMS SIP optimization server 210.

CRNM450 may keep track of SIP message types for each originating user equipment 120 and corresponding network element with success and failure rates and counts for call setup and teardown. CRNM450 may feed this information back into SSPAMM 420 to improve pattern recognition and sub-classification methodologies. For example, CRNM450 may identify a success rate for a particular originating device 120, which may be used to improve call pattern recognition for that originating device 120. Similarly, CRNM450 may identify a success rate for a particular network element 215 that may be used to improve SIP establishment sessions involving that particular network element 215. In one embodiment, CRNM450 may be implemented within processor 320 of IMS SIP optimization server 210.

Adaptive interface module 460 may provide customized packet messages to appropriate network elements 215 within the existing IMS architecture (e.g., IMS network 115) to which IMS SIP optimization server 210 is connected. The customized packet message may include SIP commands to other network elements participating in the intended SIP session. The adaptation interface module 460 may further process reply messages to the customized packet message and return a result status from the corresponding network element. Accordingly, the adaptive interface module 460 may create and update a SIP command and message library for the corresponding network element 215. In one embodiment, adaptive interface module 460 may be implemented within processor 320 of IMS SIP optimization server 210. SIP commands and messages for adaptive interface module 460 may be stored, for example, in main memory 330 and/or storage device 350 of IMS SIP optimization server 210.

Although fig. 4 shows exemplary functional components of IMS SIP optimization server 210, in other embodiments, IMS SIP optimization server 210 may contain fewer, different arrangements, or additional functional components than depicted in fig. 4. In other embodiments, one or more functional components of IMS SIP optimization server 210 may perform one or more other tasks described as being performed by one or more other functional components of IMS SIP optimization server 210.

Fig. 5 depicts a diagram of exemplary interactions between components of a portion of the network illustrated in fig. 1 and 2. As shown in fig. 5, SIP session requests 505-1, 505-2,... 505-m from one or more originating user equipment 120 (e.g., via a first network element (not shown)) may be directed to IMS SIP optimization server 210. IMS SIP optimization server 210 may include a Network Element Connectivity Interface (NECI)510 to facilitate the exchange of customized packet messages to network element 215. In particular, a customized packet message, referred to herein as an Interface Data Packet (IDP)515-1, 515-2, 515-3,... 515-n, may be provided to each respective network element 215-1, 215-2, 215-3,... 215-n. Since each network element 215 has its own set of commands and/or steps to establish a SIP session, IMS SIP optimization server 210 (e.g., adaptive interface module 460) may provide each network element with the unique IDP515 required for the IMS SIP session requested by one of originating devices 120. IMS SIP optimization server 210 may be implemented as a single server device or IMS SIP optimization server 210 may be a distributed system.

Fig. 6 depicts a flow diagram illustrating an exemplary process 600 for setting up an IMS SIP session according to an embodiment described herein. In one embodiment, process 600 may be performed by IMS SIP optimization server 210. In another embodiment, some or all of process 600 may be performed by another device or group of devices, with or without IMS SIP optimization server 210.

As shown in fig. 6, process 600 may begin with collecting caller SIP session data (block 610). For example, IMS SIP optimization server 210 (e.g., pdgfm 410) may collect data for a plurality of IMS SIP sessions initiated by originating user equipment 120. The session data may include, for example, the source address of the caller (e.g., originating user equipment 120), the destination address of each call (e.g., terminating user equipment 125), the network type associated with the destination address (e.g., wired network 105, wireless network 115), the time of the call, the duration of the call, and so forth.

SIP data from the network element may be collected (block 620). For example, IMS SIP optimization server 210 (e.g., AIM 460) may identify an appropriate SIP session command for each of the network elements (e.g., network element 215) within the IMS network (e.g., IMS network 115). Thus, for example, IMS SIP optimization server 210 may identify one set of commands to set up a SIP session for network element 215-1 (which may be a P-CSCF) and a different set of commands to set up a SIP session for network element 215-2 (which may be a SIP AS).

A call mode may be determined (block 630). For example, the IMS SIP optimization server 210 (e.g., pdgfm 410 and/or SSPAMM 420) may analyze the session collection data to build and manage categories and subcategories. The categories for a single originating device may distinguish between, for example, a call session to a terminating device using a wired network and a call session to a terminating device using a wireless network. The call session to the terminating device using the wireless network may be further grouped by the type of wireless network or network protocol used (e.g., CDMA, GSM, 3G LTE, etc.). IMS SIP optimization server 210 may identify patterns within the categories and/or subcategories. For example, a particular originating user equipment 120 may regularly make an IMS call to a particular terminating device 125 at about noon on a weekday. IMS SIP optimization server 210 may identify the call mode and prioritize network resources to facilitate the SIP session prior to the call from that particular originating user equipment 120.

The pattern accuracy may be analyzed (block 640). For example, IMS SIP optimization server 210 (e.g., ASCM 430) may apply a control theory approach to measure the accuracy of previously identified patterns. Thus, IMS SIP optimization server 210 can account for random deviations from the identified pattern.

A SIP session may be initiated with the last network element (block 650). For example, IMS SIP optimization server 210 (e.g., SSAMM 440), in response to the SIP session invite message, may identify the last network element (e.g., network element 215-n) in the SIP session establishment procedure for the particular SIP session invite message. The last network element 215-n may be the closest network element to the terminating device required to establish the requested SIP session. IMS SIP optimization server 210 may bypass intermediate network element 215 and provide a SIP session invite message to last network element 215-n with the appearance of having been processed sequentially through all network elements SIP establishment procedures.

Customized SIP messages may be initiated to other network elements (block 660). For example, IMS SIP optimization server 210 (e.g., SSAMM 440) can provide an IDP to each intermediate network element 215 to update each intermediate network element of the SIP session state for originating user equipment 120 and terminating user equipment 125. In one embodiment, the customized SIP message may be provided in parallel with the SIP session invite message sent to the respective last network element 215-n.

The SIP session data may be updated (block 670). For example, IMS SIP optimization server 210 (e.g., CRNM 450) may identify whether the optimized SIP session establishment succeeded or failed. CRNM450 may then provide session data to one or more other modules within IMS SIP optimization server 210 to further improve, for example, the schema definition and SIP command and message library.

Although the process 600 is described primarily in the context of SIP session establishment, the process 600 may similarly be applied to SIP session teardown commands (e.g., cancel or bye SIP request). Accordingly, IMS SIP optimization server 210 may provide reduced message traffic and transaction time for both IMS SIP setup and teardown.

Fig. 7 provides a simplified call flow for an exemplary SIP setup session according to embodiments described herein. As shown in fig. 7, the originating user equipment 120 (e.g., UE1) may initiate a SIP session by sending a SIP invite message 702 to the first network element 215-1 (e.g., P-CSCF). The first network element may in turn provide the SIP invite message 704 to an IMS SIP optimization server (ISOP) 210. IMS SIP optimization server 210 may direct SIP invite message 706 directly to the last network element 215-4 (e.g., S-CSCF 215-4) in the SIP setup sequence for the requested SIP session, bypassing intermediate network elements 215-2 (e.g., HSS) and 215-3(SIP AS). Finally network element 215-4 may send SIP invite message 708 to terminating user equipment 125 (e.g., UE 2).

Assuming that the SIP invite message was successfully received, understood, and accepted, terminating user equipment 125 may respond to the SIP invite message with a success message 710 for the last network element 215-4. Finally network element 215-4 may then again provide success message 712 to IMS SIP optimization server 210, bypassing intermediate network elements 215-3 and 215-2. IMS SIP optimization server 210 may provide success message 714 to first network element 215-1 and first network element 215-1 may then provide success message 716 to originating user equipment 120 to complete the SIP session establishment.

The intermediate network elements 215-2 and 215-3 may be updated to support SIP session establishment by receiving customized packet messages. Accordingly, IMS SIP optimization server 210 may send IDP 718 to intermediate network element 215-3 and IDP720 to intermediate network element 215-2 in parallel with SIP invite message 706. Assuming that the IDP is successfully received, understood, and accepted, each of intermediate network elements 215-2 and 215-3 may respond to IMS SIP optimization server 210 with success messages 722 and 724, respectively. Although two intermediate network elements 215-2 and 215-3 are shown in the simplified example of fig. 7, in other embodiments, more or fewer intermediate network elements 215 may be included.

Systems and/or methods described herein may include an IMS SIP optimization server in communication with a plurality of network elements within an IMS network. An IMS SIP optimization server may facilitate an end-to-end SIP session between an originating user equipment and a terminating user equipment while concurrently sending SIP session information to intermediate network elements. An IMS SIP optimization server may collect historical SIP session data for originating, terminating, and network elements to predict SIP session activity and enable parallel setup messages to be used for intermediate network elements. The IMS SIP optimization server may receive a SIP request from a first network element, wherein the first network element is the closest network element in the SIP sequence to the originating user equipment, and send a related SIP request to a last network element, wherein the last network element is the closest network element in the SIP sequence to the terminating user equipment. The IMS SIP optimization server may also send the customized packet message to any intermediate network element, where the intermediate network element is between the first network element and the last network element in the SIP sequence, and where the customized packet message includes a SIP setup command for each of the intermediate network elements.

The foregoing description of embodiments provides illustration and description, but is not intended to be exhaustive or to limit the invention to the precise form disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of the invention.

For example, while series of blocks have been described with regard to fig. 6, the order of the blocks may be modified in other implementations. Further, non-dependent blocks may be performed in parallel.

It will be apparent that aspects described herein may be implemented in many different forms of software, firmware, and hardware in the implementations illustrated in the figures. The actual software code or specialized control hardware used to implement these aspects is not limiting of the present invention. Thus, the operation and behavior of the aspects were described without reference to the specific software code — it being understood that software and control hardware may be designed to implement the aspects based on the description herein.

Furthermore, certain portions of the invention may be implemented as "logic" that performs one or more functions. The logic may include: hardware, such as an application specific integrated circuit or a field programmable gate array; or a combination of hardware and software.

Although particular combinations of features are recited in the claims and/or disclosed in the specification, these combinations are not intended to limit the disclosure of the invention. Indeed, many of these features may be combined in ways not explicitly recited in the claims and/or explicitly disclosed in the specification.

No element, act, or instruction used in the description of the present application should be construed as critical or essential to the invention unless explicitly described as such. Also, as used herein, an item without an added quantity is intended to include one or more items. The word "one" or similar language is used when referring to only one item. Further, the phrase "based on" is intended to mean "based, at least in part, on" unless explicitly stated otherwise.

Claims (22)

1. A computer device, comprising:

a Session Initiation Protocol (SIP) session activation manager module in communication with a plurality of network elements within a network, wherein the SIP session activation manager module facilitates an end-to-end SIP session between an originating user equipment and a terminating user equipment and is configured to:

receiving a SIP request from a first network element of the plurality of network elements, wherein the first network element is the closest network element in a SIP sequence to the originating user equipment,

sending the relevant SIP request to a last network element of the plurality of network elements, wherein the last network element is the closest network element in the SIP sequence to the terminating user equipment, an

Sending a customized packet message to an intermediate network element of the plurality of network elements, wherein the intermediate network element is between the first network element and the last network element in the SIP sequence, and wherein the customized packet message comprises a SIP setup command for the intermediate network element.

2. The apparatus of claim 1, further comprising:

a mode data collection and classification module for collecting SIP call flow data for a plurality of SIP sessions within the network.

3. The apparatus of claim 2, further comprising:

a SIP Session mode analysis manager module to identify a session mode based on the SIP call flow data, wherein the SIP Session activation manager module prioritizes the end-to-end SIP session based on the session mode.

4. The apparatus of claim 3, further comprising:

and the self-adaptive controller module is used for evaluating the accuracy of the conversation mode.

5. The apparatus of claim 1, further comprising:

a client logging network module to determine a successful SIP session rate for the originating device or one of the plurality of network elements.

6. The apparatus of claim 1, further comprising:

an adaptive interface module to identify a SIP setup or teardown command message for each of the plurality of network elements.

7. The apparatus of claim 1, wherein the network comprises an Internet Protocol (IP) multimedia subsystem (IMS) network.

8. A computer-implemented method, comprising:

receiving, by a processor of the computer, a Session Initiation Protocol (SIP) request from a first network element of a plurality of network elements, wherein the first network element is the closest network element in a SIP sequence to an originating user equipment,

sending, by the processor, an associated SIP request to a last network element of the plurality of network elements, wherein the last network element is a network element in the SIP sequence that is closest to the terminating user equipment, and

sending, by the processor, a customized packet message to an intermediate network element of the plurality of network elements, wherein the intermediate network element is between the first network element and the last network element in the SIP sequence, and wherein the customized packet message includes a SIP setup command for the intermediate network element.

9. The computer-implemented method of claim 8, wherein the sending the customized packet message to an intermediate network element is performed in parallel with the sending the relevant SIP request to a final network element.

10. The computer-implemented method of claim 8, further comprising:

SIP call flow data is collected for a plurality of SIP sessions within the network.

11. The computer-implemented method of claim 10,

identifying a session mode based on the SIP call flow data, wherein the SIP Session activation manager module prioritizes the end-to-end SIP session based on the session mode.

12. The method of claim 11, further comprising:

evaluating an accuracy of the conversation mode based on at least one stochastic control methodology.

13. The method of claim 8, further comprising:

comparing the number of successful SIP sessions to a total number of sessions for the originating device or one of the plurality of network elements.

14. The method of claim 8, wherein,

identifying a particular SIP setup or teardown command message for each of the plurality of network elements.

15. The method of claim 8, wherein the network comprises an Internet Protocol (IP) multimedia subsystem (IMS) network.

16. An apparatus, comprising:

a memory for storing a plurality of instructions to set up a Session Initiation Protocol (SIP) session; and

a processor to execute instructions in the memory to:

receiving a SIP request over a network from a first network element, wherein the first network element is the closest network element in a SIP sequence to an originating user equipment,

sending the relevant SIP request over the network to a last network element, wherein the last network element is the network element in the SIP sequence that is closest to the terminating user equipment, an

Sending one or more customized packet messages over the network to an intermediate network element, wherein the intermediate network element is between the first network element and the last network element in the SIP sequence, and wherein each of the one or more customized packet messages includes a SIP command for a particular one of the intermediate network elements,

wherein the SIP request, the related SIP request, and the one or more customized packet messages together initiate an end-to-end SIP session between the originating user equipment and the terminating user equipment.

17. The method of claim 16, wherein the processor is further configured to:

collecting SIP call flow data for a plurality of SIP sessions within the network,

identifying a plurality of session modes based on the SIP call flow data, an

Prioritizing the end-to-end SIP sessions based on the session patterns.

18. The method of claim 16, wherein the processor is further configured to:

a SIP setup or teardown command message is identified for each of the plurality of network elements.

19. The method of claim 16, wherein the network comprises an Internet Protocol (IP) multimedia subsystem (IMS) network.

20. The method of claim 16, wherein the processor sends the relevant SIP request to the last network element and the one or more customized packet messages to the intermediate network element in parallel.

21. A system, comprising:

means for receiving a Session Initiation Protocol (SIP) request from a first network element, wherein the first network element is the closest network element in a SIP sequence to an originating user equipment,

means for sending the relevant SIP request to the last network element, wherein the last network element is the network element in the SIP sequence closest to the terminating user equipment, and

means for sending one or more customized packet messages to an intermediate network element, wherein the intermediate network element is between the first network element and the last network element in the SIP sequence, and wherein each of the one or more customized packet messages includes a SIP command for a particular one of the intermediate network elements,

wherein the SIP request, the related SIP request, and the one or more customized packet messages together initiate an end-to-end SIP session between the originating user equipment and the terminating user equipment.

22. The system of claim 21, wherein the network comprises an Internet Protocol (IP) multimedia subsystem (IMS) network.