Method and system for handling dynamic group creation in v2x systems

Abstract

A method and apparatus for handling dynamic group creation in a vehicle-to-anything (V2X) system are provided. The method includes allocating, by a first server, a link layer identifier corresponding to dynamic group information, transmitting, by the first server, a push request including the link layer identifier corresponding to the dynamic group information to a first V2X user equipment (UE) from a plurality of V2X UEs, receiving, by the first V2X UE, the link layer identifier corresponding to the dynamic group information, and storing, by the first V2X UE, the link layer identifier corresponding to the dynamic group information.

Description

[0001] This application is a divisional application of patent application No. 201980045582.6, filed on May 13, 2019, with the title “Method and system for handling dynamic group creation in V2X system”. TECHNICAL FIELD

[0002] The present disclosure relates to a vehicle-to-everything (V2X) communication system. More specifically, the present disclosure relates to a method and system for handling dynamic group creation in a V2X communication system. BACKGROUND

[0003] To meet the demand for wireless data traffic having increased since deployment of 4th-generation (4G) communication systems, efforts have been made to develop an improved 5th-generation (5G) or pre-5G communication system. The 5G or pre-5G communication system is also called a 'beyond 4G network' or a 'post long term evolution (LTE) system'. The 5G communication system is considered to be implemented in higher frequency (millimeter-wave) bands, e.g., 60 GHz bands, so as to accomplish higher data rates. To decrease propagation loss of the radio waves and increase the transmission distance, the beamforming, massive multiple-input multiple-output (MIMO), full dimensional MIMO (FD-MIMO), array antenna, analog beam forming, large scale antenna techniques are discussed for use with the 5G communication system. In addition, in the 5G system, development for system network improvement is under way based on advanced small cells, cloud radio access networks (RANs), ultra-dense networks, a device-to-device (D2D) communication, wireless backhaul, a moving network, cooperative communication, coordinated multi-points (CoMP), reception-end interference cancellation and the like. In the 5G system, hybrid mobile key (HMK) and Feher's quadrature amplitude modulation (FQAM) and sliding window superposition coding (SWSC), which are advanced coding modulation (ACM) techniques, and filter bank multi-carrier (FBMC), non-orthogonal multiple access (NOMA), and sparse code multiple access (SCMA), which are advanced access techniques, have been developed.

[0004] The Internet, which is a human centered connectivity network where humans generate and consume information, is now evolving to the Internet of Things (IoT) where distributed entities, such as things, exchange and process information to create a smart world. The Internet of Everything (IoE), which is a combination of the IoT technology and the Big data processing technology through connection with a cloud server, has emerged as an advanced form of the IoT technology. As technology elements, such as "sensing technology", "wired / wireless communication and network infrastructure", "service interface technology", and "security technology" have been demanded for IoT implementation, a sensor network, a Machine-to-Machine (M2M) communication, Machine Type Communication (MTC), and the like have been researched. Such an IoT environment can provide intelligent Internet technology services by collecting and analyzing data generated from connected things. The IoT can be applied to a variety of fields including smart home, smart building, smart city, smart car or connected cars, smart grid, health care, smart appliances, and advanced medical services through aggregation and combination of existing information technology (IT) and various industrial applications.

[0005] In line with this, various attempts have been made to apply 5G communication systems to IoT networks. For example, technologies, such as a sensor network, MTC, and M2M communication, can be implemented by beamforming, MIMO, and array antennas. Application of a cloud RAN as the above-described big data processing technology can also be considered as an example of convergence between the 5G technology and the IoT technology.

[0006] As described above, various services can be provided according to the development of a wireless communication system, and thus methods for easily providing such services are required.

[0007] The above information is presented as background information only to assist with an understanding of the present disclosure. No determination has been made, and no assertion is made, as to whether any of the above might be applicable as prior art with regard to the present disclosure. SUMMARY

[0008] TECHNICAL SOLUTION

[0009] According to an aspect of an example embodiment, there is provided a method and device for handling dynamic group creation in a vehicle-to-everything (V2X) system.

[0010] TECHNICAL EFFECT

[0011] Aspects of the disclosure provide an efficient communication method in a communication system. BRIEF DESCRIPTION OF DRAWINGS

[0012] The above and other aspects, features, and advantages of certain embodiments of the disclosure will be more apparent from the following detailed description taken in conjunction with the accompanying drawings, in which:

[0013] Figure 1FIG. illustrates an overview of a vehicle-to-everything (V2X) system for handling dynamic group creation according to an embodiment of the disclosure;

[0014] Figure 2 FIG. illustrates another overview of a V2X system for handling dynamic group creation according to an embodiment of the disclosure;

[0015] Figure 3 is a block diagram of a V2X user equipment (UE) for handling dynamic group creation according to an embodiment of the disclosure;

[0016] Figure 4 is a block diagram of a server for handling dynamic group creation according to an embodiment of the disclosure;

[0017] Figure 5 is a block diagram of various elements in a V2X UE for handling dynamic group creation according to an embodiment of the disclosure;

[0018] Figure 6 is a block diagram of various elements in a server for handling dynamic group creation according to an embodiment of the disclosure;

[0019] Figure 7 is a sequence diagram illustrating various operations in a platoon leader announcement in an on-network according to an embodiment of the disclosure;

[0020] Figure 8 is a flow diagram illustrating operations for joining a platoon in an on-network according to an embodiment of the disclosure;

[0021] Figure 9 is a flow diagram illustrating operations for leaving a platoon in an on-network according to an embodiment of the disclosure;

[0022] Figure 10 is a flow diagram illustrating operations for merging two or more platoons in an on-network according to an embodiment of the disclosure;

[0023] Figure 11 is a flow diagram illustrating operations for splitting a platoon into more than one platoon in an on-network according to an embodiment of the disclosure;

[0024] Figure 12 is a flow diagram illustrating operations for joining or creating a platoon in an off-network according to an embodiment of the disclosure;

[0025] Figure 13 is a flow diagram illustrating operations for platoon communication in an off-network according to an embodiment of the disclosure;

[0026] Figure 14is a flow diagram illustrating operations for disbanding a platoon in an offline network according to embodiments of the disclosure;

[0027] Figure 15 is a flow diagram illustrating operations for switching between platoons in an offline network according to embodiments of the disclosure;

[0028] Figure 16 is a flow diagram illustrating operations for detecting absence of a platoon leader in an offline network according to embodiments of the disclosure;

[0029] Figure 17 is a flow diagram illustrating existing V2X application layer functional model detailing V2X including functional entities at V2X application layer according to embodiments of the disclosure;

[0030] Figure 18 is a sequence diagram illustrating a step-by-step procedure for handling dynamic group creation according to embodiments of the disclosure;

[0031] Figure 19 is another sequence diagram illustrating a step-by-step procedure for handling dynamic group creation according to embodiments of the disclosure;

[0032] Figure 20 is a sequence diagram illustrating a step-by-step procedure for creating a dynamic group for Uu communication according to embodiments of the disclosure;

[0033] Figure 21 is a sequence diagram illustrating a step-by-step procedure for joining a dynamic group for Uu communication according to embodiments of the disclosure;

[0034] Figure 22 is a sequence diagram illustrating a step-by-step procedure for service continuity of a dynamic group when moving from Uu communication to PC5 communication according to embodiments of the disclosure;

[0035] Figure 23 is a sequence diagram illustrating a step-by-step procedure for creating a dynamic group for PC5 communication according to embodiments of the disclosure;

[0036] Figure 24 is a sequence diagram illustrating a step-by-step procedure for joining a dynamic group for PC5 communication according to embodiments of the disclosure;

[0037] Figure 25 is a sequence diagram illustrating a step-by-step procedure for merging dynamic groups during PC5 communication according to embodiments of the disclosure;

[0038] Figure 26 is a sequence diagram illustrating a step-by-step procedure for merging dynamic groups during PC5 communication according to embodiments of the disclosure;

[0039] Figure 27 is a sequence diagram illustrating a procedure for splitting a dynamic group during PC5 communication according to an embodiment of the disclosure;

[0040] Figure 28 is a flowchart illustrating a method for handling dynamic group creation in a V2X system according to an embodiment of the disclosure;

[0041] Figure 29 is a flowchart illustrating a method for handling dynamic group creation in a V2X system according to an embodiment of the disclosure;

[0042] Figure 30 is a flowchart illustrating a method for handling dynamic group creation in a V2X system according to an embodiment of the disclosure;

[0043] Figure 31 is a flowchart illustrating a method for handling dynamic group creation in a V2X system according to an embodiment of the disclosure; and

[0044] Figure 32 is a block diagram of a UE (V2X UE) according to an embodiment of the disclosure.

[0045] Throughout the drawings, it should be noted that the same reference numbers are used to depict the same or similar elements, features, and structures. DETAILED DESCRIPTION

[0046] Aspects of the disclosure are to address at least the above-mentioned problems and / or disadvantages and to provide at least the advantages described below. Accordingly, an aspect of the disclosure is to provide a method and apparatus for handling dynamic group creation in a vehicle-to-everything (V2X) system.

[0047] Additional aspects will be set forth in part in the description which follows, and in part will become apparent to those skilled in the art upon examination of the following description and / or can be learned by practice of the embodiments.

[0048] According to an aspect of the disclosure, a method for handling dynamic group creation in a V2X system is provided. The method includes assigning, by a first server, a link layer identifier corresponding to dynamic group information. In addition, the method includes transmitting, by the first server, a push request including the link layer identifier corresponding to the dynamic group information to a first V2X user equipment (UE) from a plurality of V2X UEs. In addition, the method includes receiving, by the first V2X UE, the link layer identifier corresponding to the dynamic group information. In addition, the method includes storing, by the first V2X UE, the link layer identifier corresponding to the dynamic group information.

[0049] In an embodiment, the assigning, by the first server, the link layer identifier corresponding to the dynamic group information comprises receiving, by the first server, a dynamic group configuration request corresponding to the dynamic group information from the second server, and assigning, by the first server, the link layer identifier corresponding to the dynamic group information based on the dynamic group configuration request.

[0050] In an embodiment, the receiving, by the first V2X UE, the link layer identifier corresponding to the dynamic group information comprises receiving, by the first V2X UE, a dynamic group configuration request corresponding to the dynamic group information, and receiving, by the first V2X UE, the link layer identifier corresponding to the dynamic group information based on the dynamic group configuration request.

[0051] The method further comprises broadcasting, by the first V2X UE, the link layer identifier corresponding to the dynamic group information to at least one second V2X UE from the plurality of V2X UEs in the V2X system.

[0052] The method further comprises receiving, by the at least one second V2X UE, the link layer identifier corresponding to the dynamic group information from the first V2X UE. Further, the method comprises storing, by the at least one second V2X UE, the dynamic group information and the link layer identifier.

[0053] The method further comprises determining, by the at least one second V2X UE, whether the dynamic group information corresponding to the at least one dynamic group is available in the V2X system. Further, the method comprises transmitting, by the at least one second V2X UE, a dynamic group join request message corresponding to the dynamic group information to the second server in response to the dynamic group information corresponding to the at least one dynamic group being available in the V2X system. Further, the method comprises receiving, by the at least one second V2X UE, a dynamic group join response message corresponding to the dynamic group information from the second server. Further, the method comprises establishing, by the at least one second V2X UE, the dynamic group communication with the first V2X UE in the V2X system via the first communication interface.

[0054] The method further comprises determining, by the at least one second V2X UE, whether the at least one second V2X UE is in an out-of-service area in the V2X system. Further, the method comprises continuing, by the at least one second V2X UE, the dynamic group communication with the first V2X UE by switching from the first communication interface to the second communication interface.

[0055] In an embodiment, the dynamic group information comprises at least one of a dynamic group identifier (ID), a group definition, or a group leader.

[0056] In an embodiment, the link layer identifier is set to a ProSe layer-2 group ID obtained from a pool of link layer identifiers.

[0057] In an embodiment, the first communication interface is a Uu interface and the second communication interface is a PC5 interface.

[0058] According to another aspect of the disclosure, a method for handling dynamic group creation in a V2X system is provided. The method includes receiving, by a first server from a second server, a dynamic group configuration request corresponding to dynamic group information. In addition, the method includes allocating, by the first server, a link layer identifier corresponding to the dynamic group information. In addition, the method includes transmitting, by the first server, a push request including the link layer identifier corresponding to the dynamic group information to a first V2X UE from a plurality of V2X UEs.

[0059] According to another aspect of the disclosure, a method for handling dynamic group creation in a V2X system is provided. The method includes receiving, by a first V2X UE from a plurality of V2X UEs, a push request including a link layer identifier corresponding to dynamic group information from a first server. In addition, the method includes storing, by the first V2X UE, the link layer identifier corresponding to the dynamic group information. In addition, the method includes broadcasting, by the first V2X UE, the link layer identifier corresponding to the dynamic group information to at least one second V2X UE from the plurality of V2X UEs in the V2X system.

[0060] According to another aspect of the disclosure, a method for handling dynamic group creation in a V2X system is provided. The method includes receiving, by a first V2X UE, a link layer identifier corresponding to dynamic group information. In addition, the method includes storing, by the first V2X UE, the link layer identifier corresponding to the dynamic group information. In addition, the method includes broadcasting, by the first V2X UE, the link layer identifier corresponding to the dynamic group information to at least one second V2X UE from the plurality of V2X UEs in the V2X system. In addition, the method includes establishing, by the first V2X UE, a dynamic group communication with the at least one second V2X UE based on the dynamic group information.

[0061] Accordingly, the embodiments herein disclose a V2X system for handling dynamic group creation. A first server is configured to receive a dynamic group configuration request corresponding to dynamic group information from a second server. In addition, the first server is configured to allocate a link layer identifier corresponding to the dynamic group information. The first server is configured to transmit a push request including the link layer identifier corresponding to the dynamic group information to a first V2X UE from a plurality of V2X UEs. The first V2X UE is configured to receive the link layer identifier corresponding to the dynamic group information and store the link layer identifier corresponding to the dynamic group information.

[0062] According to another aspect of the disclosure, a server for handling dynamic group creation in a V2X system is provided. The server includes a processor coupled with a memory. The processor is configured to receive a dynamic group configuration request corresponding to dynamic group information from another server. In addition, the processor is configured to allocate a link layer identifier corresponding to the dynamic group information. In addition, the processor is configured to transmit a push request including the link layer identifier corresponding to the dynamic group information to a first V2X UE from a plurality of V2X UEs.

[0063] According to another aspect of the disclosure, a V2X UE for handling dynamic group creation in a V2X system is provided. The V2X UE includes a processor coupled with a memory. The processor is configured to receive a push request including a link layer identifier corresponding to dynamic group information from a server. In addition, the processor is configured to store the link layer identifier corresponding to the dynamic group information. The processor is configured to broadcast the link layer identifier corresponding to the dynamic group information to at least one second V2X UE from a plurality of V2X UEs in the V2X system. The processor is configured to establish a dynamic group communication with the first V2X UE in the V2X system via a first communication interface.

[0064] According to another aspect of the disclosure, a V2X UE for handling dynamic group creation in a V2X system is provided. The V2X UE includes a processor coupled with a memory. The processor is configured to receive a link layer identifier corresponding to dynamic group information. The processor is configured to store, by a first V2X UE, the link layer identifier corresponding to the dynamic group information. The processor is configured to broadcast the link layer identifier corresponding to the dynamic group information to at least one second V2X UE from a plurality of V2X UEs in the V2X system. The processor is configured to establish a dynamic group communication with the at least one second V2X UE based on the dynamic group information.

[0065] For those skilled in the art, other aspects, advantages and salient features of the disclosure will become clear from the following detailed description, which, taken in conjunction with the annexed drawings, discloses various embodiments of the present disclosure.

[0066] Embodiments

[0067] The following description with reference to the accompanying drawings is provided to assist in a comprehensive understanding of various embodiments of the present disclosure as defined by the claims and their equivalents. It includes various specific details to assist in that understanding but those skilled in the art will recognize that various changes can be made to the various embodiments described herein without departing from the scope and spirit of the present disclosure. In addition, descriptions of well-known functions and constructions can be omitted for clarity and conciseness.

[0068] The terms and words used in the following description and claims are not limited to the literal meanings and are only used to enable a clear and consistent understanding of the present disclosure by the present inventors. Accordingly, it is apparent that the description of various embodiments of the present disclosure provided only for the purpose of illustration is not to be used to limit the present disclosure as defined by the appended claims and their equivalents.

[0069] It will be understood that the singular forms "a," "an," and "the" include plural referents unless the context clearly dictates otherwise. Thus, for example, reference to "a" component can include reference to one or more of such components.

[0070] As is traditional in the field, embodiments can be described and illustrated in terms of blocks that represent one or more functions to be performed by one or more functionally similar components. These blocks, which can be referred to herein as units and / or modules, are physically implemented by analog and / or digital circuitry, such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hardwired circuits, and the like, and can optionally be driven by firmware and / or software. For example, the circuitry can be embodied in one or more semiconductor chips, or on a substrate such as a printed circuit board. The circuitry that forms the blocks can be implemented by specialized hardware, or by a processor such as one or more programmed microprocessors and associated circuitry, or by a combination of specialized hardware and a processor that performs certain functions of the blocks. Each block of the embodiments can be physically separated from another block or blocks, or two or more blocks can be physically combined in a single block without departing from the scope of the disclosure. Likewise, multiple blocks of the embodiments can be physically combined in a single block without departing from the scope of the disclosure.

[0071] The accompanying drawings are used to help easily understand various technical features and will be described in greater detail below. The embodiments presented herein are not limited in scope by the accompanying drawings, as the embodiments in their breadth are defined by the appended claims and equivalents thereof. Although the terms "first", "second", etc. can be used herein to describe various elements, these elements should not be limited by these terms. These terms are generally only used to distinguish one element from another.

[0072] Vehicle communication is expected to make a huge contribution in the development of transportation systems. There are various wireless communication systems that enable a wide range of applications and use cases in a vehicular environment, such as cooperative collision warning or autonomous driving. Vehicle-to-anything (V2X) applications, referred to as V2X, include vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-network (V2N), vehicle-to-pedestrian (V2P). These four types of V2X applications can use "cooperative awareness" to provide more intelligent services for end users. Transportation services and sets of messages associated with transportation services have been defined in various automotive standards development organizations (SDOs), and the Third Generation Partnership Project (3GPP) is working on the transmission of messages. Different V2X scenarios (e.g., vehicle platooning, advanced driving, extended sensors, remote driving, etc.) require the transmission of V2X messages with different performance requirements for 3GPP systems.

[0073] Vehicles using information and communication technology as a highly cooperative group drive are known as vehicle platooning. All vehicles in the platoon receive periodic data from the lead vehicle to perform platooning operations. This information allows the distance between vehicles to become extremely small, i.e., the gap distance converted to time can be very low (sub-second), effectively increasing highway capacity, reducing congestion, and reducing fuel consumption.

[0074] While the vehicle platooning method found in the existing method generally has an organized platoon for platoon management, platoon formation involves vehicles including a predetermined set of platoon leader identification.

[0075] As such, it is desirable to address the above disadvantages or other shortcomings or at least provide a useful alternative.

[0076] The terms "link layer identifier" and "PC5 parameter" are used interchangeably in the present disclosure. The terms "V2X on-network" and "on-network" are used interchangeably in the present disclosure. The terms "V2X off-network" and "off-network" are used interchangeably in the present disclosure.

[0077] A main aspect of embodiments herein is to provide methods and systems for dynamic group management and communication in a V2X system.

[0078] Another aspect of embodiments herein is to provide dynamic platoon formation and management (e.g., joining a platoon, leaving a platoon, splitting a platoon, merging a platoon, etc.).

[0079] Another aspect of the present disclosure is to determine when a platoon needs a new platoon leader.

[0080] Another aspect of the present disclosure is to announce a new leader of a platoon.

[0081] The embodiments herein disclose a method for handling dynamic group creation in a V2X system. The method includes receiving, by a first server, a dynamic group configuration request corresponding to dynamic group information from a second server. Further, the method includes assigning, by the first server, a link layer identifier corresponding to the dynamic group information. Further, the method includes sending, by the first server, a push request comprising the link layer identifier corresponding to the dynamic group information to a first V2X UE of a plurality of V2X UEs. Further, the method includes receiving, by the first V2X UE, the link layer identifier corresponding to the dynamic group information. Further, the method includes storing, by the first V2X UE, the link layer identifier corresponding to the dynamic group information.

[0082] Unlike existing methods and systems, the proposed method can be used to form platoons in a self-organizing manner by dynamically determining a platoon leader. The online network dynamic platoons are formed according to the proposed method, wherein V2X users should join the platoon to communicate with the platoon members. A platoon member can leave the platoon at any time and will not be able to further communicate within that platoon. The platoon is dissolved when there are no platoon members left in the platoon to communicate. Two or more platoons can be merged as needed, which can result in a new platoon leader announcement. Similarly, a platoon can be split into two or more and result in determining a platoon leader for each split platoon.

[0083] In the proposed method, dynamic groups can be formed for specific purposes decided by the V2X system at the application layer. However, the members of the dynamic group are dynamically determined during operation (either with the assistance of a V2X application server or independently by a V2X UE when it is not connected to a network). The proposed system supports the application layer to form V2X dynamic groups by including V2X UEs to groups determined in a self-organizing manner. In a V2X dynamic group, the group management operations that need to be supported include adding or removing members of the group, splitting or merging of the group.

[0084] Further, the system enables application layer V2X dynamic group formation and communication. For V2X dynamic group formation with V2X UEs in Uu communication range, the system provides support to identify V2X UEs from one or more PLMNs that belong to the dynamic group. Further, the system provides PC5 parameters to enable dynamic group communication continuity through V5 provisioning. Further, the system provides support for dynamic group management (adding or removing members, splitting or merging dynamic groups).

[0085] For V2X dynamic group formation with V2X UEs in PC5 communication range, the system provides support to identify V2X UEs that belong to the dynamic group. Further, the system provides support for dynamic group management (adding or removing members, splitting or merging dynamic groups).

[0086] The proposed system supports application layer to form V2X dynamic groups by including V2X UEs (which can be from multiple PLMNs) to groups determined in an ad-hoc manner. In addition, the system enables application layer V2X dynamic group formation and communication. For V2X dynamic group formation with V2X UEs in Uu communication range, the system provides support to identify V2X UEs from one or more PLMNs. In addition, the communication over Uu interface can be one of unicast or multicast or a combination of both. In addition, support for PC5 parameters to enable dynamic group communication continuity over V5 provisioning is provided. In addition, support for dynamic group management is provided. For V2X dynamic group formation with V2X UEs in PC5 communication range, the system provides support to identify V2X UEs belonging to the dynamic group. In addition, support to enable dynamic group communication over V5 is provided. In addition, support for dynamic group management is provided. Group management operations include adding / removing group members and splitting / merging of groups.

[0087] Certain V2X scenarios require group based communication (e.g., platooning). Unlike V2X communication for safety scenarios where communication in the communication range is received by all V2X UEs in the communication range, group based communication expects to be received by V2X UEs only of the group. Dynamic groups can be formed for specific purposes decided at the application layer. However, the members of the dynamic group are determined dynamically during operation (with the assistance of a V2X application server or independently by the V2X UEs when the V2X UEs are not connected to the network). While traditional vehicle platooning methods are limited to organized platooning for fleet management, i.e., platoon formation requires a predetermined set of following vehicles and a platoon leader, the proposed system supports application layer to form V2X dynamic groups by including V2X UEs to groups determined in an ad-hoc manner. In V2X dynamic groups, the group management operations that need to be supported include adding or removing members of the group, splitting or merging of groups. Dynamic platooning can be formed with the assistance of a V2X application server (AS) or independently by the V2X UEs if the V2X UEs are not connected to the network.

[0088] Reference will now be made to the drawings wherein like numerals refer to like components throughout the several figures, and more particularly Figures 1-16 and Figures 18-31 to the drawings which illustrate a preferred embodiment. Figure 1 The drawings illustrate embodiments of the present disclosure.

[0089] Figure 1 FIG. 1 illustrates an overview of a V2X system 1000a for handling dynamic group creation, according to an embodiment of the present disclosure.

[0090] Reference will now be made to the drawings wherein like numerals refer to like components throughout the several figures, and more particularly Figure 1, the V2X system 1000a can be a V2X online network. The V2X system 1000a includes a plurality of V2X UEs 100a-100n and a server 200 including a first server 200a and a second server 200b. The first server 200a is a V2X application enablement (VAE) server and the second server 200b is a V2X application specific server. The first server 200a is configured to receive a dynamic group configuration request corresponding to dynamic group information from the second server 200b. The dynamic group information includes at least one of a dynamic group identifier (ID), a group definition, or a group leader.

[0091] Further, the first server 200a is configured to allocate a link layer identifier corresponding to the dynamic group information. The link layer identifier can be a ProSe layer-2 group ID. The link layer identifier is set to the ProSe layer-2 group ID obtained from a pool of link layer identifiers. Further, the first server 200a is configured to send a push request including the link layer identifier corresponding to the dynamic group information to a first V2X UE 100a from the plurality of V2X UEs 100a-100n. The first V2X UE 100a is configured to receive the link layer identifier corresponding to the dynamic group information and store the link layer identifier corresponding to the dynamic group information.

[0092] In an embodiment, the first V2X UE 100a is configured to broadcast the link layer identifier corresponding to the dynamic group information to at least one second V2X UE from the plurality of V2X UEs 100b-100n in the V2X system 1000.

[0093] In an embodiment, the at least one second V2X UE 100b is configured to receive the link layer identifier corresponding to the dynamic group information from the first V2X UE 100a. Further, the at least one second V2X UE 100b is configured to store the dynamic group information and the link layer identifier. Further, the at least one second V2X UE 100b is configured to determine whether the dynamic group information corresponding to at least one dynamic group is available in the V2X system 1000. Further, the at least one second V2X UE 100b is configured to send a dynamic group join request message corresponding to the dynamic group information to the second server 200b. Further, the at least one second V2X UE 100b is configured to receive a dynamic group join response message corresponding to the dynamic group information from the second server 200b. Further, the at least one second V2X UE 100b is configured to establish a dynamic group communication with the first V2X UE 100a in the V2X system 1000 over the first communication interface.

[0094] In an embodiment, the at least one second V2X UE 100b is configured to determine whether the at least one second V2X UE is in an out-of-service area in the V2X system 1000 and continue the dynamic group communication with the first V2X UE 100a by switching from the first communication interface to the second communication interface. The first communication interface can be a Uu interface and the second communication interface can be a PC5 interface.

[0095] Figure 2 FIGURE 2 illustrates another overview of a V2X system for handling dynamic group creation according to embodiments of the present disclosure.

[0096] Reference Figure 2 , the V2X system 1000b can be a V2X offline network. In an embodiment, the V2X system 1000b includes a plurality of V2X UEs 100a-100n. A first V2X UE 100a from the plurality of V2X UEs 100a-100n is configured to create a dynamic group corresponding to dynamic group information. The first V2X UE 100a generates a link layer identifier according to at least one of a link layer identifier pool or a link layer identifier rule corresponding to the dynamic group information. The first V2X UE 100a sends a push request including the link layer identifier corresponding to the dynamic group information to at least one second V2X UE from the plurality of V2X UEs 100a-100n. The at least one second V2X UE 100b is configured to receive the link layer identifier corresponding to the dynamic group information. In addition, the at least one second V2X UE 100b is configured to store the link layer identifier corresponding to the dynamic group information. In addition, the at least one second V2X UE 100b is configured to broadcast the link layer identifier corresponding to the dynamic group information to at least one third V2X UE from the plurality of V2X UEs 100a-100n in the V2X system 1000. In addition, the at least one second V2X UE 100b is configured to establish a dynamic group communication with the at least one first V2X UE and the at least one third V2X UE based on the dynamic group information.

[0097] Figure 3 is a block diagram of a V2X UE for handling dynamic group creation according to embodiments of the present disclosure.

[0098] Reference Figure 3, the V2X UE 100a includes a processor 110, a memory 120, a communicator 130, and a VAE client 140. The processor 110 is coupled with the memory 120, the communicator 130, and the VAE client 140. The processor 110 is configured to receive, from the first server 200a, a push request including a link layer identifier corresponding to dynamic group information. The processor 110 is configured to store the link layer identifier corresponding to the dynamic group information. The processor 110 is configured to broadcast, in the V2X system 1000, the link layer identifier corresponding to the dynamic group information to at least one second V2X UE from a plurality of V2X UEs 100a-100n. The processor 110 is configured to establish, in the V2X system 1000a, dynamic group communication with the at least one second V2X UE through the first communication interface.

[0099] In an embodiment, the processor 110 is configured to determine whether the at least one second V2X UE is in an out-of-service area in the V2X system 1000b. Based on the determination, the processor 110 is configured to continue the dynamic group communication with the first V2X UE 100a by switching from the first communication interface to the second communication interface.

[0100] In an embodiment, the processor 110 is configured to configure a dynamic group corresponding to the dynamic group information. Further, the processor 110 is configured to generate the link layer identifier according to at least one of a pool of link layer identifiers or link layer identifier rules corresponding to the dynamic group information. Further, the processor 110 is configured to send, to at least one second V2X UE from a plurality of V2X UEs 100b-100n, a push request including the link layer identifier corresponding to the dynamic group information.

[0101] In an embodiment, the processor 110 is configured to receive the link layer identifier corresponding to the dynamic group information. Further, the processor 110 is configured to store the link layer identifier corresponding to the dynamic group information. Further, the processor 110 is configured to broadcast, in the V2X system, the link layer identifier corresponding to the dynamic group information to at least one second V2X UE from a plurality of V2X UEs 100a-100n. Further, the processor 110 is configured to establish dynamic group communication with the at least one second V2X UE based on the dynamic group information.

[0102] The V2X application-specific client 150 provides client-side functionality corresponding to the V2X application (e.g., a platooning client). The V2X application-specific client 150 utilizes the VAE client 140 for V2X application layer support functionality. In an embodiment, the V2X application-specific client 150 is responsible for V2X dynamic group information. In an embodiment, the V2X application-specific client 150 requests the VAE client 140 to configure a dynamic group corresponding to the dynamic group information.

[0103] In an embodiment, the VAE client 140 generates the ProSe layer-2 group ID independently based on a supplied ProSe layer-2 group ID generation rule for its group information, or the VAE client 140 allocates the ProSe layer-2 group ID from a configured pool of ProSe layer-2 group IDs. In addition, the VAE client 140 can further advertise the dynamic group information including the corresponding ProSe layer-2 group ID to other VAE clients within a PC5 communication proximity on a PC5 channel dedicated for V5-AE communication, enabling more V2X UEs to join the dynamic group. The VAE client 140 stores the received PC5 communication parameters corresponding to the dynamic group information received from another VAE client.

[0104] In another embodiment, the VAE client 140 stores the received PC5 communication parameters corresponding to the dynamic group information received from the VAE server 200a. The VAE client 140 can further advertise the dynamic group information including the corresponding ProSe layer-2 group ID to other VAE clients within a PC5 communication proximity on a PC5 channel dedicated for V5-AE communication, enabling more V2X UEs to join the dynamic group.

[0105] The communicator 130 is configured for communicating internally between internal hardware components and communicating with external devices via one or more networks. The VAE client 140 can be, for example, but is not limited to, a V2X application, a platooning application, etc. The memory 120 stores instructions to be executed by the processor 110. The memory 120 can include a non-volatile storage element. Examples of such non-volatile storage elements can include a magnetic hard disk, an optical disk, a floppy disk, a flash memory, or a form of electrically programmable memory (EPROM) or electrically erasable and programmable (EEPROM) memory. In addition, the memory 120 can be considered a non-transitory storage medium in certain examples. The term "non-transitory" can indicate that the storage medium does not specifically

[0106] Although Figure 3 Various hardware components of the V2X UE 100a-100n are shown, but it will be understood that other embodiments are not limited thereto. In other embodiments, the V2X UE 100a-100n can include a fewer or greater number of components. In addition, the labels or names of the components are for illustrative purposes only and do not limit the scope of the present disclosure. One or more components can be combined together to perform the same or substantially similar functions to process the dynamic group creation.

[0107] Figure 4 is a block diagram of a server for handling dynamic group creation according to an embodiment of the disclosure.

[0108] Referring to Figure 4 , the server 200a includes a processor 210, a memory 220, and a communicator 230. The processor 210 is configured to receive a dynamic group configuration request corresponding to dynamic group information from another server 200b. Further, according to an embodiment of the disclosure, the server 200a can be a base station (Node B).

[0109] The processor 210 is configured to allocate a link layer identifier corresponding to the dynamic group information. The processor 210 is configured to transmit a push request including the link layer identifier corresponding to the dynamic group information to a first V2X UE 100a from among a plurality of V2X UEs 100a-100n.

[0110] The communicator 230 is configured for internal communication between internal hardware components and communication with external devices via one or more networks. The memory 220 stores instructions to be executed by the processor 210. The memory 220 can include a non-volatile storage element. Examples of such non-volatile storage elements can include a magnetic hard disk, an optical disk, a floppy disk, a flash memory, or in the form of an EPROM or EEPROM memory. In addition, the memory 220 can be considered a non-transitory storage medium in some examples. The term "non-transitory" can indicate that the storage medium does not specifically embody the carrier wave or propagating signal. However, the term "non-transitory" should not be interpreted to mean that the memory 220 is non-removable. In some examples, the memory 220 can be configured to store a larger amount of information than the memory. In some examples, the non-transitory storage medium can store data that can change over time (e.g., in RAM or a cache).

[0111] Although Figure 4 Various hardware components of the server 200a are illustrated, it will be understood that other embodiments are not limited thereto. In other embodiments, the server 200a can include a less or greater number of components. In addition, the labels or names of the components are used for illustrative purposes only and do not limit the scope of the disclosure. One or more components can be combined together to perform the same or substantially similar functions to handle dynamic group creation.

[0112] Figure 5 is a block diagram of various elements in the processor 110 of the V2X UE 100a-100n for handling dynamic group creation according to an embodiment of the disclosure.

[0113] Referring to Figure 5The processor 110 includes a push request processor 110a, a dynamic group communication establisher 110b, a V2X UE condition determiner 110c, a dynamic group processor 110d, and a link layer identifier processor 110e.

[0114] The push request processor 110a is configured to receive a push request including a link layer identifier corresponding to dynamic group information from the first server 200a. In addition, the push request processor 110a is configured to store the link layer identifier corresponding to the dynamic group information. The dynamic group communication establisher 110b is configured to broadcast the link layer identifier corresponding to the dynamic group information to at least one second V2X UE from the plurality of V2X UEs 100a-100n in the V2X system 1000. The dynamic group communication establisher 110b is configured to establish a dynamic group communication with the at least one second V2X UE in the V2X system 1000a through the first communication interface.

[0115] In an embodiment, the V2X UE condition determiner 110c is configured to determine whether the at least one second V2X UE is in an out-of-service area of the V2X system 1000b. Based on the determination, the dynamic group processor 110d is configured to continue the dynamic group communication with the first V2X UE 100a by switching from the first communication interface to the second communication interface.

[0116] In an embodiment, the dynamic group processor 110d is configured to configure a dynamic group corresponding to the dynamic group information. In addition, the link layer identifier processor 110e is configured to generate the link layer identifier according to at least one of a link layer identifier pool or a link layer identifier rule corresponding to the dynamic group information. In addition, the push request processor 110a is configured to transmit a push request including the link layer identifier corresponding to the dynamic group information to at least one second V2X UE from the plurality of V2X UEs 100b-100n.

[0117] In an embodiment, the push request processor 110a is configured to receive a link layer identifier corresponding to dynamic group information. In addition, the dynamic group communication establisher 110b is configured to establish a dynamic group communication with at least one second V2X UE based on the dynamic group information.

[0118] Although Figure 5 Various hardware components of the processor 110 are illustrated, but it will be understood that other embodiments are not limited thereto. In other embodiments, the processor 110 can include a fewer or greater number of components. In addition, the labels or names of the components are used for illustrative purposes only and do not limit the scope of the present disclosure. One or more components can be combined together to perform the same or substantially similar functions to process dynamic group creation.

[0119] Figure 6is a block diagram of various elements in a processor 210 of a server for handling dynamic group creation according to an embodiment of the disclosure.

[0120] Referring to Figure 6 , the processor 210 includes a dynamic group configuration request receiver 210a, a link layer identifier allocator 210b, and a push request processor 210c. The dynamic group configuration request receiver 210a is configured to receive a dynamic group configuration request corresponding to dynamic group information from another server 200b. The link layer identifier allocator 210b is configured to allocate a link layer identifier corresponding to the dynamic group information. The push request processor 210c is configured to transmit a push request including the link layer identifier corresponding to the dynamic group information to a first V2X UE 100a from a plurality of V2X UEs 100a-100n.

[0121] Although Figure 6 various hardware components of the processor 210 are illustrated, it will be understood that other embodiments are not limited thereto. In other embodiments, the processor 210 can include a less or greater number of components. Additionally, the labels or names of the components are used for illustrative purposes only and do not limit the scope of the disclosure. One or more components can be combined together to perform the same or substantially similar functions to handle dynamic group creation.

[0122] Figure 7 is a sequence diagram illustrating various operations in platoon leader announcement in an online network according to an embodiment of the disclosure.

[0123] Referring to Figure 7 In broadcast type V2X communication, there can be no need to form a group as all entities receiving the broadcast message can consume it. However, before group important V2X communication, a group needs to be formed with a correct set of V2X UEs. If the membership of V2X UEs is already known while the group is being created, such organized group can be created on an application server and used for online network group communication. The same organized group can also be configured for V2X UEs for offline network group communication.

[0124] In organized platooning, a group can be created at any time before V2X communication and a platoon leader can be assigned. However, for on-demand dynamic platooning for instant V2X communication, a dynamic platoon is created and a platoon leader is determined at runtime. The dynamic platoon is ephemeral, i.e., the dynamic group exists until at least one user is using the group for V2X communication. The dynamic platoon can be formed with the help of a network called online network mode (e.g., roadside units (RSUs), application servers, etc.) or formed without the help of a network in offline network mode.

[0125] A V2X UE includes application client (client side functionality corresponding to V2X application) and enabling client (provides client side V2X application layer support functionality) functionalities.

[0126] Online network dynamic platooning : In online network dynamic platooning, V2X users should join the platoon to communicate with the platoon members. A platoon member can leave the platoon at any time and will not be able to further communicate within the platoon. A platoon is dissolved when there are no platoon members left to communicate in the platoon. Two or more platoons can be merged as needed, which can result in a new platoon leader announcement. Similarly, a platoon can be split into two or more and result in determining a platoon leader for each split platoon.

[0127] 1.1) Server 200 : A dynamic platoon is created and maintained by a server 200, which is then used for online network and offline network V2X communication. Examples of such server 200 include V2X application server, RSU, etc. In the case of V2X application server as server 200, each V2X UE of the platoon can belong to different PLMN. In the case of RSU as server 200, V2X UEs of the platoon can belong to different PLMN as long as the PLMNs have service agreements. The application server can further include application specific server (i.e., server side functionality corresponding to V2X application) and application enabling server (i.e., server side V2X application layer support functionality) functionalities.

[0128] 1.2) Platooning information : Platoon information is created and maintained by server 200a for each dynamic platoon. The information includes at least platoon ID, platoon member IDs, platoon leader, platoon source location, platoon destination location, platoon direction, platoon path nodes, platoon creation time, vehicle type (which can include automation level), allowed maximum number of members, ProSe layer-2 platoon ID, etc.

[0129] 1.3) Determining a platoon leader : The platoon leader provides platoon management information, such as platoon speed, platoon lane position, inter-vehicle distance, etc., to the following vehicles. The platoon leader can check commute information fed back from the following vehicles to determine such management information and then provide to the following vehicles. Determining the platoon leader depends on application logic. At any point in time, there will be only one platoon leader for each platoon. The platoon leader can be a vehicle at the front of the platoon, a vehicle that triggered a new platoon creation, a vehicle at the center of the platoon, an RSU, a V2X application server, etc.

[0130] 1.4) Announcing a platoon leader: After the determination of the platoon leader, the platoon members need to know the platoon leader so that the following vehicles react and adapt their respective vehicle's commuting parameters (e.g., speed, lane position, inter-vehicle distance, etc.) to keep the part of the platoon. So, any time the platoon leader changes or a new member joins the platoon, the platoon leader is announced to the whole platoon or specific members of the platoon. Figure 1 The operation description in FIG. 8B describes how the server 200 in the online network initiates the platoon leader announcement to other platoon members.

[0131] Preconditions : A platoon has been created with members.

[0132] Referring to Figure 7 In which the server 200 in which the platoon resides is triggered (e.g., due to the determination of a new platoon leader) to update the platoon members at operation 702. The server 200 sends a platoon leader announcement request to the platoon members (all or specific members as application) at operation 704, which includes the platoon leader to be followed during the platoon communication. At operation 706, the platoon members receiving the announcement store the received platoon leader information. At operation 708, the platoon members receiving the announcement send a platoon leader announcement response to the server 200 to confirm the platoon leader announcement completion.

[0133] Figure 8 FIG. 8B is a flowchart S800 illustrating operations for joining a platoon in an online network system according to an embodiment of the present disclosure.

[0134] Preconditions : The user of the V2X UE 100a has turned on the platoon application on the vehicle and is interested in platooning to travel to a specific destination. The vehicle information, i.e., vehicle type, vehicle location, etc. is accessible by the platoon application. The user has indicated the destination information to the platoon application. The V2X UE 100a is configured with the server 200 / the server 200 is available.

[0135] At operation S802, the server 200 has received a platoon join request from the platoon application on the V2X UE, including vehicle information and user indicated destination information. At operation S804, the server 200 considers the vehicle and user provided information to determine if a relevant platoon already exists. If the platoon does not exist, at operation S806, the server 200 can decide to create a new platoon. Even if such a platoon exists, depending on the request time and other factors, such as the maximum number of members limit for the platoon has been reached, the server 200 can decide to create a new platoon. Otherwise, the server 200 can decide to add the requesting user to an existing platoon. Upon deciding to create a new platoon, the server 200 must generate platoon information. At operation S808, the platoon information needs to determine a platoon leader. The platoon information is then shared with the platoon join request user. At operation S810, when the server 200 decides to include the platoon join request user to an existing platoon, the platoon information is shared with the platoon join request user. At operation S812, upon a new user joining an existing platoon, the server 200 determines if a new platoon leader is needed. At operation S814, if a new platoon leader must be selected, the procedure described in section 1.3 is followed. At operation S816, the procedure described in section 1.4 is followed to announce the new platoon leader. In this case, the announcement is made to all members of the platoon. At operation S818, the platoon formation is complete and the members participate in V2X communication.

[0136] Figure 9 is a flowchart S900 illustrating operations for leaving a platoon in an online network according to embodiments of the present disclosure herein.

[0137] Preconditions The user of the V2X UE has been a member of the platoon. At operation S902, the server 200 has received a leave platoon request from the platoon application on the V2X UE 100a, including the platoon ID the user is leaving. At operation S904, the server 200 checks if the user leaving the platoon is the platoon leader to decide if the platoon continues. At operation S906, the server 200 checks based on policies to dissolve or continue the platoon, for example, the leader leaves the platoon, the last member leaves the platoon, the platoon is dissolved. At operation 908, if the server 200 has decided to dissolve the platoon, the server 200 releases resources and can remove the relevant platoon information from the server 200. At S910, if the platoon leader leaves the platoon, the server 200 determines a new platoon leader as described in section 1.3. At operation S912, the procedure described in section 1.4 is followed to announce the new platoon leader. In this case, the announcement is made to all members of the platoon. At operation S914, the existing platoon members continue to participate in V2X communication.

[0138] Figure 10is a flowchart S1000 illustrating operations for merging two or more platoons in an online network according to embodiments of the present disclosure.

[0139] Preconditions : There are two or more platoons being merged.

[0140] At operation S1002, the server 200 decides to merge two or more platoons based on a policy, e.g., the platoons have destinations on the same path, the platoon members are still within the maximum member limit by merging the platoon members from the platoons being merged. At operation S1004, the server 200 decides to extend from one of the existing platoons that is merging with members of other platoons, thus ensuring the total platoon members are still within the maximum member limit. At operation S1006, the server 200 determines whether a new platoon leader is needed when merging the platoons. At operation S1008, if a new platoon leader must be selected, the procedure described in Section 1.3 is followed. At operation S1010, the updated platoon information (as described in Section 1.2) is shared with all platoon members. At operation S1012, the server 200 disbands the other platoons and releases the resources, except for the relevant platoon information. At operation S1014, the platoon members participate in V2X communication.

[0141] Figure 11 is a flowchart S1100 illustrating operations for splitting a platoon into more than one platoon in an online network according to embodiments of the present disclosure.

[0142] Preconditions : The existing platoon is the one that must be split.

[0143] At operation S1102, the server 200 decides to split the platoon, for example, due to a subset of the platoon members having destinations requiring different paths. At operation S1104, the server 200 decides to move a subset of the platoon members to a newly created platoon and the remaining members continue with the reformed platoon with updated platoon information (described in section 1.2). At operation S1106, when the subset of platoon members move to the new platoon, the server 200 has to decide if there is a platoon leader that can continue with the reformed platoon. At operation S1108, if a new platoon leader has to be selected, the procedure described in section 1.3 is followed. At operation S1110, the updated platoon information (as described in section 1.2) is shared with all members of the reformed platoon. At operation S1112, the existing platoon members continue to participate in V2X communication. At operation S1114, a new platoon is created for the newer destination. At operation S1116, the subset of platoon members from the original platoon move to the new platoon. At operation S1118, upon creation of the new platoon, the server 200 determines the platoon leader following the procedure described in section 1.3. At operation S1120, the procedure described in section 1.4 is followed to announce the new platoon leader. In this case, the announcement is made to all members of the newly created platoon. At operation S1122, the platoon formation is complete and the members participate in V2X communication.

[0144] Figure 12 is a flowchart S1200 illustrating an operation for joining or creating a platoon in an offline network, according to an embodiment of the present disclosure.

[0145] Offline network dynamic platooning : Dynamic platooning in offline networks is created and maintained by individual platoon members. In offline network dynamic platooning, V2X users should either create a new platoon or join an existing platoon if they are aware of one, in order to communicate with other platoon members. A platoon member moving out of the communication range of other platoon members is considered to have left the platoon. A platoon can be released by a platoon member when no communication is received from any other platoon member for a configured amount of time. A platoon member can switch platoons if they are within the communication range of multiple platoons.

[0146] 2.1 Platooning information : In offline networks, platoon information is generated and updated, maintained, and communicated to subsequent platoon members by the platoon leader (or creator of the platoon). This information includes at least platoon ID, platoon member IDs, platoon leader, platoon source location, platoon destination location, platoon direction, platoon creation time, vehicle type (which can include automation level), allowed maximum number of members, ProSe Layer-2 platoon ID, etc.

[0147] 2.2 Determining a platoon leader: The platoon leader provides platoon management information such as platoon speed, platoon lane position, inter-vehicle distance, etc. to the follower vehicles. The platoon leader can check the input from the follower vehicles to determine such management information and then provide to the follower vehicles. Determining the platoon leader depends on the application logic. At any point in time, there will be only one platoon leader for each platoon. In offline networks, the platoon leader can be the vehicle at the front of the platoon, the vehicle that triggered the creation of a new platoon, the vehicle at the center of the platoon, etc. In offline networks, the platoon is inherently highly dynamic due to coverage limitations, but a new platoon leader is determined only in 2 scenarios. When a platoon merges with another platoon (which can have only 1 member), it can result in two platoon leaders. When the leader of the current platoon leaves the platoon, it results in no platoon leader.

[0148] 2.3 Subsequent platoon leaders : After the determination of the new platoon leader, the platoon members need to be updated about the change in the platoon leader so that the follower vehicles react and adapt their respective vehicle's parameters (speed, lane position, inter-vehicle distance, etc.) to maintain their part of the platoon. So any time the platoon leader changes, the new platoon leader announces it to the entire platoon.

[0149] 2.5 Platooning communication and periodic announcement of platooning information : During platoon communication, the V2X UEs share commute information such as traffic information, lane information, speed information, etc. with each other. The platoon leader takes into account the feedback information and generates instructions for the follower vehicles to maintain the platoon. During platoon communication, the platoon leader needs to periodically announce platoon information to non-member V2X UEs that want to join the platoon and to platoon members that want to be aware of the platoon leader available.

[0150] 2.6 Disbanding a platoon : During platoon communication, if a V2X UE decides to end the platoon communication and disband the platoon, it simply stops sending or receiving or processing any communication related to the platoon. If the leader of the platoon decides to end the platoon communication, it eventually results in the follower vehicles detecting the absence of the platoon leader.

[0151] Preconditions : The user has turned on the platoon application on the vehicle and is interested in platooning to travel to a particular destination. The vehicle information, i.e. vehicle type, vehicle location, etc. is accessible by the platoon application. The user has indicated the destination information to the platoon application.

[0152] At operation S1202, the V2X user requests the V2X UE 100a to join the platoon. The user's request to join the platoon includes the destination information.

[0153] Upon receiving the request of the user, at operation S1204, the V2X UE 100a determines whether the V2X UE knows an existing platoon that matches the user's request. To know the existing platoon, the V2X UE 100a can process the periodic platoon announcements received from the existing platoon within the communication range.

[0154] If the V2X UE knows an existing platoon that fits the criteria such as the destination of the platoon, the type of vehicle, etc., then at operation S1206, the V2X UE joins the platoon.

[0155] If the V2X UE 100a does not know an existing platoon that fits the criteria, then at operation S1208, the V2X UE 100a generates new platoon information. The new platoon information includes, but is not limited to, information such as the destination of the platoon, the type of vehicle, the Prose Layer-2 platoon ID, etc.

[0156] At operation S1210, once the platoon information is generated, the V2X UE 100 announces or broadcasts the platoon information to other V2X UEs in the communication range. This broadcast announcement helps other V2X UEs know the existing V2X platoon within the communication range. If the periodic platoon announcement is not received within a configured amount of time, the V2X UE can assume that the platoon is no longer available.

[0157] Once announced, the V2X UEs 100 that are part of the platoon, i.e., the platoon leader and the follower vehicles, share the commute information with each other. The platoon leader takes this feedback information into account and provides instructions to the follower vehicles about the platoon at operation S1212.

[0158] Figure 13 is a flowchart S1300 illustrating operations for platoon communication in an offline network, according to an embodiment of the present disclosure.

[0159] At operation S1302, the platoon communication is active. At operation S1304, the V2X UEs 100 check whether they are the platoon leader. At operation S1306, if the V2X UE 100 is the platoon leader, it starts a timer with a preconfigured value. At operation S1308, the V2X UE waits for the expiration of the timer and continues the platoon communication and the platoon leader responsibilities. At operation S1310, at the expiration of the timer, the V2X UE 100 announces the platoon again for other non-member V2X UEs to join or for the platoon members to know that the platoon leader is available.

[0160] Figure 14 is a flowchart S1400 illustrating operations for dissolving a platoon in an offline network, according to an embodiment of the present disclosure.

[0161] The platoon communication is active at operation S1402. At operation S1404, the V2X UE 100 decides to disband the platoon. The decision can be based on multiple factors such as, but not limited to, not receiving any communication from other platoon members, reaching the destination, deviation in the route such as change in destination, change in vehicle conditions, etc. If the V2X UE decides to disband the platoon, then at operation S1406, it stops processing any communication related to the platoon. If the V2X UE is the leader, then it also stops advertising the platoon.

[0162] Figure 15 is a flowchart S1500 illustrating operations for switching between platoons in an offline network, according to an embodiment of the disclosure.

[0163] Switching platoons and merging : Due to the dynamic nature of the offline network communication, a V2X UE can receive platoon information from different platoon leaders while being part of a platoon. Some of these platoon information can be relevant to the V2X UE receiving it. If the V2X UE receives information of a new platoon that is more suitable for the V2X UE, then the V2X UE can decide to switch platoons. If all members of one platoon switch to another platoon, then a merged platoon results.

[0164] Preconditions : Members of two or more similar platoons in the communication range.

[0165] At operation S1502, in the offline network communication, the V2X UE 100 can receive platoon advertisements from several platoon leaders. At operation S1504, the V2X UE processes the received platoon advertisements to detect and filter platoons that are relevant or similar to the platoon that the V2X UE 100 is part of. This filtered information about other platoons is further analyzed by the V2X UE 100 to find a platoon that the V2X UE 100 can switch to. At operation S1506, a decision is made by the V2X UE 100 or the V2X user about whether to switch the platoon to a different platoon that is more relevant. If the V2X UE 100 or the V2X user decides not to switch the platoon, then at operation S1508, the platoon communication with the current platoon continues. If the V2X UE 100 or the V2X user decides to switch the platoon, then the V2X UE 100 stops all communication with the current platoon and starts communication with the new platoon. At operation S1510, the platoon communication with the selected platoon continues. This platoon communication includes sending periodic platoon advertisements if the V2X UE is the leader of the platoon.

[0166] Figure 16 is a flowchart S1600 illustrating operations when a V2X vehicle detects absence of a platoon leader in an offline network, according to an embodiment of the disclosure.

[0167] Detecting absence of a leader In offline networks, the platoon leader can leave the platoon without informing the follower vehicles. This can happen for multiple reasons, such as the platoon leader changing destination, the platoon leader going out of communication range, etc. In this scenario, the follower vehicles need to monitor the presence of the platoon leader, for example, by monitoring the platoon announcements, and when the absence of the platoon leader is detected, a new platoon leader should be determined.

[0168] At operation S1602, the follower vehicles need to monitor the presence of the platoon leader in the offline network. The follower vehicles can detect the absence of the platoon leader, for example, by not receiving the platoon announcement for a configured time period.

[0169] At operation S1604, upon determining the absence of the platoon leader, a new platoon leader should be selected immediately. To select the new leader of the platoon, the follower vehicles compete by sharing information about their V2X UEs 100 with each other. This information can include elements such as the geographical location of the vehicle, the location of the vehicle, the destination of the vehicle, lane information, speed information, the type of vehicle, etc., and the V2X UE 100 compares its own information with other V2X UEs upon receiving the information from other V2X UEs. Based on the available inputs, the V2X UE 100 determines whether the vehicle is the new platoon leader or not. This decision can be based on input parameters such as the vehicle location.

[0170] At operation S1606, if the V2X UE determines that it is not the platoon leader and there is another follower member that is better suited to be the platoon leader.

[0171] The V2X UE 100 waits to receive a platoon announcement from this other V2X UE 100. If the V2X UE 100 receives the platoon announcement, it continues the platoon communication as mentioned at operation S1608.

[0172] If the V2X UE determines that it is the new platoon leader, at operation S1610, it starts sending periodic platoon announcements to other V2X UEs. The platoon announcement includes information such as the destination of the platoon, the type of vehicle, the inter-vehicle distance, the Prose layer-2 platoon ID, etc.

[0173] At operation S1612, after the determination of the new platoon leader. The platoon communication continues.

[0174] Dynamic platoon continuity moving from online to offline networks. The platoon information (described in section 1.2) created while the V2X UE is online ensures that it is available at the V2X UE even when it enters the offline network. This platoon information continues to be used for offline network V2X communication.

[0175] Dynamic Platooning Continuity from one RSU to another. To help dynamic platooning continuity from one RSU to another, the RSU creating the new platoon stores the platoon information in the central repository. In case the new RSU receives commuter information from unknown V2X platoon, the RSU retrieves the platoon information from the central repository (as described in 1.2) and the new RSU performs the function of the platoon leader.

[0176] Figure 17 The existing V2X application layer functional model of V2X including functional entities at the V2X application layer is illustrated in accordance with embodiments of the present disclosure.

[0177] Reference Figure 17 The V2X application server 200 is composed of a VAE server 200a and a V2X application specific server 200b. The VAE server 200a provides V2X application layer support functions to the V2X application specific server 200b through the Vs reference point. The V2X UE 100a-100n is composed of a VAE client and a V2X application specific client. The VAE client provides V2X application layer support functions to the V2X application specific client. The VAE client communicates with the VAE server through the V1-AE reference point. The V2X application specific client communicates with the V2X application specific server through the V1-APP reference point.

[0178] The VAE client of V2X UE2 communicates with the VAE client of V2X UE1 through the V5-AE reference point. The V2X application specific client of V2X UE2 communicates with the VAE client of V2X UE1 through the V5-APP reference point. V2X UE1 can also act as UE-to-Network relay to enable the VAE client on V2X UE2 to access the VAE server through the V1-AE reference point and the V2X application specific client on V2X UE2 to access the V2X application specific server through the V1-APP reference point.

[0179] The V1-AE messages can be sent over unicast, transparent multicast via xMB, transparent multicast via MB2. The opaque multicast via xMB is triggered by the V1-AE message. The multicast distribution can be supported by both transparent and opaque multicast modes. The VAE server interacts with the 3GPP network system 300 through the V2, MB2, xMB, Rx and T8 reference points. EPS and 5GS are considered as 3GPP network systems. While the traditional vehicle platooning method is limited to organized platooning for fleet management, i.e., platoon formation requires a predetermined set of following vehicles and a platoon leader, the present disclosure focuses on V2X architecture and method to enable vehicles to dynamically form platoons. The dynamic platooning can be formed with the assistance of V2X AS or independently by V2X UE if the V2X UE is not connected to the network.

[0180] Figure 18 is a sequence diagram illustrating the step-by-step procedure of the process for online network dynamic group creation according to an embodiment of the disclosure.

[0181] At operation 1802, the V2X application specific server 200b requests the VAE server 200a to configure a dynamic group corresponding to the dynamic group information. At operation 1804, to enable PC5 communication, the VAE server 200a allocates a ProSe layer-2 group ID from a pool of available ProSe layer-2 group IDs to the received dynamic group information. At operation 1806, the VAE server 200a triggers a push request to the VAE client 140 including the ProSe layer-2 group ID corresponding to the dynamic group information. At operation 1808, the VAE client 140 stores the received PC5 communication parameters corresponding to the dynamic group information received from the VAE server 200a.

[0182] In an embodiment, the V2X application specific server 200b defines the dynamic group, wherein the V2X UE 100 of the VAE client 140 is assigned as the dynamic group leader.

[0183] In an embodiment, the VAE server 200a has a pool of ProSe layer-2 group IDs that can be assigned to the dynamic group.

[0184] In an embodiment, the VAE client 140 can further advertise the dynamic group information including the corresponding ProSe layer-2 group ID to other VAE clients within PC5 communication proximity on a PC5 channel dedicated for V5-AE communication, enabling more V2X UEs to join the dynamic group.

[0185] Figure 19 is a sequence diagram illustrating the step-by-step procedure of the process for offline network dynamic group creation according to an embodiment of the disclosure.

[0186] At operation 1902, the V2X application specific client 2 requests the VAE client 2 to configure a dynamic group corresponding to the dynamic group information. At operation 1904, each VAE client 140 generates a ProSe layer-2 group ID independently based on a generated rule for its provisioned ProSe layer-2 group ID, or the VAE client 2 allocates a ProSe layer-2 group ID from a configured pool of ProSe layer-2 group IDs. At 1906, the VAE client can further advertise the dynamic group information including the corresponding ProSe layer-2 group ID to other VAE clients within PC5 communication proximity on a PC5 channel dedicated for V5-AE communication, enabling more V2X UEs to join the dynamic group. In an embodiment, at operation 1906, the VAE client 140 advertising the dynamic group information indicates itself as the platooning leader of the dynamic group.

[0187] At operation 1908, the VAE client stores the PC5 communication parameters corresponding to the dynamic group information received from another VAE client.

[0188] In an embodiment, when one or more VAE clients are in the coverage area of the VAE server 200a, they are configured with a pool of unique ProSe layer-2 group IDs.

[0189] Figure 20 is a sequence diagram illustrating a procedure for creating a dynamic group for Uu communication in accordance with an embodiment of the present disclosure.

[0190] Referring to Figure 20 , the V2X application specific server 200b is responsible for V2X dynamic group creation (including, for example, group ID allocation, information defining group criteria), member management (e.g., user authorization), checking whether there exists an existing dynamic group for the defined group criteria, regulation and distribution of dynamic group communication over the Uu interface, and interaction with the VAE server 200a. The VAE server 200a is responsible for allocating a ProSe layer-2 group ID from a ProSe layer-2 group ID pool corresponding to the dynamic group creation information provided by the V2X application specific server, and then transmitting the allocation of the ProSe layer-2 group ID and the V2X dynamic group creation information to the VAE client 140 over the V1 reference point.

[0191] Precondition: A V2X user of the second V2X UE 100b requests to create a dynamic group including information required to define group criteria, as shown in operation 2002.

[0192] At operation 2004, the second V2X UE 100b determines whether there exists an existing dynamic group that has been defined in correspondence with the group information provided by the V2X user.

[0193] If the corresponding dynamic group does not exist, at operation 2006, the second V2X UE 100b transmits a create dynamic group request including the group information provided by the V2X user to the V2X application specific server 200b.

[0194] At operation 2008, the V2X application specific server 200b checks V2X user authorization to create a dynamic group, and also checks whether there exists an already defined existing dynamic group corresponding to the group information provided by the V2X user. If the corresponding dynamic group does not exist for the group information provided by the V2X user, the V2X application specific server 200b creates a new dynamic group, allocates a group ID, adds the V2X user as a group member, and defines group criteria.

[0195] At operation 2010, the V2X application specific server 200b includes the relevant information from the created dynamic group in a create dynamic group response and sends to the second V2X UE 100b.

[0196] At operation 2012, the V2X application specific server 200b requests the VAE server 200a to configure a dynamic group for PC5 communication, including the dynamic group ID, V2X group members and group criteria.

[0197] At operation 2014, for enabling PC5 communication, the VAE server 200b allocates a ProSe Layer-2 group ID from the ProSe Layer-2 group ID pool corresponding to the dynamic group creation information provided by the V2X application specific server 200b.

[0198] At operation 2016, the VAE server 200a triggers a push request including PC5 parameters and dynamic group creation information to the VAE client 140 of the second V2X UE 100b requesting to create a dynamic group.

[0199] At operation 2018, the VAE client 140 stores the received PC5 parameters in the second V2X UE 100b.

[0200] At operation 2020, the VAE client 140 broadcasts the PC5 parameters and dynamic group creation information using the ProSe Layer-2 ID received by the V2X UEs 100a-110n in the PC5 communication proximity range, pre-configured per V2X service.

[0201] At operation 2022, upon receiving the broadcast, the VAE client 140 stores the received PC5 parameters and dynamic group creation information in the V2X UE 100a.

[0202] One or more VAE clients 140 receiving the confirmation for dynamic group creation can participate in the group communication over the Uu interface.

[0203] Figure 21 is a sequence diagram illustrating the procedure for joining a dynamic group for Uu communication in steps according to an embodiment of the disclosure.

[0204] Precondition: Upon receiving the broadcast, the first V2X UE 100a has stored the received PC5 parameters and dynamic group creation information, as shown in operation 2102.

[0205] Precondition: The V2X user of the first V2X UE 100a requests to create a dynamic group including the information required to define the group criteria, as shown in operation 2104.

[0206] At operation 2106, the first V2X UE 100a determines whether there is an already defined existing dynamic group corresponding to the group information provided by the V2X user at the second V2X UE 100b.

[0207] If the corresponding dynamic group is determined, at operation 2108, 100a transmits a join dynamic group request including the V2X group ID to the V2X application specific server 200b.

[0208] At operation 2110, the V2X application specific server 200b checks authorization of the V2X user to join the existing dynamic group. If the V2X user is authorized to join the dynamic group, the V2X application specific server 200b adds the V2X user as a group member.

[0209] At operation 2112, the V2X application specific server 200b acknowledges the first V2X UE 100a in a join dynamic group response.

[0210] At operation 2114, the V2X application specific server 200b notifies all existing members of the group of the user associated with the first V2X UE 100a joining the dynamic group.

[0211] One or more VAE clients 140 that are members of the dynamic group can participate in group communication through the Uu interface.

[0212] Figure 22 is a sequence diagram illustrating a procedure of step-by-step steps for service continuity of a dynamic group when moving from Uu communication to PC5 communication according to an embodiment of the disclosure.

[0213] Precondition: At the time of receiving the broadcast, the first V2X UE 100a and the second V2X UE 100b have stored the received PC5 parameters and dynamic group creation information, as shown in operations 2202a and 2202b.

[0214] Precondition: The V2X UEs 100a and 100b that are members of the dynamic group can participate in group communication through the Uu interface, as shown in operations 2204a and 2204b.

[0215] At operations 2206a and 2206b, the V2X UEs 100a and 100b have moved to an area in which they lose connection with the system 1000a.

[0216] At operations 2208a and 2208b, the V2X UEs 100a and 100b of the dynamic group requiring V2X service over Uu interface communication support service continuity within the dynamic group members that have moved to an area where there is no coverage, over the PC5 interface. So, the V2X UEs 100a and 100b of the dynamic group switch to the PC5 communication mode using the parameters configured at operations 2202a and 2202b.

[0217] At operation 2210, one or more VAE clients 140 that are members of the dynamic group and switched to the PC5 communication mode can continue their group communication over the PC5 interface.

[0218] Figure 23 is a sequence diagram illustrating a procedure for creating a dynamic group for PC5 communication according to an embodiment of the disclosure.

[0219] At operation 2302, the V2X UEs 100a-100n are configured with a pool of unique ProSe layer-2 IDs while the V2X UEs 100a-100n are still in the coverage area of the VAE server 200a.

[0220] At operation 2304, when the first V2X 100a is not in the coverage area of the system 1000a, the V2X user associated with the first V2X UE 100a requests to create a dynamic group, providing information required to define group criteria. The first V2X UE 100a determines whether there is an already defined existing dynamic group corresponding to the group information provided by the V2X user.

[0221] At operation 2306, if there is no corresponding dynamic group, the VAE client 140 of the first V2X UE 100a allocates a ProSe layer-2 group ID from the ProSe layer-2 group ID pool corresponding to the dynamic group creation information provided by the V2X user.

[0222] At operation 2308, the VAE client 140 of the first V2X UE 100a triggers a broadcast request including PC5 parameters and dynamic group creation information using the ProSe layer-2 ID received in the PC5 communication proximity range of each V2X service pre-configured and the V2X UEs 100b-100n.

[0223] At operation 2310, upon receiving the broadcast, the VAE client 140 stores the received PC5 parameters and dynamic group creation information in the first V2X UE 100a.

[0224] At operations 2312a and 2312b, one or more VAE clients 140 that receive the PC5 parameters for the dynamic group can participate in group communication over the PC5 interface.

[0225] Figure 24 is a sequence diagram illustrating a procedure for the steps to join a dynamic group for PC5 communication according to an embodiment of the disclosure.

[0226] Precondition: At the time of receiving the broadcast, the VAE client 140 has stored the received PC5 parameters and dynamic group creation information in the second V2X UE 100b, as shown in operation 2402.

[0227] At operation 2404, when the first V2X 100a is not in the coverage area of the system 1000b, the V2X user of the second V2X UE 100b requests to create a dynamic group, providing information required to define group criteria. The second V2X UE 100b determines whether there is an already defined existing dynamic group corresponding to the group information provided by the V2X user.

[0228] If the corresponding dynamic group exists, at operation 2406, the VAE client 140 of the second V2X UE 100b uses the stored PC5 parameters for the dynamic group, and can participate in group communication through the PC5 interface.

[0229] Figure 25 is a sequence diagram illustrating a procedure for the steps to merge a dynamic group during PC5 communication according to an embodiment of the disclosure.

[0230] Precondition: According to a request of the V2X user of the V2X UE 1 (not in the coverage area of the system 1000a), a dynamic group has been created and broadcasted PC5 parameters and dynamic group creation information through the PC5 interface. However, the VAE client 140 of the third V2X UE 100c is not in the proximity range of PC5 communication with the first V2X UE 100a, and has not received the broadcast from the VAE client 140 of the first V2X UE 100a, as shown in operation 2502.

[0231] The V2X user of the third V2X UE 100c requests to create a dynamic group, providing information required to define group criteria. The third V2X UE 100c determines that there is no already defined existing dynamic group corresponding to the group information, and allocates a ProSe layer-2 group ID from a ProSe layer-2 group ID pool.

[0232] At operation 2504, the VAE client 140 of the third V2X UE 100c triggers a broadcast request including PC5 parameters and dynamic group creation information, using ProSe layer-2 IDs received from V2X UEs 100a and 100b in the PC5 communication proximity range, pre-configured for each V2X service.

[0233] At operation 2506, upon receiving the broadcast from the third V2X UE 100c, the VAE client 140 at the first V2X UE 100a determines that there exists an already existing dynamic group for the same group criteria.

[0234] At operation 2508, the VAE client 140 at the first V2X UE 100a triggers a broadcast request including PC5 parameters and dynamic group creation information using the preconfigured per V2X service and the ProSe Layer-2 ID received by the V2X UE in the PC5 communication proximity of the third V2X UE 100c.

[0235] The VAE client 140 at the third V2X UE 100c analyzes that there exists an existing dynamic group and stops using the ProSe Layer 2 ID assigned at operation 2504.

[0236] At operation 2510, the VAE client 140 stores the received PC5 parameters and dynamic group creation information in the first V2X UE 100a.

[0237] At operation 2512, the V2X UEs 100a-100c participate in the dynamic group communication using the ProSe Layer 2 ID assigned at operation 2502 over the PC5 interface.

[0238] Figure 26 is a sequence diagram illustrating the steps of a procedure for merging dynamic groups during PC5 communication according to an embodiment of the disclosure.

[0239] Precondition: A dynamic group has been created and broadcasted PC5 parameters and dynamic group creation information over the PC5 interface as shown at operation 2602, upon request of a V2X user associated with the first V2X UE 100a (not in the coverage area of the system 1000a). However, the VAE client 140 at the third V2X UE 100c is not in the proximity of PC5 communication with the first V2X UE 100a and does not receive the broadcast from the VAE client 140 at the first V2X UE 100a.

[0240] At operation 2604, upon request of a V2X user at the third V2X UE 100c to create a dynamic group, the information required to define the group criteria is provided. The third V2X UE 100c determines that there is no already defined existing dynamic group corresponding to the group information and allocates a ProSe Layer-2 group ID from the ProSe Layer-2 group ID pool.

[0241] At operation 2606, the VAE client 140 at the V2X UE 100a triggers a broadcast request including PC5 parameters and dynamic group creation information using each V2X service pre-configuration and the ProSe Layer-2 ID received by the V2X UE in the PC5 communication proximity range.

[0242] At operation 2608, upon receiving the broadcast from the third V2X UE 100c, the VAE client 140 at the first V2X UE 100a determines that there already exists an existing dynamic group for the same group criteria.

[0243] At operation 2610, the VAE client 140 at the first V2X UE 100a stops using the ProSe Layer 2 ID assigned at operation 2602. The VAE client 140 at the V2X UE 100a stores the received PC5 parameters and dynamic group creation information in the V2X UE.

[0244] At operation 2612, the V2X UEs 100a-100c participate in the dynamic group communication using the ProSe Layer 2 ID assigned at operation 2608 over the PC5 interface.

[0245] Figure 27 is a sequence diagram illustrating the steps of a procedure for splitting a dynamic group during PC5 communication according to an embodiment of the disclosure.

[0246] Precondition: One or more VAE clients 140 participate in the dynamic group communication using the ProSe Layer-2 ID corresponding to the dynamic group over the PC5 interface, as shown at operation 2702.

[0247] At operation 2704, the VAE client 140 at the first V2X UE 100a stops using the ProSe Layer-2 ID being used for communication in operation 2702.

[0248] At operation 2706, when a V2X user at the third V2X UE 100c decides to create a new group for the same group criteria, the steps in Figure 23 are followed, resulting in the assignment of a new ProSe Layer 2 group ID. The third V2X UE 100c participates in the dynamic group communication using the ProSe Layer 2 ID assigned at operation 2706 over the PC5 interface.

[0249] Figure 28 is a flowchart S2800 illustrating a method for handling dynamic group creation in a V2X system 1000a according to an embodiment of the disclosure.

[0250] Operations S2802-S2806 are performed by the processor 210. At operation S2802, the method includes receiving, from the second server 200b, a push request including a link layer identifier corresponding to dynamic group information. At operation S2804, the method includes assigning the link layer identifier corresponding to the dynamic group information. At operation S2804, the method includes transmitting, to a first V2X UE 100a from the plurality of V2X UEs 100a-100n, a push request including the link layer identifier corresponding to the dynamic group information.

[0251] Figure 29 FIG. 29 is a flowchart S2900 illustrating a method for handling dynamic group creation in a V2X system 1000a according to an embodiment of the disclosure.

[0252] Operations S2902-S2906 are performed by the processor 110. At operation S2902, the method includes receiving, from the first server 200a, a push request including a link layer identifier corresponding to dynamic group information. At operation S2904, the method includes storing the link layer identifier corresponding to the dynamic group information. At operation S2906, the method includes broadcasting, in the V2X system 1000a, the link layer identifier corresponding to the dynamic group information to at least one second V2X UE from the plurality of V2X UEs 100a-100n.

[0253] Figure 30 FIG. 31 is a flowchart S3100 illustrating a method for handling dynamic group creation in a V2X system 1000b according to an embodiment of the disclosure.

[0254] Operations S3002-S3006 are performed by the processor 110. At operation S3002, the method includes configuring a dynamic group corresponding to dynamic group information. At operation S3004, the method includes generating a link layer identifier according to at least one of a link layer identifier pool or a link layer identifier rule corresponding to the dynamic group information. At operation S3006, the method includes transmitting, to at least one second V2X UE from the plurality of V2X UEs 100a-100n, a push request including the link layer identifier corresponding to the dynamic group information.

[0255] Figure 31 FIG. 31 is a flowchart S3100 illustrating a method for handling dynamic group creation in a V2X system 1000b according to an embodiment of the disclosure.

[0256] Processor 110 executes operations S3102-S3108. In operation S3102, the method includes receiving a link layer identifier corresponding to dynamic group information. In operation S3104, the method includes storing the link layer identifier corresponding to the dynamic group information. In operation S3106, the method includes broadcasting the link layer identifier corresponding to the dynamic group information to at least one second V2X UE from a plurality of V2X UEs 100a-100n in the V2X system 1000. In operation S3108, the method includes establishing dynamic group communication between a first V2X UE 100a and at least one second V2X UE based on the dynamic group information.

[0257] Figure 32 This is a block diagram of a V2X UE according to an embodiment of the present disclosure.

[0258] refer to Figure 32 The V2X UE 3200 may include a processor 3210, a transceiver (e.g., a communicator) 3220, and a memory 3230. However, not all of the components shown in the figures are mandatory. The V2X UE 3200 may be composed of, for example... Figure 32 The implementation may involve more or fewer components. Alternatively, according to another embodiment, the processor 3210, transceiver 3220, and memory 3230 can be implemented as a single chip. The V2X UE 3200 can correspond to... Figure 3 The V2X UE. The processor 3210 can correspond to... Figure 5 The processor 110. The above components will now be described in more detail.

[0259] Processor 3210 may include one or more processors or other processing means for controlling the proposed functions, processes, and / or methods. Operation of user equipment 3200 may be implemented by processor 3210. The processor is operable to perform embodiments of this disclosure, and the operation of processor 3210 may correspond to... Figure 5 The processor 110.

[0260] Transceiver (e.g., communicator) 3220 may include an RF transmitter for up-converting and amplifying the transmitted signal, and an RF receiver for down-converting the frequency of the received signal. However, according to another embodiment, transceiver 3220 may be implemented with more or fewer components than those illustrated in the components diagram.

[0261] Transceiver 3220 can be connected to processor 3210 and send and / or receive signals. Signals may include control information and data. Additionally, transceiver 3220 can receive signals and output signals to processor 3210 via a wireless channel. Transceiver 3220 can also transmit signals output from processor 3210 via a wireless channel.

[0262] The memory 3230 can store control information or data included in a signal obtained by the V2X UE 3200. The memory 3230 can be connected to the processor 3210 and store at least one instruction or a protocol or a parameter for the proposed functions, processes, and / or methods. The memory 3230 can include a read-only memory (ROM) and / or a RAM and / or a hard disk and / or a compact disk (CD)-ROM and / or a digital versatile disk (DVD) and / or other storage means.

[0263] The various actions, acts, blocks, steps, or the like in flowcharts S800-S1600 and S2800-S3100 can be executed in the order presented, in a different order or simultaneously. Further, in some embodiments, certain actions, acts, blocks, steps, or the like can be omitted, added, modified, skipped, or the like without departing from the scope of the disclosure.

[0264] Embodiments disclosed herein can be implemented using at least one software program running on at least one hardware device and performing network management functions to control the elements.

[0265] While the disclosure has been illustrated and described with reference to various embodiments thereof, it will be understood by those skilled in the art that various changes in form and details can be made therein without departing from the spirit and scope of the disclosure as defined by the appended claims and their equivalents.

Claims

1. A method executed by a VAE client enabling a vehicle-to-everything (V2X) application for switching group communication modes in a V2X system, comprising: Receive a push request from the VAE server, which includes PC5 parameters configured for V2X dynamic groups and dynamic group information, wherein the dynamic group information includes a dynamic group identifier ID; Storage configuration for PC5 parameters of V2X dynamic groups; A VAE client participates in group communication with at least one V2X User Equipment (UE) via the Uu interface, wherein the at least one V2X UE is a member of a V2X dynamic group; Provide PC5 parameters and dynamic group information to at least one V2X UE; Identify whether a connection involving at least one V2X UE has been lost in group communication via the Uu interface; In response to a lost connection via the Uu interface, the VAE client, based on the stored configuration of the PC5 parameters for V2X dynamic groups, will switch the group communication mode via the Uu interface to the group communication mode via the PC5 interface; and The VAE client communicates with at least one V2X UE execution group via the PC5 interface.

2. The method as described in claim 1, wherein, The VAE client communicates with at least one V2X UE on the PC5 channel, which is dedicated to V5-AE communication.

3. The method as described in claim 1, wherein, Dynamic group information also includes at least one of the following: information about the group definition or information about the group leader.

4. The method of claim 1, wherein, The dynamic group information corresponds to the ProSe layer-2 group identifier ID of the VAE client.

5. The method of claim 4, wherein, The ProSe layer-2 group IDs obtained from the pool of ProSe layer-2 group IDs are assigned by the VAE server.

6. A vehicle-to-everything (V2X) application enabling VAE client for switching group communication modes in a vehicle-to-everything (V2X) system, comprising: Memory; as well as The processor coupled to the memory is configured as follows: Receive a push request from the VAE server, including PC5 parameters configured for V2X dynamic groups and dynamic group information, wherein the dynamic group information includes a dynamic group identifier ID. Storage configuration for PC5 parameters of V2X dynamic groups, A VAE client participates in group communication with at least one V2X User Equipment (UE) via the Uu interface, wherein the at least one V2X UE is a member of a V2X dynamic group. Provide PC5 parameters and dynamic group information to at least one V2X UE. Identify whether a connection involving at least one V2X UE has been lost in group communication via the Uu interface. In response to a lost connection via the Uu interface, the storage-based configuration of the PC5 parameters for V2X dynamic groups will switch the group communication mode from the Uu interface to the PC5 interface. Communicates with the at least one V2X UE execution group via the PC5 interface.

7. The VAE client as described in claim 6, wherein, The VAE client communicates with at least one V2X UE on the PC5 channel, which is dedicated to V5-AE communication.

8. The VAE client as described in claim 6, wherein, Dynamic group information also includes at least one of the following: information about the group definition or information about the group leader.

9. The VAE client as described in claim 6, wherein, The dynamic group information corresponds to the ProSe layer-2 group identifier ID of the VAE client.

10. The VAE client as described in claim 9, wherein, The ProSe layer-2 group IDs obtained from the pool of ProSe layer-2 group IDs are assigned by the VAE server.

Images