# US 2023/0067571 A1 · Methods and systems for managing mission critical data (mcdata) sessions

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2023/0067571 A1
- Document ID: US20230067571A1
- Status: Published application
- Kind: A1
- Application number: 17/983,629
- Filed: 2022-11-09
- Published: 2023-03-02
- Earliest claimed: 2020-05-22
- Assignees: Samsung Electronics Co., Ltd.
- Applicants: Samsung Electronics Co., Ltd.
- Inventors: Kiran GAJULA; Kiran Gurudev KAPALE; Siva Prasad GUNDUR
- Web page: https://patentgrep.com/patent/US20230067571A1

## CPC

- H04L 69/329: in the application layer [OSI layer 7]
- H04W 4/90: Services for handling of emergency or hazardous situations, e.g. earthquake and tsunami warning systems [ETWS]
- H04L 5/0044: {Allocation of payload; Allocation of data channels, e.g. PDSCH or PUSCH}
- H04W 4/08: User group management
- H04W 4/12: Messaging; Mailboxes; Announcements
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## Abstract

The disclosure relates to a communication method and system for converging a 5th-Generation (5G) communication system for supporting higher data rates beyond a 4th-Generation (4G) system with a technology for Internet of Things (IoT). A method is provided. The method includes transmitting by at least one sender, respective MCData User Identifier (ID) to at least one receiver User Equipment (UE), receiving, by the at least one receiver UE, the MCData User ID of the at least one sender UE, and decoding, by the at least one receiver UE, the received sender MCData User ID to identify the at least one sender UE, wherein the sender MCData User ID is included in one of a signaling payload message content and a MCData notification message sent by the at least one sender UE to the at least one receiver UE.

## Claims

### Claim 1

A method for managing a mission critical data (MCData) session, the method comprising:
triggering, by a sender User Equipment (UE), transmission of data to at least one receiver UE;
adding, by the sender UE, a sender user identifier (ID) in a signaling payload of the data to be transmitted; and
transmitting, by the sender UE, the data with the sender user ID in the signaling payload to the at least one receiver UE.

### Claim 2 (depends on 1)

The method of claim 1, further comprising:
receiving, by the at least one receiver UE, the data from the sender UE; and
decoding, by the at least one receiver UE, the sender user ID added in the signaling payload of the received data to identify the sender UE of the received data.

### Claim 3 (depends on 1)

The method of claim 1, wherein the sender UE is an initiator of the MCData session.

### Claim 4 (depends on 1)

The method of claim 1, wherein the sender UE is not an initiator of the MCData session.

### Claim 5 (depends on 1)

The method of claim 1,
wherein the data transmitted by the sender UE to the at least one receiver UE includes a message, and
wherein the message includes at least one of a content, a file, audio, a video, an image, and text.

### Claim 6 (depends on 5)

The method of claim 5, wherein the data transmitted by the sender UE to the at least one receiver UE includes a notification sent by the at least one receiver UE as an acknowledgement in response to the message received from the sender UE.

### Claim 7 (depends on 2)

The method of claim 2,
wherein the signaling payload of the received data includes an Information Element (IE) corresponding to the sender user ID and one or more IEs corresponding to the data,
wherein the IE corresponding to the sender user ID is associated with at least one of an information element index (IEI) field indicating a value of the sender user ID, a type field indicating a type of the sender user ID, a presence field, a format field indicating a format of the sender user ID, and a length field indicating a length of the sender user ID, and
wherein the sender user ID is a MCData user ID.

### Claim 8 (depends on 7)

The method of claim 7, wherein the decoding, by the at least one receiver UE, of the sender user ID comprises:
decoding the IE corresponding to the sender user ID and the associated at least one of the IEI field, the type field, the presence field, the format field, and the length field of the signaling payload of the received data in sequence to identify the sender UE of the received data.

### Claim 9

A method for identifying a sender of data in a mission critical data (MCData) session, the method comprising:
transmitting, by at least one sender User Equipment (UE), respective MCData User Identifier (ID) to at least one receiver UE;
receiving, by the at least one receiver UE, the MCData User ID of the at least one sender UE; and
decoding, by the at least one receiver UE, the received sender MCData User ID to identify the at least one sender UE,
wherein the sender MCData User ID is included in one of a signaling payload message and a MCData notification message sent by the at least one sender UE to the at least one receiver UE.

### Claim 10 (depends on 9)

The method of claim 9, wherein the at least one sender UE is an initiator of the MCData session.

### Claim 11 (depends on 9)

The method of claim 9, wherein the at least one sender UE is not an initiator of the MCData session.

### Claim 12

A mission critical data (MCData) communication system comprising:
a plurality of User Equipment (UEs),
wherein a sender UE of the plurality of UEs s configured to:
trigger transmission of data to at least one receiver UE,
add a sender user identifier (ID) in a signaling payload of the data to be transmitted, and
transmit the data with the sender user ID in the signaling payload to the at least one receiver UE.

### Claim 13 (depends on 12)

The MCData communication system of claim 12,
wherein a receiver UE of the at least one receiver UE is configured to:
receive the data from the sender UE, and
decode the sender user ID added in the signaling payload of the received data to identify the sender UE of the received data,
wherein the receiver UE is configured to decode the sender user ID by:
decoding an Information Element (IE) corresponding to the sender user ID and associated at least one of an Information Element Index (IEI) field, a type field, a presence field, a format field, and a length field present in the signaling payload of the received data in sequence to identify the sender UE of the received data.

### Claim 14

A sender User Equipment (UE) in a mission critical data (MCData) communication system, the UE comprising:
a transceiver; and
processing circuitry coupled to the transceiver and configured to:
trigger transmission of data to a receiver UE,
add a sender user identifier (ID) to a signaling payload of the data, and
transmit the data along with the sender user ID to the receiver UE, wherein the data includes a message to the receiver UE.

### Claim 15

A receiver User Equipment (UE) in a mission critical data (MCData) communication system, the UE comprising:
a transceiver; and
processing circuitry coupled to the transceiver and configured to:
receive a signaling payload message content of data from a sender UE, wherein the signaling payload message includes a sender user identifier (ID) of the sender UE and the data, and
decode the signaling payload message content of the data to identify the sender UE of the data, wherein the data is one of a message and a notification.
