C2MS 1.0 FTF Avatar
  1. OMG Issue

C2MS — Flatten the message hierarchy re: C2CX, TLM, and NDM messages

  • Key: C2MS-23
  • Status: closed  
  • Source: NASA ( Mr. John Bugenhagen)
  • Summary:

    There is an intermediate sub-layer that is not needed in the C2CX, TLM, and NDM messages that makes common processing more difficult. I suggest removing the sub-layer so that all messages are uniquely identifiable by their type and sub-type.

    For example, heartbeat messages are currently categorized like this:
    type - MSG
    subtype - C2CX
    c2cx-subtype - HB

    I suggest there is no need for the C2CX layer. it should be like this:
    type - MSG
    subtype - HB

    Similarly for other C2CX messages, TLM messages, and NDM messages.

  • Reported: C2MS 1.0b1 — Tue, 18 Sep 2018 19:14 GMT
  • Disposition: Resolved — C2MS 1.0
  • Disposition Summary:

    C2CX and TLM messages were done; NDMs require more thought

    C2CX Messages:

    • re-organized section 8.5 to match other message sections
    • made all messages have a unique MESSAGE-SUBTYPE value (CFG, CNTL, DEV, HB, RSRC)
    • removed C2CX-SUBTYPE field from all messages

    TLM Messages:

    • re-organized section 8.6 to match other message sections
    • made all messages have a unique MESSAGE-SUBTYPE value (TLMFRAME, TLMPKT, TLMPROC, TLMTDM)
    • removed FORMAT field from all messages

    Updated table 6-6 to remove the row (2 cells) that shows C2CX as a Subtype value "C2CX | Component-to-Component Transfer"

    NDM Messages:
    Not flattened because the NDM-TYPE field is not fixed for the sub messages. For example, for AEM messages the value is CCSDS-AEM or AEM. Therefore, to flatten it out would require addition of 6 new messages - deemed out of scope for this revision.

  • Updated: Tue, 8 Oct 2019 17:51 GMT
  • Attachments: