US9906616B2 - Systems and methods for multi-line, multi-device service in a communications network - Google Patents

Systems and methods for multi-line, multi-device service in a communications network Download PDF

Info

Publication number
US9906616B2
US9906616B2 US14/992,791 US201614992791A US9906616B2 US 9906616 B2 US9906616 B2 US 9906616B2 US 201614992791 A US201614992791 A US 201614992791A US 9906616 B2 US9906616 B2 US 9906616B2
Authority
US
United States
Prior art keywords
lines
line
service node
user
proxy service
Prior art date
Legal status (The legal status 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 status listed.)
Active, expires
Application number
US14/992,791
Other languages
English (en)
Other versions
US20160352855A1 (en
Inventor
Anish Sharma
Michael Brett Wallis
Bejoy Pankajakshan
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
T Mobile USA Inc
Mavenir Systems Inc
Original Assignee
Mavenir Systems 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
Assigned to MITEL NETWORKS CORPORATION reassignment MITEL NETWORKS CORPORATION ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: PANKAJAKSHAN, BEJOY, SHARMA, ANISH, WALLIS, MICHAEL BRETT
Priority to US14/992,791 priority Critical patent/US9906616B2/en
Application filed by Mavenir Systems Inc filed Critical Mavenir Systems Inc
Priority to EP16151266.0A priority patent/EP3101864B1/de
Priority to CA2917793A priority patent/CA2917793C/en
Assigned to BANK OF AMERICA, N.A. (ACTING THROUGH ITS CANADA BRANCH), AS CANADIAN COLLATERAL AGENT reassignment BANK OF AMERICA, N.A. (ACTING THROUGH ITS CANADA BRANCH), AS CANADIAN COLLATERAL AGENT SECURITY INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: MITEL NETWORKS CORPORATION
Publication of US20160352855A1 publication Critical patent/US20160352855A1/en
Assigned to MITEL MOBILITY, INC. reassignment MITEL MOBILITY, INC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: MITEL NETWORKS CORPORATION
Assigned to MITEL MOBILITY INC. reassignment MITEL MOBILITY INC. PARTIAL RELEASE OF SECURITY INTEREST IN PATENTS Assignors: BANK OF AMERICA, N.A.
Assigned to CERBERUS BUSINESS FINANCE, LLC, AS COLLATERAL AGENT reassignment CERBERUS BUSINESS FINANCE, LLC, AS COLLATERAL AGENT GRANT OF A SECURITY INTEREST -- PATENTS Assignors: MAVENIR SYSTEMS, INC. (F/K/A MITEL MOBILITY INC.)
Assigned to MITEL NETWORKS, INC., MITEL US HOLDINGS, INC., MITEL (DELAWARE), INC., MITEL BUSINESS SYSTEMS, INC., MITEL COMMUNICATIONS, INC., MITEL NETWORKS CORPORATION reassignment MITEL NETWORKS, INC. RELEASE BY SECURED PARTY (SEE DOCUMENT FOR DETAILS). Assignors: BANK OF AMERICA, N.A., (ACTING THROUGH ITS CANADA BRANCH), AS CANADIAN COLLATERAL AGENT, BANK OF AMERICA, N.A., AS COLLATERAL AGENT
Assigned to MAVENIR SYSTEMS, INC. reassignment MAVENIR SYSTEMS, INC. CHANGE OF NAME (SEE DOCUMENT FOR DETAILS). Assignors: MITEL MOBILITY INC.
Publication of US9906616B2 publication Critical patent/US9906616B2/en
Application granted granted Critical
Assigned to MAVENIR SYSTEMS, INC. (F/K/A MITEL MOBILITY INC.) reassignment MAVENIR SYSTEMS, INC. (F/K/A MITEL MOBILITY INC.) RELEASE BY SECURED PARTY (SEE DOCUMENT FOR DETAILS). Assignors: CERBERUS BUSINESS FINANCE, LLC, AS COLLATERAL AGENT
Assigned to GOLDMAN SACHS LENDING PARTNERS LLC, AS COLLATERAL AGENT reassignment GOLDMAN SACHS LENDING PARTNERS LLC, AS COLLATERAL AGENT GRANT OF SECURITY INTEREST IN PATENTS Assignors: MAVENIR SYSTEMS, INC.
Assigned to T-MOBILE USA, INC. reassignment T-MOBILE USA, INC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: SEWARD, SHELBY, PISCOPO, Robert F., Jr.
Assigned to JPMORGAN CHASE BANK, N.A. reassignment JPMORGAN CHASE BANK, N.A. SECURITY AGREEMENT Assignors: MAVENIR SYSTEMS, INC.
Assigned to MAVENIR SYSTEMS, INC. reassignment MAVENIR SYSTEMS, INC. TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENT COLLATERAL - RELEASE OF 046139.0299 Assignors: GOLDMAN SACHS LENDING PARTNERS LLC, AS COLLATERAL AGENT
Assigned to JPMORGAN CHASE BANK, N.A. reassignment JPMORGAN CHASE BANK, N.A. SECURITY AGREEMENT Assignors: MAVENIR SYSTEMS, INC.
Assigned to WILMINGTON SAVINGS FUND SOCIETY, FSB reassignment WILMINGTON SAVINGS FUND SOCIETY, FSB SECURITY INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: MAVENIR SYSTEMS, INC.
Assigned to WILMINGTON SAVINGS FUND SOCIETY, FSB reassignment WILMINGTON SAVINGS FUND SOCIETY, FSB SECURITY INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: MAVENIR SYSTEMS, INC.
Active legal-status Critical Current
Adjusted expiration legal-status Critical

Links

Images

Classifications

    • H04L67/2838—
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/56—Provisioning of proxy services
    • H04L67/567—Integrating service provisioning from a plurality of service providers
    • 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/1083—In-session procedures
    • H04L65/1094—Inter-user-equipment sessions transfer or sharing
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/23—Updating
    • G06F16/2379—Updates performed during online database operations; commit processing
    • G06F17/30377—
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
    • G06F3/0481—Interaction techniques based on graphical user interfaces [GUI] based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance
    • G06F3/0482—Interaction with lists of selectable items, e.g. menus
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
    • G06F3/0484—Interaction techniques based on graphical user interfaces [GUI] for the control of specific functions or operations, e.g. selecting or manipulating an object, an image or a displayed text element, setting a parameter value or selecting a range
    • G06F3/04842—Selection of displayed objects or displayed text elements
    • 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/1016—IP multimedia subsystem [IMS]
    • 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/1073—Registration or de-registration
    • 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/1083—In-session procedures
    • H04L65/1095—Inter-network session transfer or sharing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H04W60/04—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration using triggered events
    • H04W76/025—
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/15—Setup of multiple wireless link connections

Definitions

  • the present disclosure generally relates to communication systems and methods, and more particularly to communication systems and methods that allow for the use of multiple lines on one or more devices in a communications network.
  • typical communication networks generally provide a single line or number that is associated with a UE.
  • Various users can have several devices, each with its own line.
  • a user may wish to use one or more lines with one or more devices and/or share a line with other users.
  • While some Over The Top applications may provide an ability for a user to use a second line on a device, such applications generally do not allow for multiple lines to be used on multiple devices in an efficient and/or transparent manner. Accordingly, improved communications systems and methods are desired.
  • FIG. 1 illustrates a network architecture diagram of an exemplary communication network according to the present disclosure
  • FIG. 2 illustrates a data flow diagram of an exemplary registration fork process according to the present disclosure
  • FIG. 3 illustrates a more detailed data flow diagram of an exemplary registration fork process according to the present disclosure
  • FIG. 4 illustrates a data flow diagram of an exemplary mobile originated request according to the present disclosure
  • FIG. 5 illustrates a data flow diagram of an exemplary mobile terminated request according to the present disclosure
  • FIG. 6 illustrates a data flow diagram of an exemplary multi-line registration request according to the present disclosure
  • FIG. 7 illustrates a data flow diagram of an exemplary mobile originated request and subsequent SRVCC according to the present disclosure.
  • FIG. 8 illustrates a data flow diagram of an exemplary mobile terminated request and subsequent SRVCC according to the present disclosure.
  • Various embodiments of the disclosure provide systems and methods for allowing users to use multiples lines on one or more devices. For example, a single device can be used to make and/or receive communications using two or more lines and/or multiple devices can use the same line, such that a communication to the line is sent to all of the devices using that line.
  • This technology is generally referred to herein as multi-line, multi-device or MLMD technology.
  • communication networks tie a number to a user and often to a device—i.e., devices are typically locked by operators, such as telecommunication companies, to a particular number/line when a device or line is purchased, and users are generally not allowed to use any other number on the device, except by using an Over The Top (OTT) application or a device vendor native application to allow line sharing to be a native feature of the device.
  • OTT applications can make line sharing a native feature and typically require authorization for use by the operator.
  • the OTT applications or native applications work in conjunction with an operator's network to achieve the desired functionality.
  • the service logic to allow line sharing is in the network and is tied to a user's subscription.
  • the present disclosure provides exemplary multi-device, multi-line systems and methods that provide a relatively easy user experience and reduce a dependency on existing network functions to provide the desired functionality.
  • Examples of the disclosure are discussed in connection with providing various functions in connection with an IP Multimedia Core Network Subsystem (IMS) network using session-initiation-protocol (SIP).
  • IMS IP Multimedia Core Network Subsystem
  • SIP session-initiation-protocol
  • the disclosure is not limited to use with such networks and/or protocols, and to the extent compatible, can be used in connection with other communication networks, network architectures, and/or protocols.
  • FIG. 1 illustrates a network or system 100 that includes user devices or user equipment (UE) 102 - 106 (also referred to herein as devices), a portal 108 to an IP access layer 126 , a web service gateway 110 , a contact point (e.g., a P-CSCF) 112 , a proxy service node (PSN) 114 , an IMS core 116 , one or more application servers 118 , a home subscriber server (HSS) 120 , a converged database (CDB) 122 , and a provisioning system 124 .
  • UE user equipment
  • network 100 and in particular, PSN 114 and CDB 122 , allow multiple devices (e.g., devices 102 - 106 ) to have access to and use multiple lines in a relatively easy manner.
  • the line sharing service can be access and/or device agnostic, i.e., any IP access which can support IMS communication, in the illustrated example, can be used by a client and any device which has IP connectivity can use the MLMD service.
  • User devices also referred to herein as user equipment (UE), 102 - 106 can include any suitable device with wired and/or wireless communication features.
  • user devices 102 - 106 can include a wearable device, a tablet computer, a smart phone, a personal (e.g., laptop) computer, a streaming device, such as a game console or other media streaming device, such as Roku, Amazon Fire TV, or the like, a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a mobile device, a wireless device, a wireless communication device, an access terminal, a mobile terminal, a handset, a user agent, or other suitable device.
  • one or more of devices 102 - 106 includes a client.
  • client can refer to a downloadable OTT application, a native phone application, a soft phone or a browser-based client.
  • the client performs one or more client functions as described herein.
  • the client can include a user interface to display or present multiple lines available for use on a device.
  • the client can allow a user to select a line from the available lines for registration and/or use.
  • the client can also allow a user to enter account information associated with one or more lines that can be used by a network provider, such as a telecommunications company.
  • the client can allow a user to log in to access various system and method features described herein. Additional exemplary client functions are described below.
  • Portal 108 can include any suitable portal, such as a portal provided by a network (e.g., telecommunications) provider.
  • a user can use portal 108 to gain network access, register devices and/or lines, perform operations related to line sharing, and/or the like.
  • Web service gateway (WSG) 110 is a network gateway that allows one or more devices to secure network access.
  • WSG 110 can also act as an orchestrator between the operator backend systems and CDB 122 for service-related provisioning.
  • WSG handles records from provisioning system 124 and can interact with CDB 122 or another network node to provision a user to allow a user to use one or more of the MLMD features described herein.
  • WSG can receive information from provisioning system 124 and convert that information to a message format understood by CDB 122 , thereby essentially hiding CDB 122 provisioning complexities from an operator's system.
  • Exemplary WSG 110 front-end operations allow a client to create/manage devices sharing one or more lines and to activate/deactivate the line(s) on the device(s).
  • WSG 110 can also support authorization/authentication for line(s) selected by a client—e.g., in association with an operator's backend provisioning node.
  • a network contact point e.g., a P-CSCF 112 is a session-initiation-protocol (SIP) first point of contact with an IMS network.
  • SIP session-initiation-protocol
  • P-CSCF can form part of IMS core 116 .
  • PSN 114 is a network node that enables registration of multiple lines associated with a device.
  • PSN 114 can be a standalone node in the network or may be co-located with a proxy or edge node, e.g., an A-Session Border Controller (A-SBC), Proxy-CSCF (P-CSCF), or Access Transfer Control Function (ATCF) node—e.g., ATCF 128 .
  • A-SBC A-Session Border Controller
  • P-CSCF Proxy-CSCF
  • ATCF Access Transfer Control Function
  • PSN 114 is a signaling-only node; however, nothing prevents media anchoring on PSN 114 .
  • PSN 114 can function as an I-CSCF and can authorize and/or authenticate one or more lines selected by a user (e.g., using a device 102 - 106 having a suitable client). Once the lines are authorized and/or authenticated, PSN 114 communicates a register message (e.g., a REGISTER request) for each line to IMS core 116 .
  • a register message e.g., a REGISTER request
  • IMS core 116 can include typical IMS core functions, such as call session control functions.
  • IMS core 116 generally includes an interrogating CSCF (I-CSCF) node and a serving CSCF (S-CSCF) node.
  • I-CSCF interrogating CSCF
  • S-CSCF serving CSCF
  • the I-CSCF and S-CSCF described herein perform typical I-CSCF and S-CSCF functions.
  • Application servers 118 can perform a variety of functions. Application servers 118 generally interact with S-CSCF using SIP. Various application servers 118 are described in more detail below.
  • HSS 120 is a database that supports the IMS network entities that handle communications.
  • HSS 120 can contain, for example, subscription-related information, including phone numbers, billing information, on which nodes users are registered, authentication information, user identity information, and the like.
  • HSS 120 can assist IMS core 116 with routing procedures.
  • CDB 122 stores service-related data, including line-sharing information. As shared lines are added or removed, the information is stored/updated in CDB 122 . The information can be updated on CDB 122 using an operator's provisioning system to update CDB 122 . Alternatively, as noted above, WSG 110 can perform front-end operations on behalf of CDB 122 . This front-end function can, but need not be co-located with CDB 122 .
  • the service data in the CDB are accessible to application servers 118 , which are responsible for executing the service logic of the server.
  • Provisioning system 124 can be a typical operator provisioning system. Provisioning system 124 can be used to assign one or more lines to a user and/or to one or more devices. Provisioning system can use information, such as user identity, user address, and lines associated with a user. Provisioning system 124 can provision a user to, for example, WSG 110 , CDB 110 , or HSS 120 .
  • IMS Implicit Registration Set
  • HSS Home Subscriber Server
  • CSCFs Call Session Control Functions
  • AS Application Servers
  • This architecture relies on existing IMS functions and has several shortcomings.
  • One such shortcoming is that the IRS on HSS is updated whenever a user permits another user to use a line or the user revokes permissions on a shared line.
  • the IRS on the HSS is typically separate for business and personal lines for reasons related to accounting, ownership, management, and the like.
  • Exemplary systems and networks such as network 100 , include one or more CDB 122 for storing (e.g., all) service data.
  • PSN 114 is provided to authorize and optionally authenticate multiple lines associated with a user and/or device. This allows the MLMD functions described herein, without requiring changes on an HSS (e.g., HSS 120 ).
  • a client, registrar (S-CSCF) within IMS core 116 and application servers 118 support Contact bindings based on the instance-id present in a “sip.instance” parameter in the Contact header.
  • the instance-id is a globally unique value that corresponds to a device and can be based on the Information Mobile Station Equipment Identity (IMEI) of the communication device.
  • IMEI Information Mobile Station Equipment Identity
  • a user registers an IMPU (IMS Public User Identity) in the network (e.g., network 100 ).
  • Activation of a line on a device corresponds to registering the line in the network.
  • a user can be presented, via a user interface of a client on a device (e.g., device 102 , 104 , or 106 ), a list of available lines, and the user can select, using the client/user interface, which line(s) to be registered for service.
  • the client sends a SIP REGISTER request to the network (e.g., to P-CSCF 112 ).
  • the line(s) selected by the user are put in a SIP header within the REGISTER request.
  • the SIP header is referred to as a P-Multi-Line-Association header, but an existing header or a header under another name can also be expanded to achieve the same functionality.
  • P-CSCF 112 processes the request (e.g., as the P-CSCF would process a typical request), and based on presence of the SIP header carrying selected lines, forwards the request to PSN 114 .
  • One way to achieve forwarding the request is to manipulate the outgoing request just before the request is put on wire in a way so as to add a Route header pointing to PSN 114 when the P-Multi-Line-Association header is present in the REGISTER requests.
  • the logic can be built in to the P-CSCF SW or a tool/script that runs on machine hosting P-CSCF can be used.
  • This tool/scripts can intercept an outgoing SIP REGISTER message and instead of sending the message to the I-CSCF, forward the message to PSN 114 based on the information in the header.
  • this routing could be on a per SIP method basis, such that if the P-Multi-Line header is present, then an INVITE is sent to PSN 114 (but the MESSAGE requests are not sent). In this case, the initial/refresh/deregister requests for the service are handled by PSN 114 .
  • PSN 114 looks like an I-CSCF to P-CSCF 112 . PSN 114 then authorizes (and optionally authenticates) the selected lines. Post authorization/authentication, PSN 114 sends multiple REGISTER messages (one for each selected line) towards the Interrogating-CSCF (I-CSCF) 202 , illustrated in FIGS. 2 and 3 , where PSN 114 acts as the P-CSCF. Because PSN 114 does all of the mapping, mapping information correlating multiple lines need not be stored in IMS core 116 .
  • I-CSCF Interrogating-CSCF
  • An exemplary REGISTER request sent by PSN 114 has the following characteristics: the “Path” header in the request is not changed by the PSN 114 , so that subsequent terminations are directly sent to P-CSCF 112 . If PSN 114 authenticated the user, then PSN 114 adds “integrated-protected” in the Authorization header of REGISTER request to “auth-done” and thus the REGISTER request is not challenged by IMS core 116 . PSN 114 does not change the Contact header including the “sip.instance” parameter.
  • PSN 114 removes that line from the header and includes the updated header in the REGISTER directed towards IMS core 116 , so application servers 118 and IMS core 116 can access the same updated header if desired or required.
  • FIGS. 2 and 3 illustrate registration forking, where a client is registering 3 lines/IMPU (IMPU 1 , IMPU 2 and IMPU 3 ) and one of the lines (IMPU 1 ) is the AoR, and IMS core 116 uses the forked mapping.
  • This AoR in the incoming REGISTER to PSN 114 is considered as Primary Line for the purpose of service logic.
  • PSN 114 waits until all selected lines are registered (e.g., in a SCC AS for the respective lines). Each line may be served by a distinct Serving-CSCF (S-CSCF) and hence different “Service-Route” values may be received in responses.
  • S-CSCF Serving-CSCF
  • PSN 114 merges the P-Associated-URI header from all 200 OK responses and then sends a 200 OK response with the consolidated P-Associated-URI header to P-CSCF 112 .
  • P-CSCF 112 forwards the response to the client.
  • the Service-Route in the 200 OK response to P-CSCF 112 points to the S-CSCF which registered the AoR selected by the client.
  • FIG. 3 illustrates aggregation of REGISTER responses at PSN 114 .
  • the responses from I-CSCF 202 show multiple IMPUs in the P-Associated-URI header that are aggregated by PSN 114 .
  • PSN 114 maintains different bindings towards P-CSCF 112 and IMS core 116 , as shown.
  • PSN 114 does not remain in the path for any subsequent non-REGISTER requests.
  • the registration will be served by same S-CSCF and application server 118 , because due to prior registration of the same line, an S-CSCF is already assigned to such a line. In other words, all registrations of the same line in network 100 are served by the same S-CSCF and application server 118 .
  • PSN 114 is in the path for subsequent registration related signaling, while P-CSCF 112 continues to handle communications, such as voice, video and messaging sessions of the user. All the lines activated (e.g., selected for use) by the user are available for use on the device because of their presence in P-Associated-URI header in the 200 OK response.
  • the 200 OK response from PSN 114 to the P-CSCF 112 contains the PSN URI as the topmost Service-Route header followed by the URI of the S-CSCF serving the AoR. As a result, PSN 114 knows only the S-CSCFs that are serving the forked registrations.
  • P-CSCF 112 logic is configured such that it sends only the REGISTER messages to PSN 114 and the rest of the SIP requests are routed to the S-CSCF serving the AoR.
  • the service logic related to handling calls and messages is executed in application servers 118 that have access to the data stored in CDB 122 . Any change by the user or the operator affecting the service data is stored/updated in CDB 122 .
  • application server(s) 118 can fetch the service data from CDB 122 .
  • the service data can contain, for example, but is not limited to: 1) a list of lines which are eligible for service; 2) a list of users to be alerted when a call/message is received for a shared line (this allows presenting the call/message to the user who has activated a shared line; the user here corresponds to a Primary Line); and 3) a list of users (e.g., corresponding to a Primary Line) who are currently using a shared line (i.e., those users who activated one or more shared lines on their devices).
  • the client When a user who is using a shared line deactivates the line on a device (e.g., device 102 , 104 , or 106 —e.g., using a user interface), the client sends a refresh REGISTER request with only the active lines in the request. The then active lines are carried in in the same SIP header that was used in the initial registration request.
  • PSN 114 receives such a REGISTER request from P-CSCF 112 , PSN 114 compares the lines present with the lines previously registered by the client.
  • PSN 114 de-registers the line by sending a (de)REGISTER request to IMS core 116 .
  • PSN 114 sends a refresh REGISTER message to IMS core 116 .
  • the P-CSCF routes all Mobile Originated (MO) requests except REGISTER to the S-CSCF of the AoR
  • MO Mobile Originated
  • the From or P-Preferred-Identity header in an MO request contains the AoR, and the desired CLI (Calling Number) is placed in a different SIP header.
  • the S-CSCF of the AoR processes the request as usual without knowing the actual CLI.
  • the service logic in the application server 118 serving the AoR checks for the presence of the desired CLI and then replaces the From/P-Asserted-Identity header in the outgoing request with the desired CLI, and forwards the request to the IMS core so that the same can be routed to the AS serving the new CLI where all the services are applied.
  • the role of the AS serving the AoR is restricted to changing the CLI with the desired line and the actual services are provided by the AS serving the chosen CLI.
  • FIG. 4 illustrates a diagram of an exemplary mobile originated request data flow in accordance with illustrative embodiments of the disclosure.
  • the example is described in the context of a voice call; it can easily be extended to other multi-media services.
  • User-A and User-B are owners of Line 1 and Line 2 , respectively, and User-B shared Line 2 with User-A.
  • User-A activated Line 2 with Line 1 being the AoR.
  • User-A originates a call and wants to use the calling line as “Line 2 .”
  • the request is received by application server for line 1 (AS- 1 ) (e.g., one of application servers 118 ).
  • AS- 1 application server for line 1 (AS- 1 ) (e.g., one of application servers 118 ).
  • AS- 1 based on “Original Calling party” information in the request, changes the CLI to “Line 2 ” and the request is routed to application server for line 2 (AS- 2 ) (e.g., another one of application servers 118 ) through the IMS core (e.g., IMS core 116 ). Originating services are provided by AS- 2 , which can be one of application servers 118 .
  • Mobile-terminated (MT) calls or messages for a line can be routed to an AS (e.g., one or application servers 118 ) using, for example, typical IMS routing procedures over an IMS Service Control (ISC) interface.
  • an AS e.g., one or application servers 118
  • ISC IMS Service Control
  • a line may be a shared line
  • the AS uses information corresponding to devices and/or lines to which the communication should be forwarded.
  • the AS (the application server corresponding to the primary line or the AoR) obtains the line information from the CDB (e.g., CDB 122 ) and bindings for the devices from third party registrations.
  • CDB e.g., CDB 122
  • bindings for the devices from third party registrations.
  • One way to identify a device binding is from the “sip.instance” parameter in the Contact header of the embedded REGISTER request received in a third party REGISTER. This collective set of devices/line information gathered in this manner is known as
  • the SIP requests meant for that line are forwarded to the IMS core (e.g., IMS core 116 ), so as to reach the AS that is serving the user.
  • the request contains information for the other AS and User to know whether the actual called party is different from the served user indicated in the request, so that a terminating request routing is performed without applying any services for the served user (the services are applied at the AS serving the actual called party).
  • the request meant for a shared line is presented to different users who activated the line on their devices.
  • the AS serving the original called party plays the role of an anchor for terminating sessions, applying terminating services, and routing to appropriate instances of the called party, while the AS serving other lines is responsible for routing to appropriate instances of those lines but does not provide terminating services.
  • FIG. 5 illustrates a diagram of an exemplary mobile terminated request data flow.
  • the example is described in the context of a voice call; it can easily be extended to other multi-media services.
  • User-A and User-B are owners of Line 1 and Line 2 , respectively, and User-B shared Line 2 with User-A.
  • AS- 2 receives an INVITE
  • AS- 2 terminates the invite to User-B's device and also forwards the request to AS- 1 , so that User-A can also receive the request.
  • the device based on “Actual called party” (line 2 ) can, if desired, play a distinctive ring tone to let the user know that a shared line (or non-primary line) is being called.
  • MLMD communication such as a MLMD communication described above, between network types (e.g., packet-switched and circuit-switched networks).
  • SRVCC Single Radio Voice Call Continuity
  • LTE Long-Term Evolution
  • CS Circuit-Switched
  • a line used by a user for the communication can be either a native line assigned to the device or a shared line.
  • SCC AS Service Centralization and Continuity application server
  • SCC AS Service Centralization and Continuity application server
  • the SCC AS can handle the management of the access transfer of an active session according to 3GPP technical specification TS 23.237, the contents of which are incorporated herein by reference, to the extent such contents do not conflict with the present disclosure.
  • the SCC AS coordinates the proper media and signaling exchange to the access network in which the UE/device is present.
  • a Session Transfer Number (STN-SR) can be used to facilitate that coordination.
  • an HSS e.g., HSS 120
  • HSS 120 can be updated with the STN-SR and exchange SRVCC information with the Access Transfer Control Function (ATCF) at the time of registration.
  • the STN-SR is a unique identifier per subscriber and is stored in the HSS.
  • the STN-SR identifies ATCF and SRVCC information sent by SCC AS and includes its own identifier (ATU-STI).
  • ATU-STI own identifier
  • the STN-SR follows the E.164 telecommunications number format and is used by the MSC server for session transfer of the media path from the PS domain to the CS Domain.
  • the STN-SR is configured for an SRVCC subscriber at the time of service provisioning.
  • the AoR and forked registrations by PSN 114 could go to different SCC AS, which, according to standard functioning of a SCC AS, would result in multiple HSS updates and SRVCC information exchange with the ATCF.
  • the SRVCC procedure in MLMD service architecture is based on a line subscribed by the user (or the native line assigned to the UE) and not the shared line, because the native line subscription is known to the EPC network.
  • Various examples of the disclosure provide enhanced registration and call processing procedures related to MLMD service to cover SRVCC.
  • Exemplary systems and methods in accordance with the disclosure allow service continuity to be achieved through the registration path of a native line irrespective of whether the communication (e.g., voice call) involves the native line.
  • an AS of a native line is involved in any MO voice call path, even though the actual calling line preferred by the user is or may be different.
  • the Service Centralization and Continuity Application Server (SCC AS or AS) of the native line can be involved in the MT call path for Single Radio-Voice Call Continuity (SRVCC).
  • SCC AS or AS Service Centralization and Continuity Application Server
  • AoR line or AoR primary line can be involved in the MT call path for Single Radio-Voice Call Continuity (SRVCC).
  • FIG. 6 illustrates a data flow diagram of an exemplary multi-line registration request according to the present disclosure.
  • the method illustrated in FIG. 6 includes a PSN (e.g., PSN 114 ) and an SCC-AS (e.g., an application server 118 ) to enable communication handoffs between PS and CS networks.
  • the method illustrated in FIG. 6 can be performed each time a user activates or deactivates a line—e.g., using the client and methods described herein.
  • the non-primary/native lines can be automatically deactivated—e.g., each time a device is turned on or off and/or loses a connection to a network, or the non-primary/native lines can be maintained as active, until deactivated by a user using the client.
  • the process begins by using a client to register a plurality of lines (e.g., lines 1 and 2 , where line 1 is the native line—e.g., the line associated with the AoR) associated with a user device.
  • An initial communication is sent from a client (e.g., the client described above) to P-CSCF/ATCF, which forwards the communication to a PSN (e.g., PSN 114 ).
  • the PSN communicates with an IMS core (e.g., IMS core 116 ) to register each of the (e.g., selected) lines for a user device.
  • the PSN waits for each line to be registered with a respective SCC AS for each line and receives an acknowledgement (e.g., 200 OK) that the lines have been registered.
  • service logic of an application server enhances the P-Multi-Line-Association header used at the time of registration to include the native line identification, such that the native line assigned to the device is included in the header along with all permissioned lines.
  • the service logic further includes logic to avoid multiple STN-SR updates in an HSS (e.g., HSS 120 ) and SRVCC information exchange with ATCFs through a different SCC AS.
  • Enhancements in SCC AS may be made to check the P-Multi-Line-Association header (in the embedded REGISTER message) upon receiving a third party registration, and determine whether the Line/IMPU being registered is the same as the native line of the device—or not. If not, the SCC AS suppresses the STN-SR update in the HSS and sends the SRVCC information to the ATCF. The SCC AS may or may not send a failure response to the third party REGISTER.
  • initial filter criteria IFCs
  • IFCs initial filter criteria
  • the PSN when sending forked registration for shared lines, includes a parameter (in any existing or in P-Multi-Line-Association SIP header) that is validated by the IFC, and if Service Point Trigger (SPT) is matched, the third party registration to SCC AS is skipped. In this way, only the SCC AS of the native line of the device receives a third party register request from the S-CSCF.
  • a parameter in any existing or in P-Multi-Line-Association SIP header
  • SPT Service Point Trigger
  • Exemplary embodiments of the disclosure ensure that during a registration request, the HSS is updated only once for the native line of the device, and not for any shared line active on the device.
  • the STN-SR available to the MME through the HSS would identify the ATCF that would serve or anchor the voice sessions of the native line of the device.
  • This will also ensure that only one SIP MESSAGE carrying the SRVCC information is sent to the ATCF (through the PSN) when there could be potentially more than one SCC-AS involved (combined AoR and forked registration paths).
  • This can be achieved by PSN 114 replacing the ATCF URI in the path header with its own URI in the forked REGISTER messages, so that the SIP MESSAGE sent by SCC-AS is routed to PSN 114 .
  • PSN 114 then sends the SIP MESSAGE to the ATCF using the original ATCF URI that was replaced.
  • the PSN receives only one SIP MESSAGE.
  • the PSN relays the same to ATCF with no change in the SRVCC information.
  • FIG. 7 illustrates a data flow diagram of an exemplary method of handing off a communication from a PS to a CS network—e.g., from mobile originated request and subsequent SRVCC according to embodiments of the present disclosure.
  • a call can be placed using a selected line.
  • the example illustrated in FIG. 7 corresponds to a user selecting line 2 (a non-primary/native line).
  • line 1 associated with the user is used to hand over calls from the PS network to the CS network.
  • the SCC AS associates the call on line 2 with line 1 to allow the call handoff between network types.
  • the IMS core and P-CSCF/ATCF treat the communication as a communication from line 1 , until the SCC AS changes the calling party from line 1 to line 2 .
  • the communication e.g., voice call
  • any shared line on a device is anchored on SCC-AS serving the native line (the access transfer is also handled by the same SCC AS).
  • FIG. 8 illustrates a call flow diagram where a call for shared line (line 2 ) is presented to the user and later the same call is transferred to CS access.
  • an MGCF sends an INVITE to an I/S-CSCF, which then sends the request to telephony application server (TAS).
  • TAS forwards the call to SCC AS for line 1 to anchor line 1 .
  • the communication goes back to the IMS core (I/S-CSCF) and then terminates the call—e.g., using standard protocols.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Theoretical Computer Science (AREA)
  • Multimedia (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Physics & Mathematics (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Databases & Information Systems (AREA)
  • Human Computer Interaction (AREA)
  • Data Mining & Analysis (AREA)
  • Computer Security & Cryptography (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Telephonic Communication Services (AREA)
US14/992,791 2015-06-01 2016-01-11 Systems and methods for multi-line, multi-device service in a communications network Active 2036-05-14 US9906616B2 (en)

Priority Applications (3)

Application Number Priority Date Filing Date Title
US14/992,791 US9906616B2 (en) 2015-06-01 2016-01-11 Systems and methods for multi-line, multi-device service in a communications network
EP16151266.0A EP3101864B1 (de) 2015-06-01 2016-01-14 Systeme und verfahren für mehrvorrichtungsdienst mit mehreren leitungen in einem kommunikationsnetz
CA2917793A CA2917793C (en) 2015-06-01 2016-01-14 Systems and methods for multi-line, multi-device service in a communications network

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201562230318P 2015-06-01 2015-06-01
US14/992,791 US9906616B2 (en) 2015-06-01 2016-01-11 Systems and methods for multi-line, multi-device service in a communications network

Publications (2)

Publication Number Publication Date
US20160352855A1 US20160352855A1 (en) 2016-12-01
US9906616B2 true US9906616B2 (en) 2018-02-27

Family

ID=55236177

Family Applications (1)

Application Number Title Priority Date Filing Date
US14/992,791 Active 2036-05-14 US9906616B2 (en) 2015-06-01 2016-01-11 Systems and methods for multi-line, multi-device service in a communications network

Country Status (3)

Country Link
US (1) US9906616B2 (de)
EP (1) EP3101864B1 (de)
CA (1) CA2917793C (de)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180019957A1 (en) * 2016-07-18 2018-01-18 T-Mobile Usa, Inc. Rcs origination forking
US10153993B2 (en) 2016-07-18 2018-12-11 T-Mobile Usa, Inc. RCS origination forking
US11032331B2 (en) * 2017-09-21 2021-06-08 T-Mobile Usa, Inc. Batched IMS SIP registration proxy

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10904343B2 (en) 2015-07-07 2021-01-26 T-Mobile Usa, Inc. Message delivery based on subsets of network identities
WO2018104060A1 (en) * 2016-12-05 2018-06-14 Telefonaktiebolaget Lm Ericsson (Publ) Service continuity after an application server fallback
US11503453B2 (en) 2018-08-21 2022-11-15 T-Mobile Usa, Inc. Virtual line registration system

Citations (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040230697A1 (en) 2003-05-13 2004-11-18 Nokia Corporation Registrations in a communication system
US20070153776A1 (en) * 2005-12-29 2007-07-05 Joseph Gigo K Method and apparatus for routing internet telephone calls based upon the media types and formats or CODEC capabilities of the end points or destinations
US20080165942A1 (en) * 2005-03-07 2008-07-10 Fabrizio Provenzale Method and System for Call Screening
US20090055899A1 (en) 2007-08-21 2009-02-26 Qualcomm Incorporated Method and apparatus for optimization of sigcomp udvm performance
US20090191871A1 (en) 2008-01-24 2009-07-30 At&T Labs System and method of providing ims services to users on originating non ims devices and other devices that do not have a previous relationship with the user
US20090280789A1 (en) * 2005-06-01 2009-11-12 Sanyo Electric Co., Ltd. Telephone and method of controlling telephone
US20120095810A1 (en) * 2010-10-19 2012-04-19 Wen Miao Large scale privacy protected campaign mobilization method
US8369313B2 (en) 2008-12-17 2013-02-05 At&T Intellectual Property I, L.P. IMS and method of multiple S-CSCF operation in support of single PUID
US20130132854A1 (en) * 2009-01-28 2013-05-23 Headwater Partners I Llc Service Plan Design, User Interfaces, Application Programming Interfaces, and Device Management
US20160309320A1 (en) * 2015-04-14 2016-10-20 T-Mobile Usa, Inc. Multi-line mobile service with dynamic msisdn association

Patent Citations (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040230697A1 (en) 2003-05-13 2004-11-18 Nokia Corporation Registrations in a communication system
US20080165942A1 (en) * 2005-03-07 2008-07-10 Fabrizio Provenzale Method and System for Call Screening
US20090280789A1 (en) * 2005-06-01 2009-11-12 Sanyo Electric Co., Ltd. Telephone and method of controlling telephone
US20070153776A1 (en) * 2005-12-29 2007-07-05 Joseph Gigo K Method and apparatus for routing internet telephone calls based upon the media types and formats or CODEC capabilities of the end points or destinations
US20090055899A1 (en) 2007-08-21 2009-02-26 Qualcomm Incorporated Method and apparatus for optimization of sigcomp udvm performance
US20090191871A1 (en) 2008-01-24 2009-07-30 At&T Labs System and method of providing ims services to users on originating non ims devices and other devices that do not have a previous relationship with the user
US8369313B2 (en) 2008-12-17 2013-02-05 At&T Intellectual Property I, L.P. IMS and method of multiple S-CSCF operation in support of single PUID
US20130132854A1 (en) * 2009-01-28 2013-05-23 Headwater Partners I Llc Service Plan Design, User Interfaces, Application Programming Interfaces, and Device Management
US20120095810A1 (en) * 2010-10-19 2012-04-19 Wen Miao Large scale privacy protected campaign mobilization method
US20160309320A1 (en) * 2015-04-14 2016-10-20 T-Mobile Usa, Inc. Multi-line mobile service with dynamic msisdn association

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
Soroushinejad M et al"Implementing Multiple Line Appearances Using the Session Initiation Protocol"; MPEG Meeting, 3/16-23/11, Geneva.

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180019957A1 (en) * 2016-07-18 2018-01-18 T-Mobile Usa, Inc. Rcs origination forking
US10153993B2 (en) 2016-07-18 2018-12-11 T-Mobile Usa, Inc. RCS origination forking
US10237212B2 (en) * 2016-07-18 2019-03-19 T-Mobile Usa, Inc. RCS origination forking
US11032331B2 (en) * 2017-09-21 2021-06-08 T-Mobile Usa, Inc. Batched IMS SIP registration proxy

Also Published As

Publication number Publication date
CA2917793C (en) 2019-09-24
EP3101864B1 (de) 2018-08-01
EP3101864A1 (de) 2016-12-07
US20160352855A1 (en) 2016-12-01
CA2917793A1 (en) 2016-12-01

Similar Documents

Publication Publication Date Title
US9906616B2 (en) Systems and methods for multi-line, multi-device service in a communications network
US10028175B2 (en) Systems and methods for single radio voice call continuity in a multi-line, multi-device service environment in a communications network
US9906566B2 (en) Voice session termination for messaging clients in IMS
RU2584468C2 (ru) Способы и устройство для поддержки реализации непрерывности службы ims
US8953583B2 (en) Method and system for selective call forwarding based on media attributes in telecommunication network
US8918518B2 (en) Access session controller, IP multimedia subsystem and registration and session method thereof
US8634381B2 (en) Session transfer between different access network types
US8422405B2 (en) Mobile switching center platform having interfaces with functionalities defined by an architecture that provides packet-switched multimedia subscriber services
US8325707B2 (en) Session initiation from application servers in an IP multimedia subsystem
JP5425970B2 (ja) ネットワーク内サービスの移行及び活性化
JP2011526431A (ja) Ｉｍｓおよび回路交換ネットワークにおけるメッセージルーティングの方法およびシステム
CN101931923B (zh) Ip多媒体子系统网络的用户注册方法及业务实现系统
JP5805200B2 (ja) 非常サービスのための登録を維持する方法及び装置
US20130151720A1 (en) Network entity and method for managing session initiation protocol communications towards a user entity in a communication network
US10064146B2 (en) Method and system for supplementary services synchronization across networks
US9913252B2 (en) Communication system and method for multi-line, multi-device service with user capability discovery
JP6234272B2 (ja) アーリーメディアの送信タイミングを制御するセッション制御方法、ｓｉｐサーバ及びプログラム
WO2011134157A1 (zh) 个人网络元素注册方法、设备和系统
JP2013012814A (ja) セッション設定方法、設定条件管理サーバ、セッション制御ノード及び移動通信システム

Legal Events

Date Code Title Description
AS Assignment

Owner name: MITEL NETWORKS CORPORATION, CANADA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:SHARMA, ANISH;WALLIS, MICHAEL BRETT;PANKAJAKSHAN, BEJOY;SIGNING DATES FROM 20160106 TO 20160107;REEL/FRAME:037456/0559

AS Assignment

Owner name: BANK OF AMERICA, N.A. (ACTING THROUGH ITS CANADA B

Free format text: SECURITY INTEREST;ASSIGNOR:MITEL NETWORKS CORPORATION;REEL/FRAME:038056/0290

Effective date: 20160315

AS Assignment

Owner name: MITEL MOBILITY, INC., TEXAS

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MITEL NETWORKS CORPORATION;REEL/FRAME:040754/0952

Effective date: 20161222

AS Assignment

Owner name: MITEL MOBILITY INC., TEXAS

Free format text: PARTIAL RELEASE OF SECURITY INTEREST IN PATENTS;ASSIGNOR:BANK OF AMERICA, N.A.;REEL/FRAME:041868/0510

Effective date: 20170227

AS Assignment

Owner name: CERBERUS BUSINESS FINANCE, LLC, AS COLLATERAL AGEN

Free format text: GRANT OF A SECURITY INTEREST -- PATENTS;ASSIGNOR:MAVENIR SYSTEMS, INC. (F/K/A MITEL MOBILITY INC.);REEL/FRAME:041877/0881

Effective date: 20170228

AS Assignment

Owner name: MITEL NETWORKS, INC., ARIZONA

Free format text: RELEASE BY SECURED PARTY;ASSIGNORS:BANK OF AMERICA, N.A., AS COLLATERAL AGENT;BANK OF AMERICA, N.A., (ACTING THROUGH ITS CANADA BRANCH), AS CANADIAN COLLATERAL AGENT;REEL/FRAME:042244/0461

Effective date: 20170309

Owner name: MITEL COMMUNICATIONS, INC., TEXAS

Free format text: RELEASE BY SECURED PARTY;ASSIGNORS:BANK OF AMERICA, N.A., AS COLLATERAL AGENT;BANK OF AMERICA, N.A., (ACTING THROUGH ITS CANADA BRANCH), AS CANADIAN COLLATERAL AGENT;REEL/FRAME:042244/0461

Effective date: 20170309

Owner name: MITEL NETWORKS CORPORATION, CANADA

Free format text: RELEASE BY SECURED PARTY;ASSIGNORS:BANK OF AMERICA, N.A., AS COLLATERAL AGENT;BANK OF AMERICA, N.A., (ACTING THROUGH ITS CANADA BRANCH), AS CANADIAN COLLATERAL AGENT;REEL/FRAME:042244/0461

Effective date: 20170309

Owner name: MITEL (DELAWARE), INC., ARIZONA

Free format text: RELEASE BY SECURED PARTY;ASSIGNORS:BANK OF AMERICA, N.A., AS COLLATERAL AGENT;BANK OF AMERICA, N.A., (ACTING THROUGH ITS CANADA BRANCH), AS CANADIAN COLLATERAL AGENT;REEL/FRAME:042244/0461

Effective date: 20170309

Owner name: MITEL BUSINESS SYSTEMS, INC., ARIZONA

Free format text: RELEASE BY SECURED PARTY;ASSIGNORS:BANK OF AMERICA, N.A., AS COLLATERAL AGENT;BANK OF AMERICA, N.A., (ACTING THROUGH ITS CANADA BRANCH), AS CANADIAN COLLATERAL AGENT;REEL/FRAME:042244/0461

Effective date: 20170309

Owner name: MITEL US HOLDINGS, INC., ARIZONA

Free format text: RELEASE BY SECURED PARTY;ASSIGNORS:BANK OF AMERICA, N.A., AS COLLATERAL AGENT;BANK OF AMERICA, N.A., (ACTING THROUGH ITS CANADA BRANCH), AS CANADIAN COLLATERAL AGENT;REEL/FRAME:042244/0461

Effective date: 20170309

AS Assignment

Owner name: MAVENIR SYSTEMS, INC., TEXAS

Free format text: CHANGE OF NAME;ASSIGNOR:MITEL MOBILITY INC.;REEL/FRAME:042369/0185

Effective date: 20170228

STCF Information on status: patent grant

Free format text: PATENTED CASE

AS Assignment

Owner name: MAVENIR SYSTEMS, INC. (F/K/A MITEL MOBILITY INC.),

Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CERBERUS BUSINESS FINANCE, LLC, AS COLLATERAL AGENT;REEL/FRAME:045773/0100

Effective date: 20180508

AS Assignment

Owner name: GOLDMAN SACHS LENDING PARTNERS LLC, AS COLLATERAL AGENT, NEW YORK

Free format text: GRANT OF SECURITY INTEREST IN PATENTS;ASSIGNOR:MAVENIR SYSTEMS, INC.;REEL/FRAME:046139/0299

Effective date: 20180508

Owner name: GOLDMAN SACHS LENDING PARTNERS LLC, AS COLLATERAL

Free format text: GRANT OF SECURITY INTEREST IN PATENTS;ASSIGNOR:MAVENIR SYSTEMS, INC.;REEL/FRAME:046139/0299

Effective date: 20180508

AS Assignment

Owner name: T-MOBILE USA, INC., WASHINGTON

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:SEWARD, SHELBY;PISCOPO, ROBERT F., JR.;SIGNING DATES FROM 20200527 TO 20200528;REEL/FRAME:053218/0280

CC Certificate of correction
CC Certificate of correction
MAFP Maintenance fee payment

Free format text: PAYMENT OF MAINTENANCE FEE, 4TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1551); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

Year of fee payment: 4

AS Assignment

Owner name: JPMORGAN CHASE BANK, N.A., NEW YORK

Free format text: SECURITY AGREEMENT;ASSIGNOR:MAVENIR SYSTEMS, INC.;REEL/FRAME:057221/0801

Effective date: 20210818

Owner name: MAVENIR SYSTEMS, INC., TEXAS

Free format text: TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENT COLLATERAL - RELEASE OF 046139.0299;ASSIGNOR:GOLDMAN SACHS LENDING PARTNERS LLC, AS COLLATERAL AGENT;REEL/FRAME:057222/0398

Effective date: 20210818

AS Assignment

Owner name: JPMORGAN CHASE BANK, N.A., NEW YORK

Free format text: SECURITY AGREEMENT;ASSIGNOR:MAVENIR SYSTEMS, INC.;REEL/FRAME:060641/0242

Effective date: 20220712

AS Assignment

Owner name: WILMINGTON SAVINGS FUND SOCIETY, FSB, DELAWARE

Free format text: SECURITY INTEREST;ASSIGNOR:MAVENIR SYSTEMS, INC.;REEL/FRAME:067565/0678

Effective date: 20240529