Content for  TS 33.128  Word version:  18.6.0

The IRI-POI present in the RCS Servers shall send xIRI over LI_X2 for the events listed in clause 7.13.4 of TS 33.127, the details of which are described in the following clauses. If the RCS implementation uses protocols other than SIP and MSRP, alternative triggers may be used such that the IRI-POI in the RCS Server generates appropriate xIRIs for the events listed in clause 7.13.4 of TS 33.127.

The xIRI containing an RCSRegistration record shall be generated when the IRI-POI in the S-CSCF or in an RCS Server detects that an RCS target matching one of the RCS identifiers, provided via LI_X1 has registered, reregistered or deregistered for RCS services. Accordingly, the IRI-POI in the RCS Server generates the xIRI when the following event is detected:

• When the IRI-POI is located in the S-CSCF:
  • If the S-CSCF uses third-party registrations to notify the RCS Server when a UE registers, when the S-CSCF receives a 200 OK from the RCS Server in response to a third-party SIP REGISTER request registering, reregistering or deregistering a target with the RCS Server.
  • If the S-CSCF is the NF responsible for handling RCS Registrations:
    • When the S-CSCF sends a 200 OK to a target in response to a SIP REGISTER request that includes any of the service feature tags listed in GSMA RCC.07 [78] clause 2.4.3, clause 2.4.4 or clause 2.4.4.1 Table 3.
    • When the S-CSCF sends a 200 OK to a target in response to a SIP REGISTER request for deregistration when the service features supported by the target include any of the service features listed in GSMA RCC.07 [78] clause 2.4.3, clause 2.4.4 or clause 2.4.4.1 Table 3.
• When the IRI-POI is located in the RCS Server:
  • When the RCS Server sends a 200 OK to a target in response to a SIP REGISTER request that includes any of the service feature tags listed in GSMA RCC.07 [78] clause 2.4.3, clause 2.4.4 or clause 2.4.4.1 Table 3.
  • When the RCS Server sends a 200 OK to a target in response to a SIP REGISTER request for deregistration when the service features supported by the target include any of the service features listed in GSMA RCC.07 [78] clause 2.4.3, clause 2.4.4 or clause 2.4.4.1 Table 3.
  • When the RCS server sends a 200 OK to the S-CSCF in response to a SIP NOTIFY request for a target with an Event header field with a value set to "reg" as specified in clauses 5.1.1.3 and 5.1.1.7 of TS 24.229.

The IRI-POI present in the RCS Server shall generate an xIRI containing an RCSMessage record when the IRI-POI present in the RCS Server detects that an RCS target has sent or received an RCS message. In this specification, an RCS message refers to any message sent or received in the context of pager mode standalone messaging, large message mode messaging, 1-to-1 chat or group chat. This xIRI is also generated when the target sends or receives a delivery notification or display notification. Accordingly, the IRI-POI in the RCS Server shall generate the RCSMessage xIRI when it detects the following events:

• The RCS Server receives a SIP MESSAGE from the target or destined to the target, determined by the direction attribute present in the CPM Header, and:
  • The "Contact" or "Accept-Contact" header includes a service feature tag among the feature tags listed in GSMA RCC.07 [78] clause 2.4.4.1 Table 3.
  • The SIP "Content-Type" header is "message/cpim".
• The RCS Server receives an MSRP packet from the target or destined to the target and:
  • The content of the MSRP packet is a CPIM (Common Presence and Instant Messaging) object (see definition in RFC 3862).