×

Non-IMS rich communication suite

  • US 9,549,073 B2
  • Filed: 06/24/2014
  • Issued: 01/17/2017
  • Est. Priority Date: 10/07/2011
  • Status: Active Grant
First Claim
Patent Images

1. A method for delivering messages between a legacy messaging client and a Rich Communication Suite (RCS) client in a non-IMS RCS telecommunication system comprising four logical entities, the first logical entity is a session controller (SC), the second logical entity is a control node (CN), the third logical entity is a Protocol Conversion Gateway (PCG), and the fourth logical entity is a subscriber and routing database (SRDB);

  • said logical entities function in operative association with a telecommunication network having a plurality of user agents, a home location register (HLR) and one or more legacy controllers selected from a short messaging service center (SMSC) and a multimedia messaging service center (MMSC) to transmit messages from a First Subscriber to a Second Subscriber over the telecommunication network, comprising the steps of;

    Sending from a First Subscriber using a legacy messaging client a Short Message Delivery Point-to-Point Bearer Service (SMDPP protocol) message to a Short Messaging Service Center (SMSC) for delivery to a Second Subscriber;

    Forwarding from the SMSC a Short Message Peer-to-Peer (SMPP protocol) message to said PCG for delivery;

    Assigning a mapping by the PCG of the Modular Integrated Services Digital Network (MISDN) to a RCS client proxy;

    Sending from the PCG an INVITE to said Control Node (CN) acting as a Call Session Control Function (CSCF) to request an RCS session with the Second Subscriber;

    Querying by the CN of the SRDB to determine if the Second Subscriber'"'"'s target handset is RCS capable of having an RCS client, wherein SRDB data is populated by prior registration call flow;

    Querying said HLR if the Second Subscriber'"'"'s target handset is RCS capable to authenticate both the First Subscriber and the Second Subscriber;

    Forwarding the INVITE to the Second Subscriber once the HLR Query authenticates the First Subscriber and the Second Subscriber;

    Sending from the PCG acting as an RCS client of the Second Subscriber an ACCEPT message to the CN;

    Sending from the CN a CREATE SESSION command to the Session Controller (SC);

    Sending from the SC an ACCEPT message back to the CN;

    Forwarding from the CN the ACCEPT message to the PCG;

    Sending one or more communications between the Second Subscriber and the PCG over Message Session Relay Protocol (MSRP) via the SC;

    Forwarding said one or more communications over SMPP to the SMSC for delivery to the First Subscriber;

    the steps are performed on the non-IMS RCS telecommunications system, said logical entities, the telecommunication network, and subscriber devices having programming instructions saved to non-transitory storage media and executed on processors for performing the method;

    the PCG handles conversion of one or more communications from legacy Signalling System 7 (SS7), SMPP, or MM4/MM7 traffic (Multimedia Messaging interface 4, MM4) (Multimedia Messaging interface 7, MM7) to RCS/SIP/MSRP (Session Initiation Protocol, SIP) for delivery from SMSCs and/or MMSCs;

    the PCG acts as an RCS client to the SC and as an Extended Short Messaging Entity (ESME) to legacy SMSC/MMSC infrastructure;

    the SC is responsible for the set up and control of MSRP sessions in the non-IMS RCS telecommunications system;

    the CN handles one or more signaling interfaces, including both SIP and SS7, necessary to handle registration, session set up, and subscriber authentication;

    the CN acts in the non-IMS RCS telecommunications system as both a proxy call session control function (P-CSCF) and a serving call session control function (S-CSCF);

    the CN acts as an application controller for RCS; and

    the SRDB acts as a home subscriber server (HSS) in the non-IMS RCS telecommunications system and holds individual handset capability information garnered in the registration process, and any operator- or handset-specific routing information.

View all claims
  • 1 Assignment
Timeline View
Assignment View
    ×
    ×