Message filtering method and apparatus in vehicle networking based on LTE-V2X

Abstract

The present disclosure provides a method for message filtering. The method comprises storing a list of layer two identifiers for message filtering at an access stratum or adaptation stratum, comparing a destination layer two identifier of a received message with the layer two identifiers in the list of layer two identifiers at the access stratum or adaptation stratum, and passing the received message from the access stratum or adaptation stratum to an upper layer when the destination layer two identifier is the same as one of the layer two identifiers in the list of layer two identifiers.

Description

Technical Field

[0001] This invention relates to LTE-V2X-based vehicle-to-everything (V2X) wireless communication technology, and more specifically to a technique for message filtering in LTE-V2X-based V2X-based V2X wireless communication. Background Technology

[0002] Dedicated Short-Range Communication (DSRC) based on the IEEE 802.11p standard and LTE-V2X based on the 3GPP Long Term Evolution (LTE) standard are currently the two mainstream communication standards used in the field of vehicle-to-everything (V2X) communication. Compared with DSRC technology, LTE-V2X can utilize existing cellular network infrastructure and spectrum resources, resulting in lower application costs. Furthermore, LTE-V2X technology offers significant improvements in bandwidth, applicability, and quality of service, making it suitable for various V2X communication application scenarios. Therefore, LTE-V2X-based V2X wireless communication technology helps overcome the shortcomings of traditional DSRC communication and achieves better service quality, making it a current hot research direction.

[0003] Despite the numerous advantages of LTE-V2X technology compared to DSRC, the current LTE-V2X standard primarily uses broadcast communication. In broadcast mode, the destination Layer 2 identifier in a message is mapped from the application identifier (AID) within the message, rather than the actual Layer 2 identifier of the receiving end. Therefore, according to the current LTE-V2X standard, when the receiving end receives a broadcast message, it does not perform address filtering based on the destination Layer 2 identifier in the message. Instead, it filters the message based on the application identifier (AID) at the Dedicated Management Entity (DME) or Dedicated Short Message Protocol (DSMP) layer to select the service messages that the receiving end is currently interested in.

[0004] In the current message filtering mechanism, the receiving end forwards all received broadcast messages to the DME or DSMP layer for filtering, increasing the message processing overhead at the DME and DSMP. Especially as the LTE-V2X standard needs to gradually implement unicast communication, the current message filtering mechanism cannot directly filter out unicast messages transmitted via dedicated unicast links. This results in the receiving end processing unicast messages destined for other receiving ends, which not only fails to demonstrate the advantages of unicast transmission but also reduces the efficiency of message reception and processing. Summary of the Invention

[0005] This invention is not intended to identify key or essential features of the protected subject matter, nor is it intended to limit the scope of the protected subject matter. The invention will be further described in the following detailed description.

[0006] To address the technical issues of the message filtering mechanism in the existing LTE-V2X standard, this disclosure introduces new service primitives at the message receiver and implements a preliminary message filtering mechanism based on Layer 2 identifiers at the receiver's access or adaptation layer, thereby greatly improving the efficiency of message processing and resource utilization at the communication receiver.

[0007] In one aspect, this disclosure provides a method for message filtering. The method includes storing a list of Layer 2 identifiers for message filtering at the access layer; comparing the destination Layer 2 identifier of a received message with the Layer 2 identifiers in the list of Layer 2 identifiers at the access layer; and when the destination Layer 2 identifier matches one of the Layer 2 identifiers in the list of Layer 2 identifiers, transmitting the received message from the access layer to the adaptation layer.

[0008] In one aspect, this disclosure provides a method for message filtering. The method includes storing a list of Layer 2 identifiers for message filtering at an adaptation layer; comparing the destination Layer 2 identifier of a received message with the Layer 2 identifiers in the list of Layer 2 identifiers at the adaptation layer; and when the destination Layer 2 identifier matches one of the Layer 2 identifiers in the list of Layer 2 identifiers, transmitting the received message from the adaptation layer to a dedicated short message protocol layer.

[0009] In another aspect, this disclosure also provides an apparatus for data frame communication. The apparatus includes a memory and at least one processor coupled to the memory. The at least one processor is configured to: store a list of Layer 2 identifiers for message filtering in an access layer; compare a destination Layer 2 identifier of a received message with a Layer 2 identifier in the list of Layer 2 identifiers in the access layer; and when the destination Layer 2 identifier is the same as a Layer 2 identifier in the list of Layer 2 identifiers, transmit the received message from the access layer to an adaptation layer.

[0010] In another aspect, this disclosure also provides an apparatus for data frame communication. The apparatus includes a memory and at least one processor coupled to the memory. The at least one processor is configured to: store a list of Layer 2 identifiers for message filtering in an adaptation layer; compare the destination Layer 2 identifier of a received message with a Layer 2 identifier in the list of Layer 2 identifiers in the adaptation layer; and when the destination Layer 2 identifier is the same as a Layer 2 identifier in the list of Layer 2 identifiers, transmit the received message from the adaptation layer to a dedicated short message protocol layer.

[0011] In another aspect, this disclosure also provides a computer-readable storage medium having computer-executable code stored thereon for performing the following method steps: storing a list of Layer 2 identifiers for message filtering in an access layer; comparing the destination Layer 2 identifier of a received message with a Layer 2 identifier in the list of Layer 2 identifiers in the access layer; and transmitting the received message from the access layer to the adaptation layer when the destination Layer 2 identifier is the same as a Layer 2 identifier in the list of Layer 2 identifiers.

[0012] In another aspect, this disclosure also provides a computer-readable storage medium having computer-executable code stored thereon for performing the following method steps: storing a list of layer 2 identifiers for message filtering in an adaptation layer; comparing the destination layer 2 identifier of a received message with the layer 2 identifiers in the list of layer 2 identifiers in the adaptation layer; and when the destination layer 2 identifier is the same as a layer 2 identifier in the list of layer 2 identifiers, transmitting the received message from the adaptation layer to a dedicated short message protocol layer.

[0013] In another aspect, this disclosure also provides a computer program product including instructions executable by a processor to perform the following operations: storing a list of Layer 2 identifiers for message filtering in an access layer; comparing a destination Layer 2 identifier of a received message with a Layer 2 identifier in the list of Layer 2 identifiers in the access layer; and transmitting the received message from the access layer to the adaptation layer when the destination Layer 2 identifier is the same as a Layer 2 identifier in the list of Layer 2 identifiers.

[0014] In another aspect, this disclosure also provides a computer program product including instructions executable by a processor to perform the following operations: storing a list of Layer 2 identifiers for message filtering in an adaptation layer; comparing the destination Layer 2 identifier of a received message with the Layer 2 identifiers in the list of Layer 2 identifiers in the adaptation layer; and transmitting the received message from the adaptation layer to a dedicated short message protocol layer when the destination Layer 2 identifier is the same as a Layer 2 identifier in the list of Layer 2 identifiers.

[0015] It should be noted that one or more of the above aspects include the detailed description below and the features specifically recited in the claims. The following description and drawings set forth some exemplary features in detail from multiple aspects. These features merely indicate various ways in which the principles of each aspect can be implemented, and this disclosure is intended to include all such aspects and their equivalents. Attached Figure Description

[0016] Figure 1 A protocol stack framework diagram of LTE-V2X-based vehicle-to-everything (V2X) wireless communication technology is shown.

[0017] Figure 2A schematic diagram of the protocol layer process for receiving dedicated short message data frames is shown.

[0018] Figure 3 A flowchart illustrating the inter-layer protocol interaction process for receiving dedicated short message data frames according to this disclosure is shown.

[0019] Figure 4 A flowchart illustrating the inter-layer protocol interaction process for receiving dedicated short message data frames according to this disclosure is shown.

[0020] Figure 5 An exemplary method flowchart for message filtering at the access layer according to this disclosure is shown.

[0021] Figure 6 An exemplary method flowchart for message filtering in an adaptation layer according to this disclosure is shown.

[0022] Figure 7 A block diagram of an exemplary apparatus for message filtering according to this disclosure is shown. Detailed Implementation

[0023] The various embodiments will now be described in detail with reference to the accompanying drawings. It should be understood that the description of these specific embodiments is merely intended to enable those skilled in the art to better understand and implement the present disclosure, and is not intended to limit the scope of the present disclosure in any way.

[0024] Figure 1 This diagram illustrates the protocol stack framework of LTE-V2X-based vehicle-to-everything (V2X) wireless communication technology. The protocol stack of LTE-V2X V2X wireless communication equipment mainly includes the application layer, network layer, and access layer. At the access layer, LTE-V2X supports the cellular communication Uu interface and the direct communication PC5 interface. The Uu interface is the interface between the user terminal and the access network equipment (e.g., eNode B) in the LTE-V2X standard. The PC5 interface is the interface used for direct connection between terminal devices (e.g., between vehicles) in the LTE-V2X standard.

[0025] The network layer comprises a data sublayer and a management sublayer. The management sublayer primarily handles system configuration and maintenance, and its functions are integrated into a Dedicated Management Entity (DME). The DME is a general-purpose integration of management services, providing a management interface to the data sublayer, enabling interaction with the data sublayer and the use of its services to transmit management data streams between different user devices. The data sublayer includes: IP and TCP / UDP layers, a Dedicated Short Message Protocol (DSMP) layer, and an adaptation layer. The data sublayer is used for user plane data transmission between user device application layers, and for the transmission of control plane messages between user device management layer entities (e.g., dedicated management entities) or between management layer entities and application layers. The IP and DSMP protocols in the data sublayer are optional. Embodiments of this disclosure primarily relate to message filtering of DSMP-based dedicated short message data frames. The DSMP protocol layer is mainly responsible for data interaction with different applications. The DSMP entity can deliver application layer data packets to the lower layer and transmit short messages of interest to the application layer. The DSMP protocol can use application identifiers (AIDs) to distinguish different application layer services.

[0026] The adaptation layer provides transmission adaptation functions between the underlying access technology (such as LTE-V2X) and the upper-layer protocol stack. The adaptation layer can receive DSMP or DME data packets sent by the upper layer, distinguish the underlying interface used by the data packet to be sent, and deliver the corresponding data packet to the underlying layer that conforms to the corresponding access layer interface for transmission. The adaptation layer can also receive data packets from the lower layer, distinguish the upper-layer protocol type to which the corresponding data packet belongs, and deliver the data packet to the designated upper-layer protocol stack. The adaptation layer's functions also include: mapping between application identifiers and destination layer 2 identifiers, generation / modification / maintenance of source layer 2 identifiers, mapping between unicast / multicast addresses and layer 2 identifiers, etc.

[0027] The application layer is the highest layer of the user protocol stack. It determines the service data to receive based on device needs and then passes this data to the network and access layers for transmission. The application layer can request communication applications or short message services of interest from lower layers. It can also receive messages of interest from lower layers.

[0028] Figure 2This diagram illustrates the inter-layer protocol process for receiving Dedicated Short Message (DSM) data frames. Before receiving the message carried by the DSM data frame, the receiving application layer needs to request the communication application or short message service of interest from the DME in the network layer. For example, when transmitting a Dedicated Service Announcement (DSA) message carried by a DSM data frame, the receiving application layer can use the DME-UserService.request (DME-User Service Request) service primitive to indicate to the management entity the application service that the application layer is interested in or wishes to receive. The parameters of the DME-UserService.request service primitive are as follows:

[0029]

[0030] Table 1 describes the parameters of the DME-UserService.request service primitive. The application identifier can be further used to identify different DSA message service types.

[0031]

[0032]

[0033] Table 1

[0034] After accepting a request, the DME can reply to the application layer with the DME-UserService.confirm service primitive. The DME-UserService.confirm service primitive is used to acknowledge receipt of the corresponding request from the upper layer. If the DME accepts this request, upon receiving a DSA message, it will pass the matching DSA message to the application layer based on the application of interest identifier set in the upper layer request. The parameters of this service primitive are as follows:

[0035]

[0036] Table 2 explains the parameters of the DME-UserService.confirm service primitive.

[0037]

[0038] Table 2

[0039] For example, when transmitting DSM data messages, the receiving application layer can use the DME-DSMService.request service primitive to indicate to the management entity that the upper-layer entity wants to receive a DSM data frame with a specified AID. The parameters of the DME-DSMService.request service primitive are as follows:

[0040]

[0041]

[0042] Table 3 describes the parameters of the DME-DSMService.request service primitive. The application identifier can be used to identify different DSM data frame service types, such as the DSM type that carries DSA messages.

[0043]

[0044] Table 3

[0045] After receiving a request, DME can reply to the application layer with the DME-DSMService.confirm service primitive. The DME-DSMService.confirm service primitive is used to confirm receipt of the corresponding request from the upper layer, and it includes the following parameters:

[0046]

[0047] Table 4 explains the parameters of the DME-DSMService.confirm service primitive.

[0048]

[0049] Table 4

[0050] Next, as Figure 2 As shown, according to the existing LTE-V2X standard, when the access layer receives an access message, it processes the message based on the information related to the access technology in the access layer frame header and sends the ACCESS-LAYER.indication service primitive to the adaptation layer to indicate that access data has been received. The parameters of this service primitive are as follows:

[0051]

[0052]

[0053] Table 5 describes the parameters of the ACCESS-LAYER.indication service primitive, including the following data: Figure 2 The adapter layer frame header, DSMP frame header, and data are shown.

[0054]

[0055] Table 5

[0056] The adaptation layer can process received messages based on protocol type information in the adaptation layer frame header and send the ADAPTATION-LAYER.indication service primitive to the DSMP layer. The parameters of this service primitive are as follows:

[0057]

[0058]

[0059] Table 6 describes the parameters of the ADAPTATION-LAYER.indication service primitive, including the following data: Figure 2 The DSMP frame header and data are shown below.

[0060]

[0061] Table 6

[0062] The DSMP layer can process received messages based on information in the DSMP frame header. The DSMP frame header may include information such as version, DSMP extension indicator, AID, and length. According to the existing LTE-V2X standard, the DSMP layer can determine whether the data in the received message is a DSA message or a service data message based on the AID. If it is a service data message, the DSMP layer can further determine whether the message is of interest to the application layer based on the AID, and send the DSM.indication service primitive to the application layer to indicate that the application layer has received the message of interest. If it is a DSA message, the DSMP layer sends the DSA message to the DME entity for filtering and processing through the DSM.indication service primitive. The parameters of the DSM.indication service primitive are as follows:

[0063]

[0064]

[0065] Table 7 describes the parameters of the DSM.indication service primitive, where the data can be DSA data frames or user service data.

[0066]

[0067] Table 7

[0068] The current LTE-V2X standard's mechanism for filtering received DSM data frames based on AID in the DSMP layer or DME entity introduces unnecessary processing overhead at the network layer and is unsuitable for unicast communication. Therefore, this disclosure introduces a new service primitive at the message receiver and provides a mechanism for message filtering based on Layer 2 identifiers at the receiver's access or adaptation layer. The message filtering mechanism of this disclosure is applicable to unicast messages, broadcast messages, and situations where unicast and broadcast messages coexist. By filtering messages based on Layer 2 identifiers at the adaptation or even access layer, this mechanism ensures that only the messages needed by the receiver are passed to the upper layer for processing. This enables the receiving device to process messages efficiently and effectively, reducing latency and improving resource utilization. Thus, while ensuring normal communication and interaction between devices, it maximizes the efficiency and resource utilization of the receiver's message processing.

[0069] Figure 3 A flowchart illustrating the inter-layer protocol interaction for receiving dedicated short message data frames according to an embodiment of this disclosure is shown. Figure 3 In the illustrated embodiment, the receiving end can filter received unicast and / or broadcast messages at the access layer. These messages can be either DSM data frames carrying service data (also referred to herein as DSM messages) or DSA data frames carrying dedicated service announcements (also referred to herein as DSA messages).

[0070] In step 301, the receiving application layer can use the DME-UserService.request service primitive to indicate to the DME the criteria description of the application layer for which it is interested, in order to receive DSA messages. This service primitive may include an Application Identifier (AID) for identifying the application of interest, and an enumerated type variable action indication to indicate whether related user application information should be added or deleted from local storage. If the Action is set to "Add," it means the receiving end should receive and pass messages of the application type corresponding to that AID to the upper layer; if the Action is set to "Delete," it means the receiving end no longer needs to receive and pass messages of the application type corresponding to that AID to the upper layer. In step 305, the DME can reply with the DME-UserService.confirm service primitive after accepting the user service request.

[0071] In step 301, the receiving application layer can also indicate to the management entity via the DME-DSMService.request service primitive that the upper-layer entity wants to receive a DSM of interest for receiving DSM data messages. This service primitive may include relevant AID and Action information. Correspondingly, in step 305, the DME can reply with the DME-DSMService.confirm service primitive after accepting the DSM service request.

[0072] The DME, through AID and Action information, combined with locally stored information, can obtain all application types and their application identifiers of interest to the current receiving application layer. The AID information obtained at the DME through the above steps can include either AIDs identifying the DSM message types the application layer wishes to receive, or AIDs identifying the DSA message types the application layer wishes to receive.

[0073] In one embodiment of this disclosure, the DME can send the AID.indication (Application Identifier Indication) service primitive to the DSMP layer in step 310 to pass the application identifier of the service type of interest to the receiving application layer to the lower layer. The parameters of the AID.indication service primitive are as follows:

[0074]

[0075] Table 8 describes the parameters of the AID.indication service primitive.

[0076]

[0077] Table 8

[0078] The receiving DME can use the AID.indication primitive to inform the DSMP layer of the application identifier (AID) related to the application type of interest currently being received by the application layer, along with an enumerated variable action indicating "add" or "delete". If the Action is "add", it means that the relevant user application information should be added from the local information storage, i.e., the receiving end needs to receive messages of the service type represented by the application identifier; if the Action is "delete", it means that the relevant user application information should be deleted from the local information storage, i.e., the receiving end no longer needs to receive messages of the service type represented by the application identifier. Through the AID.indication service primitive from the DME to the DSMP, the DSMP layer can obtain not only the AID identifying the type of DSM data frame that the application layer is interested in or wants to receive, but also the AID identifying the type of DSA message that the application layer is interested in or wants to receive. In another embodiment of this disclosure, the AID.indication service primitive from the DME to the DSMP layer may not be necessary. The DSMP layer can obtain the AID identifying the type of DSM data frame that the application layer is interested in or wants to receive using existing methods.

[0079] In step 315, the receiving DSMP layer can pass the application identifier (AID) of interest to the application layer and its corresponding "add" or "delete" action indicator to the adaptation layer via the AID.indication service primitive. The AID.indication service primitive from the DSMP layer to the adaptation layer can be the same as the AID.indication service primitive from the DME to the DSMP layer, and its specific parameters can be found in Table 8. The values ​​of the parameters in the AID.indication service primitive from the DSMP layer to the adaptation layer can be set based on the parameter values ​​in the AID.indication service primitive from the DME to the DSMP layer. In another embodiment, the values ​​of the parameters in the AID.indication service primitive from the DSMP layer to the adaptation layer can also be set independently by the DSMP layer.

[0080] In another embodiment of this disclosure, since the content of the AID.indication service primitives in steps 310 and 315 can be consistent, the operations in steps 310 and 315 can be implemented in one step. That is, the receiving DME can directly inform the adaptation layer of the application identifier (AID) related to the application type of interest to the application layer, as well as the enumerated variable action indicating its "addition" and "deletion," through the AID.indication service primitive. The adaptation layer can obtain all application types of interest to the current receiving application layer through the AID and Action information from the AID.indication service primitive from the DME, combined with local storage information. This may include DSM messages that the application layer wants to receive, and may also include DSA messages that the application layer wants to receive. The embodiments of this disclosure are not limited to the specific form of the service primitive. The receiving DME entity or DSMP layer can also transmit the application identifier of interest to the adaptation layer in other ways.

[0081] In step 320, the receiving adaptation layer can map the AID in the AID.indication service primitive from the DSMP layer or DME entity to the corresponding Layer 2 identifier based on the mapping relationship between application identifiers and Layer 2 identifiers. This Layer 2 identifier can be called the Application_Layer-2ID. This mapping operation for AIDs can be based on the same mapping relationship as the mapping operation from AID to destination Layer 2 identifier performed by the sending adaptation layer when the sending end broadcasts the DSM message or DSA message related to the AID. Therefore, the Application_Layer-2 identifier obtained by the receiving end from the mapping of the AID of interest to the application layer in step 320 can be used to filter the received broadcast messages to select the broadcast messages of interest to the application layer.

[0082] In another embodiment of this disclosure, the receiver adaptation layer can also generate a Layer 2 identifier for the local device based on its local Media Access Control (MAC) address. This generated Layer 2 identifier is identical to the destination Layer 2 identifier in unicast messages destined for this receiver, and therefore can be referred to as the Destination_Layer-2 ID, and can be used to filter received unicast messages.

[0083] In step 320, the receiving adaptation layer can pass the Application_Layer-2 ID and Destination_Layer-2 ID to the receiving access layer through the Layer-2ID.indication service primitive. The parameters of the Layer-2ID.indication service primitive are as follows:

[0084]

[0085] Table 9 describes the parameters of the Layer-2ID.indication service primitive.

[0086]

[0087] Table 9

[0088] The `Action` parameter in the `Layer-2ID.indication` service primitive indicates the operation to be performed on the `Application_Layer-2 ID` parameter within that primitive. If `Action` is set to "Add", it means that the user application information associated with that `Application_Layer-2 ID` should be added to the local storage, indicating that the receiving end needs to receive messages of the service type represented by that `Application_Layer-2 ID`. If `Action` is set to "Delete", it means that the user application information associated with that `Application_Layer-2 ID` should be deleted from the local storage, indicating that the receiving end no longer needs to receive messages of the service type represented by that `Application_Layer-2 ID`.

[0089] In one embodiment of this disclosure, the Destination_Layer-2 ID parameter in the Layer-2ID.indication service primitive can be optional. That is, the parameters of the Layer-2ID.indication service primitive can include only the Application_Layer-2 ID and the corresponding Action. In another embodiment, the Application_Layer-2 ID parameter and the corresponding Action parameter in the Layer-2ID.indication service primitive can be optional. That is, the parameters of the Layer-2ID.indication service primitive can include only the Destination_Layer-2 ID. The receiving adaptation layer can use the Layer-2ID.indication service primitive to transmit the Destination_Layer-2 ID, or the Application_Layer-2 ID and the corresponding Action, to the access layer separately. The embodiments of this disclosure are not limited to the specific form of the service primitive; the receiving adaptation layer can also transmit the local Layer 2 identifier and the application Layer 2 identifier obtained by mapping the AID of interest currently being explored by the upper layer to the access layer in other ways.

[0090] Through one or more steps in steps 301-320, the receiving access layer can obtain a list of Layer 2 identifiers for filtering received messages. This list is stored locally and maintained and updated; for example, Layer 2 identifiers obtained from AID mappings that are no longer of interest to the upper layer are deleted, or Layer 2 identifiers obtained from AID mappings that are currently of interest to the upper layer are added. This list of Layer 2 identifiers may include local Layer 2 identifiers (which can also be called destination Layer 2 identifiers from the perspective of received messages), one or more Layer 2 identifiers for business messages of current interest to the application layer (which can also be called application Layer 2 identifiers), or a combination of both. Destination Layer 2 identifiers can be used for address-based message filtering. Application Layer 2 identifiers can be used for message filtering based on business application type.

[0091] When the receiving end receives a message, in step 325, the receiving end access layer can obtain the destination layer 2 identifier from the received message, and filter the received message at the access layer by comparing the obtained destination layer 2 identifier with the layer 2 identifiers in its locally stored layer 2 identifier list. The conditions for the access layer to filter messages may include:

[0092] (1) The destination Layer 2 identifier in the message data packet is the same as the destination Layer 2 identifier in the local Layer 2 identifier list;

[0093] (2) The destination layer 2 identifier in the message data packet is the same as an application layer 2 identifier in the local layer 2 identifier list.

[0094] Condition (1) indicates that the message is a unicast message sent to the receiving end via a dedicated unicast link. Condition (2) indicates that the message is a broadcast service message that the receiving end is currently interested in.

[0095] In an embodiment where the access layer filters both unicast and broadcast messages, the receiving access layer continues to pass the message to the upper layer when one of the two filtering conditions is met. If neither filtering condition is met, the access layer can discard the message. In an embodiment where the access layer filters only unicast messages, when the destination layer 2 identifier in the message data packet is located in the unicast message address range, the receiving access layer determines whether condition (1) is met: if the condition is met, the access layer continues to pass the message to the upper layer; if the condition is not met, the access layer can discard the message. When the destination layer 2 identifier in the message data packet is located in the broadcast message address range, the receiving access layer can hand over the broadcast message to the upper layer for processing according to the existing standard without filtering the broadcast message. In an embodiment where the receiving end only receives broadcast messages, the access layer can determine only whether the received message meets condition (2): if the condition is met, the access layer continues to pass the message to the upper layer; if the condition is not met, the access layer can discard the message.

[0096] In step 325, after the access layer completes message filtering, it can inform the adaptation layer of information such as the data in the data packet, the source layer 2 identifier, and the destination layer 2 identifier through the ACCESS-LAYER.indication service primitive as shown in Table 5. In step 330, the receiving adaptation layer can obtain the Source_address and Destination_address as shown in Table 6 based on the source layer 2 identifier and the destination layer 2 identifier in the ACCESS-LAYER.indication service primitive, and inform the DSMP layer of the data and the above address information through the ADAPTATION-LAYER.indication service primitive.

[0097] The DSMP layer can determine whether the data carried in the received message is a DSA message or a DSM message based on the DSMP frame header information (e.g., AID) in the ADAPTATION-LAYER.indication service primitive data parameters. For DSA messages, the receiving DSMP layer can send data and application identifier information to the DME in step 335 using the DSM.indication service primitive as shown in Table 7. When the DME receives the DSA message, it can match the application identifier of interest set by the upper layer request with the application identifier in the DSA message to further determine the application information of the DSA message. For DSM messages, the receiving DSMP layer can directly pass the DSM messages of interest to the application layer through the DSM.indication service primitive in step 340.

[0098] exist Figure 3In the protocol layer interaction process shown for receiving DSM data frames, the receiving end can filter unicast messages at the access layer based on the relationship between the layer 2 identifier and the destination address of the received message. At the same time, it can also filter broadcast messages based on the mapping relationship between the layer 2 identifier and the application identifier that identifies different application types. This ensures that only unicast messages that are directed to the receiving end and broadcast messages that the receiving end may need will be passed through the access layer to the upper layer for further processing, while most messages that the receiving end does not need will be discarded directly at the access layer. This improves the efficiency of message processing and resource utilization at the receiving end, helps to reduce communication latency, and improves communication quality.

[0099] Figure 4 A flowchart illustrating the inter-layer protocol interaction for receiving dedicated short message data frames according to another embodiment of this disclosure is shown. Figure 4 In the illustrated embodiment, the receiving end can filter received unicast and / or broadcast messages at the adaptation layer. These messages can be either DSM or DSA messages.

[0100] In step 401, the receiving application layer can use the DME-UserService.request service primitive to indicate to the DME the criteria description of the application layer for which it is interested, in order to receive DSA messages. In step 405, the DME can reply with the DME-UserService.confirm service primitive after accepting the user service request. In step 401, the receiving application layer can also use the DME-DSMService.request service primitive to indicate to the management entity that the upper-layer entity wants to receive a DSM of interest, in order to receive DSM data messages. Accordingly, in step 405, the DME can reply with the DME-DSMService.confirm service primitive after accepting the DSM service request. The specific operations of steps 401 and 405 are similar to... Figure 3 Steps 301 and 305 in the illustrated embodiment are the same and will not be repeated here.

[0101] In one embodiment of this disclosure, the DME may send an AID.indication (Application Identifier Indication) service primitive to the DSMP layer in step 410 to pass the application identifier of the service type currently of interest to the receiving application layer to the lower layer. The parameters and descriptions of the AID.indication service primitive can be found in Table 8. Through the AID.indication service primitive from the DME to the DSMP layer, the DSMP layer can obtain not only the AID identifying the type of DSM data frames that the application layer is interested in or wishes to receive, but also the AID identifying the type of DSA messages that the application layer is interested in or wishes to receive. In another embodiment of this disclosure, the AID.indication service primitive from the DME to the DSMP layer may not be necessary. The DSMP layer can obtain the AID identifying the type of DSM data frames that the application layer is interested in or wishes to receive using existing methods.

[0102] In step 415, the receiving DSMP layer can pass the application identifier (AID) of interest to the application layer and its corresponding "add" or "delete" action indicator to the adaptation layer via the AID.indication service primitive. The AID.indication service primitive from the DSMP layer to the adaptation layer can be the same as the AID.indication service primitive from the DME to the DSMP layer, and its specific parameters can be found in Table 8. The values ​​of the parameters in the AID.indication service primitive from the DSMP layer to the adaptation layer can be set based on the parameter values ​​in the AID.indication service primitive from the DME to the DSMP layer. In another embodiment, the values ​​of the parameters in the AID.indication service primitive from the DSMP layer to the adaptation layer can also be set independently by the DSMP layer.

[0103] In another embodiment of this disclosure, with Figure 3The illustrated embodiment is identical; steps 410 and 415 can be implemented in one step: the receiving DME can directly inform the adaptation layer of the application identifier (AID) related to the application type of interest to the application layer, along with enumerated variable actions indicating "addition" and "deletion," via the AID.indication primitive. The adaptation layer, through the AID and Action information from the AID.indication service primitive from the DME, and in conjunction with locally stored information, can obtain all application types of interest to the current receiving application layer. This may include DSM messages and DSA messages that the application layer wishes to receive. This disclosure is not limited to the specific form of the service primitive; the receiving DME entity or DSMP layer can also transmit application identifiers of interest to the adaptation layer in other ways.

[0104] The receiving adaptation layer can map the AID in the AID.indication service primitive from the DSMP layer or DME entity to the corresponding Layer 2 identifier based on the mapping relationship between application identifiers and Layer 2 identifiers. This Layer 2 identifier can be called the Application_Layer-2 ID. This mapping operation for AIDs is based on the same mapping relationship as the mapping operation from AID to destination Layer 2 identifier performed by the sending adaptation layer when the sending end broadcasts DSM or DSA messages related to the AID. Therefore, the application layer 2 identifier can be used to filter received broadcast messages to select those that the application layer is interested in.

[0105] In another embodiment of this disclosure, the receiver adaptation layer can also generate a Layer 2 identifier for the local device based on its local Media Access Control (MAC) address. This generated Layer 2 identifier is identical to the destination Layer 2 identifier in unicast messages destined for this receiver, and therefore can be referred to as the Destination_Layer-2 ID, and can be used to filter received unicast messages.

[0106] Through one or more steps in steps 401-415, the receiving adaptation layer can obtain a list of Layer 2 identifiers for filtering received messages. This list is stored locally and maintained and updated; for example, Layer 2 identifiers obtained from AID mappings that are no longer of interest to the upper layer are deleted, or Layer 2 identifiers obtained from AID mappings that are currently of interest to the upper layer are added. This list of Layer 2 identifiers may include local Layer 2 identifiers (which can also be called destination Layer 2 identifiers from the perspective of received messages), one or more Layer 2 identifiers for business messages of current interest to the application layer (which can also be called application Layer 2 identifiers), or a combination of both. Destination Layer 2 identifiers can be used for address-based message filtering. Application Layer 2 identifiers can be used for message filtering based on business application type.

[0107] When the receiving end receives a message, in step 425, the receiving end access layer can process the received message according to the existing standard, and inform the adaptation layer of the data obtained from the received message, the source layer 2 identifier, and the destination layer 2 identifier through the ACCESS-LAYER.indication service primitive as shown in Table 5.

[0108] In step 430, the receiving adaptation layer can obtain the destination layer 2 identifier of the received message based on the parameters in the ACCESS-LAYER.indication service primitive, and filter the received message by comparing the obtained destination layer 2 identifier with the layer 2 identifier in its locally stored layer 2 identifier list. The conditions for the adaptation layer to filter messages may include: (1) the destination layer 2 identifier in the message data packet is the same as the destination layer 2 identifier in the local layer 2 identifier list;

[0109] (2) The destination layer 2 identifier in the message data packet is the same as an application layer 2 identifier in the local layer 2 identifier list.

[0110] Condition (1) indicates that the message is a unicast message sent to the receiving end via a dedicated unicast link. Condition (2) indicates that the message is a broadcast service message that the receiving end is currently interested in.

[0111] In an embodiment that filters both unicast and broadcast messages simultaneously, the receiving adaptation layer continues to pass the message to the upper layer when one of the two filtering conditions is met. If neither filtering condition is met, the adaptation layer can discard the message. In an embodiment that filters only unicast messages, when the destination layer 2 identifier in the message data packet is located in the unicast message address range, the receiving adaptation layer determines whether condition (1) is met: if the condition is met, the adaptation layer continues to pass the message to the upper layer; if the condition is not met, the adaptation layer can discard the message. When the destination layer 2 identifier in the message data packet is located in the broadcast message address range, the receiving adaptation layer can pass the broadcast message to the upper layer for processing according to the existing standard without filtering the broadcast message. In an embodiment where the receiving end only receives broadcast messages, the adaptation layer can determine only whether the received message meets condition (2): if the condition is met, the adaptation layer continues to pass the message to the upper layer; if the condition is not met, the adaptation layer can discard the message.

[0112] In step 430, the receiving adaptation layer can inform the DSMP layer of data and address information via the ADAPTATION-LAYER.indication service primitive after completing message filtering. The DSMP layer can determine whether the data carried in the received message is a DSA message or a DSM message based on the DSMP frame header information (e.g., AID) in the data parameters of the ADAPTATION-LAYER.indication service primitive. For DSA messages, the receiving DSMP layer can send data and application identifier information to the DME via the DSM.indication service primitive as shown in Table 7 in step 435. When the DME receives the DSA message, it can match the application identifier of interest set by the upper layer with the application identifier in the DSA message to further determine the application information of the DSA message. For DSM messages, the receiving DSMP layer can directly pass the DSM messages of interest to the application layer via the DSM.indication service primitive in step 440.

[0113] exist Figure 4 In the protocol layer interaction process shown for receiving DSM data frames, the receiving end can filter the received messages at the adaptation layer, eliminating the need to pass layer 2 identifiers to the access layer. This reduces the overhead of storing and updating the layer 2 identifier list for message filtering at the access layer, and also reduces the message processing burden at the upper layers. This improves the efficiency of message processing and resource utilization at the receiving end, which is beneficial for reducing communication latency and improving communication quality.

[0114] Figure 5A flowchart is shown of an exemplary method 500 for message filtering at the access layer according to an embodiment of the present disclosure. Method 500 can be executed by a receiving end for filtering received unicast or broadcast messages. At block 510, method 500 may store a list of layer 2 identifiers for message filtering at the access layer. The receiving end may follow the steps as follows... Figure 3 Steps 301-320 shown may be used to obtain and store the Layer 2 identifier list. This Layer 2 identifier list may include local Layer 2 identifiers. For example, method 500 may include receiving a Layer 2 identifier indication service primitive from the adaptation layer at the access layer. The parameters of the Layer 2 identifier indication service primitive include a local Layer 2 identifier generated based on the local media access control address. Method 500 may include storing the generated local Layer 2 identifier in a Layer 2 identifier list for message filtering in block 510.

[0115] The Layer 2 identifier list may also include application Layer 2 identifiers. In one embodiment, method 500 may include receiving an application identifier indication service primitive from a dedicated management entity at the adaptation layer. The parameters of the application identifier indication service primitive include an application identifier and a behavior indication, which includes adding or deleting. In another embodiment, method 500 may include receiving a first application identifier indication service primitive from a dedicated management entity at a dedicated short message protocol layer, the parameters of which include an application identifier and a behavior indication, which includes adding or deleting; and receiving a second application identifier indication service primitive from a dedicated short message protocol layer at the adaptation layer, the parameters of which include the same parameters as the first application identifier indication service primitive. After the adaptation layer obtains the application identifier and corresponding behavior indication related to the application type of interest to the application layer, method 500 may further include receiving a Layer 2 identifier indication service primitive from the adaptation layer at the access layer. The parameters of the Layer 2 identifier indication service primitive include the application Layer 2 identifier and the behavior indication, the application Layer 2 identifier being generated by the adaptation layer based on the application identifier; and adding or deleting the corresponding application Layer 2 identifier in the Layer 2 identifier list according to the behavior indication in the Layer 2 identifier indication service primitive in block 510.

[0116] In block 520, method 500 can compare the destination Layer 2 identifier of the received message with the Layer 2 identifiers in the Layer 2 identifier list at the access layer. When it is determined in block 530 that the destination Layer 2 identifier is the same as one of the Layer 2 identifiers in the Layer 2 identifier list, method 500 can transmit the received message from the access layer to the adaptation layer in block 540. When it is determined in block 530 that the destination Layer 2 identifier is different from all the Layer 2 identifiers in the Layer 2 identifier list, method 500 can discard the received message at the access layer in block 550.

[0117] Figure 6 A flowchart is shown of an exemplary method 600 for message filtering at an adaptation layer according to an embodiment of the present disclosure. Method 600 can be executed by a receiving end for filtering received unicast or broadcast messages. At block 610, method 600 may store a list of layer 2 identifiers for message filtering at the adaptation layer. The receiving end may configure the method as follows: Figure 4 One or more steps from steps 401 to 415 shown are used to obtain and store the Layer 2 identifier list. This Layer 2 identifier list may include local Layer 2 identifiers. For example, in block 610, method 600 may include generating local Layer 2 identifiers based on local Media Access Control (MAC) addresses and storing the generated local Layer 2 identifiers in a Layer 2 identifier list for message filtering.

[0118] The Layer 2 identifier list may also include application Layer 2 identifiers. For example, method 600 may include receiving an application identifier indication service primitive from a dedicated management entity or a dedicated short message protocol layer at the adaptation layer. The parameters of the application identifier indication service primitive include an application identifier and a behavior indication, which includes adding or deleting. At block 610, method 600 may further include generating application Layer 2 identifiers based on the application identifiers in the application identifier indication service primitive, and adding or deleting the generated application Layer 2 identifiers from the Layer 2 identifier list according to the corresponding behavior indications.

[0119] In block 620, method 600 can compare the destination Layer 2 identifier of the received message with the Layer 2 identifiers in the Layer 2 identifier list at the adaptation layer. When it is determined in block 630 that the destination Layer 2 identifier is the same as one of the Layer 2 identifiers in the Layer 2 identifier list, method 600 can transmit the received message from the adaptation layer to the dedicated short message protocol layer in block 640. When it is determined in block 630 that the destination Layer 2 identifier is different from all the Layer 2 identifiers in the Layer 2 identifier list, method 600 can discard the received message in the adaptation layer in block 650.

[0120] Figure 7 A block diagram of an exemplary device 700 for message filtering according to the present disclosure is shown. Device 700 may include at least one processor 710 and a memory 720. Processor 710 may be coupled to memory 720 via bus 730. Processor 710 may be configured to perform combined... Figure 5 The method described in section 6 is used to filter received unicast or broadcast messages at the access or adaptation layer based on a stored list of layer 2 identifiers.

[0121] According to one embodiment, at least one processor 710 may be configured to: store a list of Layer 2 identifiers for message filtering in the access layer; compare the destination Layer 2 identifier of a received message with the Layer 2 identifiers in the list of Layer 2 identifiers in the access layer; and when the destination Layer 2 identifier is the same as a Layer 2 identifier in the list of Layer 2 identifiers, pass the received message from the access layer to the adaptation layer.

[0122] According to another embodiment, at least one processor 710 may be configured to: store a list of Layer 2 identifiers for message filtering in the adaptation layer; compare the destination Layer 2 identifier of a received message with the Layer 2 identifiers in the list of Layer 2 identifiers in the adaptation layer; and when the destination Layer 2 identifier is the same as a Layer 2 identifier in the list of Layer 2 identifiers, transmit the received message from the adaptation layer to the dedicated short message protocol layer.

[0123] This disclosure also provides a computer-readable storage medium. The computer-readable storage medium stores information for performing a combination. Figure 5 Or the computer-executable code of the method described in 6.

[0124] This disclosure also provides a computer program product. The computer program product includes components executable by a processor to achieve [combination / adaptation]. Figure 5 Or the instructions for the method described in 6.

[0125] Those skilled in the art should understand that the various embodiments disclosed above can be modified and varied in various ways without departing from the spirit of the invention. All such modifications and variations should fall within the protection scope of the present invention, and the protection scope of the present invention should be defined by the claims.

Claims

1. A method for message filtering: A list of Layer 2 identifiers for message filtering is stored in the access layer. This list includes local Layer 2 identifiers and application Layer 2 identifiers. The local layer 2 identifier is used to filter received unicast messages, and the application layer 2 identifier is used to filter received broadcast messages. At the access layer, the destination layer 2 identifier of the received message is compared with the layer 2 identifier in the layer 2 identifier list. as well as When the destination layer 2 identifier is the same as one of the layer 2 identifiers in the layer 2 identifier list, the received message is transmitted from the access layer to the adaptation layer; when the destination layer 2 identifier is different from all the layer 2 identifiers in the layer 2 identifier list, the received message is discarded at the access layer.

2. The method according to claim 1, further comprising: The access layer receives a Layer 2 identifier indication service primitive from the adaptation layer. The parameters of the Layer 2 identifier indication service primitive include the local Layer 2 identifier, which is generated based on the local media access control address. The storage of the layer 2 identifier list for message filtering includes storing the local layer 2 identifier in the layer 2 identifier list.

3. The method according to claim 1, further comprising: The adaptation layer receives an application identifier indication service primitive from a dedicated management entity. The parameters of the application identifier indication service primitive include an application identifier and a behavior indication, which includes adding or deleting.

4. The method according to claim 1, further comprising: The first application identifier indication service primitive is received from a dedicated management entity at the dedicated short message protocol layer. The parameters of the first application identifier indication service primitive include an application identifier and a behavior indication, wherein the behavior indication includes adding or deleting. as well as The adaptation layer receives a second application identifier indication service primitive from the dedicated short message protocol layer. The parameters of the second application identifier indication service primitive include the application identifier and the behavior indication.

5. The method according to claim 3 or 4, further comprising: The access layer receives a Layer 2 identifier indication service primitive from the adaptation layer. The parameters of the Layer 2 identifier indication service primitive include the application Layer 2 identifier and the behavior indication. The application Layer 2 identifier is generated based on the application identifier.

6. The method according to claim 5, wherein, The list of layer 2 identifiers stored for message filtering includes: The application layer 2 identifier is added or removed from the layer 2 identifier list according to the behavior instruction.

7. A method for message filtering, comprising: The adaptation layer stores a list of Layer 2 identifiers for message filtering. The Layer 2 identifiers in the list include local Layer 2 identifiers and application Layer 2 identifiers. The local Layer 2 identifiers are used to filter received unicast messages, and the application Layer 2 identifiers are used to filter received broadcast messages. The adaptation layer compares the destination layer 2 identifier of the received message with the layer 2 identifiers in the layer 2 identifier list; and When the destination layer 2 identifier is the same as one of the layer 2 identifiers in the layer 2 identifier list, the received message is transmitted from the adaptation layer to the dedicated short message protocol layer. When the destination layer 2 identifier is different from all the layer 2 identifiers in the layer 2 identifier list, the received message is discarded at the adaptation layer.

8. The method according to claim 7, wherein, The list of layer 2 identifiers stored for message filtering includes: The local layer 2 identifier is generated based on the local media access control address.

9. The method according to claim 7, further comprising: The adaptation layer receives application identifier indication service primitives from a dedicated management entity or a dedicated short message protocol layer. The parameters of the application identifier indication service primitives include an application identifier and a behavior indication, which includes adding or deleting.

10. The method according to claim 9, wherein, The list of layer 2 identifiers stored for message filtering includes: The application layer two identifier is generated based on the application identifier; and The application layer 2 identifier is added or removed from the layer 2 identifier list according to the behavior instruction.

11. An apparatus for message filtering, comprising: Memory; as well as At least one processor coupled to the memory and configured to perform the method according to any one of claims 1-10.

12. A computer-readable storage medium having stored thereon computer-executable code for performing the method according to any one of claims 1-10.

13. A computer program product comprising instructions executable by a processor to implement the method according to any one of claims 1-10.

Images