Method and apparatus for transmitting a mission critical data message in a communication system

Abstract

Embodiments herein disclose formats for MCData messages and notifications, and methods for coding (encoding and decoding) MCData messages and notifications in a MCData communication system. The method includes generating, by a first UE, an encoded MCData message or notification comprising of signaling payload and data payload content related to one or more MCData user payloads. Further the method includes deriving, by a second UE, the actual MCData messages or notifications by decoding the received encoded MCData messages or notifications. The formats for MCData messages and MCData notifications optimize control headers and allow maximum user data size that can be carried in a single message over signalling, which aids in sending multiple user payloads in a single message.

The invention claimed is: 
     
       1. A method for transmitting a mission critical data (MCData) message by a user equipment (UE) in a communication system, comprising:
 generating an MCData message including signalling content related to an MCData payload; and 
 transmitting the MCData message to one or more UEs, 
 wherein the signalling content includes a signalling payload message identity information element to identify a type of the MCData message, a date and time information element, a conversation identifier (ID) information element to identify a conversation, and a message ID information element to identify the MCData a message within the conversation, 
 wherein the signalling payload message identity information is information with element has a length of 1 octet, the date and time information is information with element has a length of 5 octets, the conversation ID information is information with element has a length of 16 octets, and the message ID information is information with element has a length of 16 octets, and 
 wherein each of the signalling payload message identity information element, the date and time information element, the conversation ID information element, and the message ID information has element is associated with a type-length-value (TLV) format including related to a value part without a type part and a length part only. 
 
     
     
       2. The method  claim 1 , wherein the MCData payload is a short data service (SDS) data payload, the MCData message is an SDS signalling payload message, and the signalling content further includes at least one of:
 an In-Reply-to message ID information usedelement to associate the MCData message within the conversation that is a reply to an existing MCData message in the conversation, 
 an application ID information element to identify an application for which the SDS data payload is intended, and 
 an SDS disposition request type information element to identify a type of an SDS disposition notification requested. 
 
     
     
       3. The method  claim 1 , wherein the MCData payload is a file distribution (FD) data payload, the MCData message is an FD signalling payload message, and the signalling content further includes at least one of:
 an In-Reply-to message ID information usedelement to associate the MCData message within the conversation that is a reply to an existing MCData message in the conversation, 
 an application ID information element to identify an application for which the FD data payload is intended, 
 an FD disposition request type information element to indicateidentify a type of an FD disposition notification requested, 
 a mandatory download information element to indicateinform that it is mandatory to download a file, 
 a payload information element containing a URL pointing to the filepayload intended for a recipient user or application, and 
 a metadata information element containing data used to describe the file. 
 
     
     
       4. A method for transmitting a mission critical data (MCData) message by a user equipment (UE) in a communication system, the method comprising:
 generating an MCData message including signalling content related to an MCData payload; and 
 transmitting the MCData message to one or more UEs, 
 wherein the signalling content includes signalling payload message identity information to identify a type of the MCData message, date and time information, conversation identifier (ID) information to identify a conversation, and message ID information to identify the MCData message, 
 wherein the MCData payload is a file distribution (FD) data payload, the MCData message is an FD signalling payload message, and the signalling content further includes at least one of: 
 In-Reply-to message ID information used to associate the MCData message within the conversation that is a reply to an existing MCData message in the conversation, 
 application ID information to identify an application for which the FD data payload is intended, 
 FD disposition request type information to indicate a type of an FD disposition notification requested, 
 mandatory download information to indicate that it is mandatory to download a file, 
 payload information containing a URL pointing to the file, and 
 metadata information containing data used to describe the file,The method of claim 3, 
 wherein the FD disposition request type information is information with element has a length of 1 octet, the application ID information is information with element has a length of 2 octets, the In-Reply-to message ID information is information with element has a length of 17 octets, the mandatory download information is information with element has a length of 1 octet, 
 wherein each of the In-Reply-to message ID information element, the application ID information element, the FD disposition request type information element, and the mandatory download information has element is associated with a (TLV) format including related to a type part and a value part without a length part, and 
 wherein each of the metadata information element and the payload information has a element is associated with the TLV format including the related to a type part, the a length part, and the a value part. 
 
     
     
       5. A user equipment (UE) in a communication system, comprising:
 a transceiver; and 
 at least one processor configured to:
 generate a mission critical data (MCData) message including signalling content related to an MCData payload, and 
 control the transceiver to transmit the MCData message to one or more UEs, 
 
 wherein the signalling content includes a signalling payload message identity information element to identify a type of the MCData message, a date and time information element, a conversation identifier (ID) information element to identify a conversation, and a message ID information element to identify the MCData a message within the conversation, 
 wherein the signalling payload message identity information is information with element has a length of 1 octet, the date and time information is information with element has a length of 5 octets, the conversation ID information is information with element has a length of 16 octets, and the message ID information is information with element has a length of 16 octets, and 
 wherein each of the signalling payload message identity information element, the date and time information element, the conversation ID information element, and the message ID information has element is associated with a type-length-value (TLV) format including related to a value part without a type part and a length part only. 
 
     
     
       6. The UE  claim 5 , wherein the MCData payload is a short data service (SDS) data payload, the MCData message is an SDS signalling payload message for providing signalling content related to an SDS data payload, and the signalling content further includes at least one of:
 an In-Reply-to message ID information usedelement to associate the MCData message within the conversation that is a reply to an existing MCData message in the conversation, 
 an application ID information element to identify an application for which the SDS data payload is intended, and 
 an SDS disposition request type information element to identify a type of an SDS disposition notification requested. 
 
     
     
       7. The UE  claim 5 , wherein the MCData payload is a file distribution (FD) data payload, the MCData message is an FD signalling payload message for providing signalling content related to an FD data payload, and the signalling content further includes at least one of:
 an In-Reply-to message ID information usedelement to associate the MCData message within the conversation that is a reply to an existing MCData message in the conversation, 
 an application ID information element to identify an application for which the FD data payload is intended, 
 an FD disposition request type information element to indicateidentify a type of an FD disposition notification requested, 
 a mandatory download information element to indicateinform that it is mandatory to download a file, 
 a payload information element containing a URL pointing to the filepayload intended for a recipient user or application, and 
 a metadata information element containing data used to describe the file. 
 
     
     
       8. A user equipment (UE) in a communication system, comprising:
 a transceiver; and 
 at least one processor configured to:
 generate a mission critical data (MCData) message including signalling content related to an MCData payload, and 
 control the transceiver to transmit the MCData message to one or more UEs, 
 
 wherein the signalling content includes signalling payload message identity information to identify a type of the MCData message, date and time information, conversation identifier (ID) information to identify a conversation, and message ID information to identify the MCData message, 
 wherein the MCData payload is a file distribution (FD) data payload, the MCData message is an FD signalling payload message for providing signalling content related to an FD data payload, and the signalling content further includes at least one of: 
 In-Reply-to message ID information used to associate the MCData message within the conversation that is a reply to an existing MCData message in the conversation, 
 application ID information to identify an application for which the FD data payload is intended, 
 FD disposition request type information to indicate a type of an FD disposition notification requested, 
 mandatory download information to indicate that it is mandatory to download a file, 
 payload information containing a URL pointing to the file, and 
 metadata information containing data used to describe the file, The UE of claim 5, 
 wherein the FD disposition request type information is information with element has a length of 1 octet, the application ID information is information with element has a length of 2 octets, the In-Reply-to message ID information is information with element has a length of 17 octets, and the mandatory download information is information with element has a length of 1 octet, 
 wherein each of the In-Reply-to message ID information element, the application ID information element, the FD disposition request type information element, and the mandatory download information has element is associated with a (TLV) format including related to a type part and a value part without a length part, and 
 wherein each of the metadata information element and the payload information has a element is associated with the TLV format including the a type part, the a length part, and the a value part. 
 
     
     
       9. A user equipment (UE) in a communication system, comprising:
 a transceiver; and   at least one processor configured to:
 generate a mission critical data (MCData) message including signalling content related to an MCData payload, and 
 control the transceiver to transmit the MCData message to one or more UEs, 
   wherein the signalling content includes signalling payload message identity information to identify a type of the MCData message, date and time information, conversation identifier (ID) information to identify a conversation, and message ID information to identify the MCData message,   wherein the MCData payload is a short data service (SDS) data payload, the MCData message is an SDS signalling payload message for providing signalling content related to an SDS data payload, and the signaling content further includes at least one of:   In-Reply-to message ID information used to associate the MCData message within the conversation that is a reply to an existing MCData message in the conversation,   application ID information to identify an application for which the SDS data payload is intended, and   SDS disposition request type information to identify a type of an SDS disposition notification requested,   wherein the In-Reply-to message ID information is information with a length of 17 octets, the application ID information is information with a length of 2 octets, and the SDS disposition request type information is information with a length of 1 octet, and   wherein each of the In-Reply-to message ID information, the application ID information, and the SDS disposition request type information has a format including a type part and a value part without a length part.   
     
     
       10. The UE of  claim 5 , wherein the at least one processor is further configured to control the transceiver to transmit a data payload message to the one or more UEs when transmitting the MCData payload, and
 wherein the data payload message includes data payload message identity information to identify a type of the data payload message, number of payloads information to identify a number of payloads included in the data payload message, and payload information including payload data.   
     
     
       11. A method for transmitting a mission critical data (MCData) message by a user equipment (UE) in a communication system, the method comprising:
 generating an MCData message including signalling content related to an MCData payload; and   transmitting the MCData message to one or more UEs,   wherein the signalling content includes signalling payload message identity information to identify a type of the MCData message, date and time information, conversation identifier (ID) information to identify a conversation, and message ID information to identify the MCData message,   wherein the MCData payload is a short data service (SDS) data payload, the MCData message is an SDS signalling payload message, and the signalling content further includes at least one of:   In-Reply-to message ID information used to associate the MCData message within the conversation that is a reply to an existing MCData message in the conversation,   application ID information to identity an application for which the SDS data payload is intended, and   SDS disposition request type information to identify a type of an SDS disposition notification requested,   wherein the In-Reply-to message ID information is information with a length of 17 octets, the application ID information is information with a length of 2 octets, and the SDS disposition request type information is information with a length of 1 octet, and   wherein each of the In-Reply-to message ID information, the application ID information and the SDS disposition request type information has a type-length-value (TLV) format including a type part and a value part without a length part.   
     
     
       12. The method of  claim 1 , further comprising transmitting a data payload message to the one or more UEs when transmitting the MCData payload,
 wherein the data payload message includes data payload message identity information to identify a type of the data payload message, number of payloads information to identify a number of payloads included in the data payload message, and payload information including payload data.   
     
     
       13. A method for sending a mission critical data (MCData) message by a user equipment (UE) in a communication system, the method comprising:
 identifying at least one of a short message data service (SDS) for sharing data with one or more UEs or a file distribution (FD) service for sharing a file with the one or more UEs for an MCData service;   setting a first message type information element to identify a message type as an SDS signaling payload message in a first field of the MCData message in case that the MCData service is the SDS, and setting a second message type information element to identify a message type as an FD signaling payload message in the first field of the MCData message in case that the MCData service is the FD service, wherein the message type information element and the second message type information element are associated with a first format with a length of 1 octet;   setting a first date and time information element to indicate a time associated with a transmission of a message in a second field of the MCData message in case that the MCData service is the SDS, and setting a second date and time information element to indicate a time associated with a transmission of a file in the second field of the MCData message in case that the MCData service is the FD service, wherein the first date and time information element and the second date and time information element are associated with the first format with a length of 5 octet:   setting a conversation identifier (ID) information element to identify a conversation in a third field of the MCData message, wherein the conversation ID information element is associated with the first format with a length of 16 octet;   setting a message ID information element to identify a message within the conversation in a fourth field of the MCData message, wherein the message ID information element is associated with the first format with a length of 16 octet; and   sending, to the one or more UEs, the MCData message including the first field, the second field, the third field, and the fourth field,   wherein the first format is a type-length-value (TLV) format related to a value only.   
     
     
       14. The method of claim 13, further comprising:
 in case that the MCData service is the SDS, setting at least one of an In-Reply-to message ID information element, an application ID information element, or an SDS disposition request type information element,   wherein the In-Reply-to message ID information element is set in a fifth field of the MCData message, the In-Reply-to message ID information element is used to associate a message within the conversation that is a reply to an existing message in the conversation, and the In-Reply-to message ID information element is associated with a second format with a length of 17 octet,   wherein the application ID information element is set in a sixth field of the MCData message, the application ID information element is used to identify an application for which a payload is intended, and the application ID information element is associated with the second format with a length of 2 octet,   wherein the SDS disposition request type information element is set in a seventh field of the MCData message, the SDS disposition request type information element is used to identify a type of an SDS disposition notification that a sender requires from a receiver, and the SDS disposition request type information element is associated with the second format with a length of 1 octet, and   wherein the sent MCData message further includes at least one of the fifth field, the sixth field, or the seventh field.   
     
     
       15. The method of claim 14, wherein the second format is a TLV format related to a type and a value. 
     
     
       16. The method of claim 13, further comprising:
 in case that the MCData service is the FD service, setting at least one of an In-Reply-to message ID information element, an application ID information element, an FD disposition request type information element, a mandatory download information element, a payload information element, or a metadata information element,   wherein the In-Reply-to message ID information element is set in a fifth field of the MCData message, the In-Reply-to message ID information element is used to associate a message within the conversation that is a reply to an existing message in the conversation, and the In-Reply-to message ID information element is associated with a second format with a length of 17 octet,   wherein the application ID information element is set in a sixth field of the MCData message, the application ID information element is used to identify an application for which a payload is intended, and the application ID information element is associated with the second format with a length of 2 octet,   wherein the FD disposition request type information element is set in a seventh field of the MCData message, the FD disposition request type information element is used to identify a type of an FD disposition notification that a sender requires from a receiver, and the FD disposition request type information element has the second format with a length of 1 octet,   wherein the mandatory download information element is set in an eighth field of the MCData message, the mandatory download information element is for an originating client to inform an terminating client that the file must be downloaded immediately, and the mandatory download information element is associated with the second format with a length of 1 octet,   wherein the payload information element is set in a ninth field of the MCData message, the payload information element contains a payload intended for a recipient user or application, and the payload information element is associated with a third format,   wherein the metadata information element is set in a tenth field of the MCData message, the metadata information element is used to describe the file, and the metadata information element is associated with the third format, and   wherein the sent MCData message further includes at least one of the fifth field, the sixth field, the seventh field, the eighth field, the ninth field, or the tenth field.   
     
     
       17. The method of claim 16, wherein the second format is a TLV format related to a type, and the third format is a TLV format related to the type, the value, and a length. 
     
     
       18. A user equipment (UE) in a communication system, the UE comprising:
 a transceiver; and   at least one processor configured to:
 identify at least one of a short message data service (SDS) for sharing data with one or more UEs or a file distribution (FD) service for sharing a file with the one or more UEs for a mission critical data (MCData) service, 
 set a first message type information element to identify a message type as an SDS signaling payload message in a first field of the MCData message in case that the MCData service is the SDS, and set a second message type information element to identify a message type as an FD signaling payload message in the first field of the MCData message in case that the MCData service is the FD service, wherein the first message type information element and the second message type information element are associated with a first format with a length of 1 octet, 
 set a first date and time information element to indicate a time associated with a transmission of a message in a second field of the MCData message in case that the MCData service is the SDS, and set a second date and time information element to indicate a time associated with a transmission of a file in the second field of the MCData message in case that the MCData service is the FD service, wherein the first date and time information element and the second date and time information element are associated with the first format with a length of 5 octet, 
 set a conversation identifier (ID) information element to identify a conversation in a third field of the MCData message, wherein the conversation ID information element is associated with the first format with a length of 16 octet, 
 set a message ID information element to identify a message within the conversation in a fourth field of the MCData message, wherein the message ID information element is associated with the first format with a length of 16 octet, and 
 control the transceiver to send, to the one or more UEs, the MCData message including the first field, the second field, the third field, and the fourth field, 
   wherein the first format is a type-length-value (TLV) format related to a value only.   
     
     
       19. The UE of claim 18, wherein the at least one processor is further configured to:
 in case that the MCData service is the SDS, set at least one of an In-Reply-to message ID information element, an application ID information element, or an SDS disposition request type information element,   wherein the In-Reply-to message ID information element is set in a fifth field of the MCData message, the In-Reply-to message ID information element is used to associate a message within the conversation that is a reply to an existing message in the conversation, and the In-Reply-to message ID information element is associated with a second format with a length of 17 octet,   wherein the application ID information element is set in a sixth field of the MCData message, the application ID information element is used to identify an application for which a payload is intended, and the application ID information element is associated with the second format with a length of 2 octet,   wherein the SDS disposition request type information element is set in a seventh field of the MCData message, the SDS disposition request type information element is used to identify a type of an SDS disposition notification that a sender requires from a receiver, and the SDS disposition request type information element is associated with the second format with a length of 1 octet, and   wherein the sent MCData message further includes at least one of the fifth field, the sixth field, or the seventh field.   
     
     
       20. The UE of claim 19, wherein the second format is a TLV format related to a type and a value. 
     
     
       21. The UE of claim 18, wherein the at least one processor is further configured to:
 in case that the MCData service is the FD service, set at least one of an In-Reply-to message ID information element, an application ID information element, an FD disposition request type information element, a mandatory download information element, a payload information element, or a metadata information element,   wherein the In-Reply-to message ID information element is set in a fifth field of the MCData message, the In-Reply-to message ID information element is used to associate a message within the conversation that is a reply to an existing message in the conversation, and the In-Reply-to message ID information element is associated with a second format with a length of 17 octet,   wherein the application ID information element is set in a sixth field of the MCData message, the application ID information element is used to identify an application for which a payload is intended, and the application ID information element is associated with the second format with a length of 2 octet,   wherein the FD disposition request type information element is set in a seventh field of the MCData message, the FD disposition request type information element is used to identify a type of an FD disposition notification that a sender requires from a receiver, and the FD disposition request type information element is associated with the second format with a length of 1 octet,   wherein the mandatory download information element is set in an eighth field of the MCData message, the mandatory download information element is for an originating client to inform an terminating client that the file must be downloaded immediately, and the mandatory download information element is associated with the second format with a length of 1 octet,   wherein the payload information element is set in a ninth field of the MCData message, the payload information element contains a payload intended for a recipient user or application, and the payload information element is associated with a third format,   wherein the metadata information element is set in a tenth field of the MCData message, the metadata information element is used to describe the file, and the metadata information element is associated with the third format, and   wherein the sent MCData message further includes at least one of the fifth field, the sixth field, the seventh field, the eighth field, the ninth field, or the tenth field.   
     
     
       22. The UE of claim 21, wherein the second format is a TLV format related to a type and a value, and the third format is a TLV format related to a type, a value, and a length. 
     
     
       23. The method claim 2, wherein the In-Reply-to message ID information element has a length of 17 octets, the application ID information element has a length of 2 octets, and the SDS disposition request type information element has a length of 1 octet, and
 wherein each of the In-Reply-to message ID information element, the application ID information element, and the SDS disposition request type information element is associated with a TLV format related to a type and a value.   
     
     
       24. The UE claim 5, wherein the In-Reply-to message ID information element has a length of 17 octets, the application ID information element has a length of 2 octets, and the SDS disposition request type information element has a length of 1 octet, and
 wherein each of the In-Reply-to message ID information element, the application ID information element, and the SDS disposition request type information element is associated with a TLV format related to a value only.