Open APIs

 View Only

  • 1.  TMF 681 Communication API - CREATE Notification & SEND two operations

    Posted Sep 03, 2019 09:32
    Edited by Rabinder Devnani Sep 04, 2019 04:28
    Hi,

    Was going through "TMF681_Communication_API_REST_Specification_R18.0.1" and found that there are 2 API operations for Communications API i.e. 
    "POST /communicationMessage" & "POST /communicationMessage/send". I want to understand requirement of creating 2 separate operations and not using only "send" operation to save the message and send to the receiver Related Party in a single operation?

    I am assuming that operations "POST /communicationMessage" & "POST /communicationMessage/{ID}/send" are used in conjunction first to create CommunicationMessage and then to send the created one.

    Does it relate to scheduled notifications with "SendTime" in future?

    @Ludovic Robert & @Jonathan Goldberg your thoughts?    ​​

    ------------------------------
    Rabinder Devnani
    Sterlite Technologies Limited
    ------------------------------


  • 2.  RE: TMF 681 Communication API - CREATE Notification & SEND two operations

    Posted Sep 04, 2019 04:25
    Hello,

    + @Knut Johannessen ​ who took the lead on this API.

    Best regards

    Ludovic
    ​

    ------------------------------
    Ludovic Robert
    Orange
    ------------------------------



  • 3.  RE: TMF 681 Communication API - CREATE Notification & SEND two operations

    Posted Sep 04, 2019 08:40
    The API supports two modes: 
    - prepare and later mark for sending (in two operations)
    - submit and mark for sending in a single operation

    This reflects the business requirements that have been a basis for the work.

    The use of sendTime is to my understanding independent of the above.

    For information, in the ongoing work on 19.5 it is considered to consolidate in one operation and to include a new boolean property "readyToSend" (or similar). Again, the use of sendTime is independent of this.

    ------------------------------
    Knut Johannessen
    Telenor ASA
    ------------------------------

    Original Message


  • 4.  RE: TMF 681 Communication API - CREATE Notification & SEND two operations

    Posted Sep 04, 2019 09:05
    Ok Kunt, thanks for clarity.

    So sendTime is used for scheduling purposes ? If not then, should we introduce other parameter to schedule the delivery of the message in future?

    ------------------------------
    Rabinder Devnani
    Sterlite Technologies Limited
    ------------------------------

    Original Message


  • 5.  RE: TMF 681 Communication API - CREATE Notification & SEND two operations

    Posted Sep 04, 2019 12:55
    ​Yeah , the original sendTime attribute is not for scheduling purposes. I think it's a good idea to introduce a new parameter.

    ------------------------------
    Hongxia Hao
    Huawei Technologies Co. Ltd
    ------------------------------

    Original Message


  • 6.  RE: TMF 681 Communication API - CREATE Notification & SEND two operations

    Posted Sep 05, 2019 02:46
    Edited by Rabinder Devnani Oct 15, 2019 02:56
    Hi @Hongxia Hao,

    Ok, so it just represents when the message was sent rather than when to send. I think it is good to introduce a new parameters for scheduling the messages in cases where customer chooses time when to be notified or contacted for different purposes, or according to the telco policy the customers should be sent promotions during the day only or if we have a promotion messages to be scheduled at a particular time to be sent to concerned parties (although this can be driven by scheduling the campaign as well), etc.

    @Knut Johannessen , whats your thought?

    ​​​

    ------------------------------
    Rabinder Devnani
    Sterlite Technologies Limited
    ------------------------------

    Original Message


Related Content