Message verification method and communication equipment
By determining the length of the part to be verified based on message type or length information, the problem that A-IoT messages cannot verify the command or data parts separately is solved, achieving higher message integrity and accuracy.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-09-30
- Publication Date
- 2026-04-07
AI Technical Summary
The message format of A-IoT messages is relatively simple, making it impossible to perform separate verification on the command or data parts, thus making it difficult to guarantee the integrity and accuracy of the messages.
By determining the length of the part to be verified based on message type or length information, separate verification of the data part or control information of A-IoT messages can be achieved.
It improves the integrity and accuracy of A-IoT messages and ensures the precision of message verification.
Smart Images
Figure CN121815267A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of communication technology, and in particular to a message verification method and communication device. Background Technology
[0002] Ambient Internet of Things (A-IoT) devices can be applied to scenarios such as smart buildings, asset tracking, agriculture, and smart homes. They are IoT devices that can collect environmental energy from environmental energy sources such as radio waves, light, motion, heat, or any other available environmental energy sources and are driven by environmental energy.
[0003] A-IoT messages have a relatively simple and irregular message format. Therefore, message verification typically only allows for the verification of the entire A-IoT message. It's impossible to separately verify the command or data portions of an A-IoT message, making it difficult to guarantee the integrity and accuracy of the A-IoT message. Summary of the Invention
[0004] This application provides a message verification method and communication device to solve the problem that current A-IoT message verification methods cannot separately verify the command or data parts of A-IoT messages, making it difficult to guarantee the integrity and accuracy of A-IoT messages.
[0005] To achieve the above objectives, the embodiments of this application adopt the following technical solutions:
[0006] In a first aspect, a message verification method is provided, comprising: determining the length of the part of the first message to be verified based on the message type or length information of the first message; determining the part of the first message to be verified based on the length of the part to be verified; and verifying the part to be verified.
[0007] The first message can be an environmental IoT (AIoT) message sent by other devices to the first device. These other devices can be base stations, UEs, readers, etc.
[0008] The portion to be verified mentioned above refers to the corresponding part in the CRC check requirement. Message verification can be performed on the entire first message, or on a portion of the first message. For example, it can be the control information of the first message or the data portion of the first message. That is, the portion to be verified can be the entire first message, the control information of the first message, or the data portion of the first message.
[0009] The message type of the first message mentioned above is used to indicate the specific type of operation indicated by the first message. The message type of the message may include, but is not limited to, message types such as inventory, read, and write.
[0010] Message types can also be specified to include two-step contention-based random access (2-step CBRA) inventory, three-step CBRA inventory, contention-free random access (CFRA) inventory, two-step CBRA reads, three-step CBRA reads, and so on.
[0011] The aforementioned length information can be used to indicate the length of the control information in the first message and / or the length of the data portion of the first message.
[0012] In this embodiment, the length of the data portion of the first message or the length of the control information of the first message is determined by the message type or length information of the first message. This allows the data portion and / or control information of the first message to be obtained separately, fulfilling the need for separate verification of the data portion or control information of the first message and improving the integrity and accuracy of A-IoT messages.
[0013] In one possible implementation of the first aspect, the first message includes message type information, which is used to indicate the message type of the first message; determining the length of the part to be verified of the message according to the message type of the first message includes: if the part to be verified is control information of the first message, then determining the length of the control information of the first message according to the message type of the first message indicated by the message type information of the first message.
[0014] The message type information of the first message can be carried in the command of the network physical layer (L1) of Long Term Evolution (LTE), or it can be carried in the MAC CE command, or it can be carried in the protocol data unit (PDU) of the higher layer.
[0015] For example, taking RTD messages as an example, 2 bits can be set to indicate the message type. For example, 00 indicates that the CE command is a disk storage command, 01 indicates that the message type is a read command, and 10 indicates that the main type of the CE command is a write command.
[0016] In one possible implementation of the first aspect, determining the length of the part to be verified of the message according to the message type of the first message includes: if the part to be verified is the data part of the first message, then determining the length of the control information of the first message according to the message type information of the first message indicating the message type of the first message; and determining the length of the data part of the first message according to the length of the control information of the first message and the total length of the first message.
[0017] In the case where the first message corresponds to the RAN1# scheme, the total length of the first message can be determined by the actual number of bits between the random access preamble and the random access postamble.
[0018] When the first message is a message corresponding to the RAN2# scheme, the total length of the first message can be the bit-aligned total length, and the total length is a multiple of 8 bits.
[0019] After determining the total length of the first message and the length of the control information of the first message, the length of the data portion of the first message can be obtained by subtracting the length of the control information of the first message from the total length of the first message.
[0020] In one possible implementation of the first aspect, determining the length of the control information of the first message according to the message type information of the first message indicates the message type of the first message includes: determining the length of the control information of the first message according to the message type information of the first message indicates the message type of the first message and a first correspondence relationship, wherein the first correspondence relationship indicates the relationship between at least one message type and the length of at least one control information.
[0021] The message type of a message corresponds to the length of its control information. That is, there is a first correspondence between the message type and the length of the control information. After determining the message type of the first message, the length of the control information of the first message can be determined based on the message type and the first correspondence.
[0022] In one possible implementation of the first aspect, the message type information includes main type information and / or subtype information.
[0023] The main type information is used to indicate the main type of the CE command in the first message, and the subtype information is used to indicate the subtype of the CE command in the first message.
[0024] For example, taking RTD messages as an example, 2 bits can be set to indicate the main type. For instance, 00 indicates that the main type of the CE command is a disk storage command, 01 indicates that the main type of the CE command is a read command, and 10 indicates that the main type of the CE command is a write command. 2 bits can also be set to indicate the subtype. For example, 00 indicates triggering a 3-step CBRA, 01 indicates triggering a 2-step CBRA, and 10 indicates a CFRA.
[0025] Segmenting and differentiating message types is beneficial for the subsequent expansion of message types.
[0026] In one possible implementation of the first aspect, the length information of the first message is used to indicate the length of the control information of the first message; determining the length of the portion of the first message to be verified based on the length information of the first message includes:
[0027] If the part to be verified is the control information of the first message, then the length of the control information of the first message is determined according to the length information;
[0028] If the part to be verified is the data part of the first message, then the length of the control information of the first message is determined according to the length information, and the length of the data part of the first message is determined according to the length of the control information of the first message and the total length of the first message.
[0029] The first message sent from the network includes length information indicating the length of control information within the first message. This length information can be located at a preset position within the first message, independent of the message type, or its position can be set according to the message type. This preset position can be on the L1 layer signaling of the downlink PRDCH or uplink PDRCH. Alternatively, the preset position can be set according to the signaling structure, for example, in a subsequent field of the message type.
[0030] In one possible implementation of the first aspect, the length information of the first message is used to indicate the length of the data portion of the first message;
[0031] Based on the length information of the first message, the length of the part of the first message to be verified is determined to include:
[0032] If the part to be verified is the control information of the first message, then the length of the data part of the first message is determined according to the length information, and the length of the control information of the first message is determined according to the length of the data part of the first message and the total length of the first message.
[0033] If the part to be verified is the data part of the first message, then the length of the data part of the first message is determined based on the length information.
[0034] The first message sent from the network includes length information indicating the length of the data portion of the first message. Therefore, the first device can determine the length of the data portion of the first message based on the length information in the first message.
[0035] In one possible implementation of the first aspect, the length information of the first message is located at a preset position in the first message.
[0036] The aforementioned length information can be carried in physical layer information (PRDCH), such as in an L1 layer command, and the length information is independent of subsequent messages. Alternatively, the length information can be carried in higher-layer messages, such as messages generated by the MAC CE or A-IoT layer.
[0037] Optionally, the length information of the first message may also indicate the length of the control information of the first message and the length of the data portion of the first message. That is, the length information of the first message includes length information for indicating the length of the control information of the first message and length information for indicating the length of the data portion of the first message. After receiving the first message, the first device can determine the length of the control information of the first message based on the length information for indicating the length of the control information of the first message, and can also determine the length of the data portion of the first message based on the length information for indicating the length of the data portion of the first message.
[0038] In one possible implementation of the first aspect, the length information of the first message is carried in physical layer information, or the length information of the first message is carried in a higher layer message.
[0039] In one possible implementation of the first aspect, determining the length of the portion of the first message to be verified based on the type of the first message includes:
[0040] The message type of the first message is determined based on the level state information and the second correspondence. The second correspondence is used to indicate the relationship between at least one level state and at least one message type. The level state information is used to indicate the first level state, and the first level state corresponds to the first message type.
[0041] Based on the message type of the first message and the third correspondence, the length of the part of the first message to be verified is determined. The third correspondence is used to indicate the relationship between the length of at least one message type and at least one control information.
[0042] Different voltage levels can correspond to different message types. For example, a low voltage level corresponds to the message type "inventory," while a high voltage level corresponds to the message type "command." Similarly, a low-high-low-high voltage level corresponds to the message type "inventory," while a low-high-high-low voltage level corresponds to the message type "command."
[0043] After determining the message type of the first message based on the level status information of the first message, the first device can uniquely determine the length of the control information of the first message.
[0044] For example, an inventory message may include protocol-defined indications such as process ID, number of device IDs, and RACH type. The number of device IDs is carried in the data section, therefore the length of the control information is fixed; for example, the control information length of an inventory message can be 16 bits. Similarly, a command message may include protocol-defined indications such as process ID, number of device IDs, command type, and RACH type. The number of device IDs and the specific command content are carried in the data section, and the length of its control information is also fixed; for example, the control information length of a command message can be 20 bits. In other words, once the message type of the first message is determined, the length of its control information can be uniquely determined.
[0045] In one possible implementation of the first aspect, the length of the portion of the first message to be verified is determined based on the message type of the first message and the third correspondence, including:
[0046] If the part to be verified is the control information of the first message, then the length of the control information of the first message is determined according to the message type of the first message and the third correspondence.
[0047] In one possible implementation of the first aspect, the length of the portion of the first message to be verified is determined based on the message type of the first message and the third correspondence, including:
[0048] If the part to be verified is the data part of the first message, then the length of the control information of the first message is determined according to the message type of the first message and the third correspondence; the length of the data part of the first message is determined according to the length of the control information of the first message and the total length of the first message.
[0049] In one possible implementation of the first aspect, the level state information is carried in physical layer signaling, or the level state information is carried in a random access preamble.
[0050] Optionally, if the level status information is carried in the Physical Reader to Device Channel (PRDCH), the message type of the first message can be determined based on the level status information in the PRDCH.
[0051] For example, assuming that the level state information in the PRDCH of the first message corresponds to a low level state, and in the second correspondence, the low level state corresponds to inventory, then based on the level state information of the first message and the second correspondence, the message type of the first message can be determined to be inventory.
[0052] For example, assuming that the level state information in the PRDCH of the first message corresponds to a high level state, and that the high level state corresponds to command in the second correspondence, then the message type of the first message can be determined to be command based on the level state information of the first message and the second correspondence.
[0053] Optionally, the message type of the first message is determined by the level status information carried in the preamble, i.e., the level status information existing in the preamble, such as the level status information carried in the signaling start flag or the signaling segmentation flag.
[0054] For example, assuming the level status information in the rdelimeter / start indicato of the first message is low-high-low-high, and the low-high-low-high level corresponds to inventory in the second correspondence, then the message type of the first message can be determined to be inventory based on the level status information of the first message and the second correspondence.
[0055] For example, assuming the level status information in the rdelimeter / start indicato of the first message is low-high-high-low, and the low-high-high-low level corresponds to command in the second correspondence, then the message type of the first message can be determined as command based on the level status information of the first message and the second correspondence.
[0056] For example, assuming the level status information in the rdelimeter / start indicato of the first message is high-low-low-high, and in the second correspondence, high-low-low-high corresponds to disable, then the message type of the first message can be determined to be disable based on the level status information of the first message and the second correspondence.
[0057] In one possible implementation of the first aspect, the first message is an AIoT (Artificial Intelligence of Things) message.
[0058] Secondly, a communication device is provided, which has the function of implementing the message verification method described in the first aspect. The communication device includes at least one module for implementing the message verification method provided in the first aspect.
[0059] Thirdly, a communication device is provided, comprising: one or more processors, and a memory; the memory is coupled to the one or more processors, the memory being used to store computer program code, the computer program code including computer instructions, wherein the one or more processors invoke the computer instructions to cause the communication device to execute the message verification method provided in the first aspect.
[0060] Fourthly, a chip system is provided for use in a communication device. The chip system includes one or more processors, which are used to invoke computer instructions to cause the communication device to execute the message verification method provided in the first aspect.
[0061] Fifthly, a computer-readable storage medium is provided, the computer-readable storage medium including instructions that, when executed on a communication device, cause the communication device to perform the message verification method provided in the first aspect.
[0062] In a sixth aspect, a computer program product is provided, which, when run on a communication device, causes the communication device to execute the message verification method provided in the first aspect.
[0063] The technical effects achieved by the second, third, fourth, fifth, and sixth aspects mentioned above are similar to those achieved by the technical means corresponding to the first aspect mentioned above, and will not be repeated here. Attached Figure Description
[0064] Figure 1 This is a schematic diagram of an environmental Internet of Things (IoT) network topology provided in an embodiment of this application;
[0065] Figure 2 This is a schematic diagram illustrating the implementation process of a message verification method provided in an embodiment of this application;
[0066] Figure 3 This is a schematic diagram illustrating the implementation of another message verification method provided in this application embodiment;
[0067] Figure 4 This is a schematic diagram illustrating the implementation of another message verification method provided in this application embodiment;
[0068] Figure 5 This is a schematic diagram illustrating the implementation of another message verification method provided in this application embodiment;
[0069] Figure 6 This is a schematic diagram of a message format for a first message provided in an embodiment of this application;
[0070] Figure 7 This is a schematic diagram illustrating the implementation of another message verification method provided in this application embodiment;
[0071] Figure 8 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application;
[0072] Figure 9 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application. Detailed Implementation
[0073] In the following description, specific details such as particular system architectures and technologies are set forth for illustrative purposes and not for limiting purposes, in order to provide a thorough understanding of the embodiments of this application. However, those skilled in the art will understand that this application may also be implemented in other embodiments without these specific details.
[0074] It should be understood that, when used in this specification and the appended claims, the term "comprising" indicates the presence of the described features, integrals, steps, operations, elements, and / or components, but does not exclude the presence or addition of one or more other features, integrals, steps, operations, elements, components, and / or collections thereof. The terms "comprising," "including," "having," and variations thereof all mean "including but not limited to," unless otherwise specifically emphasized.
[0075] It should be understood that "one or more" as mentioned in this application refers to one, two, or more, and "multiple" as mentioned in this application refers to two or more. In the description of this application, unless otherwise stated, " / " means "or," for example, A / B can mean A or B. The "and / or" in this document is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone.
[0076] To facilitate a clear description of the technical solutions of this application, the terms "first" and "second" are used to distinguish identical or similar items with essentially the same function and effect. Those skilled in the art will understand that the terms "first" and "second" do not limit the quantity or execution order, and that the terms "first" and "second" do not necessarily imply that they are different.
[0077] The terms "one embodiment" or "some embodiments" used in this application mean that one or more embodiments of this application include the specific features, structures, or characteristics described in that embodiment. Therefore, the phrases "in one embodiment," "in some embodiments," "in other embodiments," "in still other embodiments," etc., appearing in different parts of this application do not necessarily refer to the same embodiment, but rather mean "one or more, but not all, embodiments," unless otherwise specifically emphasized.
[0078] The steps involved in the message verification method provided in this application are merely examples. Not all steps are mandatory, nor are all contents involved in each step required. They can be added or removed as needed during use.
[0079] The same step or step or content with the same function in the embodiments of this application can be referenced and learned from each other in different embodiments.
[0080] The following describes the ambient the internet of things (A-IoT) devices involved in the embodiments of this application.
[0081] Environmental IoT devices (A-IoT devices) are also known as passive IoT devices. They are new types of IoT devices that primarily harvest environmental energy from radio waves, light, motion, heat, or any other available environmental energy source, and use this energy as their power source.
[0082] Environmental IoT devices can be applied in various scenarios, such as smart buildings, asset tracking, agriculture, and smart homes. For example, environmental IoT devices can be smart switches, smart locks, smart meters, sensor-based devices for monitoring machine status and environmental conditions, building automation and control equipment, asset tagging devices, etc., and this application does not limit the specific applications to these. In these scenarios, the networking requirements of environmental IoT devices are generally simple, possibly involving only asset information reporting or sending minimal sensor data.
[0083] Environmental IoT devices typically collect environmental energy that can only generate a very small amount of electricity, which necessitates that these devices be simpler and more energy-efficient. Therefore, environmental IoT devices need to achieve low-power computing and low-power communication.
[0084] In some embodiments, environmental IoT devices can report business data (including but not limited to asset information, sensor data, etc.) to a communication node. This communication node can be a reader, base station, or user equipment (UE). For example, the UE can be a mobile terminal (MT), mobile station (MS), mobile unit (MU), radio unit, remote unit, user agent, mobile client, etc., but this application embodiment does not limit this.
[0085] The message verification method provided in this application embodiment can be applied to the above-mentioned environmental IoT device or the above-mentioned reader / writer. That is, the communication device involved in this application embodiment can be either the above-mentioned environmental IoT device or the above-mentioned reader / writer. This application embodiment does not limit this.
[0086] In practical applications, environmental IoT network topologies can include the following two types:
[0087] Topology 1: such as Figure 1 As shown in Figure (a), an environmental IoT device can communicate with a base station. Communication between the base station and the environmental IoT device can include data and / or signaling.
[0088] Alternatively, in this case, the base station and the environmental IoT device can communicate directly, or the base station and the environmental IoT device can communicate through intermediate nodes (including but not limited to relays, integrated access and backhaul (IAB) nodes, terminals, amplifiers, etc.).
[0089] Topology 2: such as Figure 1 As shown in Figure (b), the environmental IoT device can communicate with the UE. Communication between the UE and the environmental IoT device can include data and / or signaling.
[0090] Alternatively, in this case, the UE can communicate with the base station.
[0091] It should be noted that the embodiments of this application only use the above two topologies as examples to illustrate the networking topologies of the environmental Internet of Things. In actual applications, there may be other different topologies, which are not limited in this application.
[0092] During message transmission, numerous factors can cause errors in the messages received by the receiver. Verification of received messages can improve their accuracy and integrity. Cyclic redundancy check (CRC) is one of the most commonly used verification methods in digital communication.
[0093] To improve the completeness of verification, it is usually necessary to verify the command information or data part of the message separately. However, the message format of current A-IoT messages is simpler and less regular than that of messages such as 5G new radio (NR) messages. Therefore, when performing message verification, it is usually only possible to verify the entire A-IoT message, and it is not possible to verify the command part or data part of the A-IoT message separately.
[0094] Based on this, this application provides a message verification method that determines the length of the data portion or the length of the control information of the first message by using the message type or length information of the first message. This allows for the separate acquisition of the data portion and / or the control information of the first message, fulfilling the need for separate verification of the data portion or the control information of the first message and improving the integrity and accuracy of A-IoT messages.
[0095] See Figure 2 This diagram illustrates a message verification method provided in an embodiment of this application. The embodiment uses an A-IoT device (hereinafter referred to as the first device) as the executing entity to describe the message verification method provided in this application. The method may include the following steps:
[0096] Step 201: The first device determines the length of the part of the first message to be verified based on the message type or length information of the first message.
[0097] In some embodiments, the first message may be an environmental Internet of Things (AIoT) message sent by other devices to the first device. These other devices may be base stations, UEs, readers, or other devices, and this application does not limit them.
[0098] In practical applications, the message format of A-IoT messages is relatively simple and does not distinguish too much from the form of medium access control (MAC) layer protocol data units (PDUs). Under certain security conditions, A-IoT messages usually convert core network (CN) commands into radio access network (RAN) signaling for distribution. The aforementioned first message can be a message distributed by the RAN side. Of course, the aforementioned first message can also be sent by communication nodes such as readers.
[0099] The first device can receive the first message sent by the RAN side and determine the message type or length information of the first message, so that the first device can determine the length of the part to be verified based on the message type or length information of the first message.
[0100] The aforementioned part to be verified refers to the corresponding portion in the CRC verification requirement. It can be understood that the message verification in this embodiment can be performed on the entire first message, or on a portion of the first message. For example, it can be the verification of the control information of the first message, or the verification of the data portion of the first message. That is, the part to be verified can be the entire first message, the control information of the first message, or the data portion of the first message. This embodiment uses the verification requirement where the part to be verified is either the control information or the data portion of the first message, as an example for illustration.
[0101] The message type of the first message mentioned above is used to indicate the specific type of operation indicated by the first message. The message type of the message may include, but is not limited to, message types such as inventory, read, and write.
[0102] In some embodiments, the message type may further be specified as a two-step contention-based random access (2-step CBRA) inventory, a three-step CBRA inventory, a contention-free random access (CFRA) inventory, a 2-step CBRA read, a three-step CBRA read, and so on. The aforementioned length information can be used to indicate the length of the control information in the first message and / or the length of the data portion of the first message.
[0103] Based on the message type of the first message, the length of the part of the first message to be verified can specifically include the following two methods:
[0104] The first method, such as Figure 3 As shown, the first device receives a first message, which includes message type information indicating the message type of the first message. The first device determines the length of the control information in the first message based on the message type indicated by the message type information.
[0105] The above message type information is used to indicate the message type of the first message.
[0106] Here, the first device can determine the length of the control information of the first message based on the message type of the first message.
[0107] In some embodiments, the message type of a message corresponds to the length of the control information of the message, that is, there is a first correspondence between the message type of the message and the length of the control information. After determining the message type of the first message, the length of the control information of the first message can be determined according to the message type of the first message and the first correspondence.
[0108] In practical applications, the aforementioned control information can be information from the MAC control element (CE) part, and the aforementioned message type can be the type of MAC CE command.
[0109] The aforementioned first correspondence is used to indicate the relationship between the length of at least one message type and at least one control information.
[0110] It is understandable that the first device can determine the message type of the first message it indicates based on the message type information of the first message, and determine the length of the control information of the first message based on the message type of the first message and the first correspondence. The message type information of the first message type can uniquely identify a message type and the length of the corresponding control information.
[0111] Here, the first device establishes a correspondence between message types and control information lengths, namely the aforementioned first correspondence. It can be understood that this correspondence can be many-to-one or one-to-one. That is, multiple message types can correspond to one control information length, or one message type can correspond to one control information length, and different message types correspond to different control information lengths.
[0112] In the embodiments of this application, the message type information of the first message can be carried in the command of the network physical layer (L1) of Long Term Evolution (LTE), or the message type information of the first message can be carried in the MAC CE command, or it can be carried in the protocol data unit (PDU) of the higher layer.
[0113] For example, taking RTD messages as an example, 2 bits can be set to indicate the message type. For example, 00 indicates that the CE command is a disk storage command, 01 indicates that the message type is a read command, and 10 indicates that the main type of the CE command is a write command.
[0114] In this example, assuming the message type information included in the first message is 00, the message type of the first message can be determined to be a disk storage command; assuming the message type information included in the first message is 01, the message type of the first message can be determined to be a read command; assuming the message type information included in the first message is 02, the message type of the first message can be determined to be a write command.
[0115] For example, suppose 3 bits are set to indicate the message type, such as 000 indicating a 3-step CBRA disk save command, 001 indicating a 2-step CBRA disk save command, 010 indicating a CFRA disk save command, 011 indicating a read command, 101 indicating a write command, etc.
[0116] In this example, assuming the message type information included in the first message is 000, the message type of the first message can be determined to be a 3-step CBRA disk storage command; assuming the message type information included in the first message is 001, the message type of the first message can be determined to be a 2-step CBRA disk storage command; assuming the message type information included in the first message is 011, the message type of the first message can be determined to be a read command.
[0117] In some embodiments, the aforementioned message type information may specifically include main type information and / or subtype information. The main type information indicates the main type of the CE command in the first message, and the subtype information indicates the subtype of the CE command in the first message. Segmenting and distinguishing message types facilitates the expansion of subsequent message types.
[0118] For example, taking RTD messages as an example, 2 bits can be set to indicate the main type. For instance, 00 indicates that the main type of the CE command is a disk storage command, 01 indicates that the main type of the CE command is a read command, and 10 indicates that the main type of the CE command is a write command. 2 bits can also be set to indicate the subtype. For example, 00 indicates triggering a 3-step CBRA, 01 indicates triggering a 2-step CBRA, and 10 indicates a CFRA.
[0119] If the message type information included in the first message is 0000, then the message type of the first message can be determined to be a 3-step CBRA disk storage command; if the message type information included in the first message is 0001, then the message type of the first message can be determined to be a 2-step CBRA disk storage command.
[0120] In some embodiments, after the first device determines the message type of the first message based on the message type information of the first message, in addition to determining the length of the control information of the first message based on the first correspondence mentioned above, it can also calculate the length occupied by the feature parameters in the data portion based on the message type and the feature parameters in the control information, and then further determine the length of the control information. The feature parameters in the control information may be the number of device IDs in the control information, and the number of bits occupied by the device IDs in the data portion can be deduced based on the number of device IDs.
[0121] For example, taking the message type of the first message as a disk storage command, the control information contains some fields with a fixed number of bits, such as the disk storage type and the reply type. However, the number of devices to be disked in the control information is variable. The number of devices to be disked depends on the number of device IDs added to the control information. Once the fixed length of the device ID and the number of devices are determined, the length of the variable part can be obtained. The length of the control part can be obtained by adding the fields with the fixed number of bits to the length of the variable part.
[0122] As can be seen from the above, the message type information indicates the message type of the first message. The first device can determine the message type of the first message based on the message type information. After determining the message type of the first message, the length of the control information of the first message can be further determined. The part to be verified can be either the control information or the data part of the first message. Therefore, the first device can determine the length of the part to be verified based on the message type of the first message indicated by the message type information, which may include the following situations:
[0123] Case 1: The part to be verified is the control information of the first message.
[0124] In this case, the first device can determine the length of the control information of the first message based on the message type of the first message indicated by the message type information of the first message. Specifically, it can determine the length of the control information of the first message based on the message type of the first message and the first correspondence, that is, the length of the part to be verified.
[0125] Case 2: The part to be verified is the data part of the first message.
[0126] In this case, the first device can determine the length of the control information of the first message based on the message type information of the first message, and then determine the length of the data part of the first message based on the length of the control information of the first message and the total length of the first message, thus obtaining the length of the part to be verified.
[0127] Here, we will explain how to determine the total length of the first message:
[0128] When the first message corresponds to the RAN1# scheme, the total length of the first message can be determined by the actual number of bits between the random access preamble and the random access postamble.
[0129] When the first message is a message corresponding to the RAN2# scheme, the total length of the first message can be the bit-aligned total length, and the total length is a multiple of 8 bits.
[0130] The RAN1# and RAN2# schemes can be found in the relevant content on A-IoT determined at the 3GPP TSG RAN 102 meeting, which will not be elaborated here.
[0131] After determining the total length of the first message and the length of the control information of the first message, the length of the data portion of the first message can be obtained by subtracting the length of the control information of the first message from the total length of the first message.
[0132] The second method, such as Figure 4 As shown, the first message may also include level status information. The first device can determine the message type of the first message based on the level status information and the second correspondence. After determining the message type of the first message, the length of the control information of the first message can be further determined based on the message type of the first message and the third correspondence.
[0133] The second correspondence is used to indicate the relationship between at least one level state and at least one message type, and the aforementioned level state information is used to indicate the first level state, which corresponds to the first message type.
[0134] The third correspondence is used to indicate the relationship between the length of at least one message type and at least one control information.
[0135] In this embodiment, the message type of A-IoT message may include at least one preset message type, and each preset message type corresponds to a level state. For example, the message type of A-IoT message may include inventory, command, disable, enable, kill, read, write, etc.; or, the message type of A-IoT message may include both inventory and command.
[0136] It should be noted that the above is only an example and not a limitation. The number of preset message types included in the A-IoT message types can be determined according to the actual application.
[0137] It is understandable that different voltage levels can correspond to different message types. For example, a low voltage level corresponds to the message type "inventory," while a high voltage level corresponds to the message type "command." Similarly, a low-high-low-high voltage level corresponds to the message type "inventory," while a low-high-high-low voltage level corresponds to the message type "command."
[0138] It is understandable that the above correspondence between level states and message types is only an example. In actual applications, it can be set according to application requirements. For example, a correspondence can be set between low level state and command, that is, the message type corresponding to low level state is command, and a correspondence can be set between high level state and inventory, that is, the message type corresponding to high level state is inventory.
[0139] In this embodiment of the application, each preset type of control information corresponds to it, so the length of the control information is uniquely determined. That is, after the first device determines the message type of the first message based on the level status information of the first message, it can uniquely determine the length of the control information of the first message.
[0140] For example, an inventory message may include protocol-defined indications such as process ID, number of device IDs, and RACH type. The number of device IDs is carried in the data section, therefore the length of the control information is fixed; for example, the control information length of an inventory message can be 16 bits. Similarly, a command message may include protocol-defined indications such as process ID, number of device IDs, command type, and RACH type. The number of device IDs and the specific command content are carried in the data section, and the length of its control information is also fixed; for example, the control information length of a command message can be 20 bits. In other words, once the message type of the first message is determined, the length of its control information can be uniquely determined.
[0141] In practical applications, the aforementioned level state information can be carried in physical layer signaling or in a preamble.
[0142] In one embodiment of this application, when the level status information is carried in the Physical Reader to Device Channel (PRDCH), the message type of the first message can be determined based on the level status information in the PRDCH.
[0143] For example, assuming that the level state information in the PRDCH of the first message corresponds to a low level state, and in the second correspondence, the low level state corresponds to inventory, then based on the level state information of the first message and the second correspondence, the message type of the first message can be determined to be inventory.
[0144] For example, assuming that the level state information in the PRDCH of the first message corresponds to a high level state, and that the high level state corresponds to command in the second correspondence, then the message type of the first message can be determined to be command based on the level state information of the first message and the second correspondence.
[0145] In one embodiment of this application, the message type of the first message is determined by the level state information carried in the preamble, that is, the level state information existing in the preamble, such as the level state information carried in the signaling start flag or the signaling segmentation flag.
[0146] For example, assuming the level status information in the rdelimeter / start indicato of the first message is low-high-low-high, and the low-high-low-high level corresponds to inventory in the second correspondence, then the message type of the first message can be determined to be inventory based on the level status information of the first message and the second correspondence.
[0147] For example, assuming the level status information in the rdelimeter / start indicato of the first message is low-high-high-low, and the low-high-high-low level corresponds to command in the second correspondence, then the message type of the first message can be determined as command based on the level status information of the first message and the second correspondence.
[0148] For example, assuming the level status information in the rdelimeter / start indicato of the first message is high-low-low-high, and in the second correspondence, high-low-low-high corresponds to disable, then the message type of the first message can be determined to be disable based on the level status information of the first message and the second correspondence.
[0149] Once the first device determines the message type of the first message, it can determine the length of the part to be verified based on the message type of the first message.
[0150] Here, after the first device determines the message type of the first message, it can determine the length of the control information of the first message based on the message type of the first message and the third correspondence. The part to be verified can be either the control information or the data part of the first message. Therefore, the first device can determine the length of the part to be verified based on the message type information of the first message and the third correspondence, which may include the following situations:
[0151] Case 1: The part to be verified is the control information of the first message.
[0152] In this case, the first device can determine the length of the control information of the first message, i.e. the length of the part to be verified, based on the message type of the first message and the third correspondence.
[0153] Case 2: The part to be verified is the data part of the first message.
[0154] In this case, the first device can determine the length of the control information of the first message based on the message type of the first message and the third correspondence, and then determine the length of the data part of the first message based on the length of the control information of the first message and the total length of the first message, thus obtaining the length of the part to be verified.
[0155] The method for determining the total length of the first message has been explained in the previous embodiment and will not be repeated here.
[0156] The above explains how to determine the length of the part to be verified in the first message based on its message type. The following explains how to determine the length of the part to be verified in the first message based on its length information:
[0157] In one embodiment of this application, as Figure 5 As shown, the length information of the first message can be used to indicate the length of the control information of the first message.
[0158] In practical applications, the first message sent by the network includes length information indicating the length of control information in the first message. This length information can be located at a preset position in the first message, regardless of the message type, or the position of the length information can be set according to the message type. The preset position can be on the L1 layer signaling of the downlink PRDCH or uplink PDRCH. Of course, the preset position can also be set according to the structure of the signaling, for example, it can be set in a subsequent field of the message type. This application embodiment does not specify the specific position.
[0159] For example, please see Figure 6 , Figure 6 The illustration shows a schematic diagram of the message format of the first message provided in an embodiment of this application, wherein the first message includes length information, control information, CRC checksum, and data portion.
[0160] It should be noted that the aforementioned length information can be carried in physical layer information (PRDCH), such as in the L1 layer command, and the length information is independent of subsequent messages. Alternatively, the aforementioned length information can be carried in higher-layer messages, such as messages generated by the MAC CE or A-IoT layer.
[0161] In some embodiments, when the length information is carried in a higher-level message, the entire higher-level message needs to be checked with a CRC check before the length information can be obtained.
[0162] Here, the first device can determine the length of the portion to be verified based on the length information of the first message. Similarly, the portion to be verified can be either the control information of the first message or the data portion of the first message. Therefore, determining the length of the portion to be verified based on the length information of the first message can include the following two cases:
[0163] Case 1: The part to be verified is the control information of the first message.
[0164] Since the length information of the first message is used to indicate the length of the control information of the first message, the length of the control information of the first message can be determined directly based on the length information of the first message, that is, the length of the part to be verified is obtained.
[0165] Case 2: The part to be verified is the data part of the first message.
[0166] Since the length information of the first message is used to indicate the length of the control information of the first message, the length of the control information of the first message can be determined based on the length information of the first message. Then, based on the length of the control information of the first message and the total length of the first message, the length of the data part of the first message can be determined, thus obtaining the length of the part to be verified.
[0167] The method for determining the total length of the first message has been explained in the previous embodiment and will not be repeated here.
[0168] In some embodiments, such as Figure 7 As shown, the length information described above can also be used to indicate the length of the data portion of the first message.
[0169] In practical applications, the first message sent by the network includes length information indicating the length of the data portion of the first message. Therefore, the first device can determine the length of the data portion of the first message based on the length information in the first message.
[0170] The portion to be verified can be either the control information of the first message or the data portion of the first message. Therefore, determining the length of the portion to be verified based on the length information of the first message can include the following two cases:
[0171] Case 1: The part to be verified is the control information of the first message.
[0172] Since the length information of the first message is used to indicate the length of the data part of the first message, the length of the data part of the first message can be determined based on the length information of the first message. Then, based on the length of the data part of the first message and the total length of the first message, the length of the control information of the first message can be determined, thus obtaining the length of the part to be verified.
[0173] Case 2: The part to be verified is the data part of the first message.
[0174] Since the length information of the first message is used to indicate the length of the data part of the first message, the length of the data part of the first message can be determined based on the length information of the first message, that is, the length of the part to be verified is obtained.
[0175] The method for determining the total length of the first message has been explained in the previous embodiment and will not be repeated here.
[0176] It is understood that the length information of the first message can also indicate the length of the control information of the first message and the length of the data part of the first message. That is, the length information of the first message includes length information used to indicate the length of the control information of the first message and length information used to indicate the length of the data part of the first message. After receiving the first message, the first device can determine the length of the control information of the first message based on the length information used to indicate the length of the control information of the first message, and can also determine the length of the data part of the first message based on the length information used to indicate the length of the data part of the first message.
[0177] Step 202: The first device determines the part of the first message to be verified based on the length of the part to be verified in the first message.
[0178] In practical applications, after determining the length of the part to be verified, the first message can be divided into the part to be verified and other parts, which are the parts that do not need to be verified.
[0179] It is understandable that the aforementioned first message includes control information and data. When the part to be verified is the control information of the first message, the control information of the corresponding first message can be obtained after determining the length of the control information of the first message; when the part to be verified is the data part of the first message, the data part of the corresponding first message can be obtained after determining the length of the data part of the first message.
[0180] Step 203: The first device verifies the part to be verified.
[0181] In this embodiment of the application, after the first device obtains the part to be verified, it can perform CRC verification on the part to be verified, thereby fulfilling the requirement of separate verification of the control information or data part of the first message, and improving the integrity and accuracy of the received first message.
[0182] As can be seen from the above, the message verification method provided in this application embodiment can determine the length of the data part of the first message or the length of the control information of the first message through the message type or length information of the first message, and then can separately obtain the data part and / or the control information of the first message, so as to realize the need for separate verification of the data part or the control information of the first message and improve the integrity and accuracy of A-IoT messages.
[0183] Figure 8This is a schematic diagram of the structure of a communication device provided in an embodiment of this application. This communication device can be the first device described above. See also... Figure 8 The communication device includes at least one processor 801, a communication bus 802, a memory 803, and at least one communication interface 804.
[0184] The processor 801 may be a microprocessor (including a central processing unit (CPU) or the like), an application-specific integrated circuit (ASIC), or one or more integrated circuits used to control the execution of the program of the present application.
[0185] The communication bus 802 may include a path for transmitting information between the aforementioned components.
[0186] The memory 803 may be a read-only memory (ROM), random access memory (RAM), electrically erasable programmable read-only memory (EEPROM), optical disc (including compact disc read-only memory (CD-ROM), compressed optical disc, laser disc, digital versatile optical disc, Blu-ray disc, etc.), magnetic disk storage medium, or other magnetic storage device, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures that can be accessed by a computer, but not limited thereto. The memory 803 may exist independently and be connected to the processor 801 via the communication bus 802. The memory 803 may also be integrated with the processor 801.
[0187] The communication interface 804 uses any transceiver-like device to communicate with other devices or communication networks, such as Ethernet, radio access network (RAN), wireless local area network (WLAN), etc.
[0188] As an example, processor 801 may include one or more CPUs, such as Figure 8 CPU0 and CPU1 are shown in the diagram.
[0189] As an example, the communication device may include multiple processors, such as Figure 8The processors 801 and 805 are shown. Each of these processors can be a single-core processor or a multi-core processor. A processor here can refer to one or more devices, circuits, and / or processing cores used to process data (such as computer program instructions).
[0190] As an example, the communication device may also include an output device 806 and an input device 807. The output device 806 communicates with the processor 801 and can display information in various ways. For example, the output device 806 may be a liquid crystal display (LCD), a light-emitting diode (LED) display device, a cathode ray tube (CRT) display device, or a projector, etc. The input device 807 communicates with the processor 801 and can receive user input in various ways. For example, the input device 807 may be a mouse, keyboard, touchscreen device, or sensing device, etc.
[0191] The memory 803 stores program code 810 for executing the scheme of this application, and the processor 801 executes the program code 810 stored in the memory 803. This communication device can implement the above-mentioned... Figure 2 The message verification method provided in the embodiment.
[0192] Figure 9 This is a schematic diagram of a communication device provided in an embodiment of this application. The device can be implemented as part or all of a communication equipment by software, hardware, or a combination of both. This communication device can be as described above. Figure 8 The communication device described in the embodiment. See also Figure 9 The device includes: a first determining module 901, a second determining module 902, and a verification module 903.
[0193] The first determining module 901 is used to determine the length of the part of the first message to be verified based on the message type or length information of the first message.
[0194] The second determining module 902 is used to determine the part of the first message to be verified based on the length of the part to be verified.
[0195] The verification module 903 is used to verify the part to be verified.
[0196] In this embodiment, the length of the data portion of the first message or the length of the control information of the first message is determined by the message type or length information of the first message. This allows the data portion and / or control information of the first message to be obtained separately, fulfilling the need for separate verification of the data portion or control information of the first message and improving the integrity and accuracy of A-IoT messages.
[0197] It should be noted that the communication device provided in the above embodiments is only illustrated by the division of the above functional modules when performing message verification. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.
[0198] The functional units and modules in the above embodiments can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit. Furthermore, the specific names of the functional units and modules are only for easy differentiation and are not intended to limit the scope of protection of the embodiments of this application.
[0199] The communication device and message verification method embodiments provided in the above embodiments belong to the same concept. The specific working process and technical effects of the units and modules in the above embodiments can be found in the method embodiment section, and will not be repeated here.
[0200] It should be understood that the sequence number of each step in the above embodiments does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.
[0201] In the above embodiments, the descriptions of each embodiment have different focuses. For parts that are not described in detail or recorded in a certain embodiment, please refer to the relevant descriptions of other embodiments.
[0202] This application also provides a computer-readable storage medium storing a computer program that, when executed by a processor, can implement the steps in the various method embodiments described above.
[0203] This application also provides a computer program product that, when run on a communication device, enables the communication device to implement the steps described in the various method embodiments above.
[0204] This application also provides a chip system including a processor coupled to a memory. The processor executes a computer program stored in the memory to implement the steps of any method embodiment of this application. The chip system can be a single chip or a chip module composed of multiple chips.
[0205] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product. This computer program product includes one or more computer instructions. When these computer instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic cable, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave) means. The computer-readable storage medium can be any available medium accessible to a computer, or a data storage device such as a server or data center that integrates one or more available media. The available media can be magnetic media (such as floppy disks, hard disks, magnetic tapes, etc.), optical media (such as Digital Versatile Discs (DVDs), etc.) or semiconductor media (such as Solid State Disks (SSDs), etc.).
[0206] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties. Furthermore, the collection, use and processing of the relevant data must comply with the relevant regulations and standards of the relevant countries and regions, and corresponding operation entry points are provided for users to choose to authorize or refuse.
[0207] The above-described embodiments are optional embodiments provided by this application and are not intended to limit this application. Any modifications, equivalent substitutions, improvements, etc., made within the technical scope disclosed in this application should be included within the protection scope of this application.
Claims
1. A message verification method, characterized in that, The method includes: The length of the part of the first message to be verified is determined based on the message type or length information of the first message. The portion to be verified in the first message is determined based on the length of the portion to be verified. The part to be verified is then verified.
2. The message verification method according to claim 1, characterized in that, The first message includes message type information, which indicates the message type of the first message; Determining the length of the portion of the message to be verified based on the message type of the first message includes: If the part to be verified is the control information of the first message, then the length of the control information of the first message is determined according to the message type of the first message indicated by the message type information of the first message.
3. The message verification method according to claim 2, characterized in that, Determining the length of the portion of the message to be verified based on the message type of the first message includes: If the part to be verified is the data part of the first message, then the length of the control information of the first message is determined according to the message type of the first message indicated by the message type information of the first message; The length of the data portion of the first message is determined based on the length of the control information in the first message and the total length of the first message.
4. The message verification method according to claim 2 or 3, characterized in that, Determining the length of the control information of the first message based on the message type information of the first message includes: The length of the control information of the first message is determined based on the message type information of the first message and the first correspondence relationship indicated by the message type information of the first message. The first correspondence relationship indicates the relationship between the length of at least one message type and at least one control information.
5. The message verification method according to any one of claims 2 to 4, characterized in that, The message type information includes main type information and / or subtype information.
6. The message verification method according to claim 1, characterized in that, The length information of the first message is used to indicate the length of the control information in the first message; Determining the length of the portion of the first message to be verified based on the length information of the first message includes: If the part to be verified is the control information of the first message, then the length of the control information of the first message is determined according to the length information; If the part to be verified is the data part of the first message, then the length of the control information of the first message is determined according to the length information, and the length of the data part of the first message is determined according to the length of the control information of the first message and the total length of the first message.
7. The message verification method according to claim 1, characterized in that, The length information of the first message is used to indicate the length of the data portion of the first message; Determining the length of the portion of the first message to be verified based on the length information of the first message includes: If the part to be verified is the control information of the first message, then the length of the data part of the first message is determined according to the length information, and the length of the control information of the first message is determined according to the length of the data part of the first message and the total length of the first message. If the part to be verified is the data part of the first message, then the length of the data part of the first message is determined according to the length information.
8. The message verification method according to any one of claims 1 to 7, characterized in that, The length information of the first message is located at a preset position in the first message.
9. The message verification method according to any one of claims 1 to 8, characterized in that, The length information of the first message is carried in physical layer information, or the length information of the first message is carried in higher layer messages.
10. The message verification method according to claim 1, characterized in that, Determining the length of the portion of the first message to be verified based on the type of the first message includes: The message type of the first message is determined based on the level state information and the second correspondence. The second correspondence is used to indicate the relationship between at least one level state and at least one message type. The level state information is used to indicate the first level state, and the first level state corresponds to the first message type. Based on the message type of the first message and the third correspondence, the length of the part of the first message to be verified is determined, wherein the third correspondence is used to indicate the relationship between the length of at least one message type and at least one control information.
11. The message verification method according to claim 10, characterized in that, Determining the length of the portion of the first message to be verified based on the message type of the first message and the third correspondence includes: If the part to be verified is the control information of the first message, then the length of the control information of the first message is determined according to the message type of the first message and the third correspondence.
12. The message verification method according to claim 10, characterized in that, Determining the length of the portion of the first message to be verified based on the message type of the first message and the third correspondence includes: If the part to be verified is the data part of the first message, then the length of the control information of the first message is determined according to the message type of the first message and the third correspondence. The length of the data portion of the first message is determined based on the length of the control information in the first message and the total length of the first message.
13. The message verification method according to any one of claims 10 to 12, characterized in that, The level state information is carried in physical layer signaling, or the level state information is carried in random access preamble.
14. The message verification method according to any one of claims 1 to 13, characterized in that, The first message is an AIoT (Artificial Intelligence of Things) message.
15. A communication device, characterized in that, The communication device includes a processor and a storage medium, the storage medium storing instructions that, when executed by the processor, cause the message verification method according to any one of claims 1 to 14 to be implemented.
16. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes instructions that, when executed by a processor, cause the message verification method according to any one of claims 1 to 14 to be implemented.
17. A computer program product, characterized in that, The computer program product includes instructions that, when executed by a processor, cause the message verification method according to any one of claims 1 to 14 to be implemented.