Rich communication services multicast system
An improved telecommunications network that can reduce the network load on a rich communication services (RCS) server and/or local routers that implement 1-to-N and/or M-to-N services is described herein. In particular, the improved telecommunications network may include an improved RCS server that can route multicast messages instead of and/or in addition to unicast messages. For example, the improved RCS server can create a multicast group for a group of UEs in response to a request from a UE to create a group of UEs. Creation of the multicast group may include assigning a group Internet protocol (IP) address to the multicast group. The improved RCS server can then determine which UEs in the multicast group are capable of sending and/or receiving multicast messages, and send multicast messages instead of unicast messages to these UEs.
1. A computer-implemented method comprising:
obtaining, from a first user equipment (UE), a request to create a multicast group, wherein the request comprises an indication that the first UE, a second UE, and a third UE are to be members of the multicast group;
validating that the first UE, the second UE, and the third UE are registered with a telecommunications network;
assigning an address to the multicast group;
determining that the first UE and the second UE are capable of handling multicast messages;
determining that the third UE is incapable of handling multicast messages;
transmitting a multicast invite message to the first UE and the second UE, wherein reception of the multicast invite message causes the first UE and the second UE to join the multicast group; and
transmitting a unicast invite message to the third UE, wherein reception of the unicast invite message causes the third UE to join the multicast group, such that a message intended for the multicast group is transmitted as a multicast message to the first UE and the second UE and as a unicast message to the third UE;
wherein the computer-implemented method is implemented by a rich communication services (RCS) system comprising physical hardware and operating in a core network of the telecommunications network.
2. The computer-implemented method of claim 1 , wherein determining that the first UE and the second UE are capable of handling multicast messages further comprises:
transmitting a first session initiation protocol (SIP) option message to the first UE, wherein the first SIP option message comprises a contact parameter;
receiving, in response to the first SIP option message, a first 200 OK message that comprises the contact parameter;
transmitting a second SIP option message to the second UE, wherein the second SIP option message comprises the contact parameter; and
receiving, in response to the second SIP option message, a second 200 OK message that comprises the contact parameter.
3. The computer-implemented method of claim 1 , wherein determining that the third UE is incapable of handling multicast messages further comprises:
transmitting a session initiation protocol (SIP) option message to the third UE, wherein the SIP option message comprises a contact parameter; and
receiving, in response to the SIP option message, a 200 OK message that does not comprise the contact parameter.
4. The computer-implemented method of claim 1 , further comprising:
receiving, from the first UE in response to the multicast invite message, a first acknowledgement message that comprises the address assigned to the multicast group; and
receiving, from the third UE in response to the unicast invite message, a second acknowledgement message that comprises an address of the third UE.
5. The computer-implemented method of claim 1 , further comprising:
determining that the third UE is now capable of handling multicast messages; and
transmitting a second multicast invite message to the third UE such that a second message intended for the multicast group is transmitted as a second multicast message to the third UE instead of as a second unicast message.
6. Non-transitory, computer-readable storage media comprising computer-executable instructions, wherein the computer-executable instructions, when executed by a computer system, cause the computer system to:
obtain, from a first user equipment (UE), a request to create a multicast group, wherein the request comprises an indication that the first UE, a second UE, and a third UE are to be members of the multicast group;
assign an address to the multicast group;
determine that the first UE and the second UE are capable of handling multicast messages;
determine that the third UE is incapable of handling multicast messages;
transmit a multicast invite message to the first UE and the second UE, wherein reception of the multicast invite message causes the first UE and the second UE to join the multicast group; and
transmit a unicast invite message to the third UE, wherein reception of the unicast invite message causes the third UE to join the multicast group, such that a message intended for the multicast group is transmitted as a multicast message to the first UE and the second UE and as a unicast message to the third UE.
7. The non-transitory, computer-readable storage media of claim 6 , wherein the computer-executable instructions further cause the computer system to:
transmit a first session initiation protocol (SIP) option message to the first UE, wherein the first SIP option message comprises a contact parameter;
process a first 200 OK message received from the first UE that comprises the contact parameter;
transmit a second SIP option message to the second UE, wherein the second SIP option message comprises the contact parameter; and
process a second 200 OK message received from the second UE that comprises the contact parameter.
8. The non-transitory, computer-readable storage media of claim 6 , wherein the computer-executable instructions further cause the computer system to:
transmit a session initiation protocol (SIP) option message to the third UE, wherein the SIP option message comprises a contact parameter; and
process a 200 OK message received from the third UE that does not comprise the contact parameter.
9. The non-transitory, computer-readable storage media of claim 6 , wherein the computer-executable instructions further cause the computer system to:
process a first acknowledgement message received from the first UE in response to the multicast invite message, wherein the first acknowledgement message comprises the address assigned to the multicast group; and
process a second acknowledgement message received from the third UE in response to the unicast invite message, wherein the second acknowledgement message comprises an address of the third UE.
10. The non-transitory, computer-readable storage media of claim 6 , wherein the computer-executable instructions further cause the computer system to:
determine that the third UE is now capable of handling multicast messages; and
transmit a second multicast invite message to the third UE such that a second message intended for the multicast group is transmitted as a second multicast message to the third UE instead of as a second unicast message.
11. The non-transitory, computer-readable storage media of claim 6 , wherein a first multicast router is local to the first UE and the second UE.
12. The non-transitory, computer-readable storage media of claim 11 , wherein the computer-executable instructions further cause the computer system to:
process a second message transmitted by the third UE, wherein the second message comprises the address of the multicast group in a destination field;
generate a second multicast message using the second message transmitted by the third UE; and
transmit a single copy of the second multicast message for reception by the first multicast router, wherein reception of the second multicast message causes the first multicast router to transmit the second multicast message to the first UE and to the second UE.
13. The non-transitory, computer-readable storage media of claim 11 , wherein reception of the multicast invite message causes the first UE to invite the first multicast router to join the multicast group.
14. A core network comprising:
a multicast router rendezvous point; and
a rich communication services (RCS) system comprising a processor in communication with the multicast router rendezvous point and configured with specific computer-executable instructions to:
obtain, from a first user equipment (UE), a request to create a multicast group, wherein the request comprises an indication that the first UE, a second UE, and a third UE are to be members of the multicast group;
assign an address to the multicast group;
cause the multicast router rendezvous point to join the multicast group;
determine that the first UE and the second UE are capable of handling multicast messages;
determine that the third UE is incapable of handling multicast messages;
transmit a multicast invite message to the first UE and the second UE, wherein reception of the multicast invite message causes the first UE and the second UE to join the multicast group; and
transmit a unicast invite message to the third UE, wherein reception of the unicast invite message causes the third UE to join the multicast group, such that a message intended for the multicast group is transmitted as a multicast message to the first UE and the second UE and as a unicast message to the third UE.
15. The core network of claim 14 , wherein the RCS system is further configured with specific computer-executable instructions to:
transmit a first session initiation protocol (SIP) option message to the first UE, wherein the first SIP option message comprises a contact parameter;
process a first 200 OK message received from the first UE that comprises the contact parameter;
transmit a second SIP option message to the second UE, wherein the second SIP option message comprises the contact parameter; and
process a second 200 OK message received from the second UE that comprises the contact parameter.
16. The core network of claim 14 , wherein the RCS system is further configured with specific computer-executable instructions to:
transmit a session initiation protocol (SIP) option message to the third UE, wherein the SIP option message comprises a contact parameter; and
process a 200 OK message received from the third UE that does not comprise the contact parameter.
17. The core network of claim 14 , wherein the RCS system is further configured with specific computer-executable instructions to:
process a first acknowledgement message received from the first UE in response to the multicast invite message, wherein the first acknowledgement message comprises the address assigned to the multicast group; and
process a second acknowledgement message received from the third UE in response to the unicast invite message, wherein the second acknowledgement message comprises an address of the third UE.
18. The core network of claim 14 , wherein the RCS system is further configured with specific computer-executable instructions to:
determine that the third UE is now capable of handling multicast messages; and
transmit a second multicast invite message to the third UE such that a second message intended for the multicast group is transmitted as a second multicast message to the third UE instead of as a second unicast message.
19. The core network of claim 18 , wherein a first multicast router is local to the first UE and the second UE.
20. The core network of claim 18 , wherein the RCS system is further configured with specific computer-executable instructions to:
process a second message transmitted by the third UE via the multicast router rendezvous point, wherein the second message comprises the address of the multicast group in a destination field;
generate a second multicast message using the second message transmitted by the third UE; and
transmit a single copy of the second multicast message for reception by the first multicast router via the multicast router rendezvous point, wherein reception of the second multicast message causes the first multicast router to transmit the second multicast message to the first UE and to the second UE.