Group communication method and related products

By using group keys and hash functions in V2X technology to convert application layer group identification into destination L2 ID, the problem of lack of conversion mechanism in the existing technology is solved, and a secure and privacy end-to-end grouping is achieved. Communication.

CN114616844BActive Publication Date: 2024-11-29HUAWEI TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN201980101772.5
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2019-11-08
Publication Date
2024-11-29
Estimated Expiration
2039-11-08

AI Technical Summary

Technical Problem

The lack of mechanisms for converting application layer group identification into destination L2 IDs in the prior art, resulting in the inability to achieve end-to-end group communication and there are problems of insufficient security and privacy protection.

Method used

By passing a packet carrying the current destination ID between user devices and using the group key and hash function for ID conversion, ensuring that the application layer group ID is safely converted to the destination L2 ID, preventing opponents from tampering and Connect the destination L2 ID to the UE group membership relationship.

Benefits of technology

End-to-end group communication is realized, ensuring the security and privacy of communication, reducing computing costs and delays, and enhancing the security of the conversion process.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN114616844B_ABST
    Figure CN114616844B_ABST
Patent Text Reader

Abstract

A group communication method and related products are provided. In the method, a first user device obtains a group identifier (ID), which is used to identify a group including at least a first user device and a second user device; the first user device determines a current destination ID according to the group ID, and sends a packet carrying the current destination ID to the second user device. According to the group communication method and device provided by the present disclosure, the application layer group ID is converted into a destination L2ID, thereby realizing end-to-end group communication.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present disclosure relates to the field of V2X technology, and in particular to a group communication method and related products. Background Art

[0002] The so-called vehicle to everything (V2X), which is similar to the popular business to business (B2B) and business to costumer (B2C), refers to the information exchange between the vehicle and the outside world. The Internet of vehicles has laid a new direction for automotive technology by integrating global positioning system (GPS) navigation technology, vehicle-to-vehicle communication technology, wireless communication and remote sensing technology, and has achieved compatibility between manual and autonomous driving.

[0003] The 3rd generation partnership project (3GPP) TR 23.786 focuses on the study of architectural enhancements to the evolved packet system (EPS) and 5G system (5GS) to support advanced V2X services. Solution #21 "Group communication enhancements for NR PC5" was selected as the baseline for the specification work to address KI #1 "Support for enhanced V2X (eV2X) group communication". Combined with the Figure 5 .4.1-1, since the lower layer cannot directly use the upper layer identifier (ID), the group identifier provided by the application layer will be converted into a destination L2 identifier (layer 2 identifier, L2 ID). However, there is no mechanism for the conversion in the related art.

[0004] The purpose of providing this background information is to reveal information that the applicant believes may be relevant to the present disclosure. It is not necessary to admit, nor should it be construed, that any of the foregoing information constitutes prior art against the present disclosure. Summary of the invention

[0005] In view of this, in order to solve the above problems, the present disclosure provides a group communication method and related products.

[0006] The above and other objects are achieved by the subject matter claimed in the independent claims. Other implementations are apparent from the dependent claims, the description and the drawings.

[0007] A first aspect of the present disclosure relates to a group communication method, comprising: a first user device obtains a group identifier (ID), wherein the group identifier is used to identify a group including at least the first user device and a second user device; the first user device determines a current destination ID based on the group ID, wherein the current destination ID is used to identify the second user device in the group; and the first user device sends a packet carrying the current destination ID to the second user device.

[0008] According to the solution provided by the present disclosure, the application layer group ID is converted into a destination L2 ID, thereby achieving end-to-end group communication.

[0009] According to the first aspect, in a possible implementation of the method, the first user device determines the current destination ID according to the group ID, including: the first user device obtains at least one parameter for determining the current destination ID; the first user device determines the current destination ID according to the group ID and the at least one parameter. Wherein, the first user device determines the current destination ID according to the group ID and the at least one parameter, including: the first user device determines whether a trigger condition is met; in response to determining that the trigger condition is met, the first user device generates the current destination ID according to the group ID and the at least one parameter; in response to determining that the trigger condition is not met, the first user device determines the previously generated destination ID as the current destination ID.

[0010] According to the solution provided by the present disclosure, the conversion of the destination ID can be performed multiple times, thereby ensuring that the application layer group ID is securely converted to the destination L2 ID, and the conversion process cannot be tampered with by an adversary. The adversary cannot connect the destination L2 ID and the UE group membership, thereby protecting the integrity and privacy of the member UEs. Since the destination L2 ID is not encrypted, the UE only decrypts the message or only listens to the message sent to itself, thereby reducing the computing cost and reducing the latency (although this may not apply to the first conversion process, it is beneficial to subsequent conversions). In addition, the random number is sent arbitrarily, which further ensures the security of the conversion process.

[0011] A second aspect of the present disclosure relates to a group communication method, comprising: a second user device receives a packet carrying a current destination identification (ID), wherein the current destination ID is used to identify the second user device in a group, the group including at least a first user device and the second user device; the second user device verifies the current destination ID in the received packet through a local destination ID.

[0012] According to the solution provided by the present disclosure, the application layer group ID is converted into a destination L2 ID, thereby achieving end-to-end group communication.

[0013] In a possible implementation of the method described in the second aspect, the method further includes: the second user device obtains a group ID, wherein the group ID is used to identify the group; the second user device obtains at least one parameter for determining the local destination ID; the second user device determines the local destination ID according to the group ID and the at least one parameter. The second user device determines the local destination ID according to the group ID and the at least one parameter, including: the second user device determines whether there is an encrypted random number in the received packet; in response to determining that there is an encrypted random number in the received packet, the second user device decrypts the encrypted random number by using the at least one parameter, and the second user device generates the local destination ID according to the group ID using a hash function and the decrypted random number; in response to determining that there is no encrypted random number in the received packet, the second user device determines the previously generated local destination ID as the local destination ID.

[0014] According to the solution provided by the present disclosure, the conversion of the destination ID can be performed multiple times, thereby ensuring that the application layer group ID is securely converted to the destination L2 ID, and the conversion process cannot be tampered with by an adversary. The adversary cannot connect the destination L2 ID and the UE group membership, thereby protecting the integrity and privacy of the member UEs. Since the destination L2 ID is not encrypted, the UE only decrypts the message or only listens to the message sent to itself, thereby reducing the computing cost and delay.

[0015] A third aspect of the present disclosure relates to a first user device, comprising a memory, a processor, an input interface, and an output interface. The memory, the processor, the input interface, and the output interface are interconnected via a bus system. The memory is used to store instructions, and the processor is used to execute the instructions stored in the memory to execute the method described in the first aspect or any possible implementation of the first aspect.

[0016] A fourth aspect of the present disclosure relates to a second user device, comprising a memory, a processor, an input interface, and an output interface. The memory, the processor, the input interface, and the output interface are interconnected via a bus system. The memory is used to store instructions, and the processor is used to execute the instructions stored in the memory to execute the method described in the second aspect or any possible implementation of the second aspect.

[0017] A fifth aspect of the present disclosure relates to a computer storage medium storing computer executable instructions, which, when executed, is used to implement the method described in the first aspect or the second aspect of the present disclosure and any possible implementation thereof.

[0018] A sixth aspect of the present disclosure relates to a computer program product comprising instructions, which, when executed on a computer, enables the computer to execute the method described in the first aspect or the second aspect above or any possible implementation thereof. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] The accompanying drawings are used to provide a further understanding of the present disclosure, constitute a part of the specification, and are used together with the following specific embodiments to explain the present disclosure, but should not be interpreted as limiting the present disclosure. In the accompanying drawings:

[0020] Figure 1 A schematic flow chart of a group communication method provided by an embodiment of the present disclosure;

[0021] Figure 2 A schematic flow chart of a group communication method provided by an embodiment of the present disclosure;

[0022] Figure 3 A schematic flow chart of a group communication method provided by an embodiment of the present disclosure;

[0023] Figure 4 A schematic flow chart of a group communication method provided by an embodiment of the present disclosure;

[0024] Figure 5 A schematic flow chart of a group communication method provided by an embodiment of the present disclosure;

[0025] Figure 6 A schematic flow chart of a group communication method provided by an embodiment of the present disclosure;

[0026] Figure 7 A schematic diagram of the structure of a first user equipment provided in an embodiment of the present disclosure;

[0027] Figure 8 A schematic diagram of the structure of a second user equipment provided in an embodiment of the present disclosure;

[0028] Fig. 9 A schematic block diagram of a first user equipment provided in an embodiment of the present disclosure;

[0029] Fig.10 A schematic block diagram of a second user equipment provided in an embodiment of the present disclosure. DETAILED DESCRIPTION

[0030] The following description will refer to the accompanying drawings that form a part of the present disclosure, and the accompanying drawings show specific aspects of the embodiments of the present disclosure or show specific aspects in which the embodiments of the present disclosure can be used in an illustrative manner. It should be understood that the embodiments of the present disclosure can be used in other aspects and may include structural or logical changes not depicted in the drawings. Therefore, the following detailed description should not be understood in a restrictive sense, and the scope of the present disclosure is defined by the appended claims.

[0031] For example, it should be understood that the disclosure related to the described method may also be applicable to the corresponding device or system for performing the method, and vice versa. For example, if one or more specific method steps are described, the corresponding device may include one or more units such as functional units to perform the one or more method steps described (for example, one unit performs one or more steps, or multiple units perform one or more steps of multiple steps respectively), even if such one or more units are not explicitly described or illustrated in the drawings. On the other hand, for example, if a specific device is described according to one or more units such as functional units, the corresponding method may include a step to perform the function of one or more units (for example, one step performs the function of one or more units, or multiple steps perform the function of one or more units of multiple units respectively), even if such one or more units are not explicitly described or illustrated in the drawings. Further, it is understood that, unless otherwise explicitly stated, the features of the various exemplary embodiments and / or aspects described herein may be combined with each other.

[0032] Before describing the present disclosure, several terms that may be used herein are briefly explained.

[0033] A user device may also be referred to as a terminal device, terminal station or user equipment and may be any of the following devices: a smartphone, a mobile phone, a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a handheld device capable of wireless communication, a vehicle-mounted device, a wearable device, a computing device or other processing device connected to a wireless modem.

[0034] In group communication, the destination layer 2 (layer 2, L2) ID identifies the target of the data in the sidelink proSe direct communication, and the group key is issued by the application layer, especially the group management server, for each group to which the user equipment (UE) belongs. In fact, the group key is shared by the group members and is used to convert the group ID to the destination L2 ID.

[0035] It is assumed that a group ID is associated with both data traffic and control traffic. During group communication, the group ID may change or may not change, and the present disclosure does not limit this. For ease of description, it is assumed that the group ID remains unchanged during group communication. However, these solutions can still be applied to situations where the group ID changes after slight modifications, and the details will be described in the following embodiments.

[0036] Further, for data traffic from the application layer and without an associated group ID, the V2X layer handles the data traffic through traditional operations, i.e., the default provider service identifier (PSID) / intelligent transport system (ITS)-application identifier (AID) mapping is used to determine the destination L2 ID. In addition, a unicast link / multicast group can be assigned a flow identifier when it is established. The corresponding connection profile information, such as L2 ID, transmission settings, quality of service (QoS) parameters, etc., can be associated with the flow identifier. In this case, the upper layer only needs to use the flow identifier to indicate the destination and pass the flow identifier down with the data packet. Further, when the application layer passes down the data packet associated with the group ID, the V2X layer marks the data packet with the configured QoS settings (5G quality of service (QoS) indicator (abbreviated as 5QI) and distance (range)), and passes these configured QoS settings down to the AS layer. The V2X layer also indicates to the AS layer that the packet is for group communication in order to distinguish the packet from broadcast traffic.

[0037] It should be noted that one possible application scenario may be vehicle-to-everything (V2X) group communication. However, the disclosure is only described here using V2X group communication as an example, but this should not be interpreted as a limitation on the solution provided by the disclosure. The solution proposed in the disclosure may also be applied to other scenarios where appropriate.

[0038] As described above, there is no mechanism for the above conversion in the related art. However, if the group key is used to directly encrypt all elements, that is, the entire data packet including the L2 ID, the receiving UE cannot know which multicast messages are directed to them, and therefore all encrypted messages must be decoded, thereby increasing the computational cost of the receiving UE. The receiving UE listens to messages sent to itself based on the destination L2 ID. If the destination L2 ID is encrypted, the receiving UE must decode all received messages to find the message sent to itself. In response to this problem, the embodiments of the present disclosure provide a solution, namely, converting the group ID into the destination L2 ID without increasing the computational cost of the UE.

[0039] Moreover, the conversion from the group ID to the destination L2 ID can be security-protected in terms of confidentiality and traceability. Unless the conversion is performed carefully, the group membership of a specific user equipment (UE) may be revealed. For example, an attacker may be able to query whether there are any members of a group at a certain location. If the application layer group ID is not securely converted by the V2X layer, an intruder may link back to the UE group membership. An intruder may also tamper with the conversion process to generate a false destination layer 2 ID. Therefore, in order to securely convert the group ID provided by the application layer into the destination layer 2 ID, a hash function is introduced in some embodiments of the present disclosure, wherein the hash function is used by the V2X layer to securely convert the application layer group ID into the destination L2 ID. In addition, a group key is used to securely convert the ID. This will be described in detail below in conjunction with the embodiments.

[0040] The embodiments of the present disclosure will be described in detail below with reference to the accompanying drawings.

[0041] Figure 1 A schematic flow chart of a group communication method provided in an embodiment of the present disclosure. The method can be executed by a first user device and a second user device. The method includes the following steps.

[0042] S101. A first user equipment obtains a group ID.

[0043] The group identifier is used to identify a group including at least a first user device and a second user device. The group may include multiple user devices, and the same user device may belong to different groups at the same time. Each group is identified by a group ID. During the group communication process, the group ID may change or may not change. In the description, the first user device and the second user device are defined to illustrate the end-to-end group communication, and they can be any group members that are respectively a sending user device and a receiving user device. There is no limit on the number of group members in the disclosed embodiments.

[0044] In one possible implementation, referring to the three-layer structure (including application layer, V2X layer and access layer) in IoT (Internet of Things), the group ID can be provided by the application layer and can also be called a vertical application layer (VAL) group ID. The VAL group ID is a unique identifier within the VAL service that represents a group of VAL users or VAL UEs according to the VAL service. The group of VAL users can belong to the same or different VAL service providers. The VAL group ID indicates the VAL application server that defines the group.

[0045] In this step, the first user equipment obtains the group ID. In a possible implementation, the first user equipment receives the group ID from a third party. Here, the third party may be, for example, a group management server. The group management server is responsible for managing the group and may distribute useful information to group members, such as a group key for generating a destination L2 ID.

[0046] In addition, unless otherwise defined, the first user equipment may also be referred to as a sending UE or a sending user equipment, and the second user equipment may also be referred to as a receiving UE or a receiving user equipment.

[0047] S102: The first user equipment determines a current destination ID according to the group ID.

[0048] The current destination ID is used to identify the second user device in the group. The first user device and the second user device use the current destination ID for group communication. In one possible implementation, the current destination ID can be a destination layer 2 ID (layer 2ID, L2 ID) in the sidelink proximity service direct communication, which identifies the target of the data in the sidelink proximity service direct communication. The destination L2 ID is 24 bits long and is split into two bit strings in the media access control (media access control, MAC) address layer. The first bit string is the least significant bit (LSB) part (8 bits) of the destination L2 ID, which is forwarded to the physical layer as a sidelink control layer 1 (L1) ID; it identifies the target of the data used in the sidelink control and is used to filter packets at the physical layer. The second bit string is the most significant bit (MSB) part (16 bits) of the destination L2 ID, which is carried in the MAC header and is used to filter packets at the MAC layer. The above only provides non-limiting examples of IDs. It should be noted that the length of the ID can also be different. Similarly, distribution of the ID into a least significant bit portion and a most significant bit portion may be achieved in a manner different from that described above.

[0049] In group communication, L2 IDs, including source L2 ID and destination L2 ID, identify the source and destination of a multicast packet, respectively. If the same UE is part of multiple groups, the L2 ID of the UE in each group is different. The destination user L2 ID defines the destination of the packet, which in group communication is every UE in the group except the sending UE. In summary, the source L2 ID represents a single UE of the link, and the destination L2 ID represents every UE in the multicast communication.

[0050] There are many possible implementations for the first user equipment to determine the current destination ID according to the group ID. In one possible implementation, the first user equipment obtains at least one parameter for determining the current destination ID, and determines the current destination ID according to the group ID and the at least one parameter.

[0051] Here, the at least one parameter may be received by the first user equipment from a third party, wherein the third party may be a group management server. In some embodiments, the at least one parameter may include a group key. As described above, the group key is issued to each group to which the user equipment (UE) belongs, and the group key may be issued using the mechanism defined in TS23.434. For example, the key management server may provide relevant security information to the group management server, which may be relayed to members of the group. The key management server also supports interaction with a corresponding key management server in a distributed vertical business service enabler architecture layer (SEAL) deployment. In some embodiments, the at least one parameter may not include a group key, but may use other parameters that can be used to convert the group ID into the current destination ID, for example, a set of random numbers and the order of the set of random numbers may be used. In the following embodiments, the implementation of the above-mentioned determination step will be described in detail in conjunction with the accompanying drawings.

[0052] S103: The first user equipment sends a packet carrying a current destination ID to the second user equipment.

[0053] After determining the current destination ID, the first user equipment may send the packet carrying the current destination ID to the second user equipment. In a possible implementation, the packet has the same structure as that of the related art. For the sake of brevity, it will not be described here.

[0054] Taking IoT as an example, the lower layer cannot use the ID of the upper layer, so it is necessary to convert the upper layer ID, i.e., the group ID, into the lower layer ID, i.e., the destination L2 ID. Therefore, the V2X layer of each user equipment can convert the group ID into the destination L2 ID. Therefore, the packet carrying the current destination ID in this article can be a packet of the AS layer, wherein the packet of the AS layer is transmitted in the AS layer between the first user equipment and the second user equipment.

[0055] In addition, the packet may be a data packet or a control packet, which is not limited in this document.

[0056] S104: The second user equipment receives the packet carrying the current destination ID.

[0057] S105: The second user equipment verifies the current destination ID in the received packet through the local destination ID.

[0058] The second user equipment maintains the destination ID locally, referred to herein as the local destination ID.

[0059] The second user equipment obtains a group ID and at least one parameter for determining a local destination ID, and then determines the local destination ID according to the group ID and the at least one parameter. The description of the group ID and the at least one parameter is the same as that in the above-mentioned steps on the first user equipment side, and is not repeated here for the sake of brevity.

[0060] The local destination ID is used by the second user device for verification, and may be determined by the second user device before receiving the packet or after receiving the packet. In one possible implementation, the receiving user device, i.e., the second user device, requires some parameters from the first user device to determine the local destination ID (e.g., in combination with Figure 4 In the embodiment described above, the parameter may be carried in the packet together with the current destination ID, and the determination of the local destination ID may be performed after receiving the packet. In this case, the structure of the packet will be different from that in the related art. In another possible implementation, the second user device may determine the local destination ID on its own side without any information from the first user device (for example, in combination with Figure 2 , Figure 3 and Figure 5 Details can be discussed in the following examples.

[0061] The verification is actually performed by the second user device to verify the conversion accuracy of the destination ID. In a possible implementation, the second user device can compare the current destination ID in the received packet with the local destination ID. If the two are the same, the second user device can start monitoring the packet using the current destination ID. In other words, the verification is only to ensure that the destination ID calculated by the second user device is the same as the destination ID sent by the first user device.

[0062] According to the solution provided by the present disclosure, the application layer group ID is converted into a destination L2 ID, thereby achieving end-to-end group communication.

[0063] As described above, the group ID may be converted to a destination ID using the at least one parameter, which may be a group key. Figures 2 to 3 Embodiments are described in which a group key is used for conversion. In these embodiments, the second user device determines its local destination ID without any information from the first user device, and the current destination ID generated by the first user device and the local destination ID generated by the second user device can remain unchanged during the group communication. The following description assumes that the group ID remains unchanged during the group communication. When the group ID changes during the group communication, the destination ID converted from the group ID also changes. Each time the group ID changes, the same process can be applied to convert the group ID to the destination ID. For the sake of brevity, it will not be repeated below.

[0064] Figure 2 A schematic flow chart of a group communication method provided for an embodiment of the present disclosure. According to this embodiment, taking IoT as an example, the sending UE directly uses the issued group key to generate an L2 ID. Since all UEs in the group have the group key, they all follow the same mechanism to obtain the L2 ID. Referring to IoT, the V2X layer of each user equipment (or UE) uses the issued group key to convert the group identity into the destination L2 ID.

[0065] The method may include the following steps.

[0066] S201: A key management server sends security information for generating a group key, and a group management server receives the security information from the key management server.

[0067] Considering the confidentiality and security of the group key, the key management server may provide the security information to the group management server for generating the group key.

[0068] S202: The group management server generates a group key using the security information.

[0069] After receiving the security information, the group management server can generate a group key. The embodiment of the present disclosure does not limit the specific generation method.

[0070] S203: The group management server sends a group ID and key material to the first user equipment and the second user equipment, and the first user equipment and the second user equipment receive the group ID and key material from the group management server respectively.

[0071] In one possible implementation, Figure 2 As shown, the group management server can send key material to the first user device and the second user device, so that the two user devices can generate keys for conversion by themselves. At this time, in step S202, the group management server no longer needs to generate a group key. Similarly, in other embodiments, the group management server can also send key material instead of sending a group key, and the embodiments of the present disclosure are not limited to this.

[0072] In another possible implementation manner, the group management server may generate a group key, and send the group key to the first user equipment and the second user equipment.

[0073] The group management server sends the group ID and the key material to the first user device and the second user device, so that the two user devices can generate destination IDs by themselves.

[0074] S204: The first user equipment determines a current destination ID according to the group ID and the group key, and the second user equipment determines a local destination ID according to the group ID and the group key.

[0075] The first user equipment may determine the current destination ID in a variety of ways. In one possible implementation, the first user equipment generates the current destination ID according to the group ID using a group key and a predefined algorithm. Here, the predefined algorithm is not limited in the embodiment. In another possible implementation, the conversion from the group ID to the destination L2 ID may be implemented in a variety of ways. For example, according to the length of the L2 ID, the encrypted value of the group ID may be directly used as the destination L2 ID. The encryption method used in TS 33.501 may be used.

[0076] The second user equipment may determine the local destination ID in the same manner as the first user equipment generates the current destination ID. For example, the second user equipment determines the local destination ID using at least one parameter and a predefined algorithm according to the group ID.

[0077] S205: The first user equipment sends a packet carrying the current destination ID to the second user equipment, and the second user equipment receives the packet carrying the current destination ID.

[0078] After determining the current destination ID, the first user equipment may send the packet carrying the current destination ID to the second user equipment. In a possible implementation, the packet has the same structure as that of the related art. For the sake of brevity, it will not be described here.

[0079] In this embodiment, the second user equipment generates the local destination ID by itself, ie, does not rely on any information from the first user equipment. Therefore, the determination of the local destination ID can be independent of receiving the packet from the first user equipment.

[0080] S206: The second user equipment verifies the current destination ID in the received packet through the local destination ID.

[0081] For more description of this step, please refer to the relevant description in step S105.

[0082] It should be noted that the key management server and group management server in the embodiments of the present disclosure are for illustrative purposes and should not be construed as limiting the present disclosure. Other similar devices may be used to replace these servers as long as those devices can work in the same manner as described in the embodiments.

[0083] According to the solution provided by the present disclosure, a group key is used to convert an application layer group ID into a destination L2 ID, thereby achieving end-to-end group communication.

[0084] Figure 3 A schematic flow chart of a group communication method provided for an embodiment of the present disclosure. According to this embodiment, taking IoT as an example, asymmetric ID-based encryption is used for conversion to ensure the conversion security of the destination L2 ID. The identity-based system allows any party to generate a public key from a known identity value (in this case, the application layer group ID, i.e., the group ID). A trusted third party (in this case, the group management server) creates a corresponding private key. First, the group management server publishes a master public key and retains the corresponding master private key. Using the master public key, any user device can calculate the public key corresponding to the group ID by combining the master public key and the group ID value. In order to obtain the corresponding private key, the UE is authorized to communicate with the group management server using the group ID, and the group management server uses the master private key to generate a private key for the group ID. Then, both parties (such as a sending user device and a receiving user device) can encrypt their respective messages.

[0085] The method comprises the following steps.

[0086] S301: A key management server sends security information for generating a group key and a private key, and a group management server receives the security information from the key management server.

[0087] Considering the confidentiality and security of the group key, the key management server may provide security information to the group management server for generating the group key and for generating a private key for the first user device and the second user device. For a description of the security information to be provided by the key management server for generating a master private key (in this embodiment, a private key corresponding to the group ID) and a master public key (group key), see TS 23.434.

[0088] S302: The group management server generates a group key and a private key using the security information.

[0089] After receiving the security information, the group management server can generate a group key and a private key for the first user device and the second user device. The specific generation method is not limited in the embodiment of the present disclosure.

[0090] The group management server sends the group key as a master public key to UEs (eg, a first user equipment and a second user equipment) that are group members, and generates and retains a master private key.

[0091] S303: The group management server sends a group ID and a group key to the first user equipment and the second user equipment, and the first user equipment and the second user equipment receive the group ID and the group key from the group management server respectively.

[0092] For this step, please refer to the relevant description in step S203.

[0093] S304: The first user equipment determines a current destination ID according to the group ID and the group key, and the second user equipment determines a local destination ID according to the group ID and the group key.

[0094] For more description of this step, please refer to the relevant description in step S204.

[0095] S305: The first user equipment generates a public key using the group ID and the group key, and encrypts a packet carrying the current destination ID using the public key.

[0096] The sending UE, i.e. the first user equipment, uses the group ID and the master public key to calculate the public key of the receiving UE, i.e. the second user equipment. The receiving UE calculates the public key of the sending UE in a similar manner (not shown in the figure). The destination L2 ID is calculated using the master public key, and all UEs in the group perform this calculation.

[0097] Various ID-based encryption algorithms may be used, such as Boneh-Franklin, Sakai-Kasahara, Boneh-Boyen, etc., and the embodiments of the present disclosure do not limit the selection of these methods.

[0098] S306: The second user equipment authenticates the group management server and obtains a private key.

[0099] In this step, the receiving UE or the second user equipment uses the group ID for authentication and receives a private key from the group management server. The private key corresponds to the public key generated by the first user equipment based on the group ID and the group key. All UEs are authenticated by the group management server and receive their corresponding private keys. It should be noted that when creating a group, the authentication is likely to be completed by the application layer. Therefore, the above authentication can be skipped and the private key can be obtained directly. Otherwise, the authentication method in TS33.501 can be used.

[0100] S307: The first user equipment sends the encrypted packet to the second user equipment, and the second user equipment receives the encrypted packet carrying the current destination ID.

[0101] Then, the sending UE, ie, the first user equipment, encrypts the data packet using the public key.

[0102] S308: The second user equipment verifies the current destination ID in the received packet through the local destination ID.

[0103] After receiving the packet, the second user equipment may obtain the destination L2 ID using the corresponding private key received from the group management server.

[0104] The second user equipment uses the private key to decrypt the packet carrying the current destination ID, and compares the current destination ID in the decrypted packet with the local destination ID. For the above verification, please refer to the relevant description in step S105.

[0105] According to the solution provided by the present disclosure, an application layer group ID is converted into a destination L2 ID using asymmetric ID-based encryption, thereby achieving end-to-end group communication and ensuring the security of communication.

[0106] In reference Figure 2 and Figure 3 In the above embodiment shown in FIG. 1 , a conversion from a group ID to a destination ID is performed once, thereby achieving end-to-end group communication between group members. As described above, the present disclosure also provides a solution for further ensuring the security of the above conversion. In general, unlike the above embodiment, in combination with Figure 4 and Figure 5In the illustrated embodiment, the conversion of the destination ID is performed multiple times during the group communication process instead of once. Similar to the above embodiment, when the group ID changes during the group communication process, the destination ID converted from the group ID also changes, and the same process can be applied each time. For the sake of brevity, the details will not be repeated. When the group ID remains unchanged during the group communication process, the group ID can also be converted multiple times and converted into different destination IDs to avoid attacks by intruders. Figure 4 and Figure 5 Provide detailed explanation.

[0107] When the group ID is converted multiple times, the first user device needs to determine the trigger condition of each conversion. In a possible implementation, the first user device may determine whether the trigger condition is met before the conversion; in response to determining that the trigger condition is met, the first user device generates a current destination ID according to the group ID and the group key; otherwise, in response to determining that the trigger condition is not met, the first user device determines the previously generated destination ID as the current destination ID.

[0108] Three specific solutions will be described in the following examples. Figure 4 In the first two related solutions, first, the first user device and the second user device both receive a group ID from the group management server, and after the group members have received the corresponding group ID, a UE (e.g., the first user device) is selected as the group leader in the first conversion because there is no destination ID between the two user devices. Therefore, the first user device and the second user device both generate an initial destination ID based on the group key and the initial random number from the group management server. Then, after the initial destination ID is generated, the two user devices can communicate with each other using the initial destination ID. Therefore, in the second conversion, the first user device selected as the group leader generates a random number (if necessary), and the second user device can generate its local destination ID based on the random number from the first user device. The same process as the second conversion can be used in consecutive conversions. Therefore, the first user device can determine the trigger condition after the first conversion and between each two consecutive conversions. The trigger condition for initiating the second conversion can be the same as the trigger condition for the subsequent conversion after the second conversion is triggered, or it can be different.

[0109] In with Figure 5 Among the related solutions, different from Figure 4Related to the first two solutions, the second user device can generate its local destination ID without any information from the first user device. In this case, the first user device can determine the trigger condition between each two conversions, that is, after each conversion, the first user device can determine whether the trigger condition is met and decide whether to generate a new destination ID or continue to use the previously generated destination ID (or the existing destination ID).

[0110] See now Figure 4 , Figure 4 A schematic flow chart of a group communication method provided for an embodiment of the present disclosure. According to this embodiment, taking IoT as an example, the sending UE generates a random number and uses a hash function to calculate the destination L2 ID through the group ID provided by the application layer. The random number is encrypted using a group key, which is issued to all UEs belonging to the group and sent to all UEs. The receiving UE decrypts the random number and uses the random number to calculate the corresponding destination L2 ID. The number of times the L2 ID is changed before the application layer changes the group ID depends on various implementation methods. After all group members have received the corresponding group ID, the group management server selects a UE as the group leader. The UE will serve as the initiator of the second ID conversion.

[0111] The method may include the following steps.

[0112] S401: A key management server sends security information for generating a group key, and a group management server receives the security information from the key management server.

[0113] For this step, please refer to the relevant description in step S201.

[0114] S402: The group management server generates a group key using the security information.

[0115] For this step, please refer to the relevant description in step S202.

[0116] In addition to generating the group key, the group management server may also generate an initial random number for the first conversion, and the first user device and the second user device use the initial random number to generate an initial destination ID. In another possible implementation, the group management server may send information for generating an initial random number to each user device, so that each user device can generate an initial random number by itself. For example, the group management server may send corresponding data for generating an initial random number instead of sending the initial random number itself, thereby reducing the computational cost. All UEs use the received data to generate the same initial random number. This case assumes that all UEs have the same random number generator. For information about the random number generator, see TS 33.501.

[0117] S403: The group management server sends a group ID, an initial random number, and a group key to the first user equipment and the second user equipment, and the first user equipment and the second user equipment receive the group ID and the group key from the group management server respectively.

[0118] For the first transition, which may be triggered by the application layer creating a group or the application layer changing the group ID, the group management server provides each UE with a group ID, an initial random number RAND0 and a group key.

[0119] S404: The first user equipment generates an initial destination ID according to the group ID by using a hash function and an initial random number, and the second user equipment generates an initial local destination ID according to the group ID by using a hash function and an initial random number.

[0120] As described above, since there is no destination ID for implementing group communication when creating a group, all group members generate an initial destination ID based on the group ID, the initial random number and the group key from the group management server. In this way, after the first conversion, that is, from the group ID to the initial destination ID, user devices can communicate with each other using the converted initial destination ID.

[0121] Each user device uses the initial random number RAND0 and the group ID as inputs to the hash function to obtain the destination L2 ID, as follows:

[0122] Hash(GroupID, RAND0) = Destination L2 ID

[0123] As described in the above embodiments, the length of the destination L2 ID can be different, so the implementation of the hash function can vary according to the length of the destination L2 ID and the change of the group ID. For example, the SHA-256 hash function can take the group identifier and RAND0 as its input and output a unique destination L2 ID with a length of 256 bits.

[0124] S405: The first user equipment generates a current destination ID according to the group ID using a hash function and a determined random number.

[0125] As described above, after the first conversion, when the trigger condition is met, the first user equipment selected as the initiator can initiate the second conversion. The initiator can trigger the conversion of the destination L2 ID according to the internal timer of the initiator (the first user equipment). For example, the time used to change the source L2 ID can also be used to change the destination L2 ID of the group communication. Alternatively, the trigger condition is that the time period starting from the moment of generating the previously generated destination ID exceeds the second predefined time period. For example, the group management server can send a timer T (which expires after the second predefined time period) to the initiator so that the initiator can use the timer T to initiate the second conversion.

[0126] After the trigger condition is met, the first user equipment can determine a random number and generate a current destination ID using a hash function and the determined random number according to the group ID. Since the current destination ID here is generated in the second conversion, the initial destination ID can be considered as the previously generated destination ID.

[0127] S406. The first user equipment encrypts the random number using the group key, and sends a packet carrying the current destination ID and the encrypted random number to the second user equipment; the second user equipment receives the packet carrying the current destination ID and the encrypted random number.

[0128] The group key issued to the group members is used to encrypt the random number. The AS layer of the first user equipment sends the encrypted random number and the current destination L2 ID in the data packet. The encrypted random number can be added as a prefix of the data packet or appended to the data packet, and the data packet will not be changed.

[0129] The random number may be encrypted directly with the group key or with separate integrity and confidentiality related keys derived according to the mechanism mentioned in TS 33.303.

[0130] The first user device and the second user device communicate using the initial destination ID generated in step S404 while sending and receiving the encrypted random number and the current destination ID generated in step S405.

[0131] S407: The second user equipment decrypts the encrypted random number using the group key, and generates a local destination ID according to the group ID using a hash function and the decrypted random number.

[0132] On the receiving side, the group key is used to decrypt the random number sent by the first user equipment. The V2X layer of the second user equipment uses the received random number and the same hash function mentioned in step S405 to calculate the local destination ID according to the group ID.

[0133] S408: The second user equipment verifies the current destination ID in the received packet through the local destination ID.

[0134] When the second user equipment has calculated the local destination ID and verified that the local destination ID is the same as the ID sent by the first user equipment, the second user equipment may start using the new ID, ie the current destination ID.

[0135] The above steps describe the first conversion and the second conversion. For the consecutive conversions after the second conversion, a random number RANDi (for example, a 256-bit number) (i=1~n, where n is the number of L2 ID conversions before the group ID changes) is generated by the first user device (initiator user device) each time the trigger condition is met. Then, the same process as described in steps S405-S408 can be applied to the first user device and the second user device. Taking IoT as an example, the V2X layer of the first user device uses a hash function and a random number RANDi to convert the application layer group ID to a new destination L2 ID. As described above, the trigger conditions for these consecutive conversions can be the same as the trigger conditions for the second conversion, that is, each conversion after the second conversion can be based on the internal timer of the initiator (first user device). For example, the group management server can send a timer T to the initiator (first user device) so that the first user device can use the timer T to start the next conversion.

[0136] In both cases where the application layer group ID changes or does not change during group communication, the group ID is converted to a new L2 ID multiple times during the validity period of the application layer group ID. Each time the conversion is performed, the encrypted random number is sent along. It is important to note that the lifetime or expiration time of the destination ID is less than the expiration time of the group ID.

[0137] In addition, as a possible implementation, in order to further ensure the security of the conversion, a random number can be arbitrarily generated and sent, which can be called the ON / OFF mode of the random number. That is, sometimes a random number is generated, and the encrypted value is added to the package sent by the first user device to the second user device. Sometimes a random number may not be generated, and the encrypted value will not be added to the package. For example, before each conversion, when the first user device determines that the trigger condition is met (such as the expiration of the timer T), it means that the next conversion is required. In this case, the first user device can directly generate a random number and continue the above process, such as in step S405, or the first user device can first determine whether to generate a random number according to the generation condition, and then determine the random number to be used for the conversion. That is, the first user device determines whether the generation condition of the random number generation is met; in response to determining that the generation condition is met, the first user device generates a random number; in response to determining that the generation condition is not met, the first user device uses the previously generated random number as the random number.

[0138] In a possible implementation, the generation condition here may be that the lifetime of the previously generated random number exceeds the first predefined period. It should be noted that the lifetime or expiration time of the random number is less than the expiration time of the destination ID.

[0139] (a) When the time period starting from the moment of generating the previously generated random number exceeds the first predefined time period, the first user equipment decides to generate a new random number. At this time, the newly generated random number can be used for the conversion of the current destination ID in step S405, and in step S406, the newly generated random number needs to be encrypted and transmitted in the packet.

[0140] (b) When the period from the moment of generating the previously generated random number does not exceed the first predefined period, the first user equipment decides not to generate a new random number. At this time, the previously generated random number is used for conversion, thereby obtaining the same result as the previous conversion. Therefore, the first user equipment can directly use the previously generated destination ID. At this time, the random number does not need to be encrypted and transmitted in the packet.

[0141] In another possible implementation, the generation condition here may be that a flag in a predefined pattern is true. The frequency of sending or not sending the encrypted random number may depend on the implementation. For example, the random number may be generated by following a predefined pattern: 1,1,0,0,1,0,0... (where flag 1 indicates generating a random number, and flag 0 indicates not generating a random number). This pattern may also be issued by the application layer.

[0142] On the receiving side, the second user device determines whether there is an encrypted random number in the received packet; in response to determining that there is an encrypted random number in the received packet, the second user device decrypts the encrypted random number and generates a local destination ID based on the group ID using a hash function and the decrypted random number; in response to determining that there is no encrypted random number in the received packet, the second user device determines the previously generated local destination ID as the local destination ID, that is, the second user device continues to use the previously generated local destination ID.

[0143] In short, in the ON / OFF mode, the process is the same as Figure 4 The process shown in is similar to that shown in , except that after the first conversion, the random number is generated and sent encrypted in some cases and not in others, and this decision is made arbitrarily.

[0144] According to the solution provided by the present disclosure, the conversion of the destination ID can be performed multiple times, thereby ensuring that the application layer group ID is securely converted to the destination L2 ID, and the conversion process cannot be tampered with by an adversary. The adversary cannot connect the destination L2 ID and the UE group membership, thereby protecting the integrity and privacy of the member UEs. Since the destination L2 ID is not encrypted, the UE only decrypts the message or only listens to the message sent to itself, thereby reducing the computing cost and reducing the latency (although this may not apply to the first conversion process, it is beneficial to subsequent conversions). In addition, the random number is sent arbitrarily, which further ensures the security of the conversion process.

[0145] In the above combination Figure 4 In the described embodiment, the second user device needs to calculate its local destination ID based on information (eg, an encrypted random number) from the first user device. In the following embodiments, the second user device may generate its local destination ID without any information from the first user device.

[0146] Figure 5 A schematic flow chart of a group communication method provided by an embodiment of the present disclosure. According to this embodiment, taking IoT as an example, the group management server sends a set of random numbers, a timer value (time interval) and the sequence of the set of random numbers to all user devices. These user devices use the random numbers to calculate the destination L2 ID through the group ID according to the sequence number.

[0147] The method may include the following steps.

[0148] S501. A group management server sends a group ID, a time interval, a set of random numbers, and an order of the set of random numbers to a first user device and a second user device; the first user device and the second user device respectively receive the group ID, the set of random numbers, and an order of the set of random numbers from the group management server.

[0149] After the group is created, the group management server sends the group ID to the associated user devices. The group management server also sends a set of random numbers and the order of the set of random numbers, which refers to the specific order in which the random numbers are to be used. The time interval is also sent.

[0150] It should be noted that the length of the set of random numbers depends on the implementation. For example, whether there are 10 random numbers or 100 random numbers in the set of random numbers depends on the update frequency of the destination ID.

[0151] The group management server may also send corresponding data for generating the set of random numbers instead of sending the set of random numbers themselves, thereby reducing the computational cost. All user equipments use the received data to generate the same set of random numbers in the same order. This assumes that all UEs have the same random number generator. For the random number generator, see TS 33.501.

[0152] S502: The first user equipment generates an existing destination ID according to the group ID, the set of random numbers and the order of the set of random numbers, and the second user equipment generates an existing local destination ID according to the group ID, the set of random numbers and the order of the set of random numbers.

[0153] The first user equipment may select a random number from the set of random numbers according to the order of the set of random numbers, and generate the existing destination ID (previously generated destination ID) using a hash function and the selected random number according to the group ID.

[0154] For example, for the first conversion, the first user equipment uses the group ID and the first random number as inputs of a hash function according to the sequence to generate an existing destination ID.

[0155] Hash(GroupId, RAND1) = Existing DestinationID

[0156] Here, RAND1 represents the first random number in the set of random numbers according to the sequence. For consecutive conversions, for example, if the sequence number in the sequence of the set of random numbers is 7, the first user device generates a destination ID using the 7th random number.

[0157] On the receiving side, the second user equipment performs similar operations as the first user equipment to obtain the existing local destination ID. After each update, the second user equipment listens to the existing destination ID and the new destination ID until it receives a message carrying the new destination ID from the sending user equipment.

[0158] S503: The first user equipment sends a packet carrying an existing destination ID to the second user equipment, and the second user equipment receives the packet carrying the existing destination ID.

[0159] S504: The second user equipment verifies the existing destination ID in the received packet by using the existing local destination ID.

[0160] For this step, please refer to the relevant description in step S105.

[0161] S505. When the time interval expires, the first user equipment generates a new destination ID according to the group ID, the set of random numbers and the order of the set of random numbers, and the second user equipment generates a new local destination ID according to the group ID, the set of random numbers and the order of the set of random numbers.

[0162] When the time interval expires, a new destination ID is calculated using the next random number in the sequence. That is, when the time interval expires, the first user equipment calculates a new destination ID using the next random number in the sequence.

[0163] Hash(GroupId, RAND2) = NewDestinationID

[0164] Here, RAND2 represents the second random number in the set of random numbers according to the order.

[0165] S506: The first user equipment sends a packet carrying a new destination ID to the second user equipment, and the second user equipment receives the packet carrying the new destination ID.

[0166] S507: The second user equipment verifies the new destination ID in the received packet through the new local destination ID.

[0167] When the current destination ID in the received packet is the same as the local destination ID, the second user device starts to monitor the packet using the current destination ID. In fact, in order to ensure time synchronization, the second user device starts to monitor the existing destination ID and the new destination ID. As long as the second user device receives a message carrying the new destination ID, it can stop monitoring the existing destination ID.

[0168] The destination L2 ID is updated every time the time interval expires until the application layer triggers a change to the group ID.

[0169] In this embodiment, for the sake of convenience, the destination ID is updated only once. In practical applications, each update of the destination ID can be the same as the process described in this article, and for the sake of brevity, it will not be repeated here.

[0170] According to the solution provided by the present disclosure, the conversion of the destination ID can be performed multiple times, thereby ensuring that the application layer group ID is securely converted to the destination L2 ID, and the conversion process cannot be tampered with by an adversary. The adversary cannot connect the destination L2 ID and the UE group membership, thereby protecting the integrity and privacy of the member UEs. Since the destination L2 ID is not encrypted, the UE only decrypts the message or only listens to the message sent to itself, thereby reducing the computing cost and delay.

[0171] Figure 6 A schematic flow chart of a group communication method provided in an embodiment of the present disclosure. Figure 6 In fact, it corresponds to Figure 5 Solution shown, but with more details. Figure 6 The process of securely translating an application layer group ID into a destination L2 ID is shown.

[0172] S601, set up a group: after creating a group, the group management server sends a group ID and a timer T to the associated UE, and also sends a set of random numbers and a specific order in which these random numbers are to be used. It is assumed that the application layer signaling is protected.

[0173] S602, converting ID: all UEs use the group ID and the first random number as inputs of a hash function according to the order to generate a destination L2 ID.

[0174] S603, Update ID: When the timer T expires, a new destination L2 ID is calculated using the next random number according to the sequence. The UE can listen to the existing destination L2 ID and the new destination L2 ID within a certain period or before receiving a message with a new destination ID to avoid any time synchronization problems.

[0175] The destination L2 ID is updated until the application layer changes the group ID.

[0176] The group management server may also send corresponding data to generate a random number instead of sending the random number itself.

[0177] Figure 7A schematic diagram of the structure of a first user equipment provided by an embodiment of the present disclosure: The first user equipment 700 includes an acquisition module 701, a determination module 702 and a sending module 703.

[0178] The acquisition module 701 is used to acquire a group identifier (ID), wherein the group identifier is used to identify a group including at least a first user device and a second user device. The determination module 702 is used to determine a current destination ID according to the group ID, wherein the current destination ID is used to identify a second user device in the group. The sending module 703 is used to send a packet carrying the current destination ID to the second user device.

[0179] In a possible implementation, the determining module 702 is specifically configured to:

[0180] obtaining at least one parameter for determining the current destination ID;

[0181] The current destination ID is determined based on the group ID and the at least one parameter.

[0182] In a possible implementation, the determining module 702 is specifically configured to:

[0183] Determine whether the trigger condition is met;

[0184] In response to determining that the trigger condition is satisfied, generating the current destination ID based on the group ID and the at least one parameter;

[0185] In response to determining that the trigger condition is not satisfied, a previously generated destination ID is determined as the current destination ID.

[0186] In a possible implementation, the determining module 702 is specifically configured to:

[0187] Determine the random number;

[0188] The current destination ID is generated according to the group ID using a hash function and the random number.

[0189] In a possible implementation, the determining module 702 is specifically configured to:

[0190] Determining whether a generation condition for generating the random number is met;

[0191] In response to determining that the generation condition is satisfied, generating the random number;

[0192] In response to determining that the generation condition is not satisfied, a previously generated random number is used as the random number.

[0193] In a possible implementation, the sending module 703 is specifically configured to:

[0194] In response to determining that the generation condition is met, encrypting the random number using the at least one parameter; and sending a packet carrying the current destination ID and the encrypted random number to the second user equipment.

[0195] In a possible implementation, the sending module 703 is specifically configured to:

[0196] In response to determining that the generation condition is not satisfied, sending a packet carrying the current destination ID to the second user equipment.

[0197] In a possible implementation, the generation condition is: the lifetime of a previously generated random number exceeds a first predefined period of time, or a flag in a predefined pattern is true.

[0198] In a possible implementation manner, the previously generated destination ID is generated by the first user equipment according to the group ID by using a hash function and an initial random number.

[0199] In a possible implementation manner, the initial random number is received by the first user equipment from a third party, or is generated by the first user equipment according to information from a third party.

[0200] In a possible implementation, the determining module 702 is specifically configured to:

[0201] The current destination ID is generated according to the group ID using the at least one parameter and a predefined algorithm.

[0202] In a possible implementation, the sending module 703 is specifically configured to:

[0203] generating a public key using the group ID and the at least one parameter;

[0204] encrypting the packet carrying the current destination ID by using the public key;

[0205] Send the encrypted packet to the second user equipment.

[0206] In a possible implementation manner, the at least one parameter includes a set of random numbers and an order of the set of random numbers.

[0207] The determining module 702 is specifically used for:

[0208] selecting a random number from the set of random numbers according to an order of the set of random numbers;

[0209] The current destination ID is generated according to the group ID using a hash function and the selected random number.

[0210] In a possible implementation manner, the at least one parameter includes a group key.

[0211] In a possible implementation manner, the trigger condition is that a period starting from the moment when the previously generated destination ID is generated exceeds a second predefined period.

[0212] In a possible implementation, the acquisition module 701 is specifically used to:

[0213] The at least one parameter is received from a third party.

[0214] In a possible implementation, the acquisition module 701 is specifically used to:

[0215] The group ID is received from a third party.

[0216] In a possible implementation manner, the third party is a group management server.

[0217] In a possible implementation manner, the packet carrying the current destination ID is an access stratum (AS) packet.

[0218] In a possible implementation manner, the current destination ID is a destination layer 2 ID (L2 ID) in sidelink proximity service direct communication.

[0219] In a possible implementation manner, the packet is a data packet or a control packet.

[0220] In a possible implementation manner, the group ID is a vertical application layer ID.

[0221] According to the solution provided by the present disclosure, the conversion of the destination ID can be performed multiple times, thereby ensuring that the application layer group ID is securely converted to the destination L2 ID, and the conversion process cannot be tampered with by an adversary. The adversary cannot connect the destination L2 ID and the UE group membership, thereby protecting the integrity and privacy of the member UEs. Since the destination L2 ID is not encrypted, the UE only decrypts the message or only listens to the message sent to itself, thereby reducing the computing cost and delay.

[0222] Figure 8 The second user equipment 800 includes a receiving module 801 and a verification module 802 .

[0223] The receiving module 801 is used to receive a packet carrying a current destination identification (ID), wherein the current destination ID is used to identify a second user device in a group, wherein the group includes at least a first user device and a second user device. The verification module 802 is used to verify the current destination ID in the received packet through a local destination ID.

[0224] In a possible implementation manner, the second user equipment further includes:

[0225] An acquisition module, configured to: acquire a group ID, wherein the group ID is used to identify the group; acquire at least one parameter used to determine the local destination ID;

[0226] A determination module is used to determine the local destination ID according to the group ID and the at least one parameter.

[0227] In a possible implementation manner, the determining module is specifically configured to:

[0228] Determining whether an encrypted random number exists in the received packet;

[0229] In response to determining that the encrypted random number exists in the received packet, decrypting the encrypted random number using the at least one parameter, and generating the local destination ID using a hash function and the decrypted random number according to the group ID;

[0230] In response to determining that the encrypted random number is not present in the received packet, a previously generated local destination ID is determined as the local destination ID.

[0231] In a possible implementation manner, the determining module is specifically configured to:

[0232] The local destination ID is generated according to the group ID using the at least one parameter and a predefined algorithm.

[0233] In a possible implementation, the verification module 802 is specifically configured to:

[0234] Obtaining a private key, wherein the private key corresponds to a public key generated by the first user equipment according to the group ID and the at least one parameter;

[0235] Decrypting the packet carrying the current destination ID using the private key;

[0236] The current destination ID in the decrypted packet is compared with the local destination ID.

[0237] In a possible implementation manner, the at least one parameter includes a set of random numbers and an order of the set of random numbers.

[0238] Wherein, the determination module is specifically used for:

[0239] selecting a random number from the set of random numbers according to an order of the set of random numbers;

[0240] The local destination ID is generated based on the group ID using a hash function and the selected random number.

[0241] In a possible implementation manner, the second user equipment further includes a monitoring module, configured to:

[0242] When the current destination ID in the received packet is identical to the local destination ID, sniffing packets begins using the current destination ID.

[0243] According to the solution provided by the present disclosure, the conversion of the destination ID can be performed multiple times, thereby ensuring that the application layer group ID is securely converted to the destination L2 ID, and the conversion process cannot be tampered with by an adversary. The adversary cannot connect the destination L2 ID and the UE group membership, thereby protecting the integrity and privacy of the member UEs. Since the destination L2 ID is not encrypted, the UE only decrypts the message or only listens to the message sent to itself, thereby reducing the computing cost and delay.

[0244] like Fig. 9 As shown, the embodiment of the present disclosure further provides a first user equipment 900. The equipment 900 may be Figure 7 The device 700 in the embodiment can be used to implement the content related to the first user device corresponding to the method in the method embodiment. The device 900 includes an input interface 910, an output interface 920, a processor 930 and a memory 940. The input interface 810, the output interface 920, the processor 930 and the memory 940 can be connected through a bus system. The memory 940 is used to store programs, instructions or codes. The processor 930 is used to execute the program, instruction or code in the memory 940 to control the input interface 910 to receive signals, control the output interface 920 to send signals, and complete the operations in the above method embodiments.

[0245] In a specific implementation, Figure 7 The sending module 703 in the device 700 can be Fig. 9 The output interface 920 in is implemented, similarly, Figure 7 The acquisition module 701 and the determination module 702 in the device 700 can be Fig. 9 The processor 930 in is implemented.

[0246] like Fig.10 As shown, the embodiment of the present disclosure further provides a second user device 1000. The device 1000 may be Figure 8 The device 800 in the embodiment can be used to implement the content related to the second user device corresponding to the method in the method embodiment. The device 1000 includes an input interface 1010, an output interface 1020, a processor 1030 and a memory 1040. The input interface 1010, the output interface 1020, the processor 1030 and the memory 1040 can be connected through a bus system. The memory 1040 is used to store programs, instructions or codes. The processor 1030 is used to execute the programs, instructions or codes in the memory 1040 to control the input interface 1010 to receive signals, control the output interface 1020 to send signals, and complete the operations in the above method embodiments.

[0247] In a specific implementation, Figure 8 The receiving module 801 in the device 800 can be Fig.10 The output interface 1020 in the implementation, similarly, Figure 8 The verification module 802 in the device 800 can be Fig.10 The processor 1030 in is implemented.

[0248] The present disclosure also provides a computer storage medium storing computer executable instructions, which is used to implement the method described in the embodiments of the present disclosure when the computer executable instructions are executed.

[0249] The present disclosure also provides a computer program product including instructions. When the instructions are executed on a computer, the computer is enabled to execute the method described in the above embodiments.

[0250] The terms such as “first”, “second”, etc. mentioned in the present disclosure and claims as well as the above drawings are intended to distinguish different objects but are not intended to limit a specific order.

[0251] The terms "and / or" and the like in the embodiments of the present disclosure are only used to describe the association relationship between associated objects, indicating that three relationships may exist. For example, A and / or B may mean: only A exists, A and B exist at the same time, and only B exists.

[0252] In the embodiments of the present disclosure, expressions such as "exemplary" or "for example" are used to indicate the description of an example or instance. In the embodiments of the present disclosure, any embodiment or design scheme described as "exemplary" or "for example" should not be interpreted as being more preferred or more advantageous than other embodiments or design schemes. In particular, the use of "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner.

[0253] In one or more examples, the functions described may be implemented by hardware, software, firmware, or any combination thereof. If implemented by software, the functions may be stored in or transmitted via a computer-readable medium as one or more instructions or codes and executed by a hardware-based processing unit. A computer-readable medium may include a computer-readable storage medium corresponding to a tangible medium such as a data storage medium, or to a communication medium including any medium that facilitates the transfer of a computer program from one place to another (e.g., according to a communication protocol). In this manner, a computer-readable medium may generally correspond to (1) a non-transitory tangible computer-readable storage medium or (2) a communication medium such as a signal or carrier wave. A data storage medium may be any available medium accessed by one or more computers or one or more processors to retrieve instructions, codes, and / or data structures for implementing the techniques described in the present disclosure. A computer program product may include a computer-readable medium.

[0254] As an example and not limitation, such computer-readable storage media may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage devices, magnetic disk storage devices or other magnetic storage devices, flash memory or any other medium that can be used to store the required program code in the form of instructions or data structures and can be accessed by a computer. In addition, any connection can also be appropriately defined as a computer-readable medium. For example, if the instructions are transmitted from a website, server or other remote source using coaxial cables, optical fiber cables, twisted pairs and digital subscriber lines (DSL), or wireless technologies such as infrared, radio and microwaves, then coaxial cables, optical fiber cables, twisted pairs and DSL, or wireless technologies such as infrared, radio and microwaves are also included in the definition of medium. However, it should be understood that computer-readable storage media and data storage media do not include connections, carriers, signals or other transient media, but refer to non-transient tangible storage media. Disks and optical disks used herein include compact discs (CDs), laser discs, optical discs, digital versatile discs (DVDs), floppy disks and Blu-ray discs, where disks usually reproduce data magnetically, while optical discs use lasers to reproduce data optically. Combinations of the above should also be included within the scope of computer-readable media.

[0255] Instructions can be executed by one or more processors, for example, one or more digital signal processors (DSP), one or more general-purpose microprocessors, one or more application specific integrated circuits (ASIC), one or more field programmable logic arrays (FPGA) or other equivalent integrated or discrete logic circuits. Therefore, the term "processor" used herein may refer to any of the above structures or any other structure suitable for implementing the techniques described herein. In addition, in some aspects, the various functions described herein may be provided in dedicated hardware and / or software modules for encoding and decoding, or incorporated in a combined codec. Moreover, these techniques may be fully implemented in one or more circuits or logic elements.

[0256] The technology of the present disclosure can be implemented in a variety of devices or apparatuses, including wireless handsets, integrated circuits (ICs), or a group of ICs (e.g., chipsets). The present disclosure describes various components, modules, or units to emphasize the functional aspects of the devices used to perform the disclosed technology, but it is not necessarily required to be implemented by different hardware units. In fact, as described above, the various units can be combined in a codec hardware unit in combination with appropriate software and / or firmware, or provided by a collection of interoperable hardware units including one or more processors as described above.

[0257] Non-transitory computer-readable media include all types of computer-readable media, including magnetic storage media, optical storage media, and solid-state storage media, but specifically do not include signals. It should be understood that the software can be installed in a router, client, or other network device and sold together with it. Alternatively, the software can be obtained and loaded into the device, including through optical disk media or from any form of network or distribution system, including, for example, from a server owned by the software developer or from a server used but not owned by the software developer. For example, the software can be stored in a server for distribution over the Internet.

[0258] In an alternative embodiment, some or all of the software may be replaced by dedicated hardware, including custom integrated circuits, gate arrays, FPGAs, PLDs, and special-purpose computers. In one embodiment, the software (stored in a storage device) that implements one or more embodiments is used to program one or more processors. One or more processors may communicate with one or more computer-readable media / storage devices, peripheral devices, and / or communication interfaces. In an alternative embodiment, some or all of the software may be replaced by dedicated hardware, including custom integrated circuits, gate arrays, FPGAs, PLDs, and special-purpose computers. In an embodiment, the term "unit" may include a circuit (or integrated circuit) or a software component.

[0259] For the purpose of illustration and description, a detailed description is presented above, which is not intended to be exhaustive or limit the subject matter claimed herein to one or more precise forms disclosed. According to the above guidance, many modifications and changes can be made. The various embodiments described are selected to better explain the principles of the disclosed technology and its practical application, so that those skilled in the art can better utilize the technology of the various embodiments and various modifications are suitable for the expected specific use. Therefore, the scope of the present invention is defined by the appended claims.

[0260] The present disclosure is described in conjunction with various embodiments. However, other changes and modifications made to the disclosed embodiments may be understood and implemented in conjunction with the drawings, the disclosure and the appended claims, and these changes and modifications should be understood to be included in the appended claims. In the claims, the word "comprising" does not exclude other elements or steps, and "one" or "an" does not exclude multiple. A single processor or other unit may implement the functions of several items listed in the claims. The detailed description of certain measures in mutually different dependent claims does not indicate, exclude or imply that the combination of these measures cannot be used advantageously. The computer program may be stored or distributed on a suitable medium, such as an optical storage medium or solid-state medium provided together with other hardware or as part of other hardware, and may also be distributed in other forms, such as via the Internet or other wired or wireless communication systems.

Claims

1. A group communication method, characterized in that: include: The first user equipment obtains a group identifier (ID), wherein the group ID is used to identify a group including at least the first user equipment and a second user equipment; The first user equipment acquires at least one parameter; The first user equipment determines a current destination ID according to the group ID and the at least one parameter, wherein the current destination ID is used to identify the second user equipment in the group; The first user equipment sends a packet carrying the current destination ID to the second user equipment; Wherein, determining the current destination ID includes: The first user equipment determines a random number, wherein the random number is included in the at least one parameter; The first user equipment generates the current destination ID according to the group ID by using a hash function and the random number.

2. The method according to claim 1, characterized in that The first user equipment determines the current destination ID according to the group ID and the at least one parameter, including: Determining, by the first user equipment, whether a trigger condition is met; In response to determining that the trigger condition is satisfied, the first user equipment generates the current destination ID according to the group ID and the at least one parameter; In response to determining that the trigger condition is not satisfied, the first user equipment determines a previously generated destination ID as the current destination ID.

3. The method according to claim 2, characterized in that The first user equipment determines a random number, including: Determining, by the first user equipment, whether a generation condition for generating the random number is met; In response to determining that the generation condition is met, the first user equipment generates the random number; In response to determining that the generation condition is not satisfied, the first user equipment uses a previously generated random number as the random number.

4. The method according to claim 3, characterized in that The first user equipment sends a packet carrying the current destination ID to the second user equipment, including: In response to determining that the generation condition is met, the first user equipment encrypts the random number using the at least one parameter; and the first user equipment sends a packet carrying the current destination ID and the encrypted random number to the second user equipment.

5. The method according to claim 3, characterized in that: The first user equipment sends a packet carrying the current destination ID to the second user equipment, including: In response to determining that the generation condition is not satisfied, the first user equipment sends a packet carrying the current destination ID to the second user equipment.

6. The method according to any one of claims 3 to 5, characterized in that The generation condition is that the lifetime of the previously generated random number exceeds a first predefined period of time, or a flag in a predefined pattern is true.

7. The method according to any one of claims 2 to 5, characterized in that The previously generated destination ID is generated by the first user equipment according to the group ID using a hash function and an initial random number.

8. The method according to claim 7, characterized in that The initial random number is received by the first user equipment from a third party, or is generated by the first user equipment according to information from a third party.

9. The method according to claim 1, characterized in that: The first user equipment determines the current destination ID according to the group ID and the at least one parameter, including: The first user equipment generates the current destination ID according to the group ID using the at least one parameter and a predefined algorithm.

10. The method according to claim 9, characterized in that The first user equipment sends a packet carrying the current destination ID to the second user equipment, including: The first user equipment generates a public key using the group ID and the at least one parameter; The first user equipment encrypts the packet carrying the current destination ID by using the public key; The first user equipment sends the encrypted packet to the second user equipment.

11. The method according to claim 2, characterized in that The at least one parameter includes a set of random numbers and an order of the set of random numbers; The first user equipment generates the current destination ID according to the group ID and the at least one parameter, including: The first user equipment selects the random number from the set of random numbers according to an order of the set of random numbers; The first user equipment generates the current destination ID according to the group ID using the hash function and the selected random number.

12. The method according to any one of claims 2 to 5 and 9 to 10, characterized in that The at least one parameter comprises a group key.

13. The method according to any one of claims 2 to 5 and 11, characterized in that The trigger condition is that a period of time starting from the time when the previously generated destination ID is generated exceeds a second predefined period of time.

14. The method according to any one of claims 1 to 5 and 9 to 11, characterized in that The first user equipment acquires at least one parameter, including: The first user equipment receives the at least one parameter from a third party.

15. The method according to any one of claims 1 to 5 and 9 to 11, characterized in that The first user equipment obtains the group ID, including: The first user device receives the group ID from a third party.

16. The method according to claim 14, characterized in that The third party is a group management server.

17. The method according to any one of claims 1 to 5 and 9 to 11, characterized in that The packet carrying the current destination ID is an access layer (AS) packet.

18. The method according to any one of claims 1 to 5 and 9 to 11, characterized in that The current destination ID is a destination layer 2 ID (L2 ID) in sidelink proximity service direct communication.

19. The method according to any one of claims 1 to 5 and 9 to 11, characterized in that The packet is a data packet or a control packet.

20. The method according to any one of claims 1 to 5 and 9 to 11, characterized in that The group ID is a vertical application layer ID.

21. A group communication method, characterized in that: include: The second user equipment receives a packet carrying a current destination identification (ID), wherein the current destination ID is used to identify the second user equipment in a group, the group including at least the first user equipment and the second user equipment; The second user equipment obtains a group ID, where the group ID is used to identify the group; The second user equipment acquires at least one parameter; The second user equipment determines a local destination ID based on the group ID and the at least one parameter; The second user equipment verifies the current destination ID in the received packet by means of the local destination ID; The second user equipment determines the local destination ID according to the group ID and the at least one parameter, including: Determining, by the second user equipment, whether an encrypted random number exists in the received packet; In response to determining that the encrypted random number exists in the received packet, the second user equipment decrypts the encrypted random number using the at least one parameter, and the second user equipment generates the local destination ID using a hash function and the decrypted random number according to the group ID; In response to determining that the encrypted random number is not present in the received packet, the second user equipment determines a previously generated local destination ID as the local destination ID.

22. The method according to claim 21, characterized in that The second user equipment determines the local destination ID according to the group ID and the at least one parameter, including: The second user equipment generates the local destination ID according to the group ID by using the at least one parameter and a predefined algorithm.

23. The method according to claim 22, characterized in that The second user equipment verifies the current destination ID in the received packet by using the local destination ID, comprising: The second user equipment obtains a private key, wherein the private key corresponds to a public key generated by the first user equipment according to the group ID and the at least one parameter; The second user equipment uses the private key to decrypt the packet carrying the current destination ID; The second user device compares the current destination ID in the decrypted packet with the local destination ID.

24. The method according to any one of claims 21 to 23, characterized in that After the second user equipment verifies the current destination ID in the received packet by means of the local destination ID, the method further comprises: When the current destination ID in the received packet is identical to the local destination ID, the second user equipment starts listening for packets using the current destination ID.

25. A first user equipment, characterized in that: The invention comprises a processor and a memory, wherein the memory is used to store a computer program that can be executed on the processor, and when the computer program is executed, the processor is used to execute the method according to any one of claims 1 to 20.

26. A second user equipment, characterized in that: The invention comprises a processor and a memory, wherein the memory is used to store a computer program that can be executed on the processor, and when the computer program is executed, the processor is used to execute the method according to any one of claims 21 to 24.

27. A computer storage medium storing computer executable instructions, characterized in that: When the computer executable instructions are executed, they are used to implement the method according to any one of claims 1 to 20.

28. A computer storage medium storing computer executable instructions, characterized in that: When the computer executable instructions are executed, they are used to implement the method according to any one of claims 21 to 24.