Non-IMS Rich Communication Suite
1 Assignment
0 Petitions
Accused Products
Abstract
This invention relates to telecommunications, and in particular, to a Rich Communication Suite (RCS) and RCS-e (“e” for enhanced) messaging infrastructure within a network without the need to deploy an IP Multimedia Subsystem (IMS) core within the network.
58 Citations
5 Claims
-
1. (canceled)
-
2. (canceled)
-
3. A method for delivering messages between a legacy messaging client and an RCS client, comprising the steps of:
-
a. Step 401. Subscriber 1 uses a traditional messaging client to send an SMDPP message to the SMSC for delivery to Subscriber 2. b. Step 402. SMSC forwards an SMPP message to the PCG for delivery. c. Step 403. PCG assigns a mapping of the MISDN to one of its RCS client proxy. d. Step 404. PCG sends an INVITE to the CN (acting as the CSCF) to request an RCS session with Subscriber 2. e. Step 405. CN queries the SRDB to determine if the target handset is RCS capable. (This data is populated per the registration call flow above.) f. Step 406. Once the target handset is deemed RCS capable, an HLR query (or other external system as necessary) is performed to authenticate both the invitee and invited parties. g. Step 407. Assuming both queries are validated, the CN forwards the INVITE to Subscriber 2. h. Step 408. Subscriber 2'"'"'s RCS client issues an ACCEPT message to the CN. i. Step 409. CN issues a CREATE SESSION command to the SC. j. Step 410. SC issues an ACCEPT message back to the CN. k. Step 411. CN forwards ACCEPT message to PCG. l. Step 412. Subscriber 2 and PCG communicate over MRSP via the SC, which are then forwarded over SMPP to the SMSC for delivery to Subscriber 1. - View Dependent Claims (5)
-
-
4. (canceled)
Specification