Patent Description:
To meet the demand for wireless data traffic having increased since deployment of <NUM>th generation (<NUM>) communication systems, efforts have been made to develop an improved <NUM>th generation (<NUM>) or pre-<NUM> communication system. Therefore, the <NUM> or pre-<NUM> communication system is also called a 'Beyond <NUM> Network' or a 'Post long-term evolution (LTE) System'. The <NUM> communication system is considered to be implemented in higher frequency (millimeter (mm) Wave) bands, e.g., <NUM> gigahertz (GHz) bands, so as to accomplish higher data rates. In the <NUM> system, Hybrid FSK and QAM Modulation (FQAM) and sliding window superposition coding (SWSC) as an advanced coding modulation (ACM), and filter bank multi carrier (FBMC), non-orthogonal multiple access (NOMA), and sparse code multiple access (SCMA) as an advanced access technology have been developed.

In general, a vertical domain is an industry or group of enterprises in which similar products or services are developed, produced, and provided. <NUM>rd Generation Partnership Project (3GPP) is defining multiple verticals like Vehicle to everything (V2XAPP), <NUM>th Generation (<NUM>) Messaging Architecture (5GMARCH), unmanned aerial vehicle (UASAPP) and Factories of the Future (FFAPP). A Service Enabler Architecture Layer (SEAL) is an enabling layer architecture which provides set of common services to multiple verticals. The common services include group management, configuration management, location management, identity management, key management and network resource management. The vertical service provider can decide to use one or more services from SEAL.

In particular, SEAL group management service offers multiple features and capabilities to manage groups - like creating group, modifying group configuration, modifying membership of the group, creating dynamic group, creating location based group, subscribing to group change event, etc. Although, the SEAL group management offers multiple capabilities there is no procedure which supports fetching of list of groups where the vertical application layer (VAL) user is member of. Also, there is no procedure which supports sending group creation notifications to the VAL users who do not support SEAL clients.

Thus, it is desired to address the above mentioned disadvantages or other shortcomings or at least provide a useful alternative
The above information is presented as background information only to assist with an understanding of the disclosure.

<NPL>, specifies the functional architecture for service enabler architecture layer (SEAL) and the procedures, information flows and APIs for each service within SEAL in order to support vertical applications over the 3GPP system.

<NPL>, discusses solutions to satisfy the requirements for MSGin5G Service (message service for Massive Internet of Things (MIoT) over <NUM> System).

Accordingly, an aspect of the disclosure is to provide a device and method to make vertical application layer (VAL) client aware of group information.

Another aspect of the disclosure is to provide a method and device for synchronization of group creation information between the server and the client.

Preferred embodiments of the invention are matter of the dependent claims.

Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the various embodiments described herein can be made without departing from the scope of the disclosure as defined by the claims.

As is traditional in the field, embodiments may be described and illustrated in terms of blocks which carry out a described function or functions. These blocks, which may be referred to herein as managers, units, modules, hardware components or the like, are physically implemented by analog and/or digital circuits such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hardwired circuits and the like, and may optionally be driven by firmware. The circuits may, for example, be embodied in one or more semiconductor chips, or on substrate supports such as printed circuit boards and the like. The circuits constituting a block may be implemented by dedicated hardware, or by a processor (e.g., one or more programmed microprocessors and associated circuitry), or by a combination of dedicated hardware to perform some functions of the block and a processor to perform other functions of the block. Each block of the embodiments may be physically separated into two or more interacting and discrete blocks without departing from the scope of the disclosure. Likewise, the blocks of the embodiments may be physically combined into more complex blocks without departing from the scope of the disclosure.

The accompanying drawings are used to help easily understand various technical features and it should be understood that the embodiments presented herein are not limited by the accompanying drawings.

Accordingly, the embodiment herein is to provide a system and method to make a vertical application layer (VAL) client aware of group information. The proposed method provides procedures for VAL client to fetch the list of groups to which it has membership, with help of a Service Enabler Architecture Layer (SEAL) client. Further, the proposed method provides procedures for sending notifications to the group members who do not have SEAL clients available with them.

<FIG> is a block diagram illustrating a User Equipment (<NUM>) in communication with a SEAL server (<NUM>) and a VAL server (<NUM>) for synchronization of group information between the UE (<NUM>), the VAL server (<NUM>) and the SEAL server (<NUM>) in a wireless system (<NUM>), according to an embodiment of the disclosure.

Referring to <FIG>, the UE (<NUM>) is communicating with the SEAL server (<NUM>) and the VAL server (<NUM>) over a 3GPP network (<NUM>). The UE (<NUM>) comprises a SEAL Client (<NUM>), a VAL client (<NUM>), a memory (<NUM>), a processor (<NUM>) and a communicator (<NUM>).

The SEAL client (<NUM>) comprises a SEAL Client group information sync controller (101a) for synchronizing group information based on the SEAL client (<NUM>) instructions.

The SEAL server (<NUM>) comprises a SEAL server group information sync controller (<NUM>) for synchronizing group information based on the SEAL server (<NUM>) instructions.

In an embodiment, the VAL client (<NUM>) is a MSGin5G client and the VAL server (<NUM>) is a MSGin5G server. The SEAL server (<NUM>) may comprise a group management server and the SEAL client (<NUM>) comprises a group management client.

The VAL client (<NUM>) comprises a VAL Client group information sync controller (102a) for synchronizing group information based on the VAL client (<NUM>) instructions.

The VAL server (<NUM>) comprises a VAL server group information sync controller (<NUM>) for synchronizing group information based on the VAL server (<NUM>) instructions.

The VAL Client group information sync controller (102a), the VAL server group information sync controller (<NUM>), the SEAL Client server information sync controller (101a), the SEAL server group information sync controller (<NUM>), are implemented by processing circuitry such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hardwired circuits, or the like, and may optionally be driven by firmware. The circuits maybe, for example, be embodied in one or more semiconductor chips, or on substrate supports such as printed circuit boards and the like.

The memory (<NUM>) stores instructions to be executed by the processor (<NUM>) for synchronization of group information between the UE (<NUM>), the VAL server (<NUM>) and the SEAL server (<NUM>). The memory (<NUM>) may include non-volatile storage elements. Examples of such non-volatile storage elements may include magnetic hard discs, optical discs, floppy discs, flash memories, or forms of electrically programmable memories (EPROM) or electrically erasable and programmable (EEPROM) memories.

In addition, the memory (<NUM>) may, in some examples, be considered a non-transitory storage medium. The term "non-transitory" may indicate that the storage medium is not embodied in a carrier wave or a propagated signal. However, the term "non-transitory" should not be interpreted that the memory (<NUM>) is non-movable. In some examples, the memory (<NUM>) can be configured to store larger amounts of information than the memory. In certain examples, a non-transitory storage medium may store data that can, over time, change (e.g., in Random Access Memory (RAM) or cache). The memory (<NUM>) can be an internal storage or it can be an external storage unit of the UE (<NUM>), a cloud storage, or any other type of external storage.

In an embodiment, the processor (<NUM>) communicates with the SEAL client (<NUM>), the VAL client (<NUM>), the memory (<NUM>), and the communicator (<NUM>). The processor (<NUM>) is configured to execute instructions stored in the memory (<NUM>) for synchronization of group information between the UE (<NUM>), the VAL server (<NUM>) and the SEAL server (<NUM>). The processor (<NUM>) may include one or a plurality of processors, may be a general purpose processor, such as a central processing unit (CPU), an application processor (AP), or the like, a graphics-only processing unit such as a graphics processing unit (GPU), a visual processing unit (VPU), and/or an Artificial intelligence (AI) dedicated processor such as a neural processing unit (NPU).

In an embodiment, the communicator (<NUM>) is configured for communicating internally between internal hardware components and with external devices via one or more networks. The communicator (<NUM>) includes an electronic circuit specific to a standard that enables wired or wireless communication.

In an embodiment the proposed method and UE (<NUM>) provides different scenarios where synchronization of group information is provided between the UE (<NUM>) and the SEAL server (<NUM>) and the VAL/MSGin5G Server (<NUM>).

In an embodiment, when the UE (<NUM>) is in offline mode or in power saving mode, the UE (<NUM>) may not be aware about newly created or deleted MSGin5G groups in which the UE (<NUM>) or a user of the UE (<NUM>) is a member. In this procedure, the MSGin5G client (<NUM>) send a group list fetch request to the SEAL client (<NUM>) for retrieving information about the groups handled by the SEAL client (<NUM>).

Upon receiving the group list fetch request, the SEAL client (<NUM>) forwards the group list fetch request to the SEAL server (<NUM>).

In response to receiving the group list fetch request, the SEAL server (<NUM>) checks the authorization of the group list fetch request and if authorized (<NUM>) the SEAL server (<NUM>) shares a group list fetch response with the SEAL client (<NUM>). Further, the SEAL client (<NUM>) notifies the group list fetch response to the UE (<NUM>).

The group list fetch response comprises the UE ID/MSGin5G service ID (VAL User) for whom group list fetch request is received, a list of Group service ID (VAL groups) for which the MSGin5G service ID (VAL User/UE ID) is member and a result indicating success or failure. In an embodiment, the SEAL client (<NUM>) notifies the list of Group service ID for which the MSGin5G service ID (VAL User/UE ID) is member to the UE (<NUM>).

In an embodiment, the pre-conditions for a group to be entered in the group list are as follows: The group is previously defined on the SEAL server (<NUM>) including a list of users of the group. The List of groups to which a VAL UE/VAL User belongs to is known to the SEAL server (<NUM>) for each of the VAL UE/VAL User. The MSGin5G UE (<NUM>) (i.e., VAL user) has not received group announcement message as it is offline.

Another scenario is of sharing group creation notification. Pre-conditions for the scenario are as follows: The SEAL client (<NUM>), the SEAL server (<NUM>), the MSGin5G Client (<NUM>), the MSGin5G server (<NUM>) and the group members belong to a same VAL system. The authorized VAL user/UE/administrator (<NUM>) is aware of the user's identities which will be constituted to form the VAL group.

The SEAL client (<NUM>) of an authorized UE (<NUM>) requests a group create operation to the SEAL server (<NUM>). During the group creation, the SEAL server (<NUM>) creates and stores the information of the created group. Further, the SEAL server (<NUM>) conditionally notify the VAL/MSGin5G server regarding the group creation with the information of the group members. The VAL group members of the VAL group are notified about the newly created VAL group configuration data. Further, the SEAL server (<NUM>) provides a group creation response to the SEAL client (<NUM>) of the administrator/authorized VAL user/UE.

Another scenario is of sharing group creation notification when the group members (UE) (<NUM>) does not include SEAL client (<NUM>). Pre-conditions for the scenario are as follows: The MSGin5G Server (<NUM>) interacts with the SEAL Server (<NUM>) using the procedures over SEAL-S reference point. The MSGin5G Server (<NUM>) is aware of a legacy 3GPP message client (e.g., SMS client) in legacy 3GPP UE and interacts with it via Legacy 3GPP Message Gateway. The MSGin5G Server (<NUM>) is aware of the Non-3GPP message client in Non-3GPP UE and interacts with it via Non-3GPP Message Gateway. The group creation notification includes identities belonging to different types of UEs i.e., MSGin5G UE, Legacy 3GPP UE and Non-3GPP UE.

In an embodiment, the SEAL Server (<NUM>) sends a group creation notification message to the MSGin5G Server including a list of identities belonging to different types of UEs i.e., MSGin5G UE, Legacy 3GPP UE and Non-3GPP UE. Upon receiving the group creation notification message, the MSGin5G server (VAL server) determines whether the received group creation notification message has a list of identities that belong to Legacy 3GPP UEs or Non-3GPP UEs or both. The MSGin5G server analyses a registration status of the members in the received identity list and determines if it is to be routed to a Legacy 3GPP UE or Non-3GPP UEs or both and determines that a group notification message should be sent to those UEs.

In an embodiment, upon determining that the group notification message should be sent to Legacy 3GPP UEs, the MSGin5G Server initiates the group notification message to a legacy 3GPP Message Gateway for delivery. The legacy 3GPP Message Gateway translates the group notification message to a legacy 3GPP message and sends it to a legacy 3GPP message client.

In another embodiment, upon determining that the group notification message should be sent to Non-3GPP UEs, the MSGin5G Server initiates the group notification message to a Non-3GPP Message Gateway for delivery. The Non-3GPP Message Gateway translates the group notification message to a Non-3GPP message and sends it to a Non-3GPP message client. Thus, as seen above, the proposed method and UE (<NUM>) provides synchronization of group information between the UE (<NUM>), the VAL server (<NUM>) and the SEAL server (<NUM>) in different scenarios.

Although the <FIG> shows various hardware components of the UE (<NUM>), it is to be understood that other embodiments are not limited thereon. In other embodiments, the UE (<NUM>) may include less or more number of components. Further, the labels or names of the components are used only for illustrative purpose and does not limit the scope of the disclosure. One or more components can be combined together to perform same or substantially similar function to synchronization of group information between the UE (<NUM>), the VAL server (<NUM>) and the SEAL server (<NUM>).

<FIG> is a sequence diagram, illustrating a sequence sending group creation information to the UE (<NUM>), according to an embodiment of the disclosure.

Referring to <FIG>, the VAL client/MSGin5G client (<NUM>) is communicating with the group management client in the SEAL client (<NUM>) and the VAL server/MSGin5G server (<NUM>), which in turn is communicating with the group management server in the SEAL server (<NUM>).

At operation <NUM>, the group management client/SEAL client (<NUM>) of the authorized VAL user/UE (<NUM>)/administrator requests group create operation to the group management server/SEAL server (<NUM>) for creating a VAL group. The identities of the users or UEs being grouped and the information of the VAL services that are to be enabled on the group is included in group create message.

At operation <NUM>, during the group creation, the group management server/SEAL server (<NUM>) creates and stores the information of the group. The group management server/SEAL server (<NUM>) performs a check on the policies e.g., maximum limit of the total number of VAL group members for the VAL group(s) and the like.

At operation <NUM>, the group management server/SEAL server (<NUM>) conditionally notifies the VAL server/MSGin5G server (<NUM>) regarding the group creation with the information of the group members. In an embodiment, when the identity list comprising the list of VAL user IDs or VAL UE IDs that are part of the created group contains the list of VAL user IDs or VAL UE IDs which does not have group management client on the UE (e.g., legacy 3GPP UEs orNon-3GPP UEs), it is responsibility of the VAL server/MSGin5G server (<NUM>) to initiate the group creation notification towards those UEs. The sequence/method of initiating the group creation notification towards legacy 3GPP UEs or Non-3GPP UEs is explained in description of <FIG>.

At operation <NUM>, the VAL group members of the VAL group are notified about the newly created VAL group configuration data. Such notification is sent to the VAL group members having group management client.

At operation <NUM>, the group management server/SEAL server (<NUM>) provides a group creation response to the group management client/SEAL client (<NUM>) of the administrator/authorized VAL user/UE (<NUM>).

In an embodiment, the pre-conditions for the current scenario are: the group management client/SEAL client (<NUM>), the group management server/SEAL server (<NUM>), the MSGin5G server/VAL server (<NUM>) and the VAL group members belong to the same VAL system. The authorized VAL user/UE/administrator is aware of the users' identities which will be combined to form the VAL group. Identity list that is part of the group to be created may contain the list of VAL user IDs or VAL UE IDs which does not have group management client on the UE (e.g., legacy 3GPP UEs or Non-3GPP UEs).

Thus, as seen in the above sequence, the group creation information is successfully shared with the UE (<NUM>) from the SEAL server (<NUM>).

<FIG> is a sequence diagram, illustrating a sequence of fetching group list from the SEAL server (<NUM>), according to an embodiment of the disclosure.

Referring to <FIG>, the VAL client/MSGin5G client (<NUM>) is communicating with the group management client in the SEAL client (<NUM>), which in turn is communicating with the group management server in the SEAL server (<NUM>).

At operation <NUM>, the MSGin5G client/VAL client (<NUM>) sends the group list fetch request to the SEAL client/group management client (<NUM>). The group list fetch request is for sharing the list of groups of in which UE (<NUM>) is a member. The group list fetch request comprises an Identity (ID) of the VAL/MSGin5G UE (<NUM>) sending the request. The group list fetch request also comprises a specified period which indicates the SEAL server (<NUM>) to provide list of the groups created between the specified period. The contents of the group list fetch request is shown in table <NUM>.

At operation <NUM>, the group management client/SEAL client (<NUM>) initiates the group list fetch request towards the SEAL server/group management server (<NUM>). The information elements described in Table (<NUM>) are included in the group list fetch request sent to the SEAL server (<NUM>).

At operation <NUM>, the SEAL server/group management server (<NUM>) checks the authorization of group list fetch request and if authorized, sends the group list fetch response containing list of groups in which the UE (<NUM>) is member. The information elements described in Table (<NUM>) are included in the group list fetch response. The table <NUM> comprises a UE ID/ MSGin5G service of the UE (<NUM>) for whom group list fetch request is received, a list of Group service ID (VAL groups) for which the MSGin5G service ID UE (<NUM>) is member and a result indicating success or failure.

At operation <NUM>, the group management client/SEAL client (<NUM>) notifies the list of groups to the MSGin5G Client /VAL client (<NUM>).

In an embodiment, the pre-conditions for the group to be entered in the group list are as follows: The group is previously defined on the SEAL server (<NUM>) including a list of users of the group. The list of groups to which a VAL UE/ VAL User belongs to is known to the SEAL server (<NUM>) for each of the VAL UE/ VAL User. The MSGin5G UE (<NUM>) (i.e., VAL user) has not received group announcement message as it is offline mode.

Thus, as seen in the above sequence, the group information is successfully shared with the UE (<NUM>) from the SEAL server (<NUM>).

<FIG> is a sequence diagram, illustrating a sequence sending group creation information to the UE (<NUM>), when the group members are legacy 3GPP UE and non-3GPP UEs, according to an embodiment of the disclosure.

Referring to <FIG>, the VAL client/MSGin5G client (<NUM>) is communicating with the VAL server/MSGin5G server (<NUM>), which in turn is communicating with the group management server in the SEAL server (<NUM>). In the embodiment, the UE (<NUM>) does not comprise the SEAL client (<NUM>) and hence the SEAL server (<NUM>) communicates with the VAL server (<NUM>) which in turn communicates with the 3GPP legacy gateway (<NUM>) the non-3GPP Message Gateway (<NUM>).

At operation <NUM>, the SEAL Server/Group management server (<NUM>) sends a group creation notification message to the MSGin5G Server (<NUM>) including the list of identities belonging to different types of UEs i.e., MSGin5G UE, Legacy 3GPP UE and Non-3GPP UE. The contents of the group creation notification are displayed in table <NUM>.

At operation <NUM>, the MSGin5G server/VAL server (<NUM>) determines whether the received group creation notification message has list of identities that belong to Legacy 3GPP UEs or Non-3GPP UEs or both. The MSGin5G server (<NUM>) analyses a registration status of the members in the received identity list and determines if it is to be routed to a Legacy 3GPP UE or Non-3GPP UEs or both and that a group notification message should be sent to those UEs.

In another embodiment, SEAL Server/Group management server (<NUM>) determines whether the received group creation notification message has list of identities that belong to Legacy 3GPP UEs or Non-3GPP UEs or both. The SEAL Server/Group management server (<NUM>) analyses a registration status of the members in the received identity list and determines if it is to be routed to a Legacy 3GPP UE or Non-3GPP UEs or both and that a group notification message should be sent to those UEs.

At operation 406a, upon determining at <NUM> that the group notification message should be sent to Legacy 3GPP UEs, the MSGin5G Server (<NUM>) initiates the group notification message to the legacy 3GPP Message Gateway (<NUM>) for delivery. The information elements defined in Table (<NUM>) are included in the request. At operation 408a the legacy 3GPP Message Gateway (<NUM>) translates the group notification message to a legacy 3GPP message and sends it to the legacy 3GPP message client/UE (<NUM>). In another embodiment, at operation 406b upon determining at operation <NUM> that the group notification message should be sent to non-3GPP UEs, the MSGin5G Server (<NUM>) initiates the group notification message to the non-3GPP Message Gateway (<NUM>) for delivery. The information elements defined in Table (<NUM>) are included in the request. At operation 408b the legacy 3GPP Message Gateway (<NUM>) translates the group notification message to a legacy 3GPP message and sends it to the legacy 3GPP message client/UE (<NUM>).

The pre-condition for the current scenarios are: the MSGin5G Server (<NUM>) interacts with the Server (<NUM>) using the procedures over SEAL-S reference point. The MSGin5G Server (<NUM>) is aware of the legacy 3GPP message client in legacy 3GPP UE (<NUM>) and interacts with it via Legacy 3GPP Message Gateway (<NUM>). The MSGin5G Server is aware of the Non-3GPP message client in Non-3GPP UE (<NUM>) and interacts with it via Non-3GPP Message Gateway (<NUM>). The group creation notification includes identities belonging to different types of UEs i.e., MSGin5G UE, Legacy 3GPP UE and Non-3GPP UE.

Thus, referring to <FIG>, the proposed method and UE (<NUM>) successfully shares the group creation information with the legacy 3GPP UE and the non-3GPP UE.

<FIG> is a schematic diagram, illustrating a sequence for determination of further action after receiving a SEAL-S message, according to an embodiment of the disclosure.

Referring to <FIG>, the SEAL server (<NUM>) is communicating with the VAL/MSGin5G server (<NUM>), which in turn is communicating with the VAL/MSGin5G client (<NUM>).

At operation <NUM>, the SEAL server (<NUM>) sends the SEAL-S message to the VAL server (<NUM>). At operation <NUM>, the VAL server (<NUM>) determines if any further action is required towards the VAL client (<NUM>). At operation <NUM>, the VAL server (<NUM>) initiates the determined action towards the VAL client (<NUM>). In an embodiment, example of further action may be notifying the VAL client (<NUM>) about formation of a new group and the like.

<FIG> is a sequence diagram, illustrating a method flow <NUM> for synchronizing the group information, according to an embodiment as disclosed herein.

Referring to <FIG>, at operation <NUM>, the SEAL client (<NUM>) sends the group creation request to the SEAL server (<NUM>).

At operation <NUM>, upon receiving the group creation request the SEAL server (<NUM>) creates the VAL group and stores information about the VAL group.

At operation <NUM>, the SEAL server (<NUM>) sends the group creation notification to the VAL server (<NUM>). Further, the VAL server (<NUM>) sends the group creation notification to the VAL client (<NUM>).

In an embodiment, the VAL server determines if the identity list of group members received from the SEAL server (<NUM>) comprises legacy 3GPP UE (<NUM>) or non-3GPP UE (<NUM>).

At operation 608a, upon determining that the identity list comprises the legacy 3GPP UE (<NUM>), then the VAL server (<NUM>), send the group notification to the Legacy 3GPP message gateway (<NUM>).

At operation 610a the Legacy 3GPP Message Gateway (<NUM>), sends the group notification received from the SEAL server (<NUM>) to the legacy 3GPP UE (<NUM>).

At operation 608b, upon determining that the identity list comprises the non-3GPP UE (<NUM>), then the VAL server (<NUM>), send the group notification to the non-3GPP message gateway (<NUM>).

At operation 610b the non-3GPP Message Gateway (<NUM>), sends the group notification received from the SEAL server (<NUM>) to the non-3GPP UE (<NUM>).

The various actions, acts, blocks, operations, or the like in the flow diagram <NUM> may be performed in the order presented, in a different order or simultaneously. Further, in some embodiments, some of the actions, acts, blocks, operations, or the like may be omitted, added, modified, skipped, or the like without departing from the scope of the disclosure.

<FIG> is a flow diagram, illustrating a method flow <NUM> for fetching group list of which the UE (<NUM>) is a member, according to an embodiment of the disclosure.

At operation <NUM>, the MSGin5G client (<NUM>) sends the group list fetch request to the SEAL client (<NUM>) for sharing a list of groups for which the UE (<NUM>) is a member, wherein the request comprises the MSGin5G service ID.

At operation <NUM>, the SEAL client (<NUM>) initiates the group list fetch request towards the SEAL server (<NUM>).

At operation <NUM>, the SEAL sever (<NUM>) authorizes the group list fetch request and sends the group list fetch response comprising the list of group for which the UE (<NUM>) is the member in response to the group list fetch request, to the SEAL client (<NUM>).

At operation <NUM>, the SEAL client notifies the MSGin5G client (<NUM>) about the group list fetch response.

<FIG> shows various hardware components of the client (<NUM>) in the wireless communication system, according to various embodiments as disclosed in this application. The client (<NUM>) can be, for example but not limited to a cellular phone, a tablet, a smart phone, a laptop, a Personal Digital Assistant (PDA), a global positioning system, a multimedia device, a video device, an internet of things (IoT) device, a smart watch, a game console, a smart watch, a foldable display device, an Unmanned Aerial Vehicle (UAV), an airplane or the like. The client (<NUM>) may also be referred to by those skilled in the art as a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communications device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, or the like. The client (<NUM>) may also comprise at least one of SEAL client / group management client(<NUM>), MSGin5G client / VAL client(<NUM>), legacy 3GPP UE(<NUM>), or non-3GPP UE(<NUM>) in this application.

In an example embodiment, the client (<NUM>) includes at least one processor (<NUM>) and transceiver (<NUM>). The at least one processor (<NUM>) is coupled with the transceiver (<NUM>). The at least one processor (<NUM>) is configured to perform various processes. The transceiver (<NUM>) is configured for communicating internally between internal hardware components and with external devices via one or more networks. Although the <FIG> shows various hardware components of the client (<NUM>) but it is to be understood that other example embodiments are not limited thereto. In other example embodiments, the client (<NUM>) may include less or more components. Further, the labels or names of the components are used only for illustrative purposes.

<FIG> shows various hardware components of the server (<NUM>) in the wireless communication system, according to various embodiments as disclosed in this application.

The server (<NUM>) comprises various network function entities in core network (e.g. <NUM> CORE). The server (<NUM>) may include at least one of AMF(Access and Mobility Management Function), SMF(Session Management Function), UDM(Unified Data Management), NEF(Network Exposure Function), AUSF(Authentication Server Function), AAA(Authentication, Authorization, and Accounting) Server, AF(Application Function), and/or base station. The server (<NUM>) may also comprise SEAL server / group management server (<NUM>) or MSGin5G server / VAL server (<NUM>) in this application.

In an example embodiment, the server (<NUM>) includes at least one processor (<NUM>) and transceiver (<NUM>). The at least one processor (<NUM>) is coupled with the transceiver (<NUM>). The at least one processor (<NUM>) is configured to perform various processes. The transceiver (<NUM>) is configured for communicating internally between internal hardware components and with external devices via one or more networks. Although the <FIG> shows various hardware components of the server (<NUM>) but it is to be understood that other example embodiments are not limited thereto. In other example embodiments, the network entity (<NUM>) may include less or more components. Further, the labels or names of the components are used only for illustrative purposes.

Claim 1:
A method of a group management client (<NUM>) for a service enabler architecture layer, SEAL, service for a wireless communication system (<NUM>), the method comprising:
receiving, from a vertical application layer, VAL, client (<NUM>), a request for a list of groups in which a VAL user equipment, UE, (<NUM>) of the VAL client is a member;
transmitting, to a group management server (<NUM>) for the SEAL service, a group list fetch request comprising an identity of the VAL UE; and
receiving, from the group management server, a group list fetch response comprising at least one VAL group identifier, ID, indicating the list of the groups; and
notifying, to the VAL client, the list of the groups.