Communication method and apparatus

Abstract

The application provides a communication method and device, relates to the fields of Internet of Things and communication technology. For the Internet of Things device, the method comprises the following steps: receiving downlink data, the downlink data carrying downlink identification information and at least one type of downlink information, the downlink identification information being used for indicating the corresponding type of downlink information; and identifying the type of the at least one type of downlink information according to the downlink identification information. For the Internet of Things device, the method comprises the following steps: receiving downlink data, the downlink data carrying at least one type of downlink information at at least one downlink resource position, the downlink resource position corresponding to the type of downlink information; and when the downlink information is received at the at least one downlink resource position, determining that the type of the received downlink information is the type of downlink information corresponding to the at least one downlink resource position. The scheme solves the problem of distinguishing different types of information in the same channel.

Description

Communication method and device

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of China on April 3, 2024, with application number 202410417478.8 and invention name “Communication Method and Device”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of Internet of Things technology, and in particular to a communication method and device. Background Art

[0003] The Ambient IoT (Ambient IoT), also known as the Passive IoT, is an IoT network comprised of devices with limited or no battery storage. These devices rely on energy harvested from the environment, such as solar energy, radio waves, motion, vibration, heat, or pressure. Cellular-based Passive IoT technology can leverage existing large-scale cellular infrastructure to reduce costs while also improving the coverage of Passive IoT, leveraging mature cellular technologies such as interference management and mobility management.

[0004] However, the current passive IoT technology based on cellular communication needs to transmit different information on the same channel when implementing communication. Therefore, there is an urgent need for a communication method to solve the problem of distinguishing different types of information on the same channel. Summary of the Invention

[0005] In order to solve the above problems, the present application provides a communication method and device, which solves the problem of distinguishing different types of information in the same channel.

[0006] In a first aspect, the present application provides a communication method that can be applied to an Internet of Things device, the method comprising: receiving downlink data, the downlink data carrying downlink identification information and at least one type of downlink information, the downlink identification information being used to indicate the corresponding category of downlink information; and identifying the type of at least one type of downlink information based on the downlink identification information.

[0007] In this implementation, when a connection is established between a network device and an IoT device, the network device can send downlink data to the IoT device. The downlink data carries downlink identification information and at least one type of downlink information. The downlink identification information is used to indicate the corresponding type of downlink information. After receiving the downlink data, the IoT device can identify the type of at least one type of downlink information based on the downlink identification information. This allows multiple types of downlink information to be sent on a single physical channel, and the IoT device can also identify the type of downlink information, solving the problem of distinguishing different types of information on the same channel.

[0008] In one possible implementation, when the IoT device has the capability to send information to the network device, the method further includes: sending uplink data, where the uplink data carries uplink identification information and at least one type of uplink information, wherein the uplink identification information is used to indicate the corresponding type of uplink information.

[0009] In this implementation, when a connection is established between a network device and an IoT device, the network device receives uplink data sent by the IoT device. The uplink data carries uplink identification information and at least one type of uplink information. The uplink identification information is used to indicate the corresponding type of uplink information. After receiving the uplink data, the network device can identify the type of at least one type of uplink information based on the uplink identification information. Therefore, even if multiple types of uplink information are sent on a single uplink physical channel, the network device can still identify the type of uplink information, solving the problem of distinguishing different types of information on the same channel.

[0010] In one possible implementation, the uplink information identifier and the downlink information identifier are preamble codes, and the type of at least one type of downlink information is identified based on the downlink identification information, including: determining the type of at least one type of downlink information based on the length of the preamble code; before sending the uplink data, it also includes: determining the length of the preamble code corresponding to at least one type of uplink information.

[0011] In one possible implementation, the uplink information identifier and the downlink information identifier are preamble codes, and the type of at least one type of downlink information is identified based on the downlink identifier information, including: determining the type of at least one type of downlink information based on the sequence type of the preamble code, where the sequence type of the preamble code is one of the following: pseudo-random PN sequence, longest linear feedback shift register sequence, Gold sequence, and Zadoff-Chu sequence; before sending the uplink data, it also includes: determining the sequence type of the preamble code corresponding to the at least one type of uplink information.

[0012] In one possible implementation, the uplink information identifier and the downlink information identifier are preamble codes, and the type of at least one type of downlink information is identified based on the downlink identification information, including: determining the type of at least one type of downlink information based on the sequence of the preamble code; before sending the uplink data, it also includes: determining the sequence of the preamble code corresponding to the at least one type of uplink information.

[0013] In a possible implementation, a sequence of preamble codes indicating each type of uplink information and downlink information is generated by corresponding generation parameters.

[0014] In one possible implementation, the uplink information identifier and the downlink information identifier serve as preamble codes, and based on the downlink identification information, the type of at least one type of downlink information is identified, including: determining the type of at least one type of downlink information based on a first sequence and a sequence of the downlink identification information, wherein the sequence in the downlink identification information is generated by cyclically shifting the first sequence in a corresponding manner; before sending the uplink data, the method further includes: determining a cyclic shift mode corresponding to at least one type of uplink data, and cyclically shifting the second sequence according to the corresponding cyclic shift mode to generate a preamble code corresponding to at least one type of uplink information.

[0015] In one possible implementation, the uplink information identifier and the downlink information identifier are preamble codes, and the type of at least one type of downlink information is identified based on the downlink identification information, including: determining the type of at least one type of downlink information based on the encoding method of the preamble code, and the encoding method of the preamble code is one of the following: Manchester encoding, pulse width PIE encoding, Miller encoding, and pulse position PPM encoding; before sending the uplink data, it also includes: determining the encoding method of the preamble code corresponding to at least one type of uplink information.

[0016] In one possible implementation, the downlink information identifier is a first field in the downlink data that is at a first position and occupies a first number of bits. Based on the downlink identification information, the type of at least one type of downlink information is identified, including: determining the type of at least one type of downlink information based on the sequence of the first field; the uplink information identifier is a second field in the uplink data that is at a second position and occupies a second number of bits. Before sending the uplink data, it also includes: determining the sequence of the second fields corresponding to at least one type of uplink information.

[0017] In one possible implementation, the downlink information identifier is a third field in the downlink data that is in the third position and occupies a third number of bits. According to the downlink identification information, the type of at least one type of downlink information is identified, including: determining the type of at least one type of downlink information according to the encoding method of the third field, the encoding method is one of the following: Manchester encoding, pulse width PIE encoding, Miller encoding, pulse position PPM encoding; the uplink information identifier is a fourth field in the uplink data that is in the fourth position and occupies a fourth number of bits. Before sending the uplink data, it also includes: determining the encoding method of the fourth field corresponding to at least one type of uplink information.

[0018] In one possible implementation, the downlink information identifier is the fifth field in the downlink data that is at the fifth position and occupies the fifth number of bits. According to the downlink identification information, the type of at least one type of downlink information is identified, including: determining the type of at least one type of downlink information according to the modulation method of the fifth field; the uplink information identifier is the sixth field in the uplink data that is at the sixth position and occupies the sixth number of bits. Before sending the uplink data, it also includes: determining the modulation method of the sixth field corresponding to at least one type of uplink information.

[0019] In one possible implementation, the uplink information identifier and the downlink information identifier are cyclic redundancy check CRC codes, and the type of at least one type of downlink information is identified based on the downlink identification information, including: determining the type of at least one type of downlink information based on the number of bits of the CRC code; before sending the uplink data, it also includes: determining the number of bits of the CRC code corresponding to at least one type of uplink information.

[0020] In one possible implementation, the uplink information identifier and the downlink information identifier are cyclic redundancy check (CRC) codes. Based on the downlink identifier information, the type of at least one type of downlink information is identified, including: determining the type of at least one type of downlink information based on the radio network temporary identifier (RNTI) used when scrambling the CRC code; before sending the uplink data, it also includes: determining the RNTI used when scrambling the CRC codes corresponding to the at least one type of uplink information.

[0021] In one possible implementation, at least one type of downlink information includes a first type of downlink information and a second type of downlink information, the first type of downlink information includes broadcast information, the first type of downlink information corresponds to first downlink identification information, the second type of downlink information includes downlink control information and downlink data information, and the second type of downlink information corresponds to second downlink identification information; at least one type of uplink information includes a first type of uplink information and a second type of uplink information, the first type of uplink information includes access information, the first type of uplink information corresponds to first uplink identification information, the second type of uplink information includes uplink control information and uplink data information, and the second type of uplink information corresponds to second uplink identification information.

[0022] In a second aspect, the present application also provides a communication method that can be applied to Internet of Things devices, the method comprising: receiving downlink data, wherein the downlink data carries at least one type of downlink information in at least one downlink resource location, and the downlink resource location corresponds to the type of the downlink information; when downlink information is received in at least one downlink resource location, determining that the type of the received downlink information is the type of downlink information corresponding to at least one downlink resource location.

[0023] This implementation allows network devices and IoT devices to use the resource location of information to distinguish between different types of information when establishing a connection. Even when multiple types of downlink information are sent on a single physical channel, the IoT device can identify the type of downlink information based on its resource location, solving the problem of distinguishing different types of information on the same channel.

[0024] In one possible implementation, when the IoT device has the ability to send uplink data to the network device, the method further includes: sending uplink data, wherein the uplink data carries at least one type of uplink information in at least one uplink resource location, and the uplink resource location corresponds to the type of uplink information.

[0025] With this implementation, when an IoT device sends multiple types of uplink information on an uplink physical channel, the network device can use the signal's resource location to distinguish the signal type, thereby solving the problem of distinguishing different types of information on the same channel.

[0026] In one possible implementation, the downlink resource position and the uplink resource position are frequency domain resource positions. When downlink information is received at at least one downlink resource position, the type of the received downlink information is determined to be the type of downlink information corresponding to at least one downlink resource position, specifically including: when downlink information is received at at least one downlink frequency domain resource position, the type of corresponding downlink information is determined according to the downlink frequency domain resource position, the frequency domain resource position is one of the following: the position of the resource element RE, the position of the resource element RE group, the RE group including multiple REs; before sending uplink data, it also includes: determining the uplink frequency domain resource positions corresponding to at least one type of uplink information.

[0027] In one possible implementation, the uplink resource location and the downlink resource location are frequency domain resource locations. When downlink information is received at at least one downlink resource location, the type of the received downlink information is determined to be the type of downlink information corresponding to the at least one downlink resource location, specifically including: when downlink information is received at at least one downlink frequency domain resource location, determining the type of corresponding downlink information according to the spread spectrum code of the downlink frequency domain resource location; before sending uplink data, further including: determining the spread spectrum codes corresponding to at least one type of uplink information.

[0028] In one possible implementation, the uplink resource location and the downlink resource location are time domain resource locations. When downlink information is received at at least one downlink resource location, the type of the received downlink information is determined to be the type of downlink information corresponding to at least one downlink resource location. Specifically, the method includes: when downlink information is received at at least one downlink time domain resource location, the type of corresponding downlink information is determined according to the downlink time domain resource location, and the time configuration parameter of the time domain resource location is one of the following: system frame number SFN, time slot number, orthogonal frequency division multiplexing OFDM symbol number, and OFDM symbol offset value; before sending uplink data, the method also includes: determining the uplink time domain resource locations corresponding to at least one type of uplink information.

[0029] In one possible implementation, at least one type of downlink information includes a first type of downlink information and a second type of downlink information, the first type of downlink information includes broadcast information, the first type of downlink information corresponds to a first downlink resource position, the second type of downlink information includes downlink control information and downlink data information, the second type of downlink information corresponds to a second downlink resource position; at least one type of uplink information includes a first type of uplink information and a second type of uplink information, the first type of uplink information includes access information, the first type of uplink information corresponds to a first uplink resource position, the second type of uplink information includes uplink control information and uplink data information, the second type of uplink information corresponds to a second uplink resource position.

[0030] On the third aspect, the present application also provides a communication method that can be applied to a network device, the method comprising: sending downlink data, wherein the downlink data carries downlink identification information and at least one category of downlink information, and the downlink identification information is used to indicate the corresponding category of downlink information.

[0031] In one possible implementation, the method further includes: receiving uplink data, the uplink data carrying uplink identification information and at least one category of uplink information, the uplink identification information being used to indicate the corresponding category of uplink information; and identifying the type of at least one category of uplink information based on the uplink identification information.

[0032] In one possible implementation, the uplink information identifier and the downlink information identifier are preamble codes. Before sending the downlink data, it also includes: determining the length of the preamble code corresponding to at least one type of downlink information; identifying the type of at least one type of uplink information based on the uplink identification information, including: determining the type of at least one type of uplink information based on the length of the preamble code.

[0033] In one possible implementation, the uplink information identifier and the downlink information identifier are preamble codes. Before sending the downlink data, it also includes: determining the sequence type of the preamble code corresponding to at least one type of downlink information, where the sequence type of the preamble code is one of the following: pseudo-random PN sequence, longest linear feedback shift register sequence, Gold sequence, Zadoff-Chu sequence; identifying the type of at least one type of uplink information based on the uplink identifier information, including: determining the type of at least one type of uplink information based on the sequence type of the preamble code.

[0034] In one possible implementation, the uplink information identifier and the downlink information identifier are preamble codes. Before sending the downlink data, it also includes: determining the sequence of the preamble codes corresponding to at least one type of downlink information; identifying the type of at least one type of uplink information based on the uplink identifier information, including: determining the type of at least one type of uplink information based on the sequence of the preamble code.

[0035] In a possible implementation, a sequence of preamble codes indicating each type of uplink information and downlink information is generated by corresponding generation parameters.

[0036] In one possible implementation, the uplink information identifier and the downlink information identifier are preamble codes. Before sending the downlink data, the method further includes: determining a cyclic shift method corresponding to at least one type of downlink information, and cyclically shifting a first sequence according to the corresponding cyclic shift method to generate a preamble code corresponding to at least one type of downlink data; identifying the type of at least one type of uplink information based on the uplink identification information, including: determining the type of at least one type of uplink information based on a second sequence and the sequence of the uplink identification information, wherein the sequence in the uplink identification information is generated by cyclically shifting the second sequence in a corresponding manner.

[0037] In a possible implementation, the uplink information identifier and the downlink information identifier serve as a preamble, and before sending downlink data, the following is further included:

[0038] Determine the encoding method of the preamble code corresponding to at least one type of downlink information, the encoding method of the preamble code is one of the following: Manchester encoding, pulse width PIE encoding, Miller encoding, pulse position PPM encoding; according to the uplink identification information, identify the type of at least one type of uplink information, including: determining the type of at least one type of uplink information according to the encoding method of the preamble code.

[0039] In one possible implementation, the downlink information identifier is a first field in the downlink data that is in the first position and occupies a first number of bits. Before sending the downlink data, it also includes: determining the sequence of the first fields corresponding to at least one type of downlink information; the uplink information identifier is a second field in the uplink data that is in the second position and occupies a second number of bits. According to the uplink identification information, the type of at least one type of uplink information is identified, including: determining the type of at least one type of uplink information according to the sequence of the second field.

[0040] In one possible implementation, the downlink information identifier is a third field in the downlink data that is in the third position and occupies a third number of bits. Before sending the downlink data, it also includes: determining the encoding method of the third field corresponding to at least one type of downlink information, the encoding method is one of the following: Manchester encoding, pulse width PIE encoding, Miller encoding, pulse position PPM encoding; the uplink information identifier is a fourth field in the uplink data that is in the fourth position and occupies a fourth number of bits. According to the uplink identification information, the type of at least one type of uplink information is identified, including: determining the type of at least one type of uplink information according to the encoding method of the fourth field.

[0041] In one possible implementation, the downlink information identifier is the fifth field in the downlink data that is at the fifth position and occupies the fifth number of bits. Before sending the downlink data, it also includes: determining the modulation method of the third field corresponding to at least one type of downlink information; the uplink information identifier is the sixth field in the uplink data that is at the sixth position and occupies the sixth number of bits. According to the uplink identification information, the type of at least one type of uplink information is identified, including: determining the type of at least one type of uplink information according to the modulation method of the sixth field.

[0042] In one possible implementation, the uplink information identifier and the downlink information identifier are cyclic redundancy check CRC codes. Before sending the downlink data, it also includes: determining the number of bits of the CRC code corresponding to at least one type of downlink information; identifying the type of at least one type of uplink information based on the uplink identification information, including: determining the type of at least one type of uplink information based on the number of bits of the CRC code.

[0043] In one possible implementation, the uplink information identifier and the downlink information identifier are cyclic redundancy check CRC codes. Before sending the downlink data, it also includes: determining the wireless network temporary identifier RNTI used when scrambling the CRC codes corresponding to at least one type of downlink information; identifying the type of at least one type of uplink information based on the uplink identification information, including: determining the type of at least one type of uplink information based on the RNTI used when scrambling the CRC code.

[0044] In a fourth aspect, the present application also provides another communication method that can be applied to a network device, the method comprising: sending downlink data, wherein the downlink data carries at least one type of downlink information in at least one downlink resource location, and the downlink resource location corresponds to the type of downlink information.

[0045] In one possible implementation, the method also includes: receiving uplink data, the uplink data carrying at least one type of uplink information in at least one uplink resource location, and the uplink resource location corresponds to the type of the uplink information; when uplink information is received in at least one uplink resource location, determining that the type of the received uplink information is the type of uplink information corresponding to at least one uplink resource location.

[0046] In one possible implementation, the downlink resource position and the uplink resource position are frequency domain resource positions. Before sending downlink data, it also includes: determining the downlink frequency domain resource position corresponding to at least one type of downlink information, the frequency domain resource position is one of the following: the position of the resource element RE, the position of the resource element RE group, and the RE group includes multiple REs; when uplink information is received at at least one uplink resource position, determining the type of the received uplink information is the type of uplink information corresponding to at least one uplink resource position, including: when uplink information is received at at least one uplink frequency domain resource position, determining the type of corresponding uplink information according to the position of the uplink frequency domain resource.

[0047] In one possible implementation, the downlink resource location and the uplink resource location are frequency domain resource locations. Before sending downlink data, it also includes: determining the spread spectrum codes corresponding to at least one type of downlink information; when uplink information is received at at least one uplink resource location, determining that the type of the received uplink information is the type of uplink information corresponding to at least one uplink resource location, including: when uplink information is received at at least one uplink resource location, determining the type of corresponding uplink information according to the spread spectrum code of the uplink frequency domain resource.

[0048] In a possible implementation, the downlink resource location and the uplink resource location are time domain resource locations. Before sending the downlink data, the method further includes: determining downlink time domain resource locations corresponding to at least one type of downlink information, where a time configuration parameter of the time domain resource location is one of the following: a system frame number SFN, a time slot number, an orthogonal frequency division multiplexing (OFDM) symbol number, and an OFDM symbol offset value;

[0049] When uplink information is received at at least one uplink resource location, determining the type of the received uplink information is the type of uplink information corresponding to at least one uplink resource location, including: when uplink information is received at at least one uplink resource location, determining the type of corresponding uplink information according to the uplink time domain resource location.

[0050] In one possible implementation, at least one type of downlink information includes a first type of downlink information and a second type of downlink information, the first type of downlink information includes broadcast information, the first type of downlink information corresponds to a first downlink resource position, the second type of downlink information includes downlink control information and downlink data information, the second type of downlink information corresponds to a second downlink resource position; at least one type of uplink information includes a first type of uplink information and a second type of uplink information, the first type of uplink information includes access information, the first type of uplink information corresponds to a first uplink resource position, the second type of uplink information includes uplink control information and uplink data information, the second type of uplink information corresponds to a second uplink resource position.

[0051] In a fifth aspect, the present application further provides a communication device that can be applied to an IoT device, the communication device comprising: a first receiving unit and a first processing unit. The first receiving unit is configured to receive downlink data. The first processing unit is configured to identify the type of at least one type of downlink information based on downlink identification information.

[0052] In one possible implementation, a communication device includes a first sending unit configured to send uplink data, wherein the uplink data carries uplink identification information and at least one type of uplink information, and the uplink identification information is used to indicate the corresponding type of uplink information.

[0053] In a sixth aspect, the present application further provides a communication device that can be applied to an Internet of Things device, the communication device comprising: a first receiving unit and a first processing unit. The first receiving unit is configured to receive downlink data. The downlink data carries at least one type of downlink information in at least one downlink resource location, and the downlink resource location corresponds to the type of downlink information. The first processing unit is configured to, when receiving downlink information in at least one downlink resource location, determine that the type of the received downlink information is the type of downlink information corresponding to the at least one downlink resource location.

[0054] In a possible implementation, the method further includes: a first sending unit configured to send uplink data, wherein the uplink data carries at least one type of uplink information in at least one uplink resource location, and the uplink resource location corresponds to the type of the uplink information.

[0055] In a seventh aspect, the present application further provides a communication device, which can be applied to a network device, and the communication device includes a second sending unit. The second sending unit is used to receive uplink data, and the uplink data carries at least one type of uplink information in at least one uplink resource location, and the uplink resource location corresponds to the type of uplink information.

[0056] In one possible implementation, the communication apparatus further includes: a second receiving unit configured to receive uplink data, wherein the uplink data carries at least one type of uplink information in at least one uplink resource location, where the uplink resource location corresponds to the type of the uplink information; and a second processing unit configured to, upon receiving the uplink information in the at least one uplink resource location, determine that the type of the received uplink information is the type of uplink information corresponding to the at least one uplink resource location.

[0057] In an eighth aspect, the present application further provides another communication device, which can be applied to a network device, the communication device including a second sending unit. The second sending unit is configured to send downlink data. The downlink data carries at least one type of downlink information in at least one downlink resource location, and the downlink resource location corresponds to the type of downlink information.

[0058] In one possible implementation, the communication device also includes: a second receiving unit, used to receive uplink data, the uplink data carrying at least one type of uplink information in at least one uplink resource location, and the uplink resource location corresponds to the type of uplink information; a second processing unit, used to determine that the type of the received uplink information is the type of uplink information corresponding to at least one uplink resource location when uplink information is received in at least one uplink resource location.

[0059] In a ninth aspect, the present application also provides an Internet of Things device, which includes at least one processor, and the at least one processor is used to execute computer programs or instructions to implement the communication methods provided in the first and second aspects above.

[0060] In a tenth aspect, the present application further provides a network device, comprising a processor and a memory. The processor is coupled to the memory, the memory is configured to store instructions, and the processor is configured to execute a computer program or instruction stored in the memory to implement the communication method described in the third aspect or the communication method described in the fourth aspect.

[0061] In the eleventh aspect, the present application also provides a computer storage medium for storing a computer program, which, when executed, implements the communication method provided in the first aspect, or the second aspect, or the third aspect, or the fourth aspect above. BRIEF DESCRIPTION OF THE DRAWINGS

[0062] FIG1 is a schematic diagram of different types of IoT connection scales provided by an embodiment of the present application;

[0063] FIG2 is a schematic diagram of the architecture of a communication system provided in an embodiment of the present application;

[0064] FIG3 is a schematic diagram of the architecture of another communication system provided in an embodiment of the present application;

[0065] FIG4 is a schematic diagram of the architecture of another communication system provided in an embodiment of the present application;

[0066] FIG5 is a schematic diagram of the architecture of another communication system provided in an embodiment of the present application;

[0067] FIG6 is a flow chart of a communication method provided in an embodiment of the present application;

[0068] FIG7 is a flow chart of another communication method provided in an embodiment of the present application;

[0069] FIG8 is a flow chart of another communication method provided in an embodiment of the present application;

[0070] FIG9 is a flow chart of another communication method provided in an embodiment of the present application;

[0071] FIG10 is a flowchart of another communication method provided in an embodiment of the present application;

[0072] FIG11 is a flowchart of another communication method provided in an embodiment of the present application;

[0073] FIG12 is a flowchart of another communication method provided in an embodiment of the present application;

[0074] FIG13 is a flow chart of another communication method provided in an embodiment of the present application;

[0075] FIG14 is a flowchart of another communication method provided in an embodiment of the present application;

[0076] FIG15 is a flowchart of another communication method provided in an embodiment of the present application;

[0077] FIG16 is a flowchart of another communication method provided in an embodiment of the present application;

[0078] FIG17 is a flowchart of another communication method provided in an embodiment of the present application;

[0079] FIG18 is a flow chart of another communication method provided in an embodiment of the present application;

[0080] FIG19 is a flowchart of another communication method provided in an embodiment of the present application;

[0081] FIG20 is a schematic diagram of resource locations provided in an embodiment of the present application;

[0082] FIG21 is a flowchart of another communication method provided in an embodiment of the present application;

[0083] FIG22 is a flow chart of another communication method provided in an embodiment of the present application;

[0084] FIG23 is a flowchart of another communication method provided in an embodiment of the present application;

[0085] FIG24 is a schematic diagram of a communication device provided in an embodiment of the present application;

[0086] FIG25 is a schematic diagram of another communication device provided in an embodiment of the present application;

[0087] FIG26 is a schematic diagram of a network device provided in an embodiment of the present application;

[0088] Figure 27 is a schematic diagram of an Internet of Things device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0089] In order to enable people skilled in the art to more clearly understand the solution of the present application, the application scenario of the technical solution of the present application is first described below.

[0090] With the development of the Internet of Things (IoT), a consensus has emerged regarding the classification of IoT nodes into three different speed levels: high-speed, medium-speed, and low-speed. High-speed IoT is primarily carried by fifth-generation (5G) mobile communication technologies such as enhanced mobile broadband (eMBB), 4G Category 4+ (Category 4+), and Wi-Fi 6. Medium-speed IoT is currently primarily carried by 4G Category 1, 3G, and 2G. Low-speed IoT is primarily carried by narrowband cellular IoT (NB-IoT), long-range wide area network (LoRaWAN), and Bluetooth Low Energy (BLE). Different speeds correspond to different power consumption levels, forming three distinct scenarios and correspondingly facing three different levels of IoT connection numbers.

[0091] See Figure 1, which is a schematic diagram of the different types of IoT connection scales provided in an embodiment of the present application.

[0092] Low-speed IoT standards like NB-IoT, LoRaWAN, and BLE can support tens of billions of connections. Medium- and high-speed IoT standards can support far fewer connections than low-speed ones. Based on these three IoT scenarios, the Ambient IoT category will be the primary source of hundreds of billions of IoT connections.

[0093] The main application scenarios of Ambient IoT include but are not limited to industrial sensor networks, logistics and warehousing, smart wearable devices, medical health, smart homes and other fields, which are described in detail below.

[0094] Industrial sensor networks: Industrial sensor networks are primarily used in industrial production processes, such as temperature and humidity monitoring, vibration monitoring, and production line monitoring, enabling industrial automation and intelligent management. For example, by deploying zero-power sensing devices beneath the tracks, they can monitor and collect track pressure, temperature, and other information. Furthermore, these devices can be deployed in extreme environments, such as those with high and low temperatures, moving or rotating parts, high vibration, and high humidity, where battery life is limited.

[0095] Logistics and warehousing: With the continued growth of the logistics industry, companies are facing increasing pressure on warehousing and labor costs. Digital management of logistics packages can not only further improve logistics and warehousing management efficiency, but also save high labor costs. Zero-power communication technology affixes communication terminal logos to the surface of packages or goods packaging, allowing for the acquisition of logistics information and management of the entire logistics process, making warehousing operations simpler and more efficient.

[0096] Smart wearable devices: After mobile phones, smart wearables are among the most promising consumer devices for large-scale applications. Currently, various wearable devices have wireless connectivity. Depending on the functional positioning of each product, they can be used in a variety of scenarios, including health monitoring, exercise monitoring, motion sensing, and mobile positioning. Zero-power communication technology aims to ultimately break free from battery constraints, achieving longer battery life, more convenient energy security, and a better user experience.

[0097] Healthcare: Portable medical devices can meet consumers' needs for home health services, but the unique characteristics of medical monitoring devices (especially implantable ones) significantly limit their application scenarios due to issues such as battery life and portable power supplies. Zero-power IoT technology can achieve extremely low power consumption. Furthermore, the lack of batteries reduces size, facilitates flexible folding, and eliminates the need for liquid immersion. This will facilitate real-time monitoring of medical device data and efficient digital management of health conditions.

[0098] Smart home: The application of zero-power communication technology in the smart home field can get rid of complex wiring, enable each terminal to be independently controlled, and achieve long-term online operation without the need for human energy intervention.

[0099] Traditional radio frequency identification (RFID) is a passive IoT technology that uses radio frequency (RF) for contactless, two-way data communication. It uses RF to read and write to recording media (electronic tags or radio frequency cards) to achieve target identification and data exchange. However, due to its lack of interference management, lack of mobility support, and coverage range of only approximately 10 meters, this technology is unlikely to support the trillion-level demand for future applications. Therefore, the Third Generation Partnership Project (3GPP) is currently discussing the development of passive IoT technology based on cellular communications. This approach can reduce costs by leveraging existing large-scale cellular infrastructure, while also leveraging mature cellular communication technologies, such as interference management and mobility management, to improve the coverage of passive IoT.

[0100] The following first introduces the architecture of the communication system in the embodiment of the present application.

[0101] See Figure 2, which is a schematic diagram of the architecture of a communication system provided in an embodiment of the present application.

[0102] The communication system includes a network device 201, a terminal device 202, and an auxiliary node 203. The auxiliary node 203 can be a relay, user equipment (UE), an integrated access and backhaul (IAB) node, a repeater, etc., and has the capability of environmental Internet of Things. During uplink transmission, the terminal device 202 can send uplink data to the network device 201 through the auxiliary node 203. The communication method proposed in the embodiment of the present application can be applied to the communication system described in FIG. 2.

[0103] See Figure 3, which is a schematic diagram of the architecture of another communication system provided in an embodiment of the present application.

[0104] The communication system includes a network device 201 , a terminal device 202 , and an Ambient IoT device 204 .

[0105] The Ambient IoT device 204 may be configured to receive an excitation signal or a backscattered signal.

[0106] Optionally, the Ambient IoT device 204 may not be a power storage device and may not be able to independently generate or amplify signals.

[0107] Optionally, the Ambient IoT device 204 may be a power storage device, but may not be able to independently generate or amplify signals.

[0108] Optionally, the Ambient IoT device 204 may be a power storage device, or may independently generate or amplify signals.

[0109] Optionally, the Ambient IoT device 204 is a power storage device (capacitor) or a super capacitor. The communication method proposed in the embodiment of the present application can be applied to the communication system shown in FIG. 3 .

[0110] See Figure 4, which is a schematic diagram of the architecture of another communication system provided in an embodiment of the present application.

[0111] The communication system includes a network device 201 and an Ambient IoT device 204. The communication method proposed in the embodiment of the present application can be applied to the communication system shown in FIG4.

[0112] See Figure 5, which is a schematic diagram of the architecture of another communication system provided in an embodiment of the present application.

[0113] The communication system includes a terminal device 202 and an Ambient IoT device 204. In the communication system, the terminal device 202 is a device deployed in a wireless access network to provide wireless communication functions for the Ambient IoT device 204. The communication method proposed in the embodiment of the present application can be applied to the communication system shown in FIG5.

[0114] The Ambient IoT device 204 in the above description may also be referred to as a device. A network device may also be referred to as a reader, that is, a network device may function as a reader / writer.

[0115] The communication method provided in the embodiment of the present application can be applied to cellular communication systems related to the third generation partnership project (3GPP), for example, fourth generation (4G) communication systems, such as long term evolution (LTE) communication systems, and can also be applied to fifth generation (5G) communication systems. th The present invention relates to a sixth generation (5G) communication system, such as a 5G new radio (NR) communication system, or various communication systems applied to the future, such as a sixth generation (6G) communication system.

[0116] The method provided in the embodiment of the present application can also be applied to a Bluetooth system, a Wi-Fi system, a LoRa system or an Internet of Vehicles system, a communication system that supports the integration of multiple wireless technologies, and a device-to-device (D2D) system. The method provided in the embodiment of the present application can also be applied to a satellite communication system. The satellite communication system can be integrated with the above-mentioned communication system. The wireless communication systems involved in this application also include but are not limited to: a narrowband Internet of Things system (NB-IoT), a global system for mobile communications (GSM), an enhanced data rate for GSM evolution system (EDGE), a wideband code division multiple access system (WCDMA), a code division multiple access 2000 system (CDMA2000), or a time division-synchronization code division multiple access system (TD-SCDMA).

[0117] The network device 201 may be an access network device of a 3GPP-related cellular system. For example, a 4G mobile communication system or a 5G mobile communication system. The network device may also be an access network device in an open access network (O-RAN or ORAN) or a cloud radio access network (CRAN). Alternatively, the network device may be an access network device in a communication system resulting from the fusion of two or more of the above communication systems.

[0118] The network device 201 includes, but is not limited to, an evolved Node B (eNB), a radio network controller (RNC), a Node B (NB), a base station controller (BSC), a base transceiver station (BTS), a home base station (e.g., home evolved NodeB, or home Node B, HNB), a base band unit (BBU), an access point (AP) in a wireless fidelity (WIFI) system, a macro base station, a micro base station, a wireless relay node, a donor node, a wireless controller in a CR AN scenario, a wireless backhaul node, a transmission point (TP) or a transmission and receiving point (TRP). The network device can also be an access network device in a 5G mobile communication system. For example, a next generation NodeB (gNB) in a new radio (NR) system, a TRP, a TP, or one or a group of antenna panels (including multiple antenna panels) of a base station in a 5G mobile communication system. Alternatively, the network device may also be a network node constituting a gNB or a transmission point. For example, a centralized unit (CU), a distributed unit (DU), a CU-control plane (CP), a CU-user plane (UP), or a radio unit (RU). The CU and DU may be configured separately or included in the same network element. For example, a BBU. The RU may be included in a radio frequency device or radio frequency unit. For example, in a remote radio unit (RRU), an active antenna unit (AAU), or a remote radio head (RRH). Alternatively, the network device may also be a server, a wearable device, a vehicle, or an on-board device. For example, in V2X technology, the network device may be a road side unit (RSU).

[0119] It should be noted that the network device can be the device or apparatus shown above, or it can be a component (for example, a chip), module, or unit in the device or apparatus shown above, and this application does not limit it specifically.

[0120] Terminal device 202, which may also be referred to as user equipment (UE), mobile station (MS), or mobile terminal (MT), is a device that provides voice or data connectivity to a user. Specifically, it includes a device that provides voice to a user, a device that provides data connectivity to a user, or a device that provides both voice and data connectivity to a user. For example, it may include a handheld device with wireless connectivity or a processing device connected to a wireless modem. The terminal device can communicate with the core network via a radio access network (RAN), exchange voice or data with the RAN, or exchange voice and data with the RAN. Currently, terminal devices may include: mobile phones, tablet computers, laptop computers, PDAs, mobile internet devices (MIDs), wearable devices (such as smart watches, smart bracelets, pedometers, etc.), in-vehicle devices (such as cars, bicycles, electric vehicles, airplanes, ships, trains, high-speed trains, etc.), virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, smart home devices (such as refrigerators, televisions, air conditioners, electric meters, etc.), intelligent robots, workshop equipment, wireless terminals in unmanned driving, wireless terminals in remote surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, and flying devices (such as intelligent robots, hot air balloons, drones, airplanes). Terminal devices may also be other devices with terminal functions, for example, a terminal device may also be a device that functions as a terminal in D2D communication.The terminal device may also include vehicle to everything (V2X) terminal equipment, machine-to-machine / machine-type communications (M2M / MTC) terminal equipment, Internet of Things (IoT) terminal equipment, light terminal equipment (light UE), reduced capability UE (REDCAP UE), subscriber unit, subscriber station, mobile station, remote station, access point (AP), remote terminal, access terminal, user terminal, user agent, or user equipment (user device), drone equipment, etc. For example, it may include a mobile phone (or so-called "cellular" phone), a computer with a mobile terminal device, a portable, pocket-sized, handheld, or computer-built-in mobile device, etc. For example, personal communication service (PCS) phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), and other devices. Also included are limited devices, such as devices with low power consumption, or devices with limited storage capacity, or devices with limited computing power. Examples include information sensing devices such as barcodes, radio frequency identification (RFID), sensors, global positioning systems (GPS), and laser scanners. In this application, terminal devices with wireless transceiver capabilities and chips that can be provided in the aforementioned terminal devices are collectively referred to as terminal devices.

[0121] It should be noted that the terminal device can be a device or apparatus with a chip, or a device or apparatus with integrated circuits, or a chip, module or control unit in the device or apparatus shown above, and this application does not limit this specifically.

[0122] In current passive IoT technologies based on cellular communications, readers must transmit different information within the same channel when communicating with IoT devices. Specifically, the 3GPP design for Ambient IoT technology introduces only one physical channel for downlink communication: the physical reader-to-device channel (PRDCH), and one physical channel for uplink communication: the physical device-to-reader channel (PDRCH). However, the communication between readers and devices currently involves different types of information, creating an urgent need for a communication method that can distinguish between these different types of information within the same channel.

[0123] In order to solve the above problems, the embodiments of the present application provide a communication method, device and storage medium. When a connection is established between a network device and an IoT device, the network device can send downlink data to the IoT device. The downlink data carries downlink identification information and at least one type of downlink information. The downlink identification information is used to indicate the corresponding type of downlink information. After receiving the downlink data, the IoT device can identify the type of at least one type of downlink information based on the downlink identification information. This enables multiple types of downlink information to be sent on one physical channel, and the IoT device can also identify the type of downlink information, solving the problem of distinguishing different types of information on the same channel.

[0124] The technical solutions in the embodiments of the present application are described below in conjunction with the accompanying drawings in the embodiments of the present application. Obviously, the embodiments described are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative work are within the scope of protection of this application.

[0125] The Ambient IoT device described below in this application may also be referred to as an IoT device or simply a device. The following first describes an implementation where the IoT device is used only to receive excitations and does not have the ability to backscatter signals. In this implementation, a connection is established between the network device and the IoT device, using the first downlink physical channel, also known as the PRDCH.

[0126] See Figure 6, which is a flowchart of a communication method provided in an embodiment of the present application.

[0127] The communication method provided in the embodiment of the present application includes the following steps:

[0128] S11: The network device sends downlink data.

[0129] The downlink data sent by the network device carries downlink identification information and at least one type of downlink information, and the downlink identification information is used to indicate the corresponding type of downlink information.

[0130] Downlink data may carry multiple types of downlink information, and the embodiments of the present application do not impose any specific restrictions on the specific types and quantities of downlink information. Common downlink information is specifically introduced below.

[0131] Downlink information may include downlink broadcast information, downlink control information, and downlink data information.

[0132] The downlink broadcast information may include the following access information or function information:

[0133] In one possible implementation, the first downlink physical channel carries a portion of basic system information for initial access, including information required for the IoT device to receive a channel carrying the remaining basic system information;

[0134] In another possible implementation, the IoT device performs the minimum information required for uplink transmission;

[0135] In yet another possible implementation, all basic system information for initial access is carried.

[0136] Downlink control information mainly includes the scheduling information required for IoT devices to receive downlink data information and transmit uplink information. It can also transmit the slot format indicator (SFI) and preemption indication (PI).

[0137] Downlink data information may include data information related to the service.

[0138] When the network device sends different types of downlink data, it carries downlink identification information for indicating different types of downlink information in the downlink data.

[0139] Downlink identification information is used to indicate the corresponding category of downlink information. In one possible implementation, the downlink identification information and the downlink information may have a one-to-one correspondence, meaning that one piece of downlink identification information may indicate one category of downlink information. In another possible implementation, the downlink identification information and the downlink information may have a one-to-many correspondence, meaning that one piece of downlink identification information may indicate multiple categories of downlink data, such as downlink control information and downlink data information.

[0140] S12: The IoT device identifies at least one type of downlink information based on the downlink identification information.

[0141] When the IoT device receives downlink data, it identifies the type of at least one type of downlink information based on the downlink identification information carried in the downlink data.

[0142] The following example illustrates a network device sending downlink data to an IoT device. The downlink data includes downlink broadcast information, downlink control information, and downlink data information. Specifically, the downlink identification information of the downlink broadcast information is the first type of downlink information, while the downlink control information and downlink data information are the second type of downlink information. The first type of downlink information corresponds to the first downlink identification information, and the second type of downlink information corresponds to the second downlink identification information. After receiving the downlink data, the IoT device parses the data to determine the specific type of downlink information. When the downlink identification information is determined to be the first downlink identification information, the current downlink information is identified as downlink broadcast information. When the downlink identification information is determined to be the second downlink identification information, the current downlink information is identified as downlink control information and downlink data information.

[0143] In summary, using the method provided in the embodiment of the present application, when a connection is established between a network device and an IoT device, the network device can send downlink data to the IoT device. The downlink data carries downlink identification information and at least one type of downlink information, and the downlink identification information is used to indicate the corresponding type of downlink information. After receiving the downlink data, the IoT device can identify the type of at least one type of downlink information based on the downlink identification information. Therefore, even if multiple types of downlink information are sent on a physical channel, the IoT device can also identify the type of downlink information, solving the problem of distinguishing different types of information on the same channel.

[0144] In the above embodiments, the IoT device is used only to receive excitation and does not have the ability to backscatter signals. The following describes the implementation method when the IoT device has the ability to backscatter signals.

[0145] See Figure 7, which is a flowchart of another communication method provided in an embodiment of the present application.

[0146] At this time, the network device transmits downlink data to the IoT device, and the IoT device transmits uplink data to the network device. The first uplink physical channel is also the PDRCH.

[0147] The method comprises the following steps:

[0148] S21: The network device sends downlink data.

[0149] S22: The IoT device identifies at least one type of downlink information based on the downlink identification information.

[0150] For the description of S21, please refer to the above S11, and for the description of S22, please refer to the above S12, which will not be repeated here.

[0151] S23: The IoT device sends uplink data.

[0152] The uplink data carries uplink identification information and at least one type of uplink information.

[0153] The uplink data may carry multiple types of uplink information, and the uplink information may include uplink control information, uplink access information, and uplink data information.

[0154] The uplink access information may be used in a random access process, for example, to carry a random access preamble.

[0155] Uplink control information can carry uplink control information (UCI), feedback hybrid automatic repeat request-ACKnowledgement (HARQ-ACK), indicate whether the downlink transport block is received correctly; report channel status information; request uplink resources when uplink data arrives, etc.

[0156] The uplink data information may include data information related to the service.

[0157] The uplink identification information is used to indicate uplink information of a corresponding category. In one possible implementation, the uplink identification information and the uplink information may have a one-to-one correspondence, that is, one piece of uplink identification information may indicate one category of uplink information. In another possible implementation, the uplink identification information and the uplink information may have a one-to-many correspondence, that is, one piece of uplink identification information may indicate multiple categories of uplink data, for example, uplink control information and uplink data information.

[0158] S24: The network device identifies the type of at least one type of uplink information according to the uplink identification information.

[0159] After receiving uplink data, the network device in the embodiment of the present application identifies the type of at least one type of uplink information based on the uplink identification information carried in the uplink data.

[0160] The following example illustrates that a network device receives uplink data sent by an IoT device. The uplink data includes uplink access information, uplink control information, and uplink data information. The uplink identification information of the uplink access information is the first type of uplink information, and the uplink control information and uplink data information are the second type of uplink information. The first type of uplink information corresponds to the first uplink identification information, and the second type of uplink information corresponds to the second uplink identification information. After the network device receives the downlink data, it parses the data to determine the specific category of the uplink information. When the uplink identification information is determined to be the first uplink identification information, the current uplink information is identified as uplink connection information; when the uplink identification information is determined to be the second uplink identification information, the current uplink information is identified as uplink control information and uplink data information.

[0161] In summary, by utilizing the method provided in the embodiment of the present application, when a connection is established between a network device and an IoT device, it is possible to identify various types of downlink information. Furthermore, when a connection is established between a network device and an IoT device, the network device receives uplink data sent by the IoT device. The uplink data carries uplink identification information and at least one type of uplink information, and the uplink identification information is used to indicate the corresponding type of uplink information. After receiving the uplink data, the network device can identify the type of at least one type of uplink information based on the uplink identification information. Therefore, even if multiple types of uplink information are sent on one uplink physical channel, the network device can also identify the type of uplink information, thereby solving the problem of distinguishing different types of information on the same channel.

[0162] The following description uses the example of an IoT device with backscattering capability. The implementation is similar when the IoT device is only used to receive stimulus, omitting the steps involved in transmitting uplink data from the IoT device to the network device.

[0163] The following first describes the implementation method when the uplink information identifier and the downlink information identifier are preambles.

[0164] When the uplink information identifier and the downlink information identifier are preamble codes, in a possible implementation, the length of the preamble code may be used to distinguish different information types.

[0165] See Figure 8, which is a flowchart of another communication method provided in an embodiment of the present application.

[0166] S31: The network device determines the length of the preamble code corresponding to at least one type of downlink information.

[0167] The downlink identification information is a preamble, and the length of the preamble can distinguish the type of downlink information.

[0168] For example, the preamble length of downlink broadcast information is N1 bits, the preamble length of downlink control information is N2 bits, and the preamble length of downlink data information is N3 bits.

[0169] For another example, the preamble length of downlink broadcast information is M1 bits, and the preamble length of downlink control information and downlink data information is M2 bits. In this implementation, in the M2-bit preamble, the first X1 bits of the M2 bits can be used to indicate the downlink control information, and the last X2 bits of the M2 bits can be used to indicate the downlink data information; or in the M2-bit preamble, the first X1 bits of the M2 bits can be used to indicate the downlink data information, and the last X2 bits of the M2 bits can be used to indicate the downlink control information; or other methods can be used to indicate the downlink control information and downlink data information.

[0170] S32: The network device sends downlink data.

[0171] S33: The IoT device determines the type of at least one type of downlink information based on the length of the preamble code.

[0172] After receiving downlink data, the IoT device parses the preamble length information and determines the type of downlink information based on the preamble length. For example, if the parsed preamble length is N1 bits, the current downlink information can be determined to be downlink broadcast information.

[0173] S34: The IoT device determines the length of the preamble code corresponding to at least one type of uplink information.

[0174] The uplink identification information is a preamble, and the length of the preamble can distinguish the type of uplink information.

[0175] For example, the preamble length of uplink access information is n1 bits, the preamble length of uplink control information is n2 bits, and the preamble length of uplink data information is n3 bits.

[0176] For another example, the preamble length of uplink access information is m1 bits, and the preamble length of uplink control information and uplink data information is m2 bits. In this implementation, in the m2-bit preamble, the first x1 bits of the m2 bits can be used to indicate the uplink control information, and the last x2 bits of the m2 bits can be used to indicate the uplink data information; or in the m2-bit preamble, the first x1 bits of the m2 bits can be used to indicate the uplink data information, and the last x2 bits of the m2 bits can be used to indicate the uplink control information; or other methods can be used to indicate the uplink control information and uplink data information.

[0177] S35: The IoT device sends uplink data.

[0178] S36: The network device determines the type of at least one type of uplink information according to the length of the preamble.

[0179] After receiving the uplink data, the network device analyzes the length of the preamble and determines the type of the corresponding uplink information based on the length of the preamble. For example, if the parsed preamble length is n1 bits, the current uplink information can be determined to be uplink access information.

[0180] In some embodiments, M1 and m1 in the above description may correspond to the same, M2 and m2 may correspond to the same, N1 and n1 may correspond to the same, N2 and n2 may correspond to the same, and N3 and n3 may correspond to the same.

[0181] To sum up, through the solution provided in the embodiments of the present application, when multiple categories of uplink information are sent on an uplink physical channel, or multiple categories of downlink information are sent on a downlink physical channel, the length of the preamble code can be used to distinguish different categories of information, thereby solving the problem of distinguishing different types of information on the same channel.

[0182] When the uplink information identifier and the downlink information identifier are preamble codes, in another possible implementation, different information types may be distinguished by using the sequence type of the preamble code.

[0183] See Figure 9, which is a flowchart of another communication method provided in an embodiment of the present application.

[0184] S41: The network device determines a sequence type of a preamble code corresponding to at least one type of downlink information.

[0185] The downlink identification information is the preamble, and the sequence type of the preamble can distinguish the type of downlink information. The sequence type of the preamble includes but is not limited to the following types:

[0186] Pseudo-Noise (PN) sequence, longest linear feedback shift register sequence (M sequence for short), Gold sequence, Zadoff-Chu sequence, etc.

[0187] For example, the sequence type of the preamble code of the downlink broadcast information is an M sequence, and the sequence type of the preamble code of the downlink control information and the downlink data information is a PN sequence.

[0188] For another example, the sequence type of the preamble of downlink broadcast information is an M sequence, the sequence type of the preamble of downlink control information is a Gold sequence, and the sequence type of the preamble of downlink data information is a PN sequence.

[0189] S42: The network device sends downlink data.

[0190] S43: The IoT device determines the type of at least one type of downlink information according to the sequence type of the preamble code.

[0191] After receiving downlink data, the IoT device parses the preamble and determines the type of downlink information based on the preamble sequence type. For example, if the preamble sequence type is M sequence, the current downlink information can be determined to be downlink broadcast information.

[0192] S44: The IoT device determines a sequence type of a preamble code corresponding to at least one type of uplink information.

[0193] The uplink identification information is also a preamble, and the sequence type of the preamble can distinguish the type of uplink information.

[0194] For example, the sequence type of the preamble code of the uplink access information is an M sequence, and the sequence type of the preamble code of the uplink control information and the uplink data information is a PN sequence.

[0195] For another example, the sequence type of the preamble of uplink broadcast information is an M sequence, the sequence type of the preamble of uplink control information is a Gold sequence, and the sequence type of the preamble of uplink data information is a PN sequence.

[0196] S45: The IoT device sends uplink data.

[0197] S46: The network device determines the type of at least one type of uplink information according to the sequence type of the preamble.

[0198] After receiving the uplink data, the network device parses the preamble to obtain the preamble, and determines the type of the corresponding uplink information based on the sequence type of the preamble. For example, if the sequence type of the preamble is M sequence, the current uplink information can be determined to be uplink access information.

[0199] To summarize, through the solution provided in the embodiments of the present application, when multiple categories of uplink information are sent on an uplink physical channel, or multiple categories of downlink information are sent on a downlink physical channel, the sequence type of the preamble code can be used to distinguish different categories of information, thereby solving the problem of distinguishing different types of information on the same channel.

[0200] When the uplink information identifier and the downlink information identifier are preamble codes, in another possible implementation, a sequence of preamble codes may be used to distinguish different information types.

[0201] See Figure 10, which is a flowchart of another communication method provided in an embodiment of the present application.

[0202] S51: The network device determines a sequence of a preamble code corresponding to at least one type of downlink information.

[0203] In the embodiment of the present application, the downlink identification information is a preamble code, and the sequence of the preamble code can distinguish the type of downlink information.

[0204] For example, the sequence of the preamble code of the downlink broadcast information is 111111, and the sequence of the preamble code of the downlink control information and the downlink data information is 111000.

[0205] Furthermore, the preamble sequence may be generated based on generation parameters. For example, the generation parameter of the preamble sequence of downlink broadcast information is ID1, and the generation parameter of the preamble sequence of downlink control information and downlink data information is ID2.

[0206] For another example, the sequence of the preamble code of the downlink broadcast information is 111111, the sequence of the preamble code of the downlink control information is 101010, and the sequence of the preamble code of the downlink data information is 111000.

[0207] Furthermore, at this time, the generation parameter of the preamble sequence of the downlink broadcast information is ID1, the generation parameter of the preamble sequence of the downlink control information is ID2, and the generation parameter of the preamble sequence of the downlink data information is ID3.

[0208] The above specific sequences are for illustration only and do not constitute a limitation on the technical solution of the present application. The embodiments of the present application do not limit the number of bits in the preamble sequence.

[0209] S52: The network device sends downlink data.

[0210] S53: The IoT device determines the type of at least one type of downlink information according to the sequence of the preamble code.

[0211] After receiving downlink data, the IoT device parses the preamble and determines the type of downlink information based on the preamble sequence. For example, if the parsed preamble sequence is 111111, the current downlink information can be determined to be a downlink broadcast message.

[0212] S54: The IoT device determines a sequence of a preamble code corresponding to at least one type of uplink information.

[0213] The uplink identification information is a preamble, and the sequence of the preamble can distinguish the type of uplink information.

[0214] For example, the sequence of the preamble of the uplink access information is 000000, and the sequence of the preamble of the uplink control information and the uplink data information is 111000. Furthermore, the sequence of the preamble can be generated based on a generation parameter. For example, the generation parameter of the preamble sequence of the uplink access information is ID4; the generation parameter of the preamble sequence of the uplink control information and the uplink data information is ID5, and in some embodiments, it can also be ID2.

[0215] For another example, the sequence of the preamble of the uplink access information is 000000, the sequence of the preamble of the uplink control information is 101010, and the sequence of the preamble of the uplink data information is 111000. Furthermore, in this case, the generation parameter of the preamble sequence of the uplink broadcast information is ID4; the generation parameter of the preamble sequence of the uplink control information is ID5, and in some embodiments, it may also be ID2; the generation parameter of the preamble sequence of the uplink data information is ID6, and in some embodiments, it may also be ID3.

[0216] The above specific sequences are for illustration only and do not constitute a limitation on the technical solution of the present application. The embodiments of the present application do not limit the number of bits in the preamble sequence.

[0217] S55: The IoT device sends uplink data.

[0218] S56: The network device determines the type of at least one type of uplink information according to the sequence of the preamble code.

[0219] After receiving the uplink data, the network device parses the preamble to obtain the preamble, and determines the type of the corresponding uplink information based on the preamble sequence. For example, if the parsed preamble sequence is 000000, it can be determined that the current uplink information is uplink access information.

[0220] To summarize, through the solution provided in the embodiments of the present application, when multiple categories of uplink information are sent on an uplink physical channel, or multiple categories of downlink information are sent on a downlink physical channel, the sequence of the preamble code can be used to distinguish different categories of information, thereby solving the problem of distinguishing different types of information on the same channel.

[0221] When the uplink information identifier and the downlink information identifier are preamble codes, in another possible implementation, different information types may be distinguished by using a cyclic shift of the preamble code.

[0222] See Figure 11, which is a flowchart of another communication method provided in an embodiment of the present application.

[0223] S61: The network device determines a cyclic shift mode of a preamble code corresponding to at least one type of downlink information.

[0224] In this embodiment of the present application, the downlink identification information is a preamble, and different cyclic shifts of the same preamble sequence are used to distinguish the type of downlink information. The downlink identification information is cyclically shifted based on the first sequence. Cyclic shifting is the process of cyclically shifting the binary sequence of the preamble, either by shifting the lower bits to the upper bits of the sequence or by shifting the higher bits to the lower bits of the sequence.

[0225] For example, the first sequence is 111000, the sequence of the preamble code of the downlink broadcast information is 110001 (one highest bit of the first sequence is right shifted), and the sequence of the preamble code of the downlink control information and downlink data information is 100011 (two highest bits of the first sequence are right shifted).

[0226] For another example, the first sequence is 111000, the preamble sequence of the downlink broadcast information is 110001, the preamble sequence of the downlink control information is 100011, and the preamble sequence of the downlink data information is 000111 (the three high bits of the first sequence are right shifted).

[0227] S62: The network device sends downlink data.

[0228] S63: The IoT device determines a type of at least one type of downlink information according to the first sequence and the sequence of the downlink identification information.

[0229] After receiving downlink data, the IoT device parses the preamble and compares it with the locally stored first sequence to determine the cyclic shift method and, therefore, the type of the corresponding downlink information. For example, if the parsed preamble sequence is 110001, the first sequence can be used to determine that the current downlink information is downlink broadcast information. The first sequence is stored because, in one possible implementation, the first sequence can be modified or generated by parameter generation. In another possible implementation, if the first sequence is not modified, the IoT device can also directly determine the type of downlink information based on the sequence of the downlink identification information.

[0230] S64: The IoT device determines a cyclic shift mode of a preamble code corresponding to at least one type of uplink information.

[0231] The uplink identification information is a preamble, and different cyclic shift modes of the same preamble sequence are used to distinguish the type of uplink information. The uplink identification information is cyclically shifted based on the second sequence.

[0232] For example, the second sequence is 001100, the sequence of the preamble code of the uplink access information is 011000 (one highest bit of the second sequence is right shifted), and the sequence of the preamble code of the uplink control information and uplink data information is 110000 (two highest bits of the second sequence are right shifted).

[0233] For another example, the second sequence is 001100, the preamble sequence of uplink access information is 011000, the preamble sequence of downlink control information is 110000, and the preamble sequence of downlink data information is 100001 (the three high bits of the second sequence are right shifted).

[0234] S65: The IoT device sends uplink data.

[0235] S66: The network device determines the type of at least one type of uplink information according to the second sequence and the sequence of the uplink identification information.

[0236] After receiving uplink data, the network device parses and obtains the preamble, compares the sequence of the preamble with the locally stored second sequence, determines the cyclic shift method, and then determines the type of corresponding uplink information. For example, when the sequence of the preamble obtained by parsing is 011000, based on the first sequence, it can be determined that the current uplink information is uplink access information. The second sequence is stored because, in one possible implementation, the second sequence can be modified or generated by generating parameters. In another possible implementation, when the second sequence is not modified, the network device can also directly determine the type of uplink information based on the sequence of the uplink identification information.

[0237] The first sequence and the second sequence in the embodiment of the present application are only examples and do not constitute a limitation on the technical aspects of the present application. In actual applications, the first sequence and the second sequence can adopt other sequence lengths and other sequences.

[0238] To summarize, through the solution provided in the embodiments of the present application, when multiple categories of uplink information are sent on an uplink physical channel, or multiple categories of downlink information are sent on a downlink physical channel, different sequences generated after cyclic shifting of a specified sequence can be used as preamble codes to distinguish different categories of information, thereby solving the problem of distinguishing different types of information on the same channel.

[0239] When the uplink information identifier and the downlink information identifier are preamble codes, in another possible implementation, different information types may be distinguished by using a coding method of the preamble code.

[0240] See Figure 12, which is a flowchart of another communication method provided in an embodiment of the present application.

[0241] S71: The network device determines a coding method of a preamble code corresponding to at least one type of downlink information.

[0242] In the embodiment of the present application, the downlink identification information is a preamble, and the encoding method of the preamble can distinguish the type of downlink information. The encoding method of the preamble can include but is not limited to the following methods:

[0243] Manchester encoding, Pulse interval encoding (PIE) encoding, Miller encoding, and Pulse Position Modulation (PPM) encoding.

[0244] For example, the encoding method of the preamble code of the downlink broadcast information is Manchester encoding, and the encoding method of the preamble codes of the downlink control information and the downlink data information is PIE encoding.

[0245] The above encoding methods are all examples and do not constitute a limitation on the technical solutions of this application.

[0246] S72: The network device sends downlink data.

[0247] S73: The IoT device determines the type of at least one type of downlink information according to the encoding method of the preamble code.

[0248] After receiving downlink data, the IoT device parses the preamble and determines the type of downlink information based on the preamble's encoding method. For example, if the preamble's encoding method is Manchester encoding, the current downlink information can be determined to be downlink broadcast information.

[0249] S74: The IoT device determines a coding method for a preamble code corresponding to at least one type of uplink information.

[0250] In the embodiment of the present application, the uplink identification information is a preamble code, and the encoding method of the preamble code can distinguish the type of uplink information.

[0251] For example, the encoding method of the preamble code of the uplink access information is Manchester encoding, and the encoding method of the preamble codes of the uplink control information and the uplink data information is PIE encoding.

[0252] S75: The IoT device sends uplink data.

[0253] S76: The network device determines the type of at least one type of uplink information according to the encoding method of the preamble.

[0254] After receiving the uplink data, the network device parses the preamble and determines the type of uplink information based on the encoding method of the preamble. For example, if the encoding method of the preamble is Manchester encoding, the current uplink information can be determined to be uplink access information.

[0255] To sum up, through the solution provided in the embodiments of the present application, when multiple categories of uplink information are sent on an uplink physical channel, or multiple categories of downlink information are sent on a downlink physical channel, the encoding method of the preamble code can be used to distinguish different categories of information, thereby solving the problem of distinguishing different types of information on the same channel.

[0256] The above embodiment describes the implementation when the uplink information identifier and the downlink information identifier are preamble codes. The following describes the implementation when the uplink information identifier and the downlink information identifier are fixed bit data in the physical channel.

[0257] See Figure 13, which is a flowchart of another communication method provided in an embodiment of the present application.

[0258] S81: The network device determines a sequence of first fields corresponding to at least one type of downlink information.

[0259] In the embodiment of the present application, the downlink identification information is a first field located at a first position and occupying a first number of bits in the downlink data, that is, the downlink identification information is a field at a fixed position in the downlink data.

[0260] The first position may be the head position, tail position or other position of the data, and is not specifically limited in the embodiment of the present application.

[0261] The embodiment of the present application does not specifically limit the size of the first bit number, for example, it can be 2 bits, 3 bits, etc., as illustrated below.

[0262] For example, the first field is two bits at the head position, the corresponding first field of the downlink broadcast information is 00, and the first field of the downlink control information and the downlink data information is 01.

[0263] For another example, the first field is two bits at the head position, the first field corresponding to the downlink broadcast information is 00, the first field corresponding to the downlink control information is 01, and the first field corresponding to the downlink data information is 11.

[0264] The above specific first field is only for illustration and does not constitute a limitation on the technical solution of this application.

[0265] S82: The network device sends downlink data.

[0266] S83: The IoT device determines the type of at least one type of downlink information based on the sequence of the first field.

[0267] After receiving downlink data, the IoT device parses the data at the first position and the first number of bits, that is, parses the data in the first field, and determines the type of the corresponding downlink information based on the sequence of the first field. For example, when the sequence of the first field obtained by parsing is 00, it can be determined that the current downlink information is downlink broadcast information. Furthermore, when the position of the first field is at the head position, the IoT device can also determine whether to receive and demodulate subsequent information based on the detection result of the first field. In other words, if the information type cannot be identified after parsing the data in the first field, it can stop receiving and demodulating subsequent data.

[0268] S84: The IoT device determines a sequence of second fields corresponding to at least one type of uplink information.

[0269] The uplink identification information is a second field located at a second position and occupying a second number of bits in the uplink data, that is, the uplink identification information is a field at a fixed position in the uplink data.

[0270] The second position may be the head position, tail position or other position of the data, and is not specifically limited in the embodiment of the present application.

[0271] The embodiment of the present application does not specifically limit the size of the second bit number, for example, it can be 2 bits, 3 bits, etc., as illustrated below.

[0272] For example, the second field is two bits at the head position, the corresponding second field of the uplink access information is 11, and the second fields of the uplink control information and the uplink data information are 01.

[0273] For another example, the second field is two bits at the head position, the first field corresponding to the uplink access information is 11, the second field corresponding to the uplink control information is 01, and the second field corresponding to the uplink data information is 11.

[0274] The above specific second field is only for illustration and does not constitute a limitation on the technical solution of this application.

[0275] S85: The IoT device sends uplink data.

[0276] S86: The network device determines the type of at least one type of uplink information according to the sequence of the second field.

[0277] After receiving the uplink data, the network device parses the data at the second position and the second number of bits, that is, parses the data in the second field, and determines the type of the corresponding uplink information based on the sequence of the second field. For example, when the sequence of the second field obtained by parsing is 11, it can be determined that the current uplink information is uplink access information. Furthermore, when the position of the second field is at the head position, the network device can also determine whether to receive and demodulate subsequent information based on the detection result of the second field. In other words, if the information type cannot be identified after parsing the data in the second field, it is not necessary to continue receiving and demodulating subsequent data.

[0278] To summarize, through the solution provided in the embodiments of the present application, when sending multiple categories of uplink information on an uplink physical channel, or sending multiple categories of downlink information on a downlink physical channel, fields with specific positions and specific numbers of bits can be used to distinguish different categories of information, thereby solving the problem of distinguishing different types of information on the same channel.

[0279] In another possible implementation, different types of information may be distinguished by using an encoding method of a field at a specific position and with a specific number of bits, which is described in detail below.

[0280] See Figure 14, which is a flowchart of another communication method provided in an embodiment of the present application.

[0281] S91: The network device determines a coding method for a third field corresponding to at least one type of downlink information.

[0282] In the embodiment of the present application, the downlink identification information is a third field located at a third position and occupying a third number of bits in the downlink data, that is, the downlink identification information is a field at a fixed position in the downlink data.

[0283] The third position may be the head position, tail position or other position of the data, and is not specifically limited in the embodiment of the present application.

[0284] The embodiment of the present application does not specifically limit the size of the third bit number, for example, it is 2 bits, 3 bits, etc.

[0285] The encoding method of the third field may include but is not limited to the following methods:

[0286] Manchester encoding, PIE encoding, Miller encoding, PPM encoding.

[0287] For example, the third field is two bits in the header position. The encoding method of the third field of the downlink broadcast information is Manchester encoding, and the encoding method of the third field corresponding to the downlink control information and downlink data information is PIE encoding. Furthermore, the downlink control information and downlink data information can be distinguished by different sequences of the third field.

[0288] S92: The network device sends downlink data.

[0289] S93: The IoT device determines the type of at least one type of downlink information according to the encoding method of the third field.

[0290] After receiving the downlink data, the IoT device parses and obtains the encoding method of the data at the third position and the third number of bits, that is, parses the encoding method of the third field, and determines the type of the corresponding downlink information based on the encoding method. For example, when the encoding method of the first third field is Manchester encoding, it can be determined that the current downlink information is downlink broadcast information. Furthermore, when the position of the third field is at the head position, the IoT device can also determine whether it needs to receive and demodulate the subsequent information based on the encoding method detection result of the third field, that is, when it is determined that the information type cannot be identified based on the encoding method detection result of the third field, it can stop receiving and demodulating subsequent data.

[0291] S94: The IoT device determines a coding method for each fourth field corresponding to at least one type of uplink information.

[0292] The uplink identification information is a fourth field located at the fourth position and occupying the fourth number of bits in the uplink data, that is, the uplink identification information is a field at a fixed position in the uplink data.

[0293] The fourth position may be the head position, tail position or other position of the data, and is not specifically limited in the embodiment of the present application.

[0294] The embodiment of the present application does not specifically limit the size of the fourth bit number, for example, it can be 2 bits, 3 bits, etc.

[0295] The encoding method of the fourth field may include but is not limited to the following methods:

[0296] Manchester encoding, PIE encoding, Miller encoding, PPM encoding.

[0297] For example, the fourth field is two bits at the head position, the encoding method of the fourth field of the uplink access information is Manchester encoding, and the encoding method of the fourth field corresponding to the uplink control information and uplink data information is PIE encoding. Furthermore, the uplink control information and uplink data information can be distinguished by different sequences of the fourth field.

[0298] S95: The IoT device sends uplink data.

[0299] S96: The network device determines the type of at least one type of uplink information according to the encoding method of the fourth field.

[0300] After receiving the uplink data, the network device parses and obtains the encoding method of the data at the fourth position and the fourth number of bits, that is, parses the encoding method of the fourth field, and determines the type of the corresponding uplink information according to the encoding method. For example, when the encoding method of the fourth field obtained by parsing is Manchester encoding, it can be determined that the current uplink information is uplink access information. Furthermore, when the position of the fourth field is at the head position, the network device can also determine whether it needs to receive and demodulate the subsequent information based on the encoding method detection result of the fourth field, that is, when it is determined that the information type cannot be identified based on the encoding method detection result of the fourth field, it is possible to stop receiving and demodulating subsequent data.

[0301] To summarize, through the solution provided in the embodiments of the present application, when sending multiple categories of uplink information on an uplink physical channel, or sending multiple categories of downlink information on a downlink physical channel, the encoding method of fields with specific positions and specific numbers of bits can be used to distinguish different categories of information, thereby solving the problem of distinguishing different types of information on the same channel.

[0302] In another possible implementation, different types of information may be distinguished based on the modulation method of a field at a specific position and a specific number of bits, which is described in detail below.

[0303] See Figure 15, which is a flowchart of another communication method provided in an embodiment of the present application.

[0304] S101: A network device determines a modulation mode of a fifth field corresponding to at least one type of downlink information.

[0305] In the embodiment of the present application, the downlink identification information is the fifth field located at the fifth position and occupying the fifth number of bits in the downlink data, that is, the downlink identification information is a field at a fixed position in the downlink data.

[0306] The fifth position may be the head position, tail position or other position of the data, and is not specifically limited in the embodiment of the present application.

[0307] The embodiment of the present application does not specifically limit the size of the fifth bit number, for example, it can be 2 bits, 3 bits, etc.

[0308] The modulation mode of the fifth field may be on-off keying (OOK), which may include but is not limited to the following modes: OOK-1 and OOK-4.

[0309] OOK-1 and OOK-4 are two on-off keying modulation methods.

[0310] For example, the fifth field is two bits at the head position, the modulation mode of the fifth field of the downlink broadcast information is OOK-1, and the modulation mode of the fifth field corresponding to the downlink control information and downlink data information is OOK-4.

[0311] S102: The network device sends downlink data.

[0312] S103: The IoT device determines the type of at least one type of downlink information according to the modulation mode of the fifth field.

[0313] After receiving the downlink data, the IoT device parses and obtains the modulation mode of the data at the fifth position and the fifth bit number, that is, parses the encoding mode of the fifth field, and determines the type of the corresponding downlink information based on the encoding mode. For example, when the encoding mode of the first fifth field is OOK-1, it can be determined that the current downlink information is downlink broadcast information. Furthermore, when the position of the fifth field is at the head position, the IoT device can also determine whether it needs to receive and demodulate the subsequent information based on the modulation mode detection result of the fifth field, that is, when it is determined that the information type cannot be identified based on the modulation mode detection result of the fifth field, it can stop receiving and demodulating subsequent data.

[0314] S104: The IoT device determines a modulation mode of the sixth field corresponding to at least one type of uplink information.

[0315] The uplink identification information is the sixth field located at the sixth position and occupying the sixth number of bits in the uplink data, that is, the uplink identification information is a field at a fixed position in the uplink data.

[0316] The sixth position may be the head position, tail position or other position of the data, and is not specifically limited in the embodiment of the present application.

[0317] The embodiment of the present application does not specifically limit the size of the sixth bit number, for example, it can be 2 bits, 3 bits, etc.

[0318] The modulation mode of the sixth field may be OOK, including but not limited to the following modes: OOK-1 and OOK-4.

[0319] For example, the sixth field is two bits at the head position, the modulation mode of the sixth field of the uplink access information is OOK-1, and the modulation mode of the sixth field corresponding to the uplink control information and uplink data information is OOK-4.

[0320] S105: The IoT device sends uplink data.

[0321] S106: The network device determines the type of at least one type of uplink information according to the modulation mode of the sixth field.

[0322] After receiving the uplink data, the network device parses and obtains the modulation mode of the data at the sixth position and the sixth bit number, that is, parses the modulation mode of the sixth field, and determines the type of the corresponding uplink information based on the modulation mode. For example, when the modulation mode of the first sixth field is OOK-1, it can be determined that the current uplink information is uplink access information. Furthermore, when the position of the sixth field is at the head position, the network device can also determine whether it needs to receive and demodulate the subsequent information based on the modulation mode detection result of the sixth field, that is, when it is determined that the information type cannot be identified based on the modulation mode detection result of the sixth field, it can stop receiving and demodulating subsequent data.

[0323] In another possible implementation, for the fifth field and the sixth field, different types of information can be distinguished based on the overlaid sequence of the field at a specific position and a specific number of bits, for example, based on the type of sequence of the field and different sequences, or by using the overlaid sequence to distinguish the type of information carried. It is understandable that the method of distinguishing different types of information by overlaid sequence can also be extended to the scenario where the uplink identification information and the downlink identification information are the preamble code, that is, different types of information are distinguished based on the overlaid sequence of the preamble code field, which will not be repeated here.

[0324] To summarize, through the solution provided in the embodiments of the present application, when sending multiple categories of uplink information on an uplink physical channel, or sending multiple categories of downlink information on a downlink physical channel, the modulation method of the field with a specific position and a specific number of bits can be used to distinguish different categories of information, thereby solving the problem of distinguishing different types of information on the same channel.

[0325] The above embodiments describe implementations when the uplink information identifier and the downlink information identifier are specific fields. The following describes implementations when the uplink information identifier and the downlink information identifier are cyclic redundancy check (CRC) codes.

[0326] See Figure 16, which is a flowchart of another communication method provided in an embodiment of the present application.

[0327] The method comprises the following steps:

[0328] S111: The network device determines the number of bits of the CRC code corresponding to at least one type of downlink information.

[0329] In the embodiment of the present application, the downlink identification information is a CRC code of the downlink data. The length of the CRC code, that is, the number of bits of the CRC code, can be used to represent different types of downlink information.

[0330] For example, the number of bits of the CRC code corresponding to the downlink broadcast information is a first number of bits, and the number of bits of the CRC codes of the downlink control information and the downlink data information is a second number of bits.

[0331] For another example, the number of bits of the CRC code corresponding to the downlink broadcast information is the first number of bits, the number of bits of the CRC code corresponding to the downlink control information is the second number of bits, and the number of bits of the CRC code corresponding to the downlink data information is the third number of bits.

[0332] The embodiment of the present application does not specifically limit the number of bits of the CRC code of each type of information.

[0333] S112: The network device sends downlink data.

[0334] S113: The IoT device determines the type of at least one type of downlink information based on the number of bits of the CRC code.

[0335] After receiving the downlink data, the IoT device parses the downlink data, determines the number of bits in the CRC code, and determines the type of the corresponding downlink information based on the number of bits in the CRC code. For example, if the number of bits in the CRC code is the first number, the current downlink information can be determined to be downlink broadcast information.

[0336] S114: The IoT device determines the number of bits of the CRC code corresponding to at least one type of uplink information.

[0337] In the embodiment of the present application, the uplink identification information is a CRC code of the uplink data. The length of the CRC code, that is, the number of bits of the CRC code, can be used to represent different types of uplink information.

[0338] For example, the number of bits of the CRC code corresponding to the uplink access information is a first number of bits, and the number of bits of the CRC codes corresponding to the uplink control information and the uplink data information is a second number of bits.

[0339] For another example, the number of bits of the CRC code corresponding to the uplink access information is a first number of bits, the number of bits of the CRC code corresponding to the uplink control information is a second number of bits, and the number of bits of the CRC code corresponding to the uplink data information is a third number of bits.

[0340] The embodiment of the present application does not specifically limit the number of bits of the CRC code of each type of uplink information.

[0341] S115: The IoT device sends uplink data.

[0342] S116: The network device determines the type of at least one type of uplink information according to the number of bits of the CRC code.

[0343] After receiving the uplink data, the network device parses the uplink data, determines the number of bits in the CRC code, and determines the type of the corresponding uplink information based on the number of bits in the CRC code. For example, when the number of bits in the CRC code obtained by parsing is the first number of bits, it can be determined that the current uplink information is uplink access information.

[0344] When using this implementation, the network device and the IoT device need to know the number of bits of each type of information sent by the other side, as well as the number of bits of the CRC code of each type of information.

[0345] To sum up, through the solution provided in the embodiments of the present application, when multiple categories of uplink information are sent on an uplink physical channel, or multiple categories of downlink information are sent on a downlink physical channel, the number of bits of the CRC code can be used to distinguish different categories of information, so as to solve the problem of distinguishing different types of information in the same channel.

[0346] In another possible implementation, the uplink information identifier and the downlink information identifier are cyclic redundancy check (CRC) codes, but the CRC codes are scrambled in different ways, which will be described in detail below.

[0347] See Figure 17, which is a flowchart of another communication method provided in an embodiment of the present application.

[0348] The method comprises the following steps:

[0349] S121: The network device determines an RNTI to be used when scrambling CRC codes corresponding to at least one type of downlink information.

[0350] In the embodiment of the present application, the downlink identification information is a CRC code of the downlink data. Different types of downlink information can be represented by a radio network temporary identity (RNTI) used when scrambling the CRC code of the downlink data.

[0351] In one possible implementation, the RNTI is a 16-bit identifier whose value depends on the RNTI type. An IoT device can only decode a received message using the correct RNTI.

[0352] For example, the RNTI used to scramble the CRC code corresponding to the downlink broadcast information is the first RNTI, and the RNTI used to scramble the CRC code of the downlink control information and the downlink data information is the second RNTI.

[0353] For another example, the RNTI of the CRC code corresponding to the scrambled downlink broadcast information is the first RNTI, the RNTI of the CRC code used to scramble the downlink control information is the second RNTI, and the RNTI of the CRC code used to scramble the downlink data information is the third RNTI.

[0354] S122: The network device sends downlink data.

[0355] S123: The IoT device determines the type of at least one type of downlink information according to the RNTI used when scrambling the CRC code.

[0356] After receiving the downlink data, the IoT device parses the data, determines the number of bits in the CRC code, and determines the type of the corresponding downlink information based on the RNTI used during decoding. For example, if the RNTI used during decoding is the first RNTI, the current downlink information can be determined to be downlink broadcast information.

[0357] S124: The IoT device determines the RNTI to be used when scrambling the CRC codes corresponding to at least one type of uplink information.

[0358] In the embodiment of the present application, the uplink identification information is a CRC code of the uplink data. The RNTI used when scrambling the CRC code of the uplink data can be used to represent different types of uplink information.

[0359] For example, the RNTI used to scramble the CRC code of the uplink access information is the first RNTI, and the RNTI used to scramble the CRC code of the uplink control information and the uplink data information is the second RNTI.

[0360] For another example, the RNTI used to scramble the CRC code of uplink access information is the first RNTI, the RNTI used to scramble the CRC code of uplink control information is the second RNTI, and the RNTI used to scramble the CRC code of uplink data information is the third RNTI.

[0361] S125: The IoT device sends uplink data.

[0362] S126: The network device determines the type of at least one type of uplink information according to the RNTI used when scrambling the CRC code.

[0363] After receiving the downlink data, the network device parses the downlink data, determines the number of bits in the CRC code, and determines the type of the corresponding uplink information based on the RNTI used during decoding. For example, when the RNTI used during decoding is the first RNTI, the current uplink information can be determined to be uplink access information.

[0364] To summarize, through the solution provided in the embodiments of the present application, when multiple categories of uplink information are sent on an uplink physical channel, or multiple categories of downlink information are sent on a downlink physical channel, different RNTIs used when scrambling the CRC code of the data can be used to represent different types of information, so as to solve the problem of distinguishing different types of information on the same channel.

[0365] In the above various implementations, identification information exists in both uplink data and downlink data to distinguish different types of information. The following describes an implementation method for distinguishing information categories based on the resource locations of uplink data and downlink data.

[0366] The following first explains how to implement an IoT device that is only used to receive excitation and does not have the ability to backscatter signals.

[0367] See Figure 18, which is a flowchart of another communication method provided in an embodiment of the present application.

[0368] The method comprises the following steps:

[0369] S131: The network device sends downlink data.

[0370] In the downlink data sent by the network device, different types of downlink information are carried in different resource locations. The resource location can be a frequency domain resource location or a time domain resource location, which is not specifically limited in the embodiment of the present application.

[0371] Downlink data may carry multiple types of downlink information, and the embodiments of the present application do not impose any specific restrictions on the specific types and quantities of downlink information.

[0372] In one possible implementation, a one-to-one correspondence may exist between resource locations and downlink information. That is, one resource location may indicate one type of downlink information, such as a first resource location carrying downlink broadcast information. In another possible implementation, a one-to-many correspondence may exist between resource locations and downlink information. That is, one resource location may carry multiple types of downlink data, such as a resource location carrying both downlink control information and downlink data information.

[0373] S132: When the IoT device receives downlink information at at least one downlink resource location, it determines that the type of the received downlink information is the type of downlink information corresponding to the at least one downlink resource location.

[0374] When an IoT device receives downlink data, it determines the type of downlink information based on the resource location of the downlink information carried in the downlink data. For example, if the first resource location is used to carry downlink broadcast information, the IoT device determines that the type of downlink information is downlink broadcast information when the resource location of the current downlink information is the first resource location.

[0375] In summary, using the method provided in the embodiments of the present application, even if multiple categories of downlink information are sent on a physical channel, the IoT device can identify the type of downlink information based on the resource location of the downlink information, thereby solving the problem of distinguishing different types of information on the same channel.

[0376] The following describes how to implement backscattering capabilities when IoT devices have them.

[0377] See Figure 19, which is a flowchart of another communication method provided in an embodiment of the present application.

[0378] S141: The network device sends downlink data.

[0379] S142: When the IoT device receives downlink information at at least one downlink resource location, it determines that the type of the received downlink information is the type of downlink information corresponding to the at least one downlink resource location.

[0380] For the description of S141, please refer to the above S131, and for the description of S142, please refer to the above S132, which will not be repeated here.

[0381] S143: The IoT device sends uplink data.

[0382] In the uplink data sent by the IoT device, different types of uplink information are carried in different resource locations. The resource location can be a frequency domain resource location or a time domain resource location, which is not specifically limited in the embodiments of the present application.

[0383] The uplink data may carry multiple types of uplink information. The embodiments of the present application do not impose any specific restrictions on the specific types and quantities of the uplink information.

[0384] In one possible implementation, there may be a one-to-one correspondence between resource locations and uplink information, i.e., one resource location may indicate one type of uplink information, e.g., a first resource location may carry uplink access information. In another possible implementation, there may be a one-to-many correspondence between resource locations and uplink information, i.e., one resource location may carry multiple types of uplink data, e.g., one resource location may carry both uplink control information and uplink data information.

[0385] S144: When the network device receives uplink information at at least one uplink resource location, it determines that the type of the received uplink information is the type of uplink information corresponding to the at least one uplink resource location.

[0386] When a network device receives uplink data, it determines the type of uplink information based on the resource location of the uplink information carried in the uplink data. For example, if the first resource location is used to carry uplink access information, the IoT device determines that the type of uplink information is uplink access information when the resource location of the current uplink information is the first resource location.

[0387] Please also refer to Figure 20, which is a schematic diagram of the resource location provided in an embodiment of the present application.

[0388] When the resource location is the frequency domain resource location shown in 20-(A) in FIG20 , different types of information correspond to different signal frequencies in the frequency domain, and the signal receiving end can identify the type of signal based on the frequency difference.

[0389] When the resource location is the time domain resource location shown in 20-(B) in FIG20 , different types of information correspond to different receiving times in the time domain, and the signal receiving end can identify the type of signal according to the signal receiving time.

[0390] In practical applications, downlink information may include first-category downlink information and second-category downlink information. The first-category downlink information includes broadcast information, corresponding to a first downlink resource location. The second-category downlink information includes downlink control information and downlink data information, corresponding to a second downlink resource location. Uplink information may include first-category uplink information and second-category uplink information. The first-category uplink information includes access information, corresponding to a first uplink resource location. The second-category uplink information includes uplink control information and uplink data information, corresponding to a second uplink resource location.

[0391] To summarize, using the method provided in the embodiments of the present application, when sending multiple categories of downlink information on a downlink physical channel, or sending multiple categories of uplink information on an uplink physical channel, the resource location of the signal can be used to distinguish the type of signal, so as to solve the problem of distinguishing different types of information on the same channel.

[0392] The following specifically describes the implementation method when the resource location is a frequency domain resource location.

[0393] See Figure 21, which is a flowchart of another communication method provided in an embodiment of the present application.

[0394] S151: The network device determines a downlink frequency domain resource position corresponding to at least one type of downlink information.

[0395] In the embodiment of the present application, the downlink frequency domain resource location is used to distinguish the type of downlink information.

[0396] The frequency domain resource position includes but is not limited to one of the following: the position of a resource element (RE) and the position of an RE group.

[0397] An RE group includes multiple REs. In the frequency domain, an RE represents the smallest unit of frequency domain resources, occupying one subcarrier (15 kHz). In the time domain, an RE represents the smallest unit of time domain resources, occupying one OFDM symbol (1 / 14 ms).

[0398] The specific use of RE or RE group can be determined by the amount of data in the actual application. When the amount of data to be transmitted is large, RE group can be used, and when the amount of data is small, RE can be used.

[0399] For example, when the downlink information transmitted is downlink broadcast information, the allocated frequency domain resource position is the first frequency domain resource position, such as the frequency band of frequency A-frequency B, which can correspond to one RE, multiple REs, one RE group or multiple RE groups; when the downlink information transmitted is downlink control information and downlink data information, the allocated frequency domain resource position is the second frequency domain resource position, such as the frequency band of frequency C-frequency D, which can correspond to one RE, multiple REs, one RE group or multiple RE groups.

[0400] For another example, when the transmitted downlink information is downlink broadcast information, the allocated frequency domain resource position is the first frequency domain resource position, such as the frequency band of frequency A-frequency B, which can correspond to one RE, multiple REs, one RE group or multiple RE groups; when the transmitted downlink information is downlink control information, the allocated frequency domain resource position is the second frequency domain resource position, such as the frequency band of frequency C-frequency D, which can correspond to one RE, multiple REs, one RE group or multiple RE groups; when the transmitted downlink information is downlink data information, when the transmitted downlink information is downlink control information, the allocated frequency domain resource position is the third frequency domain resource position, such as the frequency band of frequency E-frequency F, which can correspond to one RE, multiple REs, one RE group or multiple RE groups.

[0401] S152: The network device sends downlink data.

[0402] S153: When the IoT device receives downlink information at at least one downlink frequency domain resource location, it determines the type of the corresponding downlink information according to the downlink frequency domain resource location.

[0403] After receiving downlink data, the IoT device determines the type of downlink information based on the frequency domain resource location at the time the downlink data is received. For example, if downlink data is received in the frequency band of frequency A-frequency B, the current downlink information can be determined to be downlink broadcast information.

[0404] S154: The IoT device determines a frequency domain resource location of an uplink corresponding to at least one type of uplink information.

[0405] In the embodiment of the present application, the type of uplink information is distinguished by the uplink frequency domain resource location. The frequency domain resource location includes but is not limited to one of the following: a RE location, a RE group location, wherein the RE group includes multiple REs.

[0406] The specific use of RE or RE group can be determined by the amount of data in the actual application. When the amount of data to be transmitted is large, RE group can be used, and when the amount of data is small, RE can be used.

[0407] For example, when the uplink information transmitted is uplink access information, the allocated frequency domain resource position is the fourth frequency domain resource position, such as the frequency band of frequency G-frequency H, which can correspond to one RE, multiple REs, one RE group or multiple RE groups; when the uplink information transmitted is uplink control information and uplink data information, the allocated frequency domain resource position is the fifth frequency domain resource position, such as the frequency band of frequency M-frequency N, which can correspond to one RE, multiple REs, one RE group or multiple RE groups.

[0408] For another example, when the transmitted uplink information is uplink access broadcast information, the allocated frequency domain resource position is the fourth frequency domain resource position, such as the frequency band of frequency G-frequency H, which can correspond to one RE, multiple REs, one RE group or multiple RE groups; when the transmitted uplink information is uplink control information, the allocated frequency domain resource position is the fifth frequency domain resource position, such as the frequency band of frequency M-frequency N, which can correspond to one RE, multiple REs, one RE group or multiple RE groups; when the transmitted uplink information is uplink data information, when the transmitted uplink information is uplink control information, the allocated frequency domain resource position is the sixth frequency domain resource position, such as the frequency band of frequency X-frequency Y, which can correspond to one RE, multiple REs, one RE group or multiple RE groups.

[0409] S155: The IoT device sends uplink data.

[0410] S156: When the network device receives uplink information at at least one uplink resource location, it determines the type of corresponding uplink information according to the location of the uplink frequency domain resource.

[0411] After receiving uplink data, the network device determines the type of uplink information based on the frequency domain resource location at the time the uplink data was received. For example, when uplink data is received in the frequency band of frequency G to frequency H, i.e., the fourth frequency domain resource location, the current uplink information can be determined to be uplink broadcast information.

[0412] To sum up, using the method provided in the embodiments of the present application, when sending multiple categories of downlink information on a downlink physical channel, or sending multiple categories of uplink information on an uplink physical channel, the frequency domain resource position when the signal is received can be used to distinguish the type of signal, so as to solve the problem of distinguishing different types of information in the same channel.

[0413] In another possible implementation, different types of information use different spreading codes, and the spreading codes can be used to distinguish the types of information, which is described in detail below.

[0414] See Figure 22, which is a flowchart of another communication method provided in an embodiment of the present application.

[0415] S161: The network device determines a spreading code corresponding to at least one type of downlink information.

[0416] In the embodiment of the present application, spread spectrum codes are used to distinguish types of downlink information.

[0417] Spread spectrum technology amplifies the spectrum of a transmitted signal through spread-spectrum modulation. The data transmitter, or network device, uses a spreading code that is generally unrelated to the specific service data. However, the data receiver, or IoT device, requires the spreading code to despread the transmitted data.

[0418] The frequency domain resource position includes but is not limited to one of the following: the position of a resource element (RE) and the position of an RE group.

[0419] For example, when the transmitted downlink information is downlink broadcast information, the adopted spreading code is the first spreading code; when the transmitted downlink information is downlink control information and downlink data information, the adopted spreading code is the second spreading code.

[0420] For another example, when the transmitted downlink information is downlink broadcast information, the spreading code used is the first spreading code; when the transmitted downlink information is downlink control information, the spreading code used is the second spreading code; when the transmitted downlink information is downlink data information, the spreading code used is the third spreading code.

[0421] S162: The network device sends downlink data.

[0422] S163: When the IoT device receives downlink information at at least one downlink frequency domain resource location, it determines the type of the corresponding downlink information according to the spreading code of the downlink frequency domain resource location.

[0423] The IoT device determines the type of the corresponding downlink information based on the spreading code used during despreading. For example, when the spreading code used during despreading is the first spreading code, the current downlink information can be determined to be downlink broadcast information.

[0424] S164: The IoT device determines a spreading code corresponding to at least one type of uplink information.

[0425] In the embodiment of the present application, a spreading code is used to distinguish the type of uplink information.

[0426] For example, when the transmitted uplink information is uplink access information, the adopted spreading code is the first spreading code; when the transmitted uplink information is uplink control information and uplink data information, the adopted spreading code is the second spreading code.

[0427] For another example, when the transmitted uplink information is uplink access information, the spreading code used is the first spreading code; when the transmitted uplink information is uplink control information, the spreading code used is the second spreading code; when the transmitted uplink information is uplink data information, the spreading code used is the third spreading code.

[0428] S165: The IoT device sends uplink data.

[0429] S166: When the network device receives uplink information at at least one uplink resource location, it determines the type of the corresponding uplink information according to the spreading code of the uplink frequency domain resource.

[0430] The network device determines the type of the corresponding uplink information according to the spreading code used in despreading. For example, when the spreading code used in despreading is the first spreading code, the current uplink information can be determined to be uplink access information.

[0431] To summarize, using the method provided in the embodiments of the present application, when sending multiple categories of downlink information on a downlink physical channel, or sending multiple categories of uplink information on an uplink physical channel, spread spectrum codes can be used to distinguish the types of signals to solve the problem of distinguishing different types of information on the same channel.

[0432] The following describes the implementation method when the resource location is a time domain resource location.

[0433] See Figure 23, which is a flowchart of another communication method provided in an embodiment of the present application.

[0434] The method comprises the following steps:

[0435] S171: The network device determines downlink time domain resource locations corresponding to at least one type of downlink information.

[0436] In the embodiment of the present application, the time domain resource location is used to distinguish the type of downlink information.

[0437] The time configuration parameter of the time domain resource location may be one of the following: a system frame number (SFN), a timeslot number, an orthogonal frequency division multiplexing (OFDM) symbol number, or an OFDM symbol offset value.

[0438] When the time configuration parameter of the time domain resource location is SFN, for example, the first time domain resource location can be the relative time determined by the system frame number F1 to the system frame number F2, and the second time domain resource location can be the relative time determined by the system frame number F3 to the system frame number F4.

[0439] When the time configuration parameter of the time domain resource location is the time slot number, for example, the first time domain resource location may be the time slot determined by time slot number n1 to time slot number n2, and the second time domain resource location may be the time slot determined by time slot number n3 to time slot number n4.

[0440] When the time configuration parameter of the time domain resource position is the OFDM symbol number, for example, the first time domain resource position may be the relative time determined by the OFDM symbol number n1, and the second time domain resource position may be the relative time determined by the OFDM symbol number n2.

[0441] When the time configuration parameter of the time domain resource position is the OFDM symbol offset value, for example, the first time domain resource position may be the relative time determined by the OFDM symbol offset value off1, and the second time domain resource position may be the relative time determined by the OFDM symbol offset value off2.

[0442] There can be a one-to-one correspondence between the time domain resource location and the downlink information, that is, one time domain resource location can carry one type of downlink information; there can also be a one-to-many correspondence between the time domain resource location and the downlink information, that is, one time domain resource location can carry multiple types of downlink data, as illustrated below.

[0443] For example, when the transmitted downlink information is downlink broadcast information, the corresponding time domain resource position is the first time domain resource position; when the transmitted downlink information is downlink control information and downlink data information, the corresponding time domain resource position is the second time domain resource position.

[0444] For another example, when the transmitted downlink information is downlink broadcast information, the corresponding time domain resource position is the first time domain resource position; when the transmitted downlink information is downlink control information, the corresponding time domain resource position is the second time domain resource position; when the transmitted downlink information is downlink data information, the corresponding time domain resource position is the third time domain resource position.

[0445] S172: The network device sends downlink data.

[0446] S173: When the IoT device receives downlink information at at least one downlink time domain resource location, it determines the type of the corresponding downlink information according to the downlink time domain resource location.

[0447] The IoT device determines the type of the corresponding downlink information based on the time domain resource location of the received downlink information. For example, when the time domain resource location of the received downlink information is the first time domain resource location, it can be determined that the current downlink information is downlink broadcast information.

[0448] S174: The IoT device determines the uplink time domain resource location corresponding to at least one type of uplink information.

[0449] In the embodiment of the present application, the time domain resource location is used to distinguish the type of uplink information.

[0450] The time configuration parameter of the time domain resource location may be one of the following: SFN, timeslot number, OFDM symbol number, or OFDM symbol offset value.

[0451] There can be a one-to-one correspondence between the time domain resource location and the uplink information, that is, one time domain resource location can carry one type of uplink information; there can also be a one-to-many correspondence between the time domain resource location and the uplink information, that is, one time domain resource location can carry multiple types of uplink data, as illustrated below.

[0452] For example, when the transmitted uplink information is uplink access information, the corresponding time domain resource position is the first time domain resource position; when the transmitted uplink information is uplink control information and uplink data information, the corresponding time domain resource position is the second time domain resource position.

[0453] For another example, when the transmitted uplink information is uplink access information, the corresponding time domain resource position is the first time domain resource position; when the transmitted uplink information is uplink control information, the corresponding time domain resource position is the second time domain resource position; when the transmitted uplink information is uplink data information, the corresponding time domain resource position is the third time domain resource position.

[0454] S175: The IoT device sends uplink data.

[0455] S176: When the network device receives uplink information at at least one uplink resource location, it determines the type of corresponding downlink information according to the uplink time domain resource location.

[0456] The network device determines the type of the corresponding uplink information according to the time domain resource location of the received uplink information. For example, when the time domain resource location of the received uplink information is the first time domain resource location, it can be determined that the current uplink information is uplink access information.

[0457] To summarize, using the method provided in the embodiments of the present application, when sending multiple categories of downlink information on a downlink physical channel, or sending multiple categories of uplink information on an uplink physical channel, the time domain resource location can be used to distinguish the type of signal to solve the problem of distinguishing different types of information on the same channel.

[0458] Based on the communication method provided in the above embodiments, an embodiment of the present application further provides a communication device, which is described in detail below with reference to the accompanying drawings.

[0459] See Figures 24 and 25. Figure 24 is a schematic diagram of a communication device provided in an embodiment of the present application; Figure 25 is a schematic diagram of another communication device provided in an embodiment of the present application.

[0460] The communication device 10 can be applied to an IoT device, and the communication device 20 can be applied to a network device.

[0461] The communication device 10 includes a first receiving unit 11, a first processing unit 12, and a first sending unit 13. In another possible implementation, the communication device 10 may not include the first sending unit 13.

[0462] The communication device 20 includes a second receiving unit 21 , a second processing unit 22 and a second sending unit 23 .

[0463] In a possible implementation, the first receiving unit 11 is configured to receive downlink data, wherein the downlink data carries downlink identification information and at least one type of downlink information, and the downlink identification information is used to indicate the corresponding type of downlink information.

[0464] In a possible implementation, the first processing unit 12 is configured to identify a type of at least one type of downlink information according to the downlink identification information.

[0465] In a possible implementation, the first sending unit 13 is configured to send uplink data, wherein the uplink data carries uplink identification information and at least one type of uplink information, and the uplink identification information is used to indicate the corresponding type of uplink information.

[0466] In a possible implementation, the uplink information identifier and the downlink information identifier are preamble codes, and the first processing unit 12 is used to determine the type of at least one type of downlink information according to the length of the preamble code; and determine the length of the preamble code corresponding to the at least one type of uplink information.

[0467] In one possible implementation, the uplink information identifier and the downlink information identifier are preambles, and the first processing unit 12 is configured to determine the type of at least one type of downlink information based on a sequence type of the preamble; and determine the sequence type of the preamble corresponding to each of the at least one type of uplink information. The preamble sequence type includes, but is not limited to, one of the following: a pseudo-random PN sequence, a longest linear feedback shift register sequence, a Gold sequence, or a Zadoff-Chu sequence.

[0468] In a possible implementation, the uplink information identifier and the downlink information identifier are preamble codes, and the first processing unit 12 is used to determine the type of at least one type of downlink information according to the sequence of the preamble code; and determine the sequence of the preamble code corresponding to the at least one type of uplink information.

[0469] In a possible implementation, a sequence of preamble codes indicating each type of uplink information and downlink information is generated by corresponding generation parameters.

[0470] In one possible implementation, the uplink information identifier and the downlink information identifier serve as preambles. The first processing unit 12 is configured to determine the type of at least one type of downlink information based on a first sequence and a sequence of the downlink identification information; determine a cyclic shift pattern corresponding to at least one type of uplink data, and cyclically shift the second sequence according to the corresponding cyclic shift pattern to generate preambles corresponding to the at least one type of uplink information. The sequence in the downlink identification information is generated by cyclically shifting the first sequence in the corresponding pattern.

[0471] In one possible implementation, the uplink information identifier and the downlink information identifier are preambles, and the first processing unit 12 is configured to determine the type of at least one type of downlink information based on an encoding scheme of the preamble; and before sending uplink data, determine an encoding scheme for the preamble corresponding to each of the at least one type of uplink information. The encoding scheme for the preamble is one of the following: Manchester encoding, pulse width encoding, Miller encoding, and pulse position encoding.

[0472] In one possible implementation, the downlink information identifier is a first field located at a first position and occupying a first number of bits in the downlink data; the uplink information identifier is a second field located at a second position and occupying a second number of bits in the uplink data. The first processing unit 12 is configured to determine the type of at least one type of downlink information based on a sequence of the first field; and to determine the sequence of the second field corresponding to each of the at least one type of uplink information.

[0473] In one possible implementation, the downlink information identifier is a first field located at a first position and occupying a first number of bits in the downlink data; the uplink information identifier is a second field located at a second position and occupying a second number of bits in the uplink data. The first processing unit 12 is configured to determine the type of at least one type of downlink information based on the encoding method of the third field; and to determine the encoding method of the fourth field corresponding to each of the at least one type of uplink information.

[0474] In one possible implementation, the downlink information identifier is a fifth field located at a fifth position and occupying a fifth number of bits in the downlink data, and the uplink information identifier is a sixth field located at a sixth position and occupying a sixth number of bits in the uplink data. The first processing unit 12 is configured to determine the type of at least one type of downlink information based on the modulation mode of the fifth field; and determine the modulation mode of the sixth field corresponding to each of the at least one type of uplink information.

[0475] In one possible implementation, the uplink information identifier and the downlink information identifier are CRC codes. The first processing unit 12 is configured to determine the type of at least one type of downlink information based on the number of bits of the CRC code; and before sending uplink data, determine the number of bits of the CRC code corresponding to each of the at least one type of uplink information.

[0476] In one possible implementation, the uplink information identifier and the downlink information identifier are CRC codes. The first processing unit 12 is configured to determine the type of at least one type of downlink information using the RNTI used when scrambling the CRC code; and, before sending uplink data, determine the RNTI used when scrambling the CRC codes corresponding to the at least one type of uplink information.

[0477] In one possible implementation, at least one type of downlink information includes a first type of downlink information and a second type of downlink information, the first type of downlink information includes broadcast information, the first type of downlink information corresponds to first downlink identification information, the second type of downlink information includes downlink control information and downlink data information, and the second type of downlink information corresponds to second downlink identification information; at least one type of uplink information includes a first type of uplink information and a second type of uplink information, the first type of uplink information includes access information, the first type of uplink information corresponds to first uplink identification information, the second type of uplink information includes uplink control information and uplink data information, and the second type of uplink information corresponds to second uplink identification information.

[0478] In one possible implementation, the first receiving unit 11 is configured to receive downlink data. The downlink data carries at least one type of downlink information in at least one downlink resource location, where the downlink resource location corresponds to the type of the downlink information. The first processing unit 12 is configured to, upon receiving downlink information in the at least one downlink resource location, determine that the type of the received downlink information is the type of downlink information corresponding to the at least one downlink resource location.

[0479] In a possible implementation, the first sending unit 13 is configured to send uplink data, wherein the uplink data carries at least one type of uplink information in at least one uplink resource location, and the uplink resource location corresponds to the type of the uplink information.

[0480] In one possible implementation, the uplink resource location and the uplink resource location are frequency domain resource locations. The first processing unit 12 is configured to, upon receiving downlink information at at least one downlink frequency domain resource location, determine the type of corresponding downlink information based on the downlink frequency domain resource location; and, before sending uplink data, determine the uplink frequency domain resource locations corresponding to at least one type of uplink information. The frequency domain resource location is one of the following: a resource element (RE) location, or a resource element (RE) group location, where the RE group includes multiple REs.

[0481] In one possible implementation, the uplink resource location and the downlink resource location are frequency domain resource locations. The first processing unit 12 is configured to, upon receiving downlink information at at least one downlink frequency domain resource location, determine the type of corresponding downlink information based on the spreading code of the downlink frequency domain resource location; and, before sending uplink data, determine the spreading code corresponding to each of at least one type of uplink information.

[0482] In one possible implementation, the uplink resource location and the downlink resource location are time domain resource locations. The first processing unit 12 is specifically configured to, upon receiving downlink information at at least one downlink time domain resource location, determine the type of corresponding downlink information based on the downlink time domain resource location; and, before sending uplink data, determine the uplink time domain resource location corresponding to each of the at least one type of uplink information. The time configuration parameter of the time domain resource location is one of the following: a system frame number (SFN), a time slot number, an orthogonal frequency division multiplexing (OFDM) symbol number, or an OFDM symbol offset value.

[0483] In one possible implementation, at least one type of downlink information includes first-type downlink information and second-type downlink information, the first-type downlink information includes broadcast information, the first-type downlink information corresponds to a first downlink resource location, the second-type downlink information includes downlink control information and downlink data information, the second-type downlink information corresponds to a second downlink resource location. At least one type of uplink information includes first-type uplink information and second-type uplink information, the first-type uplink information includes access information, the first-type uplink information corresponds to a first uplink resource location, the second-type uplink information includes uplink control information and uplink data information, the second-type uplink information corresponds to a second uplink resource location.

[0484] In a possible implementation, the second sending unit 23 is configured to send downlink data, wherein the downlink data carries downlink identification information and at least one type of downlink information, and the downlink identification information is used to indicate the corresponding type of downlink information.

[0485] In one possible implementation, the second receiving unit 21 receives uplink data. The uplink data carries uplink identification information and at least one type of uplink information, where the uplink identification information indicates the corresponding type of uplink information. The second processing unit 22 is configured to identify the type of the at least one type of uplink information based on the uplink identification information.

[0486] In one possible implementation, the uplink information identifier and the downlink information identifier are preambles. The second processing unit 22 is configured to determine the length of the preamble corresponding to at least one type of downlink information before sending downlink data; and determine the type of at least one type of uplink information based on the length of the preamble.

[0487] In one possible implementation, the uplink information identifier and the downlink information identifier are preambles. The second processing unit 22 is configured to determine, before sending downlink data, the sequence type of the preamble corresponding to at least one type of downlink information; and determine the type of at least one type of uplink information based on the sequence type of the preamble.

[0488] In one possible implementation, the uplink information identifier and the downlink information identifier are preamble codes. The second processing unit 22 is configured to determine the preamble code sequence corresponding to at least one type of downlink information before sending downlink data; and determine the type of at least one type of uplink information based on the preamble code sequence.

[0489] In a possible implementation, a sequence of preamble codes indicating each type of uplink information and downlink information is generated by corresponding generation parameters.

[0490] In one possible implementation, the uplink information identifier and the downlink information identifier are preambles. The second processing unit 22 is configured to, before transmitting downlink data, determine a cyclic shift pattern corresponding to at least one type of downlink information, and cyclically shift a first sequence according to the corresponding cyclic shift pattern to generate at least one type of preamble corresponding to the downlink data; and determine the type of the at least one type of uplink information based on the second sequence and the sequence of the uplink identification information. The sequence in the uplink identification information is generated by cyclically shifting the second sequence in the corresponding pattern.

[0491] In one possible implementation, the uplink information identifier and the downlink information identifier are preamble codes, and the second processing unit 22 is used to determine the encoding method of the preamble codes corresponding to the at least one type of downlink information before sending the downlink data; and determine the type of the at least one type of uplink information based on the encoding method of the preamble code.

[0492] In one possible implementation, the downlink information identifier is a first field located at a first position and occupying a first number of bits in the downlink data, and the uplink information identifier is a second field located at a second position and occupying a second number of bits in the uplink data. The second processing unit 22 is configured to, before sending the downlink data, determine a sequence of the first field corresponding to at least one type of downlink information; and determine a type of the at least one type of uplink information based on the sequence of the second field.

[0493] In one possible implementation, the downlink information identifier is a third field located at a third position and occupying a third number of bits in the downlink data, and the uplink information identifier is a fourth field located at a fourth position and occupying a fourth number of bits in the uplink data. The second processing unit 22 is configured to determine a coding scheme for the third field corresponding to at least one type of downlink information, respectively; and determine a type of the at least one type of uplink information based on the coding scheme of the fourth field.

[0494] In one possible implementation, the downlink information identifier is a fifth field located at a fifth position and occupying a fifth number of bits in the downlink data, and the uplink information identifier is a sixth field located at a sixth position and occupying a sixth number of bits in the uplink data. The second processing unit 22 is configured to determine a modulation scheme of the third field corresponding to at least one type of downlink information; and determine a type of the at least one type of uplink information based on the modulation scheme of the sixth field.

[0495] In a possible implementation, the uplink information identifier and the downlink information identifier are CRC codes. The second processing unit 22 is configured to determine the number of bits of the CRC code corresponding to at least one type of downlink information, and determine the type of at least one type of uplink information based on the number of bits of the CRC code.

[0496] In one possible implementation, the uplink information identifier and the downlink information identifier are CRC codes. The second processing unit 22 is configured to determine, before sending downlink data, an RNTI to be used when scrambling the CRC codes corresponding to the at least one type of downlink information; and determine the type of the at least one type of uplink information based on the RNTI used when scrambling the CRC codes.

[0497] In a possible implementation, the second sending unit 21 is configured to send downlink data, wherein the downlink data carries at least one type of downlink information in at least one downlink resource location, and the downlink resource location corresponds to the type of the downlink information.

[0498] In one possible implementation, the second receiving unit 23 is configured to receive uplink data. The uplink data carries at least one type of uplink information in at least one uplink resource location, where the uplink resource location corresponds to the type of the uplink information. The second processing unit 22 is configured to, upon receiving the uplink information in the at least one uplink resource location, determine that the type of the received uplink information is the type of uplink information corresponding to the at least one uplink resource location.

[0499] In one possible implementation, the downlink resource location and the uplink resource location are frequency domain resource locations. The second processing unit 22 is configured to, before sending downlink data, determine downlink frequency domain resource locations corresponding to at least one type of downlink information; and when uplink information is received at at least one uplink frequency domain resource location, determine the type of the corresponding uplink information based on the location of the uplink frequency domain resource.

[0500] In one possible implementation, the downlink resource location and the uplink resource location are frequency domain resource locations. The second processing unit 22 is configured to, before transmitting downlink data, determine a spreading code corresponding to at least one type of downlink information; and when uplink information is received at at least one uplink resource location, determine the type of the corresponding uplink information based on the spreading code of the uplink frequency domain resource.

[0501] In one possible implementation, the downlink resource location and the uplink resource location are frequency domain resource locations. The second processing unit 22 is configured to, before sending downlink data, determine downlink time domain resource locations corresponding to at least one type of downlink information; and when uplink information is received at at least one uplink resource location, determine the type of the corresponding uplink information based on the uplink time domain resource location.

[0502] The embodiment of the present application also provides a network device, which is described in detail below with reference to the accompanying drawings.

[0503] See Figure 26, which is a schematic diagram of a network device provided in an embodiment of the present application.

[0504] The network device includes but is not limited to a base station, a core network unit, and other network devices. The network device is described as a base station as an example.

[0505] The base station includes part 1110 , part 1120 and part 1130 .

[0506] Part 1110 is mainly used for baseband processing, controlling the base station, etc.; Part 1110 is usually the control center of the base station, which can usually be called a processor, and is used to control the base station to execute the communication method in the above method embodiment.

[0507] Section 1120 is primarily used to store computer program code and data. Section 1130 is primarily used for transmitting and receiving radio frequency signals and converting radio frequency signals into baseband signals. Section 1130 is often referred to as a transceiver module, transceiver, transceiver circuit, or transceiver.

[0508] The transceiver module in section 1130, also known as a transceiver or transceiver, includes an antenna 1133 and a radio frequency circuit (not shown), which primarily performs radio frequency processing. Alternatively, the device used for receiving in section 1130 can be considered a receiver, and the device used for transmitting can be considered a transmitter. Specifically, section 1130 includes a receiver 1132 and a transmitter 1131. A receiver can also be referred to as a receiving module, receiver, or receiving circuit, and a transmitter can be referred to as a transmitting module, transmitter, or transmitting circuit.

[0509] Sections 1110 and 1120 may include one or more boards, each of which may include one or more processors and one or more memories. The processor is used to read and execute programs in the memory to implement baseband processing functions and control the base station. If multiple boards are present, the boards may be interconnected to enhance processing capabilities. As an optional implementation, multiple boards may share one or more processors, multiple boards may share one or more memories, or multiple boards may simultaneously share one or more processors.

[0510] For example, in one implementation, the transceiver module in section 1130 is used to execute the process of sending and receiving related information executed by the network device in the aforementioned method embodiment. The processor in section 1110 is used to execute the process of processing related information executed by the network device in the aforementioned method embodiment.

[0511] It should be understood that FIG26 is merely an example and not a limitation, and the network device including the processor, memory, and transceiver may not rely on the structure shown in FIG26 .

[0512] See Figure 27, which is a schematic diagram of an Internet of Things device provided in an embodiment of the present application.

[0513] The embodiments of the present application do not specifically limit the type of IoT device. The IoT device can be used to receive excitation signals or backscattered signals; it may not be a power storage device and cannot independently generate or amplify signals; it may be a power storage device, but cannot independently generate or amplify signals; it may be a power storage device and can also independently generate or amplify signals; it may be a power storage device (capacitor) or a super capacitor.

[0514] The IoT device shown in FIG27 includes a processor 310, an energy storage unit 320, a sensor module 330, an indicator 340, an internal memory 350, a communication module 360, and an antenna 370. It is understood that the structure illustrated in this embodiment does not constitute a specific limitation on the electronic device. In other embodiments, the electronic device may include more or fewer components than shown, or combine certain components, split certain components, or arrange the components differently. The components shown in the figure can be implemented in hardware, software, or a combination of software and hardware.

[0515] The processor 310 may include one or more processing units. For example, the processor 310 may include an application processor (AP), a modem processor, a graphics processing unit (GPU), an image signal processor (ISP), a controller, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural-network processing unit (NPU). The different processing units may be independent devices or integrated into one or more processors.

[0516] It is understood that the interface connection relationship between the modules illustrated in this embodiment is only a schematic illustration and does not constitute a structural limitation of the electronic device. In other embodiments of the present application, the electronic device may also adopt different interface connection methods in the above embodiments, or a combination of multiple interface connection methods.

[0517] The energy storage unit 320 may be a battery, a capacitor, or other energy storage element. It is understood that when the electronic device is an ambient IoT device, it may not have an energy storage unit, but instead directly collects energy from the environment to power itself, such as solar energy, radio waves, motion, vibration, heat, or pressure.

[0518] The sensor module 330 may include one or more of a pressure sensor, a gyroscope sensor, an air pressure sensor, a magnetic sensor, an acceleration sensor, a distance sensor, a proximity light sensor, a fingerprint sensor, a temperature sensor, a touch sensor, an ambient light sensor, a bone conduction sensor, etc., to realize the detection function.

[0519] The indicator 340 may be an indicator light, which may be used to indicate whether the device is started or to indicate a message, etc. The indicator 340 may also not be provided.

[0520] The internal memory 350 can be used to store computer executable program code, which includes instructions. The processor 310 executes various functional applications and data processing of the electronic device by running the instructions stored in the internal memory 350. The internal memory 350 may include a program storage area and a data storage area. Among them, the program storage area can store an operating system, an application required for at least one function, etc. The data storage area can store data collected or generated during the use of the IoT device. The internal memory 350 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, a universal flash storage (UFS), etc.

[0521] The wireless communication function of the IoT device can be implemented through the communication module 360 ​​and the antenna 370. The antenna 370 may include one or more antennas. When the electronic device is an ambient IoT device, the antenna 370 can also serve as an energy receiving unit, using the collected electromagnetic wave energy to power the IoT device.

[0522] The present application also provides a communication system, which may include a network device as shown in Figure 26 and an Internet of Things device as shown in Figure 27.

[0523] An embodiment of the present application also provides a computer-readable storage medium. The computer-readable storage medium can be any available medium that a computing device can store or a data storage device such as a data center that contains one or more available media. The available medium can be a magnetic medium (for example, a floppy disk, a hard disk, a tape), an optical medium (for example, a DVD), or a semiconductor medium (for example, a solid-state hard disk), etc. The computer-readable storage medium includes instructions that instruct the electronic device to execute the above-mentioned communication method. An embodiment of the present application also provides another computer-readable storage medium. The computer-readable storage medium includes instructions that instruct the electronic device to execute the above-mentioned communication method.

[0524] The embodiment of the present application further provides a computer program product comprising instructions. The computer program product may be software or a program product comprising instructions that can be run on an electronic device or stored in any available medium. When the computer program product is run on at least one electronic device, the at least one electronic device executes the above-mentioned communication method. The embodiment of the present application further provides a computer program product comprising instructions. When the computer program product is run on at least one electronic device, the at least one electronic device executes the above-mentioned communication method.

[0525] It should be understood that in this application, "at least one (item)" means one or more, and "plurality" means two or more. "And / or" is used to describe the association relationship of associated objects, indicating that three relationships may exist. For example, "A and / or B" can mean: only A exists, only B exists, and A and B exist at the same time, where A and B can be singular or plural. The character " / " generally indicates that the previous and next associated objects are in an "or" relationship. "At least one of the following items" or similar expressions refers to any combination of these items, including any combination of single items or plural items. For example, at least one of a, b or c can mean: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, c can be single or multiple.

[0526] As described above, the above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the above embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the above embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present application.

Claims

1. A communication method, characterized in that: The method comprises: receiving downlink data, where the downlink data carries downlink identification information and at least one type of downlink information, where the downlink identification information is used to indicate the corresponding type of downlink information; The type of the at least one type of downlink information is identified according to the downlink identification information.

2. The method according to claim 1, characterized in that The method further comprises: Uplink data is sent, where the uplink data carries uplink identification information and at least one type of uplink information, wherein the uplink identification information is used to indicate uplink information of a corresponding type.

3. The method according to claim 2, characterized in that The uplink information identifier and the downlink information identifier are preamble codes, and identifying the type of the at least one type of downlink information according to the downlink identifier information includes: determining, according to the length of the preamble, a type of the at least one type of downlink information; Before sending the uplink data, the method further includes: Determine the length of the preamble code corresponding to the at least one type of uplink information.

4. The method according to claim 2, characterized in that The uplink information identifier and the downlink information identifier are preamble codes, and identifying the type of the at least one type of downlink information according to the downlink identifier information includes: Determine the type of the at least one type of downlink information according to a sequence type of the preamble, where the sequence type of the preamble is one of the following: Pseudo-random PN sequence, longest linear feedback shift register sequence, Gold sequence, Zadoff-Chu sequence; Before sending the uplink data, the method further includes: Determine a sequence type of a preamble code corresponding to each of the at least one type of uplink information.

5. The method according to claim 2, characterized in that The uplink information identifier and the downlink information identifier are preamble codes, and identifying the type of the at least one type of downlink information according to the downlink identifier information includes: Determining a type of the at least one type of downlink information according to a sequence of the preamble; Before sending the uplink data, the method further includes: Determine a sequence of a preamble code corresponding to each of the at least one type of uplink information.

6. The method according to claim 5, characterized in that A sequence of preamble codes indicating each type of the uplink information and the downlink information is generated by corresponding generation parameters.

7. The method according to claim 2, characterized in that The uplink information identifier and the downlink information identifier are preamble codes, and identifying the type of the at least one type of downlink information according to the downlink identifier information includes: determining a type of the at least one type of downlink information according to a first sequence and a sequence of the downlink identification information, wherein the sequence in the downlink identification information is generated by performing a corresponding cyclic shift on the first sequence; Before sending the uplink data, the method further includes: Determine cyclic shift modes corresponding to the at least one type of uplink data, and perform cyclic shift on the second sequence according to the corresponding cyclic shift modes to generate preamble codes corresponding to the at least one type of uplink information.

8. The method according to claim 2, characterized in that The uplink information identifier and the downlink information identifier are preamble codes, and identifying the type of the at least one type of downlink information according to the downlink identifier information includes: Determine the type of the at least one type of downlink information according to an encoding mode of the preamble, where the encoding mode of the preamble is one of the following: Manchester encoding, pulse width PIE encoding, Miller encoding, pulse position PPM encoding; Before sending the uplink data, the method further includes: Determine a coding mode of the preamble codes respectively corresponding to the at least one type of uplink information.

9. The method according to claim 2, characterized in that The downlink information identifier is a first field in the downlink data that is located at a first position and occupies a first number of bits. The identifying, based on the downlink identifier information, the type of the at least one type of downlink information includes: determining, according to a sequence of the first field, a type of the at least one type of downlink information; The uplink information identifier is a second field in the uplink data that is located at a second position and occupies a second number of bits. Before sending the uplink data, the method further includes: Determine a sequence of second fields corresponding to the at least one type of uplink information.

10. The method according to claim 2, characterized in that The downlink information identifier is a third field located at a third position and occupying a third number of bits in the downlink data, and identifying the type of the at least one type of downlink information according to the downlink identifier information includes: Determine the type of the at least one type of downlink information according to a coding mode of the third field, where the coding mode is one of the following: Manchester encoding, pulse width PIE encoding, Miller encoding, pulse position PPM encoding; The uplink information identifier is a fourth field located at a fourth position and occupying a fourth number of bits in the uplink data. Before sending the uplink data, the method further includes: Determine a coding mode of the fourth field corresponding to each of the at least one type of uplink information.

11. The method according to claim 2, characterized in that The downlink information identifier is a fifth field located at a fifth position and occupying a fifth number of bits in the downlink data, and identifying the type of the at least one type of downlink information according to the downlink identifier information includes: determining, according to a modulation mode of the fifth field, a type of the at least one type of downlink information; The uplink information identifier is a sixth field located at a sixth position and occupying a sixth number of bits in the uplink data. Before sending the uplink data, the method further includes: Determine a modulation mode of the sixth field corresponding to each of the at least one type of uplink information.

12. The method according to claim 2, characterized in that The uplink information identifier and the downlink information identifier are cyclic redundancy check (CRC) codes, and the identifying, according to the downlink identifier information, the type of the at least one type of downlink information includes: Determining a type of the at least one type of downlink information according to the number of bits of the CRC code; Before sending the uplink data, the method further includes: Determine the number of bits of the CRC code corresponding to the at least one type of uplink information.

13. The method according to claim 2, characterized in that The uplink information identifier and the downlink information identifier are cyclic redundancy check (CRC) codes, and the identifying, according to the downlink identifier information, the type of the at least one type of downlink information includes: Determining a type of the at least one type of downlink information according to a radio network temporary identifier (RNTI) used when scrambling the CRC code; Before sending the uplink data, the method further includes: Determine an RNTI used when scrambling the CRC codes respectively corresponding to the at least one type of uplink information.

14. The method according to any one of claims 2 to 13, characterized in that The at least one type of downlink information includes a first type of downlink information and a second type of downlink information, the first type of downlink information includes broadcast information, the first type of downlink information corresponds to first downlink identification information, the second type of downlink information includes downlink control information and downlink data information, and the second type of downlink information corresponds to second downlink identification information; The at least one type of uplink information includes a first type of uplink information and a second type of uplink information, the first type of uplink information includes access information, the first type of uplink information corresponds to first uplink identification information, the second type of uplink information includes uplink control information and uplink data information, and the second type of uplink information corresponds to second uplink identification information.

15. A communication method, characterized in that: The method comprises: receiving downlink data, wherein the downlink data carries at least one type of downlink information in at least one downlink resource location, the downlink resource location corresponding to the type of the downlink information; When downlink information is received at the at least one downlink resource location, it is determined that the type of the received downlink information is the type of downlink information corresponding to the at least one downlink resource location.

16. The method according to claim 15, characterized in that The method further comprises: Uplink data is sent, wherein the uplink data carries at least one type of uplink information in at least one uplink resource location, and the uplink resource location corresponds to the type of the uplink information.

17. The method according to claim 16, characterized in that The downlink resource position and the uplink resource position are frequency domain resource positions, and when downlink information is received at the at least one downlink resource position, determining that the type of the received downlink information is the type of downlink information corresponding to the at least one downlink resource position specifically includes: When downlink information is received at the at least one downlink frequency domain resource location, a type of corresponding downlink information is determined according to the downlink frequency domain resource location, where the frequency domain resource location is one of the following: The position of a resource element RE and the position of a resource element RE group, wherein the RE group includes multiple REs; Before sending the uplink data, the method further includes: Determine uplink frequency domain resource locations corresponding to the at least one type of uplink information.

18. The method according to claim 16, characterized in that The uplink resource position and the downlink resource position are frequency domain resource positions, and when downlink information is received at the at least one downlink resource position, determining that the type of the received downlink information is the type of downlink information corresponding to the at least one downlink resource position specifically includes: When downlink information is received at the at least one downlink frequency domain resource location, determining a type of corresponding downlink information according to a spreading code at the downlink frequency domain resource location; Before sending the uplink data, the method further includes: Determine spreading codes corresponding to the at least one type of uplink information.

19. The method according to claim 16, wherein The uplink resource position and the downlink resource position are time domain resource positions, and when downlink information is received at the at least one downlink resource position, determining that the type of the received downlink information is the type of downlink information corresponding to the at least one downlink resource position specifically includes: When downlink information is received at the at least one downlink time domain resource location, a type of corresponding downlink information is determined according to the downlink time domain resource location, where a time configuration parameter of the time domain resource location is one of the following: System frame number SFN, time slot number, orthogonal frequency division multiplexing OFDM symbol number, OFDM symbol offset value; Before sending the uplink data, the method further includes: Determine uplink time domain resource locations corresponding to the at least one type of uplink information.

20. The method according to any one of claims 16 to 19, characterized in that The at least one type of downlink information includes a first type of downlink information and a second type of downlink information, the first type of downlink information includes broadcast information, the first type of downlink information corresponds to a first downlink resource position, the second type of downlink information includes downlink control information and downlink data information, and the second type of downlink information corresponds to a second downlink resource position; The at least one type of uplink information includes a first type of uplink information and a second type of uplink information, the first type of uplink information includes access information, the first type of uplink information corresponds to a first uplink resource position, the second type of uplink information includes uplink control information and uplink data information, the second type of uplink information corresponds to a second uplink resource position.

21. A communication method, characterized in that: The method comprises: Downlink data is sent, wherein the downlink data carries downlink identification information and at least one type of downlink information, and the downlink identification information is used to indicate the corresponding type of downlink information.

22. The method according to claim 21, characterized in that The method further comprises: receiving uplink data, where the uplink data carries uplink identification information and at least one type of uplink information, where the uplink identification information is used to indicate the corresponding type of uplink information; The type of the at least one type of uplink information is identified according to the uplink identification information.

23. The method according to claim 22, characterized in that The uplink information identifier and the downlink information identifier are preamble codes, and before sending the downlink data, the method further includes: Determining the length of the preamble code corresponding to each of the at least one type of downlink information; The identifying, according to the uplink identification information, a type of the at least one type of uplink information includes: The type of the at least one type of uplink information is determined according to the length of the preamble.

24. The method according to claim 22, characterized in that The uplink information identifier and the downlink information identifier are preamble codes, and before sending the downlink data, the method further includes: Determine a sequence type of a preamble code corresponding to each of the at least one type of downlink information, where the sequence type of the preamble code is one of the following: Pseudo-random PN sequence, longest linear feedback shift register sequence, Gold sequence, Zadoff-Chu sequence; The identifying, according to the uplink identification information, a type of the at least one type of uplink information includes: The type of the at least one type of uplink information is determined according to the sequence type of the preamble.

25. The method according to claim 22, wherein The uplink information identifier and the downlink information identifier are preamble codes, and before sending the downlink data, the method further includes: Determining sequences of preamble codes corresponding to the at least one type of downlink information; The identifying, according to the uplink identification information, a type of the at least one type of uplink information includes: The type of the at least one type of uplink information is determined according to the sequence of the preamble code.

26. The method according to claim 25, wherein a sequence of preamble codes indicating each type of the uplink information and the downlink information is generated by corresponding generation parameters.

27. The method according to claim 22, wherein The uplink information identifier and the downlink information identifier are preamble codes, and before sending the downlink data, the method further includes: Determining cyclic shift modes corresponding to the at least one type of downlink information, and performing cyclic shift on the first sequence according to the corresponding cyclic shift modes to generate preamble codes corresponding to the at least one type of downlink data; The identifying, according to the uplink identification information, a type of the at least one type of uplink information includes: The type of the at least one type of uplink information is determined according to the second sequence and the sequence of the uplink identification information, wherein the sequence in the uplink identification information is generated by performing a corresponding cyclic shift on the second sequence.

28. The method according to claim 22, wherein The uplink information identifier and the downlink information identifier are preamble codes, and before sending the downlink data, the method further includes: Determine a coding mode for a preamble code corresponding to each of the at least one type of downlink information, where the coding mode for the preamble code is one of the following: Manchester encoding, pulse width PIE encoding, Miller encoding, pulse position PPM encoding; The identifying, according to the uplink identification information, a type of the at least one type of uplink information includes: The type of the at least one type of uplink information is determined according to the encoding mode of the preamble.

29. The method according to claim 22, wherein The downlink information identifier is a first field in the downlink data that is located at a first position and occupies a first number of bits. Before sending the downlink data, the method further includes: Determining sequences of first fields corresponding to the at least one type of downlink information; The uplink information identifier is a second field in the uplink data that is located at a second position and occupies a second number of bits, and the identifying, according to the uplink identifier information, a type of the at least one type of uplink information includes: The type of the at least one type of uplink information is determined according to the sequence of the second field.

30. The method according to claim 22, wherein The downlink information identifier is a third field in the downlink data that is located at a third position and occupies a third number of bits. Before sending the downlink data, the method further includes: Determine a coding mode for the third field corresponding to each of the at least one type of downlink information, where the coding mode is one of the following: Manchester encoding, pulse width PIE encoding, Miller encoding, pulse position PPM encoding; The uplink information identifier is a fourth field located at a fourth position and occupying a fourth number of bits in the uplink data, and identifying the type of the at least one type of uplink information according to the uplink identifier information includes: The type of the at least one type of uplink information is determined according to the encoding mode of the fourth field.

31. The method according to claim 22, wherein The downlink information identifier is a fifth field located at a fifth position and occupying a fifth number of bits in the downlink data. Before sending the downlink data, the method further includes: Determining a modulation mode of a third field corresponding to each of the at least one type of downlink information; The uplink information identifier is a sixth field located at a sixth position and occupying a sixth number of bits in the uplink data, and identifying the type of the at least one type of uplink information according to the uplink identifier information includes: The type of the at least one type of uplink information is determined according to the modulation mode of the sixth field.

32. The method according to claim 22, wherein The uplink information identifier and the downlink information identifier are cyclic redundancy check CRC codes, and before sending the downlink data, the method further includes: Determining the number of bits of the CRC code corresponding to the at least one type of downlink information; The identifying, according to the uplink identification information, a type of the at least one type of uplink information includes: The type of the at least one type of uplink information is determined according to the number of bits of the CRC code.

33. The method according to claim 22, wherein The uplink information identifier and the downlink information identifier are cyclic redundancy check CRC codes, and before sending the downlink data, the method further includes: Determine a radio network temporary identifier (RNTI) used when scrambling the CRC codes corresponding to the at least one type of downlink information; The identifying, according to the uplink identification information, a type of the at least one type of uplink information includes: The type of the at least one type of uplink information is determined according to the RNTI used when the CRC code is scrambled.

34. The method according to any one of claims 22 to 33, wherein: The at least one type of downlink information includes a first type of downlink information and a second type of downlink information, the first type of downlink information includes broadcast information, the first type of downlink information corresponds to first downlink identification information, the second type of downlink information includes downlink control information and downlink data information, and the second type of downlink information corresponds to second downlink identification information; The at least one type of uplink information includes a first type of uplink information and a second type of uplink information, the first type of uplink information includes access information, the first type of uplink information corresponds to first uplink identification information, the second type of uplink information includes uplink control information and uplink data information, and the second type of uplink information corresponds to second uplink identification information.

35. A communication method, characterized in that: The method comprises: Downlink data is sent, wherein the downlink data carries at least one type of downlink information in at least one downlink resource position, and the downlink resource position corresponds to the type of the downlink information.

36. The method according to claim 35, characterized in that The method further comprises: receiving uplink data, wherein the uplink data carries at least one type of uplink information in at least one uplink resource location, the uplink resource location corresponding to the type of the uplink information; When uplink information is received at the at least one uplink resource location, it is determined that the type of the received uplink information is the type of uplink information corresponding to the at least one uplink resource location.

37. The method according to claim 36, wherein The downlink resource position and the uplink resource position are frequency domain resource positions. Before sending the downlink data, the method further includes: Determine a downlink frequency domain resource location corresponding to each of the at least one type of downlink information, where the frequency domain resource location is one of the following: The position of a resource element RE and the position of a resource element RE group, wherein the RE group includes multiple REs; The step of determining, when uplink information is received at the at least one uplink resource location, that the type of the received uplink information is the type of uplink information corresponding to the at least one uplink resource location, includes: When uplink information is received at the at least one uplink frequency domain resource location, the type of the corresponding uplink information is determined according to the location of the uplink frequency domain resource.

38. The method according to claim 36, characterized in that The downlink resource position and the uplink resource position are frequency domain resource positions. Before sending the downlink data, the method further includes: Determining spreading codes corresponding to the at least one type of downlink information; The step of determining, when uplink information is received at the at least one uplink resource location, that the type of the received uplink information is the type of uplink information corresponding to the at least one uplink resource location, includes: When uplink information is received at the at least one uplink resource location, the type of the corresponding uplink information is determined according to the spreading code of the uplink frequency domain resource.

39. The method according to claim 36, wherein The downlink resource position and the uplink resource position are time domain resource positions. Before sending the downlink data, the method further includes: Determine downlink time domain resource locations corresponding to the at least one type of downlink information, where a time configuration parameter of the time domain resource location is one of the following: System frame number SFN, time slot number, orthogonal frequency division multiplexing OFDM symbol number, OFDM symbol offset value; The step of determining, when uplink information is received at the at least one uplink resource location, that the type of the received uplink information is the type of uplink information corresponding to the at least one uplink resource location, includes: When uplink information is received at the at least one uplink resource location, the type of the corresponding uplink information is determined according to the uplink time domain resource location.

40. The method according to any one of claims 36 to 39, wherein: The at least one type of downlink information includes a first type of downlink information and a second type of downlink information, the first type of downlink information includes broadcast information, the first type of downlink information corresponds to a first downlink resource position, the second type of downlink information includes downlink control information and downlink data information, and the second type of downlink information corresponds to a second downlink resource position; The at least one type of uplink information includes a first type of uplink information and a second type of uplink information, the first type of uplink information includes access information, the first type of uplink information corresponds to a first uplink resource position, the second type of uplink information includes uplink control information and uplink data information, the second type of uplink information corresponds to a second uplink resource position.

41. An Internet of Things device, characterized in that: The Internet of Things device includes at least one processor, and the at least one processor is used to execute a computer program or instruction to implement the communication method according to any one of claims 1 to 14, or to implement the communication method according to any one of claims 15 to 20.

42. A network device, characterized in that: The network device includes a processor and a memory; The processor is coupled to the memory; The memory is used to store instructions The processor is configured to execute a computer program or instruction stored in the memory to implement the communication method according to any one of claims 21 to 34, or to implement the communication method according to any one of claims 35 to 40.

Images