Method and system for sharing function alias in task key video

Abstract

The present disclosure provides a method for managing a task critical video (MCVideo) group call. The method comprises sending (602), by at least one sender user equipment (UE) in the MCVideo group call, an MCVideo message to an MCVideo server. The method comprises receiving (604), by at least one recipient UE in the MCVideo group call, an MCVideo message from an MCVideo server, where at least one of a plurality of functional alias IDs is encoded and included in the MCVideo message. The method comprises decoding (606), by at least one recipient UE in the MCVideo group call, at least one of a plurality of functional alias IDs from the MCVideo message.

Description

Technical Field

[0001] The present disclosure relates to an electronic device for wireless communication and a method of operating an electronic device. Background Art

[0002] In order to meet the demand for increased wireless data services since the deployment of 4G communication systems, efforts have been made to develop improved 5G or quasi-5G communication systems. Therefore, 5G or quasi-5G communication systems are also referred to as "post-4G networks" or "post-LTE systems". 5G communication systems are considered to be implemented in higher frequency (millimeter wave) bands, such as the 60GHz band, in order to achieve higher data rates. In order to reduce the propagation loss of radio waves and increase the transmission distance, beamforming, massive multiple-input multiple-output (MIMO), full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and massive antenna technology are discussed in 5G communication systems. In addition, in 5G communication systems, development of system network improvements based on advanced small cells, cloud radio access networks (RAN), ultra-dense networks, device-to-device (D2D) communications, wireless backhaul, mobile networks, collaborative communications, coordinated multi-point (CoMP), receiving-end interference elimination, etc. is underway. In 5G systems, hybrid FSK and QAM modulation (FQAM) and sliding window superposition coding (SWSC) as advanced coding modulation (ACM), and filter bank multi-carrier (FBMC), non-orthogonal multiple access (NOMA) and sparse code multiple access (SCMA) as advanced access technologies have been developed.

[0003] The Internet is a human-centered connectivity network where humans generate and consume information, and is now developing into the Internet of Things (IoT), where distributed entities such as things exchange and process information without human intervention. The Internet of Everything (IoE) is an Internet where IoT technology and big data processing technology are combined through connection with cloud servers. Technology elements such as "sensing technology", "wired / wireless communication and network infrastructure", "service interface technology" and "security technology" have recently been studied for IoT implementation, sensor networks, machine-to-machine (M2M) communication, machine type communication (MTC), etc. This IoT environment can provide smart Internet technology services that create new value for human life by collecting and analyzing data generated between connected things. Through the integration and combination between existing information technology (IT) and various industrial applications, IT can be applied to various fields, including smart homes, smart buildings, smart cities, smart cars or connected cars, smart grids, health care, smart devices and advanced medical services.

[0004] In line with this, various attempts have been made to apply 5G communication systems to IoT networks. For example, technologies such as sensor networks, machine type communications (MTC), and machine-to-machine (M2M) communications can be implemented through beamforming, MIMO, and array antennas. The application of cloud radio access networks (RANs) as the above-mentioned big data processing technology can also be considered as an example of the fusion between 5G technology and IoT technology.

[0005] Currently, MCVideo services are widely used in public safety services. Multiple first responders receive media content in the form of audio and video on the UE, and the first responders act according to the received media content. The media content can indicate emergency situations such as accidents, fires, etc. Summary of the invention

[0006] Technical issues

[0007] Therefore, since multiple MCVideo users from different locations can be connected together, it becomes important to identify the roles of the connected users. In the existing 3GPP MCVideo service, a user cannot share his / her preferred role which is called a functional alias:

[0008] 1. While starting or joining a group call;

[0009] 2. "Request to send" or "Request to receive" in MCVideo group call.

[0010] Therefore, as can be seen, there is a need to overcome at least one of the above problems to enable the use of functional aliases assigned to users who are participants in an MCVideo group call.

[0011] Technical Solution

[0012] In one embodiment, the present invention discloses a method for enabling the use of multiple function alias IDs in a mission critical video (MCVideo) group call. The method includes sending an MCVideo message by at least one sending user equipment (UE) in the MCVideo group call to an MCVideo server, wherein at least one of the multiple function alias IDs is encoded during the sending and included in the MCVideo message. The method includes receiving an MCVideo message of at least one sending UE from the MCVideo server by at least one receiving UE in the MCVideo group call. The method includes decoding at least one of the multiple function alias IDs from the MCVideo message by at least one receiving UE in the MCVideo group call.

[0013] In one embodiment, the present invention discloses a system for enabling the use of multiple function alias IDs in a mission critical video (MCVideo) group call. The system is configured to send an MCVideo message to an MCVideo server by at least one sending user equipment (UE) in the MCVideo group call, wherein during the sending, at least one of the multiple function alias IDs is encoded and included in the MCVideo message. The system is configured to receive an MCVideo message of at least one sending UE from the MCVideo server by at least one receiving UE in the MCVideo group call. The system is configured to decode at least one of the multiple function alias IDs from the MCVideo message by at least one receiving UE in the MCVideo group call.

[0014] In order to further illustrate the advantages and features of the present invention, a more specific description of the present invention will be presented by reference to the specific embodiments of the present invention shown in the accompanying drawings. It should be understood that these drawings only describe typical embodiments of the present invention and therefore should not be considered as limiting the scope of the present invention. The present invention will be described and explained with additional features and details in conjunction with the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] These and other features, aspects and advantages of the present invention will become better understood when the following detailed description is read with reference to the accompanying drawings, in which like characters refer to like parts throughout the several views, and in which:

[0016] Figure 1 A system for sharing function aliases in an MCVideo group call according to an embodiment of the present disclosure is shown;

[0017] Figure 2 and Figure 3 An exemplary embodiment for sharing a function alias in an MCVideo group call according to an embodiment of the present disclosure is shown;

[0018] Figure 4 and Figure 5 An exemplary embodiment of displaying the functional alias of each user during an interaction within an MCVideo group call, thereby allowing participants to identify the role of the interaction participant(s), according to an embodiment of the present disclosure is shown;

[0019] Figure 6 A method for sharing a function alias in an MCVideo group call according to an embodiment of the present disclosure is shown;

[0020] Figure 7 A method for obtaining multiple functional alias IDs at an MCVideo transmission participant receiver in a Media Transmission Notification (MTN) message according to an embodiment of the present disclosure is shown; and

[0021] Figure 8 A method for obtaining multiple function alias IDs at an MCVideo transmission participant sender in a Media Reception Notification (MRN) message according to an embodiment of the present disclosure is shown.

[0022] Furthermore, those skilled in the art will appreciate that the elements in the drawings are illustrated for simplicity and may not necessarily be drawn to scale. For example, a flow chart illustrates the method in terms of the most salient steps involved to help improve understanding of the various aspects of the present invention. Furthermore, with respect to the structure of the device, one or more components of the device may be represented in the drawings by conventional symbols, and the drawings may show only those specific details relevant to understanding the embodiments of the present invention so as not to obscure the drawings, which details are apparent to those of ordinary skill in the art having the benefit of the description herein. DETAILED DESCRIPTION

[0023] To promote an understanding of the principles of the invention, reference will now be made to the embodiments illustrated in the drawings and specific language will be used to describe the embodiments. It will be understood, however, that the scope of the invention is not intended to be limited thereby and that such changes and further modifications in the illustrated systems, and such further applications of the principles of the invention illustrated therein are deemed to be within the ordinary scope of those skilled in the art to which the invention relates.

[0024] Those skilled in the art will understand that both the foregoing general description and the following detailed description are illustrative of the present invention and are not intended to limit the present invention.

[0025] Reference throughout the specification to "one aspect," "another aspect," or similar language means that a particular feature, structure, or characteristic described in connection with that embodiment is included in at least one embodiment of the present invention. Thus, phrases "in one embodiment," "in another embodiment," and similar language appearing throughout the specification may, but do not necessarily, all refer to the same embodiment.

[0026] The terms "comprises," "includes," or any other variation thereof are intended to cover a non-exclusive inclusion, such that a process or method that includes a series of steps includes not only those steps but may also include other steps not expressly listed or inherent to such process or method. Similarly, one or more devices or subsystems or elements or structures or components do not exclude the presence of other devices or other subsystems or other elements or other structures or other components or additional devices or additional subsystems or additional elements or additional structures or additional components, without further limitations.

[0027] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which the invention belongs. The systems, methods, and examples provided herein are illustrative only and not limiting.

[0028] The present disclosure provides methods and systems that enable users to share their preferred function aliases while starting or joining an MCVideo group call and while requesting to send or receive. In the present disclosure, the function alias is suggested as an "XML element" as part of the MCVideo XML identified by the "application / vnd.3gpp.mcvideo-info+xml" content type in the SIP message and the "function alias ID field", and the "function alias ID field" is part of the transmission request message, media transmission notification (MTN) message, receive media request and media reception notification (MRN) message. In the present disclosure, users are able to select an appropriate role or name before joining an MCVideo group call, and the appropriate role or name is visible to other users in the call. In other words, the function alias indicates the role or name of the user connected in the MCVideo environment / service.

[0029] In the present disclosure, the term "user" may be interchangeably referred to as a "participant." Furthermore, the term "functional alias" may be interchangeably referred to as a "role or name."

[0030] Reference Figure 1 In one embodiment, the system 100 of the present disclosure may include but is not limited to a processor 102 , a memory 104 , an MCVideo service unit 106 , and a function alias management unit 108 .

[0031] The processor 102 may be a single processing unit or multiple units, all of which may include multiple computing units. The processor 102 may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, state machines, logic circuits, and / or any device that manipulates signals based on operational instructions. Among other capabilities, the processor 102 is configured to retrieve and execute computer-readable instructions and data stored in the memory 104.

[0032] Memory 104 may include any non-transitory computer-readable medium known in the art, including, for example, volatile memory (e.g., static random access memory (SRAM) and dynamic random access memory (DRAM)), and / or non-volatile memory (e.g., read-only memory (ROM), erasable programmable ROM, flash memory, hard disks, optical disks, and magnetic tapes).

[0033] The MCVideo service 106 provides MCVideo group and private call service features. In an exemplary embodiment, for MCVideo group calls provided by the MCVideo service 106, a host or organization can define roles or names of participants joining the call. Thus, a participant can select a specific role or name before joining the call. During the call, the selected role or name is visible to all participants in addition to the participant's name.

[0034] The function alias management unit 108 provides management of multiple aliases and activation and deactivation of aliases. In an exemplary embodiment, an organization or group or company can predefine function aliases managed by the function alias management unit 108 in the system that can be applied to participants of an MCVideo group call. Therefore, for such an MCVideo group call, participants can select one of the predefined roles or names before joining the call.

[0035] In one embodiment, the present invention discloses a system 100 for enabling multiple function alias IDs in a mission critical video (MCVideo) group call. The system 100 is configured to send an MCVideo message to an MCVideo server by at least one sending user equipment (UE) in the MCVideo group call. The system 100 is configured to receive an MCVideo message from an MC video server by at least one receiving UE in the MCVideo group call, wherein at least one of the multiple function alias IDs is encoded and included in the MCVideo message. The system 100 is configured to decode at least one of the multiple function alias IDs from the MCVideo message by at least one receiving UE in the MCVideo group call.

[0036] In one embodiment, the system 100 is configured to send at least one of a plurality of function alias IDs from an MCVideo message in a group call request to participants of the MCVideo group call.

[0037] In one embodiment, at least one sender UE may be the initiator of the MCVideo group call. In addition, at least one sender UE may not be the initiator of the MCVideo group call.

[0038] In one embodiment, the capability alias ID includes incorporating capability alias URI based elements into the MCVideoInfo XML schema to allow for sharing of multiple capability alias IDs.

[0039] In one embodiment, in order to send the MCVideo message, the system is configured to check whether the state of at least one of the plurality of function alias IDs is activated, and add at least one of the plurality of function alias IDs to the MCVideo message. In addition, the system is configured to check whether the state of at least one of the plurality of function alias IDs is one of inactive or inactive, and add a user ID to the MCVideo message.

[0040] In one embodiment, the status of at least one of the plurality of function alias IDs comprises:

[0041] 1) At least one of the multiple function alias IDs is in an unactivated state where it has not been activated by the user;

[0042] 2) in an activated state, wherein at least one of the plurality of function alias IDs has not been activated by the user;

[0043] 3) an activated state, wherein at least one of the plurality of function alias IDs is activated for use by a user; and

[0044] 4) An unactivated state, in which at least one of the multiple function alias IDs is activated but not used by the user.

[0045] In one embodiment, the present invention discloses a system 100 for sharing multiple functional alias IDs of MCVideo transmission participants in a transmission request message. The system 100 is configured to transmit a transmission request message to a transmission control server by at least one transmission participant sender user equipment (UE), wherein at least one of the multiple functional alias IDs is encoded and included in the transmission request message.

[0046] In one embodiment, the present invention discloses a system 100 for obtaining multiple functional alias IDs at a MCVideo transmission participant receiver in a media transmission notification (MTN) message. The system 100 is configured to send a transmission request message to a transmission control server by at least one sending user equipment (UE). The system 100 is configured to receive a media transmission notification (MTN) message from a transmission control server by at least one transmission participant receiving UE, wherein at least one of the multiple functional alias IDs is encoded and included in the media transmission notification (MTN) message. The system 100 is configured to decode at least one of the multiple functional alias IDs from the media transmission notification (MTN) message by at least one transmission participant receiving UE.

[0047] In one embodiment, sending the transport request message includes including the function alias ID to the MCVideo transport control message as an Information Element Identifier (IEI) Function Alias ​​field.

[0048] In one embodiment, the IEI Function Alias ​​field is incorporated into at least one of the following:

[0049] a) MCVideo transmission request message;

[0050] b) MCVideo media transmission notification message;

[0051] c) MCVideo receives a media request message; and

[0052] d)MCVideo media receives notification message.

[0053] In one embodiment, the present invention discloses a system 100 for sharing multiple functional alias IDs of MCVideo participants in a received media request message. The system 100 is configured to transmit a received media request message to a transmission control server by at least one transmission participant user equipment (UE), wherein at least one of the multiple functional alias IDs is encoded and included in the received media request message.

[0054] In one embodiment, the present invention discloses a system 100 for obtaining multiple functional alias IDs at an MCVideo transmission participant sender in a media reception notification (MRN) message. The system 100 is configured to send a receive media request message to a transmission control server by at least one sender user equipment (UE). The system 100 is configured to receive a media reception notification (MRN) message from a transmission control server by a transmission participant sender UE, wherein at least one of the multiple functional alias IDs is encoded and included in the media reception notification (MRN) message. The system 100 is configured to decode at least one of the multiple functional alias IDs from the media reception notification (MRN) message by the transmission participant sender UE.

[0055] In one embodiment, the MCVideo server may be the same as or different from the transport control server.

[0056] Figures 2 to 3 An exemplary embodiment for sharing a function alias in an MCVideo group call according to an embodiment of the present disclosure is shown. Figure 2 An overview of the group members who have joined the group call with their assigned function aliases is shown. Figure 3 The function aliases selected by the participants when joining the MCVideo group call are shown, and the UX details the group members of the participant group call and their assigned function aliases. For example: Police Technician, Constable, Officer, Deputy, Sergeant, Inspector, and Superintendent.

[0057] Figure 4The display of the functional alias of each user during an interaction within an MCVideo group call is shown, which allows participants to identify the role of the (multiple) interaction participants. Thus, in the example shown, the police terminal sends a transmission request to the MCVideo transmission control server to share the live video stream. Thereafter, the MCVideo transmission control server then triggers a Media Transmission Notification (MTN) message that is sent to all other group members sharing the live video stream regarding the police capacity.

[0058] Figure 5 The display of the functional alias of each user during an interaction within an MCVideo group call is shown, which allows participants to identify the roles of the participants in the interaction. Thus, in the example shown, a police member (Police Technician, Constable, Deputy Sheriff) sends a receive media request to the MCVideo transport control server to obtain a live video stream from the "Superintendent". Thereafter, the MCVideo transport control server then triggers a Media Receive Notification (MRN) message to the Superintendent with a list of police members receiving the live video stream.

[0059] In an exemplary embodiment, the system may provide the user with multiple function aliases received through the MCVideo service configuration document, and the user may activate or deactivate the appropriate function alias using the SIP public and presence information data format. Thus, the user may select one of the function aliases before joining the MCVideo group call. For another MCVideo group call, the user may select a different function alias before joining the call. For example, in an MCVideo group call in the Future Railway Mobile Communication System (FRMC), the user selects "Railway.Driver11@bangaloremetro.com" as the function alias, and for another MCVideo group call, the user may select "Railway.Clerk12@bangaloremetro.com" as the function alias based on his role defined for the trip.

[0060] In an exemplary embodiment, users can switch function aliases during an MCVideo group call based on the appropriate function alias activated. For example, one user with a function alias of "Railway.Clerk12@bangaloremetro.com" leaves the call, and then another user in the call can change the function alias to "Railway.Clerk12@bangaloremetro.com" to continue the call (role switching is possible).

[0061] Figure 6A method 600 for sharing a function alias in an MCVideo group call according to an embodiment of the present disclosure is shown. In step 602, the method includes sending an MCVideo message to an MCVideo server by at least one sending user equipment (UE) in the MCVideo group call. In step 604, the method includes receiving an MCVideo message from an MC video server by at least one receiving UE in the MCVideo group call, wherein at least one of a plurality of function alias IDs is encoded and included in the MCVideo message. In step 606, the method includes decoding at least one of a plurality of function alias IDs from the MCVideo message by at least one receiving UE in the MCVideo group call.

[0062] In one embodiment, the method includes sending at least one of the plurality of function alias IDs encoded in a group call request from an MCVideo message to participants of the MCVideo group call.

[0063] In one embodiment, at least one sender UE may be the initiator of the MCVideo group call. In addition, at least one sender UE may not be the initiator of the MCVideo group call.

[0064] In one embodiment, the capability alias ID includes incorporating capability alias URI based elements into the MCVideoInfo XML schema to allow for sharing of multiple capability alias IDs.

[0065] In one embodiment, sending the MCVideo message includes checking whether the state of at least one of the multiple function alias IDs is activated and adding at least one of the multiple function alias IDs to the MCVideo message. It also includes checking whether the state of at least one of the multiple function alias IDs is not activated or inactive and adding the user ID to the MCVideo message.

[0066] In one embodiment, the status of at least one of the plurality of function alias IDs comprises:

[0067] 1) At least one of the multiple function alias IDs is in an unactivated state where it has not been activated by the user;

[0068] 2) in an activated state, wherein at least one of the plurality of function alias IDs has not been activated by the user;

[0069] 3) an activated state, in which at least one of the plurality of function alias IDs is activated for use by the user; and

[0070] 4) An unactivated state, in which at least one of the multiple function alias IDs is activated but not used by the user.

[0071] In one embodiment, the present invention discloses a method for sharing multiple functional alias IDs of MCVideo transmission participants in a transmission request message. The method includes sending a transmission request message to a transmission control server by at least one transmission participant sender user equipment (UE), wherein at least one of the multiple functional alias IDs is encoded and included in the transmission request message.

[0072] In one embodiment, Figure 7 As shown, the present invention discloses a method 700 for obtaining multiple functional alias IDs at an MCVideo transmission participant receiver in a media transmission notification (MTN) message. In step 702, the method includes sending a transmission request message to a transmission control server by at least one transmitting user equipment (UE). In step 704, the method includes receiving a media transmission notification message (MTN) from a transmission control server by at least one transmission participant receiving UE, wherein at least one of the multiple functional alias IDs is encoded and included in the media transmission notification (MTN) message. In step 706, the method includes decoding at least one of the multiple functional alias IDs from the media transmission notification (MTN) message by at least one transmission participant receiving UE.

[0073] In one embodiment, method 700 includes sending a transport request message including including a function alias ID to an MCVideo transport control message as an Information Element Identifier (IEI) Function Alias ​​field.

[0074] In one embodiment, the IEI Function Alias ​​field is incorporated into at least one of the following:

[0075] a) MCVideo transmission request message;

[0076] b) MCVideo media transmission notification message;

[0077] c) MCVideo receives a media request message; and

[0078] d)MCVideo media receives notification message.

[0079] In one embodiment, the present invention discloses a method for sharing multiple functional alias IDs of MCVideo participants in a receive media request message. The method includes sending a receive media request message by at least one transmission participant user equipment (UE) to a transmission control server, wherein at least one of the multiple functional alias IDs is encoded and included in the receive media request message.

[0080] In one embodiment, Figure 8As shown, the present invention discloses a method 800 for obtaining multiple functional alias IDs at an MCVideo transmission participant sender in a media reception notification (MRN) message. In step 802, the method includes sending a receive media request message to a transmission control server by at least one sender user equipment (UE). In step 804, the method includes receiving a media reception notification (MRN) message from a transmission control server by the transmission participant sender UE, wherein at least one of the multiple functional alias IDs is encoded and included in the media reception notification (MRN) message. In step 806, the method includes decoding at least one of the multiple functional alias IDs from the media reception notification (MRN) message by the transmission participant sender UE.

[0081] In one embodiment, the MCVideo server may be the same as or different from the transport control server.

[0082] In an exemplary embodiment, the present invention discloses an MCVideo Info XML schema. <functional-alias-uri>(See 3GPP 24.281 Section F.1) which enables MCVideo users to share their preferred function aliases and is encoded as follows:

[0083] 1) If <mcvideoinfo>Include <mcvideo-params>Element, if necessary, you can <functional-alias-uri>Included in encrypted content.

[0084] 2) Then, <functional-alias-uri>Elements include <mcvideouri>An element whose value represents a role or capability alias.

[0085] Table 1 discloses exemplary MCVideo transport control specific data fields defined by 3GPP 24.581, which adds the "Function Alias ​​Field ID" used in the systems and methods of the present disclosure.

[0086] Transmission control specific data fields

[0087]

[0088] In this embodiment, the proposed Function Alias ​​field contains a URI that identifies the role that the MCVideo user wishes to be for this instance. Table 2 discloses an exemplary Function Alias ​​field ID method for use in the systems and methods of the present disclosure.

[0089] Function Alias ​​Field

[0090]

[0091] The <Function Alias ​​Field ID> value is a binary value and is set according to Table 9.2.3.1-1. The <Function Alias ​​Length> value is a binary value and includes a value indicating the length in octets of the <Function Alias ​​Field ID> value excluding padding.

[0092] The <function alias> value is encoded as described in Table 8.2.3.19-2 3GPP 24.581.

[0093] If the length of the <Function Alias> value is not a multiple of (2+4) bytes, the <Function Alias ​​Field> value should be padded to (a multiple of 2+4) bytes. The value of the padding byte is set to zero and the padding byte is ignored by the receiver.

[0094] Table 3 discloses extensions of an exemplary transmission request message used in the systems and methods of the present disclosure.

[0095] Transmission Request Message

[0096]

[0097] Except for the first three 32-bit words, the order of the fields is irrelevant.

[0098] Subtype:

[0099] Encode the subtype according to Table 9.2.2.1-1.

[0100] length:

[0101] The length is encoded as specified in clause 9.1.2.

[0102] SSRC:

[0103] The SSRC field carries the SSRC of the transmission participant that sent the transmission request message.

[0104] The contents of the SSRC field are encoded as specified in IETF RFC 3550 [3].

[0105] Transfer Priority:

[0106] The Transmission Priority field is encoded as described in clause 9.2.3.2.

[0107] User ID:

[0108] The User ID field is used only in non-networking and is encoded as described in clause 9.2.3.8.

[0109] Transmission Indicator:

[0110] The Transmission Indicator field is encoded as described in clause 9.2.3.11.

[0111] Function Alias: The Function Alias ​​field carries the function alias URI of the sending user. The Function Alias ​​field is encoded as described in clause 9.2.3.21.

[0112] Table 4 discloses extensions of an exemplary Media Transmission Notification (MTN) message used in the systems and methods of the present disclosure.

[0113] Media transmission notification message

[0114]

[0115] Except for the first three 32-bit words, the order of the fields is irrelevant.

[0116] Subtype:

[0117] Encode the subtype according to Table 9.2.2.1-2.

[0118] length:

[0119] The length is encoded as specified in clause 9.1.2.

[0120] SSRC:

[0121] The SSRC field carries the SSRC of the transport control server.

[0122] The SSRC field is encoded as specified in IETF RFC 3550 [3].

[0123] User ID:

[0124] The User ID field carries the MCVideo ID of the user sending the media.

[0125] The User ID value is encoded as specified in clause 9.2.3.8.

[0126] Transmitter SSRC:

[0127] The SSRC of the Transmitter field carries the SSRC of the user sending the media.

[0128] The SSRC of the transmitter field is encoded as described in clause 9.2.3.16.

[0129] Request permission to transfer:

[0130] The Permission Requested Transmission field is encoded as specified in clause 9.2.3.7.

[0131] Transmission Indicator:

[0132] The Transmission Indicator field is encoded as described in clause 9.2.3.11.

[0133] Tracking Information:

[0134] When the MCVideo call involves a non-control MCVideo function, the Track Info field is included. The method of the Track Info field is described in clause 9.2.3.13.

[0135] Function Alias: The Function Alias ​​field carries the function alias URI of the sending user. The Function Alias ​​field is encoded as described in clause 9.2.3.21.

[0136] Table 5 discloses an example receive media request message extension used in the systems and methods of the present disclosure.

[0137] Receiving media request message

[0138]

[0139] Except for the first three 32-bit words, the order of the fields is irrelevant.

[0140] Subtype:

[0141] Encode the subtype according to Table 9.2.2.1-1.

[0142] length:

[0143] The length is encoded as specified in clause 9.1.2.

[0144] SSRC:

[0145] The SSRC field carries the SSRC of the sending participant requesting to receive media from another user.

[0146] The contents of the SSRC field are encoded as specified in IETF RFC 3550 [3].

[0147] User ID:

[0148] The User ID field is used to carry the identity of the user requesting to receive media and is encoded as described in clause 9.2.3.8.

[0149] Transmitter SSRC:

[0150] The SSRC of the Transmitter field carries the SSRC of the user sending the media.

[0151] The SSRC of the Transmit field is encoded as described in clause 9.2.3.16.

[0152] Transmission Indicator:

[0153] The Transmission Indicator field is encoded as described in clause 9.2.3.11.

[0154] Receiving priority:

[0155] The Receive Priority field is encoded as described in clause 9.2.3.19.

[0156] Tracking Information:

[0157] When an MCVideo call involves a non-controlling MCVideo function, the Tracking Information field is included. The method for the Tracking Information field is described in clause 9.2.3.13.

[0158] Function Alias: The Function Alias ​​field carries the function alias URI of the user requesting media reception. The Function Alias ​​field is encoded as described in clause 9.2.3.21.

[0159] Table 6 discloses extensions to an exemplary Media Reception Notification (MRN) message used in the systems and methods of the present disclosure.

[0160] Media reception notification message

[0161]

[0162] Except for the first three 32-bit words, the order of the fields is irrelevant.

[0163] Subtype:

[0164] Encode the subtype according to Table 9.2.2.1-2.

[0165] length:

[0166] The length is encoded as specified in clause 9.1.2.

[0167] SSRC:

[0168] The SSRC field carries the SSRC of the transport control server.

[0169] The contents of the SSRC field are encoded as specified in IETF RFC 3550 [3].

[0170] User ID:

[0171] The User ID field is used to carry the identity of the user who is receiving the media and is encoded as described in clause 9.2.3.8.

[0172] Function Alias: The Function Alias ​​field carries the function alias URI of the user requesting media reception. The Function Alias ​​field is encoded as described in clause 9.2.3.21.

[0173] In an exemplary embodiment, the method steps for entering the "G: Transmission Taken" state are as follows:

[0174] In this method, a media transmission notification message is sent to the receiving control

[0175] Arbitration logic. Media Transmission Notification (MTN) message:

[0176] 1) If privacy is not requested, include the MCVideo ID of the authorized MCVideo user in the User ID field;

[0177] 2) Include the SSRC of the authorized MCVideo user in the SSRC of the transmitter field;

[0178] 3) Include a message sequence number field, and the message sequence number value increases by 1;

[0179] 4) If the session is a broadcast group call, it shall include a Permission to Transmit field with the request set to "0";

[0180] 5) If the session is not a broadcast group call, a Permission to Transmit field with the request set to "1" may be included;

[0181] 6) if the group call is a broadcast group call, system call, emergency call, impending permanent call, or temporary group session, a transport indicator field with appropriate indication shall be included; and

[0182] 7) If the transfer request has a functional alias field, the user's functional alias should be included in the functional alias field of the transfer notification message.

[0183] 8) Start the "general receive control operation" state machine.

[0184] At least according to the aforementioned embodiments, the present disclosure leads to at least the following advantages:

[0185] 1) Allow users to select a function alias before joining a call;

[0186] 2) Make the user's functional alias visible to the participants of the call;

[0187] 3) Enable a system that predefines function aliases for a class of actors.

[0188] In an exemplary embodiment, a system for sharing multiple functional alias IDs of MCVideo transmission participants in a transmission request message, the system comprising: a processor; and a memory device containing instructions, the instructions, when executed by the processor, causing the processor to: transmit a transmission request message to a transmission control server by at least one transmission participant sender user equipment (UE), wherein at least one of the multiple functional alias IDs is encoded and included in the transmission request message.

[0189] In an exemplary embodiment, a system for obtaining multiple functional alias IDs at an MCVideo transmission participant receiver in a media transmission notification (MTN) message, the system comprising: a processor; and a memory device containing instructions, which, when executed by the processor, causes the processor to: receive the media transmission notification (MTN) message from a transmission control server by at least one transmission participant receiver UE, wherein at least one of the multiple functional alias IDs is encoded and included in the media transmission notification (MTN) message, and decode at least one of the multiple functional alias IDs from the media transmission notification (MTN) message by the at least one transmission participant receiver UE.

[0190] In an exemplary embodiment, a system for sharing multiple functional alias IDs of MCVideo participants in a received media request message, the system comprising: a processor; and a memory device containing instructions, the instructions, when executed by the processor, causing the processor to: transmit a received media request message to a transmission control server by at least one transmission participant user equipment (UE), wherein at least one of the multiple functional alias IDs is encoded and included in the received media request message.

[0191] In an exemplary embodiment, a system for obtaining multiple functional alias IDs at an MCVideo transmission participant sender in a media reception notification (MRN) message, the system comprising: a processor; and a memory device containing instructions, the instructions, when executed by the processor, causing the processor to: receive the media reception notification (MRN) message from a transmission control server by the transmission participant sender UE, wherein at least one of the multiple functional alias IDs is encoded and included in the media reception notification (MRN) message, and decode at least one of the multiple functional alias IDs from the media reception notification (MRN) message by the transmission participant sender UE.

[0192] Although specific language has been used to describe the subject matter of the present invention, it is not intended to impose any restrictions thereon. As will be apparent to those skilled in the art, various work modifications may be made to the method to realize the inventive concept taught herein. The accompanying drawings and the foregoing description provide examples of embodiments. It will be appreciated by those skilled in the art that one or more of the elements may be well combined into a single functional element. Alternatively, some elements may be divided into a plurality of functional elements. Elements from one embodiment may be added to another embodiment.< / mcvideouri> < / mcvideoinfo>

Claims

1. A method (600) for managing a video communication group call by a server in a communication system supporting a public safety service, the method comprising: receiving (602) a first message from at least one sending user equipment UE in the video communication group call, the first message comprising function alias information related to a role of a user; as well as A second message is sent (604) to at least one receiving UE in the video communication group call based on the received first message, wherein the second message includes function alias information related to the user role.

2. The method according to claim 1, in, The information related to the user's role includes a function alias identification (ID).

3. The method according to claim 1, in, The video communication group call is a mission critical (MC) video communication group call.

4. The method according to claim 1, wherein: The first message and the second message are Session Initiation Protocol (SIP) messages.

5. The method according to claim 1, wherein: The at least one sender UE is not the initiator of the video communication group call.

6. The method according to claim 1, wherein: The function alias information includes a function alias Uniform Resource Identifier (URI) based on an element of the MCVideo Info XML schema so that the function alias information can be shared.

7. The method according to claim 1, wherein: The first message and the second message are transmission request messages.

8. The method according to claim 7, wherein: The transmission request message includes a function alias ID as an information element identifier IEI function alias field.

9. The method according to claim 8, wherein: The IEI function alias field is included in at least one of the following: a) MCVideo transmission request message; b) MCVideo media transmission notification message; c) MCVideo receives a media request message; and d)MCVideo media receives notification message.

10. The method according to claim 1, wherein: The first message is a receive media request message, and the second message is a media reception notification (MRN) message.

11. A server for managing video communication group calls in a communication system supporting public safety services, the server comprising: Transceiver; as well as At least one processor (102) coupled to the transceiver, configured to: receiving (602) a first message from at least one sending user equipment UE in the video communication group call, the first message comprising function alias information related to a role of a user; as well as A second message is sent (604) to at least one receiving UE in the video communication group call based on the received first message, wherein the second message includes function alias information related to the user role.

12. The server according to claim 11, wherein: The information related to the user's role includes a function alias identification (ID).

13. The server according to claim 11, wherein: The video communication group call is a mission critical (MC) video communication group call.

14. The server according to claim 11, wherein: The first message and the second message are Session Initiation Protocol (SIP) messages.

15. The server according to claim 11, wherein: The at least one sender UE is not the initiator of the video communication group call.

Images